Skip to main content

Network Time Protocol Version 4 (NTPv4) Extension Fields
draft-ietf-ntp-extension-field-07

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: brian@innovationslab.net, ntpwg@lists.ntp.org, draft-ietf-ntp-extension-field@ietf.org, "The IESG" <iesg@ietf.org>, ntp-chairs@ietf.org, kodonog@pobox.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'The Network Time Protocol Version 4 (NTPv4) Extension Fields' to Proposed Standard (draft-ietf-ntp-extension-field-07.txt)

The IESG has approved the following document:
- 'The Network Time Protocol Version 4 (NTPv4) Extension Fields'
  (draft-ietf-ntp-extension-field-07.txt) as Proposed Standard

This document is the product of the Network Time Protocol Working Group.

The IESG contact persons are Brian Haberman and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ntp-extension-field/


Ballot Text

Technical Summary: 

The Network Time Protocol Version 4 (NTPv4) [RFC5905] defines the optional usage of extension fields in NTP packets. The current document updates RFC5905 by clarifying some points regarding the usage of the NTP extension fields.

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. Since the publication of NTPv4, various questions were raised on the WG mailing list regarding the correct usage of extension fields. These questions and discussions triggered the publication of the current document. 
 
Document Quality:
 
This document has been reviewed and revised many times. There were no specific external expert reviews conducted. The WGLC notification was sent to the TICTOC working group in addition to the NTP working group
 
Personnel: 

Karen O'Donoghue is acting as the Document Shepherd.  Brian Haberman is the Responsible Area Director. 

RFC Editor Note