idnits 2.17.1 draft-ietf-idmr-igmp-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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 Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an 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 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 (9 June 1996) is 10182 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 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '6') -- Possible downref: Non-RFC (?) normative reference: ref. '7' ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '8') -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDMR Working Group Keith McCloghrie 3 INTERNET-DRAFT Dino Farinacci 4 Expires December 1996 cisco Systems 5 9 June 1996 7 Internet Group Management Protocol MIB 8 10 Status of this Memo 12 This document is an Internet Draft. Internet Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its Areas, and 14 its Working Groups. Note that other groups may also distribute working 15 documents as Internet Drafts. 17 Internet Drafts are valid for a maximum of six months and may be 18 updated, replaced, or obsoleted by other documents at any time. It is 19 inappropriate to use Internet Drafts as reference material or to cite 20 them other than as a "work in progress". 22 1. Introduction 24 This memo defines an experimental portion of the Management Information 25 Base (MIB) for use with network management protocols in the Internet 26 community. In particular, it describes managed objects used for 27 managing the Internet Group Management Protocol (IGMP). All of this MIB 28 module is applicable to IP multicast routers [6,7,8,9]; a subset is 29 applicable to hosts implementing IGMP [5]. 31 Draft IGMP MIB June 1996 33 2. Revision History 35 A record of changes which will be removed before publication. 37 9 June 39 (1) added support for IGMP version 2. 41 3. The SNMP Network Management Framework 43 The SNMP Network Management Framework presently consists of three major 44 components. They are: 46 o RFC 1902 [1] which defines the SMI, the mechanisms used for 47 describing and naming objects for the purpose of management. 49 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 50 objects for the Internet suite of protocols. 52 o RFC 1157 [3] and RFC 1905 [4] which define two versions of the 53 protocol used for network access to managed objects. 55 The Framework permits new objects to be defined for the purpose of 56 experimentation and evaluation. 58 3.1. Object Definitions 60 Managed objects are accessed via a virtual information store, termed the 61 Management Information Base or MIB. Objects in the MIB are defined 62 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 63 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 64 an administratively assigned name. The object type together with an 65 object instance serves to uniquely identify a specific instantiation of 66 the object. For human convenience, we often use a textual string, 67 termed the descriptor, to refer to the object type. 69 Draft IGMP MIB June 1996 71 4. Overview 73 This MIB module contains two tables: 75 (1) the IGMP Interface Table which contains one row for each interface 76 on which IGMP is enabled, and 78 (2) the IGMP Cache Table which contains one row for each IP multicast 79 group for which there are members on a particular interface. 81 Both tables are intended to be implemented by hosts and routers, but 82 some columnar objects in each table apply only to routers. 84 Draft IGMP MIB June 1996 86 5. Definitions 88 IGMP-MIB DEFINITIONS ::= BEGIN 90 IMPORTS 91 MODULE-IDENTITY, OBJECT-TYPE, experimental, 92 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 93 RowStatus, TruthValue FROM SNMPv2-TC 94 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 96 igmpMIB MODULE-IDENTITY 97 LAST-UPDATED "9504281659Z" 98 ORGANIZATION "IETF IDMR Working Group." 99 CONTACT-INFO 100 " Keith McCloghrie 101 Cisco Systems, Inc. 102 170 West Tasman Drive 103 San Jose, CA 95134-1706 104 US 106 Phone: +1 408 526 5260 107 EMail: kzm@cisco.com" 108 DESCRIPTION 109 "The MIB module for IGMP Management." 110 ::= { experimental 59 } 112 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 } 114 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 115 Draft IGMP MIB June 1996 117 -- 118 -- The IGMP Interface Table 119 -- 121 igmpInterfaceTable OBJECT-TYPE 122 SYNTAX SEQUENCE OF IgmpInterfaceEntry 123 MAX-ACCESS not-accessible 124 STATUS current 125 DESCRIPTION 126 "The (conceptual) table listing the interfaces on which IGMP 127 is enabled." 128 ::= { igmp 1 } 130 igmpInterfaceEntry OBJECT-TYPE 131 SYNTAX IgmpInterfaceEntry 132 MAX-ACCESS not-accessible 133 STATUS current 134 DESCRIPTION 135 "An entry (conceptual row) representing an interface on 136 which IGMP is enabled." 137 INDEX { igmpInterfaceIfIndex } 138 ::= { igmpInterfaceTable 1 } 140 IgmpInterfaceEntry ::= SEQUENCE { 141 igmpInterfaceIfIndex Integer32, 142 igmpInterfaceQueryInterval Integer32, 143 igmpInterfaceStatus RowStatus, 144 igmpInterfaceVersion INTEGER, 145 igmpInterfaceQuerier IpAddress, 146 igmpInterfaceQueryMaxResponseTime Integer32, 147 igmpInterfaceQuerierPresentTimeout Integer32, 148 igmpInterfaceLeaveEnabled TruthValue, 149 igmpInterfaceVersion1HostTimer Integer32 150 } 152 igmpInterfaceIfIndex OBJECT-TYPE 153 SYNTAX Integer32 154 MAX-ACCESS not-accessible 155 STATUS current 156 DESCRIPTION 157 "The interface for which IGMP is enabled." 158 ::= { igmpInterfaceEntry 1 } 160 igmpInterfaceQueryInterval OBJECT-TYPE 161 SYNTAX Integer32 163 Draft IGMP MIB June 1996 165 UNITS "seconds" 166 MAX-ACCESS read-create 167 STATUS current 168 DESCRIPTION 169 "The frequency at which IGMP Host-Query packets are 170 transmitted on this interface." 171 DEFVAL { 60 } 172 ::= { igmpInterfaceEntry 2 } 174 igmpInterfaceStatus OBJECT-TYPE 175 SYNTAX RowStatus 176 MAX-ACCESS read-create 177 STATUS current 178 DESCRIPTION 179 "The activation of a row enables IGMP on the interface. The 180 destruction of a row disables IGMP on the interface." 181 ::= { igmpInterfaceEntry 3 } 183 igmpInterfaceVersion OBJECT-TYPE 184 SYNTAX INTEGER { version1(1), version2(2) } 185 MAX-ACCESS read-create 186 STATUS current 187 DESCRIPTION 188 "The version of IFMP which is running on this interface." 189 DEFVAL { version2 } 190 ::= { igmpInterfaceEntry 4 } 192 igmpInterfaceQuerier OBJECT-TYPE 193 SYNTAX IpAddress 194 MAX-ACCESS read-only 195 STATUS current 196 DESCRIPTION 197 "The address of the IGMP Querier on the IP subnet to which 198 this interface is attached." 199 ::= { igmpInterfaceEntry 5 } 201 igmpInterfaceQueryMaxResponseTime OBJECT-TYPE 202 SYNTAX Integer32 203 UNITS "seconds" 204 MAX-ACCESS read-create 205 STATUS current 206 DESCRIPTION 207 "The maximum query response time advertised in IGMPv2 208 queries on this interface. Smaller values allow a router to 209 prune groups faster." 211 Draft IGMP MIB June 1996 213 ::= { igmpInterfaceEntry 6 } 215 igmpInterfaceQuerierPresentTimeout OBJECT-TYPE 216 SYNTAX Integer32 217 UNITS "seconds" 218 MAX-ACCESS read-create 219 STATUS current 220 DESCRIPTION 221 "A timeout interval. If no IGMPv2 queries are heard on this 222 interface within this timeout interval, the local router 223 will take over the Querier on the IP subnet to which this 224 interface is attached." 225 ::= { igmpInterfaceEntry 7 } 227 igmpInterfaceLeaveEnabled OBJECT-TYPE 228 SYNTAX TruthValue 229 MAX-ACCESS read-create 230 STATUS current 231 DESCRIPTION 232 "An indication of whether the processing of IGMPv2 Leave 233 messages is enabled on this interface." 234 DEFVAL { true } 235 ::= { igmpInterfaceEntry 8 } 237 igmpInterfaceVersion1HostTimer OBJECT-TYPE 238 SYNTAX Integer32 239 UNITS "seconds" 240 MAX-ACCESS read-only 241 STATUS current 242 DESCRIPTION 243 "The time remaining until the local router will assume that 244 there are no longer any IGMP version 1 hosts on the IP 245 subnet attached to this interface. Upon hearing any IGMPv1 246 Membership Report, this value is reset to the group 247 membership timer. While this time remaining is non-zero, 248 the local router ignores any IGMPv2 Leave messages that it 249 receives on this interface." 250 ::= { igmpInterfaceEntry 9 } 252 Draft IGMP MIB June 1996 254 -- 255 -- The IGMP Cache Table 256 -- 258 igmpCacheTable OBJECT-TYPE 259 SYNTAX SEQUENCE OF IgmpCacheEntry 260 MAX-ACCESS not-accessible 261 STATUS current 262 DESCRIPTION 263 "The (conceptual) table listing the IP multicast groups for 264 which there are members on a particular interface." 265 ::= { igmp 2 } 267 igmpCacheEntry OBJECT-TYPE 268 SYNTAX IgmpCacheEntry 269 MAX-ACCESS not-accessible 270 STATUS current 271 DESCRIPTION 272 "An entry (conceptual row) in the igmpCacheTable." 273 INDEX { igmpCacheAddress, igmpCacheIfIndex } 274 ::= { igmpCacheTable 1 } 276 IgmpCacheEntry ::= SEQUENCE { 277 igmpCacheAddress IpAddress, 278 igmpCacheIfIndex Integer32, 279 igmpCacheSelf TruthValue, 280 igmpCacheLastReporter IpAddress, 281 igmpCacheUpTime TimeTicks, 282 igmpCacheExpiryTime TimeTicks, 283 igmpCacheStatus RowStatus 284 } 286 igmpCacheAddress OBJECT-TYPE 287 SYNTAX IpAddress 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "The IP multicast group address for which this entry 292 contains information." 293 ::= { igmpCacheEntry 1 } 295 igmpCacheIfIndex OBJECT-TYPE 296 SYNTAX Integer32 297 MAX-ACCESS not-accessible 298 STATUS current 300 Draft IGMP MIB June 1996 302 DESCRIPTION 303 "The interface for which this entry contains information for 304 an IP multicast group address." 305 ::= { igmpCacheEntry 2 } 307 igmpCacheSelf OBJECT-TYPE 308 SYNTAX TruthValue 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 "An indication of whether the local system is a member of 313 this group address on this interface." 314 DEFVAL { true } 315 ::= { igmpCacheEntry 3 } 317 igmpCacheLastReporter OBJECT-TYPE 318 SYNTAX IpAddress 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The IP address of the source of the last membership report 323 received for this IP Multicast group address on this 324 interface. If no membership report has been received, this 325 object has the value 0.0.0.0." 326 ::= { igmpCacheEntry 4 } 328 igmpCacheUpTime OBJECT-TYPE 329 SYNTAX TimeTicks 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The time since the system joined this group address, or 334 zero if the system is not currently a member." 335 ::= { igmpCacheEntry 5 } 337 igmpCacheExpiryTime OBJECT-TYPE 338 SYNTAX TimeTicks 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The minimum amount of time remaining before this entry will 343 be aged out." 344 ::= { igmpCacheEntry 6 } 346 igmpCacheStatus OBJECT-TYPE 347 Draft IGMP MIB June 1996 349 SYNTAX RowStatus 350 MAX-ACCESS read-create 351 STATUS current 352 DESCRIPTION 353 "The status of this entry." 354 ::= { igmpCacheEntry 7 } 356 Draft IGMP MIB June 1996 358 -- conformance information 360 igmpMIBConformance 361 OBJECT IDENTIFIER ::= { igmpMIB 2 } 362 igmpMIBCompliances 363 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 364 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 366 -- compliance statements 368 igmpHostMIBCompliance MODULE-COMPLIANCE 369 STATUS current 370 DESCRIPTION 371 "The compliance statement for hosts implementing the IGMP 372 MIB." 373 MODULE -- this module 374 MANDATORY-GROUPS { igmpBaseMIBGroup } 376 ::= { igmpMIBCompliances 1 } 378 igmpRouterMIBCompliance MODULE-COMPLIANCE 379 STATUS current 380 DESCRIPTION 381 "The compliance statement for routers implementing the IGMP 382 MIB." 383 MODULE -- this module 384 MANDATORY-GROUPS { igmpBaseMIBGroup, 385 igmpRouterMIBGroup 386 } 387 ::= { igmpMIBCompliances 2 } 389 -- units of conformance 391 igmpBaseMIBGroup OBJECT-GROUP 392 OBJECTS { igmpCacheSelf, igmpCacheLastReporter, 393 igmpCacheStatus, igmpInterfaceStatus 394 } 395 STATUS current 396 DESCRIPTION 397 "The basic collection of objects providing management of 398 IGMP version 1 or 2." 399 ::= { igmpMIBGroups 1 } 401 Draft IGMP MIB June 1996 403 igmpRouterMIBGroup OBJECT-GROUP 404 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 405 igmpInterfaceQueryInterval 406 } 407 STATUS current 408 DESCRIPTION 409 "A collection of additional objects for management of IGMP 410 version 1 or 2 in routers." 411 ::= { igmpMIBGroups 2 } 413 igmpBaseVersion2MIBGroup OBJECT-GROUP 414 OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier } 415 STATUS current 416 DESCRIPTION 417 "A collection of additional objects for management of IGMP 418 version 2." 419 ::= { igmpMIBGroups 3 } 421 igmpRouterVersion2MIBGroup OBJECT-GROUP 422 OBJECTS { igmpInterfaceQueryMaxResponseTime, 423 igmpInterfaceQuerierPresentTimeout, 424 igmpInterfaceLeaveEnabled, 425 igmpInterfaceVersion1HostTimer 426 } 427 STATUS current 428 DESCRIPTION 429 "A collection of additional objects for management of IGMP 430 version 2 in routers." 431 ::= { igmpMIBGroups 4 } 433 END 434 Draft IGMP MIB June 1996 436 6. References 438 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 439 S. Waldbusser, "Structure of Management Information for version 2 440 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 441 January 1996. 443 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 444 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 445 RFC 1213, March 1991. 447 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 448 Management Protocol", RFC 1157, May 1990. 450 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 451 S. Waldbusser, "Protocol Operations for version 2 of the Simple 452 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 454 [5] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, 455 Stanford University, August 1989. 457 [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 458 Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman, 459 Stanford University, November 1988. 461 [7] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 462 L. Wei, "Protocol Independent Multicast (PIM): Protocol 463 Specification", Xerox, University of Southern California, Cisco 464 Systems, Lawrence Berkeley Laboratories, January 1995. 466 [8] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March 467 1994. 469 [9] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural 470 Overview and Specification", University College London, November 471 1994. 473 7. Security Considerations 475 Security issues are not discussed in this memo. 477 Draft IGMP MIB June 1996 479 8. Author's Address 481 Keith McCloghrie 482 cisco Systems, Inc. 483 170 West Tasman Drive 484 San Jose, CA 95134-1706 485 Phone: +1 408 526 5260 486 EMail: kzm@cisco.com 488 Dino Farinacci 489 cisco Systems, Inc. 490 170 West Tasman Drive 491 San Jose, CA 95134-1706 492 Phone: +1 408 526 4696 493 EMail: dino@cisco.com 495 Draft IGMP MIB June 1996 497 Table of Contents 499 1 Introduction .................................................... 1 500 2 Revision History ................................................ 2 501 3 The SNMP Network Management Framework ........................... 2 502 3.1 Object Definitions ............................................ 2 503 4 Overview ........................................................ 3 504 5 Definitions ..................................................... 4 505 6 References ...................................................... 13 506 7 Security Considerations ......................................... 13 507 8 Author's Address ................................................ 14