Using NTP Extension Fields without Authentication
draft-mizrahi-ntp-extension-field-03
| Document | Type |
Replaced Internet-Draft
(ntp WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tal Mizrahi , Danny Mayer | ||
| Last updated | 2014-07-21 (Latest revision 2014-01-02) | ||
| Replaced by | draft-ietf-ntp-extension-field | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ntp-extension-field | |
| Consensus boilerplate | Unknown | ||
| 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 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. The current definition of extension fields in NTPv4 is somewhat ambiguous regarding the connection between extension fields and the presence of a Message Authentication Code (MAC). This draft clarifies the usage of extension fields in the presence and in the absence of a MAC, while maintaining interoperability with existing implementations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)