idnits 2.17.1 draft-ietf-idmr-igmp-mib-12.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 81 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 (19 October 1999) is 8956 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 (~~), 4 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 April 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 19 October 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 October 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 IPv4 multicast routers; a subset is 51 applicable to hosts implementing IGMP. This MIB does not support 52 management of IGMP or equivalent functionality for other address 53 families, such as IPv6. Such management may be supported by other MIBs. 55 3. The SNMP Network Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in RFC 2571 [1]. 62 o Mechanisms for describing and naming objects and events for the 63 purpose of management. The first version of this Structure of 64 Management Information (SMI) is called SMIv1 and described in RFC 65 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 66 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 68 o Message protocols for transferring management information. The 69 first version of the SNMP message protocol is called SNMPv1 and 70 described in RFC 1157 [8]. A second version of the SNMP message 71 protocol, which is not an Internet standards track protocol, is 72 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 73 The third version of the message protocol is called SNMPv3 and 74 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 76 o Protocol operations for accessing management information. The first 77 set of protocol operations and associated PDU formats is described 78 in RFC 1157 [8]. A second set of protocol operations and associated 79 PDU formats is described in RFC 1905 [13]. 81 Draft IGMP MIB October 1999 83 o A set of fundamental applications described in RFC 2573 [14] and 84 the view-based access control mechanism described in RFC 2575 [15]. 86 Managed objects are accessed via a virtual information store, termed the 87 Management Information Base or MIB. Objects in the MIB are defined 88 using the mechanisms defined in the SMI. 90 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 91 conforming to the SMIv1 can be produced through the appropriate 92 translations. The resulting translated MIB must be semantically 93 equivalent, except where objects or events are omitted because no 94 translation is possible (use of Counter64). Some machine readable 95 information in SMIv2 will be converted into textual descriptions in 96 SMIv1 during the translation process. However, this loss of machine 97 readable information is not considered to change the semantics of the 98 MIB. 100 4. Overview 102 This MIB module contains two tables: 104 (1) the IGMP Interface Table which contains one row for each 105 interface on which IGMP is enabled, and 107 (2) the IGMP Cache Table which contains one row for each IP multicast 108 group for which there are members on a particular interface. 110 Both tables are intended to be implemented by hosts and routers, but 111 some columnar objects in each table apply only to routers. 113 Draft IGMP MIB October 1999 115 5. Definitions 117 IGMP-STD-MIB DEFINITIONS ::= BEGIN 119 IMPORTS 120 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32, 121 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 122 RowStatus, TruthValue FROM SNMPv2-TC 123 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 124 InterfaceIndexOrZero, 125 InterfaceIndex FROM IF-MIB; 127 igmpStdMIB MODULE-IDENTITY 128 LAST-UPDATED "9909171200Z" -- September 17, 1999 129 ORGANIZATION "IETF IDMR Working Group." 130 CONTACT-INFO 131 " Dave Thaler 132 Microsoft Corporation 133 One Microsoft Way 134 Redmond, WA 98052-6399 135 US 137 Phone: +1 425 703 8835 138 EMail: dthaler@dthaler.microsoft.com" 139 DESCRIPTION 140 "The MIB module for IGMP Management." 141 REVISION "9909171200Z" -- September 17, 1999 142 DESCRIPTION 143 "Initial version, published as RFC xxxx (to be filled in by 144 RFC-Editor)." 145 ::= { mib-2 xx } 146 -- NOTE TO RFC EDITOR: When this document is published as 147 -- an RFC, replace XX with IANA-assigned value and delete 148 -- this comment. 150 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpStdMIB 1 } 152 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 154 Draft IGMP MIB October 1999 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 ::= { igmp 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 Integer32, 182 igmpInterfaceStatus RowStatus, 183 igmpInterfaceVersion INTEGER, 184 igmpInterfaceQuerier IpAddress, 185 igmpInterfaceQueryMaxResponseTime Integer32, 186 igmpInterfaceVersion1QuerierTimer TimeTicks, 187 igmpInterfaceWrongVersionQueries Counter32, 188 igmpInterfaceJoins Counter32, 189 igmpInterfaceGroups Gauge32, 190 igmpInterfaceRobustness Integer32, 191 igmpInterfaceLastMembQueryIntvl Integer32, 192 igmpInterfaceProxyIfIndex InterfaceIndexOrZero, 193 igmpInterfaceQuerierUpTime TimeTicks, 194 igmpInterfaceQuerierExpiryTime TimeTicks 195 } 197 igmpInterfaceIfIndex OBJECT-TYPE 198 SYNTAX InterfaceIndex 199 MAX-ACCESS not-accessible 200 STATUS current 202 Draft IGMP MIB October 1999 204 DESCRIPTION 205 "The ifIndex value of the interface for which IGMP is 206 enabled." 207 ::= { igmpInterfaceEntry 1 } 209 igmpInterfaceQueryInterval OBJECT-TYPE 210 SYNTAX Integer32 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 INTEGER { version1(1), version2(2) } 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 { version2 } 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 October 1999 252 ::= { igmpInterfaceEntry 5 } 254 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 255 SYNTAX Integer32 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 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 266 SYNTAX TimeTicks 267 MAX-ACCESS read-only 268 STATUS current 269 DESCRIPTION 270 "The time remaining until the host assumes that there are no 271 IGMPv1 routers present on the interface. While this is non- 272 zero, the host will reply to all queries with version 1 273 membership reports." 274 ::= { igmpInterfaceEntry 9 } 276 igmpInterfaceWrongVersionQueries OBJECT-TYPE 277 SYNTAX Counter32 278 MAX-ACCESS read-only 279 STATUS current 280 DESCRIPTION 281 "The number of queries received whose IGMP version does not 282 match igmpInterfaceVersion. IGMP requires that all routers 283 on a LAN be configured to run the same version of IGMP. 284 Thus, if any queries are received with the wrong version, 285 this indicates a configuration error." 286 ::= { igmpInterfaceEntry 10 } 288 igmpInterfaceJoins OBJECT-TYPE 289 SYNTAX Counter32 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The number of times a group membership has been added on 294 this interface; that is, the number of times an entry for 295 this interface has been added to the Cache Table. This 296 object gives an indication of the amount of IGMP activity 298 Draft IGMP MIB October 1999 300 over time." 301 ::= { igmpInterfaceEntry 11 } 303 igmpInterfaceGroups OBJECT-TYPE 304 SYNTAX Gauge32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The current number of entries for this interface in the 309 Cache Table." 310 ::= { igmpInterfaceEntry 13 } 312 igmpInterfaceRobustness OBJECT-TYPE 313 SYNTAX Integer32 314 MAX-ACCESS read-create 315 STATUS current 316 DESCRIPTION 317 "The Robustness Variable allows tuning for the expected 318 packet loss on a subnet. If a subnet is expected to be 319 lossy, the Robustness Variable may be increased. IGMP is 320 robust to (Robustness Variable-1) packet losses." 321 DEFVAL { 2 } 322 ::= { igmpInterfaceEntry 14 } 324 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 325 SYNTAX Integer32 326 UNITS "tenths of seconds" 327 MAX-ACCESS read-create 328 STATUS current 329 DESCRIPTION 330 "The Last Member Query Interval is the Max Response Time 331 inserted into Group-Specific Queries sent in response to 332 Leave Group messages, and is also the amount of time between 333 Group-Specific Query messages. This value may be tuned to 334 modify the leave latency of the network. A reduced value 335 results in reduced time to detect the loss of the last 336 member of a group. The value of this object is irrelevant 337 if igmpInterfaceVersion is version1." 338 DEFVAL { 10 } 339 ::= { igmpInterfaceEntry 15 } 341 igmpInterfaceProxyIfIndex OBJECT-TYPE 342 SYNTAX InterfaceIndexOrZero 343 MAX-ACCESS read-create 344 STATUS current 346 Draft IGMP MIB October 1999 348 DESCRIPTION 349 "Some devices implement a form of IGMP proxying whereby 350 memberships learned on the interface represented by this 351 row, cause IGMP Host Membership Reports to be sent on the 352 interface whose ifIndex value is given by this object. Such 353 a device would implement the igmpV2RouterMIBGroup only on 354 its router interfaces (those interfaces with non-zero 355 igmpInterfaceProxyIfIndex). Typically, the value of this 356 object is 0, indicating that no proxying is being done." 357 DEFVAL { 0 } 358 ::= { igmpInterfaceEntry 16 } 360 igmpInterfaceQuerierUpTime OBJECT-TYPE 361 SYNTAX TimeTicks 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The time since igmpInterfaceQuerier was last changed." 366 ::= { igmpInterfaceEntry 17 } 368 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 369 SYNTAX TimeTicks 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The amount of time remaining before the Other Querier 374 Present Timer expires. If the local system is the querier, 375 the value of this object is zero." 376 ::= { igmpInterfaceEntry 18 } 378 Draft IGMP MIB October 1999 380 -- 381 -- The IGMP Cache Table 382 -- 384 igmpCacheTable OBJECT-TYPE 385 SYNTAX SEQUENCE OF IgmpCacheEntry 386 MAX-ACCESS not-accessible 387 STATUS current 388 DESCRIPTION 389 "The (conceptual) table listing the IP multicast groups for 390 which there are members on a particular interface." 391 ::= { igmp 2 } 393 igmpCacheEntry OBJECT-TYPE 394 SYNTAX IgmpCacheEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "An entry (conceptual row) in the igmpCacheTable." 399 INDEX { igmpCacheAddress, igmpCacheIfIndex } 400 ::= { igmpCacheTable 1 } 402 IgmpCacheEntry ::= SEQUENCE { 403 igmpCacheAddress IpAddress, 404 igmpCacheIfIndex InterfaceIndex, 405 igmpCacheSelf TruthValue, 406 igmpCacheLastReporter IpAddress, 407 igmpCacheUpTime TimeTicks, 408 igmpCacheExpiryTime TimeTicks, 409 igmpCacheStatus RowStatus, 410 igmpCacheVersion1HostTimer TimeTicks 411 } 413 igmpCacheAddress OBJECT-TYPE 414 SYNTAX IpAddress 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "The IP multicast group address for which this entry 419 contains information." 420 ::= { igmpCacheEntry 1 } 422 igmpCacheIfIndex OBJECT-TYPE 423 SYNTAX InterfaceIndex 424 MAX-ACCESS not-accessible 426 Draft IGMP MIB October 1999 428 STATUS current 429 DESCRIPTION 430 "The interface for which this entry contains information for 431 an IP multicast group address." 432 ::= { igmpCacheEntry 2 } 434 igmpCacheSelf OBJECT-TYPE 435 SYNTAX TruthValue 436 MAX-ACCESS read-create 437 STATUS current 438 DESCRIPTION 439 "An indication of whether the local system is a member of 440 this group address on this interface." 441 DEFVAL { true } 442 ::= { igmpCacheEntry 3 } 444 igmpCacheLastReporter OBJECT-TYPE 445 SYNTAX IpAddress 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The IP address of the source of the last membership report 450 received for this IP Multicast group address on this 451 interface. If no membership report has been received, this 452 object has the value 0.0.0.0." 453 ::= { igmpCacheEntry 4 } 455 igmpCacheUpTime OBJECT-TYPE 456 SYNTAX TimeTicks 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The time elapsed since this entry was created." 461 ::= { igmpCacheEntry 5 } 463 igmpCacheExpiryTime OBJECT-TYPE 464 SYNTAX TimeTicks 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The minimum amount of time remaining before this entry will 469 be aged out. A value of 0 indicates that the entry is only 470 present because igmpCacheSelf is true and that if the router 471 left the group, this entry would be aged out immediately. 472 Note that some implementations may process membership 474 Draft IGMP MIB October 1999 476 reports from the local system in the same way as reports 477 from other hosts, so a value of 0 is not required." 478 ::= { igmpCacheEntry 6 } 480 igmpCacheStatus OBJECT-TYPE 481 SYNTAX RowStatus 482 MAX-ACCESS read-create 483 STATUS current 484 DESCRIPTION 485 "The status of this entry." 486 ::= { igmpCacheEntry 7 } 488 igmpCacheVersion1HostTimer OBJECT-TYPE 489 SYNTAX TimeTicks 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The time remaining until the local router will assume that 494 there are no longer any IGMP version 1 members on the IP 495 subnet attached to this interface. Upon hearing any IGMPv1 496 Membership Report, this value is reset to the group 497 membership timer. While this time remaining is non-zero, 498 the local router ignores any IGMPv2 Leave messages for this 499 group that it receives on this interface." 500 ::= { igmpCacheEntry 8 } 502 Draft IGMP MIB October 1999 504 -- conformance information 506 igmpMIBConformance 507 OBJECT IDENTIFIER ::= { igmpStdMIB 2 } 508 igmpMIBCompliances 509 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 510 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 512 -- compliance statements 514 igmpV1HostMIBCompliance MODULE-COMPLIANCE 515 STATUS current 516 DESCRIPTION 517 "The compliance statement for hosts running IGMPv1 and 518 implementing the IGMP MIB." 519 MODULE -- this module 520 MANDATORY-GROUPS { igmpBaseMIBGroup } 522 OBJECT igmpInterfaceStatus 523 MIN-ACCESS read-only 524 DESCRIPTION 525 "Write access is not required." 527 ::= { igmpMIBCompliances 1 } 529 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 530 STATUS current 531 DESCRIPTION 532 "The compliance statement for routers running IGMPv1 and 533 implementing the IGMP MIB." 534 MODULE -- this module 535 MANDATORY-GROUPS { igmpBaseMIBGroup, 536 igmpRouterMIBGroup 537 } 539 OBJECT igmpInterfaceStatus 540 MIN-ACCESS read-only 541 DESCRIPTION 542 "Write access is not required." 544 ::= { igmpMIBCompliances 2 } 546 igmpV2HostMIBCompliance MODULE-COMPLIANCE 547 STATUS current 549 Draft IGMP MIB October 1999 551 DESCRIPTION 552 "The compliance statement for hosts running IGMPv2 and 553 implementing the IGMP MIB." 554 MODULE -- this module 555 MANDATORY-GROUPS { igmpBaseMIBGroup, 556 igmpV2HostMIBGroup 557 } 559 OBJECT igmpInterfaceStatus 560 MIN-ACCESS read-only 561 DESCRIPTION 562 "Write access is not required." 564 ::= { igmpMIBCompliances 3 } 566 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 567 STATUS current 568 DESCRIPTION 569 "The compliance statement for routers running IGMPv2 and 570 implementing the IGMP MIB." 571 MODULE -- this module 572 MANDATORY-GROUPS { igmpBaseMIBGroup, 573 igmpRouterMIBGroup, 574 igmpV2RouterMIBGroup 575 } 577 OBJECT igmpInterfaceStatus 578 MIN-ACCESS read-only 579 DESCRIPTION 580 "Write access is not required." 582 ::= { igmpMIBCompliances 4 } 584 -- units of conformance 586 igmpBaseMIBGroup OBJECT-GROUP 587 OBJECTS { igmpCacheSelf, 588 igmpCacheStatus, igmpInterfaceStatus 589 } 590 STATUS current 591 DESCRIPTION 592 "The basic collection of objects providing management of 593 IGMP version 1 or 2." 594 ::= { igmpMIBGroups 1 } 596 Draft IGMP MIB October 1999 598 igmpRouterMIBGroup OBJECT-GROUP 599 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 600 igmpInterfaceJoins, igmpInterfaceGroups, 601 igmpCacheLastReporter, igmpInterfaceQuerierUpTime, 602 igmpInterfaceQuerierExpiryTime, 603 igmpInterfaceQueryInterval 604 } 605 STATUS current 606 DESCRIPTION 607 "A collection of additional objects for management of IGMP 608 version 1 or 2 in routers." 609 ::= { igmpMIBGroups 2 } 611 igmpV2HostMIBGroup OBJECT-GROUP 612 OBJECTS { igmpInterfaceVersion1QuerierTimer } 613 STATUS current 614 DESCRIPTION 615 "A collection of additional objects for management of IGMP 616 version 2 in hosts." 617 ::= { igmpMIBGroups 3 } 619 igmpHostOptMIBGroup OBJECT-GROUP 620 OBJECTS { igmpCacheLastReporter, igmpInterfaceQuerier } 621 STATUS current 622 DESCRIPTION 623 "A collection of optional objects for IGMP hosts. 624 Supporting this group can be especially useful in an 625 environment with a router which does not support the IGMP 626 MIB." 627 ::= { igmpMIBGroups 4 } 629 igmpV2RouterMIBGroup OBJECT-GROUP 630 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 631 igmpInterfaceQueryMaxResponseTime, 632 igmpInterfaceRobustness, 633 igmpInterfaceWrongVersionQueries, 634 igmpInterfaceLastMembQueryIntvl, 635 igmpCacheVersion1HostTimer 636 } 637 STATUS current 638 DESCRIPTION 639 "A collection of additional objects for management of IGMP 640 version 2 in routers." 641 ::= { igmpMIBGroups 5 } 643 Draft IGMP MIB October 1999 645 igmpV2ProxyMIBGroup OBJECT-GROUP 646 OBJECTS { igmpInterfaceProxyIfIndex } 647 STATUS current 648 DESCRIPTION 649 "A collection of additional objects for management of IGMP 650 proxy devices." 651 ::= { igmpMIBGroups 6 } 653 END 655 Draft IGMP MIB October 1999 657 6. Security Considerations 659 This MIB contains readable objects whose values provide information 660 related to multicast sessions. Some of these objects could contain 661 sensitive information. In particular, the igmpCacheSelf and 662 igmpCacheLastReporter can be used to identify machines which are 663 listening to a given group address. There are also a number of objects 664 that have a MAX-ACCESS clause of read-write and/or read-create, which 665 allow an administrator to configure IGMP in the router. 667 While unauthorized access to the readable objects is relatively 668 innocuous, unauthorized access to the write-able objects could cause a 669 denial of service. Hence, the support for SET operations in a non- 670 secure environment without proper protection can have a negative effect 671 on network operations. 673 SNMPv1 by itself is such an insecure environment. Even if the network 674 itself is secure (for example by using IPSec), even then, there is no 675 control as to who on the secure network is allowed to access and SET 676 (change/create/delete) the objects in this MIB. 678 It is recommended that the implementers consider the security features 679 as provided by the SNMPv3 framework. Specifically, the use of the User- 680 based Security Model RFC 2574 [12] and the View-based Access Control 681 Model RFC 2575 [15] is recommended. 683 It is then a customer/user responsibility to ensure that the SNMP entity 684 giving access to this MIB, is properly configured to give access to 685 those objects only to those principals (users) that have legitimate 686 rights to access them. 688 7. Intellectual Property Notice 690 The IETF takes no position regarding the validity or scope of any 691 intellectual property or other rights that might be claimed to pertain 692 to the implementation or use of the technology described in this 693 document or the extent to which any license under such rights might or 694 might not be available; neither does it represent that it has made any 695 effort to identify any such rights. Information on the IETF's 696 procedures with respect to rights in standards-track and standards- 697 related documentation can be found in BCP-11. Copies of claims of 698 rights made available for publication and any assurances of licenses to 699 be made available, or the result of an attempt made to obtain a general 700 license or permission for the use of such proprietary rights by 702 Draft IGMP MIB October 1999 704 implementers or users of this specification can be obtained from the 705 IETF Secretariat. 707 The IETF invites any interested party to bring to its attention any 708 copyrights, patents or patent applications, or other proprietary rights 709 which may cover technology that may be required to practice this 710 standard. Please address the information to the IETF Executive 711 Director. 713 8. Acknowledgements 715 This MIB module was updated based on feedback from the IETF's Inter- 716 Domain Multicast Routing (IDMR) Working Group. 718 9. Authors' Addresses 720 Keith McCloghrie 721 cisco Systems, Inc. 722 170 West Tasman Drive 723 San Jose, CA 95134-1706 724 Phone: +1 408 526 5260 725 EMail: kzm@cisco.com 727 Dino Farinacci 728 cisco Systems, Inc. 729 170 West Tasman Drive 730 San Jose, CA 95134-1706 731 Phone: +1 408 526 4696 732 EMail: dino@cisco.com 734 Dave Thaler 735 Microsoft Corporation 736 One Microsoft Way 737 Redmond, WA 48105-6399 738 Phone: +1 425 703 8835 739 EMail: dthaler@microsoft.com 741 10. References 743 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 744 Describing SNMP Management Frameworks", RFC 2571, Cabletron 746 Draft IGMP MIB October 1999 748 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 749 1999. 751 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 752 Management Information for TCP/IP-based Internets", RFC 1155, STD 753 16, Performance Systems International, Hughes LAN Systems, May 754 1990. 756 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 757 STD 16, Performance Systems International, Hughes LAN Systems, 758 March 1991. 760 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 761 RFC 1215, Performance Systems International, March 1991. 763 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 764 and S. Waldbusser, "Structure of Management Information Version 2 765 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 766 Braunschweig, SNMP Research, First Virtual Holdings, International 767 Network Services, April 1999. 769 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 770 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 771 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 772 Virtual Holdings, International Network Services, April 1999. 774 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 775 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 776 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 777 First Virtual Holdings, International Network Services, April 1999. 779 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 780 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 781 Systems International, Performance Systems International, MIT 782 Laboratory for Computer Science, May 1990. 784 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 785 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 786 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 787 International Network Services, January 1996. 789 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 790 Mappings for Version 2 of the Simple Network Management Protocol 791 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 792 Dover Beach Consulting, Inc., International Network Services, 794 Draft IGMP MIB October 1999 796 January 1996. 798 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 799 Processing and Dispatching for the Simple Network Management 800 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 801 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 803 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 804 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 805 2574, IBM T. J. Watson Research, April 1999. 807 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 808 Operations for Version 2 of the Simple Network Management Protocol 809 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 810 Dover Beach Consulting, Inc., International Network Services, 811 January 1996. 813 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 814 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 815 Systems, April 1999. 817 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 818 Control Model (VACM) for the Simple Network Management Protocol 819 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 820 Cisco Systems, Inc., April 1999. 822 [16] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, STD 823 5, Stanford University, August 1989. 825 [17] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 826 2236, November 1997. 828 11. Full Copyright Statement 830 Copyright (C) The Internet Society (1999). All Rights Reserved. 832 This document and translations of it may be copied and furnished to 833 others, and derivative works that comment on or otherwise explain it or 834 assist in its implmentation may be prepared, copied, published and 835 distributed, in whole or in part, without restriction of any kind, 836 provided that the above copyright notice and this paragraph are included 837 on all such copies and derivative works. However, this document itself 838 may not be modified in any way, such as by removing the copyright notice 839 or references to the Internet Society or other Internet organizations, 841 Draft IGMP MIB October 1999 843 except as needed for the purpose of developing Internet standards in 844 which case the procedures for copyrights defined in the Internet 845 Standards process must be followed, or as required to translate it into 846 languages other than English. 848 The limited permissions granted above are perpetual and will not be 849 revoked by the Internet Society or its successors or assigns. 851 This document and the information contained herein is provided on an "AS 852 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 853 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 854 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 855 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 856 FITNESS FOR A PARTICULAR PURPOSE. 858 Table of Contents 860 1 Abstract ........................................................ 2 861 2 Introduction .................................................... 2 862 3 The SNMP Network Management Framework ........................... 2 863 4 Overview ........................................................ 3 864 5 Definitions ..................................................... 4 865 6 Security Considerations ......................................... 17 866 7 Intellectual Property Notice .................................... 17 867 8 Acknowledgements ................................................ 18 868 9 Authors' Addresses .............................................. 18 869 10 References ..................................................... 18 870 11 Full Copyright Statement ....................................... 20