draft-ietf-tictoc-ptp-enterprise-profile-20.txt   draft-ietf-tictoc-ptp-enterprise-profile-21.txt 
TICTOC Working Group D.A. Arnold TICTOC Working Group D.A. Arnold
Internet-Draft Meinberg-USA Internet-Draft Meinberg-USA
Intended status: Standards Track H.G. Gerstung Intended status: Standards Track H.G. Gerstung
Expires: 25 February 2022 Meinberg Expires: 4 March 2022 Meinberg
24 August 2021 31 August 2021
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-20 draft-ietf-tictoc-ptp-enterprise-profile-21
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 25 February 2022. This Internet-Draft will expire on 4 March 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 7 skipping to change at page 3, line 7
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
17. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 17. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
18. Security Considerations . . . . . . . . . . . . . . . . . . . 11 18. Security Considerations . . . . . . . . . . . . . . . . . . . 11
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
19.1. Normative References . . . . . . . . . . . . . . . . . . 12 19.1. Normative References . . . . . . . . . . . . . . . . . . 12
19.2. Informative References . . . . . . . . . . . . . . . . . 12 19.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
The Precision Time Protocol ("PTP"), standardized in IEEE 1588, has The Precision Time Protocol ("PTP"), first standardized in IEEE 1588,
been designed in its first version (IEEE 1588-2002) with the goal to has been designed in its first version (IEEE 1588-2002) with the goal
minimize configuration on the participating nodes. Network 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
IEEE 1588-2019 [IEEE1588] needs to know the identity of the time IEEE 1588-2019 [IEEE1588] needs to know the identity of the time
sources in the network (the Master Clocks). This document describes sources in the network (the Master Clocks). This document describes
clock roles and port states using the terms master and slave in order clock roles and port states using the terms master and slave in order
to correspond to the terms used in IEEE 1588, on which this document to correspond to the terms used in IEEE 1588, on which this document
is based. There is an active project in the IEEE to select is based. There is an active project in the IEEE to select
alternative terms. When this project is completed, then master and alternative terms. When this project is completed, then master and
slave will be replaced with the new alternative terms in an update to slave will be replaced with the new alternative terms in an update to
this document. this document.
skipping to change at page 5, line 44 skipping to change at page 5, line 44
Grandmaster of a PTP system, or as a back up to a Grandmaster. Grandmaster of a PTP system, or as a back up to a Grandmaster.
* PTP: The Precision Time Protocol, the timing and synchronization * PTP: The Precision Time Protocol, the timing and synchronization
protocol defined by IEEE 1588. protocol defined by IEEE 1588.
* PTP port: An interface of a PTP clock with the network. Note that * PTP port: An interface of a PTP clock with the network. Note that
there may be multiple PTP ports running on one physical interface, there may be multiple PTP ports running on one physical interface,
for example, a unicast slave which talks to several Grandmaster for example, a unicast slave which talks to several Grandmaster
clocks in parallel. clocks in parallel.
* PTPv2: Refers specifically to the second version of PTP defined by * PTPv2.1: Refers specifically to the third version of PTP defined
IEEE 1588-2019. by IEEE 1588-2019.
* Rogue Master: A clock with a port in the master state, even though * Rogue Master: A clock with a port in the master state, even though
it should not be in the master state according to the Best Master it should not be in the master state according to the Best Master
Clock Algorithm, and does not set the alternate master flag. Clock Algorithm, and does not set the alternate master flag.
* Slave clock: a clock with at least one port in the slave state, * Slave clock: a clock with at least one port in the slave state,
and no ports in the master state. and no ports in the master state.
* Slave Only Clock: An Ordinary Clock which cannot become a Master * Slave Only Clock: An Ordinary Clock which cannot become a Master
Clock. Clock.
 End of changes. 5 change blocks. 
9 lines changed or deleted 9 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/