]> Network Time Foundation

P.O. Box 918 Talent, OR 97540 US stenn@nwtime.org

General Internet Engineering Task Force NTP 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-extended-information-ef The core network packet used by NTP has no spare bits available for reporting additional state information and no larger data areas available for larger amounts of information. This proposal offers a new extension field that would contain this additional information.

The core NTP packet format has changed little since RFC 958 was published in 1985. Since then, there has been demonstrated need to convey additional information about NTP's state in an NTP packet but no backward-compatible way to usurp the few otherwise potentially available bits has been found, and no larger data areas are available in the core packet structure. This proposal offers a new extension field that would contain this additional information.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

The Field Type of the Extended Information EF includes a version number field in the low-order bits of the first octet, to make it easier to evolve this specification. The initial specification for this proposal uses Version 0, which equates to 0x0009 [ADJUST AS NEEDED BASED ON IANA, IF AN IANA REGISTRY IS USED]. A future revision for Version 1 would use 0x0109 [IBID]. The payload for Version 0 is comprised of a two octet Content Descriptor followed by a two octet Content Data field, as described below.

Field Type: TBD (Recommendation for IANA: 0x0009 (Extended-Information, Version 0)) Field Length: as needed

There are 16 bits available for state information in the Version 0 Extended Information Content Descriptor. These bits are allocated as follows: TAI Offset is stored in the low-order 8 bits (the second octet) of the Content Data. Interleave Mode indicator in the low order bit of the first octet of the Content Data. [NOTE: this may not be useful, and it can be removed if desired. It can serve as a belt-and-suspenders way to identify when a packet contains interleaved timestamps.] Reserved for future versions. SHOULD be zeroes for Version 0, and the meaning of any nonzero values is unspecified. The Content Data field of the Version 0 Extended Information extension field is comprised of two octets, with the contents allocated as follows: The low-order 8 bits (NNNN) are the TAI Offset. Any data in the high-order 8 bits (XXXX) are not part of the TAI Offset. A value of 0 in the low-order bit of the first octet indicates that the timestamps in the base packet are not interleave-mode timestamps. A value of 1 in the low-order bit of the first octet indicates that the timestamps in the base packet are interleave-mode timestamps. thru Any of the seven high-order bits in the first octet are reserved for future versions and SHOULD be zero for Version 0. The meaning of any nonzero values is unspecified.

Example: A system that wants to convey an offset to TAI of 36 seconds, and show it is in interleave mode.

The author wishes to acknowledge the contributions of Martin Burnicki and Sam Weiler.

This memo requests IANA to allocate NTP Extension Field Type 0x0009 (Extended-Information, Version 0) for this proposal.

No unusual or special security considerations are known to be associated with this proposal.

&RFC0958; &RFC2119; &RFC5905;