Document Action: 'Guidelines for Defining Packet Timestamps' to Informational RFC (draft-ietf-ntp-packet-timestamps-09.txt)
The IESG <iesg-secretary@ietf.org> Tue, 17 March 2020 21:05 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 839093A0593; Tue, 17 Mar 2020 14:05:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Guidelines for Defining Packet Timestamps' to Informational RFC (draft-ietf-ntp-packet-timestamps-09.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.121.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: draft-ietf-ntp-packet-timestamps@ietf.org, rfc-editor@rfc-editor.org, odonoghue@isoc.org, ntp-chairs@ietf.org, ntp@ietf.org, Karen O'Donoghue <odonoghue@isoc.org>, The IESG <iesg@ietf.org>, suresh@kaloom.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <158447914351.32043.4649021216196181936@ietfa.amsl.com>
Date: Tue, 17 Mar 2020 14:05:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rAo6bD9gIO9PQ7gtVUvIxeQ6k74>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 21:05:45 -0000
The IESG has approved the following document: - 'Guidelines for Defining Packet Timestamps' (draft-ietf-ntp-packet-timestamps-09.txt) as Informational RFC This document is the product of the Network Time Protocol Working Group. The IESG contact persons are Éric Vyncke and Suresh Krishnan. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-ntp-packet-timestamps/ Technical Summary 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 document. 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. Working Group Summary The document has clear working group consensus for publication, and has been reviewed by several WG participants since its initial adoption as a working group item. Document Quality This document has been reviewed and revised several times during its development. There were no specific external expert reviews conducted. Personnel Karen O'Donoghue is acting as the Document Shepherd. Suresh Krishnan is the Responsible Area Director.