draft-ietf-tictoc-ptp-enterprise-profile-08.txt   draft-ietf-tictoc-ptp-enterprise-profile-09.txt 
INTERNET-DRAFT Enterprise Profile for PTP September 2017 INTERNET-DRAFT Enterprise Profile for PTP December 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: March 28, 2018 September 28, 2017 Expires: June 12, 2018 December 12, 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-08.txt draft-ietf-tictoc-ptp-enterprise-profile-09.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 39 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 March 28, 2018. This Internet-Draft will expire on June 12, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
skipping to change at page 9, line 32 skipping to change at page 9, line 32
11. Requirements for Boundary Clocks 11. Requirements for Boundary Clocks
Boundary Clocks SHOULD support multiple simultaneous PTP domains. Boundary Clocks SHOULD support multiple simultaneous PTP domains.
This will require them to maintain servo loops for each of the This will require them to maintain servo loops for each of the
domains supported, at least in software. Boundary clocks MUST NOT domains supported, at least in software. Boundary clocks MUST NOT
combine timing information from different domains. combine timing information from different domains.
12. Management and Signaling Messages 12. Management and Signaling Messages
PTP Management messages MAY be used. Any PTP management message PTP Management messages MAY be used. Management
which is sent with the targetPortIdentity.clockIdentity set to all messages intended for a specific clock, i.e. the [IEEE1588] defined
1s (all clocks) MUST be sent as a multicast message. Management attribute targetPortIdentity.clockIdentity is not set to All 1's,
messages with any other value of for the Clock Identity is MUST be sent as a unicast message. Similarly, if any signaling
intended for a specific clock and MUST be sent as a unicast messages are used they MUST also be sent as unicast messages
message. Similarly, if any signaling messages are used they whenever the message is intended for a specific clock.
MUST also be sent as unicast messages whenever the message is
intended for a specific clock.
13. Forbidden PTP Options 13. Forbidden PTP Options
Clocks operating in the Enterprise Profile SHALL NOT use peer to Clocks operating in the Enterprise Profile SHALL NOT use peer to
peer timing for delay measurement. Grandmaster Clusters are NOT peer timing for delay measurement. Grandmaster Clusters are NOT
ALLOWED. The Alternate Master option is also forbidden. Clocks ALLOWED. The Alternate Master option is also forbidden. Clocks
operating in the Enterprise Profile SHALL NOT use Alternate operating in the Enterprise Profile SHALL NOT use Alternate
Timescales. Timescales.
14. Interoperation with IEEE 1588 Default Profile 14. Interoperation with IEEE 1588 Default Profile
skipping to change at page 10, line 32 skipping to change at page 10, line 32
to achieve interoperability with other profiles. to achieve interoperability with other profiles.
15. Profile Identification 15. Profile Identification
The IEEE 1588 standard requires that all profiles provide the The IEEE 1588 standard requires that all profiles provide the
following identifying information. following identifying information.
PTP Profile: PTP Profile:
Enterprise Profile Enterprise Profile
Version: 1.0 Version: 1.0
Profile identifier: 00-00-5E-01-00 Profile identifier: 00-00-5E-00-01-00
This profile was specified by the IETF This profile was specified by the IETF
A copy may be obtained at A copy may be obtained at
https://datatracker.ietf.org/wg/tictoc/documents https://datatracker.ietf.org/wg/tictoc/documents
16. Security Considerations 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
 End of changes. 6 change blocks. 
13 lines changed or deleted 11 lines changed or added

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