[Ntp] Last Call: <draft-ietf-ntp-packet-timestamps-07.txt> (Guidelines for Defining Packet Timestamps) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 06 February 2020 20:27 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ntp@ietf.org
Delivered-To: ntp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A67120142; Thu, 6 Feb 2020 12:27:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.117.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: ntp@ietf.org, odonoghue@isoc.org, Karen O'Donoghue <odonoghue@isoc.org>, ntp-chairs@ietf.org, draft-ietf-ntp-packet-timestamps@ietf.org, suresh@kaloom.com
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <158102086293.5064.14061859204002344539.idtracker@ietfa.amsl.com>
Date: Thu, 06 Feb 2020 12:27:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/m-AjnRqhz_cjpwBdbAbSV2_yzI8>
Subject: [Ntp] Last Call: <draft-ietf-ntp-packet-timestamps-07.txt> (Guidelines for Defining Packet Timestamps) to Informational RFC
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 20:27:44 -0000

The IESG has received a request from the Network Time Protocol WG (ntp) to
consider the following document: - 'Guidelines for Defining Packet Timestamps'
  <draft-ietf-ntp-packet-timestamps-07.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-02-20. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   Various network protocols make use of binary-encoded timestamps that
   are incorporated in the protocol packet format, referred to as packet
   timestamps for short.  This document specifies guidelines for
   defining packet timestamp formats in networking protocols at various
   layers.  It also presents three recommended timestamp formats.  The
   target audience of this memo includes network protocol designers.  It
   is expected that a new network protocol that requires a packet
   timestamp will, in most cases, use one of the recommended timestamp
   formats.  If none of the recommended formats fits the protocol
   requirements, the new protocol specification should specify the
   format of the packet timestamp according to the guidelines in this

   The rationale behind defining a relatively small set of recommended
   formats is that it enables significant reuse; network protocols can
   typically reuse the timestamp format of the Network Time Protocol
   (NTP) or the Precision Time Protocol (PTP), allowing a
   straightforward integration with an NTP or a PTP-based timer.
   Moreover, since accurate timestamping mechanisms are often
   implemented in hardware, a new network protocol that reuses an
   existing timestamp format can be quickly deployed using existing
   hardware timestamping capabilities.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.