Re: [Ntp] [Technical Errata Reported] RFC8877 (7012)

[Steven Sommars <[e-mail]>]

>> Somewhat related:  Wireshark decodes NTP timestamp=0x00000000.xxxxxxxx
incorrectly.
Nope.  The wireshark folks pointed out that RFC5905 says:

    In either format,a value of zero is a special case representing
unknown or unsynchronized time.


Sorry for the mistake.


On Tue, Jul 5, 2022 at 5:22 PM Steven Sommars <[e-mail]>
wrote:

> Somewhat related:  Wireshark decodes NTP timestamp=0x00000000.xxxxxxxx
> incorrectly.
> https://gitlab.com/wireshark/wireshark/-/issues/18174
>
> On Tue, Jul 5, 2022 at 12:45 PM MORTON JR., AL <[e-mail]> wrote:
>
>> Thanks Greg!
>> (this is a Reject).
>> Al
>>
>> > -----Original Message-----
>> > From: [e-mail] <[e-mail]>
>> > Sent: Tuesday, July 5, 2022 10:38 AM
>> > To: [e-mail]; [e-mail];
>> > [e-mail]; MORTON JR., AL <[e-mail]>;
>> > [e-mail]; [e-mail]; [e-mail];
>> > [e-mail]
>> > Cc: [e-mail]; [e-mail]
>> > Subject: RE: [Ntp] [Technical Errata Reported] RFC8877 (7012)
>> >
>> > Please note that the NTP epoch is Jan 1 1900.  The original text is
>> correct.
>> >
>> >
>> > Greg Dowd  Microchip - Freq & Time Div.
>> >
>> > Assoc. Technical Fellow - Engineering
>> > 3870 N First St, San Jose, CA 95134
>> > Direct: 408-964-7643
>> > [e-mail]
>> >
>> > -----Original Message-----
>> > From: ntp <[e-mail]> On Behalf Of RFC Errata System
>> > Sent: Monday, July 4, 2022 3:23 PM
>> > To: [e-mail]; [e-mail];
>> [e-mail];
>> > [e-mail]; [e-mail]; [e-mail];
>> > [e-mail]
>> > Cc: [e-mail]; [e-mail]; [e-mail]
>> > Subject: [Ntp] [Technical Errata Reported] RFC8877 (7012)
>> >
>> > EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the
>> > content is safe
>> >
>> > The following errata report has been submitted for RFC8877, "Guidelines
>> for
>> > Defining Packet Timestamps".
>> >
>> > --------------------------------------
>> > You may review the report below and at:
>> > https://urldefense.com/v3/__https://www.rfc-
>> > editor.org/errata/eid7012__;!!BhdT!jukU3aC-
>> >
>> LO25x_iDFWb2hspXMANwTayZRkwAKICIQY2LOECRroRbULEwVTi8fHlHvF8UImcNdt5BDqg2Lg$
>> >
>> > --------------------------------------
>> > Type: Technical
>> > Reported by: Nikolai Malykh <[e-mail]>
>> >
>> > Section: 4.2
>> >
>> > Original Text
>> > -------------
>> >    Wraparound:
>> >       This time format wraps around every 2^(32) seconds, which is
>> >       roughly 136 years.  The next wraparound will occur in the year
>> >       2036.
>> >
>> >
>> > Corrected Text
>> > --------------
>> >    Wraparound:
>> >       This time format wraps around every 2^(32) seconds, which is
>> >       roughly 136 years.  The next wraparound will occur in the year
>> >       2106.
>> >
>> >
>> > Notes
>> > -----
>> > 1970+136=2106, not 2036
>> >
>> > Instructions:
>> > -------------
>> > This erratum is currently posted as "Reported". If necessary, please use
>> > "Reply All" to discuss whether it should be verified or rejected. When a
>> > decision is reached, the verifying party can log in to change the
>> status and
>> > edit the report, if necessary.
>> >
>> > --------------------------------------
>> > RFC8877 (draft-ietf-ntp-packet-timestamps-09)
>> > --------------------------------------
>> > Title               : Guidelines for Defining Packet Timestamps
>> > Publication Date    : September 2020
>> > Author(s)           : T. Mizrahi, J. Fabini, A. Morton
>> > Category            : INFORMATIONAL
>> > Source              : Network Time Protocols
>> > Area                : Internet
>> > Stream              : IETF
>> > Verifying Party     : IESG
>> >
>> > _______________________________________________
>> > ntp mailing list
>> > [e-mail]
>> >
>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ntp__;!!BhdT
>> > !jukU3aC-
>> >
>> LO25x_iDFWb2hspXMANwTayZRkwAKICIQY2LOECRroRbULEwVTi8fHlHvF8UImcNdt4G_ybaGw$
>>
>> _______________________________________________
>> ntp mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/ntp
>>
>