Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast Messages
draft-ietf-tictoc-ptp-enterprise-profile-17
|
| Document |
Type |
|
Active Internet-Draft (tictoc WG)
|
|
Last updated |
|
2020-06-02
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
|
|
Document shepherd |
|
Karen O'Donoghue
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
TICTOC Working Group D. Arnold
Internet-Draft Meinberg-USA
Intended status: Standards Track H. Gerstung
Expires: December 4, 2020 Meinberg
June 2, 2020
Enterprise Profile for the Precision Time Protocol With Mixed Multicast
and Unicast Messages
draft-ietf-tictoc-ptp-enterprise-profile-17
Abstract
This document describes a profile for the use of the Precision Time
Protocol in an IPV4 or IPv6 Enterprise information system
environment. The profile uses the End to End Delay Measurement
Mechanism, allows both multicast and unicast Delay Request and Delay
Response Messages.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 4, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Arnold & Gerstung Expires December 4, 2020 [Page 1]
Internet-Draft Enterprise Profile for PTP June 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Technical Terms . . . . . . . . . . . . . . . . . . . . . . . 3
4. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5
5. Network Technology . . . . . . . . . . . . . . . . . . . . . 6
6. Time Transfer and Delay Measurement . . . . . . . . . . . . . 7
7. Default Message Rates . . . . . . . . . . . . . . . . . . . . 8
8. Requirements for Master Clocks . . . . . . . . . . . . . . . 8
9. Requirements for Slave Clocks . . . . . . . . . . . . . . . . 8
10. Requirements for Transparent Clocks . . . . . . . . . . . . . 9
11. Requirements for Boundary Clocks . . . . . . . . . . . . . . 9
12. Management and Signaling Messages . . . . . . . . . . . . . . 9
13. Forbidden PTP Options . . . . . . . . . . . . . . . . . . . . 10
14. Interoperation with IEEE 1588 Default Profile . . . . . . . . 10
15. Profile Identification . . . . . . . . . . . . . . . . . . . 10
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
17. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
18. Security Considerations . . . . . . . . . . . . . . . . . . . 11
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
19.1. Normative References . . . . . . . . . . . . . . . . . . 11
19.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The Precision Time Protocol ("PTP"), standardized in IEEE 1588, has
been designed in its first version (IEEE 1588-2002) with the goal to
minimize configuration on the participating nodes. Network
communication was based solely on multicast messages, which unlike
NTP did not require that a receiving node ("slave clock") in
IEEE 1588-2008 [IEEE1588] needs to know the identity of the time
sources in the network (the Master Clocks).
The "Best Master Clock Algorithm" (IEEE 1588-2008 [IEEE1588]
Subclause 9.3), a mechanism that all participating PTP nodes must
follow, set up strict rules for all members of a PTP domain to
determine which node shall be the active sending time source (Master
Clock). Although the multicast communication model has advantages in
smaller networks, it complicated the application of PTP in larger
networks, for example in environments like IP based telecommunication
Show full document text