< draft-ietf-tictoc-ptp-enterprise-profile-14.txt   draft-ietf-tictoc-ptp-enterprise-profile-15.txt >
TICTOC Working Group D. Arnold TICTOC Working Group D. Arnold
Internet-Draft H. Gerstung Internet-Draft H. Gerstung
Intended status: Standards Track Meinberg Intended status: Standards Track Meinberg
Expires: September 30, 2019 March 29, 2019 Expires: October 6, 2019 April 4, 2019
Enterprise Profile for the Precision Time Protocol With Mixed Multicast Enterprise Profile for the Precision Time Protocol With Mixed Multicast
and Unicast Messages and Unicast Messages
draft-ietf-tictoc-ptp-enterprise-profile-14 draft-ietf-tictoc-ptp-enterprise-profile-15
Abstract Abstract
This document describes a profile for the use of the Precision Time This document describes a profile for the use of the Precision Time
Protocol in an IPV4 or IPv6 Enterprise information system Protocol in an IPV4 or IPv6 Enterprise information system
environment. The profile uses the End to End Delay Measurement environment. The profile uses the End to End Delay Measurement
Mechanism, allows both multicast and unicast Delay Request and Delay Mechanism, allows both multicast and unicast Delay Request and Delay
Response Messages. Response Messages.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 30, 2019. This Internet-Draft will expire on October 6, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 11, line 24 skipping to change at page 11, line 24
Protocols used to transfer time, such as PTP and NTP can be important Protocols used to transfer time, such as PTP and NTP can be important
to security mechanisms which use time windows for keys and to security mechanisms which use time windows for keys and
authorization. Passing time through the networks poses a security authorization. Passing time through the networks poses a security
risk since time can potentially be manipulated. The use of multiple risk since time can potentially be manipulated. The use of multiple
simultaneous masters, using multiple PTP domains can mitigate simultaneous masters, using multiple PTP domains can mitigate
problems from rogue masters and man-in-the-middle attacks. See problems from rogue masters and man-in-the-middle attacks. See
sections 9 and 10. Additional security mechanisms are outside the sections 9 and 10. Additional security mechanisms are outside the
scope of this document. scope of this document.
PTP native management messages SHOULD not be used, due to the lack of PTP native management messages SHOULD NOT be used, due to the lack of
a security mechanism for this option. Secure management can be a security mechanism for this option. Secure management can be
obtained using standard management mechanisms which include security, obtained using standard management mechanisms which include security,
for example NETCONF NETCONF [RFC6241]. for example NETCONF NETCONF [RFC6241].
General security considerations of time protocols are discussed in General security considerations of time protocols are discussed in
RFC 7384 [RFC7384]. RFC 7384 [RFC7384].
19. References 19. References
19.1. Normative References 19.1. Normative References
[IEEE1588] [IEEE1588]
Institute of Electrical and Electronics Engineers, "IEEE Institute of Electrical and Electronics Engineers, "IEEE
std. 1588-2008, "IEEE Standard for a Precision Clock 1588-2008: IEEE Standard for a Precision Clock
Synchronization for Networked Measurement and Control Synchronization for Networked Measurement and Control
Systems."", 7 2008, <https://www.ieee.org>. Systems.", July 2008, <https://www.ieee.org>.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC0768, August 1980, DOI 10.17487/RFC0768, August 1980,
<https://www.rfc-editor.org/info/rfc768>. <https://www.rfc-editor.org/info/rfc768>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>. <https://www.rfc-editor.org/info/rfc791>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 12, line 18 skipping to change at page 12, line 18
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200, (IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017, DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8200>.
19.2. Informative References 19.2. Informative References
[G8271] International Telecommunication Union, "ITU-T G.8271/ [G8271] International Telecommunication Union, "ITU-T G.8271/
Y.1366, "Time and Phase Synchronization Aspects of Packet Y.1366: Time and Phase Synchronization Aspects of Packet
Networks"", 2 2012, <https://www.itu.int>. Networks", February 2012, <https://www.itu.int>.
[ISPCS] Arnold, D., "Plugfest Report", 10 2017, [ISPCS] Arnold, D., "ISPCS 2017 Plugfest Report", October 2017,
<https://www.ispcs.org>. <https://www.ispcs.org>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<https://www.rfc-editor.org/info/rfc5905>. <https://www.rfc-editor.org/info/rfc5905>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC7384] Mizrahi, T., "Security Requirements of Time Protocols in [RFC7384] Mizrahi, T., "Security Requirements of Time Protocols in
Packet Switched Networks", RFC 7384, DOI 10.17487/RFC7384, Packet Switched Networks", RFC 7384, DOI 10.17487/RFC7384,
October 2014, <https://www.rfc-editor.org/info/rfc7384>. October 2014, <https://www.rfc-editor.org/info/rfc7384>.
Authors' Addresses Authors' Addresses
Doug Arnold Doug Arnold
Meinberg Meinberg Funkuhren GmbH & Co. KG
Lange Wand 9 Lange Wand 9
Bad Pyrmont 31812 Bad Pyrmont 31812
Germany Germany
Email: doug.arnold@meinberg.de Email: doug.arnold@meinberg.de
Heiko Gerstung Heiko Gerstung
Meinberg Meinberg Funkuhren GmbH & Co. KG
Lange Wand 9 Lange Wand 9
Bad Pyrmont 31812 Bad Pyrmont 31812
Germany Germany
Email: heiko.gerstung@meinberg.de Email: heiko.gerstung@meinberg.de
 End of changes. 10 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/