Any "standard" name for ISP time services?
I'm currently composing a note to a software house, which is asking for permission to list some of our NTP servers in their software's config files. Before I do that, is there any "standard" for ISP's for naming their hosts that provide time service on ports 13, 37, or 123? Even if it's a list of "AOL users should try 'time.aol.com' first" rules, that might be an improvement.... -- Valdis Kletnieks Operating Systems Analyst Virginia Tech
On 11/16/00, Valdis.Kletnieks@vt.edu wrote:
I'm currently composing a note to a software house, which is asking for permission to list some of our NTP servers in their software's config files. Before I do that, is there any "standard" for ISP's for naming their hosts that provide time service on ports 13, 37, or 123? Even if it's a list of "AOL users should try 'time.aol.com' first" rules, that might be an improvement....
Many of them are named "time" or "clock," but then there's historical sites like clepsydra.... -- J.D. Falk "Laughter is the sound Product Manager that knowledge makes when it's born." Mail Abuse Prevention System LLC -- The Cluetrain Manifesto
At 15:05 16/11/00, Valdis.Kletnieks@vt.edu wrote:
I'm currently composing a note to a software house, which is asking for permission to list some of our NTP servers in their software's config files. Before I do that, is there any "standard" for ISP's for naming their hosts that provide time service on ports 13, 37, or 123?
I have seen two conventions pretty widely used. I prefer (1) for style reasons, but (2) seems equally sensible. 1) clock.<domain> Examples: clock.home.net clock.nrl.navy.mil clock.umd.edu clock.cmc.ec.qc.ca clock.uregina.ca clock.cuhk.edu.hk clock.nc.fukuoka-u.ac.jp clock.isc.org clock.sgi.com clock.via.net clock.osf.org clock.llnl.gov 2) ntp.<domain> Examples: See http://www.eecis.udel.edu/~mills/ntp/clock1.htm Ran rja@extremenetworks.com
On Thu, 16 Nov 2000 16:07:28 EST, Ran Atkinson said:
Examples: See http://www.eecis.udel.edu/~mills/ntp/clock1.htm
Umm.. Ran? That's how I got *INTO* this mess in the first place - I had a host listed in there, it got put into some PC shareware's config files, that got on tucows, and now I'm still seeing 30-40 packets per second on that hostname a *year* after it was removed from that file. So now when another software author is trying to Do The Right Thing, I'm being just a *tad* more cautious. ;) -- Valdis Kletnieks Operating Systems Analyst Virginia Tech
Thus spake <Valdis.Kletnieks@vt.edu>
I'm currently composing a note to a software house, which is asking for permission to list some of our NTP servers in their software's config files. Before I do that, is there any "standard" for ISP's for naming their hosts that provide time service on ports 13, 37, or 123? Even if it's a list of "AOL users should try 'time.aol.com' first" rules, that might be an improvement....
It used to be that "tick" and "tock" were the common aliases for a pair of Stratum 2 NTP servers. "truechimer" was the recommended alias for a Stratum 1 NTP server. In recent years, people seem to have moved to "ntp1", "ntp2", etc. in the same way they use "ns1", "ns2", etc. for DNS servers. I personally dislike the latter trend and prefer the more colorful names. S | | Stephen Sprunk, K5SSS, CCIE #3723 :|: :|: Network Design Consultant, GSOLE :|||: :|||: New office: RCDN2 in Richardson, TX .:|||||||:..:|||||||:. Email: ssprunk@cisco.com
participants (4)
-
J.D. Falk -
Ran Atkinson -
Stephen Sprunk -
Valdis.Kletnieks＠vt.edu