Wireshark-bugs: [Wireshark-bugs] [Bug 10440] NTP timestamp decoding
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 02 Sep 2014 21:41:33 +0000

changed bug 10440


What Removed Added
CC   jeff.morriss.ws@gmail.com

Comment # 5 on bug 10440 from 
RFC 4330 updated the definition of the timestamp; Wireshark uses the updated
definition:

~~~
      As the NTP timestamp format has been in use for over 20 years, it
      is possible that it will be in use 32 years from now, when the
      seconds field overflows.  As it is probably inappropriate to
      archive NTP timestamps before bit 0 was set in 1968, a convenient
      way to extend the useful life of NTP timestamps is the following
      convention: If bit 0 is set, the UTC time is in the range 1968-
      2036, and UTC time is reckoned from 0h 0m 0s UTC on 1 January



Mills                        Informational                      [Page 7]


RFC 4330             SNTPv4 for IPv4, IPv6 and OSI          January 2006


      1900.  If bit 0 is not set, the time is in the range 2036-2104 and
      UTC time is reckoned from 6h 28m 16s UTC on 7 February 2036.  Note
      that when calculating the correspondence, 2000 is a leap year, and
      leap seconds are not included in the reckoning.
~~~

You are receiving this mail because:
  • You are watching all bug changes.