Relaying feedback from David Ingram on draft-ietf-tictoc-security-requirements.
Thanks, Tal. From: David Ingram [mailto:[email protected]] Sent: Wednesday, October 31, 2012 9:06 AM To: [email protected] Cc: Tal Mizrahi Subject: Fwd: Undeliverable: Fwd: Request to review IETF document on time protocol security requirements Hi Karen, One little pin-pricking error in the document is the reference for 1588. It is written: [IEEE1588] IEEE TC 9 Test and Measurement Society 2000, "1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Version 2", IEEE Standard, 2008. but this should be [IEEE1588] IEEE TC 9 Instrumentation and Measurement Society 2000, "1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Version 2", IEEE Standard, 2008. to correct the sponsoring society name. I am not familiar with IETF procedures, so is the security requirements doc intended to be an RFC that others refer to? BTW, the address specified in the email bounced. I am CCing Tal as well just in case this bounces too. Regards, David. David Ingram RPEQ SMIEEE PhD Candidate [cid:[email protected]]Open Access Publications: QUT e-Prints<http://eprints.qut.edu.au/view/person/Ingram,_David.html> School of Electrical Engineering and Computer Science Science and Engineering Faculty | Queensland University of Technology, Brisbane Australia E: [email protected]<mailto:[email protected]> | M: +61 429 882436 "If we knew what it was we were doing, it would not be called research, would it?" -- Albert Einstein -------- Original Message -------- Subject: Undeliverable: Fwd: Request to review IETF document on time protocol security requirements Date: Wed, 31 Oct 2012 17:04:33 +1000 From: Microsoft Outlook <microsoftexchange329e71ec88ae4615bbc36ab6ce411...@exchange.qut.edu.au><mailto:microsoftexchange329e71ec88ae4615bbc36ab6ce411...@exchange.qut.edu.au> To: David Ingram <[email protected]><mailto:[email protected]> smtp48.gate.ord1a.rsapps.net rejected your message to the following e-mail addresses: [email protected]<mailto:[email protected]> smtp48.gate.ord1a.rsapps.net gave this error: <[email protected]><mailto:[email protected]>: Relay access denied. Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery. Diagnostic information for administrators: Generating server: QUTEXEDGE05.qut.edu.au [email protected]<mailto:[email protected]> smtp48.gate.ord1a.rsapps.net #550 5.7.1 <[email protected]><mailto:[email protected]>: Relay access denied. ## Original message headers: Received: from qutexhub02.qut.edu.au (131.181.107.107) by qutexedge05.qut.edu.au (131.181.191.22) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 31 Oct 2012 17:04:27 +1000 Received: from [127.0.0.1] (131.181.118.254) by outlook.qut.edu.au (131.181.107.107) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 31 Oct 2012 17:04:26 +1000 Message-ID: <[email protected]><mailto:[email protected]> Date: Wed, 31 Oct 2012 17:04:21 +1000 From: David Ingram <[email protected]><mailto:[email protected]> Organization: Queensland University of Technology User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: <[email protected]><mailto:[email protected]> Subject: Fwd: Request to review IETF document on time protocol security requirements References: <033e01cdb705$d7aa3cb0$86feb610$@com> In-Reply-To: <033e01cdb705$d7aa3cb0$86feb610$@com> X-Forwarded-Message-Id: <033e01cdb705$d7aa3cb0$86feb610$@com> Content-Type: multipart/alternative; boundary="------------020804070908090102010005" Return-Path: [email protected]<mailto:[email protected]>
<<inline: qut_logo.png>>
Reporting-MTA: dns; QUTEXEDGE05.qut.edu.au Final-recipient: RFC822; [email protected] Action: failed Status: 5.7.1 Remote-MTA: dns; smtp48.gate.ord1a.rsapps.net X-Supplementary-Info: <smtp48.gate.ord1a.rsapps.net #5.7.1 smtp;550 5.7.1 <[email protected]>: Relay access denied.>
--- Begin Message ---Hi Karen, One little pin-pricking error in the document is the reference for 1588. It is written: [IEEE1588] IEEE TC 9 Test and Measurement Society 2000, "1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Version 2", IEEE Standard, 2008. but this should be [IEEE1588] IEEE TC 9 Instrumentation and Measurement Society 2000, "1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems Version 2", IEEE Standard, 2008. to correct the sponsoring society name. I am not familiar with IETF procedures, so is the security requirements doc intended to be an RFC that others refer to? Regards, David. David Ingram RPEQ SMIEEE PhD Candidate Open Access Publications: QUT e-Prints<http://eprints.qut.edu.au/view/person/Ingram,_David.html> School of Electrical Engineering and Computer Science Science and Engineering Faculty | Queensland University of Technology, Brisbane Australia E: [email protected]<mailto:[email protected]> | M: +61 429 882436 "If we knew what it was we were doing, it would not be called research, would it?" -- Albert Einstein -------- Original Message -------- Subject: Request to review IETF document on time protocol security requirements Date: Wed, 31 Oct 2012 11:14:45 +1000 From: Lauren Pasquarelli <[email protected]><mailto:[email protected]> To: David Ingram <[email protected]><mailto:[email protected]> ISPCS community, Below is a link to the time protocol security requirements document that I mentioned to some of you during the recent ISPCS meeting. This document is currently in development by the IETF community, and it is intended to help define security requirements for time synchronization protocols. We would very much appreciate your review and comments. The intention is for this document to help inform the security efforts of both the IETF and IEEE 1588 communities. http://datatracker.ietf.org/doc/draft-ietf-tictoc-security-requirements/ You may send comments to either me ([email protected]<mailto:[email protected]>) or to the tictoc mailing list ([email protected]<mailto:[email protected]>). Regards, Karen O'Donoghue [email protected]<mailto:[email protected]><<inline: qut_logo.png>>
--- End Message ---
_______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
