Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast messages
draft-ietf-tictoc-ptp-enterprise-profile-28

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-tictoc-ptp-enterprise-profile@ietf.org, ek.ietf@gmail.com, rfc-editor@rfc-editor.org, tictoc-chairs@ietf.org, tictoc@ietf.org
Subject: Protocol Action: 'Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast messages' to Proposed Standard (draft-ietf-tictoc-ptp-enterprise-profile-28.txt)

The IESG has approved the following document:
- 'Enterprise Profile for the Precision Time Protocol With Mixed
   Multicast and Unicast messages'
  (draft-ietf-tictoc-ptp-enterprise-profile-28.txt) as Proposed Standard

This document is the product of the Timing over IP Connection and Transfer of
Clock Working Group.

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tictoc-ptp-enterprise-profile/

Ballot Text

Technical Summary

   This document describes a PTP Profile for the use of the Precision
   Time Protocol in an IPv4 or IPv6 Enterprise information system
   environment.  The PTP Profile uses the End-to-End delay measurement
   mechanism, allows both multicast and unicast Delay Request and Delay
   Response messages.

Working Group Summary

   Nothing of note.

Document Quality

   The document has implementations and interoperability has been
   demonstrated.  Collaboration with IEEE 1588 has been coordinated by
   at least one of the authors (and working group participants at the
   time of original writing).

Personnel

   The Document Shepherd for this document is Erik Kline. The Responsible
   Area Director is Erik Kline.

IESG Note

  This is the final document output from TICTOC.  After this, I
  expect to close the working group.  NTP has been rechartered to
  encompass work on several time sync protocols, and future work
  can be brought there (or dispatched therefrom).

IANA Note

  No IANA actions.

RFC Editor Note