Hi Not to mention the issues with hardware time stamping over large scale / multi vendor networks. As soon as you cross your property line, things start to get messy….
Bob On Oct 27, 2012, at 4:37 PM, Magnus Danielson <mag...@rubidium.dyndns.org> wrote: > On 10/27/2012 09:06 PM, Sarah White wrote: >> Sorry to post such a long thing on the subject. Most of the work I do >> with accurate time involves network synchronization. >> >> Really, the NTP / SNTP protocol isn't nearly as high performance as >> "Precision time protocol" --- PTP is the latest technology to come out >> of the "network time foundation", and NTP protocol has simply been >> around longer and as such, it is better known: >> >> http://networktimefoundation.org/projects/ > > The reason for this thread was not to necessarily get the best possible time, > but to get away from severely affected time that was causing the dataloss > issues. > > The one flaw that NTP has that motivated PTP was lack of hardware > time-stamps. There are those that have implemented hardware time-stamping to > NTP. > > It's unfortunate to compare NTP and PTP when it should be comparing software > time-stamping and hardware time-stamping. > > Cheers, > Magnus > > _______________________________________________ > 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. _______________________________________________ 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.
