idnits 2.17.1 draft-ietf-magma-rfc2933-update-00.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 4) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 19 pages 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. ** There is 1 instance of lines with control characters in the document. 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 (June 2002) is 7979 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) -- Looks like a reference, but probably isn't: 'RFC2571' on line 71 == Unused Reference: '2' is defined on line 970, but no explicit reference was found in the text ** 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) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 15 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 J. Chesterfield, 3 Draft Editor 4 Internet Draft AT&T Labs - Research 5 Document: 6 draft-ietf-magma-rfc2933-update-00.txt 7 Expires: December 2002 June 2002 9 Internet Group Management Protocol MIB 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance 14 with all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 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 Abstract 33 This memo defines a portion of the Management Information Base (MIB) 34 for use with network management protocols in the Internet community. 35 In particular, it describes objects used for managing the Internet 36 Group Management Protocol (IGMP). 38 Table of Contents 40 1. Introduction....................................................2 41 2. The SNMP Management Framework...................................2 42 3. Overview........................................................3 43 4. Definitions.....................................................3 44 5. Security Considerations........................................17 45 6. Contributors...................................................17 46 7. Acknowledgements...............................................18 47 8. Author's Addresses.............................................18 48 9. References.....................................................18 49 10. Full Copyright Statement......................................19 51 Internet Group Management Protocol MIB 53 1. Introduction 54 This memo defines a portion of the Management Information Base (MIB) 55 for use with network management protocols in the Internet community. 56 In particular, it describes objects used for managing the Internet 57 Group Management Protocol (IGMP), version 1 [17], version 2 [18] or 58 version 3 [19]. This version of the MIB is an update to rfc2933 59 incorporating IGMPv3 changes to enable "source filtering" in routers 60 and hosts. All of this MIB module is applicable to IPv4 multicast 61 routers; a subset is applicable to hosts implementing IGMP. Since 62 IGMP is specific to IPv4, this MIB does not support management of 63 equivalent functionality for other address families, such as IPv6. 64 Such management may be supported by other MIBs. 66 2. The SNMP Management Framework 68 The SNMP Management Framework presently consists of five major 69 components: 71 . An overall architecture, described in RFC 2571 [RFC2571]. 73 . Mechanisms for describing and naming objects and events for the 74 purpose of management. The first version of this Structure of 75 Management Information (SMI) is called SMIv1 and described in 76 STD 16, RFC 1155 [1], STD 16, RFC 1212 [3] and RFC 1215 [4]. 77 The second version, called SMIv2, is described in STD 58, RFC 78 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 80 . Message protocols for transferring management information. The 81 first version of the SNMP message protocol is called SNMPv1 and 82 described in STD 15, RFC 1157 [8]. A second version of the 83 SNMP message protocol, which is not an Internet standards track 84 protocol, is called SNMPv2c and described in RFC 1901 [9] and 85 RFC 1906 [10]. The third version of the message protocol is 86 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 87 RFC 2574 [12]. 89 . Protocol operations for accessing management information. The 90 first set of protocol operations and associated PDU formats is 91 described in STD 15, RFC 1157 [8]. A second set of protocol 92 operations and associated PDU formats is described in RFC 1905 93 [13]. 95 . A set of fundamental applications described in RFC 2573 [14] 96 and the view-based access control mechanism described in RFC 97 2575 [15]. 99 A more detailed introduction to the current SNMP Management 100 Framework can be found in RFC 2570 [16]. 102 Managed objects are accessed via a virtual information store, termed 103 the Management Information Base or MIB. Objects in the MIB are 104 defined using the mechanisms defined in the SMI. 106 Internet Group Management Protocol MIB 108 This memo specifies a MIB module that is compliant to the SMIv2. A 109 MIB conforming to the SMIv1 can be produced through the appropriate 110 translations. The resulting translated MIB must be semantically 111 equivalent, except where objects or events are omitted because no 112 translation is possible (use of Counter64). Some machine readable 113 information in SMIv2 will be converted into textual descriptions in 114 SMIv1 during the translation process. However, this loss of machine 115 readable information is not considered to change the semantics of 116 the MIB. 118 3. Overview 120 This MIB module contains three tables: 122 1. the IGMP Interface Table which contains one row for each 123 interface on which IGMP is enabled, 125 2. the IGMP Cache Table which contains one row for each IP 126 multicast group for which there are members on a particular 127 interface, and 128 3. the IGMP SrcList Table which contains one row for each entry in 129 the source filter record for an interface and multicast group 130 pair. 132 All tables are intended to be implemented by hosts and routers, but 133 some columnar objects in the first and second tables apply only to 134 routers. 136 4. Definitions 137 IGMP-STD-MIB DEFINITIONS ::= BEGIN 139 IMPORTS 140 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32, 141 Unsigned32, IpAddress, TimeTicks FROM SNMPv2-SMI 142 RowStatus, TruthValue FROM SNMPv2-TC 143 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 144 InterfaceIndexOrZero, 145 InterfaceIndex FROM IF-MIB; 147 igmpStdMIB MODULE-IDENTITY 148 LAST-UPDATED "200206140000Z" -- June 14, 2002 149 ORGANIZATION "IETF MAGMA Working Group." 150 CONTACT-INFO 151 " Dave Thaler 152 Microsoft Corporation 153 One Microsoft Way 154 Redmond, WA 98052-6399 155 US 157 Phone: +1 425 703 8835 158 EMail: dthaler@microsoft.com 160 Internet Group Management Protocol MIB 162 Julian Chesterfield 163 AT&T Research-Labs 164 75 Willow Road 165 Menlo Park, CA 94025 166 US 168 Phone: +1 650 330 7762 169 EMail: julian@research.att.com" 170 DESCRIPTION 171 "The MIB module for IGMP Management." 173 REVISION "200009280000Z" -- September 28, 2000 175 DESCRIPTION 176 "Initial version, published as RFC 2933.? 178 REVISION "200206140000Z" -- June 14, 2002 180 DESCRIPTION 181 "RFC 2933 revised 6/02 to incorporate IGMPv3 changes." 183 ::= { mib-2 85 } 185 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpStdMIB 1 } 187 -- 188 -- The IGMP Interface Table 189 -- 191 igmpInterfaceTable OBJECT-TYPE 192 SYNTAX SEQUENCE OF IgmpInterfaceEntry 193 MAX-ACCESS not-accessible 194 STATUS current 195 DESCRIPTION 196 "The (conceptual) table listing the interfaces on which IGMP 197 is enabled." 198 ::= { igmpMIBObjects 1 } 200 igmpInterfaceEntry OBJECT-TYPE 201 SYNTAX IgmpInterfaceEntry 202 MAX-ACCESS not-accessible 203 STATUS current 204 DESCRIPTION 205 "An entry (conceptual row) representing an interface on 206 which IGMP is enabled." 207 INDEX { igmpInterfaceIfIndex } 208 ::= { igmpInterfaceTable 1 } 210 IgmpInterfaceEntry ::= SEQUENCE { 211 igmpInterfaceIfIndex InterfaceIndex, 212 igmpInterfaceQueryInterval Unsigned32, 213 igmpInterfaceStatus RowStatus, 214 igmpInterfaceVersion Unsigned32, 215 igmpInterfaceQuerier IpAddress, 217 Internet Group Management Protocol MIB 219 igmpInterfaceQueryMaxResponseTime Unsigned32, 220 igmpInterfaceQuerierUpTime TimeTicks, 221 igmpInterfaceQuerierExpiryTime TimeTicks, 222 igmpInterfaceVersion1QuerierTimer TimeTicks, 223 igmpInterfaceWrongVersionQueries Counter32, 224 igmpInterfaceJoins Counter32, 225 igmpInterfaceProxyIfIndex InterfaceIndexOrZero, 226 igmpInterfaceGroups Gauge32, 227 igmpInterfaceRobustness Unsigned32, 228 igmpInterfaceLastMembQueryIntvl Unsigned32, 229 igmpInterfaceVersion2QuerierTimer TimeTicks 230 } 232 igmpInterfaceIfIndex OBJECT-TYPE 233 SYNTAX InterfaceIndex 234 MAX-ACCESS not-accessible 235 STATUS current 236 DESCRIPTION 237 "The ifIndex value of the interface for which IGMP is 238 enabled." 239 ::= { igmpInterfaceEntry 1 } 241 igmpInterfaceQueryInterval OBJECT-TYPE 242 SYNTAX Unsigned32 243 UNITS "seconds" 244 MAX-ACCESS read-create 245 STATUS current 246 DESCRIPTION 247 "The frequency at which IGMP Host-Query packets are 248 transmitted on this interface." 249 DEFVAL { 125 } 250 ::= { igmpInterfaceEntry 2 } 252 igmpInterfaceStatus OBJECT-TYPE 253 SYNTAX RowStatus 254 MAX-ACCESS read-create 255 STATUS current 256 DESCRIPTION 257 "The activation of a row enables IGMP on the interface. The 258 destruction of a row disables IGMP on the interface." 259 ::= { igmpInterfaceEntry 3 } 261 igmpInterfaceVersion OBJECT-TYPE 262 SYNTAX Unsigned32 263 MAX-ACCESS read-create 264 STATUS current 265 DESCRIPTION 266 "The version of IGMP which is running on this interface. 267 This object can be used to configure a router capable of 268 running either value. For IGMP to function correctly, all 269 routers on a LAN must be configured to run the same version 270 of IGMP on that LAN." 271 DEFVAL { 2 } 273 Internet Group Management Protocol MIB 275 ::= { igmpInterfaceEntry 4 } 277 igmpInterfaceQuerier OBJECT-TYPE 278 SYNTAX IpAddress 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The address of the IGMP Querier on the IP subnet to which 283 this interface is attached." 284 ::= { igmpInterfaceEntry 5 } 286 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 287 SYNTAX Unsigned32 (0..255) 288 UNITS "tenths of seconds" 289 MAX-ACCESS read-create 290 STATUS current 291 DESCRIPTION 292 "The maximum query response time advertised in IGMPv2 293 queries on this interface." 294 DEFVAL { 100 } 295 ::= { igmpInterfaceEntry 6 } 297 igmpInterfaceQuerierUpTime OBJECT-TYPE 298 SYNTAX TimeTicks 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The time since igmpInterfaceQuerier was last changed." 303 ::= { igmpInterfaceEntry 7 } 305 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 306 SYNTAX TimeTicks 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The amount of time remaining before the Other Querier 311 Present Timer expires. If the local system is the querier, 312 the value of this object is zero." 313 ::= { igmpInterfaceEntry 8 } 315 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 316 SYNTAX TimeTicks 317 MAX-ACCESS read-only 318 STATUS current 319 DESCRIPTION 320 "The time remaining until the host assumes that there are no 321 IGMPv1 routers present on the interface. While this is non- 322 zero, the host will reply to all queries with version 1 323 membership reports." 324 ::= { igmpInterfaceEntry 9 } 326 igmpInterfaceWrongVersionQueries OBJECT-TYPE 327 SYNTAX Counter32 328 MAX-ACCESS read-only 330 Internet Group Management Protocol MIB 332 STATUS current 333 DESCRIPTION 335 "The number of queries received whose IGMP version does not 336 match igmpInterfaceVersion, over the lifetime of the row 337 entry. IGMP requires that all routers on a LAN be 338 configured to run the same version of IGMP. Thus, if any 339 queries are received with the wrong version, this indicates 340 a configuration error." 341 ::= { igmpInterfaceEntry 10 } 343 igmpInterfaceJoins OBJECT-TYPE 344 SYNTAX Counter32 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "The number of times a group membership has been added on 349 this interface; that is, the number of times an entry for 350 this interface has been added to the Cache Table. This 351 object gives an indication of the amount of IGMP activity 352 over the lifetime of the row entry." 353 ::= { igmpInterfaceEntry 11 } 355 igmpInterfaceProxyIfIndex OBJECT-TYPE 356 SYNTAX InterfaceIndexOrZero 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "Some devices implement a form of IGMP proxying whereby 361 memberships learned on the interface represented by this 362 row, cause IGMP Host Membership Reports to be sent on the 363 interface whose ifIndex value is given by this object. Such 364 a device would implement the igmpV2RouterMIBGroup only on 365 its router interfaces (those interfaces with non-zero 366 igmpInterfaceProxyIfIndex). Typically, the value of this 367 object is 0, indicating that no proxying is being done." 368 DEFVAL { 0 } 369 ::= { igmpInterfaceEntry 12 } 371 igmpInterfaceGroups OBJECT-TYPE 372 SYNTAX Gauge32 373 MAX-ACCESS read-only 374 STATUS current 375 DESCRIPTION 376 "The current number of entries for this interface in the 377 Cache Table." 378 ::= { igmpInterfaceEntry 13 } 380 igmpInterfaceRobustness OBJECT-TYPE 381 SYNTAX Unsigned32 (1..255) 382 MAX-ACCESS read-create 384 STATUS current 385 DESCRIPTION 387 Internet Group Management Protocol MIB 389 "The Robustness Variable allows tuning for the expected 390 packet loss on a subnet. If a subnet is expected to be 391 lossy, the Robustness Variable may be increased. IGMP is 392 robust to (Robustness Variable-1) packet losses." 393 DEFVAL { 2 } 394 ::= { igmpInterfaceEntry 14 } 396 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 397 SYNTAX Unsigned32 (0..255) 398 UNITS "tenths of seconds" 399 MAX-ACCESS read-create 400 STATUS current 401 DESCRIPTION 402 "The Last Member Query Interval is the Max Response Time 403 inserted into Group-Specific Queries sent in response to 404 Leave Group messages, and is also the amount of time between 405 Group-Specific Query messages. This value may be tuned to 406 modify the leave latency of the network. A reduced value 407 results in reduced time to detect the loss of the last 408 member of a group. The value of this object is irrelevant 409 if igmpInterfaceVersion is 1." 410 DEFVAL { 10 } 411 ::= { igmpInterfaceEntry 15 } 413 igmpInterfaceVersion2QuerierTimer OBJECT-TYPE 414 SYNTAX TimeTicks 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The time remaining until the host assumes that there are no 419 IGMPv2 routers present on the interface. While this is non- 420 zero, the host will reply to all queries with version 1 or 2 421 membership reports." 422 ::= { igmpInterfaceEntry 16 } 424 -- 425 -- The IGMP Cache Table 426 -- 428 igmpCacheTable OBJECT-TYPE 429 SYNTAX SEQUENCE OF IgmpCacheEntry 430 MAX-ACCESS not-accessible 431 STATUS current 432 DESCRIPTION 433 "The (conceptual) table listing the IP multicast groups for 434 which there are members on a particular interface." 435 ::= { igmpMIBObjects 2 } 437 igmpCacheEntry OBJECT-TYPE 438 SYNTAX IgmpCacheEntry 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION 442 "An entry (conceptual row) in the igmpCacheTable." 444 Internet Group Management Protocol MIB 446 INDEX { igmpCacheAddress, igmpCacheIfIndex } 447 ::= { igmpCacheTable 1 } 449 IgmpCacheEntry ::= SEQUENCE { 450 igmpCacheAddress IpAddress, 451 igmpCacheIfIndex InterfaceIndex, 452 igmpCacheSelf TruthValue, 453 igmpCacheLastReporter IpAddress, 454 igmpCacheUpTime TimeTicks, 455 igmpCacheExpiryTime TimeTicks, 456 igmpCacheStatus RowStatus, 457 igmpCacheVersion1HostTimer TimeTicks, 458 igmpCacheVersion2HostTimer TimeTicks, 459 igmpCacheSourceFilterMode Integer32 460 } 462 igmpCacheAddress OBJECT-TYPE 463 SYNTAX IpAddress 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "The IP multicast group address for which this entry 468 contains information." 469 ::= { igmpCacheEntry 1 } 471 igmpCacheIfIndex OBJECT-TYPE 472 SYNTAX InterfaceIndex 473 MAX-ACCESS not-accessible 474 STATUS current 475 DESCRIPTION 476 "The interface for which this entry contains information for 477 an IP multicast group address." 478 ::= { igmpCacheEntry 2 } 480 igmpCacheSelf OBJECT-TYPE 481 SYNTAX TruthValue 482 MAX-ACCESS read-create 483 STATUS current 484 DESCRIPTION 485 "An indication of whether the local system is a member of 486 this group address on this interface." 487 DEFVAL { true } 488 ::= { igmpCacheEntry 3 } 490 igmpCacheLastReporter OBJECT-TYPE 491 SYNTAX IpAddress 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The IP address of the source of the last membership report 496 received for this IP Multicast group address on this 497 interface. If no membership report has been received, this 498 object has the value 0.0.0.0." 500 Internet Group Management Protocol MIB 502 ::= { igmpCacheEntry 4 } 504 igmpCacheUpTime OBJECT-TYPE 505 SYNTAX TimeTicks 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "The time elapsed since this entry was created." 510 ::= { igmpCacheEntry 5 } 512 igmpCacheExpiryTime OBJECT-TYPE 513 SYNTAX TimeTicks 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "The minimum amount of time remaining before this entry will 518 be aged out. A value of 0 indicates that the entry is only 519 present because igmpCacheSelf is true and that if the router 520 left the group, this entry would be aged out immediately. 521 Note that some implementations may process membership 522 reports from the local system in the same way as reports 523 from other hosts, so a value of 0 is not required." 524 ::= { igmpCacheEntry 6 } 526 igmpCacheStatus OBJECT-TYPE 527 SYNTAX RowStatus 528 MAX-ACCESS read-create 529 STATUS current 530 DESCRIPTION 531 "The status of this entry." 532 ::= { igmpCacheEntry 7 } 534 igmpCacheVersion1HostTimer OBJECT-TYPE 535 SYNTAX TimeTicks 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The time remaining until the local router will assume that 540 there are no longer any IGMP version 1 members on the IP 541 subnet attached to this interface. Upon hearing any IGMPv1 542 Membership Report, this value is reset to the group 543 membership timer. While this time remaining is non-zero, 544 the local router ignores any IGMPv2 Leave messages for this 545 group that it receives on this interface." 546 ::= { igmpCacheEntry 8 } 548 igmpCacheVersion2HostTimer OBJECT-TYPE 549 SYNTAX TimeTicks 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The time remaining until the local router will assume that 554 there are no longer any IGMP version 2 members on the IP 556 Internet Group Management Protocol MIB 558 subnet attached to this interface. Upon hearing any IGMPv2 559 Membership Report, this value is reset to the group 560 membership timer." 561 ::= { igmpCacheEntry 9 } 563 igmpCacheSourceFilterMode OBJECT-TYPE 564 SYNTAX Integer32 {include (1), 565 exclude (2) } 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "The state in which the interface is currently set. The 570 value indicates the relevance of the corresponding source 571 list entries in the SrcList Table for IGMPv3 interfaces." 572 ::= { igmpCacheEntry 10 } 574 -- 575 -- The IGMP Source list Table 576 -- 578 igmpSrcListTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF IgmpSrcListEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "The (conceptual) table listing the Source List entries 584 corresponding to each Interface filter mode record." 585 ::= { igmpMIBObjects 3 } 587 igmpSrcListEntry OBJECT-TYPE 588 SYNTAX IgmpSrcListEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "An entry (conceptual row) in the igmpSrcListTable." 593 INDEX { igmpSrcListAddress, igmpSrcListIfIndex, 594 igmpSrcListHostAddress } 595 ::= { igmpSrcListTable 1 } 597 IgmpSrcListEntry ::= SEQUENCE { 598 igmpSrcListAddress IpAddress, 599 igmpSrcListIfIndex InterfaceIndex, 600 igmpSrcListHostAddress IpAddress, 601 igmpSrcListStatus RowStatus 602 } 604 igmpSrcListAddress OBJECT-TYPE 605 SYNTAX IpAddress 606 MAX-ACCESS not-accessible 607 STATUS current 609 Internet Group Management Protocol MIB 611 DESCRIPTION 612 "The IP multicast group address for which this entry 613 contains information." 614 ::= { igmpSrcListEntry 1 } 616 igmpSrcListIfIndex OBJECT-TYPE 617 SYNTAX InterfaceIndex 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "The interface for which this entry contains information for 622 an IP multicast group address." 623 ::= { igmpSrcListEntry 2 } 625 igmpSrcListHostAddress OBJECT-TYPE 626 SYNTAX IpAddress 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "The host address to which this entry 631 corresponds. The CacheSourceFilterMode value for this Group 632 address and interface indicates whether this Host address 633 is included or excluded." 634 ::= { igmpSrcListEntry 3 } 636 igmpSrcListStatus OBJECT-TYPE 637 SYNTAX RowStatus 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "The status of this entry." 642 ::= { igmpSrcListEntry 4 } 644 -- conformance information 646 igmpMIBConformance 647 OBJECT IDENTIFIER ::= { igmpStdMIB 2 } 648 igmpMIBCompliances 649 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 650 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 652 -- compliance statements 654 igmpV1HostMIBCompliance MODULE-COMPLIANCE 655 STATUS current 656 DESCRIPTION 657 "The compliance statement for hosts running IGMPv1 and 658 implementing the IGMP MIB." 659 MODULE -- this module 660 MANDATORY-GROUPS { igmpBaseMIBGroup } 662 OBJECT igmpInterfaceStatus 664 Internet Group Management Protocol MIB 666 MIN-ACCESS read-only 667 DESCRIPTION 668 "Write access is not required." 670 OBJECT igmpCacheStatus 671 MIN-ACCESS read-only 672 DESCRIPTION 673 "Write access is not required." 675 ::= { igmpMIBCompliances 1 } 677 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 678 STATUS current 679 DESCRIPTION 680 "The compliance statement for routers running IGMPv1 and 681 implementing the IGMP MIB." 682 MODULE -- this module 683 MANDATORY-GROUPS { igmpBaseMIBGroup, 684 igmpRouterMIBGroup 685 } 687 OBJECT igmpInterfaceStatus 688 MIN-ACCESS read-only 689 DESCRIPTION 690 "Write access is not required." 691 OBJECT igmpCacheStatus 692 MIN-ACCESS read-only 693 DESCRIPTION 694 "Write access is not required." 696 ::= { igmpMIBCompliances 2 } 698 igmpV2HostMIBCompliance MODULE-COMPLIANCE 699 STATUS current 700 DESCRIPTION 701 "The compliance statement for hosts running IGMPv2 and 702 implementing the IGMP MIB." 703 MODULE -- this module 704 MANDATORY-GROUPS { igmpBaseMIBGroup, 705 igmpV2HostMIBGroup 706 } 708 OBJECT igmpInterfaceStatus 709 MIN-ACCESS read-only 710 DESCRIPTION 711 "Write access is not required." 713 OBJECT igmpCacheStatus 714 MIN-ACCESS read-only 715 DESCRIPTION 716 "Write access is not required." 718 ::= { igmpMIBCompliances 3 } 720 Internet Group Management Protocol MIB 722 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 723 STATUS current 724 DESCRIPTION 725 "The compliance statement for routers running IGMPv2 and 726 implementing the IGMP MIB." 727 MODULE -- this module 728 MANDATORY-GROUPS { igmpBaseMIBGroup, 729 igmpRouterMIBGroup, 730 igmpV2RouterMIBGroup 731 } 733 OBJECT igmpInterfaceStatus 734 MIN-ACCESS read-only 735 DESCRIPTION 736 "Write access is not required." 737 OBJECT igmpCacheStatus 738 MIN-ACCESS read-only 739 DESCRIPTION 740 "Write access is not required." 742 ::= { igmpMIBCompliances 4 } 744 igmpV3HostMIBCompliance MODULE-COMPLIANCE 745 STATUS current 746 DESCRIPTION 747 "The compliance statement for hosts running IGMPv3 and 748 implementing the IGMP MIB." 749 MODULE -- this module 750 MANDATORY-GROUPS { igmpBaseMIBGroup, 751 igmpV2HostMIBGroup, 752 igmpV3HostMIBGroup 753 } 755 OBJECT igmpInterfaceStatus 756 MIN-ACCESS read-only 757 DESCRIPTION 758 "Write access is not required." 760 OBJECT igmpCacheStatus 761 MIN-ACCESS read-only 762 DESCRIPTION 763 "Write access is not required." 765 ::= { igmpMIBCompliances 5 } 767 igmpV3RouterMIBCompliance MODULE-COMPLIANCE 768 STATUS current 769 DESCRIPTION 770 "The compliance statement for routers running IGMPv3 and 771 implementing the IGMP MIB." 772 MODULE -- this module 773 MANDATORY-GROUPS { igmpBaseMIBGroup, 774 igmpRouterMIBGroup, 775 igmpV2RouterMIBGroup, 777 Internet Group Management Protocol MIB 779 igmpV3RouterMIBGroup 780 } 782 OBJECT igmpInterfaceStatus 783 MIN-ACCESS read-only 784 DESCRIPTION 785 "Write access is not required." 786 OBJECT igmpCacheStatus 787 MIN-ACCESS read-only 788 DESCRIPTION 789 "Write access is not required." 791 ::= { igmpMIBCompliances 6 } 793 -- units of conformance 795 igmpBaseMIBGroup OBJECT-GROUP 796 OBJECTS { igmpCacheSelf, 797 igmpCacheStatus, igmpInterfaceStatus 798 } 799 STATUS current 800 DESCRIPTION 801 "The basic collection of objects providing management of 802 IGMP version 1, 2 or 3." 803 ::= { igmpMIBGroups 1 } 805 igmpRouterMIBGroup OBJECT-GROUP 806 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 807 igmpInterfaceJoins, igmpInterfaceGroups, 808 igmpCacheLastReporter, igmpInterfaceQuerierUpTime, 809 igmpInterfaceQuerierExpiryTime, 810 igmpInterfaceQueryInterval 811 } 812 STATUS current 813 DESCRIPTION 814 "A collection of additional objects for management of IGMP 815 version 1, 2 or 3 in routers." 816 ::= { igmpMIBGroups 2 } 818 igmpV2HostMIBGroup OBJECT-GROUP 819 OBJECTS { igmpInterfaceVersion1QuerierTimer } 820 STATUS current 821 DESCRIPTION 822 "A collection of additional objects for management of IGMP 823 version 2 in hosts." 824 ::= { igmpMIBGroups 3 } 826 igmpHostOptMIBGroup OBJECT-GROUP 827 OBJECTS { igmpCacheLastReporter, igmpInterfaceQuerier } 828 STATUS current 829 DESCRIPTION 830 "A collection of optional objects for IGMP hosts. 832 Internet Group Management Protocol MIB 834 Supporting this group can be especially useful in an 835 environment with a router which does not support the IGMP 836 MIB." 837 ::= { igmpMIBGroups 4 } 839 igmpV2RouterMIBGroup OBJECT-GROUP 840 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 841 igmpInterfaceQueryMaxResponseTime, 842 igmpInterfaceRobustness, 843 igmpInterfaceWrongVersionQueries, 844 igmpInterfaceLastMembQueryIntvl, 845 igmpCacheVersion1HostTimer 846 } 847 STATUS current 848 DESCRIPTION 849 "A collection of additional objects for management of IGMP 850 version 2 in routers." 851 ::= { igmpMIBGroups 5 } 853 igmpV2ProxyMIBGroup OBJECT-GROUP 854 OBJECTS { igmpInterfaceProxyIfIndex } 855 STATUS current 856 DESCRIPTION 857 "A collection of additional objects for management of IGMP 858 proxy devices." 859 ::= { igmpMIBGroups 6 } 861 igmpV3HostMIBGroup OBJECT-GROUP 862 OBJECTS { igmpCacheSourceFilterMode, 863 igmpInterfaceVersion2QuerierTimer, 864 igmpSrcListAddress, 865 igmpSrcListIfIndex, 866 igmpSrcListHostAddress 867 } 868 STATUS current 869 DESCRIPTION 870 "A collection of additional objects for management of IGMP 871 version 3 in hosts." 872 ::= { igmpMIBGroups 7 } 874 igmpV3RouterMIBGroup OBJECT-GROUP 875 OBJECTS { igmpCacheSourceFilterMode, 876 igmpCacheVersion2HostTimer, 877 igmpSrcListAddress, 878 igmpSrcListIfIndex, 879 igmpSrcListHostAddress 880 } 881 STATUS current 882 DESCRIPTION 883 "A collection of additional objects for management of IGMP 884 version 3 in routers." 885 ::= { igmpMIBGroups 8 } 887 END 889 Internet Group Management Protocol MIB 891 5. Security Considerations 893 This MIB contains readable objects whose values provide information 894 related to multicast sessions. Some of these objects could contain 895 sensitive information. In particular, the igmpCacheSelf and 896 igmpCacheLastReporter can be used to identify machines which are 897 listening to a given group address. There are also a number of 898 objects that have a MAX-ACCESS clause of read-write and/or read- 899 create, which allow an administrator to configure IGMP in the 900 router. 902 While unauthorized access to the readable objects is relatively 903 innocuous, unauthorized access to the write-able objects could cause 904 a denial of service. Hence, the support for SET operations in a 905 non-secure environment without proper protection can have a negative 906 effect on network operations. 908 SNMPv1 by itself is such an insecure environment. Even if the 909 network itself is secure (for example by using IPSec), even then, 910 there is no control as to who on the secure network is allowed to 911 access and SET (change/create/delete) the objects in this MIB. 913 It is recommended that the implementers consider the security 914 features as provided by the SNMPv3 framework. Specifically, the use 915 of the User-based Security Model RFC 2574 [12] and the View-based 916 Access Control Model RFC 2575 [15] is recommended. 918 It is then a customer/user responsibility to ensure that the SNMP 919 entity giving access to this MIB, is properly configured to give 920 access to those objects only to those principals (users) that have 921 legitimate rights to access them. 923 6. Contributors 925 The authors of RFC 2933 from which this document is derived are: 927 Keith McCloghrie 928 cisco Systems, Inc. 929 170 West Tasman Drive 930 San Jose, CA 95134-1706 932 Phone: +1 408 526 5260 933 EMail: kzm@cisco.com 935 Dino Farinacci 936 Procket Networks 937 3850 North First Street 938 San Jose, CA 95134 940 Phone: +1 408-954-7909 941 Email: dino@procket.com 943 Internet Group Management Protocol MIB 945 Dave Thaler 946 Microsoft Corporation 947 One Microsoft Way 948 Redmond, WA 48105-6399 950 Phone: +1 425 703 8835 951 EMail: dthaler@microsoft.com 953 7. Acknowledgements 955 Thanks to Bill Fenner for feedback and suggestions regarding the MIB. 957 8. Author's Address 959 Julian Chesterfield 960 AT&T Labs - Research 961 75 Willow Road 962 Menlo Park 963 CA, 94301 965 9. References 967 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 968 Describing SNMP Management Frameworks", RFC 2571, April 1999. 970 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 971 Management Information for TCP/IP-based Internets", STD 16, RFC 972 1155, May 1990. 974 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 975 RFC 1212, March 1991. 977 [4] M. Rose, "A Convention for Defining Traps for use with the 978 SNMP", RFC 1215, March 1991. 980 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 981 M., and S. Waldbusser, "Structure of Management Information 982 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 984 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 985 M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 986 RFC 2579, April 1999. 988 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 989 M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 990 58, RFC 2580, April 1999. 992 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 993 Network Management Protocol", STD 15, RFC 1157, May 1990. 995 Internet Group Management Protocol MIB 997 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 998 "Introduction to Community-based SNMPv2", RFC 1901, January 999 1996. 1001 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1002 "Transport Mappings for Version 2 of the Simple Network 1003 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1005 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1006 Processing and Dispatching for the Simple Network Management 1007 Protocol (SNMP)", RFC 2572, April 1999. 1009 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1010 for version 3 of the Simple Network Management Protocol 1011 (SNMPv3)", RFC 2574, April 1999. 1013 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1014 Operations for Version 2 of the Simple Network Management 1015 Protocol (SNMPv2)", RFC 1905, January 1996. 1017 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1018 2573, April 1999. 1020 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1021 Control Model (VACM) for the Simple Network Management Protocol 1022 (SNMP)", RFC 2575, April 1999. 1024 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction 1025 to Version 3 of the Internet-standard Network Management 1026 Framework", RFC 2570, April 1999. 1028 [17] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1029 1112, August 1989. 1031 [18] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 1032 2236, November 1997. 1034 [19] Cain, B., Deering, S., Fenner, W., Kouvelas, I., Thyagarajan, 1035 A., ?Internet Group Management Protocol, Version 3?, , May 2002. 1038 10. Full Copyright Statement 1040 Copyright (C) The Internet Society (2000). All Rights Reserved. 1042 This document and translations of it may be copied and furnished to 1043 others, and derivative works that comment on or otherwise explain it 1044 or assist in its implementation may be prepared, copied, published 1045 and distributed, in whole or in part, without restriction of any 1046 kind, provided that the above copyright notice and this paragraph 1047 are included on all such copies and derivative works. However, this 1048 document itself may not be modified in any way, such as by removing 1049 the copyright notice or references to the Internet Society or other 1051 Internet Group Management Protocol MIB 1053 Internet organizations, except as needed for the purpose of 1054 developing Internet standards in which case the procedures for 1055 copyrights defined in the Internet languages other than English. 1057 The limited permissions granted above are perpetual and will not be 1058 revoked by the Internet Society or its successors or assigns. 1060 This document and the information contained herein is provided on an 1061 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1062 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1063 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1064 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1065 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."