idnits 2.17.1 draft-ietf-idmr-igmp-mib-11.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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 79 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 21 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. 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 (17 September 1999) is 8982 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) -- Possible downref: Non-RFC (?) normative reference: ref. '15' Summary: 13 errors (**), 0 flaws (~~), 4 warnings (==), 3 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 March 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 17 September 1999 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 (1999). All Rights Reserved. 35 Draft IGMP MIB September 1999 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]. All of 50 this MIB module is applicable to IP multicast routers; a subset is 51 applicable to hosts implementing IGMP. 53 3. The SNMP Network Management Framework 55 The SNMP Management Framework presently consists of five major 56 components: 58 o An overall architecture, described in RFC 2571 [1]. 60 o Mechanisms for describing and naming objects and events for the 61 purpose of management. The first version of this Structure of 62 Management Information (SMI) is called SMIv1 and described in RFC 63 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 64 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 66 o Message protocols for transferring management information. The 67 first version of the SNMP message protocol is called SNMPv1 and 68 described in RFC 1157 [8]. A second version of the SNMP message 69 protocol, which is not an Internet standards track protocol, is 70 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 71 The third version of the message protocol is called SNMPv3 and 72 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 74 o Protocol operations for accessing management information. The first 75 set of protocol operations and associated PDU formats is described 76 in RFC 1157 [8]. A second set of protocol operations and associated 77 PDU formats is described in RFC 1905 [13]. 79 Draft IGMP MIB September 1999 81 o A set of fundamental applications described in RFC 2573 [14] and 82 the view-based access control mechanism described in RFC 2575 [15]. 84 Managed objects are accessed via a virtual information store, termed the 85 Management Information Base or MIB. Objects in the MIB are defined 86 using the mechanisms defined in the SMI. 88 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 89 conforming to the SMIv1 can be produced through the appropriate 90 translations. The resulting translated MIB must be semantically 91 equivalent, except where objects or events are omitted because no 92 translation is possible (use of Counter64). Some machine readable 93 information in SMIv2 will be converted into textual descriptions in 94 SMIv1 during the translation process. However, this loss of machine 95 readable information is not considered to change the semantics of the 96 MIB. 98 3.1. Object Definitions 100 Managed objects are accessed via a virtual information store, termed the 101 Management Information Base or MIB. Objects in the MIB are defined 102 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 103 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 104 an administratively assigned name. The object type together with an 105 object instance serves to uniquely identify a specific instantiation of 106 the object. For human convenience, we often use a textual string, 107 termed the descriptor, to refer to the object type. 109 4. Overview 111 This MIB module contains two tables: 113 (1) the IGMP Interface Table which contains one row for each 114 interface on which IGMP is enabled, and 116 (2) the IGMP Cache Table which contains one row for each IP multicast 117 group for which there are members on a particular interface. 119 Both tables are intended to be implemented by hosts and routers, but 120 some columnar objects in each table apply only to routers. 122 Draft IGMP MIB September 1999 124 5. Definitions 126 IGMP-STD-MIB DEFINITIONS ::= BEGIN 128 IMPORTS 129 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32, 130 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 131 RowStatus, TruthValue FROM SNMPv2-TC 132 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 133 InterfaceIndexOrZero, 134 InterfaceIndex FROM IF-MIB; 136 igmpStdMIB MODULE-IDENTITY 137 LAST-UPDATED "9909171200Z" -- September 17, 1999 138 ORGANIZATION "IETF IDMR Working Group." 139 CONTACT-INFO 140 " Dave Thaler 141 Microsoft Corporation 142 One Microsoft Way 143 Redmond, WA 98052-6399 144 US 146 Phone: +1 425 703 8835 147 EMail: dthaler@dthaler.microsoft.com" 148 DESCRIPTION 149 "The MIB module for IGMP Management." 150 REVISION "9909171200Z" -- September 17, 1999 151 DESCRIPTION 152 "Initial version, published as RFC xxxx (to be filled in by 153 RFC-Editor)." 154 ::= { mib-2 xx } 155 -- NOTE TO RFC EDITOR: When this document is published as 156 -- an RFC, replace XX with IANA-assigned value and delete 157 -- this comment. 159 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpStdMIB 1 } 161 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 163 Draft IGMP MIB September 1999 165 -- 166 -- The IGMP Interface Table 167 -- 169 igmpInterfaceTable OBJECT-TYPE 170 SYNTAX SEQUENCE OF IgmpInterfaceEntry 171 MAX-ACCESS not-accessible 172 STATUS current 173 DESCRIPTION 174 "The (conceptual) table listing the interfaces on which IGMP 175 is enabled." 176 ::= { igmp 1 } 178 igmpInterfaceEntry OBJECT-TYPE 179 SYNTAX IgmpInterfaceEntry 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "An entry (conceptual row) representing an interface on 184 which IGMP is enabled." 185 INDEX { igmpInterfaceIfIndex } 186 ::= { igmpInterfaceTable 1 } 188 IgmpInterfaceEntry ::= SEQUENCE { 189 igmpInterfaceIfIndex InterfaceIndex, 190 igmpInterfaceQueryInterval Integer32, 191 igmpInterfaceStatus RowStatus, 192 igmpInterfaceVersion INTEGER, 193 igmpInterfaceQuerier IpAddress, 194 igmpInterfaceQueryMaxResponseTime Integer32, 195 igmpInterfaceVersion1QuerierTimer TimeTicks, 196 igmpInterfaceWrongVersionQueries Counter32, 197 igmpInterfaceJoins Counter32, 198 igmpInterfaceGroups Gauge32, 199 igmpInterfaceRobustness Integer32, 200 igmpInterfaceLastMembQueryIntvl Integer32, 201 igmpInterfaceProxyIfIndex InterfaceIndexOrZero, 202 igmpInterfaceQuerierUpTime TimeTicks, 203 igmpInterfaceQuerierExpiryTime TimeTicks 204 } 206 igmpInterfaceIfIndex OBJECT-TYPE 207 SYNTAX InterfaceIndex 208 MAX-ACCESS not-accessible 209 STATUS current 211 Draft IGMP MIB September 1999 213 DESCRIPTION 214 "The ifIndex value of the interface for which IGMP is 215 enabled." 216 ::= { igmpInterfaceEntry 1 } 218 igmpInterfaceQueryInterval OBJECT-TYPE 219 SYNTAX Integer32 220 UNITS "seconds" 221 MAX-ACCESS read-create 222 STATUS current 223 DESCRIPTION 224 "The frequency at which IGMP Host-Query packets are 225 transmitted on this interface." 226 DEFVAL { 125 } 227 ::= { igmpInterfaceEntry 2 } 229 igmpInterfaceStatus OBJECT-TYPE 230 SYNTAX RowStatus 231 MAX-ACCESS read-create 232 STATUS current 233 DESCRIPTION 234 "The activation of a row enables IGMP on the interface. The 235 destruction of a row disables IGMP on the interface." 236 ::= { igmpInterfaceEntry 3 } 238 igmpInterfaceVersion OBJECT-TYPE 239 SYNTAX INTEGER { version1(1), version2(2) } 240 MAX-ACCESS read-create 241 STATUS current 242 DESCRIPTION 243 "The version of IGMP which is running on this interface. 244 This object can be used to configure a router capable of 245 running either value. For IGMP to function correctly, all 246 routers on a LAN must be configured to run the same version 247 of IGMP on that LAN." 248 DEFVAL { version2 } 249 ::= { igmpInterfaceEntry 4 } 251 igmpInterfaceQuerier OBJECT-TYPE 252 SYNTAX IpAddress 253 MAX-ACCESS read-only 254 STATUS current 255 DESCRIPTION 256 "The address of the IGMP Querier on the IP subnet to which 257 this interface is attached." 259 Draft IGMP MIB September 1999 261 ::= { igmpInterfaceEntry 5 } 263 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 264 SYNTAX Integer32 265 UNITS "tenths of seconds" 266 MAX-ACCESS read-create 267 STATUS current 268 DESCRIPTION 269 "The maximum query response time advertised in IGMPv2 270 queries on this interface." 271 DEFVAL { 100 } 272 ::= { igmpInterfaceEntry 6 } 274 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 275 SYNTAX TimeTicks 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The time remaining until the host assumes that there are no 280 IGMPv1 routers present on the interface. While this is non- 281 zero, the host will reply to all queries with version 1 282 membership reports." 283 ::= { igmpInterfaceEntry 9 } 285 igmpInterfaceWrongVersionQueries OBJECT-TYPE 286 SYNTAX Counter32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of queries received whose IGMP version does not 291 match igmpInterfaceVersion. IGMP requires that all routers 292 on a LAN be configured to run the same version of IGMP. 293 Thus, if any queries are received with the wrong version, 294 this indicates a configuration error." 295 ::= { igmpInterfaceEntry 10 } 297 igmpInterfaceJoins OBJECT-TYPE 298 SYNTAX Counter32 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The number of times a group membership has been added on 303 this interface; that is, the number of times an entry for 304 this interface has been added to the Cache Table. This 305 object gives an indication of the amount of IGMP activity 307 Draft IGMP MIB September 1999 309 over time." 310 ::= { igmpInterfaceEntry 11 } 312 igmpInterfaceGroups OBJECT-TYPE 313 SYNTAX Gauge32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The current number of entries for this interface in the 318 Cache Table." 319 ::= { igmpInterfaceEntry 13 } 321 igmpInterfaceRobustness OBJECT-TYPE 322 SYNTAX Integer32 323 MAX-ACCESS read-create 324 STATUS current 325 DESCRIPTION 326 "The Robustness Variable allows tuning for the expected 327 packet loss on a subnet. If a subnet is expected to be 328 lossy, the Robustness Variable may be increased. IGMP is 329 robust to (Robustness Variable-1) packet losses." 330 DEFVAL { 2 } 331 ::= { igmpInterfaceEntry 14 } 333 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 334 SYNTAX Integer32 335 UNITS "tenths of seconds" 336 MAX-ACCESS read-create 337 STATUS current 338 DESCRIPTION 339 "The Last Member Query Interval is the Max Response Time 340 inserted into Group-Specific Queries sent in response to 341 Leave Group messages, and is also the amount of time between 342 Group-Specific Query messages. This value may be tuned to 343 modify the leave latency of the network. A reduced value 344 results in reduced time to detect the loss of the last 345 member of a group. The value of this object is irrelevant 346 if igmpInterfaceVersion is version1." 347 DEFVAL { 10 } 348 ::= { igmpInterfaceEntry 15 } 350 igmpInterfaceProxyIfIndex OBJECT-TYPE 351 SYNTAX InterfaceIndexOrZero 352 MAX-ACCESS read-create 353 STATUS current 355 Draft IGMP MIB September 1999 357 DESCRIPTION 358 "Some devices implement a form of IGMP proxying whereby 359 memberships learned on the interface represented by this 360 row, cause IGMP Host Membership Reports to be sent on the 361 interface whose ifIndex value is given by this object. Such 362 a device would implement the igmpV2RouterMIBGroup only on 363 its router interfaces (those interfaces with non-zero 364 igmpInterfaceProxyIfIndex). Typically, the value of this 365 object is 0, indicating that no proxying is being done." 366 DEFVAL { 0 } 367 ::= { igmpInterfaceEntry 16 } 369 igmpInterfaceQuerierUpTime OBJECT-TYPE 370 SYNTAX TimeTicks 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The time since igmpInterfaceQuerier was last changed." 375 ::= { igmpInterfaceEntry 17 } 377 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 378 SYNTAX TimeTicks 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The amount of time remaining before the Other Querier 383 Present Timer expires. If the local system is the querier, 384 the value of this object is zero." 385 ::= { igmpInterfaceEntry 18 } 387 Draft IGMP MIB September 1999 389 -- 390 -- The IGMP Cache Table 391 -- 393 igmpCacheTable OBJECT-TYPE 394 SYNTAX SEQUENCE OF IgmpCacheEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "The (conceptual) table listing the IP multicast groups for 399 which there are members on a particular interface." 400 ::= { igmp 2 } 402 igmpCacheEntry OBJECT-TYPE 403 SYNTAX IgmpCacheEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "An entry (conceptual row) in the igmpCacheTable." 408 INDEX { igmpCacheAddress, igmpCacheIfIndex } 409 ::= { igmpCacheTable 1 } 411 IgmpCacheEntry ::= SEQUENCE { 412 igmpCacheAddress IpAddress, 413 igmpCacheIfIndex InterfaceIndex, 414 igmpCacheSelf TruthValue, 415 igmpCacheLastReporter IpAddress, 416 igmpCacheUpTime TimeTicks, 417 igmpCacheExpiryTime TimeTicks, 418 igmpCacheStatus RowStatus, 419 igmpCacheVersion1HostTimer TimeTicks 420 } 422 igmpCacheAddress OBJECT-TYPE 423 SYNTAX IpAddress 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "The IP multicast group address for which this entry 428 contains information." 429 ::= { igmpCacheEntry 1 } 431 igmpCacheIfIndex OBJECT-TYPE 432 SYNTAX InterfaceIndex 433 MAX-ACCESS not-accessible 435 Draft IGMP MIB September 1999 437 STATUS current 438 DESCRIPTION 439 "The interface for which this entry contains information for 440 an IP multicast group address." 441 ::= { igmpCacheEntry 2 } 443 igmpCacheSelf OBJECT-TYPE 444 SYNTAX TruthValue 445 MAX-ACCESS read-create 446 STATUS current 447 DESCRIPTION 448 "An indication of whether the local system is a member of 449 this group address on this interface." 450 DEFVAL { true } 451 ::= { igmpCacheEntry 3 } 453 igmpCacheLastReporter OBJECT-TYPE 454 SYNTAX IpAddress 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The IP address of the source of the last membership report 459 received for this IP Multicast group address on this 460 interface. If no membership report has been received, this 461 object has the value 0.0.0.0." 462 ::= { igmpCacheEntry 4 } 464 igmpCacheUpTime OBJECT-TYPE 465 SYNTAX TimeTicks 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The time elapsed since this entry was created." 470 ::= { igmpCacheEntry 5 } 472 igmpCacheExpiryTime OBJECT-TYPE 473 SYNTAX TimeTicks 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The minimum amount of time remaining before this entry will 478 be aged out. A value of 0 indicates that the entry is only 479 present because igmpCacheSelf is true and that if the router 480 left the group, this entry would be aged out immediately. 481 Note that some implementations may process membership 483 Draft IGMP MIB September 1999 485 reports from the local system in the same way as reports 486 from other hosts, so a value of 0 is not required." 487 ::= { igmpCacheEntry 6 } 489 igmpCacheStatus OBJECT-TYPE 490 SYNTAX RowStatus 491 MAX-ACCESS read-create 492 STATUS current 493 DESCRIPTION 494 "The status of this entry." 495 ::= { igmpCacheEntry 7 } 497 igmpCacheVersion1HostTimer OBJECT-TYPE 498 SYNTAX TimeTicks 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "The time remaining until the local router will assume that 503 there are no longer any IGMP version 1 members on the IP 504 subnet attached to this interface. Upon hearing any IGMPv1 505 Membership Report, this value is reset to the group 506 membership timer. While this time remaining is non-zero, 507 the local router ignores any IGMPv2 Leave messages for this 508 group that it receives on this interface." 509 ::= { igmpCacheEntry 8 } 511 Draft IGMP MIB September 1999 513 -- conformance information 515 igmpMIBConformance 516 OBJECT IDENTIFIER ::= { igmpStdMIB 2 } 517 igmpMIBCompliances 518 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 519 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 521 -- compliance statements 523 igmpV1HostMIBCompliance MODULE-COMPLIANCE 524 STATUS current 525 DESCRIPTION 526 "The compliance statement for hosts running IGMPv1 and 527 implementing the IGMP MIB." 528 MODULE -- this module 529 MANDATORY-GROUPS { igmpBaseMIBGroup } 531 OBJECT igmpInterfaceStatus 532 MIN-ACCESS read-only 533 DESCRIPTION 534 "Write access is not required." 536 ::= { igmpMIBCompliances 1 } 538 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 539 STATUS current 540 DESCRIPTION 541 "The compliance statement for routers running IGMPv1 and 542 implementing the IGMP MIB." 543 MODULE -- this module 544 MANDATORY-GROUPS { igmpBaseMIBGroup, 545 igmpRouterMIBGroup 546 } 548 OBJECT igmpInterfaceStatus 549 MIN-ACCESS read-only 550 DESCRIPTION 551 "Write access is not required." 553 ::= { igmpMIBCompliances 2 } 555 igmpV2HostMIBCompliance MODULE-COMPLIANCE 556 STATUS current 558 Draft IGMP MIB September 1999 560 DESCRIPTION 561 "The compliance statement for hosts running IGMPv2 and 562 implementing the IGMP MIB." 563 MODULE -- this module 564 MANDATORY-GROUPS { igmpBaseMIBGroup, 565 igmpV2HostMIBGroup 566 } 568 OBJECT igmpInterfaceStatus 569 MIN-ACCESS read-only 570 DESCRIPTION 571 "Write access is not required." 573 ::= { igmpMIBCompliances 3 } 575 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 576 STATUS current 577 DESCRIPTION 578 "The compliance statement for routers running IGMPv2 and 579 implementing the IGMP MIB." 580 MODULE -- this module 581 MANDATORY-GROUPS { igmpBaseMIBGroup, 582 igmpRouterMIBGroup, 583 igmpV2RouterMIBGroup 584 } 586 OBJECT igmpInterfaceStatus 587 MIN-ACCESS read-only 588 DESCRIPTION 589 "Write access is not required." 591 ::= { igmpMIBCompliances 4 } 593 -- units of conformance 595 igmpBaseMIBGroup OBJECT-GROUP 596 OBJECTS { igmpCacheSelf, 597 igmpCacheStatus, igmpInterfaceStatus 598 } 599 STATUS current 600 DESCRIPTION 601 "The basic collection of objects providing management of 602 IGMP version 1 or 2." 603 ::= { igmpMIBGroups 1 } 605 Draft IGMP MIB September 1999 607 igmpRouterMIBGroup OBJECT-GROUP 608 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 609 igmpInterfaceJoins, igmpInterfaceGroups, 610 igmpCacheLastReporter, igmpInterfaceQuerierUpTime, 611 igmpInterfaceQuerierExpiryTime, 612 igmpInterfaceQueryInterval 613 } 614 STATUS current 615 DESCRIPTION 616 "A collection of additional objects for management of IGMP 617 version 1 or 2 in routers." 618 ::= { igmpMIBGroups 2 } 620 igmpV2HostMIBGroup OBJECT-GROUP 621 OBJECTS { igmpInterfaceVersion1QuerierTimer } 622 STATUS current 623 DESCRIPTION 624 "A collection of additional objects for management of IGMP 625 version 2 in hosts." 626 ::= { igmpMIBGroups 3 } 628 igmpHostOptMIBGroup OBJECT-GROUP 629 OBJECTS { igmpCacheLastReporter, igmpInterfaceQuerier } 630 STATUS current 631 DESCRIPTION 632 "A collection of optional objects for IGMP hosts. 633 Supporting this group can be especially useful in an 634 environment with a router which does not support the IGMP 635 MIB." 636 ::= { igmpMIBGroups 4 } 638 igmpV2RouterMIBGroup OBJECT-GROUP 639 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 640 igmpInterfaceQueryMaxResponseTime, 641 igmpInterfaceRobustness, 642 igmpInterfaceWrongVersionQueries, 643 igmpInterfaceLastMembQueryIntvl, 644 igmpCacheVersion1HostTimer 645 } 646 STATUS current 647 DESCRIPTION 648 "A collection of additional objects for management of IGMP 649 version 2 in routers." 650 ::= { igmpMIBGroups 5 } 652 Draft IGMP MIB September 1999 654 igmpV2ProxyMIBGroup OBJECT-GROUP 655 OBJECTS { igmpInterfaceProxyIfIndex } 656 STATUS current 657 DESCRIPTION 658 "A collection of additional objects for management of IGMP 659 proxy devices." 660 ::= { igmpMIBGroups 6 } 662 END 664 Draft IGMP MIB September 1999 666 6. Security Considerations 668 This MIB contains readable objects whose values provide information 669 related to multicast sessions. Some of these objects could contain 670 sensitive information. In particular, the igmpCacheSelf and 671 igmpCacheLastReporter can be used to identify machines which are 672 listening to a given group address. There are also a number of objects 673 that have a MAX-ACCESS clause of read-write and/or read-create, which 674 allow an administrator to configure IGMP in the router. 676 While unauthorized access to the readable objects is relatively 677 innocuous, unauthorized access to the write-able objects could cause a 678 denial of service. Hence, the support for SET operations in a non- 679 secure environment without proper protection can have a negative effect 680 on network operations. 682 SNMPv1 by itself is such an insecure environment. Even if the network 683 itself is secure (for example by using IPSec), even then, there is no 684 control as to who on the secure network is allowed to access and SET 685 (change/create/delete) the objects in this MIB. 687 It is recommended that the implementers consider the security features 688 as provided by the SNMPv3 framework. Specifically, the use of the User- 689 based Security Model RFC 2574 [12] and the View-based Access Control 690 Model RFC 2575 [15] is recommended. 692 It is then a customer/user responsibility to ensure that the SNMP entity 693 giving access to this MIB, is properly configured to give access to 694 those objects only to those principals (users) that have legitimate 695 rights to access them. 697 7. Acknowledgements 699 This MIB module was updated based on feedback from the IETF's Inter- 700 Domain Multicast Routing (IDMR) Working Group. 702 8. Authors' Addresses 704 Keith McCloghrie 705 cisco Systems, Inc. 706 170 West Tasman Drive 707 San Jose, CA 95134-1706 709 Draft IGMP MIB September 1999 711 Phone: +1 408 526 5260 712 EMail: kzm@cisco.com 714 Dino Farinacci 715 cisco Systems, Inc. 716 170 West Tasman Drive 717 San Jose, CA 95134-1706 718 Phone: +1 408 526 4696 719 EMail: dino@cisco.com 721 Dave Thaler 722 Microsoft Corporation 723 One Microsoft Way 724 Redmond, WA 48105-6399 725 Phone: +1 425 703 8835 726 EMail: dthaler@microsoft.com 728 9. References 730 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 731 Describing SNMP Management Frameworks", RFC 2571, Cabletron 732 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 733 1999. 735 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 736 Management Information for TCP/IP-based Internets", RFC 1155, STD 737 16, Performance Systems International, Hughes LAN Systems, May 738 1990. 740 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 741 STD 16, Performance Systems International, Hughes LAN Systems, 742 March 1991. 744 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 745 RFC 1215, Performance Systems International, March 1991. 747 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 748 and S. Waldbusser, "Structure of Management Information Version 2 749 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 750 Braunschweig, SNMP Research, First Virtual Holdings, International 751 Network Services, April 1999. 753 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 754 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 756 Draft IGMP MIB September 1999 758 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 759 Virtual Holdings, International Network Services, April 1999. 761 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 762 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 763 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 764 First Virtual Holdings, International Network Services, April 1999. 766 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 767 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 768 Systems International, Performance Systems International, MIT 769 Laboratory for Computer Science, May 1990. 771 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 772 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 773 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 774 International Network Services, January 1996. 776 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 777 Mappings for Version 2 of the Simple Network Management Protocol 778 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 779 Dover Beach Consulting, Inc., International Network Services, 780 January 1996. 782 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 783 Processing and Dispatching for the Simple Network Management 784 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 785 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 787 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 788 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 789 2574, IBM T. J. Watson Research, April 1999. 791 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 792 Operations for Version 2 of the Simple Network Management Protocol 793 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 794 Dover Beach Consulting, Inc., International Network Services, 795 January 1996. 797 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 798 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 799 Systems, April 1999. 801 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 802 Control Model (VACM) for the Simple Network Management Protocol 804 Draft IGMP MIB September 1999 806 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 807 Cisco Systems, Inc., April 1999. 809 [16] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, STD 810 5, Stanford University, August 1989. 812 [17] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 813 2236, November 1997. 815 10. Full Copyright Statement 817 Copyright (C) The Internet Society (1999). All Rights Reserved. 819 This document and translations of it may be copied and furnished to 820 others, and derivative works that comment on or otherwise explain it or 821 assist in its implmentation may be prepared, copied, published and 822 distributed, in whole or in part, without restriction of any kind, 823 provided that the above copyright notice and this paragraph are included 824 on all such copies and derivative works. However, this document itself 825 may not be modified in any way, such as by removing the copyright notice 826 or references to the Internet Society or other Internet organizations, 827 except as needed for the purpose of developing Internet standards in 828 which case the procedures for copyrights defined in the Internet 829 Standards process must be followed, or as required to translate it into 830 languages other than English. 832 The limited permissions granted above are perpetual and will not be 833 revoked by the Internet Society or its successors or assigns. 835 This document and the information contained herein is provided on an "AS 836 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 837 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 838 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 839 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 840 FITNESS FOR A PARTICULAR PURPOSE. 842 Table of Contents 844 1 Abstract ........................................................ 2 845 2 Introduction .................................................... 2 846 3 The SNMP Network Management Framework ........................... 2 847 3.1 Object Definitions ............................................ 3 849 Draft IGMP MIB September 1999 851 4 Overview ........................................................ 3 852 5 Definitions ..................................................... 4 853 6 Security Considerations ......................................... 17 854 7 Acknowledgements ................................................ 17 855 8 Authors' Addresses .............................................. 17 856 9 References ...................................................... 18 857 10 Full Copyright Statement ....................................... 20