Network Time Protocol I-Do Extension Field
draft-stenn-ntp-i-do-02
| Document | Type | Expired Internet-Draft (ntp WG) | |
|---|---|---|---|
| Last updated | 2017-04-27 (latest revision 2016-10-24) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-stenn-ntp-i-do-02.txt
Abstract
The first implementation of NTPv4 was released in 2003. NTPv4 is defined by RFC 5905 [RFC5905]. It contains a public-key security protocol, autokey, which is defined by RFC 5906 [RFC5906]. Until very recently, autokey has been the only defined "user" of NTP packet Extension Fields. New proposals for extension fields are being written and there is currently no convenient way to learn if a remote instance of NTP supports any extension fields or not. This proposal contains a method to tell a remote instance of NTP what we (are willing to admit we) support, and ask what they (are willing to admit they) support.
Authors
Harlan Stenn (stenn@nwtime.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)