idnits 2.17.1 draft-ietf-idmr-igmp-mib-00.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-26) 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. ** There are 59 instances of too long lines in the document, the longest one being 4 characters in excess of 72. 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 (15 July 1994) is 10878 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 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '6') -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 3 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 January 1995 Cisco Systems 5 15 July 1994 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]; a subset is 29 applicable to hosts implementing IGMP [5]. 31 Draft IGMP MIB July 1994 33 2. The SNMPv2 Network Management Framework 35 The SNMPv2 Network Management Framework consists of four major 36 components. They are: 38 o RFC 1442 [1] which defines the SMI, the mechanisms used for 39 describing and naming objects for the purpose of management. 41 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 42 objects for the Internet suite of protocols. 44 o RFC 1445 [3] which defines the administrative and other 45 architectural aspects of the framework. 47 o RFC 1448 [4] which defines the protocol used for network access to 48 managed objects. 50 The Framework permits new objects to be defined for the purpose of 51 experimentation and evaluation. 53 2.1. Object Definitions 55 Managed objects are accessed via a virtual information store, termed the 56 Management Information Base or MIB. Objects in the MIB are defined 57 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 58 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 59 an administratively assigned name. The object type together with an 60 object instance serves to uniquely identify a specific instantiation of 61 the object. For human convenience, we often use a textual string, 62 termed the descriptor, to refer to the object type. 64 3. Overview 66 This MIB module contains two tables: 68 (1) the IGMP Interface Table which contains one row for each interface 69 on which IGMP is enabled, and 71 (2) the IGMP Cache Table which contains one row for each IP multicast 72 group for which there are members on a particular interface. 74 Both tables are intended to be implemented by hosts and routers, but 75 some columnar objects in each table apply only to routers. 77 Draft IGMP MIB July 1994 79 4. Definitions 81 IGMP-MIB DEFINITIONS ::= BEGIN 83 IMPORTS 84 MODULE-IDENTITY, OBJECT-TYPE, experimental, 85 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 86 RowStatus, TruthValue FROM SNMPv2-TC 87 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 89 igmpMIB MODULE-IDENTITY 90 LAST-UPDATED "9407152359Z" 91 ORGANIZATION "IETF IDMR Working Group." 92 CONTACT-INFO 93 " Keith McCloghrie 94 cisco Systems, Inc. 95 1525 O'Brien Dr. 96 Menlo Park, CA 94025 97 EMail: kzm@cisco.com" 98 DESCRIPTION 99 "The MIB module for IGMP Management." 100 ::= { experimental xx } -- to be assigned by IANA 102 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 } 104 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 105 Draft IGMP MIB July 1994 107 -- 108 -- The IGMP Interface Table 109 -- 111 igmpInterfaceTable OBJECT-TYPE 112 SYNTAX SEQUENCE OF IgmpInterfaceEntry 113 MAX-ACCESS not-accessible 114 STATUS current 115 DESCRIPTION 116 "The (conceptual) table listing the interfaces on which IGMP 117 is enabled." 118 ::= { igmp 1 } 120 igmpInterfaceEntry OBJECT-TYPE 121 SYNTAX IgmpInterfaceEntry 122 MAX-ACCESS not-accessible 123 STATUS current 124 DESCRIPTION 125 "An entry (conceptual row) representing an interface on 126 which IGMP is enabled." 127 INDEX { igmpInterfaceIfIndex } 128 ::= { igmpInterfaceTable 1 } 130 IgmpInterfaceEntry ::= SEQUENCE { 131 igmpInterfaceIfIndex Integer32, 132 igmpInterfaceQueryInterval Integer32, 133 igmpInterfaceStatus RowStatus 134 } 136 igmpInterfaceIfIndex OBJECT-TYPE 137 SYNTAX Integer32 138 MAX-ACCESS not-accessible 139 STATUS current 140 DESCRIPTION 141 "The interface for which IGMP is enabled." 142 ::= { igmpInterfaceEntry 1 } 144 igmpInterfaceQueryInterval OBJECT-TYPE 145 SYNTAX Integer32 146 UNITS "seconds" 147 MAX-ACCESS read-create 148 STATUS current 149 DESCRIPTION 150 "The frequency at which IGMP Host-Query packets are 151 transmitted on this interface." 153 Draft IGMP MIB July 1994 155 DEFVAL { 60 } 156 ::= { igmpInterfaceEntry 2 } 158 igmpInterfaceStatus OBJECT-TYPE 159 SYNTAX RowStatus 160 MAX-ACCESS read-create 161 STATUS current 162 DESCRIPTION 163 "The activation of a row enables IGMP on the interface. The 164 destruction of a row disables IGMP on the interface." 165 ::= { igmpInterfaceEntry 3 } 167 -- 168 -- The IGMP Cache Table 169 -- 171 igmpCacheTable OBJECT-TYPE 172 SYNTAX SEQUENCE OF IgmpCacheEntry 173 MAX-ACCESS not-accessible 174 STATUS current 175 DESCRIPTION 176 "The (conceptual) table listing the IP multicast groups for 177 which there are members on a particular interface." 178 ::= { igmp 2 } 180 igmpCacheEntry OBJECT-TYPE 181 SYNTAX IgmpCacheEntry 182 MAX-ACCESS not-accessible 183 STATUS current 184 DESCRIPTION 185 "An entry (conceptual row) in the igmpCacheTable." 186 INDEX { igmpCacheAddress, igmpCacheIfIndex } 187 ::= { igmpCacheTable 1 } 189 Draft IGMP MIB July 1994 191 IgmpCacheEntry ::= SEQUENCE { 192 igmpCacheAddress IpAddress, 193 igmpCacheIfIndex Integer32, 194 igmpCacheSelf TruthValue, 195 igmpCacheLastReporter IpAddress, 196 igmpCacheUpTime TimeTicks, 197 igmpCacheExpiryTime TimeTicks, 198 igmpCacheStatus RowStatus 199 } 201 igmpCacheAddress OBJECT-TYPE 202 SYNTAX IpAddress 203 MAX-ACCESS not-accessible 204 STATUS current 205 DESCRIPTION 206 "The IP multicast group address for which this entry 207 contains information." 208 ::= { igmpCacheEntry 1 } 210 igmpCacheIfIndex OBJECT-TYPE 211 SYNTAX Integer32 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "The interface for which this entry contains information for 216 an IP multicast group address." 217 ::= { igmpCacheEntry 2 } 219 igmpCacheSelf OBJECT-TYPE 220 SYNTAX TruthValue 221 MAX-ACCESS read-create 222 STATUS current 223 DESCRIPTION 224 "An indication of whether the local system is a member of 225 this group address on this interface." 226 DEFVAL { true } 227 ::= { igmpCacheEntry 3 } 229 igmpCacheLastReporter OBJECT-TYPE 230 SYNTAX IpAddress 231 MAX-ACCESS read-only 232 STATUS current 233 DESCRIPTION 234 "The IP address of the source of the last membership report 235 received for this IP Multicast group address on this 237 Draft IGMP MIB July 1994 239 interface. If no membership report has been received, this 240 object has the value 0.0.0.0." 241 ::= { igmpCacheEntry 4 } 243 igmpCacheUpTime OBJECT-TYPE 244 SYNTAX TimeTicks 245 MAX-ACCESS read-only 246 STATUS current 247 DESCRIPTION 248 "The time since the system joined this group address, or 249 zero if the system is not currently a member." 250 ::= { igmpCacheEntry 5 } 252 igmpCacheExpiryTime OBJECT-TYPE 253 SYNTAX TimeTicks 254 MAX-ACCESS read-only 255 STATUS current 256 DESCRIPTION 257 "The minimum amount of time remaining before this entry will 258 be aged out." 259 ::= { igmpCacheEntry 6 } 261 igmpCacheStatus OBJECT-TYPE 262 SYNTAX RowStatus 263 MAX-ACCESS read-create 264 STATUS current 265 DESCRIPTION 266 "The status of this entry." 267 ::= { igmpCacheEntry 7 } 269 Draft IGMP MIB July 1994 271 -- conformance information 273 igmpMIBConformance 274 OBJECT IDENTIFIER ::= { igmpMIB 2 } 275 igmpMIBCompliances 276 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 277 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 279 -- compliance statements 281 igmpHostMIBCompliance MODULE-COMPLIANCE 282 STATUS current 283 DESCRIPTION 284 "The compliance statement for hosts implementing the IGMP 285 MIB." 286 MODULE -- this module 287 MANDATORY-GROUPS { igmpBaseMIBGroup } 289 ::= { igmpMIBCompliances 1 } 291 igmpRouterMIBCompliance MODULE-COMPLIANCE 292 STATUS current 293 DESCRIPTION 294 "The compliance statement for routers implementing the IGMP 295 MIB." 296 MODULE -- this module 297 MANDATORY-GROUPS { igmpBaseMIBGroup, 298 igmpRouterMIBGroup 299 } 300 ::= { igmpMIBCompliances 2 } 302 -- units of conformance 304 igmpBaseMIBGroup OBJECT-GROUP 305 OBJECTS { igmpCacheSelf, igmpCacheLastReporter, 306 igmpCacheStatus, igmpInterfaceStatus 307 } 308 STATUS current 309 DESCRIPTION 310 "The basic collection of objects providing management of 311 IGMP." 312 ::= { igmpMIBGroups 1 } 314 Draft IGMP MIB July 1994 316 igmpRouterMIBGroup OBJECT-GROUP 317 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 318 igmpInterfaceQueryInterval 319 } 320 STATUS current 321 DESCRIPTION 322 "A collection of additional objects for management of IGMP 323 in routers." 324 ::= { igmpMIBGroups 2 } 326 END 327 Draft IGMP MIB July 1994 329 5. Acknowledgements 331 This MIB module will be presented to the IETF's Inter-Domain Multicast 332 Routing (IDMR) Working Group. 334 6. References 336 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 337 of Management Information for version 2 of the Simple Network 338 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 339 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 340 University, April 1993. 342 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 343 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 344 RFC 1213, Hughes LAN Systems, Performance Systems International, 345 March 1991. 347 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 348 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 349 Trusted Information Systems, Hughes LAN Systems, April 1993. 351 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 352 Operations for version 2 of the Simple Network Management Protocol 353 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 354 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 356 [5] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, 357 August 1989. 359 [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 360 Multicast Routing Protocol", RFC 1075, November 1988. 362 [7] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 363 L. Wei, "Protocol Independent Multicast, Sparse Mode Protocol 364 Specification", March 1994. 366 7. Security Considerations 368 Security issues are not discussed in this memo. 370 Draft IGMP MIB July 1994 372 8. Author's Address 374 Keith McCloghrie 375 cisco Systems, Inc. 376 1525 O'Brien Dr. 377 Menlo Park, CA 94025 378 Phone: (415) 324-5260 379 EMail: kzm@cisco.com 381 Dino Farinacci 382 cisco Systems, Inc. 383 1525 O'Brien Dr. 384 Menlo Park, CA 94025 385 Phone: (415) 688-4696 386 EMail: dino@cisco.com 388 Draft IGMP MIB July 1994 390 Table of Contents 392 1 Introduction .................................................... 1 393 2 The SNMPv2 Network Management Framework ......................... 2 394 2.1 Object Definitions ............................................ 2 395 3 Overview ........................................................ 2 396 4 Definitions ..................................................... 3 397 5 Acknowledgements ................................................ 10 398 6 References ...................................................... 10 399 7 Security Considerations ......................................... 10 400 8 Author's Address ................................................ 11