draft-ietf-tictoc-ptp-enterprise-profile-17.txt   draft-ietf-tictoc-ptp-enterprise-profile-18.txt 
TICTOC Working Group D. Arnold TICTOC Working Group D. Arnold
Internet-Draft Meinberg-USA Internet-Draft Meinberg-USA
Intended status: Standards Track H. Gerstung Intended status: Standards Track H. Gerstung
Expires: December 4, 2020 Meinberg Expires: June 14, 2021 Meinberg
June 2, 2020 December 11, 2020
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-17 draft-ietf-tictoc-ptp-enterprise-profile-18
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 36 skipping to change at page 1, line 36
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 December 4, 2020. This Internet-Draft will expire on June 14, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 9, line 43 skipping to change at page 9, line 43
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. Management messages intended PTP Management messages MAY be used. Management messages intended
for a specific clock, i.e. the IEEE 1588 [IEEE1588] defined attribute for a specific clock, i.e. the IEEE 1588 [IEEE1588] defined attribute
targetPortIdentity.clockIdentity is not set to All 1's, MUST be sent targetPortIdentity.clockIdentity is not set to All 1s, MUST be sent
as a unicast message. Similarly, if any signaling messages are used as a unicast message. Similarly, if any signaling messages are used
they MUST also be sent as unicast messages whenever the message is they MUST also be sent as unicast messages whenever the message is
intended for a specific clock. intended for a specific clock.
13. Forbidden PTP Options 13. Forbidden PTP Options
Clocks operating in the Enterprise Profile SHALL NOT use peer to peer Clocks operating in the Enterprise Profile SHALL NOT use peer to peer
timing for delay measurement. Grandmaster Clusters are NOT ALLOWED. timing for delay measurement. Grandmaster Clusters are NOT ALLOWED.
The Alternate Master option is also NOT ALLOWED. Clocks operating in The Alternate Master option is also NOT ALLOWED. Clocks operating in
the Enterprise Profile SHALL NOT use Alternate Timescales. Unicast the Enterprise Profile SHALL NOT use Alternate Timescales. Unicast
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

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