NTP WG Meeting Minutes 1300-1500, 19 March 2007 Karen O'Donoghue, co-chair of the NTP WG, called the meeting to order. Dave Marlow volunteered to take minutes, and Jim Martin agreed to act as jabber scribe. Karen addressed basic administrative issues including blue sheets and agenda bashing. * NTPv4 Protocol Specification (Karen O’Donoghue) Slides: NTP WG Agenda and NTPv4 draft discussion (ntp-0.pdf) NTPv4 Specification: Currently available at: www.eecis.udel.edu/~mills/ntp4.txt Dave Mills has provided a rewrite of the NTP4 protocol 04-draft. This addresses a number of issues including: * Expanded abstract * SNTP overview * Server discovery overview * Expanded clarification of IPv6 changes to the NTPv4 header format. * Numerous editorial changes and clarifications The issues that still remain to be worked are: * Clarification of the draft's normative and informative material. * Approach to handle Autokey material. * Voiced consensus from the community. Mark Townsley, the Working Group's AD, challenged the WG to finish the NTPv4 Protocol document. Jim Martin, one of the NTPv4 Protocol document editors was asked to complete the work on the protocol and send in the 05-draft with all issues addressed to the ID list by the end of the week. Mark asked for at least five volunteers to read the document and post their comments to the Working Group list within the first two weeks of the release of the 05-draft. Eight participants volunteered including: * Malcolm Airst * Stewart Bryant * Steve Chen * Greg Dowd * Chris Elliott * Heiko Gerstung * Laurent Montini * Yaakov Stein The document will be issued as a Working Group Last Call. Mark promised to continue the effort and get the resulting draft to IETF Last Call as soon as possible, Pat Cain, the Working Group's Security advisor, is ready to assist as well. * NTPv4 MIB - Chris Elliott Slides: NTPv4 MIB Status  1(ntp-.pdf) MIB Draft: draft-ietf-ntp-ntpv4-mib-01 Chris discussed the NTPv4 MIB 01-draft that was released just prior to the meeting. The updated draft provides: * Clarifications to indicate that the MIB is not limited to use by servers. - Clients can also use the MIB. * Added the ntpSrvControl group and moved into it: – ntpSrvHeartbeatInterval - ntpSrvNotifBits * Added ntpSrvStatusTime to some notifications. * Modified ntpSrvStatusTime: - Previously Was a Counter64 object, now a 0 or 16 byte string containing the NTP 128-bit date format. - Counter64 definition left in, but commented out, to show the complexity of defining the supporting objects. Chris went over the issues which needed further work: * Need to modify ORGANIZATION and CONTACT-INFO - CONTACT-INFO still needs correct information * ntpAssocIndex and ntpAssocID need better descriptions. * Consider instrumenting a leap second object. * Consider notification for leap seconds. * Consider whether ntpSrvTimeDistance should be in the info group or status. * Consider whether ntpSrvStatusTime should be 64-bit date format. - Dropping the top 32 bits of era and bottom 32 bits of precision. * Consider defining TCs for types that might be useful elsewhere. * Consider notification for when synched. - Currently there is notification for when not in synch. * Reduce conformance/compliance requirements for NTP and SNTP clients. In addition, based on discussions at the meeting, an update is needed to the security section of the NTPv4 MIB 01-draft which states that all objects are read-only since there are now two read-write objects. Chris indicated that resolutions to the current issues would be resolved soon and that the 02-draft of the MIB would be posted soon. Karen expressed the need for people to post to the Working Group list with any issues and also to express support with 02-draft if it is sufficient. After a final discussion on the schedule for getting these two documents to WG Last Call, the meeting was adjourned.