Network Time
Protocol Extended Information Extension Field
draft-stenn-ntp-extended-information-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Harlan Stenn | ||
| Last updated | 2018-08-26 (Latest revision 2018-02-22) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The network packet format used by NTP has changed very little between NTPv1, defined by RFC 958 [RFC0958] in 1985, and NTPv4, defined by RFC 5905 [RFC5905]. The core network packet used by NTP has no spare bits available for reporting additional state information and no larger data areas available for larger amounts of information. This proposal offers a new extension field that would contains this additional information.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)