Re: [Ntp] CLOCK_TAI (was NTPv5: big picture)

[Philip Prindeville <[e-mail]>]

> On Jan 6, 2021, at 3:58 AM, Martin Burnicki <[e-mail]> wrote:
> 
> Philip Prindeville wrote:
>> 
>>> On Jan 5, 2021, at 9:09 AM, Martin Burnicki <martin.burnicki=[e-mail]> wrote:
>>> 
>>> Except the versions that aren't updated anymore, or embedded of IoT
>>> devices. This has been discussed many times before.
>> 
>> If those devices aren’t updated any more, it’s equally possible that they’ll never get an NTPv5 compatible client, either.
> 
> And if these clients are part of a huge network, you have to provide a
> one server that talks NTPv5 for the cool clients, and another server
> that provides NTPv4 for existing IoT and embedded devices?


Yup.  Just like I remember running “nameserver” (IEN-116) protocol for some IPv4 hosts that didn’t understand DNS, and Bind for others that did… even though both provided name-to-address mapping.  Of course that was 35 years ago…

I also remember running proxy-ARP for hosts that didn’t understand classless subnetting (RFC-1519), etc.



> 
>> That would necessitate an “update” of sorts, which we’ve both agreed isn’t going to happen.
> 
> Or you would have to provide (and maintain) an NTP server implementation
> that supports both v4 and v5, depending on the version of the request.


Yeah… except that I want to shed legacy encumbrances… Like leap-seconds, which really have nothing to do with clock synchronization.

-Philip


> Martin