Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast Messages

Document Type Active Internet-Draft (tictoc WG)
Last updated 2018-07-31
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: Mar 2016 - 1588v2 profile, if n... )
Document shepherd Karen O'Donoghue
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT          Enterprise Profile for PTP             July 2018

TICTOC Working Group                                         Doug Arnold
Internet Draft                                              Meinberg-USA
Intended status: Standards Track                          Heiko Gerstung
Expires: January 31, 2019                                      

          Enterprise Profile for the Precision Time Protocol
               With Mixed Multicast and Unicast Messages


Status of this Memo
     This Internet-Draft is submitted in full conformance with the
     provisions of BCP 78 and BCP 79. This document may not be
     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

     Internet-Drafts are working documents of the Internet Engineering
     Task Force (IETF), its areas, and its working groups.  Note that
     other groups may also distribute working documents as Internet-
     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

     The list of current Internet-Drafts can be accessed at

     The list of Internet-Draft Shadow Directories can be accessed at

     This Internet-Draft will expire on January 31, 2019.

Copyright Notice
     Copyright (c) 2018 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
     (http://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 the Trust Legal Provisions and are provided without
     warranty as described in the Simplified BSD License.

Arnold and Gerstung                July 31, 2017                [Page 1]

Internet-Draft          Enterprise Profile for PTP             July 2018


    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.

Table of Contents

1.   Introduction                              2
2.   Conventions used in this document         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                     9
14.  Interoperation with Other PTP Profiles   10
15.  Profile Identification                   10
16.  Security Considerations                  10
17.  IANA Considerations                      10
18.  References                               11
     18.1.  Normative References              11
     18.2.  Informative References            11
19. Acknowledgments                           11
20. 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
     [IEEE1588] needs to know the identity of the time sources in the
     network (the Master Clocks).
     The "Best Master Clock Algorithm" ([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
Show full document text