[ntp:questions] NTPv4 Peer Event Codes - secret decoder ring sought

Joseph Gwinn joegwinn at comcast.net
Fri Mar 19 22:04:12 UTC 2010


In article <aef914f9-d87c-4311-85e6-e835ff7e5cdd at k6g2000prg.googlegroups.com>,
 Dave Hart <davehart at gmail.com> wrote:

> On Mar 19, 20:47 UTC, Joseph Gwinn <joegwinn at comcast.net> wrote:
> > Dave,
> >
> > First the question:  The Code field of the Peer Status Word is 4 bits wide, and
> > yet codes are defined for values from 1 to 10 hex (decimal 16), which doesn't
> > quite map.  How does the code value fit into the field?  Wraparound, so 10 
> > (TAI) becomes zero?
> 
> Looking at the ntp-dev code, there are only two references to
> PEVNT_TAI:
> 
> #define	PEVNT_TAI	(16 | PEER_EVENT) /* TAI */
> 	{ PEVNT_TAI & ~PEER_EVENT,	"TAI" },
> 
> So your point is well taken, the value doesn't fit in the peer status
> word, but in fact it is defined but not used as far as I can see,
> arguing for its removal.  Dr. Mills may be able to shed more light.

He said offline that this TAI event doesn't exist, that it was a typo.

Joe Gwinn




More information about the questions mailing list