[1] RFC 5905 - Network Time Protocol Version 4: Protocol and Algorithms Specification ( (2017-02-26 17:11:07 +09:00)) https://tools.ietf.org/html/rfc5905#section-6

[2] RFC 868

[3] RFC 1037 - NFILE - a file access protocol, 2021-01-24T23:29:22.000Z, 2021-03-12T08:41:17.532Z https://tools.ietf.org/html/rfc1037#page-46

[4] 「200ピコ秒問題」 (2021-04-24T10:21:54.000Z) http://deztec.jp/x/10/faireal/d70408.xml

[5] rfc3830, 2021-06-09T07:03:59.000Z https://datatracker.ietf.org/doc/html/rfc3830#section-4.2.8

[6] Time formatting and storage bugs - Wikipedia, 2023-11-24T03:13:21.000Z, 2023-11-25T07:03:04.138Z https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2036

The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2³² seconds (136 years) and a theoretical resolution of 2⁻³² second (233 picoseconds). NTP uses an epoch of 1 January 1900. The first rollover occurs in 2036, prior to the UNIX year 2038 problem.

[7] The NTP Era and Era Numbering, 2012-05-12T23:56:30.000Z, 2023-11-25T07:03:55.192Z https://www.eecis.udel.edu/~mills/y2k.html

[8] t= (SDP)