Tapio Sokura wrote:
Simon Arlott wrote:

Where exactly does it say in the RFCs that the leap bits can be set more than 24 hours before the leap bit is inserted?

It's possible to read it wrong as "set before '23:59 on the day of insertion'" not "set 'before 23:59' on 'the day of insertion'" and your way makes more sense.

It would be interesting to know if the severs that are sending leap=01 have been configured to do so since the announcement of the leap second, or if they've been manually configured like that for years.

I would like to know why they advertise the leap bits as well. Maybe some reference clock implementation is flawed and sets the bits too early and it then just propagates through to the higher stratum servers.

Maybe we should take this to comp.protocols.time.ntp anyway and ask the guys who wrote the protocol and the reference implementation instead of guessing here..


I've started with a list of servers:
        stratum 1 servers in pool.ntp.org at 13:00 GMT today
        stratum 1 servers used by the above servers

This is a list of leap=01 servers with their stratum 0 and leap=01 sources:

195.234.188.26: 193.204.114.232 193.10.7.250 195.234.188.3 213.157.170.82 GPS
195.234.188.3: 193.204.114.232 193.10.7.250 195.234.188.26 213.157.170.82 GPS
62.3.200.116: 193.25.198.254 MSF
80.127.4.179: 193.204.114.232 PG0A
84.92.75.21: 193.10.7.250 193.10.7.246 140.203.16.5 (DCFa MSFa - code used 
incapable of leap=01)
128.4.1.1: GPS1 PPS
130.206.3.166: GPS
140.203.16.5: 134.226.81.3 GPS
150.214.94.5: 130.206.3.166 GPS
193.10.7.246: ?
193.10.7.250: ?
193.204.114.231: 193.204.114.232 193.204.114.233 IEN
193.204.114.232: 193.204.114.231 193.204.114.233 IEN
193.204.114.233: 193.204.114.231 193.204.114.232 IEN
212.244.160.67: 80.48.104.202 192.168.0.3 PPS
212.244.160.68: 192.168.0.2 PPS
213.157.170.82: 193.204.114.232 195.234.188.26 195.234.188.3
193.25.198.254: 193.10.7.246 193.204.114.233 132.146.236.132
134.226.81.3: 195.40.0.250 195.40.1.230
130.206.3.166: GPS
80.48.104.202: ATOM dumb
132.146.236.132: ?
195.40.0.250: 195.40.1.250 128.4.1.1 195.224.255.2 134.226.81.3
195.40.1.230: 195.40.0.250 195.40.1.250 128.4.1.1 195.224.255.2 134.226.81.3
195.40.1.250: 195.40.0.250 128.4.1.1 195.224.255.2 134.226.81.3
195.224.255.2: 62.3.200.116 80.229.167.81
80.229.167.81: ?


possible sources of leap=01: [193.204.114.231] 193.204.114.232 
[193.204.114.233] 80.48.104.202

Since 193.204.114.231 193.204.114.232 193.204.114.233 all have each other as peers, any one of them could be the local source of it, but the remote servers are only using 193.204.114.232.

servers with leap=01 that don't allow listing of peers:
        193.10.7.246 193.10.7.250 132.146.236.132 (stratum 1)
        80.229.167.81 (stratum 4)

--
Simon Arlott

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to