Resumen de It's about time...
After 25 years of development [41], the Network Time Protocol (NTP) is now firmly established as the standard cross-platform way to set and maintain computer clocks on the Internet. Most modern OSes ship out -of-the-box with clients for NTP, and manuy of those are tunrned on by default. Most networks devices nave NTP clients built-in, and even many Small Office/Home Office (SoHo) DSL/cable modems/routers have them turned on by default. Unfortunately, as adoption spreads, misconfiguration is becoming more commonm, espicially vendor misconfiguration. With misconfiguration comes bad or no clokck syncronization and abuse or even "Vandalism" of a surprisingly small number of time servers on the Internet.
The purpose of this article is to give you an update on the status of the protocol itself, the NTP Public Services Project (Where you can get support for questions you may have regarding NTP), books and documentation related to NTP, the Top Five Most Common Problems, listsof publicly accessible time servers (including the NTPServer Pool project), time syncronization "State of practice" on the Internet, the release of updated "Reference Implementation"code, and recent development s on NTP server abuse (following David Malone's article from the April 2006 issue of ;login:): Footnotes used will be in the asr (alt.sydamin.recovery) tradition[32, 33].
