Network Time Protocol Leap Smear REFID
draft-stenn-ntp-leap-smear-refid-02

Document Type Expired Internet-Draft (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 Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-stenn-ntp-leap-smear-refid-02.txt

Abstract

Leap Seconds are part of UTC. NTP timestamps are based on POSIX timestamps, which require each day to have exactly 86,400 seconds per day. Some applications and environments choose to "smear" leap second corrections over a period that can last up to 24 hours' time, and implement NTP servers that offer smeared time to clients asking them for the time. Both NTP clients and operators have no current way to tell if an NTP server is offering leap-smeared time or not. This is a problem. Similarly, an NTP server may choose to offer leap-smeared time to clients that do not appear to know that a leap event is in-process. This is a problem. This proposal offers a mechanism that provides a simple and clean solution to problems, by giving a way that clients (and operators) can trivially ask for leap-smeared time and detect a server that is offering leap-smeared time.

Authors

Harlan Stenn (stenn@nwtime.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)