Chuck, the problem is that the PC / Router / etc clock could achieve the
same accuracy even with a stratum 1 reference.. Also, I believe that there
is a issue about latency as well.... Sort of if I said "NOW", do I mean
"NOW" when I said it or do I mean "NOW" when you hear it.. :-)) . I believe
that's the problem Howard was talking about below....

Jason




""Chuck Larrieu""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> ""Howard C. Berkowitz""  wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> > In the ongoing IETF BMWG work on routing convergence, we are hoping
> > that NTP will be good enough to track protocol behavior, but some of
> > the more statistically-minded researchers are worried that it will
> > not. I'm hoping that most of our basic measurements can be done using
> > NTP-synchronized routers as the source and sink of data, but other
> > workers are pressing for GPS or other, more accurate time
> > synchronization.
>
> I thought the NTP stratum 1 reference clocks were about as accurate as one
> can get.
>
> Off topic a bit, but one of my installed utilities is an SNTP client that
> can use any public time source as a reference clock. I'm using NIST, NASA,
> or the USNO depending. Aren't these sources based on the atomic clocks
that
> claim accuracy of 1 millisecond per century or so?
>
> http://www.arachnoid.com/abouttime/index.html
> ( several interesting free things here)
>
> free - subject to the terms of the license agreement
> http://www.arachnoid.com/careware/index.html
> ( something at least one person on this list needs to take to heart )




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=30641&t=30560
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to