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

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/