The Network Time Protocol Version 4 Extension Format
draft-choudharykumar-ntp-ntpv4-extended-extensions-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vikram Choudhary , Ulrich Windl | ||
| Last updated | 2015-12-06 (Latest revision 2015-06-04) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 Time Protocol Version 4 (NTPv4) defines the optional usage of extension fields. An extension field as defined in RFC 5905, is an optional field that resides at the end of the NTP header and can be used to add optional capabilities or additional information that is not conveyed in the standard NTP header. This document redefines NTP extension header proposed in RFC 5905 for addressing unnecessary padding issue which is required for differentiating between NTP extension and MAC data.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)