idnits 2.17.1 draft-ietf-idmr-igmp-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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 Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (7 June 1999) is 9084 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: 16 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 December 1999 cisco Systems 4 Dave Thaler 5 Microsoft 6 7 June 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 June 1999 37 1. Abstact 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 o A set of fundamental applications described in RFC 2573 [14] and 80 the view-based access control mechanism described in RFC 2575 [15]. 82 Managed objects are accessed via a virtual information store, termed the 83 Management Information Base or MIB. Objects in the MIB are defined 84 using the mechanisms defined in the SMI. 86 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 87 conforming to the SMIv1 can be produced through the appropriate 88 translations. The resulting translated MIB must be semantically 89 equivalent, except where objects or events are omitted because no 90 translation is possible (use of Counter64). Some machine readable 91 information in SMIv2 will be converted into textual descriptions in 92 SMIv1 during the translation process. However, this loss of machine 93 readable information is not considered to change the semantics of the 94 MIB. 96 3.1. Object Definitions 98 Managed objects are accessed via a virtual information store, termed the 99 Management Information Base or MIB. Objects in the MIB are defined 100 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 101 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 102 an administratively assigned name. The object type together with an 103 object instance serves to uniquely identify a specific instantiation of 104 the object. For human convenience, we often use a textual string, 105 termed the descriptor, to refer to the object type. 107 4. Overview 109 This MIB module contains two tables: 111 (1) the IGMP Interface Table which contains one row for each interface 112 on which IGMP is enabled, and 114 (2) the IGMP Cache Table which contains one row for each IP multicast 115 group for which there are members on a particular interface. 117 Both tables are intended to be implemented by hosts and routers, but 118 some columnar objects in each table apply only to routers. 120 5. Definitions 122 IGMP-MIB DEFINITIONS ::= BEGIN 124 IMPORTS 125 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Counter32, Gauge32, 126 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 127 RowStatus, TruthValue FROM SNMPv2-TC 128 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 129 InterfaceIndexOrZero, 130 InterfaceIndex FROM IF-MIB; 132 igmpMIB MODULE-IDENTITY 133 LAST-UPDATED "9906071200Z" -- June 7, 1999 134 ORGANIZATION "IETF IDMR Working Group." 135 CONTACT-INFO 136 " Dave Thaler 137 Microsoft Corporation 138 One Microsoft Way 139 Redmond, WA 98052-6399 140 US 142 Phone: +1 425 703 8835 143 EMail: dthaler@dthaler.microsoft.com" 144 DESCRIPTION 145 "The MIB module for IGMP Management." 146 REVISION "9906071200Z" -- June 7, 1999 147 DESCRIPTION 148 "Initial version, published as RFC xxxx (to be filled in by 149 RFC-Editor)." 150 ::= { mib-2 xx } 151 -- NOTE TO RFC EDITOR: When this document is published as 152 -- an RFC, replace XX with IANA-assigned value and delete 153 -- this comment. 155 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 } 157 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 158 -- 159 -- The IGMP Interface Table 160 -- 162 igmpInterfaceTable OBJECT-TYPE 163 SYNTAX SEQUENCE OF IgmpInterfaceEntry 164 MAX-ACCESS not-accessible 165 STATUS current 166 DESCRIPTION 167 "The (conceptual) table listing the interfaces on which IGMP 168 is enabled." 169 ::= { igmp 1 } 171 igmpInterfaceEntry OBJECT-TYPE 172 SYNTAX IgmpInterfaceEntry 173 MAX-ACCESS not-accessible 174 STATUS current 175 DESCRIPTION 176 "An entry (conceptual row) representing an interface on 177 which IGMP is enabled." 178 INDEX { igmpInterfaceIfIndex } 179 ::= { igmpInterfaceTable 1 } 181 IgmpInterfaceEntry ::= SEQUENCE { 182 igmpInterfaceIfIndex InterfaceIndex, 183 igmpInterfaceQueryInterval Integer32, 184 igmpInterfaceStatus RowStatus, 185 igmpInterfaceVersion INTEGER, 186 igmpInterfaceQuerier IpAddress, 187 igmpInterfaceQueryMaxResponseTime Integer32, 188 igmpInterfaceVersion1QuerierTimer TimeTicks, 189 igmpInterfaceWrongVersionQueries Counter32, 190 igmpInterfaceJoins Counter32, 191 igmpInterfaceGroups Gauge32, 192 igmpInterfaceRobustness Integer32, 193 igmpInterfaceLastMembQueryIntvl Integer32, 194 igmpInterfaceProxyIfIndex InterfaceIndexOrZero, 195 igmpInterfaceQuerierUpTime TimeTicks, 196 igmpInterfaceQuerierExpiryTime TimeTicks 197 } 199 igmpInterfaceIfIndex OBJECT-TYPE 200 SYNTAX InterfaceIndex 201 MAX-ACCESS not-accessible 202 STATUS current 203 DESCRIPTION 204 "The ifIndex value of the interface for which IGMP is 205 enabled." 206 ::= { igmpInterfaceEntry 1 } 208 igmpInterfaceQueryInterval OBJECT-TYPE 209 SYNTAX Integer32 210 UNITS "seconds" 211 MAX-ACCESS read-create 212 STATUS current 213 DESCRIPTION 214 "The frequency at which IGMP Host-Query packets are 215 transmitted on this interface." 216 DEFVAL { 125 } 217 ::= { igmpInterfaceEntry 2 } 219 igmpInterfaceStatus OBJECT-TYPE 220 SYNTAX RowStatus 221 MAX-ACCESS read-create 222 STATUS current 223 DESCRIPTION 224 "The activation of a row enables IGMP on the interface. The 225 destruction of a row disables IGMP on the interface." 226 ::= { igmpInterfaceEntry 3 } 228 igmpInterfaceVersion OBJECT-TYPE 229 SYNTAX INTEGER { version1(1), version2(2) } 230 MAX-ACCESS read-create 231 STATUS current 232 DESCRIPTION 233 "The version of IGMP which is running on this interface. 234 This object can be used to configure a router capable of 235 running either value. For IGMP to function correctly, all 236 routers on a LAN must be configured to run the same version 237 of IGMP on that LAN." 238 DEFVAL { version2 } 239 ::= { igmpInterfaceEntry 4 } 241 igmpInterfaceQuerier OBJECT-TYPE 242 SYNTAX IpAddress 243 MAX-ACCESS read-only 244 STATUS current 245 DESCRIPTION 246 "The address of the IGMP Querier on the IP subnet to which 247 this interface is attached." 249 ::= { igmpInterfaceEntry 5 } 251 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 252 SYNTAX Integer32 253 UNITS "tenths of seconds" 254 MAX-ACCESS read-create 255 STATUS current 256 DESCRIPTION 257 "The maximum query response time advertised in IGMPv2 258 queries on this interface." 259 DEFVAL { 100 } 260 ::= { igmpInterfaceEntry 6 } 262 igmpInterfaceVersion1QuerierTimer OBJECT-TYPE 263 SYNTAX TimeTicks 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The time remaining until the host assumes that there are no 268 IGMPv1 routers present on the interface. While this is 269 non-zero, the host will reply to all queries with version 1 270 membership reports." 271 ::= { igmpInterfaceEntry 9 } 273 igmpInterfaceWrongVersionQueries OBJECT-TYPE 274 SYNTAX Counter32 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "The number of queries received whose IGMP version does not 279 match igmpInterfaceVersion. IGMP requires that all routers 280 on a LAN be configured to run the same version of IGMP. 281 Thus, if any queries are received with the wrong version, 282 this indicates a configuration error." 283 ::= { igmpInterfaceEntry 10 } 285 igmpInterfaceJoins OBJECT-TYPE 286 SYNTAX Counter32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of times a group membership has been added on 291 this interface; that is, the number of times an entry for 292 this interface has been added to the Cache Table. This 293 object gives an indication of the amount of IGMP activity 294 over time." 295 ::= { igmpInterfaceEntry 11 } 297 igmpInterfaceGroups OBJECT-TYPE 298 SYNTAX Gauge32 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The current number of entries for this interface in the 303 Cache Table." 304 ::= { igmpInterfaceEntry 13 } 306 igmpInterfaceRobustness OBJECT-TYPE 307 SYNTAX Integer32 308 MAX-ACCESS read-create 309 STATUS current 310 DESCRIPTION 311 "The Robustness Variable allows tuning for the expected 312 packet loss on a subnet. If a subnet is expected to be 313 lossy, the Robustness Variable may be increased. IGMP is 314 robust to (Robustness Variable-1) packet losses." 315 DEFVAL { 2 } 316 ::= { igmpInterfaceEntry 14 } 318 igmpInterfaceLastMembQueryIntvl OBJECT-TYPE 319 SYNTAX Integer32 320 UNITS "tenths of seconds" 321 MAX-ACCESS read-create 322 STATUS current 323 DESCRIPTION 324 "The Last Member Query Interval is the Max Response Time 325 inserted into Group-Specific Queries sent in response to 326 Leave Group messages, and is also the amount of time between 327 Group-Specific Query messages. This value may be tuned to 328 modify the leave latency of the network. A reduced value 329 results in reduced time to detect the loss of the last 330 member of a group. The value of this object is irrelevant 331 if igmpInterfaceVersion is version1." 332 DEFVAL { 10 } 333 ::= { igmpInterfaceEntry 15 } 335 igmpInterfaceProxyIfIndex OBJECT-TYPE 336 SYNTAX InterfaceIndexOrZero 337 MAX-ACCESS read-create 338 STATUS current 339 DESCRIPTION 340 "Some devices implement a form of IGMP proxying whereby 341 memberships learned on the interface represented by this 342 row, cause IGMP Host Membership Reports to be sent on the 343 interface whose ifIndex value is given by this object. Such 344 a device would implement the igmpV2RouterMIBGroup only on 345 its router interfaces (those interfaces with non-zero 346 igmpInterfaceProxyIfIndex). Typically, the value of this 347 object is 0, indicating that no proxying is being done." 348 DEFVAL { 0 } 349 ::= { igmpInterfaceEntry 16 } 351 igmpInterfaceQuerierUpTime OBJECT-TYPE 352 SYNTAX TimeTicks 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The time since igmpInterfaceQuerier was last changed." 357 ::= { igmpInterfaceEntry 17 } 359 igmpInterfaceQuerierExpiryTime OBJECT-TYPE 360 SYNTAX TimeTicks 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The amount of time remaining before the Other Querier 365 Present Timer expires. If the local system is the querier, 366 the value of this object is zero." 367 ::= { igmpInterfaceEntry 18 } 369 -- 370 -- The IGMP Cache Table 371 -- 373 igmpCacheTable OBJECT-TYPE 374 SYNTAX SEQUENCE OF IgmpCacheEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "The (conceptual) table listing the IP multicast groups for 379 which there are members on a particular interface." 380 ::= { igmp 2 } 382 igmpCacheEntry OBJECT-TYPE 383 SYNTAX IgmpCacheEntry 384 MAX-ACCESS not-accessible 385 STATUS current 386 DESCRIPTION 387 "An entry (conceptual row) in the igmpCacheTable." 388 INDEX { igmpCacheAddress, igmpCacheIfIndex } 389 ::= { igmpCacheTable 1 } 391 IgmpCacheEntry ::= SEQUENCE { 392 igmpCacheAddress IpAddress, 393 igmpCacheIfIndex InterfaceIndex, 394 igmpCacheSelf TruthValue, 395 igmpCacheLastReporter IpAddress, 396 igmpCacheUpTime TimeTicks, 397 igmpCacheExpiryTime TimeTicks, 398 igmpCacheStatus RowStatus, 399 igmpCacheVersion1HostTimer TimeTicks 400 } 402 igmpCacheAddress OBJECT-TYPE 403 SYNTAX IpAddress 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "The IP multicast group address for which this entry 408 contains information." 409 ::= { igmpCacheEntry 1 } 411 igmpCacheIfIndex OBJECT-TYPE 412 SYNTAX InterfaceIndex 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "The interface for which this entry contains information for 417 an IP multicast group address." 418 ::= { igmpCacheEntry 2 } 420 igmpCacheSelf OBJECT-TYPE 421 SYNTAX TruthValue 422 MAX-ACCESS read-create 423 STATUS current 424 DESCRIPTION 425 "An indication of whether the local system is a member of 426 this group address on this interface." 427 DEFVAL { true } 428 ::= { igmpCacheEntry 3 } 430 igmpCacheLastReporter OBJECT-TYPE 431 SYNTAX IpAddress 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The IP address of the source of the last membership report 436 received for this IP Multicast group address on this 437 interface. If no membership report has been received, this 438 object has the value 0.0.0.0." 439 ::= { igmpCacheEntry 4 } 441 igmpCacheUpTime OBJECT-TYPE 442 SYNTAX TimeTicks 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The time elapsed since this entry was created." 447 ::= { igmpCacheEntry 5 } 449 igmpCacheExpiryTime OBJECT-TYPE 450 SYNTAX TimeTicks 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "The minimum amount of time remaining before this entry will 455 be aged out. A value of 0 indicates that the entry is only 456 present because igmpCacheSelf is true and that if the router 457 left the group, this entry would be aged out immediately. 458 Note that some implementations may process membership 459 reports from the local system in the same way as reports 460 from other hosts, so a value of 0 is not required." 461 ::= { igmpCacheEntry 6 } 463 igmpCacheStatus OBJECT-TYPE 464 SYNTAX RowStatus 465 MAX-ACCESS read-create 466 STATUS current 467 DESCRIPTION 468 "The status of this entry." 469 ::= { igmpCacheEntry 7 } 471 igmpCacheVersion1HostTimer OBJECT-TYPE 472 SYNTAX TimeTicks 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The time remaining until the local router will assume that 477 there are no longer any IGMP version 1 members on the IP 478 subnet attached to this interface. Upon hearing any IGMPv1 479 Membership Report, this value is reset to the group 480 membership timer. While this time remaining is non-zero, 481 the local router ignores any IGMPv2 Leave messages for this 482 group that it receives on this interface." 483 ::= { igmpCacheEntry 8 } 485 -- conformance information 487 igmpMIBConformance 488 OBJECT IDENTIFIER ::= { igmpMIB 2 } 489 igmpMIBCompliances 490 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 491 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 493 -- compliance statements 495 igmpV1HostMIBCompliance MODULE-COMPLIANCE 496 STATUS current 497 DESCRIPTION 498 "The compliance statement for hosts running IGMPv1 and 499 implementing the IGMP MIB." 500 MODULE -- this module 501 MANDATORY-GROUPS { igmpBaseMIBGroup } 503 OBJECT igmpInterfaceStatus 504 MIN-ACCESS read-only 505 DESCRIPTION 506 "Write access is not required." 508 ::= { igmpMIBCompliances 1 } 510 igmpV1RouterMIBCompliance MODULE-COMPLIANCE 511 STATUS current 512 DESCRIPTION 513 "The compliance statement for routers running IGMPv1 and 514 implementing the IGMP MIB." 515 MODULE -- this module 516 MANDATORY-GROUPS { igmpBaseMIBGroup, 517 igmpRouterMIBGroup 518 } 520 OBJECT igmpInterfaceStatus 521 MIN-ACCESS read-only 522 DESCRIPTION 523 "Write access is not required." 525 ::= { igmpMIBCompliances 2 } 527 igmpV2HostMIBCompliance MODULE-COMPLIANCE 528 STATUS current 529 DESCRIPTION 530 "The compliance statement for hosts running IGMPv2 and 531 implementing the IGMP MIB." 532 MODULE -- this module 533 MANDATORY-GROUPS { igmpBaseMIBGroup, 534 igmpV2HostMIBGroup 535 } 537 OBJECT igmpInterfaceStatus 538 MIN-ACCESS read-only 539 DESCRIPTION 540 "Write access is not required." 542 ::= { igmpMIBCompliances 3 } 544 igmpV2RouterMIBCompliance MODULE-COMPLIANCE 545 STATUS current 546 DESCRIPTION 547 "The compliance statement for routers running IGMPv2 and 548 implementing the IGMP MIB." 549 MODULE -- this module 550 MANDATORY-GROUPS { igmpBaseMIBGroup, 551 igmpRouterMIBGroup, 552 igmpV2RouterMIBGroup 553 } 555 OBJECT igmpInterfaceStatus 556 MIN-ACCESS read-only 557 DESCRIPTION 558 "Write access is not required." 560 ::= { igmpMIBCompliances 4 } 562 -- units of conformance 564 igmpBaseMIBGroup OBJECT-GROUP 565 OBJECTS { igmpCacheSelf, igmpCacheLastReporter, 566 igmpCacheStatus, igmpInterfaceStatus 567 } 568 STATUS current 569 DESCRIPTION 570 "The basic collection of objects providing management of 571 IGMP version 1 or 2." 572 ::= { igmpMIBGroups 1 } 574 igmpRouterMIBGroup OBJECT-GROUP 575 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 576 igmpInterfaceQueryInterval 577 } 578 STATUS current 579 DESCRIPTION 580 "A collection of additional objects for management of IGMP 581 version 1 or 2 in routers." 582 ::= { igmpMIBGroups 2 } 584 igmpV2HostMIBGroup OBJECT-GROUP 585 OBJECTS { igmpInterfaceQuerier, 586 igmpInterfaceVersion1QuerierTimer 587 } 588 STATUS current 589 DESCRIPTION 590 "A collection of additional objects for management of IGMP 591 version 2 in hosts." 592 ::= { igmpMIBGroups 3 } 594 igmpV2RouterMIBGroup OBJECT-GROUP 595 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier, 596 igmpInterfaceQueryMaxResponseTime, 597 igmpInterfaceRobustness, 598 igmpInterfaceWrongVersionQueries, 599 igmpInterfaceJoins, igmpInterfaceGroups, 600 igmpInterfaceLastMembQueryIntvl, 601 igmpInterfaceQuerierUpTime, 602 igmpInterfaceQuerierExpiryTime, 603 igmpCacheVersion1HostTimer 604 } 605 STATUS current 606 DESCRIPTION 607 "A collection of additional objects for management of IGMP 608 version 2 in routers." 609 ::= { igmpMIBGroups 5 } 611 igmpV2ProxyMIBGroup OBJECT-GROUP 612 OBJECTS { igmpInterfaceProxyIfIndex } 613 STATUS current 614 DESCRIPTION 615 "A collection of additional objects for management of IGMP 616 proxy devices." 617 ::= { igmpMIBGroups 6 } 619 END 620 6. Security Considerations 622 This MIB contains readable objects whose values provide information 623 related to multicast sessions. Some of these objects could contain 624 sensitive information. In particular, the igmpCacheSelf and 625 igmpCacheLastReporter can be used to identify machines which are 626 listening to a given group address. There are also a number of objects 627 that have a MAX-ACCESS clause of read-write and/or read-create, which 628 allow an administrator to configure IGMP in the router. 630 While unauthorized access to the readable objects is relatively 631 innocuous, unauthorized access to the write-able objects could cause a 632 denial of service. Hence, the support for SET operations in a non- 633 secure environment without proper protection can have a negative effect 634 on network operations. 636 SNMPv1 by itself is such an insecure environment. Even if the network 637 itself is secure (for example by using IPSec), even then, there is no 638 control as to who on the secure network is allowed to access and SET 639 (change/create/delete) the objects in this MIB. 641 It is recommended that the implementers consider the security features 642 as provided by the SNMPv3 framework. Specifically, the use of the 643 User-based Security Model RFC 2574 [12] and the View-based Access 644 Control Model RFC 2575 [15] is recommended. 646 It is then a customer/user responsibility to ensure that the SNMP entity 647 giving access to this MIB, is properly configured to give access to 648 those objects only to those principals (users) that have legitimate 649 rights to access them. 651 7. Acknowledgements 653 This MIB module was updated based on feedback from the IETF's Inter- 654 Domain Multicast Routing (IDMR) Working Group. 656 8. Authors' Addresses 658 Keith McCloghrie 659 cisco Systems, Inc. 660 170 West Tasman Drive 661 San Jose, CA 95134-1706 662 Phone: +1 408 526 5260 663 EMail: kzm@cisco.com 665 Dino Farinacci 666 cisco Systems, Inc. 667 170 West Tasman Drive 668 San Jose, CA 95134-1706 669 Phone: +1 408 526 4696 670 EMail: dino@cisco.com 672 Dave Thaler 673 Microsoft Corporation 674 One Microsoft Way 675 Redmond, WA 48105-6399 676 Phone: +1 425 703 8835 677 EMail: dthaler@microsoft.com 679 9. References 681 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 682 Describing SNMP Management Frameworks", RFC 2571, Cabletron 683 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 684 1999. 686 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 687 Management Information for TCP/IP-based Internets", RFC 1155, STD 688 16, Performance Systems International, Hughes LAN Systems, May 689 1990. 691 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 692 STD 16, Performance Systems International, Hughes LAN Systems, 693 March 1991. 695 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 696 RFC 1215, Performance Systems International, March 1991. 698 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 699 and S. Waldbusser, "Structure of Management Information Version 2 700 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 701 Braunschweig, SNMP Research, First Virtual Holdings, International 702 Network Services, April 1999. 704 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 705 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 706 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 707 Virtual Holdings, International Network Services, April 1999. 709 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 710 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 711 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 712 First Virtual Holdings, International Network Services, April 1999. 714 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 715 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 716 Systems International, Performance Systems International, MIT 717 Laboratory for Computer Science, May 1990. 719 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 720 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 721 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 722 International Network Services, January 1996. 724 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 725 Mappings for Version 2 of the Simple Network Management Protocol 726 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 727 Dover Beach Consulting, Inc., International Network Services, 728 January 1996. 730 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 731 Processing and Dispatching for the Simple Network Management 732 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 733 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 735 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 736 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 737 2574, IBM T. J. Watson Research, April 1999. 739 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 740 Operations for Version 2 of the Simple Network Management Protocol 741 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 742 Dover Beach Consulting, Inc., International Network Services, 743 January 1996. 745 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 746 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 747 Systems, April 1999. 749 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 750 Control Model (VACM) for the Simple Network Management Protocol 751 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 752 Cisco Systems, Inc., April 1999. 754 [16] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, STD 755 5, Stanford University, August 1989. 757 [17] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 758 2236, November 1997. 760 10. Full Copyright Statement 762 Copyright (C) The Internet Society (1999). All Rights Reserved. 764 This document and translations of it may be copied and furnished to 765 others, and derivative works that comment on or otherwise explain it or 766 assist in its implmentation may be prepared, copied, published and 767 distributed, in whole or in part, without restriction of any kind, 768 provided that the above copyright notice and this paragraph are included 769 on all such copies and derivative works. However, this document itself 770 may not be modified in any way, such as by removing the copyright notice 771 or references to the Internet Society or other Internet organizations, 772 except as needed for the purpose of developing Internet standards in 773 which case the procedures for copyrights defined in the Internet 774 Standards process must be followed, or as required to translate it into 775 languages other than English. 777 The limited permissions granted above are perpetual and will not be 778 revoked by the Internet Society or its successors or assigns. 780 This document and the information contained herein is provided on an "AS 781 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 782 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 783 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 784 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 785 FITNESS FOR A PARTICULAR PURPOSE. 787 Table of Contents 789 1 Abstact ......................................................... 2 790 2 Introduction .................................................... 2 791 3 The SNMP Network Management Framework ........................... 2 792 3.1 Object Definitions ............................................ 3 793 4 Overview ........................................................ 3 794 5 Definitions ..................................................... 4 795 6 Security Considerations ......................................... 17 796 7 Acknowledgements ................................................ 17 797 8 Authors' Addresses .............................................. 17 798 9 References ...................................................... 18 799 10 Full Copyright Statement ....................................... 20