< draft-ietf-tictoc-ptp-enterprise-profile-21.txt   draft-ietf-tictoc-ptp-enterprise-profile-22.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: 4 March 2022 Meinberg Expires: 8 October 2022 Meinberg
31 August 2021 6 April 2022
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-21 draft-ietf-tictoc-ptp-enterprise-profile-22
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 4 March 2022. This Internet-Draft will expire on 8 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 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
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Technical Terms . . . . . . . . . . . . . . . . . . . . . . . 4 3. Technical Terms . . . . . . . . . . . . . . . . . . . . . . . 4
4. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6 4. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6
5. Network Technology . . . . . . . . . . . . . . . . . . . . . 7 5. Network Technology . . . . . . . . . . . . . . . . . . . . . 7
6. Time Transfer and Delay Measurement . . . . . . . . . . . . . 7 6. Time Transfer and Delay Measurement . . . . . . . . . . . . . 7
7. Default Message Rates . . . . . . . . . . . . . . . . . . . . 9 7. Default Message Rates . . . . . . . . . . . . . . . . . . . . 8
8. Requirements for Master Clocks . . . . . . . . . . . . . . . 9 8. Requirements for Master Clocks . . . . . . . . . . . . . . . 9
9. Requirements for Slave Clocks . . . . . . . . . . . . . . . . 9 9. Requirements for Slave Clocks . . . . . . . . . . . . . . . . 9
10. Requirements for Transparent Clocks . . . . . . . . . . . . . 10 10. Requirements for Transparent Clocks . . . . . . . . . . . . . 9
11. Requirements for Boundary Clocks . . . . . . . . . . . . . . 10 11. Requirements for Boundary Clocks . . . . . . . . . . . . . . 10
12. Management and Signaling Messages . . . . . . . . . . . . . . 10 12. Management and Signaling Messages . . . . . . . . . . . . . . 10
13. Forbidden PTP Options . . . . . . . . . . . . . . . . . . . . 10 13. Forbidden PTP Options . . . . . . . . . . . . . . . . . . . . 10
14. Interoperation with IEEE 1588 Default Profile . . . . . . . . 10 14. Interoperation with IEEE 1588 Default Profile . . . . . . . . 10
15. Profile Identification . . . . . . . . . . . . . . . . . . . 11 15. Profile Identification . . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . . . . . . . . 11
19.1. Normative References . . . . . . . . . . . . . . . . . . 12 19.1. Normative References . . . . . . . . . . . . . . . . . . 11
19.2. Informative References . . . . . . . . . . . . . . . . . 12 19.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
The Precision Time Protocol ("PTP"), first standardized in IEEE 1588, The Precision Time Protocol ("PTP"), first standardized in IEEE 1588,
has been designed in its first version (IEEE 1588-2002) with the goal has been designed in its first version (IEEE 1588-2002) with the goal
to 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
 End of changes. 11 change blocks. 
16 lines changed or deleted 16 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/