Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-26 Thread David Woolley
E-Mail Sent to this address will be added to the BlackLists wrote: unruh wrote: If in the future, MTC is defined (Mars Time Coordinate) ntp will work equally well there without UTC. Nor should a new RFC be needed simply to have ntp defined with MTC. I could see some issues if e.g. the length o

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-26 Thread E-Mail Sent to this address will be added to the BlackLists
unruh wrote: > If in the future, MTC is defined (Mars Time Coordinate) ntp will > work equally well there without UTC. Nor should a new RFC be needed > simply to have ntp defined with MTC. I could see some issues if e.g. the length of years, days, were different?

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-26 Thread unruh
On 2010-06-25, Richard B. Gilbert wrote: > pc wrote: >> At risk of stirring up a hornets' nest: >> >> The RFC unequivocally states that "A primary server is >> synchronized to a reference clock directly traceable to >> UTC." >> >> IMO, that is not a necessary condition. If I have a >> hierarchy

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-24 Thread Richard B. Gilbert
pc wrote: At risk of stirring up a hornets' nest: The RFC unequivocally states that "A primary server is synchronized to a reference clock directly traceable to UTC." IMO, that is not a necessary condition. If I have a hierarchy of NTP servers and clients with no external connection to the Inte

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-24 Thread Chuck Swiger
Hi-- On Jun 24, 2010, at 6:45 AM, pc wrote: > The RFC unequivocally states that "A primary server is synchronized to a > reference clock directly traceable to UTC." > > IMO, that is not a necessary condition. If I have a hierarchy of NTP servers > and clients with no external connection to the

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-24 Thread David L. Mills
pc, You completely miss the point. By definition a primary server is synchronized to UTC via an external source such as a GPS receiver. By definition, it operates at stratum 1. It is indeed possible to operate a server with some other reference source, even itself (orphan mode or local clock

Re: [ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-24 Thread pc
At risk of stirring up a hornets' nest: The RFC unequivocally states that "A primary server is synchronized to a reference clock directly traceable to UTC." IMO, that is not a necessary condition. If I have a hierarchy of NTP servers and clients with no external connection to the Internet and I f

[ntp:questions] Fwd: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification

2010-06-21 Thread Danny Mayer
Original Message Subject: [ntpwg] RFC 5905 on Network Time Protocol Version 4: Protocol and Algorithms Specification Date: Mon, 21 Jun 2010 15:56:06 -0700 (PDT) From: rfc-edi...@rfc-editor.org To: ietf-annou...@ietf.org, rfc-d...@rfc-editor.org CC: nt...@lists.ntp.org, rfc-e