NTPv5 use cases and requirements
draft-gruessing-ntp-ntpv5-requirements-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | James Gruessing | ||
| Last updated | 2022-05-17 (Latest revision 2021-11-13) | ||
| Replaced by | draft-ietf-ntp-ntpv5-requirements, draft-ietf-ntp-ntpv5-requirements | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| 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
This document describes the use cases, requirements, and considerations that should be factored in the design of a successor protocol to supersede version 4 of the NTP protocol [RFC5905] presently referred to as NTP version 5 ("NTPv5"). This document is non-exhaustive and does not in its current version represent working group consensus.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)