draft-ietf-tictoc-ptp-enterprise-profile-06.txt   draft-ietf-tictoc-ptp-enterprise-profile-07.txt 
Internet-Draft Enterprise Profile for PTP August 2017
TICTOC Working Group Doug Arnold TICTOC Working Group Doug Arnold
Internet Draft Meinberg-USA Internet Draft Meinberg-USA
Intended status: Standards Track Heiko Gerstung Intended status: Standards Track Heiko Gerstung
Meinberg Meinberg
Expires: July 22, 2016 Jan 22, 2016 Expires: February 21, 2017 August 21, 2017
Enterprise Profile for the Precision Time Protocol Enterprise Profile for the Precision Time Protocol
With Mixed Multicast and Unicast Messages With Mixed Multicast and Unicast Messages
draft-ietf-tictoc-ptp-enterprise-profile-06.txt draft-ietf-tictoc-ptp-enterprise-profile-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be provisions of BCP 78 and BCP 79. This document may not be
modified, and derivative works of it may not be created, except to modified, and derivative works of it may not be created, except to
publish it as an RFC and to translate it into languages other than publish it as an RFC and to translate it into languages other than
English. English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 39
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on Agust 4, 2016. This Internet-Draft will expire on February 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 23 skipping to change at page 2, line 23
Table of Contents Table of Contents
1. Introduction 2 1. Introduction 2
2. Conventions used in this document 3 2. Conventions used in this document 3
3. Technical Terms 3 3. Technical Terms 3
4. Problem Statement 5 4. Problem Statement 5
5. Network Technology 6 5. Network Technology 6
6. Time Transfer and Delay Measurement 7 6. Time Transfer and Delay Measurement 7
7. Default Message Rates 8 7. Default Message Rates 8
8. Requirements for Master Clocks 8 8. Requirements for Master Clocks 8
9. Requirements for Slave Clocks 9 9. Requirements for Slave Clocks 8
10. Requirements for Transparent Clocks 9 10. Requirements for Transparent Clocks 9
11. Requirements for Boundary Clocks 10 11. Requirements for Boundary Clocks 9
12. Management and Signaling Messages 10 12. Management and Signaling Messages 9
13. Forbidden PTP Options 10 13. Forbidden PTP Options 9
14. Interoperation with Other PTP Profiles 10 14. Interoperation with Other PTP Profiles 10
15. Security Considerations 11 15. Profile Identification 10
16. IANA Considerations 11 16. Security Considerations 10
17. References 11 17. IANA Considerations 10
17.1. Normative References 11 18. References 11
17.2. Informative References 12 18.1. Normative References 11
18. Acknowledgments 12 18.2. Informative References 11
19. Authors addresses 12 19. Acknowledgments 11
20. Authors addresses 12
1. Introduction 1. Introduction
The Precision Time Protocol ("PTP"), standardized in IEEE 1588, The Precision Time Protocol ("PTP"), standardized in IEEE 1588,
has been designed in its first version (IEEE 1588-2002) with the has been designed in its first version (IEEE 1588-2002) with the
goal to minimize configuration on the participating nodes. Network goal to minimize configuration on the participating nodes. Network
communication was based solely on multicast messages, which unlike communication was based solely on multicast messages, which unlike
NTP did not require that a receiving node ("slave clock") in NTP did not require that a receiving node ("slave clock") in
[IEEE1588] needs to know the identity of the time sources in the [IEEE1588] needs to know the identity of the time sources in the
network (the Master Clocks). network (the Master Clocks).
skipping to change at page 10, line 24 skipping to change at page 10, line 24
Profile clocks will not interoperate with Annex J.3 Default Profile Profile clocks will not interoperate with Annex J.3 Default Profile
Clocks. The Enterprise Profile Profile will will not interoperate Clocks. The Enterprise Profile Profile will will not interoperate
with the Annex J.4 variant of the Default Profile which requires with the Annex J.4 variant of the Default Profile which requires
use of the Peer to Peer Delay Measurement Mechanism. use of the Peer to Peer Delay Measurement Mechanism.
Enterprise Profile Clocks will interoperate with clocks operating Enterprise Profile Clocks will interoperate with clocks operating
in other profiles if the clocks in the other profiles obey the in other profiles if the clocks in the other profiles obey the
rules of the Enterprise Profile. These rules MUST NOT be changed rules of the Enterprise Profile. These rules MUST NOT be changed
to achieve interoperability with other profiles. to achieve interoperability with other profiles.
15. Security Considerations 15. Profile Identification
The IEEE 1588 standard requires that all profiles provide the
following identifying information.
PTP Profile:
Enterprise Profile
Version: 1.0
Profile identifier: 00-00-5E-01-00
This profile was specified by the IETF
A copy may be obtained at
https://datatracker.ietf.org/wg/tictoc/documents
16. Security Considerations
Protocols used to transfer time, such as PTP and NTP can be Protocols used to transfer time, such as PTP and NTP can be
important to security mechanisms which use time windows for keys important to security mechanisms which use time windows for keys
and authorization. Passing time through the networks poses a and authorization. Passing time through the networks poses a
security risk since time can potentially be manipulated. security risk since time can potentially be manipulated.
The use of multiple simultaneous masters, using multiple PTP The use of multiple simultaneous masters, using multiple PTP
domains can mitigate problems from rogue masters and domains can mitigate problems from rogue masters and
man-in-the-middle attacks. See sections 9 and 10. Additional man-in-the-middle attacks. See sections 9 and 10. Additional
security mechanisms are outside the scope of this document. security mechanisms are outside the scope of this document.
16. IANA Considerations 17. IANA Considerations
There are no IANA requirements in this specification. There are no IANA requirements in this specification.
17. References 18. References
17.1. Normative References 18.1. Normative References
[IEEE1588] IEEE std. 1588-2008, "IEEE Standard for a [IEEE1588] IEEE std. 1588-2008, "IEEE Standard for a
Precision Clock Synchronization for Networked Precision Clock Synchronization for Networked
Measurement and Control Systems." July, 2008. Measurement and Control Systems." July, 2008.
[RFC768] Postel, J., "User Datagram Protocol," RFC 768, [RFC768] Postel, J., "User Datagram Protocol," RFC 768,
August, 980. August, 980.
[RFC791] "Internet Protocol DARPA Internet Program Protocol [RFC791] "Internet Protocol DARPA Internet Program Protocol
Specification," RFC 791, September, 1981. Specification," RFC 791, September, 1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC 2119, Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997. March 1997.
[RFC2460] Deering, S., Hinden, R., "Internet Protocol, [RFC2460] Deering, S., Hinden, R., "Internet Protocol,
Version 6 (IPv6) Specification," RFC 2460, Version 6 (IPv6) Specification," RFC 2460,
December, 1998. December, 1998.
17.2. Informative References 18.2. Informative References
[G8271] ITU-T G.8271/Y.1366, "Time and Phase [G8271] ITU-T G.8271/Y.1366, "Time and Phase
Synchronization Aspects of Packet Networks" Synchronization Aspects of Packet Networks"
February, 2012. February, 2012.
[NTP] Mills, D., Martin, J., Burbank, J., Kasch, W., [NTP] Mills, D., Martin, J., Burbank, J., Kasch, W.,
"Network Time Protocol Version 4: Protocol and "Network Time Protocol Version 4: Protocol and
Algorithms Specification," RFC 5905, June 2010. Algorithms Specification," RFC 5905, June 2010.
18. Acknowledgments 19. Acknowledgments
The authors would like to thank members of IETF for reviewing and The authors would like to thank members of IETF for reviewing and
providing feedback on this draft. providing feedback on this draft.
This document was initially prepared using This document was initially prepared using
2-Word-v2.0.template.dot. 2-Word-v2.0.template.dot.
19. Authors' Addresses 20. Authors' Addresses
Doug Arnold Doug Arnold
Meinberg USA Meinberg USA
929 Salem End Road 929 Salem End Road
Framingham, MA 01702 Framingham, MA 01702
USA USA
Email: doug.arnold@meinberg-usa.com Email: doug.arnold@meinberg-usa.com
Heiko Gerstung Heiko Gerstung
 End of changes. 15 change blocks. 
22 lines changed or deleted 40 lines changed or added

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