Network Time Protocol MAC/Last Extension Fields
draft-stenn-ntp-mac-last-ef-04
| Document | Type | Expired Internet-Draft (candidate for ntp WG) | |
|---|---|---|---|
| Last updated | 2019-09-26 (latest revision 2019-03-25) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-stenn-ntp-mac-last-ef-04.txt
Abstract
NTP packets can be authenticated by a Message Authentication Code (MAC) if a MAC is present at the end of an NTP packet. The legacy format for this MAC is not formatted as an NTP Extension Field, and its presence may cause some implementations a parsing ambiguity. This proposal introduces two ways to resolve this problem. One is to provide a MAC Extension Field. The other is an extension field that unambiguously declares itself to be the last extension field in an NTP packet (so any additional data MUST be a legacy MAC). RFC EDITOR: PLEASE REMOVE THE FOLLOWING PARAGRAPH BEFORE PUBLISHING: The source code and issues list for this draft can be found in https://github.com/hstenn/ietf-ntp-mac-last-ef
Authors
Harlan Stenn
(stenn@nwtime.org)
Danny Mayer
(mayer@ntp.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)