So they want to in-invent NTP? I think NTP already services way more than 6.5 billion per day. The problem with NTP is while it is nearly optimal and provides the best time accuracy for a given hardware/network setup it is not technically "traceable" even if the time really is from NIST indirectly.
I think you could fix this traceability problem with some rules about how to write the configuration files, no new software. For example NTP already handles cryptographic authentication. Make the use of this monitory so that then you know you are talking to a NIST referenced server. On Tue, Mar 18, 2014 at 10:18 PM, Tom Van Baak <t...@leapsecond.com> wrote: > If you can design a system that can handle 6.5 billion requests per day, this > opportunity is for you... > > > https://www.fbo.gov/spg/DOC/NIST/AcAsD/RFI_InternetTimeServiceComments/listing.html > > Solicitation Number: RFI_InternetTimeServiceComments > > Synopsis: > Added: Mar 18, 2014 9:46 am > > SUMMARY: National Institute of Standards and Technology (NIST), Department of > Commerce, seeks information from the public on NIST's potential transition of > time services from a NIST-only service to private sector operation of an > ensemble of time servers that will provide NIST-traceable time information in > a number of different formats over the public Internet. > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. -- Chris Albertson Redondo Beach, California _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.