Danny,

This is the first I have seen the document, but my name is on it, so I should respond.

The document from which this is derived is twenty years old, although it has been updated for recent developments. However, the system per and clock status words do not align with those defined in the current ntpq and status/event codes defined in the current reference implementation documenttation. I suggest the description of the status words in the ID be changed to agree with the documentaiton or the documentatino and implementation be changed to agree with the ID.

The intent in the event codes is to align them with the protostats statistics file messages. These are define din the header files. While these change from time to time, some kind of reference should be made to the current list. I don't think this should be the IANA, so maybe the reference should be to the current documentation.

Dave

Danny Mayer wrote:

On 12/25/2011 6:35 PM, Karen O'Donoghue wrote:
Hi Danny. I think there was a glitch in the draft announcement because I
didn't specify it for the ntp working group in the draft submission
process. The document should move to a working group instead of being an
individual submission, but we haven't done that yet.

The draft is:
https://datatracker.ietf.org/doc/draft-odonoghue-ntpv4-control/

I really just tried to get the ball rolling on this. Dave Hart and
Harlen Stenn are working to update the content. Comments are definitely
welcome.

If you want people to vote to adopt the document into the WG then you
get a +1 from me.

Danny
Karen

On 12/25/11 4:12 PM, Danny Mayer wrote:
Hi Karen,

Reading over the minutes of the taipei meeting I saw references to this
document but I never saw a draft announcement. Is this published so that
it can be reviewed?

Thanks,
Danny

_______________________________________________
ntpwg mailing list
[email protected]
http://lists.ntp.org/listinfo/ntpwg

_______________________________________________
TICTOC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tictoc

Reply via email to