idnits 2.17.1 draft-ietf-ntp-ntpv4-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1220. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1231. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1238. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1244. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 4 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 25, 2008) is 5905 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NTP H. Gerstung 3 Internet-Draft Meinberg 4 Expires: August 28, 2008 C. Elliott 5 Cisco 6 February 25, 2008 8 Definitions of Managed Objects for Network Time Protocol Version 4 9 (NTPv4) 10 draft-ietf-ntp-ntpv4-mib-04 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on August 28, 2008. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2008). 41 Abstract 43 The Network Time Protocol (NTP) is used in networks of all types and 44 sizes for time synchronization of servers, workstations and other 45 networked equipment. As time synchronization is more and more a 46 mission critical service, standardized means for monitoring and 47 management of this subsystem of a networked host are required to 48 allow operators of such a service to setup a monitoring system that 49 is platform- and vendor-independant. This Internet draft provides a 50 standardized collection of data objects for monitoring the NTP entity 51 of such a network participant and it is part of the NTP Version 4 52 standardization effort. 54 Table of Contents 56 1. The Internet-Standard Management Framework . . . . . . . . . . 3 57 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Technical Description . . . . . . . . . . . . . . . . . . . . 3 59 4. MIB Definition . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 25 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 26 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 26 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 66 Intellectual Property and Copyright Statements . . . . . . . . . . 27 68 1. The Internet-Standard Management Framework 70 For a detailed overview of the documents that describe the current 71 Internet-Standard Management Framework, please refer to section 7 of 72 RFC3410 [4]. 74 Managed objects are accessed via a virtual information store, termed 75 the Management Information Base or MIB. MIB objects are generally 76 accessed through the Simple Network Management Protocol (SNMP). 77 Objects in the MIB are defined using the mechanisms defined in the 78 Structure of Management Information (SMI). This memo specifies a MIB 79 module that is compliant to the SMIv2, which is described in RFC2578 80 [1], RFC2579 [2] and RFC2580 [3]. 82 2. Introduction 84 The NTPv4 MIB Module is designed to allow SNMP to be used to monitor 85 and manage local NTP entities. It provides a collection of data 86 objects that can be queried using the SNMP protocol and represent the 87 current status of the NTP entity. This includes general information 88 about the NTP entity itself (vendor, product, version) as well as 89 connectivity to upstream NTP servers used as sources of reference 90 time and to hardware reference clocks like radio clocks. The most 91 important values are included in order to be able to detect failures 92 before they can have an impact on the overall time synchronization 93 status of the network. There are also a collection of notification 94 objects to inform about state changes in the NTP entity. There are 95 objects to control these notifications as well. 97 3. Technical Description 99 The NTPv4 MIB Module is divided into sections for general server 100 information, current NTP entity status, status information of all 101 mobilized associations (e.g. unicast upstream time servers, multicast 102 or broadcast time references and hardware clocks), NTP entity control 103 objects, NTP objects used only for notifications, as well as SNMP 104 notification definitions for core events. 106 The general server information section contains static information 107 and can be queried to identify which NTP implementation is running on 108 a host. This includes the vendor and product name of the running NTP 109 software as well as version information, hardware/os platform 110 identity and the time resolution of the underlying OS. 112 Section 2 (current NTP status) includes data objects that represent 113 the current operational status of the NTP entity. 115 The third section contains data objects that represent the set of 116 time references ("associations") the NTP entity is currently working 117 with. 119 The fourth section contains objects that can be used to control the 120 NTP entity. The currently defined objects control how often the 121 heartbeat interval notification is sent out and which notifications 122 are enabled. 124 The fifth section contains objects that are only used as varbinds in 125 notifications. There is currently only one object in this section--a 126 message that adds a clear text event message to notifications. 128 Certain important events can occur while the NTP entity is running. 129 The sixth section defines SNMP notifications for a collection of the 130 most important ones ("core events") and additionally provides a 131 heartbeat notification as well as a test notification to allow 132 management systems to test the reception of NTP related notifications 133 as well as enable heartbeat-based monitoring systems to assure that 134 the NTP entity is still up and running. 136 4. MIB Definition 138 -- ********************************************************************* 139 -- 140 --$Id: draft-ietf-ntp-ntpv4-mib-04.xml 1.12 2007/11/28 00:00:00Z chelliot $ 141 --$Name: SUBMIT_1 $ 142 -- 143 -- The Network Time Protocol Version 4 144 -- Management Information Base (MIB) 145 -- 146 -- Authors: Heiko Gerstung (heiko.gerstung@meinberg.de) 147 -- Chris Elliott (chelliot@cisco.com) 148 -- 149 -- for the Internet Engineering Task Force (IETF) 150 -- NTP Working Group (ntpwg) 151 -- 152 -- 153 -- ********************************************************************* 154 -- 155 -- $Log: draft-ietf-ntp-ntpv4-mib-04.xml $ 156 -- Revision 1.13 2008/02/25 00:00:00Z chelliot 157 -- MIB: 158 -- - Added statistics table on a per-packet mode basis 159 -- (ntpEntStatPktModeTable) 160 -- Revision 1.12 2007/11/28 00:00:00Z chelliot 161 -- MIB: 163 -- - Added protocol statistics at the entity and association level 164 -- XML/RFC: 165 -- - Changed a couple of instances of "instance" to "entity" and "srv" 166 -- to "ent". 167 -- - Changed Meinberg address and Heiko's phone number. 168 -- Revision 1.11 2007/07/23 00:00:00Z chelliot 169 -- MIB: 170 -- - Modified Contact Info 171 -- - Added Stratum and NTP time TCs 172 -- - Changed ntpEntNotifNotInSync to ntpEntNotifCurrentMode and 173 -- deleted ntpEntNotifEntityStarted and ntpEntNotifEntityStopped 174 -- - Added compliance for SNTP entities 175 -- - Changed ntpTime to ntpDateTime 176 -- Revision 1.10 2007/07/09 00:00:00Z chelliot 177 -- XML/RFC: 178 -- - Changed RFC to Internet 179 -- - Changed service and service instance* to entity/entities 180 -- - Revised the Security Considerations to include read-write object 181 -- security considerations 182 -- - Added Chris Elliott as an author 183 -- - Fixed several lines to be 72 characters long or less 184 -- MIB: 185 -- - Changed "service" and "service instance" to "entity", 186 -- and Srv to Ent 187 -- - Changed status to mode 188 -- - Added association status object 189 -- - Added leap second objects 190 -- Revision 1.9 2007/03/04 06:59:44Z chelliot 191 -- MIB: 192 -- - Added time objects, comments, changed notifications 193 -- - Changed server to service 194 -- Revision 1.8 2006/10/23 03:37:44Z chelliot 195 -- MIB: 196 -- - Changed various object types, added notification control object 197 -- Revision 1.7 2006/06/16 07:13:50Z heiko 198 -- XML/RFC: 199 -- - Added/changed comments about the to-be-done IANA SMI assignment 200 -- Revision 1.6 2006/06/16 07:04:43Z heiko 201 -- RFC/XML: 202 -- - phone number corrected 203 -- - removed unused references 204 -- MIB: 205 -- - added ntpSrvTimePrecision 206 -- - changed INTEGER objects to Integer32 207 -- - changed default value for ntpSrvStatusStratum from 99 to 16 208 -- - changed default value for ntpSrvStatusActiveRefclockId from 99-0 209 -- - changed object names to ntpSrvStatusActiveRefSourceName 210 -- (from ntpSrvStatusActiveRefclockName) and to 211 -- ntpSrvStatusNumberOfRefSources (from 212 -- ntpSrvStatusNumberOfRefclocks) 213 -- - removed ntpSrvStatusAuthKeyId object 214 -- - added ntpSrvStatusDispersion to provide the current root 215 -- dispersion 216 -- - major rework of section 3 (Status of associations) to compile 217 -- cleanly,including: 218 -- - added dispersion to the association dataset 219 -- - renaming of objects 220 -- - added an index to the association table 221 -- - formal changes 222 -- - traps are now reverse mappable 223 -- - traps are now define with payload where applicable 224 -- - added compliance statements 225 -- Revision 1.5 2006/02/27 08:28:16Z heiko 226 -- - changed to RFC format and added header as well as 227 -- introduction and technical description 228 -- - added other necessary RFC components (copyright statement etc.) 229 -- Revision 1.4 2006/02/27 07:06:49Z heiko 230 -- - removed all objects with data type REAL 231 -- - everything that needs to be floating point is now defined as 232 -- DisplayString 233 -- Revision 1.2 2006/01/23 08:58:11Z heiko 234 -- - changed the datatype of offset, jitter and delay objects from 235 -- Integer32 to REAL 236 -- 237 -- ********************************************************************* 239 NTPv4-MIB DEFINITIONS ::= BEGIN 241 IMPORTS 242 MODULE-IDENTITY, OBJECT-TYPE , mib-2, Integer32, NOTIFICATION-TYPE, 243 Unsigned32, Counter32 244 FROM SNMPv2-SMI 245 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 246 FROM SNMPv2-CONF 247 DisplayString, TEXTUAL-CONVENTION 248 FROM SNMPv2-TC 249 InetAddressType, InetAddress 250 FROM INET-ADDRESS-MIB; 252 ntpSnmpMIB MODULE-IDENTITY 253 LAST-UPDATED "200802250000Z" -- February 25, 2008 254 ORGANIZATION "The IETF NTP Working Group (ntpwg)" 255 CONTACT-INFO 256 " WG Email: ntpwg@lists.ntp.isc.org 257 Subscribe: 259 https://lists.ntp.isc.org/mailman/listinfo/ntpwg 261 Heiko Gerstung 262 Meinberg Funkuhren Gmbh & Co. KG 263 Lange Wand 9 264 Bad Pyrmont 31812 265 Germany 267 Phone: +49 5281 9309 25 268 Email: heiko.gerstung@meinberg.de 270 Chris Elliott 271 Cisco Systems, Inc. 272 7025 Kit Creek Rd., P.O. Box 14987 273 Research Triangle Park 27709 274 USA 276 Phone: +1 919-392-2146 277 Email: chelliot@cisco.com" 278 DESCRIPTION 279 "The Management Information Base for NTP time entities." 280 REVISION "200802250000Z" 281 DESCRIPTION 282 "Added ntpEntStatPktModeTable" 283 REVISION "200711280000Z" 284 DESCRIPTION 285 "Multiple proposed changes for IETF 70" 286 REVISION "200707230000Z" 287 DESCRIPTION 288 "Multiple proposed changes for IETF 69" 289 REVISION "200707090000Z" 290 DESCRIPTION 291 "Multiple changes from IETF 68" 292 REVISION "200703040000Z" 293 DESCRIPTION 294 "More MIB review modifications." 295 REVISION "200610230000Z" 296 DESCRIPTION 297 "Modifications from MIB review." 298 REVISION "200606190000Z" 299 DESCRIPTION 300 "First Draft Version" 301 REVISION "200512190000Z" 302 DESCRIPTION 303 "revised edition (added traps and stuff)" 304 REVISION "200511160000Z" 305 DESCRIPTION 306 "Initial draft" 308 ::= { mib-2 XXXXX } 310 ntpSnmpMIBObjects OBJECT IDENTIFIER ::= { ntpSnmpMIB 1 } 312 -- MIB contains 6 groups 314 ntpEntInfo OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 1 } 315 ntpEntStatus OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 2 } 316 ntpAssociation OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 3 } 317 ntpEntControl OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 4 } 318 ntpEntNotifObjects OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 5 } 319 ntpEntNotifPrefix OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 } 321 -- 322 -- Textual Conventions 323 -- 325 NtpStratum ::= TEXTUAL-CONVENTION 326 DISPLAY-HINT "d" 327 STATUS current 328 DESCRIPTION 329 "The NTP stratum, with 16 representing no stratum." 330 SYNTAX Unsigned32 (1..16) 332 NtpDateTime ::= TEXTUAL-CONVENTION 333 DISPLAY-HINT "4d:4d:4d.4d" 334 STATUS current 335 DESCRIPTION 336 "NTP date/time on the device, in 128-bit 337 NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, 338 section 6: 339 It includes a 64-bit signed seconds field 340 spanning 584 billion years and a 64-bit fraction 341 field resolving .05 attosecond (i.e. 0.5e-18). 342 For convenience in mapping between formats, the 343 seconds field is divided into a 32-bit era field 344 and a 32-bit timestamp field. 346 If time is not syncronized this field shall be a 347 zero-length string. 349 This TC is not to be used for objects that are used 350 to set the time of the node querying this object. 351 NTP should be used for this--or at least SNTP." 352 SYNTAX OCTET STRING (SIZE (0 | 16)) 354 -- 355 -- Section 1: General NTP Entity information objects 356 -- (relatively static information) 357 -- 359 ntpEntSoftwareName OBJECT-TYPE 360 SYNTAX DisplayString 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The product name of the installed NTP version." 365 -- the product name of the running ntp implementation, e.g. "ntpd" 366 ::= { ntpEntInfo 1 } 368 ntpEntSoftwareVersion OBJECT-TYPE 369 SYNTAX DisplayString 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The software version of the installed NTP implementation." 374 -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..." 375 ::= { ntpEntInfo 2 } 377 ntpEntSoftwareVersionVal OBJECT-TYPE 378 SYNTAX Unsigned32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "Software version of installed NTP as an unsigned integer 383 value." 384 -- e.g. if version string is "4.2.0b" this could be translated into 385 -- 4202. This could be useful to find out if version of entity on a 386 -- is newer or older than version of the entity on b (without too 387 -- much string parsing trouble) 388 ::= { ntpEntInfo 3 } 390 ntpEntSoftwareVendor OBJECT-TYPE 391 SYNTAX DisplayString 392 MAX-ACCESS read-only 393 STATUS current 394 DESCRIPTION 395 "The vendor/author of the installed NTP version." 396 ::= { ntpEntInfo 4 } 398 ntpEntSystemType OBJECT-TYPE 399 SYNTAX DisplayString 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "General hardware/os platform information." 404 -- e.g. "Linux 2.6.12 / x86" 405 -- freely configurable, default is OS Version / Hardware platform 406 ::= { ntpEntInfo 5 } 408 ntpEntTimeResolution OBJECT-TYPE 409 SYNTAX DisplayString 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "A string describing the time resolution of the running NTP 414 implementation." 415 -- e.g. "100 ns" 416 -- depends on the NTP implementation and the underlying OS. The 417 -- current resolution should be used, so if the OS only supports 418 -- 10ms and ntpd is capable of 1ns, the 10ms should be advertised 419 ::= { ntpEntInfo 6 } 421 ntpEntTimeResolutionVal OBJECT-TYPE 422 SYNTAX Unsigned32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The time resolution in integer format." 427 -- ntpEntTimeResolution in Integer format 428 -- shows the resolution based on 1 second, e.g. "1ms" translates to 429 -- 1000 430 ::= { ntpEntInfo 7 } 432 ntpEntTimePrecision OBJECT-TYPE 433 SYNTAX DisplayString 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "A string describing the precision with which the NTP entity 438 implementation/OS manages its time base." 439 -- e.g. "-18" means 2^-18 = 0.000003814697265625 seconds 440 -- "-5" means 2^-5 = 0.03125 seconds 441 -- depends on the NTP implementation and the underlying OS. 442 ::= { ntpEntInfo 8 } 444 ntpEntTimePrecisionVal OBJECT-TYPE 445 SYNTAX Integer32 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The entity's precision in integer format." 450 -- ntpEntTimePrecision in signed Integer format 451 -- shows the precision. A value of -5 would mean 2^-5 = 31.25 ms 452 ::= { ntpEntInfo 9 } 454 ntpEntTimeDistance OBJECT-TYPE 455 SYNTAX DisplayString 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The distance from this NTP entity to the root time reference 460 (stratum 0) source." 461 -- including the unit 462 -- e.g. "13.243 ms" 463 ::= { ntpEntInfo 10 } 465 -- 466 -- Section 2: Current NTP status (dynamic information) 467 -- 469 ntpEntStatusCurrentMode OBJECT-TYPE 470 SYNTAX DisplayString 471 MAX-ACCESS read-only 472 STATUS current 473 DESCRIPTION 474 "The actual mode of NTP as a string" 475 --- possible strings: 476 --- "not running" : NTP is not running 477 --- "not synchronized" : NTP is not synchronized to any time source 478 --- (stratum = 16) 479 --- "none configured" : NTP is not synchronized and does not have a 480 --- server configured 481 --- (stratum = 16) 482 --- "sync to local" : NTP is synchronized to own local clock 483 --- (degraded reliability) 484 --- "sync to refclock" : NTP is synchronized to a local hardware 485 --- refclock (e.g. GPS) 486 --- "sync to remote server" : NTP is synchronized to a remote NTP 487 --- server ("upstream" server) 488 --- "unknown" : The state of NTP is unknown. 489 ::= { ntpEntStatus 1 } 491 ntpEntStatusCurrentModeVal OBJECT-TYPE 492 SYNTAX INTEGER { 493 notRunning(1), 494 notSynchronized(2), 495 noneConfigured(3), 496 syncToLocal(4), 497 syncToRefclock(5), 498 syncToRemoteServer(6), 499 unknown(99) 500 } 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The current mode of the NTP as integer value." 505 -- see ntpEntStatusCurrentMode 506 DEFVAL { 99 } 507 ::= { ntpEntStatus 2 } 509 ntpEntStatusStratum OBJECT-TYPE 510 SYNTAX NtpStratum 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The NTP entity's own stratum value." 515 -- should be stratum of syspeer + 1 (or 16 if no syspeer) 516 DEFVAL { 16 } 517 ::= { ntpEntStatus 3 } 519 ntpEntStatusActiveRefSourceId OBJECT-TYPE 520 SYNTAX Unsigned32 ( 0..99999 ) 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The association ID of the current syspeer." 525 DEFVAL { 0 } 526 ::= { ntpEntStatus 4 } 528 ntpEntStatusActiveRefSourceName OBJECT-TYPE 529 SYNTAX DisplayString 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The hostname/descriptive name of the current reference source 534 selected as syspeer." 535 -- e.g. "ntp1.ptb.de" or "GPS" or "DCFi" ... 536 -- maybe something like "RefClk(8)"="hardware clock using driver 8" 537 -- would be nice 538 ::= { ntpEntStatus 5 } 540 ntpEntStatusActiveOffset OBJECT-TYPE 541 SYNTAX DisplayString 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The Time offset to the current selected reference time source 546 as a string." 548 -- including unit, e.g. "0.032 ms" or "1.232 s" 549 ::= { ntpEntStatus 6 } 551 ntpEntStatusNumberOfRefSources OBJECT-TYPE 552 SYNTAX Unsigned32 (0..99) 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "The number of reference sources configured for NTP." 557 DEFVAL { 0 } 558 ::= { ntpEntStatus 7 } 560 ntpEntStatusDispersion OBJECT-TYPE 561 SYNTAX DisplayString 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The root dispersion of the running NTP entity." 566 -- e.g. "6.927" 567 DEFVAL { "n/a" } 568 ::= { ntpEntStatus 8 } 570 ntpEntStatusEntityUptime OBJECT-TYPE 571 SYNTAX Unsigned32 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The uptime of the NTP entity in seconds." 576 -- time since ntpd was (re-)started (not sysUptime!) 577 DEFVAL { 0 } 578 ::= { ntpEntStatus 9 } 580 ntpEntStatusDateTime OBJECT-TYPE 581 SYNTAX NtpDateTime 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The current NTP date/time on the device, in 128-bit 586 NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, 587 section 6: 588 It includes a 64-bit signed seconds field 589 spanning 584 billion years and a 64-bit fraction 590 field resolving .05 attosecond (i.e. 0.5e-18). 591 For convenience in mapping between formats, the 592 seconds field is divided into a 32-bit era field 593 and a 32-bit timestamp field. 595 If time is not syncronized this field shall be a 596 zero-length string. 598 This object can be used to timestamp events on this 599 node and allow a management station to coorelate 600 different time objects. For example, a management 601 station could query this object and sysUpTime in 602 the same operation to be able to relate sysUpTime 603 to NTP time. 605 This object is not to be used to set the time of 606 the node querying this object. NTP should be used 607 for this--or at least SNTP." 608 ::= { ntpEntStatus 10 } 610 ntpEntStatusLeapSecond OBJECT-TYPE 611 SYNTAX Integer32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Date the next known leap second will occur. If there is 616 no leap second announced then this object should be 0." 617 DEFVAL { 0 } 618 ::= { ntpEntStatus 11 } 620 ntpEntStatusLeapSecDirection OBJECT-TYPE 621 SYNTAX Integer32 (-1..1) 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "Direction of next known leap second. If there is no 626 leap second announced then this object should be 0." 627 DEFVAL { 0 } 628 ::= { ntpEntStatus 12 } 630 ntpEntStatusInPkts OBJECT-TYPE 631 SYNTAX Counter32 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "The total number of NTP messages delivered to the 636 NTP entity from the transport service." 637 ::= { ntpEntStatus 13 } 639 ntpEntStatusOutPkts OBJECT-TYPE 640 SYNTAX Counter32 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The total number of NTP messages delivered to the 645 transport service by this NTP entity." 646 ::= { ntpEntStatus 14 } 648 ntpEntStatusBadVersion OBJECT-TYPE 649 SYNTAX Counter32 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "The total number of NTP messages which were delivered 654 to this NTP entity and were for an unsupported NTP 655 version." 656 ::= { ntpEntStatus 15 } 658 ntpEntStatusProtocolError OBJECT-TYPE 659 SYNTAX Counter32 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "The total number of NTP messages which were delivered 664 to this NTP entity and this entity was not able to 665 process due to an NTP protocol error." 666 ::= { ntpEntStatus 16 } 668 ntpEntStatusNotifications OBJECT-TYPE 669 SYNTAX Counter32 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The total number of SNMP notifications which this NTP 674 entity has generated." 675 ::= { ntpEntStatus 17 } 677 ntpEntStatPktModeTable OBJECT-TYPE 678 SYNTAX SEQUENCE OF NtpEntStatPktModeEntry 679 MAX-ACCESS not-accessible 680 STATUS current 681 DESCRIPTION 682 "The number of packets sent and received by packet mode." 683 ::= { ntpEntStatus 18 } 685 ntpEntStatPktModeEntry OBJECT-TYPE 686 SYNTAX NtpEntStatPktModeEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The number of packets sent and received by packet mode." 691 INDEX { ntpEntStatPktMode } 692 ::= { ntpEntStatPktModeTable 1 } 694 NtpEntStatPktModeEntry ::= SEQUENCE { 695 ntpEntStatPktMode INTEGER, 696 ntpEntStatPktSent Counter32, 697 ntpEntStatPktReceived Counter32 698 } 700 ntpEntStatPktMode OBJECT-TYPE 701 SYNTAX INTEGER { 702 symetricactive(1), 703 symetricpassive(2), 704 client(3), 705 server(4), 706 broadcastserver(5), 707 broadcastclient(6) 708 } 709 MAX-ACCESS not-accessible 710 STATUS current 711 DESCRIPTION 712 "The NTP packet mode." 713 ::= { ntpEntStatPktModeEntry 1 } 715 ntpEntStatPktSent OBJECT-TYPE 716 SYNTAX Counter32 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The number of NTP packets sent with this packet mode." 721 ::= { ntpEntStatPktModeEntry 2 } 723 ntpEntStatPktReceived OBJECT-TYPE 724 SYNTAX Counter32 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The number of NTP packets received with this packet mode." 729 ::= { ntpEntStatPktModeEntry 3 } 731 -- 732 -- Section 3: The status of all currently mobilized associations 733 -- 735 ntpAssociationTable OBJECT-TYPE 736 SYNTAX SEQUENCE OF NtpAssociationEntry 737 MAX-ACCESS not-accessible 738 STATUS current 739 DESCRIPTION 740 "The table of currently mobilized associations." 741 ::= { ntpAssociation 1 } 743 ntpAssociationEntry OBJECT-TYPE 744 SYNTAX NtpAssociationEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "The table entry of currently mobilized associations." 749 INDEX { ntpAssocId } 750 ::= { ntpAssociationTable 1 } 752 NtpAssociationEntry ::= SEQUENCE { 753 ntpAssocId Unsigned32, 754 ntpAssocName DisplayString, 755 ntpAssocRefId DisplayString, 756 ntpAssocAddressType InetAddressType, 757 ntpAssocAddress InetAddress, 758 ntpAssocOffset DisplayString, 759 ntpAssocStratum NtpStratum, 760 ntpAssocStatusJitter DisplayString, 761 ntpAssocStatusDelay DisplayString, 762 ntpAssocStatusDispersion DisplayString 763 } 765 ntpAssocId OBJECT-TYPE 766 SYNTAX Unsigned32 ( 1..99999 ) 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "The association ID. This is an internal, unique ID." 771 ::= { ntpAssociationEntry 1 } 773 ntpAssocName OBJECT-TYPE 774 SYNTAX DisplayString 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The hostname or other descriptive name for the association." 779 ::= { ntpAssociationEntry 2 } 781 ntpAssocRefId OBJECT-TYPE 782 SYNTAX DisplayString 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "The refclock driver ID, if available." 787 -- a refclock driver ID like "127.127.1.0" for non 788 -- uni/multi/broadcast associations 789 ::= { ntpAssociationEntry 3 } 791 ntpAssocAddressType OBJECT-TYPE 792 SYNTAX InetAddressType 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The type of address of the association." 797 -- contains the type of address for uni/multi/broadcast associations 798 ::= { ntpAssociationEntry 4 } 800 ntpAssocAddress OBJECT-TYPE 801 SYNTAX InetAddress 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The IP address (IPv4 or IPv6) of the association." 806 -- contains IP address of uni/multi/broadcast associations 807 ::= { ntpAssociationEntry 5 } 809 ntpAssocOffset OBJECT-TYPE 810 SYNTAX DisplayString 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "The time offset to the association as a string." 815 -- including unit, e.g. "0.032 ms" or "1.232 s" 816 ::= { ntpAssociationEntry 6 } 818 ntpAssocStratum OBJECT-TYPE 819 SYNTAX NtpStratum 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The association stratum value." 824 ::= { ntpAssociationEntry 7 } 826 ntpAssocStatusJitter OBJECT-TYPE 827 SYNTAX DisplayString 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The jitter in miliseconds as a string." 832 ::= { ntpAssociationEntry 8 } 834 ntpAssocStatusDelay OBJECT-TYPE 835 SYNTAX DisplayString 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The network delay in miliseconds as a string." 840 ::= { ntpAssociationEntry 9 } 842 ntpAssocStatusDispersion OBJECT-TYPE 843 SYNTAX DisplayString 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The root dispersion of the association." 848 -- e.g. "6.927" 849 ::= { ntpAssociationEntry 10 } 851 ntpAssociationStatisticsTable OBJECT-TYPE 852 SYNTAX SEQUENCE OF NtpAssociationStatisticsEntry 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "The table of statistics for current associations." 857 ::= { ntpAssociation 2 } 859 ntpAssociationStatisticsEntry OBJECT-TYPE 860 SYNTAX NtpAssociationStatisticsEntry 861 MAX-ACCESS not-accessible 862 STATUS current 863 DESCRIPTION 864 "The table entry of statistics for current associations." 865 INDEX { ntpAssocId } 866 ::= { ntpAssociationStatisticsTable 1 } 868 NtpAssociationStatisticsEntry ::= SEQUENCE { 869 ntpAssocStatInPkts Counter32, 870 ntpAssocStatOutPkts Counter32, 871 ntpAssocStatProtocolError Counter32 872 } 874 ntpAssocStatInPkts OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The total number of NTP messages delivered to the 880 NTP entity from this association." 881 ::= { ntpAssociationStatisticsEntry 1 } 883 ntpAssocStatOutPkts OBJECT-TYPE 884 SYNTAX Counter32 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "The total number of NTP messages delivered to the 889 transport service by this NTP entity for this 890 association." 891 ::= { ntpAssociationStatisticsEntry 2 } 893 ntpAssocStatProtocolError OBJECT-TYPE 894 SYNTAX Counter32 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "The total number of NTP messages which were delivered 899 to this NTP entity from this association and this entity 900 was not able to process due to an NTP protocol error." 901 ::= { ntpAssociationStatisticsEntry 3 } 903 -- 904 -- Section 4: Control objects 905 -- 907 ntpEntHeartbeatInterval OBJECT-TYPE 908 SYNTAX Unsigned32 909 MAX-ACCESS read-write 910 STATUS current 911 DESCRIPTION 912 "The interval at which the ntpEntNotifHeartbeat notification 913 should be sent, in seconds. If set to 0 and the 914 entNotifHeartbeat bit in ntpEntNotifBits is 1 then 915 ntpEntNotifHeartbeat is sent once." 916 DEFVAL { 60 } 917 ::= { ntpEntControl 1 } 919 ntpEntNotifBits OBJECT-TYPE 920 SYNTAX BITS { 921 notUsed(0), -- Used to sync up bit and notification 922 -- indices 923 entNotifModeChange(1), 924 entNotifStratumChange(2), 925 entNotifSyspeerChanged(3), 926 entNotifAddAssociation(4), 927 entNotifRemoveAssociation(5), 928 entNotifConfigChanged(6), 929 entNotifLeapSecondAnnounced(7), 930 entNotifHeartbeat(8) 931 } 932 MAX-ACCESS read-write 933 STATUS current 934 DESCRIPTION 935 "A bit for each notification. A 1 for a particular bit enables 936 that particular notification, a 0 disables it." 937 ::= { ntpEntControl 2 } 939 -- 940 -- Section 5: Notification objects 941 -- 943 ntpEntNotifMessage OBJECT-TYPE 944 SYNTAX DisplayString 945 MAX-ACCESS accessible-for-notify 946 STATUS current 947 DESCRIPTION 948 "Used as a payload object for all notifications. Holds a clear 949 text event message." 950 DEFVAL { "no event" } 951 ::= { ntpEntNotifObjects 1 } 953 -- 954 -- SNMP notification definitions 955 -- 957 ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 } 959 ntpEntNotifModeChange NOTIFICATION-TYPE 960 OBJECTS { ntpEntStatusCurrentModeVal } 961 STATUS current 962 DESCRIPTION 963 "The notification to be sent when the NTP entity changes mode, 964 including starting and stopping (if possible)" 965 ::= { ntpEntNotifications 1 } 967 ntpEntNotifStratumChange NOTIFICATION-TYPE 968 OBJECTS { ntpEntStatusDateTime, ntpEntStatusStratum, 969 ntpEntNotifMessage } 970 STATUS current 971 DESCRIPTION 972 "The notification to be sent when stratum level of NTP changes." 973 ::= { ntpEntNotifications 2 } 975 ntpEntNotifSyspeerChanged NOTIFICATION-TYPE 976 OBJECTS { ntpEntStatusDateTime, ntpEntStatusActiveRefSourceId, 977 ntpEntNotifMessage } 978 STATUS current 979 DESCRIPTION 980 "The notification to be sent when a (new) syspeer has been 981 selected." 982 ::= { ntpEntNotifications 3 } 984 ntpEntNotifAddAssociation NOTIFICATION-TYPE 985 OBJECTS { ntpEntStatusDateTime, ntpAssocName, ntpEntNotifMessage } 986 STATUS current 987 DESCRIPTION 988 "The notification to be sent when a new association is 989 mobilized." 990 ::= { ntpEntNotifications 4 } 992 ntpEntNotifRemoveAssociation NOTIFICATION-TYPE 993 OBJECTS { ntpEntStatusDateTime, ntpAssocName, ntpEntNotifMessage } 994 STATUS current 995 DESCRIPTION 996 "The notification to be sent when an association is 997 demobilized." 998 ::= { ntpEntNotifications 5 } 1000 ntpEntNotifConfigChanged NOTIFICATION-TYPE 1001 OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage } 1002 STATUS current 1003 DESCRIPTION 1004 "The notification to be sent when the NTP configuration has 1005 changed." 1006 -- e.g. when the system connected to the internet and was assigned 1007 -- a new IP address by the ISPs DHCP server 1008 ::= { ntpEntNotifications 6 } 1010 ntpEntNotifLeapSecondAnnounced NOTIFICATION-TYPE 1011 OBJECTS { ntpEntStatusDateTime, ntpEntNotifMessage } 1012 STATUS current 1013 DESCRIPTION 1014 "The notification to be sent when a leap second has been 1015 announced." 1016 ::= { ntpEntNotifications 7 } 1018 ntpEntNotifHeartbeat NOTIFICATION-TYPE 1019 OBJECTS { ntpEntStatusDateTime, ntpEntStatusCurrentModeVal, 1020 ntpEntHeartbeatInterval, ntpEntNotifMessage } 1021 STATUS current 1022 DESCRIPTION 1023 "The notification to be sent periodically (as defined by 1024 ntpEntHeartbeatInterval) to indicate that the NTP entity is 1025 still alive." 1026 ::= { ntpEntNotifications 8 } 1028 -- 1029 -- Conformance/Compliance statements 1030 -- 1032 ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 } 1034 ntpEntCompliances OBJECT IDENTIFIER ::= { ntpEntConformance 1 } 1035 ntpEntGroups OBJECT IDENTIFIER ::= { ntpEntConformance 2 } 1037 ntpEntNTPCompliance MODULE-COMPLIANCE 1038 STATUS current 1039 DESCRIPTION 1040 "The compliance statement for SNMP entities which use NTP and 1041 implement the NTP MIB" 1042 MODULE -- this module 1043 MANDATORY-GROUPS { 1044 ntpEntObjectsGroup1, 1045 ntpEntObjectsGroup2, 1046 ntpEntNotifPrefixGroup 1047 } 1048 ::= { ntpEntCompliances 1 } 1050 ntpEntSNTPCompliance MODULE-COMPLIANCE 1051 STATUS current 1052 DESCRIPTION 1053 "The compliance statement for SNMP entities which use SNTP and 1054 implement the NTP MIB" 1055 MODULE -- this module 1056 MANDATORY-GROUPS { 1057 ntpEntObjectsGroup1 1058 } 1059 ::= { ntpEntCompliances 2 } 1061 ntpEntObjectsGroup1 OBJECT-GROUP 1062 OBJECTS { 1063 ntpEntSoftwareName, 1064 ntpEntSoftwareVersion, 1065 ntpEntSoftwareVersionVal, 1066 ntpEntSoftwareVendor, 1067 ntpEntSystemType, 1068 ntpEntStatusEntityUptime, 1069 ntpEntStatusDateTime, 1070 ntpAssocName, 1071 ntpAssocRefId, 1072 ntpAssocAddressType, 1073 ntpAssocAddress 1074 } 1075 STATUS current 1076 DESCRIPTION 1077 "A collection of objects for the NTP MIB that all NTP 1078 or SNTP entities should implement." 1079 ::= { ntpEntGroups 1 } 1081 ntpEntObjectsGroup2 OBJECT-GROUP 1082 OBJECTS { 1083 ntpEntTimeResolution, 1084 ntpEntTimeResolutionVal, 1085 ntpEntTimePrecision, 1086 ntpEntTimePrecisionVal, 1087 ntpEntTimeDistance, 1088 ntpEntStatusCurrentMode, 1089 ntpEntStatusCurrentModeVal, 1090 ntpEntStatusStratum, 1091 ntpEntStatusActiveRefSourceId, 1092 ntpEntStatusActiveRefSourceName, 1093 ntpEntStatusActiveOffset, 1094 ntpEntStatusNumberOfRefSources, 1095 ntpEntStatusDispersion, 1096 ntpEntStatusLeapSecond, 1097 ntpEntStatusLeapSecDirection, 1098 ntpEntStatusInPkts, 1099 ntpEntStatusOutPkts, 1100 ntpEntStatusBadVersion, 1101 ntpEntStatusProtocolError, 1102 ntpEntStatusNotifications, 1103 ntpEntStatPktSent, 1104 ntpEntStatPktReceived, 1105 ntpAssocOffset, 1106 ntpAssocStratum, 1107 ntpAssocStatusJitter, 1108 ntpAssocStatusDelay, 1109 ntpAssocStatusDispersion, 1110 ntpAssocStatInPkts, 1111 ntpAssocStatOutPkts, 1112 ntpAssocStatProtocolError, 1113 ntpEntHeartbeatInterval, 1114 ntpEntNotifBits, 1115 ntpEntNotifMessage 1116 } 1117 STATUS current 1118 DESCRIPTION 1119 "A collection of objects for the NTP MIB that are optional 1120 for NTP or SNTP entities to implement." 1121 ::= { ntpEntGroups 2 } 1123 ntpEntNotifPrefixGroup NOTIFICATION-GROUP 1124 NOTIFICATIONS { 1125 ntpEntNotifModeChange, 1126 ntpEntNotifStratumChange, 1127 ntpEntNotifSyspeerChanged, 1128 ntpEntNotifAddAssociation, 1129 ntpEntNotifRemoveAssociation, 1130 ntpEntNotifConfigChanged, 1131 ntpEntNotifLeapSecondAnnounced, 1132 ntpEntNotifHeartbeat 1133 } 1134 STATUS current 1135 DESCRIPTION 1136 "A collection of notifications for the NTP MIB" 1137 ::= { ntpEntGroups 3 } 1139 END 1141 5. IANA Considerations 1143 The MIB module in this document uses the following IANA-assigned 1144 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1146 Descriptor OBJECT IDENTIFIER value 1147 ---------- ----------------------- 1149 ntpSnmp { mib-2 XXX } 1151 RFC Ed. : the IANA is requested to assign a value for "XXX" under the 1152 'mib-2' subtree and to record the assignment in the SMI Numbers 1153 registry. When the assignment has been made, the RFC Editor is asked 1154 to replace "XXX" (here and in the MIB module) with the assigned value 1155 and to remove this note. 1157 6. Security Considerations 1159 Most data objects in this MIB are read-only. The two read-write 1160 objects control notifications. The security provided by the 1161 implementation of the SNMP agent providing the data objects in this 1162 MIB will be sufficient, although it is recommended that a security 1163 level of at least SNMPv3 AuthNoPriv be used. The general access 1164 management methods used for SNMP agents apply. 1166 7. References 1167 7.1. Normative References 1169 [1] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, 1170 Ed., "Structure of Management Information Version 2 (SMIv2)", 1171 STD 58, RFC 2578, April 1999. 1173 [2] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, 1174 Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, 1175 April 1999. 1177 [3] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance 1178 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1180 7.2. Informative References 1182 [4] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction 1183 and Applicability Statements for Internet-Standard Management 1184 Framework", RFC 3410, December 2002. 1186 Authors' Addresses 1188 Heiko Gerstung 1189 Meinberg Funkuhren Gmbh & Co. KG 1190 Lange Wand 9 1191 Bad Pyrmont 31812 1192 Germany 1194 Phone: +49 5281 9309 25 1195 Email: heiko.gerstung@meinberg.de 1197 Chris Elliott 1198 Cisco Systems, Inc. 1199 7025 Kit Creek Rd., P.O. Box 14987 1200 Research Triangle Park 27709 1201 USA 1203 Phone: +1 919-392-2146 1204 Email: chelliot@cisco.com 1206 Full Copyright Statement 1208 Copyright (C) The IETF Trust (2008). 1210 This document is subject to the rights, licenses and restrictions 1211 contained in BCP 78, and except as set forth therein, the authors 1212 retain all their rights. 1214 This document and the information contained herein are provided on an 1215 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1216 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1217 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1218 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1219 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1220 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1222 Intellectual Property 1224 The IETF takes no position regarding the validity or scope of any 1225 Intellectual Property Rights or other rights that might be claimed to 1226 pertain to the implementation or use of the technology described in 1227 this document or the extent to which any license under such rights 1228 might or might not be available; nor does it represent that it has 1229 made any independent effort to identify any such rights. Information 1230 on the procedures with respect to rights in RFC documents can be 1231 found in BCP 78 and BCP 79. 1233 Copies of IPR disclosures made to the IETF Secretariat and any 1234 assurances of licenses to be made available, or the result of an 1235 attempt made to obtain a general license or permission for the use of 1236 such proprietary rights by implementers or users of this 1237 specification can be obtained from the IETF on-line IPR repository at 1238 http://www.ietf.org/ipr. 1240 The IETF invites any interested party to bring to its attention any 1241 copyrights, patents or patent applications, or other proprietary 1242 rights that may cover technology that may be required to implement 1243 this standard. Please address the information to the IETF at 1244 ietf-ipr@ietf.org. 1246 Acknowledgment 1248 Funding for the RFC Editor function is provided by the IETF 1249 Administrative Support Activity (IASA).