On 1/20/2012 10:13 AM, Michael Richardson wrote:
"Phillip" == Phillip Hallam-Baker <hallam(_at_)gmail(_dot_)com> writes:
Phillip> If we are ever going to get a handle on Internet time we
Phillip> need to get rid of the arbitrary correction factors
Phillip> introduced by leap seconds.
Phillip> The problems caused by leap seconds are that they make it
Phillip> impossible for two machines to know if they are referring
Phillip> to the same point in future time and quite often introduce
Phillip> errors in the present.
BULL. Sorry Phillip - but this is ONLY about the need to create
something that is stronger than the word of the systems administrator.
The issue is that NTP is broken. Both in its design and its use
The architecture of the time-sychronization process was specifically
designed to not produce evidence. What is produces is uncorrelated time
Can you tell me which protocols use future timestamps in an moving form
(not stored at rest in a certificate in a DANE RR, for instance), which
care about discrepancies of less than 1 minute?
I'm asking for information.
Power use tokens, any number of FIX type events which create timestamps
representing financial information. Any number of others too.
Todd S. Glassey
This is from my personal email account and any materials from this
account come with personal disclaimers.
Further I OPT OUT of any and all commercial emailings.
Ietf mailing list