idnits 2.17.00 (12 Aug 2021) /tmp/idnits27832/draft-ietf-idmr-igmp-mib-14.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- == 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 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 copyright year in the RFC 3978 Section 5.4 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 (7 July 2000) is 7981 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 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** 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 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IDMR Working Group Keith McCloghrie 2 INTERNET-DRAFT Dino Farinacci 3 Expires January 2001 cisco Systems 4 Dave Thaler 5 Microsoft 6 7 July 2000 8 Internet Group Management Protocol MIB 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with all 14 provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering Task 17 Force (IETF), its areas, and its working groups. Note that other groups 18 may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference material 23 or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Copyright Notice 33 Copyright (C) The Internet Society (2000). All Rights Reserved. 35 Draft IGMP MIB July 2000 37 1. Abstract 39 This memo defines a portion of the Management Information Base (MIB) for 40 use with network management protocols in the Internet community. In 41 particular, it describes objects used for managing the Internet Group 42 Management Protocol (IGMP). 44 2. Introduction 46 This memo defines a portion of the Management Information Base (MIB) for 47 use with network management protocols in the Internet community. In 48 particular, it describes objects used for managing the Internet Group 49 Management Protocol (IGMP), version 1 [16] or version 2 [17]. A future 50 version of this MIB will support IGMP version 3 (currently a work in 51 progress). All of this MIB module is applicable to IPv4 multicast 52 routers; a subset is applicable to hosts implementing IGMP. Since IGMP 53 is specific to IPv4, this MIB does not support management of equivalent 54 functionality for other address families, such as IPv6. Such management 55 may be supported by other MIBs. 57 3. The SNMP Network Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in RFC 2571 [1]. 64 o Mechanisms for describing and naming objects and events for the 65 purpose of management. The first version of this Structure of 66 Management Information (SMI) is called SMIv1 and described in RFC 67 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 68 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 70 o Message protocols for transferring management information. The 71 first version of the SNMP message protocol is called SNMPv1 and 72 described in RFC 1157 [8]. A second version of the SNMP message 73 protocol, which is not an Internet standards track protocol, is 74 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 75 The third version of the message protocol is called SNMPv3 and 76 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 78 o Protocol operations for accessing management information. The first 79 set of protocol operations and associated PDU formats is described 81 Draft IGMP MIB July 2000 83 in RFC 1157 [8]. A second set of protocol operations and associated 84 PDU formats is described in RFC 1905 [13]. 86 o A set of fundamental applications described in RFC 2573 [14] and 87 the view-based access control mechanism described in RFC 2575 [15]. 89 Managed objects are accessed via a virtual information store, termed the 90 Management Information Base or MIB. Objects in the MIB are defined 91 using the mechanisms defined in the SMI. 93 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 94 conforming to the SMIv1 can be produced through the appropriate 95 translations. The resulting translated MIB must be semantically 96 equivalent, except where objects or events are omitted because no 97 translation is possible (use of Counter64). Some machine readable 98 information in SMIv2 will be converted into textual descriptions in 99 SMIv1 during the translation process. However, this loss of machine 100 readable information is not considered to change the semantics of the 101 MIB. 103 4. Overview 105 This MIB module contains two tables: 107 (1) the IGMP Interface Table which contains one row for each 108 interface on which IGMP is enabled, and 110 (2) the IGMP Cache Table which contains one row for each IP multicast 111 group for which there are members on a particular interface. 113 Both tables are intended to be implemented by hosts and routers, but 114 some columnar objects in each table apply only to routers. 116 Draft IGMP MIB July 2000 118 5. Definitions 120 IGMP-STD-MIB DEFINITIONS ::= BEGIN 122 IMPORTS 123 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32, 124 Unsigned32, IpAddress, TimeTicks FROM SNMPv2-SMI 125 RowStatus, TruthValue FROM SNMPv2-TC 126 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 127 InterfaceIndexOrZero, 128 InterfaceIndex FROM IF-MIB; 130 igmpStdMIB MODULE-IDENTITY 131 LAST-UPDATED "200007071200Z" -- July 7, 2000 132 ORGANIZATION "IETF IDMR Working Group." 133 CONTACT-INFO 134 " Dave Thaler 135 Microsoft Corporation 136 One Microsoft Way 137 Redmond, WA 98052-6399 138 US 140 Phone: +1 425 703 8835 141 EMail: dthaler@microsoft.com" 142 DESCRIPTION 143 "The MIB module for IGMP Management." 144 REVISION "200007071200Z" -- July 7, 2000 145 DESCRIPTION 146 "Initial version, published as RFC xxxx (to be filled in by 147 RFC-Editor)." 148 ::= { mib-2 xx } 149 -- NOTE TO RFC EDITOR: When this document is published as 150 -- an RFC, replace XX with IANA-assigned value and delete 151 -- this comment. 153 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpStdMIB 1 } 154 Draft IGMP MIB July 2000 156 -- 157 -- The IGMP Interface Table 158 -- 160 igmpInterfaceTable OBJECT-TYPE 161 SYNTAX SEQUENCE OF IgmpInterfaceEntry 162 MAX-ACCESS not-accessible 163 STATUS current 164 DESCRIPTION 165 "The (conceptual) table listing the interfaces on which IGMP 166 is enabled." 167 ::= { igmpMIBObjects 1 } 169 igmpInterfaceEntry OBJECT-TYPE 170 SYNTAX IgmpInterfaceEntry 171 MAX-ACCESS not-accessible 172 STATUS current 173 DESCRIPTION 174 "An entry (conceptual row) representing an interface on 175 which IGMP is enabled." 176 INDEX { igmpInterfaceIfIndex } 177 ::= { igmpInterfaceTable 1 } 179 IgmpInterfaceEntry ::= SEQUENCE { 180 igmpInterfaceIfIndex InterfaceIndex, 181 igmpInterfaceQueryInterval Unsigned32, 182 igmpInterfaceStatus RowStatus, 183 igmpInterfaceVersion Unsigned32, 184 igmpInterfaceQuerier IpAddress, 185 igmpInterfaceQueryMaxResponseTime Unsigned32, 186 igmpInterfaceQuerierUpTime TimeTicks, 187 igmpInterfaceQuerierExpiryTime TimeTicks, 188 igmpInterfaceVersion1QuerierTimer TimeTicks, 189 igmpInterfaceWrongVersionQueries Counter32, 190 igmpInterfaceJoins Counter32, 191 igmpInterfaceProxyIfIndex InterfaceIndexOrZero, 192 igmpInterfaceGroups Gauge32, 193 igmpInterfaceRobustness Unsigned32, 194 igmpInterfaceLastMembQueryIntvl Unsigned32 195 } 197 igmpInterfaceIfIndex OBJECT-TYPE 198 SYNTAX InterfaceIndex 199 MAX-ACCESS not-accessible 200 STATUS current 202 Draft IGMP MIB July 2000 204 DESCRIPTION 205 "The ifIndex value of the interface for which IGMP is 206 enabled." 207 ::= { igmpInterfaceEntry 1 } 209 igmpInterfaceQueryInterval OBJECT-TYPE 210 SYNTAX Unsigned32 211 UNITS "seconds" 212 MAX-ACCESS read-create 213 STATUS current 214 DESCRIPTION 215 "The frequency at which IGMP Host-Query packets are 216 transmitted on this interface." 217 DEFVAL { 125 } 218 ::= { igmpInterfaceEntry 2 } 220 igmpInterfaceStatus OBJECT-TYPE 221 SYNTAX RowStatus 222 MAX-ACCESS read-create 223 STATUS current 224 DESCRIPTION 225 "The activation of a row enables IGMP on the interface. The 226 destruction of a row disables IGMP on the interface." 227 ::= { igmpInterfaceEntry 3 } 229 igmpInterfaceVersion OBJECT-TYPE 230 SYNTAX Unsigned32 231 MAX-ACCESS read-create 232 STATUS current 233 DESCRIPTION 234 "The version of IGMP which is running on this interface. 235 This object can be used to configure a router capable of 236 running either value. For IGMP to function correctly, all 237 routers on a LAN must be configured to run the same version 238 of IGMP on that LAN." 239 DEFVAL { 2 } 240 ::= { igmpInterfaceEntry 4 } 242 igmpInterfaceQuerier OBJECT-TYPE 243 SYNTAX IpAddress 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 "The address of the IGMP Querier on the IP subnet to which 248 this interface is attached." 250 Draft IGMP MIB July 2000 252 ::= { igmpInterfaceEntry 5 } 254 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 255 SYNTAX Unsigned32 (0..255) 256 UNITS "tenths of seconds" 257 MAX-ACCESS read-create 258 STATUS current 259 DESCRIPTION 260 "The maximum query response time advertised in IGMPv2 261 queries on this interface." 262 DEFVAL { 100 } 263 ::= { igmpInterfaceEntry 6 } 265 igmpInterfaceQuerierUpTime OBJECT-TYPE 266 SYNTAX TimeTicks 267 MAX-ACCESS read-only 268 STATUS current 269 DESCRIPTION 270 "The time since igmpInterfaceQuerier was last changed." 271 ::= { igmpInterfaceEntry 7 } 273 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 274 SYNTAX TimeTicks 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "The amount of time remaining before the Other Querier 279 Present Timer expires. If the local system is the querier, 280 the value of this object is zero." 281 ::= { igmpInterfaceEntry 8 } 283 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 284 SYNTAX TimeTicks 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The time remaining until the host assumes that there are no 289 IGMPv1 routers present on the interface. While this is non- 290 zero, the host will reply to all queries with version 1 291 membership reports." 292 ::= { igmpInterfaceEntry 9 } 294 igmpInterfaceWrongVersionQueries OBJECT-TYPE 295 SYNTAX Counter32 296 MAX-ACCESS read-only 298 Draft IGMP MIB July 2000 300 STATUS current 301 DESCRIPTION 302 "The number of queries received whose IGMP version does not 303 match igmpInterfaceVersion, over the lifetime of the row 304 entry. IGMP requires that all routers on a LAN be 305 configured to run the same version of IGMP. Thus, if any 306 queries are received with the wrong version, this indicates 307 a configuration error." 308 ::= { igmpInterfaceEntry 10 } 310 igmpInterfaceJoins OBJECT-TYPE 311 SYNTAX Counter32 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "The number of times a group membership has been added on 316 this interface; that is, the number of times an entry for 317 this interface has been added to the Cache Table. This 318 object gives an indication of the amount of IGMP activity 319 over the lifetime of the row entry." 320 ::= { igmpInterfaceEntry 11 } 322 igmpInterfaceProxyIfIndex OBJECT-TYPE 323 SYNTAX InterfaceIndexOrZero 324 MAX-ACCESS read-create 325 STATUS current 326 DESCRIPTION 327 "Some devices implement a form of IGMP proxying whereby 328 memberships learned on the interface represented by this 329 row, cause IGMP Host Membership Reports to be sent on the 330 interface whose ifIndex value is given by this object. Such 331 a device would implement the igmpV2RouterMIBGroup only on 332 its router interfaces (those interfaces with non-zero 333 igmpInterfaceProxyIfIndex). Typically, the value of this 334 object is 0, indicating that no proxying is being done." 335 DEFVAL { 0 } 336 ::= { igmpInterfaceEntry 12 } 338 igmpInterfaceGroups OBJECT-TYPE 339 SYNTAX Gauge32 340 MAX-ACCESS read-only 341 STATUS current 342 DESCRIPTION 343 "The current number of entries for this interface in the 344 Cache Table." 346 Draft IGMP MIB July 2000 348 ::= { igmpInterfaceEntry 13 } 350 igmpInterfaceRobustness OBJECT-TYPE 351 SYNTAX Unsigned32 (1..255) 352 MAX-ACCESS read-create 353 STATUS current 354 DESCRIPTION 355 "The Robustness Variable allows tuning for the expected 356 packet loss on a subnet. If a subnet is expected to be 357 lossy, the Robustness Variable may be increased. IGMP is 358 robust to (Robustness Variable-1) packet losses." 359 DEFVAL { 2 } 360 ::= { igmpInterfaceEntry 14 } 362 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 363 SYNTAX Unsigned32 (0..255) 364 UNITS "tenths of seconds" 365 MAX-ACCESS read-create 366 STATUS current 367 DESCRIPTION 368 "The Last Member Query Interval is the Max Response Time 369 inserted into Group-Specific Queries sent in response to 370 Leave Group messages, and is also the amount of time between 371 Group-Specific Query messages. This value may be tuned to 372 modify the leave latency of the network. A reduced value 373 results in reduced time to detect the loss of the last 374 member of a group. The value of this object is irrelevant 375 if igmpInterfaceVersion is 1." 376 DEFVAL { 10 } 377 ::= { igmpInterfaceEntry 15 } 379 Draft IGMP MIB July 2000 381 -- 382 -- The IGMP Cache Table 383 -- 385 igmpCacheTable OBJECT-TYPE 386 SYNTAX SEQUENCE OF IgmpCacheEntry 387 MAX-ACCESS not-accessible 388 STATUS current 389 DESCRIPTION 390 "The (conceptual) table listing the IP multicast groups for 391 which there are members on a particular interface." 392 ::= { igmpMIBObjects 2 } 394 igmpCacheEntry OBJECT-TYPE 395 SYNTAX IgmpCacheEntry 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "An entry (conceptual row) in the igmpCacheTable." 400 INDEX { igmpCacheAddress, igmpCacheIfIndex } 401 ::= { igmpCacheTable 1 } 403 IgmpCacheEntry ::= SEQUENCE { 404 igmpCacheAddress IpAddress, 405 igmpCacheIfIndex InterfaceIndex, 406 igmpCacheSelf TruthValue, 407 igmpCacheLastReporter IpAddress, 408 igmpCacheUpTime TimeTicks, 409 igmpCacheExpiryTime TimeTicks, 410 igmpCacheStatus RowStatus, 411 igmpCacheVersion1HostTimer TimeTicks 412 } 414 igmpCacheAddress OBJECT-TYPE 415 SYNTAX IpAddress 416 MAX-ACCESS not-accessible 417 STATUS current 418 DESCRIPTION 419 "The IP multicast group address for which this entry 420 contains information." 421 ::= { igmpCacheEntry 1 } 423 igmpCacheIfIndex OBJECT-TYPE 424 SYNTAX InterfaceIndex 425 MAX-ACCESS not-accessible 427 Draft IGMP MIB July 2000 429 STATUS current 430 DESCRIPTION 431 "The interface for which this entry contains information for 432 an IP multicast group address." 433 ::= { igmpCacheEntry 2 } 435 igmpCacheSelf OBJECT-TYPE 436 SYNTAX TruthValue 437 MAX-ACCESS read-create 438 STATUS current 439 DESCRIPTION 440 "An indication of whether the local system is a member of 441 this group address on this interface." 442 DEFVAL { true } 443 ::= { igmpCacheEntry 3 } 445 igmpCacheLastReporter OBJECT-TYPE 446 SYNTAX IpAddress 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The IP address of the source of the last membership report 451 received for this IP Multicast group address on this 452 interface. If no membership report has been received, this 453 object has the value 0.0.0.0." 454 ::= { igmpCacheEntry 4 } 456 igmpCacheUpTime OBJECT-TYPE 457 SYNTAX TimeTicks 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The time elapsed since this entry was created." 462 ::= { igmpCacheEntry 5 } 464 igmpCacheExpiryTime OBJECT-TYPE 465 SYNTAX TimeTicks 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The minimum amount of time remaining before this entry will 470 be aged out. A value of 0 indicates that the entry is only 471 present because igmpCacheSelf is true and that if the router 472 left the group, this entry would be aged out immediately. 473 Note that some implementations may process membership 475 Draft IGMP MIB July 2000 477 reports from the local system in the same way as reports 478 from other hosts, so a value of 0 is not required." 479 ::= { igmpCacheEntry 6 } 481 igmpCacheStatus OBJECT-TYPE 482 SYNTAX RowStatus 483 MAX-ACCESS read-create 484 STATUS current 485 DESCRIPTION 486 "The status of this entry." 487 ::= { igmpCacheEntry 7 } 489 igmpCacheVersion1HostTimer OBJECT-TYPE 490 SYNTAX TimeTicks 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The time remaining until the local router will assume that 495 there are no longer any IGMP version 1 members on the IP 496 subnet attached to this interface. Upon hearing any IGMPv1 497 Membership Report, this value is reset to the group 498 membership timer. While this time remaining is non-zero, 499 the local router ignores any IGMPv2 Leave messages for this 500 group that it receives on this interface." 501 ::= { igmpCacheEntry 8 } 503 Draft IGMP MIB July 2000 505 -- conformance information 507 igmpMIBConformance 508 OBJECT IDENTIFIER ::= { igmpStdMIB 2 } 509 igmpMIBCompliances 510 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 511 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 513 -- compliance statements 515 igmpV1HostMIBCompliance MODULE-COMPLIANCE 516 STATUS current 517 DESCRIPTION 518 "The compliance statement for hosts running IGMPv1 and 519 implementing the IGMP MIB." 520 MODULE -- this module 521 MANDATORY-GROUPS { igmpBaseMIBGroup } 523 OBJECT igmpInterfaceStatus 524 MIN-ACCESS read-only 525 DESCRIPTION 526 "Write access is not required." 528 OBJECT igmpCacheStatus 529 MIN-ACCESS read-only 530 DESCRIPTION 531 "Write access is not required." 533 ::= { igmpMIBCompliances 1 } 535 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 536 STATUS current 537 DESCRIPTION 538 "The compliance statement for routers running IGMPv1 and 539 implementing the IGMP MIB." 540 MODULE -- this module 541 MANDATORY-GROUPS { igmpBaseMIBGroup, 542 igmpRouterMIBGroup 543 } 545 OBJECT igmpInterfaceStatus 546 MIN-ACCESS read-only 547 DESCRIPTION 548 "Write access is not required." 550 Draft IGMP MIB July 2000 552 OBJECT igmpCacheStatus 553 MIN-ACCESS read-only 554 DESCRIPTION 555 "Write access is not required." 557 ::= { igmpMIBCompliances 2 } 559 igmpV2HostMIBCompliance MODULE-COMPLIANCE 560 STATUS current 561 DESCRIPTION 562 "The compliance statement for hosts running IGMPv2 and 563 implementing the IGMP MIB." 564 MODULE -- this module 565 MANDATORY-GROUPS { igmpBaseMIBGroup, 566 igmpV2HostMIBGroup 567 } 569 OBJECT igmpInterfaceStatus 570 MIN-ACCESS read-only 571 DESCRIPTION 572 "Write access is not required." 574 OBJECT igmpCacheStatus 575 MIN-ACCESS read-only 576 DESCRIPTION 577 "Write access is not required." 579 ::= { igmpMIBCompliances 3 } 581 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 582 STATUS current 583 DESCRIPTION 584 "The compliance statement for routers running IGMPv2 and 585 implementing the IGMP MIB." 586 MODULE -- this module 587 MANDATORY-GROUPS { igmpBaseMIBGroup, 588 igmpRouterMIBGroup, 589 igmpV2RouterMIBGroup 590 } 592 OBJECT igmpInterfaceStatus 593 MIN-ACCESS read-only 594 DESCRIPTION 595 "Write access is not required." 597 Draft IGMP MIB July 2000 599 OBJECT igmpCacheStatus 600 MIN-ACCESS read-only 601 DESCRIPTION 602 "Write access is not required." 604 ::= { igmpMIBCompliances 4 } 606 -- units of conformance 608 igmpBaseMIBGroup OBJECT-GROUP 609 OBJECTS { igmpCacheSelf, 610 igmpCacheStatus, igmpInterfaceStatus 611 } 612 STATUS current 613 DESCRIPTION 614 "The basic collection of objects providing management of 615 IGMP version 1 or 2." 616 ::= { igmpMIBGroups 1 } 618 igmpRouterMIBGroup OBJECT-GROUP 619 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 620 igmpInterfaceJoins, igmpInterfaceGroups, 621 igmpCacheLastReporter, igmpInterfaceQuerierUpTime, 622 igmpInterfaceQuerierExpiryTime, 623 igmpInterfaceQueryInterval 624 } 625 STATUS current 626 DESCRIPTION 627 "A collection of additional objects for management of IGMP 628 version 1 or 2 in routers." 629 ::= { igmpMIBGroups 2 } 631 igmpV2HostMIBGroup OBJECT-GROUP 632 OBJECTS { igmpInterfaceVersion1QuerierTimer } 633 STATUS current 634 DESCRIPTION 635 "A collection of additional objects for management of IGMP 636 version 2 in hosts." 637 ::= { igmpMIBGroups 3 } 639 igmpHostOptMIBGroup OBJECT-GROUP 640 OBJECTS { igmpCacheLastReporter, igmpInterfaceQuerier } 642 Draft IGMP MIB July 2000 644 STATUS current 645 DESCRIPTION 646 "A collection of optional objects for IGMP hosts. 647 Supporting this group can be especially useful in an 648 environment with a router which does not support the IGMP 649 MIB." 650 ::= { igmpMIBGroups 4 } 652 igmpV2RouterMIBGroup OBJECT-GROUP 653 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 654 igmpInterfaceQueryMaxResponseTime, 655 igmpInterfaceRobustness, 656 igmpInterfaceWrongVersionQueries, 657 igmpInterfaceLastMembQueryIntvl, 658 igmpCacheVersion1HostTimer 659 } 660 STATUS current 661 DESCRIPTION 662 "A collection of additional objects for management of IGMP 663 version 2 in routers." 664 ::= { igmpMIBGroups 5 } 666 igmpV2ProxyMIBGroup OBJECT-GROUP 667 OBJECTS { igmpInterfaceProxyIfIndex } 668 STATUS current 669 DESCRIPTION 670 "A collection of additional objects for management of IGMP 671 proxy devices." 672 ::= { igmpMIBGroups 6 } 674 END 675 Draft IGMP MIB July 2000 677 6. Security Considerations 679 This MIB contains readable objects whose values provide information 680 related to multicast sessions. Some of these objects could contain 681 sensitive information. In particular, the igmpCacheSelf and 682 igmpCacheLastReporter can be used to identify machines which are 683 listening to a given group address. There are also a number of objects 684 that have a MAX-ACCESS clause of read-write and/or read-create, which 685 allow an administrator to configure IGMP in the router. 687 While unauthorized access to the readable objects is relatively 688 innocuous, unauthorized access to the write-able objects could cause a 689 denial of service. Hence, the support for SET operations in a non- 690 secure environment without proper protection can have a negative effect 691 on network operations. 693 SNMPv1 by itself is such an insecure environment. Even if the network 694 itself is secure (for example by using IPSec), even then, there is no 695 control as to who on the secure network is allowed to access and SET 696 (change/create/delete) the objects in this MIB. 698 It is recommended that the implementers consider the security features 699 as provided by the SNMPv3 framework. Specifically, the use of the User- 700 based Security Model RFC 2574 [12] and the View-based Access Control 701 Model RFC 2575 [15] is recommended. 703 It is then a customer/user responsibility to ensure that the SNMP entity 704 giving access to this MIB, is properly configured to give access to 705 those objects only to those principals (users) that have legitimate 706 rights to access them. 708 7. Intellectual Property Notice 710 The IETF takes no position regarding the validity or scope of any 711 intellectual property or other rights that might be claimed to pertain 712 to the implementation or use of the technology described in this 713 document or the extent to which any license under such rights might or 714 might not be available; neither does it represent that it has made any 715 effort to identify any such rights. Information on the IETF's 716 procedures with respect to rights in standards-track and standards- 717 related documentation can be found in BCP-11. Copies of claims of 718 rights made available for publication and any assurances of licenses to 719 be made available, or the result of an attempt made to obtain a general 720 license or permission for the use of such proprietary rights by 721 Draft IGMP MIB July 2000 723 implementers or users of this specification can be obtained from the 724 IETF Secretariat. 726 The IETF invites any interested party to bring to its attention any 727 copyrights, patents or patent applications, or other proprietary rights 728 which may cover technology that may be required to practice this 729 standard. Please address the information to the IETF Executive 730 Director. 732 8. Acknowledgements 734 This MIB module was updated based on feedback from the IETF's Inter- 735 Domain Multicast Routing (IDMR) Working Group. 737 9. Authors' Addresses 739 Keith McCloghrie 740 cisco Systems, Inc. 741 170 West Tasman Drive 742 San Jose, CA 95134-1706 743 Phone: +1 408 526 5260 744 EMail: kzm@cisco.com 746 Dino Farinacci 747 cisco Systems, Inc. 748 170 West Tasman Drive 749 San Jose, CA 95134-1706 750 Phone: +1 408 526 4696 751 EMail: dino@cisco.com 753 Dave Thaler 754 Microsoft Corporation 755 One Microsoft Way 756 Redmond, WA 48105-6399 757 Phone: +1 425 703 8835 758 EMail: dthaler@microsoft.com 760 10. References 762 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 763 Describing SNMP Management Frameworks", RFC 2571, Cabletron 765 Draft IGMP MIB July 2000 767 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 768 1999. 770 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 771 Management Information for TCP/IP-based Internets", RFC 1155, STD 772 16, Performance Systems International, Hughes LAN Systems, May 773 1990. 775 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 776 STD 16, Performance Systems International, Hughes LAN Systems, 777 March 1991. 779 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 780 RFC 1215, Performance Systems International, March 1991. 782 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 783 and S. Waldbusser, "Structure of Management Information Version 2 784 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 785 Braunschweig, SNMP Research, First Virtual Holdings, International 786 Network Services, April 1999. 788 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 789 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 790 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 791 Virtual Holdings, International Network Services, April 1999. 793 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 794 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 795 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 796 First Virtual Holdings, International Network Services, April 1999. 798 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 799 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 800 Systems International, Performance Systems International, MIT 801 Laboratory for Computer Science, May 1990. 803 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 804 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 805 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 806 International Network Services, January 1996. 808 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 809 Mappings for Version 2 of the Simple Network Management Protocol 810 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 811 Dover Beach Consulting, Inc., International Network Services, 813 Draft IGMP MIB July 2000 815 January 1996. 817 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 818 Processing and Dispatching for the Simple Network Management 819 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 820 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 822 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 823 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 824 2574, IBM T. J. Watson Research, April 1999. 826 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 827 Operations for Version 2 of the Simple Network Management Protocol 828 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 829 Dover Beach Consulting, Inc., International Network Services, 830 January 1996. 832 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 833 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 834 Systems, April 1999. 836 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 837 Control Model (VACM) for the Simple Network Management Protocol 838 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 839 Cisco Systems, Inc., April 1999. 841 [16] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, STD 842 5, Stanford University, August 1989. 844 [17] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 845 2236, November 1997. 847 11. Full Copyright Statement 849 Copyright (C) The Internet Society (1999). All Rights Reserved. 851 This document and translations of it may be copied and furnished to 852 others, and derivative works that comment on or otherwise explain it or 853 assist in its implmentation may be prepared, copied, published and 854 distributed, in whole or in part, without restriction of any kind, 855 provided that the above copyright notice and this paragraph are included 856 on all such copies and derivative works. However, this document itself 857 may not be modified in any way, such as by removing the copyright notice 858 or references to the Internet Society or other Internet organizations, 859 Draft IGMP MIB July 2000 861 except as needed for the purpose of developing Internet standards in 862 which case the procedures for copyrights defined in the Internet 863 Standards process must be followed, or as required to translate it into 864 languages other than English. 866 The limited permissions granted above are perpetual and will not be 867 revoked by the Internet Society or its successors or assigns. 869 This document and the information contained herein is provided on an "AS 870 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 871 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 872 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 873 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 874 FITNESS FOR A PARTICULAR PURPOSE. 876 Table of Contents 878 1 Abstract ........................................................ 2 879 2 Introduction .................................................... 2 880 3 The SNMP Network Management Framework ........................... 2 881 4 Overview ........................................................ 3 882 5 Definitions ..................................................... 4 883 6 Security Considerations ......................................... 17 884 7 Intellectual Property Notice .................................... 17 885 8 Acknowledgements ................................................ 18 886 9 Authors' Addresses .............................................. 18 887 10 References ..................................................... 18 888 11 Full Copyright Statement ....................................... 20