Network Time Protocol Last Extension Field
draft-stenn-ntp-last-extension-00
| Document | Type |
Expired Internet-Draft
(ntp WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Harlan Stenn | ||
| Last updated | 2016-09-15 (Latest revision 2016-03-14) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
NTPv4 is defined by RFC 5905 [RFC5905], and it and earlier versions of the NTP Protocol have supported symmetric private key MAC authentication. MACs pre-date the Extension Fields introduced in RFC 5905 [RFC5905], and as the number of Extension Fields grows there is an increasing chance of ambiguity when deciding if the "next" set of data is an Extension Field or a MAC. This proposal defines a new Extension Field which is used to signifiy that it is the last Extension Field in the packet. If present, any subsequent data SHOULD be considered to be a legacy MAC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)