--- 1/draft-ietf-ntp-ntpv4-mib-04.txt 2008-08-29 09:12:13.000000000 +0200 +++ 2/draft-ietf-ntp-ntpv4-mib-05.txt 2008-08-29 09:12:13.000000000 +0200 @@ -1,20 +1,20 @@ NTP H. Gerstung Internet-Draft Meinberg -Expires: August 28, 2008 C. Elliott +Expires: March 1, 2009 C. Elliott Cisco - February 25, 2008 + August 28, 2008 Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) - draft-ietf-ntp-ntpv4-mib-04 + draft-ietf-ntp-ntpv4-mib-05 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -25,25 +25,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on August 28, 2008. - -Copyright Notice - - Copyright (C) The IETF Trust (2008). + This Internet-Draft will expire on March 1, 2009. Abstract The Network Time Protocol (NTP) is used in networks of all types and sizes for time synchronization of servers, workstations and other networked equipment. As time synchronization is more and more a mission critical service, standardized means for monitoring and management of this subsystem of a networked host are required to allow operators of such a service to setup a monitoring system that is platform- and vendor-independant. This Internet draft provides a @@ -62,29 +58,29 @@ 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.1. Normative References . . . . . . . . . . . . . . . . . . . 26 7.2. Informative References . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 Intellectual Property and Copyright Statements . . . . . . . . . . 27 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of - RFC3410 [4]. + RFC3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in RFC2578 - [1], RFC2579 [2] and RFC2580 [3]. + [RFC2578], RFC2579 [RFC2579] and RFC2580 [RFC2580]. 2. Introduction The NTPv4 MIB Module is designed to allow SNMP to be used to monitor and manage local NTP entities. It provides a collection of data objects that can be queried using the SNMP protocol and represent the current status of the NTP entity. This includes general information about the NTP entity itself (vendor, product, version) as well as connectivity to upstream NTP servers used as sources of reference time and to hardware reference clocks like radio clocks. The most @@ -130,43 +126,47 @@ most important ones ("core events") and additionally provides a heartbeat notification as well as a test notification to allow management systems to test the reception of NTP related notifications as well as enable heartbeat-based monitoring systems to assure that the NTP entity is still up and running. 4. MIB Definition -- ********************************************************************* -- ---$Id: draft-ietf-ntp-ntpv4-mib-04.xml 1.12 2007/11/28 00:00:00Z chelliot $ +--$Id: draft-ietf-ntp-ntpv4-mib-05.xml 1.12 2007/11/28 00:00:00Z chelliot $ --$Name: SUBMIT_1 $ -- -- The Network Time Protocol Version 4 -- Management Information Base (MIB) -- -- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de) -- Chris Elliott (chelliot@cisco.com) -- -- for the Internet Engineering Task Force (IETF) -- NTP Working Group (ntpwg) -- -- -- ********************************************************************* -- --- $Log: draft-ietf-ntp-ntpv4-mib-04.xml $ +-- $Log: draft-ietf-ntp-ntpv4-mib-05.xml $ +-- Revision 1.14 2008/08/29 00:00:00Z heiko +-- Re-submitted after expiration: +-- - The working group agreed to forward this draft in its current form (04), +-- but it expired before that could be done -- Revision 1.13 2008/02/25 00:00:00Z chelliot -- MIB: + -- - Added statistics table on a per-packet mode basis -- (ntpEntStatPktModeTable) -- Revision 1.12 2007/11/28 00:00:00Z chelliot -- MIB: - -- - Added protocol statistics at the entity and association level -- XML/RFC: -- - Changed a couple of instances of "instance" to "entity" and "srv" -- to "ent". -- - Changed Meinberg address and Heiko's phone number. -- Revision 1.11 2007/07/23 00:00:00Z chelliot -- MIB: -- - Modified Contact Info -- - Added Stratum and NTP time TCs -- - Changed ntpEntNotifNotInSync to ntpEntNotifCurrentMode and @@ -1160,36 +1159,37 @@ objects control notifications. The security provided by the implementation of the SNMP agent providing the data objects in this MIB will be sufficient, although it is recommended that a security level of at least SNMPv3 AuthNoPriv be used. The general access management methods used for SNMP agents apply. 7. References 7.1. Normative References - [1] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, - Ed., "Structure of Management Information Version 2 (SMIv2)", - STD 58, RFC 2578, April 1999. + [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. + Schoenwaelder, Ed., "Structure of Management Information + Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. - [2] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, - Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, - April 1999. + [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. + Schoenwaelder, Ed., "Textual Conventions for SMIv2", + STD 58, RFC 2579, April 1999. - [3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance - Statements for SMIv2", STD 58, RFC 2580, April 1999. + [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, + "Conformance Statements for SMIv2", STD 58, RFC 2580, + April 1999. 7.2. Informative References - [4] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction - and Applicability Statements for Internet-Standard Management - Framework", RFC 3410, December 2002. + [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, + "Introduction and Applicability Statements for Internet- + Standard Management Framework", RFC 3410, December 2002. Authors' Addresses Heiko Gerstung Meinberg Funkuhren Gmbh & Co. KG Lange Wand 9 Bad Pyrmont 31812 Germany Phone: +49 5281 9309 25 @@ -1236,15 +1236,10 @@ attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. - -Acknowledgment - - Funding for the RFC Editor function is provided by the IETF - Administrative Support Activity (IASA).