Network Time Protocol: Secure Network Time
draft-stenn-ntp-secure-network-time-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Harlan Stenn , Professor David L. Mills , Philip Prindeville | ||
| Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
| 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 proposal specifies a means for NTP instances that can establish a TCP connection between themselves to create secure ephemeral keys. With the known weaknesses of the public-key security protocol, Autokey, which is defined by RFC 5906 [RFC5906], a replacement for Autokey that supports at least Client/Server and Symmetric modes must be provided.
Authors
Harlan Stenn
Professor David L. Mills
Philip Prindeville
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)