Network Time Protocol Extended Information Extension Field
draft-stenn-ntp-extended-information-00
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Harlan Stenn | ||
| Last updated | 2017-04-27 (Latest revision 2016-10-24) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-stenn-ntp-extended-information-00.txt
https://www.ietf.org/archive/id/draft-stenn-ntp-extended-information-00.txt
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 additinal 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.)