Network Time Protocol Version 4 (NTPv4) Extension Fields
draft-stenn-ntp-extension-fields-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Tal Mizrahi , Danny Mayer , Harlan Stenn | ||
| Last updated | 2017-05-17 (Latest revision 2016-11-13) | ||
| 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) |
https://www.ietf.org/archive/id/draft-stenn-ntp-extension-fields-00.txt
Abstract
Network Time Protocol version 4 (NTPv4) defines the optional usage of extension fields. An extension field, as defined in RFC 5905 [RFC5905], resides after the end of the NTP header, and supplies optional capabilities or information that is not conveyed in the standard NTP header. This document updates RFC 5905 [RFC5905] by clarifying some points regarding NTP extension fields and their usage with legacy Message Authentication Codes (MACs). With the adoption of this update, the authors recommend rescinding [Err3627].
Authors
Tal Mizrahi
Danny Mayer
Harlan Stenn
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)