idnits 2.17.1 draft-ietf-idmr-igmp-mib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (28 July 1998) is 9402 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) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) -- Possible downref: Non-RFC (?) normative reference: ref. '15' ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '17') ** Obsolete normative reference: RFC 2117 (ref. '18') (Obsoleted by RFC 2362) -- Possible downref: Non-RFC (?) normative reference: ref. '19' ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '20') ** Downref: Normative reference to an Historic RFC: RFC 2189 (ref. '21') Summary: 25 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDMR Working Group Keith McCloghrie 3 INTERNET-DRAFT Dino Farinacci 4 Expires January 1999 cisco Systems 5 Dave Thaler 6 Microsoft 7 28 July 1998 9 Internet Group Management Protocol MIB 10 12 Status of this Memo 14 This document is an Internet Draft. Internet Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet Drafts. 19 Internet Drafts are valid for a maximum of six months and may be 20 updated, replaced, or obsoleted by other documents at any time. It is 21 inappropriate to use Internet Drafts as reference material or to cite 22 them other than as a "work in progress". 24 1. Introduction 26 This memo defines an experimental portion of the Management Information 27 Base (MIB) for use with network management protocols in the Internet 28 community. In particular, it describes managed objects used for 29 managing the Internet Group Management Protocol (IGMP). All of this MIB 30 module is applicable to IP multicast routers [17,18,19,20,21]; a subset 31 is applicable to hosts implementing IGMPv1 [16] or IGMPv2 [22]. 33 Draft IGMP MIB February 1998 35 2. Revision History 37 A record of changes which will be removed before publication. 39 28 July 1998 41 (1) filled in Security Considerations, added copyright, updated SNMP 42 boilerplate, and updated references 44 (2) added igmpInterfaceQuerierUpTime and 45 igmpInterfaceQuerierExpiryTime. 47 18 February 1998 49 (1) added igmpInterfaceProxyIfIndex to manage IGMP proxies. 51 (2) added igmpInterfaceLastMembQueryIntvl. 53 18 July 1997 55 (1) deprecated igmpInterfaceLeaves and added igmpInterfaceGroups to 56 replace it. 58 (2) deprecated igmpInterfaceQuerierPresentTimeout and added 59 igmpInterfaceRobustness to replace it since the former must be 60 derived from the latter per the IGMPv2 spec. 62 (3) replaced igmpBaseVersion2MIBGroup with igmpHostVersion2MIBGroup to 63 avoid requiring igmpInterfaceVersion1QuerierTimer at routers. 65 (4) deprecated igmpInterfaceLeaveEnabled 67 (5) added compliance statements for IGMPv2 hosts and routers 69 26 November 1996 71 (1) moved igmpInterfaceVersion1HostTimer to igmpCacheVersion1HostTimer. 73 (2) added igmpInterfaceVersion1QuerierTimer, 74 igmpInterfaceWrongVersionQueries, and igmpInterfaceJoins. 76 (3) added default value for igmpInterfaceQueryMaxResponseTime. 78 (4) moved igmpInterfaceVersion from igmpBaseVersion2MIBGroup to 79 igmpRouterVersion2MIBGroup. 81 Draft IGMP MIB February 1998 83 9 June 1996 85 (1) added support for IGMP version 2. 87 3. The SNMP Network Management Framework 89 The SNMP Management Framework presently consists of five major 90 components: 92 o An overall architecture, described in RFC 2271 [1]. 94 o Mechanisms for describing and naming objects and events for the 95 purpose of management. The first version of this Structure of 96 Management Information (SMI) is called SMIv1 and described in RFC 97 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 98 SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 100 o Message protocols for transferring management information. The 101 first version of the SNMP message protocol is called SNMPv1 and 102 described in RFC 1157 [8]. A second version of the SNMP message 103 protocol, which is not an Internet standards track protocol, is 104 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 105 The third version of the message protocol is called SNMPv3 and 106 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 108 o Protocol operations for accessing management information. The first 109 set of protocol operations and associated PDU formats is described 110 in RFC 1157 [8]. A second set of protocol operations and associated 111 PDU formats is described in RFC 1905 [13]. 113 o A set of fundamental applications described in RFC 2273 [14] and 114 the view-based access control mechanism described in RFC 2275 [15]. 116 Managed objects are accessed via a virtual information store, termed the 117 Management Information Base or MIB. Objects in the MIB are defined 118 using the mechanisms defined in the SMI. 120 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 121 conforming to the SMIv1 can be produced through the appropriate 122 translations. The resulting translated MIB must be semantically 123 equivalent, except where objects or events are omitted because no 124 translation is possible (use of Counter64). Some machine readable 125 information in SMIv2 will be converted into textual descriptions in 126 SMIv1 during the translation process. However, this loss of machine 127 Draft IGMP MIB February 1998 129 readable information is not considered to change the semantics of the 130 MIB. 132 3.1. Object Definitions 134 Managed objects are accessed via a virtual information store, termed the 135 Management Information Base or MIB. Objects in the MIB are defined 136 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 137 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 138 an administratively assigned name. The object type together with an 139 object instance serves to uniquely identify a specific instantiation of 140 the object. For human convenience, we often use a textual string, 141 termed the descriptor, to refer to the object type. 143 Draft IGMP MIB February 1998 145 4. Overview 147 This MIB module contains two tables: 149 (1) the IGMP Interface Table which contains one row for each interface 150 on which IGMP is enabled, and 152 (2) the IGMP Cache Table which contains one row for each IP multicast 153 group for which there are members on a particular interface. 155 Both tables are intended to be implemented by hosts and routers, but 156 some columnar objects in each table apply only to routers. 158 Draft IGMP MIB February 1998 160 5. Definitions 162 IGMP-MIB DEFINITIONS ::= BEGIN 164 IMPORTS 165 MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Gauge32, 166 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 167 RowStatus, TruthValue FROM SNMPv2-TC 168 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 170 igmpMIB MODULE-IDENTITY 171 LAST-UPDATED "9807281330Z" 172 ORGANIZATION "IETF IDMR Working Group." 173 CONTACT-INFO 174 " Keith McCloghrie 175 Cisco Systems, Inc. 176 170 West Tasman Drive 177 San Jose, CA 95134-1706 178 US 180 Phone: +1 408 526 5260 181 EMail: kzm@cisco.com" 182 DESCRIPTION 183 "The MIB module for IGMP Management." 184 ::= { experimental 59 } 186 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 } 188 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 189 Draft IGMP MIB February 1998 191 -- 192 -- The IGMP Interface Table 193 -- 195 igmpInterfaceTable OBJECT-TYPE 196 SYNTAX SEQUENCE OF IgmpInterfaceEntry 197 MAX-ACCESS not-accessible 198 STATUS current 199 DESCRIPTION 200 "The (conceptual) table listing the interfaces on which IGMP 201 is enabled." 202 ::= { igmp 1 } 204 igmpInterfaceEntry OBJECT-TYPE 205 SYNTAX IgmpInterfaceEntry 206 MAX-ACCESS not-accessible 207 STATUS current 208 DESCRIPTION 209 "An entry (conceptual row) representing an interface on 210 which IGMP is enabled." 211 INDEX { igmpInterfaceIfIndex } 212 ::= { igmpInterfaceTable 1 } 214 IgmpInterfaceEntry ::= SEQUENCE { 215 igmpInterfaceIfIndex Integer32, 216 igmpInterfaceQueryInterval Integer32, 217 igmpInterfaceStatus RowStatus, 218 igmpInterfaceVersion INTEGER, 219 igmpInterfaceQuerier IpAddress, 220 igmpInterfaceQueryMaxResponseTime Integer32, 221 igmpInterfaceQuerierPresentTimeout Integer32, -- deprecated 222 igmpInterfaceLeaveEnabled TruthValue, -- deprecated 223 igmpInterfaceVersion1QuerierTimer Integer32, 224 igmpInterfaceWrongVersionQueries Counter32, 225 igmpInterfaceJoins Counter32, 226 igmpInterfaceLeaves Counter32, -- deprecated 227 igmpInterfaceGroups Gauge32, 228 igmpInterfaceRobustness Integer32, 229 igmpInterfaceProxyIfIndex Integer32, 230 igmpInterfaceLastMembQueryIntvl Integer32, 231 igmpInterfaceQuerierUpTime Integer32, 232 igmpInterfaceQuerierExpiryTime Integer32 233 } 235 igmpInterfaceIfIndex OBJECT-TYPE 236 Draft IGMP MIB February 1998 238 SYNTAX Integer32 239 MAX-ACCESS not-accessible 240 STATUS current 241 DESCRIPTION 242 "The ifIndex value of the interface for which IGMP is 243 enabled." 244 ::= { igmpInterfaceEntry 1 } 246 igmpInterfaceQueryInterval OBJECT-TYPE 247 SYNTAX Integer32 248 UNITS "seconds" 249 MAX-ACCESS read-create 250 STATUS current 251 DESCRIPTION 252 "The frequency at which IGMP Host-Query packets are 253 transmitted on this interface." 254 DEFVAL { 125 } 255 ::= { igmpInterfaceEntry 2 } 257 igmpInterfaceStatus OBJECT-TYPE 258 SYNTAX RowStatus 259 MAX-ACCESS read-create 260 STATUS current 261 DESCRIPTION 262 "The activation of a row enables IGMP on the interface. The 263 destruction of a row disables IGMP on the interface." 264 ::= { igmpInterfaceEntry 3 } 266 igmpInterfaceVersion OBJECT-TYPE 267 SYNTAX INTEGER { version1(1), version2(2) } 268 MAX-ACCESS read-create 269 STATUS current 270 DESCRIPTION 271 "The version of IGMP which is running on this interface. 272 This object can be used to configure a router capable of 273 running either value. For IGMP to function correctly, all 274 routers on a LAN must be configured to run the same version 275 of IGMP on that LAN." 276 DEFVAL { version2 } 277 ::= { igmpInterfaceEntry 4 } 279 igmpInterfaceQuerier OBJECT-TYPE 280 SYNTAX IpAddress 281 MAX-ACCESS read-only 282 STATUS current 284 Draft IGMP MIB February 1998 286 DESCRIPTION 287 "The address of the IGMP Querier on the IP subnet to which 288 this interface is attached." 289 ::= { igmpInterfaceEntry 5 } 291 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 292 SYNTAX Integer32 293 UNITS "seconds" 294 MAX-ACCESS read-create 295 STATUS current 296 DESCRIPTION 297 "The maximum query response time advertised in IGMPv2 298 queries on this interface." 299 DEFVAL { 10 } 300 ::= { igmpInterfaceEntry 6 } 302 igmpInterfaceQuerierPresentTimeout OBJECT-TYPE 303 SYNTAX Integer32 304 UNITS "seconds" 305 MAX-ACCESS read-create 306 STATUS deprecated 307 DESCRIPTION 308 "A timeout interval. If no IGMPv2 queries are heard on this 309 interface within this timeout interval, the local router 310 will take over the Querier on the IP subnet to which this 311 interface is attached. This object is now deprecated, since 312 its value can be derived from igmpInterfaceRobustness." 313 DEFVAL { 255 } 314 ::= { igmpInterfaceEntry 7 } 316 igmpInterfaceLeaveEnabled OBJECT-TYPE 317 SYNTAX TruthValue 318 MAX-ACCESS read-create 319 STATUS deprecated 320 DESCRIPTION 321 "An indication of whether the processing of IGMPv2 Leave 322 messages is enabled on this interface. This object is now 323 deprecated since it must be true when igmpInterfaceVersion 324 is version2, and must be false when it is version1 to comply 325 with the IGMP specfication." 326 DEFVAL { true } 327 ::= { igmpInterfaceEntry 8 } 329 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 330 SYNTAX Integer32 332 Draft IGMP MIB February 1998 334 UNITS "seconds" 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The time remaining until the host assumes that there are no 339 IGMPv1 routers present on the interface. While this is 340 non-zero, the host will reply to all queries with version 1 341 membership reports." 342 ::= { igmpInterfaceEntry 9 } 344 igmpInterfaceWrongVersionQueries OBJECT-TYPE 345 SYNTAX Counter32 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "The number of queries received whose IGMP version does not 350 match igmpInterfaceVersion. IGMP requires that all routers 351 on a LAN be configured to run the same version of IGMP. 352 Thus, if any queries are received with the wrong version, 353 this indicates a configuration error." 354 ::= { igmpInterfaceEntry 10 } 356 igmpInterfaceJoins OBJECT-TYPE 357 SYNTAX Counter32 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The number of times a group membership has been added on 362 this interface; that is, the number of times an entry for 363 this interface has been added to the Cache Table. This 364 object gives an indication of the amount of IGMP activity 365 over time." 366 ::= { igmpInterfaceEntry 11 } 368 igmpInterfaceLeaves OBJECT-TYPE 369 SYNTAX Counter32 370 MAX-ACCESS read-only 371 STATUS deprecated 372 DESCRIPTION 373 "The number of times a group membership has been removed 374 from this interface; that is, the number of times an entry 375 for this interface has been deleted from the Cache Table. 376 This object is deprecated since its value cannot be usefully 377 compared with igmpInterfaceJoins to get the number of groups 378 joined. Instead, igmpInterfaceGroups gives the number of 380 Draft IGMP MIB February 1998 382 groups joined, which may be compared with igmpInterfaceJoins 383 to derive the number of leaves." 384 ::= { igmpInterfaceEntry 12 } 386 igmpInterfaceGroups OBJECT-TYPE 387 SYNTAX Gauge32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The current number of entries for this interface in the 392 Cache Table." 393 ::= { igmpInterfaceEntry 13 } 395 igmpInterfaceRobustness OBJECT-TYPE 396 SYNTAX Integer32 397 MAX-ACCESS read-create 398 STATUS current 399 DESCRIPTION 400 "The Robustness Variable allows tuning for the expected 401 packet loss on a subnet. If a subnet is expected to be 402 lossy, the Robustness Variable may be increased. IGMP is 403 robust to (Robustness Variable-1) packet losses." 404 DEFVAL { 2 } 405 ::= { igmpInterfaceEntry 14 } 407 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 408 SYNTAX Integer32 409 UNITS "tenths of seconds" 410 MAX-ACCESS read-create 411 STATUS current 412 DESCRIPTION 413 "The Last Member Query Interval is the Max Response Time 414 inserted into Group-Specific Queries sent in response to 415 Leave Group messages, and is also the amount of time between 416 Group-Specific Query messages. This value may be tuned to 417 modify the leave latency of the network. A reduced value 418 results in reduced time to detect the loss of the last 419 member of a group." 420 DEFVAL { 10 } 421 ::= { igmpInterfaceEntry 15 } 423 igmpInterfaceProxyIfIndex OBJECT-TYPE 424 SYNTAX Integer32 425 MAX-ACCESS read-create 426 STATUS current 428 Draft IGMP MIB February 1998 430 DESCRIPTION 431 "Some devices implement a form of IGMP proxying whereby 432 memberships learned on the interface represented by this 433 row, cause IGMP Host Membership Reports to be sent on the 434 interface whose ifIndex value is given by this object. Such 435 a device would implement the igmpV2RouterMIBGroup only on 436 its router interfaces (those interfaces whose ifIndex value 437 is given by this object on some interface). Typically, the 438 value of this object is 0, indicating that no proxying is 439 being done." 440 DEFVAL { 0 } 441 ::= { igmpInterfaceEntry 16 } 443 igmpInterfaceQuerierUpTime OBJECT-TYPE 444 SYNTAX Integer32 445 UNITS "seconds" 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The number of seconds since igmpInterfaceQuerier was last 450 changed." 451 ::= { igmpInterfaceEntry 17 } 453 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 454 SYNTAX Integer32 455 UNITS "seconds" 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The number of seconds remaining before the Other Querier 460 Present Timer expires. If the local system is the querier, 461 the value of this object is zero." 462 ::= { igmpInterfaceEntry 18 } 464 Draft IGMP MIB February 1998 466 -- 467 -- The IGMP Cache Table 468 -- 470 igmpCacheTable OBJECT-TYPE 471 SYNTAX SEQUENCE OF IgmpCacheEntry 472 MAX-ACCESS not-accessible 473 STATUS current 474 DESCRIPTION 475 "The (conceptual) table listing the IP multicast groups for 476 which there are members on a particular interface." 477 ::= { igmp 2 } 479 igmpCacheEntry OBJECT-TYPE 480 SYNTAX IgmpCacheEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "An entry (conceptual row) in the igmpCacheTable." 485 INDEX { igmpCacheAddress, igmpCacheIfIndex } 486 ::= { igmpCacheTable 1 } 488 IgmpCacheEntry ::= SEQUENCE { 489 igmpCacheAddress IpAddress, 490 igmpCacheIfIndex Integer32, 491 igmpCacheSelf TruthValue, 492 igmpCacheLastReporter IpAddress, 493 igmpCacheUpTime TimeTicks, 494 igmpCacheExpiryTime TimeTicks, 495 igmpCacheStatus RowStatus, 496 igmpCacheVersion1HostTimer Integer32 497 } 499 igmpCacheAddress OBJECT-TYPE 500 SYNTAX IpAddress 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 "The IP multicast group address for which this entry 505 contains information." 506 ::= { igmpCacheEntry 1 } 508 igmpCacheIfIndex OBJECT-TYPE 509 SYNTAX Integer32 510 MAX-ACCESS not-accessible 512 Draft IGMP MIB February 1998 514 STATUS current 515 DESCRIPTION 516 "The interface for which this entry contains information for 517 an IP multicast group address." 518 ::= { igmpCacheEntry 2 } 520 igmpCacheSelf OBJECT-TYPE 521 SYNTAX TruthValue 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "An indication of whether the local system is a member of 526 this group address on this interface." 527 DEFVAL { true } 528 ::= { igmpCacheEntry 3 } 530 igmpCacheLastReporter OBJECT-TYPE 531 SYNTAX IpAddress 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The IP address of the source of the last membership report 536 received for this IP Multicast group address on this 537 interface. If no membership report has been received, this 538 object has the value 0.0.0.0." 539 ::= { igmpCacheEntry 4 } 541 igmpCacheUpTime OBJECT-TYPE 542 SYNTAX TimeTicks 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "The time since the system joined this group address, or 547 zero if the system is not currently a member." 548 ::= { igmpCacheEntry 5 } 550 igmpCacheExpiryTime OBJECT-TYPE 551 SYNTAX TimeTicks 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "The minimum amount of time remaining before this entry will 556 be aged out." 557 ::= { igmpCacheEntry 6 } 559 Draft IGMP MIB February 1998 561 igmpCacheStatus OBJECT-TYPE 562 SYNTAX RowStatus 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 566 "The status of this entry." 567 ::= { igmpCacheEntry 7 } 569 igmpCacheVersion1HostTimer OBJECT-TYPE 570 SYNTAX Integer32 571 UNITS "seconds" 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The time remaining until the local router will assume that 576 there are no longer any IGMP version 1 members on the IP 577 subnet attached to this interface. Upon hearing any IGMPv1 578 Membership Report, this value is reset to the group 579 membership timer. While this time remaining is non-zero, 580 the local router ignores any IGMPv2 Leave messages for this 581 group that it receives on this interface." 582 ::= { igmpCacheEntry 8 } 584 Draft IGMP MIB February 1998 586 -- conformance information 588 igmpMIBConformance 589 OBJECT IDENTIFIER ::= { igmpMIB 2 } 590 igmpMIBCompliances 591 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 592 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 594 -- compliance statements 596 igmpV1HostMIBCompliance MODULE-COMPLIANCE 597 STATUS current 598 DESCRIPTION 599 "The compliance statement for hosts running IGMPv1 and 600 implementing the IGMP MIB." 601 MODULE -- this module 602 MANDATORY-GROUPS { igmpBaseMIBGroup } 604 OBJECT igmpInterfaceStatus 605 MIN-ACCESS read-only 606 DESCRIPTION 607 "Write access is not required." 609 ::= { igmpMIBCompliances 1 } 611 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 612 STATUS current 613 DESCRIPTION 614 "The compliance statement for routers running IGMPv1 and 615 implementing the IGMP MIB." 616 MODULE -- this module 617 MANDATORY-GROUPS { igmpBaseMIBGroup, 618 igmpRouterMIBGroup 619 } 621 OBJECT igmpInterfaceStatus 622 MIN-ACCESS read-only 623 DESCRIPTION 624 "Write access is not required." 626 ::= { igmpMIBCompliances 2 } 628 igmpV2HostMIBCompliance MODULE-COMPLIANCE 629 STATUS current 631 Draft IGMP MIB February 1998 633 DESCRIPTION 634 "The compliance statement for hosts running IGMPv2 and 635 implementing the IGMP MIB." 636 MODULE -- this module 637 MANDATORY-GROUPS { igmpBaseMIBGroup, 638 igmpV2HostMIBGroup 639 } 641 OBJECT igmpInterfaceStatus 642 MIN-ACCESS read-only 643 DESCRIPTION 644 "Write access is not required." 646 ::= { igmpMIBCompliances 3 } 648 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 649 STATUS current 650 DESCRIPTION 651 "The compliance statement for routers running IGMPv2 and 652 implementing the IGMP MIB." 653 MODULE -- this module 654 MANDATORY-GROUPS { igmpBaseMIBGroup, 655 igmpRouterMIBGroup, 656 igmpV2RouterMIBGroup 657 } 659 OBJECT igmpInterfaceStatus 660 MIN-ACCESS read-only 661 DESCRIPTION 662 "Write access is not required." 664 ::= { igmpMIBCompliances 4 } 666 -- units of conformance 668 igmpBaseMIBGroup OBJECT-GROUP 669 OBJECTS { igmpCacheSelf, igmpCacheLastReporter, 670 igmpCacheStatus, igmpInterfaceStatus 671 } 672 STATUS current 673 DESCRIPTION 674 "The basic collection of objects providing management of 675 IGMP version 1 or 2." 676 ::= { igmpMIBGroups 1 } 678 Draft IGMP MIB February 1998 680 igmpRouterMIBGroup OBJECT-GROUP 681 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 682 igmpInterfaceQueryInterval 683 } 684 STATUS current 685 DESCRIPTION 686 "A collection of additional objects for management of IGMP 687 version 1 or 2 in routers." 688 ::= { igmpMIBGroups 2 } 690 igmpV2HostMIBGroup OBJECT-GROUP 691 OBJECTS { igmpInterfaceQuerier, 692 igmpInterfaceVersion1QuerierTimer 693 } 694 STATUS current 695 DESCRIPTION 696 "A collection of additional objects for management of IGMP 697 version 2 in hosts." 698 ::= { igmpMIBGroups 3 } 700 igmpRouterVersion2MIBGroup OBJECT-GROUP 701 OBJECTS { igmpInterfaceVersion, 702 igmpInterfaceQueryMaxResponseTime, 703 igmpInterfaceQuerierPresentTimeout, 704 igmpInterfaceLeaveEnabled, 705 igmpInterfaceWrongVersionQueries, 706 igmpInterfaceJoins, 707 igmpInterfaceLeaves, 708 igmpCacheVersion1HostTimer 709 } 710 STATUS deprecated 711 DESCRIPTION 712 "A collection of additional objects for management of IGMP 713 version 2 in routers. This group has been obsoleted by 714 igmpV2RouterMIBGroup." 715 ::= { igmpMIBGroups 4 } 717 igmpV2RouterMIBGroup OBJECT-GROUP 718 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 719 igmpInterfaceQueryMaxResponseTime, 720 igmpInterfaceRobustness, 721 igmpInterfaceWrongVersionQueries, 722 igmpInterfaceJoins, igmpInterfaceGroups, 723 igmpInterfaceLastMembQueryIntvl, 725 Draft IGMP MIB February 1998 727 igmpInterfaceQuerierUpTime, 728 igmpInterfaceQuerierExpiryTime, 729 igmpCacheVersion1HostTimer 730 } 731 STATUS current 732 DESCRIPTION 733 "A collection of additional objects for management of IGMP 734 version 2 in routers." 735 ::= { igmpMIBGroups 5 } 737 igmpV2ProxyMIBGroup OBJECT-GROUP 738 OBJECTS { igmpInterfaceProxyIfIndex } 739 STATUS current 740 DESCRIPTION 741 "A collection of additional objects for management of IGMP 742 proxy devices." 743 ::= { igmpMIBGroups 6 } 745 END 746 Draft IGMP MIB February 1998 748 6. Security Considerations 750 This MIB contains readable objects whose values provide information 751 related to multicast sessions. Some of these objects could contain 752 sensitive information. In particular, the igmpCacheSelf and 753 igmpCacheLastReporter can be used to identify machines which are 754 listening to a given group address. There are also a number of objects 755 that have a MAX-ACCESS clause of read-write and/or read-create, which 756 allow an administrator to configure IGMP in the router. 758 While unauthorized access to the readable objects is relatively 759 innocuous, unauthorized access to the write-able objects could cause a 760 denial of service. Hence, the support for SET operations in a non- 761 secure environment without proper protection can have a negative effect 762 on network operations. 764 SNMPv1 by itself is such an insecure environment. Even if the network 765 itself is secure (for example by using IPSec), even then, there is no 766 control as to who on the secure network is allowed to access and SET 767 (change/create/delete) the objects in this MIB. 769 It is recommended that the implementers consider the security features 770 as provided by the SNMPv3 framework. Specifically, the use of the 771 User-based Security Model RFC 2274 [12] and the View-based Access 772 Control Model RFC 2275 [15] is recommended. 774 It is then a customer/user responsibility to ensure that the SNMP entity 775 giving access to this MIB, is properly configured to give access to 776 those objects only to those principals (users) that have legitimate 777 rights to access them. 779 7. Acknowledgements 781 This MIB module was updated based on feedback from the IETF's Inter- 782 Domain Multicast Routing (IDMR) Working Group. 784 8. Authors' Addresses 786 Keith McCloghrie 787 cisco Systems, Inc. 788 170 West Tasman Drive 789 San Jose, CA 95134-1706 791 Draft IGMP MIB February 1998 793 Phone: +1 408 526 5260 794 EMail: kzm@cisco.com 796 Dino Farinacci 797 cisco Systems, Inc. 798 170 West Tasman Drive 799 San Jose, CA 95134-1706 800 Phone: +1 408 526 4696 801 EMail: dino@cisco.com 803 Dave Thaler 804 Microsoft Corporation 805 One Microsoft Way 806 Redmond, WA 48105-6399 807 Phone: +1 425 703 8835 808 EMail: dthaler@microsoft.com 810 9. References 812 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 813 Describing SNMP Management Frameworks", RFC 2271, Cabletron 814 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 815 January 1998. 817 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 818 Management Information for TCP/IP-based Internets", RFC 1155, 819 Performance Systems International, Hughes LAN Systems, May 1990. 821 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 822 Performance Systems International, Hughes LAN Systems, March 1991. 824 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 825 RFC 1215, Performance Systems International, March 1991. 827 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 828 of Management Information for Version 2 of the Simple Network 829 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 830 Systems, Inc., Dover Beach Consulting, Inc., International Network 831 Services, January 1996. 833 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 834 Conventions for Version 2 of the Simple Network Management Protocol 835 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 836 Dover Beach Consulting, Inc., International Network Services, 838 Draft IGMP MIB February 1998 840 January 1996. 842 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 843 Statements for Version 2 of the Simple Network Management Protocol 844 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 845 Dover Beach Consulting, Inc., International Network Services, 846 January 1996. 848 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 849 Management Protocol", RFC 1157, SNMP Research, Performance Systems 850 International, Performance Systems International, MIT Laboratory 851 for Computer Science, May 1990. 853 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 854 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 855 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 856 International Network Services, January 1996. 858 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 859 Mappings for Version 2 of the Simple Network Management Protocol 860 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 861 Dover Beach Consulting, Inc., International Network Services, 862 January 1996. 864 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 865 Processing and Dispatching for the Simple Network Management 866 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 867 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 869 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 870 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 871 2274, IBM T. J. Watson Research, January 1998. 873 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 874 Operations for Version 2 of the Simple Network Management Protocol 875 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 876 Dover Beach Consulting, Inc., International Network Services, 877 January 1996. 879 [14] Levi, D., Meyer, P., and B. Stewart, "MPv3 Applications", RFC 2273, 880 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 881 January 1998. 883 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 884 Control Model (VACM) for the Simple Network Management Protocol 886 Draft IGMP MIB February 1998 888 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 889 Cisco Systems, Inc., January 1998. 891 [16] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, 892 Stanford University, August 1989. 894 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 895 Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman, 896 Stanford University, November 1988. 898 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 899 Handley, M., Jacobson, V., Liu, C., and P. Sharma, "Protocol 900 Independent Multicast - Sparse Mode (PIM-SM): Protocol 901 Specification", RFC 2117, June 1997. 903 [19] Estrin, D., Farinacci, D., Jacobson, V., Liu, C., Wei, L., Sharma, 904 P, and Helmy, A., "Protocol Independent Multicast-Dense Mode (PIM- 905 DM): Protocol Specification", January 1996. 907 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March 908 1994. 910 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 911 Routing: Protocol Specification", RFC 2189, September 1997. 913 [22] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 914 2236, November 1997. 916 10. Full Copyright Statement 918 Copyright (C) The Internet Society (1998). All Rights Reserved. 920 This document and translations of it may be copied and furnished to 921 others, and derivative works that comment on or otherwise explain it or 922 assist in its implmentation may be prepared, copied, published and 923 distributed, in whole or in part, without restriction of any kind, 924 provided that the above copyright notice and this paragraph are included 925 on all such copies and derivative works. However, this document itself 926 may not be modified in any way, such as by removing the copyright notice 927 or references to the Internet Society or other Internet organizations, 928 except as needed for the purpose of developing Internet standards in 929 which case the procedures for copyrights defined in the Internet 930 Standards process must be followed, or as required to translate it into 931 languages other than English. 933 Draft IGMP MIB February 1998 935 The limited permissions granted above are perpetual and will not be 936 revoked by the Internet Society or its successors or assigns. 938 This document and the information contained herein is provided on an "AS 939 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 940 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 941 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 942 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 943 FITNESS FOR A PARTICULAR PURPOSE." 945 Table of Contents 947 1 Introduction .................................................... 1 948 2 Revision History ................................................ 2 949 3 The SNMP Network Management Framework ........................... 3 950 3.1 Object Definitions ............................................ 4 951 4 Overview ........................................................ 5 952 5 Definitions ..................................................... 6 953 6 Security Considerations ......................................... 20 954 7 Acknowledgements ................................................ 20 955 8 Authors' Addresses .............................................. 20 956 9 References ...................................................... 21 957 10 Full Copyright Statement ....................................... 23