In message <E1F96Bn-00063T-00_at_mta1.cl.cam.ac.uk>, Markus Kuhn writes:
>Rob Seaman wrote on 2006-02-06 17:37 UTC:
>> 2) NTP can convey TAI as simply as UTC.
>> 3) Deploy a small network of NTP servers to keep TAI, not UTC.
>> 4) NTP client machines could therefore trivially select between TAI
>> and UTC by subscribing to different servers.
>
>NTP Version 3 as defined in RFC 1305 is clearly a protocol for
>diseminating UTC. This specification has no provisions for disseminating
>anything other than UTC (see Appendix E).
>
>You can, of course, define, publish, implement, and promote a new
>version (4?) of NTP that can also diseminate TAI, EOPs, leap-second
>tables, and other good things. I'm all for it.
There is already an effort to revise the NTP docs and I belive
the result is tentatively called NTPv4. There is some support
for distributing UTC-TAI in there.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
Received on Tue Feb 14 2006 - 15:59:23 PST