On 4/24/06, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote:
>
> I can't imagine that the ISPs would want their routers to be popular
> public NTP servers too.
>
> On the other hand, any old single-CPU box with a minimum of memory
> will work fine as a public NTP server.
>
> That being said -- I don't think anyone has approached the ISPs. If
> you have contacts at your ISP, please tell them about the NTP Pool.
>
> Eventually it'd be cool to be able to have the pool direct users to
> their local ISPs NTP server (but it doesn't make sense until many
> ISPs have their NTP servers in the pool).
That would make it sort of a chicken-and-egg problem, I suppose. An
ISP may not want to serve NTP to the rest of the Internet, but they
would probably want to serve it to their own customers. The problem is
really one of advertising server names and getting users to configure
their machines to talk to the right time servers. This is where the
pool could help, I think, if it becomes an increasingly popular
"default" setting in devices and operating systems and "location
aware" DNS is made to work.
Qwest doesn't really advertise their NTP servers to their customers
for whatever reason... I "guessed" the name of tick.qwest.net for
example, after I could find no mention of NTP servers on Qwest's site.
In any case, I will discuss NTP and the pool project during my next
call with Qwest engineers.
--
RPM
=========================
All problems can be solved by diplomacy, but violence and treachery
are equally effective, and more fun.
-Anonymous
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
