idnits 2.17.1 draft-ietf-idmr-igmp-mib-01.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-24) 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 (4 February 1995) is 10672 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: 13 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IDMR Working Group Keith McCloghrie 2 INTERNET-DRAFT Dino Farinacci 3 Expires August 1995 Cisco Systems 4 4 February 1995 6 Internet Group Management Protocol MIB 7 9 Status of this Memo 11 This document is an Internet Draft. Internet Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its Areas, and 13 its Working Groups. Note that other groups may also distribute working 14 documents as Internet Drafts. 16 Internet Drafts are valid for a maximum of six months and may be 17 updated, replaced, or obsoleted by other documents at any time. It is 18 inappropriate to use Internet Drafts as reference material or to cite 19 them other than as a "work in progress". 21 1. Introduction 23 This memo defines an experimental portion of the Management Information 24 Base (MIB) for use with network management protocols in the Internet 25 community. In particular, it describes managed objects used for 26 managing the Internet Group Management Protocol (IGMP). All of this MIB 27 module is applicable to IP multicast routers [6,7]; a subset is 28 applicable to hosts implementing IGMP [5]. 30 Draft IGMP MIB February 1995 32 2. The SNMPv2 Network Management Framework 34 The SNMPv2 Network Management Framework consists of four major 35 components. They are: 37 o RFC 1442 [1] which defines the SMI, the mechanisms used for 38 describing and naming objects for the purpose of management. 40 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 41 objects for the Internet suite of protocols. 43 o RFC 1445 [3] which defines the administrative and other 44 architectural aspects of the framework. 46 o RFC 1448 [4] which defines the protocol used for network access to 47 managed objects. 49 The Framework permits new objects to be defined for the purpose of 50 experimentation and evaluation. 52 2.1. Object Definitions 54 Managed objects are accessed via a virtual information store, termed the 55 Management Information Base or MIB. Objects in the MIB are defined 56 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 57 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 58 an administratively assigned name. The object type together with an 59 object instance serves to uniquely identify a specific instantiation of 60 the object. For human convenience, we often use a textual string, 61 termed the descriptor, to refer to the object type. 63 3. Overview 65 This MIB module contains two tables: 67 (1) the IGMP Interface Table which contains one row for each interface 68 on which IGMP is enabled, and 70 (2) the IGMP Cache Table which contains one row for each IP multicast 71 group for which there are members on a particular interface. 73 Both tables are intended to be implemented by hosts and routers, but 74 some columnar objects in each table apply only to routers. 76 Draft IGMP MIB February 1995 78 4. Definitions 80 IGMP-MIB DEFINITIONS ::= BEGIN 82 IMPORTS 83 MODULE-IDENTITY, OBJECT-TYPE, experimental, 84 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 85 RowStatus, TruthValue FROM SNMPv2-TC 86 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 88 igmpMIB MODULE-IDENTITY 89 LAST-UPDATED "9502042359Z" 90 ORGANIZATION "IETF IDMR Working Group." 91 CONTACT-INFO 92 " Keith McCloghrie 93 cisco Systems, Inc. 94 1525 O'Brien Dr. 95 Menlo Park, CA 94025 96 EMail: kzm@cisco.com" 97 DESCRIPTION 98 "The MIB module for IGMP Management." 99 ::= { experimental xx } -- to be assigned by IANA 101 igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 } 103 igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 } 104 Draft IGMP MIB February 1995 106 -- 107 -- The IGMP Interface Table 108 -- 110 igmpInterfaceTable OBJECT-TYPE 111 SYNTAX SEQUENCE OF IgmpInterfaceEntry 112 MAX-ACCESS not-accessible 113 STATUS current 114 DESCRIPTION 115 "The (conceptual) table listing the interfaces on which IGMP 116 is enabled." 117 ::= { igmp 1 } 119 igmpInterfaceEntry OBJECT-TYPE 120 SYNTAX IgmpInterfaceEntry 121 MAX-ACCESS not-accessible 122 STATUS current 123 DESCRIPTION 124 "An entry (conceptual row) representing an interface on 125 which IGMP is enabled." 126 INDEX { igmpInterfaceIfIndex } 127 ::= { igmpInterfaceTable 1 } 129 IgmpInterfaceEntry ::= SEQUENCE { 130 igmpInterfaceIfIndex Integer32, 131 igmpInterfaceQueryInterval Integer32, 132 igmpInterfaceStatus RowStatus 133 } 135 igmpInterfaceIfIndex OBJECT-TYPE 136 SYNTAX Integer32 137 MAX-ACCESS not-accessible 138 STATUS current 139 DESCRIPTION 140 "The interface for which IGMP is enabled." 141 ::= { igmpInterfaceEntry 1 } 143 igmpInterfaceQueryInterval OBJECT-TYPE 144 SYNTAX Integer32 145 UNITS "seconds" 146 MAX-ACCESS read-create 147 STATUS current 148 DESCRIPTION 149 "The frequency at which IGMP Host-Query packets are 150 transmitted on this interface." 152 Draft IGMP MIB February 1995 154 DEFVAL { 60 } 155 ::= { igmpInterfaceEntry 2 } 157 igmpInterfaceStatus OBJECT-TYPE 158 SYNTAX RowStatus 159 MAX-ACCESS read-create 160 STATUS current 161 DESCRIPTION 162 "The activation of a row enables IGMP on the interface. The 163 destruction of a row disables IGMP on the interface." 164 ::= { igmpInterfaceEntry 3 } 166 -- 167 -- The IGMP Cache Table 168 -- 170 igmpCacheTable OBJECT-TYPE 171 SYNTAX SEQUENCE OF IgmpCacheEntry 172 MAX-ACCESS not-accessible 173 STATUS current 174 DESCRIPTION 175 "The (conceptual) table listing the IP multicast groups for 176 which there are members on a particular interface." 177 ::= { igmp 2 } 179 igmpCacheEntry OBJECT-TYPE 180 SYNTAX IgmpCacheEntry 181 MAX-ACCESS not-accessible 182 STATUS current 183 DESCRIPTION 184 "An entry (conceptual row) in the igmpCacheTable." 185 INDEX { igmpCacheAddress, igmpCacheIfIndex } 186 ::= { igmpCacheTable 1 } 188 Draft IGMP MIB February 1995 190 IgmpCacheEntry ::= SEQUENCE { 191 igmpCacheAddress IpAddress, 192 igmpCacheIfIndex Integer32, 193 igmpCacheSelf TruthValue, 194 igmpCacheLastReporter IpAddress, 195 igmpCacheUpTime TimeTicks, 196 igmpCacheExpiryTime TimeTicks, 197 igmpCacheStatus RowStatus 198 } 200 igmpCacheAddress OBJECT-TYPE 201 SYNTAX IpAddress 202 MAX-ACCESS not-accessible 203 STATUS current 204 DESCRIPTION 205 "The IP multicast group address for which this entry 206 contains information." 207 ::= { igmpCacheEntry 1 } 209 igmpCacheIfIndex OBJECT-TYPE 210 SYNTAX Integer32 211 MAX-ACCESS not-accessible 212 STATUS current 213 DESCRIPTION 214 "The interface for which this entry contains information for 215 an IP multicast group address." 216 ::= { igmpCacheEntry 2 } 218 igmpCacheSelf OBJECT-TYPE 219 SYNTAX TruthValue 220 MAX-ACCESS read-create 221 STATUS current 222 DESCRIPTION 223 "An indication of whether the local system is a member of 224 this group address on this interface." 225 DEFVAL { true } 226 ::= { igmpCacheEntry 3 } 228 igmpCacheLastReporter OBJECT-TYPE 229 SYNTAX IpAddress 230 MAX-ACCESS read-only 231 STATUS current 232 DESCRIPTION 233 "The IP address of the source of the last membership report 234 received for this IP Multicast group address on this 236 Draft IGMP MIB February 1995 238 interface. If no membership report has been received, this 239 object has the value 0.0.0.0." 240 ::= { igmpCacheEntry 4 } 242 igmpCacheUpTime OBJECT-TYPE 243 SYNTAX TimeTicks 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 "The time since the system joined this group address, or 248 zero if the system is not currently a member." 249 ::= { igmpCacheEntry 5 } 251 igmpCacheExpiryTime OBJECT-TYPE 252 SYNTAX TimeTicks 253 MAX-ACCESS read-only 254 STATUS current 255 DESCRIPTION 256 "The minimum amount of time remaining before this entry will 257 be aged out." 258 ::= { igmpCacheEntry 6 } 260 igmpCacheStatus OBJECT-TYPE 261 SYNTAX RowStatus 262 MAX-ACCESS read-create 263 STATUS current 264 DESCRIPTION 265 "The status of this entry." 266 ::= { igmpCacheEntry 7 } 268 Draft IGMP MIB February 1995 270 -- conformance information 272 igmpMIBConformance 273 OBJECT IDENTIFIER ::= { igmpMIB 2 } 274 igmpMIBCompliances 275 OBJECT IDENTIFIER ::= { igmpMIBConformance 1 } 276 igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 } 278 -- compliance statements 280 igmpHostMIBCompliance MODULE-COMPLIANCE 281 STATUS current 282 DESCRIPTION 283 "The compliance statement for hosts implementing the IGMP 284 MIB." 285 MODULE -- this module 286 MANDATORY-GROUPS { igmpBaseMIBGroup } 288 ::= { igmpMIBCompliances 1 } 290 igmpRouterMIBCompliance MODULE-COMPLIANCE 291 STATUS current 292 DESCRIPTION 293 "The compliance statement for routers implementing the IGMP 294 MIB." 295 MODULE -- this module 296 MANDATORY-GROUPS { igmpBaseMIBGroup, 297 igmpRouterMIBGroup 298 } 299 ::= { igmpMIBCompliances 2 } 301 -- units of conformance 303 igmpBaseMIBGroup OBJECT-GROUP 304 OBJECTS { igmpCacheSelf, igmpCacheLastReporter, 305 igmpCacheStatus, igmpInterfaceStatus 306 } 307 STATUS current 308 DESCRIPTION 309 "The basic collection of objects providing management of 310 IGMP." 311 ::= { igmpMIBGroups 1 } 313 Draft IGMP MIB February 1995 315 igmpRouterMIBGroup OBJECT-GROUP 316 OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime, 317 igmpInterfaceQueryInterval 318 } 319 STATUS current 320 DESCRIPTION 321 "A collection of additional objects for management of IGMP 322 in routers." 323 ::= { igmpMIBGroups 2 } 325 END 326 Draft IGMP MIB February 1995 328 5. References 330 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 331 of Management Information for version 2 of the Simple Network 332 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 333 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 334 University, April 1993. 336 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 337 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 338 RFC 1213, Hughes LAN Systems, Performance Systems International, 339 March 1991. 341 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 342 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 343 Trusted Information Systems, Hughes LAN Systems, April 1993. 345 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 346 Operations for version 2 of the Simple Network Management Protocol 347 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 348 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 350 [5] Deering, S., "Host Extensions for IP Multicasting", RFC 1112, 351 August 1989. 353 [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 354 Multicast Routing Protocol", RFC 1075, November 1988. 356 [7] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 357 L. Wei, "Protocol Independent Multicast (PIM): Protocol 358 Specification", January 1995. 360 6. Security Considerations 362 Security issues are not discussed in this memo. 364 7. Author's Address 366 Keith McCloghrie 367 cisco Systems, Inc. 368 1525 O'Brien Dr. 370 Draft IGMP MIB February 1995 372 Menlo Park, CA 94025 373 Phone: (415) 324-5260 374 EMail: kzm@cisco.com 376 Dino Farinacci 377 cisco Systems, Inc. 378 1525 O'Brien Dr. 379 Menlo Park, CA 94025 380 Phone: (415) 688-4696 381 EMail: dino@cisco.com 383 Draft IGMP MIB February 1995 385 Table of Contents 387 1 Introduction .................................................... 1 388 2 The SNMPv2 Network Management Framework ......................... 2 389 2.1 Object Definitions ............................................ 2 390 3 Overview ........................................................ 2 391 4 Definitions ..................................................... 3 392 5 References ...................................................... 10 393 6 Security Considerations ......................................... 10 394 7 Author's Address ................................................ 10