idnits 2.17.00 (12 Aug 2021) /tmp/idnits30204/draft-thaler-idmr-multicast-routemib-00.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: ---------------------------------------------------------------------------- ** 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? ** 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 == The page length should not exceed 58 lines per page, but there was 27 longer pages, the longest (page 17) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 6 instances of too long lines in the document, the longest one being 1 character in excess of 72. == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 332: '...netMRouteSource. The value MUST be the...' RFC 2119 keyword, line 366: '...MRouteUpstreamNeighbor. The value MUST...' RFC 2119 keyword, line 487: '...MRouteRtAddress. The value MUST be the...' RFC 2119 keyword, line 633: '... MUST...' RFC 2119 keyword, line 683: '... MUST be the same as th...' 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 (June 2000) is 8003 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) -- Missing reference section? '1' on line 15 looks like a reference -- Missing reference section? '2' on line 44 looks like a reference -- Missing reference section? '3' on line 45 looks like a reference -- Missing reference section? '4' on line 45 looks like a reference -- Missing reference section? '5' on line 45 looks like a reference -- Missing reference section? '6' on line 45 looks like a reference -- Missing reference section? '7' on line 45 looks like a reference -- Missing reference section? '8' on line 46 looks like a reference -- Missing reference section? '9' on line 57 looks like a reference -- Missing reference section? '10' on line 62 looks like a reference -- Missing reference section? '11' on line 62 looks like a reference -- Missing reference section? '12' on line 62 looks like a reference -- Missing reference section? '13' on line 63 looks like a reference -- Missing reference section? '14' on line 63 looks like a reference -- Missing reference section? '15' on line 64 looks like a reference -- Missing reference section? '16' on line 76 looks like a reference -- Missing reference section? '17' on line 70 looks like a reference -- Missing reference section? '18' on line 72 looks like a reference -- Missing reference section? '19' on line 72 looks like a reference -- Missing reference section? '20' on line 1292 looks like a reference -- Missing reference section? '21' on line 77 looks like a reference -- Missing reference section? '22' on line 79 looks like a reference -- Missing reference section? '23' on line 1293 looks like a reference -- Missing reference section? '24' on line 116 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 5 warnings (==), 26 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IDMR Working Group Dave Thaler 2 Internet Draft Microsoft 3 Andrew Adams 4 William Siadak 5 Djinesys, Inc. 6 draft-thaler-idmr-multicast-routemib-00.txt June 2000 7 Experimental 9 Multiprotocol Multicast Routing MIB 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026 [1]. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. Internet-Drafts are draft documents valid for a maximum of 20 six months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- Drafts 22 as reference material or to cite them other than as "work in 23 progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Copyright Notice 31 Copyright (C) The Internet Society (2000). All Rights Reserved. 33 1. Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management protocols in 37 the Internet community. In particular, it describes managed 38 objects used for managing IP Multicast Routing for IPv4 and IPv6, 39 independent of the specific multicast routing protocol in use. 41 2. Introduction 43 This MIB describes objects used for managing IPv4 and IPv6 44 Multicast Routing[2],independent of the specific multicast routing 45 protocol [3,4,5,6,7] in use. This MIB extends the MIB proposed in 46 [8]. Managed objects specific to particular multicast routing 47 protocols are specified elsewhere. Similarly, this MIB does not 48 support management of multicast routing for other address families. 49 Such management may be supported by other MIBs. 51 3. The SNMP Management Framework 53 1 54 The SNMP Management Framework presently consists of five major 55 components: 57 o An overall architecture, described in RFC 2571 [9]. 59 o Mechanisms for describing and naming objects and events for 60 the purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in RFC 62 1155 [10], RFC 1212 [11] and RFC 1215 [12]. The second version, 63 called SMIv2, is described in RFC 2578 [13], RFC 2579 [14] and RFC 64 2580 [15]. 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 [16]. 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 [17] and RFC 1906 [18]. 71 The third version of the message protocol is called SNMPv3 and 72 described in RFC 1906 [18], RFC 2572 [19] and RFC 2574 [20]. 74 o Protocol operations for accessing management information. The 75 first set of protocol operations and associated PDU formats is 76 described in RFC 1157 [16]. A second set of protocol operations and 77 associated PDU formats is described in RFC 1905 [21]. 79 o A set of fundamental applications described in RFC 2573 [22] 80 and the view-based access control mechanism described in RFC 2575 81 [23]. 83 Managed objects are accessed via a virtual information store, 84 termed the Management Information Base or MIB. Objects in the MIB 85 are defined using the mechanisms defined in the SMI. 87 This memo specifies a MIB module that is compliant to the SMIv2. A 88 MIB conforming to the SMIv1 can be produced through the appropriate 89 translations. The resulting translated MIB must be semantically 90 equivalent, except where objects or events are omitted because no 91 translation is possible (use of Counter64). Some machine readable 92 information in SMIv2 will be converted into textual descriptions in 93 SMIv1 during the translation process. However, this loss of machine 94 readable information is not considered to change the semantics of 95 the MIB. 97 4. Overview 99 This MIB module contains one scalar and five tables. The tables 100 are: 102 Thaler,Adams,Siadak Experimental/Expires Dec 2000 2 103 (1) the Multicast Route Table containing multicast routing 104 information for datagrams sent by particular sources to the 105 multicast groups known to a router. 107 (2) the Multicast Routing Next Hop Table containing information 108 on the next-hops for the routing multicast datagrams. Each entry 109 is one of a list of next-hops on outgoing interfaces for particular 110 qsources sending to a particular multicast group address. 112 (3) the Multicast Routing Interface Table containing multicast 113 routing information specific to interfaces. 115 (4) the Multicast Scope Boundary Table containing the boundaries 116 configured for multicast scopes [24]. 118 (5) the Multicast Scope Name Table containing human-readable 119 names of multicast scope. 121 5. Definitions 123 INETMROUTE-STD-MIB DEFINITIONS ::= BEGIN 125 IMPORTS 126 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 127 Integer32, Counter32, Counter64, Gauge32, 128 TimeTicks FROM SNMPv2-SMI 129 RowStatus, TEXTUAL-CONVENTION, 130 TruthValue FROM SNMPv2-TC 131 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 132 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 133 InterfaceIndexOrZero, 134 InterfaceIndex FROM IF-MIB 135 IANAipRouteProtocol, 136 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 137 InetAddress, InetAddressType FROM INET-ADDRESS-MIB; 139 inetMRouteStdMIB MODULE-IDENTITY 140 LAST-UPDATED "200003090000Z" -- March 9, 2000 141 ORGANIZATION "IETF IDMR Working Group" 142 CONTACT-INFO 143 " Dave Thaler 144 Microsoft Corporation 145 One Microsoft Way 146 Redmond, WA 98052-6399 147 US 149 Phone: +1 425 703 8835 150 EMail: dthaler@dthaler.microsoft.com 152 Andrew Adams 153 Merit Network, Inc. 155 Thaler,Adams,Siadak Experimental/Expires Dec 2000 3 156 4251 Plymouth Rd. 157 Ann Arbor, MI 48105-2785 159 Phone: +1 734 763-6378 160 EMail: ala@merit.edu 162 William Siadak 163 Merit Network, Inc. 164 4251 Plymouth Rd. 165 Ann Arbor, MI 48105-2785 167 Phone: +1 734 936 2035 168 EMail: wfs@merit.edu" 170 DESCRIPTION 171 "The MIB module for management of IP Multicast routing, 172 but independent of the specific multicast routing 173 protocol in use._ 174 REVISION "200003090000Z" -- March 9, 2000 175 DESCRIPTION 176 "Initial version, published as RFC xxxx (to be filled 177 in 178 by RFC-Editor)." 179 ::= { mib-2 XX } 180 -- NOTE TO RFC EDITOR: When this document is published as 181 -- an RFC, replace XX with IANA-assigned number, 182 -- and delete this comment. 184 -- Textual Conventions 186 LanguageTag ::= TEXTUAL-CONVENTION 187 DISPLAY-HINT "100a" 188 STATUS current 189 DESCRIPTION 190 "An RFC 1766-style language tag, with all alphabetic 191 characters converted to lowercase. This restriction is 192 intended to make the lexical ordering imposed by SNMP 193 useful when applied to language tags. Note that it is 194 theoretically possible for a valid language tag to 195 exceed the allowed length of this syntax, and thus be 196 impossible to represent with this syntax. Sampling of 197 language tags in current use on the Internet suggests 198 that this limit does not pose a serious problem in 199 practice." 200 SYNTAX OCTET STRING (SIZE (1..100)) 202 -- Top-level structure of the MIB 204 inetMRouteMIBObjects OBJECT IDENTIFIER ::= { inetMRouteStdMIB 1 } 206 inetMRoute OBJECT IDENTIFIER ::= { inetMRouteMIBObjects 1 } 208 -- the IP Multicast Routing MIB-Group 210 Thaler,Adams,Siadak Experimental/Expires Dec 2000 4 211 -- 212 -- a collection of objects providing information about 213 -- IP Multicast Groups 215 inetMRouteEnabled OBJECT-TYPE 216 SYNTAX TruthValue 217 MAX-ACCESS read-write 218 STATUS current 219 DESCRIPTION 220 "The enabled status of IP Multicast routing on this 221 router." 222 ::= { inetMRoute 1 } 224 inetMRouteEntryCount OBJECT-TYPE 225 SYNTAX Gauge32 226 MAX-ACCESS read-only 227 STATUS current 228 DESCRIPTION 229 "The number of rows in the inetMRouteTable. This can 230 be 231 used to monitor the multicast routing table size." 232 ::= { inetMRoute 7 } 234 inetMRouteTable OBJECT-TYPE 235 SYNTAX SEQUENCE OF InetMRouteEntry 236 MAX-ACCESS not-accessible 237 STATUS current 238 DESCRIPTION 239 "The (conceptual) table containing multicast routing 240 information for IP datagrams sent by particular sources 241 to the IP multicast groups known to this router." 242 ::= { inetMRoute 2 } 244 inetMRouteEntry OBJECT-TYPE 245 SYNTAX InetMRouteEntry 246 MAX-ACCESS not-accessible 247 STATUS current 248 DESCRIPTION 249 "An entry (conceptual row) containing the multicast 250 routing information for IP datagrams from a particular 251 source and addressed to a particular IP multicast group 252 address. Discontinuities in counters in this entry can 253 be detected by observing the value of 254 inetMRouteUpTime." 255 INDEX { inetMRouteGroupType, 256 inetMRouteGroup, 257 inetMRouteGroupMaskLen, 258 inetMRouteSourceType, 259 inetMRouteSource, 260 inetMRouteSourceMaskLen } 261 ::= { inetMRouteTable 1 } 263 InetMRouteEntry ::= SEQUENCE { 265 Thaler,Adams,Siadak Experimental/Expires Dec 2000 5 266 inetMRouteGroupType InetAddressType, 267 inetMRouteGroup InetAddress, 268 inetMRouteGroupMaskLen INTEGER, 269 inetMRouteSourceType InetAddressType, 270 inetMRouteSource InetAddress, 271 inetMRouteSourceMaskLen INTEGER, 272 inetMRouteUpstreamNeighborType InetAddressType, 273 inetMRouteUpstreamNeighbor InetAddress, 274 inetMRouteInIfIndex InterfaceIndexOrZero, 275 inetMRouteUpTime TimeTicks, 276 inetMRouteExpiryTime TimeTicks, 277 inetMRoutePkts Counter32, 278 inetMRouteDifferentInIfPackets Counter32, 279 inetMRouteOctets Counter32, 280 inetMRouteProtocol IANAipMRouteProtocol, 281 inetMRouteRtProto IANAipRouteProtocol, 282 inetMRouteRtAddressType InetAddressType, 283 inetMRouteRtAddress InetAddress, 284 inetMRouteRtMaskLen INTEGER, 285 inetMRouteRtType INTEGER, 286 inetMRouteHCOctets Counter64 287 } 289 inetMRouteGroupType OBJECT-TYPE 290 SYNTAX InetAddressType 291 MAX-ACCESS not-accessible 292 STATUS current 293 DESCRIPTION 294 "A value indicating the address family of the address 295 contained in inetMRouteGroup. Legal values correspond 296 to the subset of address families for which multicast 297 forwarding is supported." 298 ::= { inetMRouteEntry 1 } 300 inetMRouteGroup OBJECT-TYPE 301 SYNTAX InetAddress 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "The IP multicast group address which when combined 306 with 307 the corresponding value specified in 308 inetMRouteGroupMaskLen identifies the groups for which 309 this entry contains multicast routing information." 310 ::= { inetMRouteEntry 2 } 312 inetMRouteGroupMaskLen OBJECT-TYPE 313 SYNTAX INTEGER (0..128) 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "The length in bits of the mask which when combined 318 with 320 Thaler,Adams,Siadak Experimental/Expires Dec 2000 6 321 the corresponding value of inetMRouteGroup identifies 322 the groups for which this entry contains multicast 323 routing information." 324 ::= { inetMRouteEntry 3 } 326 inetMRouteSourceType OBJECT-TYPE 327 SYNTAX InetAddressType 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "A value indicating the address family of the address 332 contained in inetMRouteSource. The value MUST be the 333 same 334 as the value of inetMRouteGroupType." 335 ::= { inetMRouteEntry 4 } 337 inetMRouteSource OBJECT-TYPE 338 SYNTAX InetAddress 339 MAX-ACCESS not-accessible 340 STATUS current 341 DESCRIPTION 342 "The network address which when combined with the 343 corresponding value of inetMRouteSourceMaskLen 344 identifies the sources for which this entry contains 345 multicast routing information." 346 ::= { inetMRouteEntry 5 } 348 inetMRouteSourceMaskLen OBJECT-TYPE 349 SYNTAX INTEGER (0..128) 350 MAX-ACCESS not-accessible 351 STATUS current 352 DESCRIPTION 353 "The length in bits of the mask which when combined 354 with 355 the corresponding value of inetMRouteSource identifies 356 the sources for which this entry contains multicast 357 routing information." 358 ::= { inetMRouteEntry 6 } 360 inetMRouteUpstreamNeighborType OBJECT-TYPE 361 SYNTAX InetAddressType 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "A value indicating the address family of the address 366 contained in inetMRouteUpstreamNeighbor. The value MUST 367 be the same as the value of inetMRouteGroupType." 368 ::= { inetMRouteEntry 7 } 370 inetMRouteUpstreamNeighbor OBJECT-TYPE 371 SYNTAX InetAddress 372 MAX-ACCESS read-only 373 STATUS current 375 Thaler,Adams,Siadak Experimental/Expires Dec 2000 7 376 DESCRIPTION 377 "The address of the upstream neighbor (e.g., RPF 378 neighbor) from which IP datagrams from these sources to 379 this multicast address are received. If the upstream 380 neighbor is unknown, then inetMRouteUpstreamNeighbor 381 will be 0.0.0.0 in the case of an IPv4 entry, and 382 0:0:0:0:0:0:0:0 in the case of an IPv6 entry. (e.g., in 383 CBT)." 384 ::= { inetMRouteEntry 8 } 386 inetMRouteInIfIndex OBJECT-TYPE 387 SYNTAX InterfaceIndexOrZero 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The value of ifIndex for the interface on which IP 392 datagrams sent by these sources to this multicast 393 address are received. A value of 0 indicates that 394 datagrams are not subject to an incoming interface 395 check, but may be accepted on multiple interfaces 396 (e.g., 397 in CBT)." 398 ::= { inetMRouteEntry 9 } 400 inetMRouteUpTime OBJECT-TYPE 401 SYNTAX TimeTicks 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The time since the multicast routing information 406 represented by this entry was learned by the router." 407 ::= { inetMRouteEntry 10 } 409 inetMRouteExpiryTime OBJECT-TYPE 410 SYNTAX TimeTicks 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The minimum amount of time remaining before this entry 415 will be aged out. The value 0 indicates that the entry 416 is not subject to aging." 417 ::= { inetMRouteEntry 11 } 419 inetMRoutePkts OBJECT-TYPE 420 SYNTAX Counter32 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The number of packets which this router has received 425 from these sources and addressed to this multicast 426 group 427 address." 428 ::= { inetMRouteEntry 12 } 430 Thaler,Adams,Siadak Experimental/Expires Dec 2000 8 431 inetMRouteDifferentInIfPackets OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The number of packets which this router has received 437 from these sources and addressed to this multicast 438 group 439 address, which were dropped because they were not 440 received on the interface indicated by 441 inetMRouteInIfIndex. Packets which are not subject to 442 an incoming interface check (e.g., using CBT) are not 443 counted." 444 ::= { inetMRouteEntry 13 } 446 inetMRouteOctets OBJECT-TYPE 447 SYNTAX Counter32 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The number of octets contained in IP datagrams which 452 were received from these sources and addressed to this 453 multicast group address, and which were forwarded by 454 this router." 455 ::= { inetMRouteEntry 14 } 457 inetMRouteProtocol OBJECT-TYPE 458 SYNTAX IANAipMRouteProtocol 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The multicast routing protocol via which this 463 multicast 464 forwarding entry was learned." 465 ::= { inetMRouteEntry 15 } 467 inetMRouteRtProto OBJECT-TYPE 468 SYNTAX IANAipRouteProtocol 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "The routing mechanism via which the route used to find 473 the upstream or parent interface for this multicast 474 forwarding entry was learned. Inclusion of values for 475 routing protocols is not intended to imply that those 476 protocols need be supported." 477 ::= { inetMRouteEntry 16 } 479 inetMRouteRtAddressType OBJECT-TYPE 480 SYNTAX InetAddressType 481 MAX-ACCESS read-only 482 STATUS current 484 Thaler,Adams,Siadak Experimental/Expires Dec 2000 9 485 DESCRIPTION 486 "A value indicating the address family of the address 487 contained in inetMRouteRtAddress. The value MUST be the 488 same as the value of inetMRouteGroupType." 489 ::= { inetMRouteEntry 17 } 491 inetMRouteRtAddress OBJECT-TYPE 492 SYNTAX InetAddress 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The address portion of the route used to find the 497 upstream or parent interface for this multicast 498 forwarding entry." 499 ::= { inetMRouteEntry 18 } 501 inetMRouteRtMaskLen OBJECT-TYPE 502 SYNTAX INTEGER (0..128) 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The length in bits of the mask associated with the 507 route used to find the upstream or parent interface for 508 this multicast forwarding entry." 509 ::= { inetMRouteEntry 19 } 511 inetMRouteRtType OBJECT-TYPE 512 SYNTAX INTEGER { 513 unicast (1), -- Unicast route used in multicast 514 RIB 515 multicast (2) -- Multicast route 516 } 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "The reason the given route was placed in the (logical) 521 multicast Routing Information Base (RIB). A value of 522 unicast means that the route would normally be placed 523 only in the unicast RIB, but was placed in the 524 multicast 525 RIB (instead or in addition) due to local 526 configuration, 527 such as when running PIM over RIP. A value of 528 multicast 529 means that the route was explicitly added to the 530 multicast RIB by the routing protocol, such as DVMRP or 531 Multiprotocol BGP." 532 ::= { inetMRouteEntry 20 } 534 inetMRouteHCOctets OBJECT-TYPE 535 SYNTAX Counter64 536 MAX-ACCESS read-only 537 STATUS current 539 Thaler,Adams,Siadak Experimental/Expires Dec 2000 10 540 DESCRIPTION 541 "The number of octets contained in IP datagrams which 542 were received from these sources and addressed to this 543 multicast group address, and which were forwarded by 544 this router. This object is a 64-bit version of 545 inetMRouteOctets." 546 ::= { inetMRouteEntry 21 } 548 -- 549 -- The IP Multicast Routing Next Hop Table 550 -- 552 inetMRouteNextHopTable OBJECT-TYPE 553 SYNTAX SEQUENCE OF InetMRouteNextHopEntry 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "The (conceptual) table containing information on the 558 next-hops on outgoing interfaces for routing IP 559 multicast datagrams. Each entry is one of a list of 560 next-hops on outgoing interfaces for particular sources 561 sending to a particular multicast group address." 562 ::= { inetMRoute 3 } 564 inetMRouteNextHopEntry OBJECT-TYPE 565 SYNTAX InetMRouteNextHopEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "An entry (conceptual row) in the list of next-hops on 570 outgoing interfaces to which IP multicast datagrams 571 from 572 particular sources to a IP multicast group address are 573 routed. Discontinuities in counters in this entry can 574 be detected by observing the value of 575 inetMRouteUpTime." 576 INDEX { inetMRouteNextHopGroupType, 577 inetMRouteNextHopGroup, 578 inetMRouteNextHopSourceType, 579 inetMRouteNextHopSource, 580 inetMRouteNextHopSourceMaskLen, 581 inetMRouteNextHopIfIndex, 582 inetMRouteNextHopAddressType, 583 inetMRouteNextHopAddress } 584 ::= { inetMRouteNextHopTable 1 } 586 InetMRouteNextHopEntry ::= SEQUENCE { 587 inetMRouteNextHopGroupType InetAddressType, 588 inetMRouteNextHopGroup InetAddress, 589 inetMRouteNextHopSourceType InetAddressType, 590 inetMRouteNextHopSource InetAddress, 591 inetMRouteNextHopSourceMaskLen INTEGER, 592 inetMRouteNextHopIfIndex InterfaceIndex, 594 Thaler,Adams,Siadak Experimental/Expires Dec 2000 11 595 inetMRouteNextHopAddressType InetAddressType, 596 inetMRouteNextHopAddress InetAddress, 597 inetMRouteNextHopPruned TruthValue, 598 inetMRouteNextHopUpTime TimeTicks, 599 inetMRouteNextHopExpiryTime TimeTicks, 600 inetMRouteNextHopClosestMemberHops Integer32, 601 inetMRouteNextHopProtocol IANAipMRouteProtocol, 602 inetMRouteNextHopPkts Counter32 603 } 605 inetMRouteNextHopGroupType OBJECT-TYPE 606 SYNTAX InetAddressType 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "A value indicating the address family of the address 611 contained in inetMRouteNextHopGroup. Legal values 612 correspond to the subset of address families for which 613 multicast forwarding is supported." 614 ::= { inetMRouteNextHopEntry 1 } 616 inetMRouteNextHopGroup OBJECT-TYPE 617 SYNTAX InetAddress 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "The IP multicast group for which this entry specifies 622 a 623 next-hop on an outgoing interface." 624 ::= { inetMRouteNextHopEntry 2 } 626 inetMRouteNextHopSourceType OBJECT-TYPE 627 SYNTAX InetAddressType 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "A value indicating the address family of the address 632 contained in inetMRouteNextHopSourceType. The value 633 MUST 634 be the same as the value of 635 inetMRouteNextHopGroupType." 636 ::= { inetMRouteNextHopEntry 3 } 638 inetMRouteNextHopSource OBJECT-TYPE 639 SYNTAX InetAddress 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "The network address which when combined with the 644 corresponding value of the mask specified in 645 inetMRouteNextHopSourceMaskLen identifies the sources 646 for which this entry specifies a next-hop on an 647 outgoing 649 Thaler,Adams,Siadak Experimental/Expires Dec 2000 12 650 interface." 651 ::= { inetMRouteNextHopEntry 4 } 653 inetMRouteNextHopSourceMaskLen OBJECT-TYPE 654 SYNTAX INTEGER (0..128) 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "The length in bits of the mask which when combined 659 with 660 the corresponding value specified in 661 inetMRouteNextHopSource identifies the sources for 662 which 663 this entry specifies a next-hop on an outgoing 664 interface." 665 ::= { inetMRouteNextHopEntry 5 } 667 inetMRouteNextHopIfIndex OBJECT-TYPE 668 SYNTAX InterfaceIndex 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "The ifIndex value of the interface for the outgoing 673 interface for this next-hop." 674 ::= { inetMRouteNextHopEntry 6 } 676 inetMRouteNextHopAddressType OBJECT-TYPE 677 SYNTAX InetAddressType 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "A value indicating the address family of the address 682 contained in inetMRouteNextHopAddressType. The value 683 MUST be the same as the value of 684 inetMRouteNextHopGroupType." 685 ::= { inetMRouteNextHopEntry 7 } 687 inetMRouteNextHopAddress OBJECT-TYPE 688 SYNTAX InetAddress 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "The address of the next-hop specific to this entry. 693 For most interfaces, this is identical to 694 inetMRouteNextHopGroup. NBMA interfaces, however, may 695 have multiple next-hop addresses out a single outgoing 696 interface." 697 ::= { inetMRouteNextHopEntry 8 } 699 inetMRouteNextHopPruned OBJECT-TYPE 700 SYNTAX TruthValue 701 MAX-ACCESS read-only 702 STATUS current 704 Thaler,Adams,Siadak Experimental/Expires Dec 2000 13 705 DESCRIPTION 706 "An indication of whether the outgoing interface and 707 next-hop represented by this entry is currently being 708 used to forward IP datagrams. The value 'false' 709 indicates it is currently being used; the value 'true' 710 indicates it is not." 711 ::= { inetMRouteNextHopEntry 9 } 713 inetMRouteNextHopUpTime OBJECT-TYPE 714 SYNTAX TimeTicks 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "The time since the multicast routing information 719 represented by this entry was learned by the router." 720 ::= { inetMRouteNextHopEntry 10 } 722 inetMRouteNextHopExpiryTime OBJECT-TYPE 723 SYNTAX TimeTicks 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The minimum amount of time remaining before this entry 728 will be aged out. If inetMRouteNextHopPruned is 729 pruned(1), the remaining time until the prune expires 730 and the state reverts to forwarding(2). Otherwise, the 731 remaining time until this entry is removed from the 732 table. The time remaining may be copied from 733 inetMRouteExpiryTime if the protocol in use for this 734 entry dos not specify next-hop timers. The value 0 735 indicates that the entry is not subject to aging." 736 ::= { inetMRouteNextHopEntry 11 } 738 inetMRouteNextHopClosestMemberHops OBJECT-TYPE 739 SYNTAX Integer32 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "The minimum number of hops between this router and any 744 member of this IP multicast group reached via this 745 next-hop on this outgoing interface. Any IP multicast 746 datagrams for the group which have a TTL (IPv4) or Hop 747 Count (IPv6) less than this number of hops will not be 748 forwarded to this next-hop." 749 ::= { inetMRouteNextHopEntry 12 } 751 inetMRouteNextHopProtocol OBJECT-TYPE 752 SYNTAX IANAipMRouteProtocol 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "The routing mechanism via which this next-hop was 757 learned." 759 Thaler,Adams,Siadak Experimental/Expires Dec 2000 14 760 ::= { inetMRouteNextHopEntry 13 } 762 inetMRouteNextHopPkts OBJECT-TYPE 763 SYNTAX Counter32 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "The number of packets which have been forwarded using 768 this route." 769 ::= { inetMRouteNextHopEntry 14 } 771 -- 772 -- The Multicast Routing Interface Table 773 -- 775 inetMRouteInterfaceTable OBJECT-TYPE 776 SYNTAX SEQUENCE OF InetMRouteInterfaceEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "The (conceptual) table containing multicast routing 781 information specific to interfaces." 782 ::= { inetMRoute 4 } 784 inetMRouteInterfaceEntry OBJECT-TYPE 785 SYNTAX InetMRouteInterfaceEntry 786 MAX-ACCESS not-accessible 787 STATUS current 788 DESCRIPTION 789 "An entry (conceptual row) containing the multicast 790 routing information for a particular interface." 791 INDEX { inetMRouteInterfaceIfIndex } 792 ::= { inetMRouteInterfaceTable 1 } 794 InetMRouteInterfaceEntry ::= SEQUENCE { 795 inetMRouteInterfaceIfIndex InterfaceIndex, 796 inetMRouteInterfaceTtl Integer32, 797 inetMRouteInterfaceProtocol IANAipMRouteProtocol, 798 inetMRouteInterfaceRateLimit Integer32, 799 inetMRouteInterfaceInMcastOctets Counter32, 800 inetMRouteInterfaceOutMcastOctets Counter32, 801 inetMRouteInterfaceHCInMcastOctets Counter64, 802 inetMRouteInterfaceHCOutMcastOctets Counter64 803 } 805 inetMRouteInterfaceIfIndex OBJECT-TYPE 806 SYNTAX InterfaceIndex 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "The ifIndex value of the interface for which this 811 entry 812 contains information." 814 Thaler,Adams,Siadak Experimental/Expires Dec 2000 15 815 ::= { inetMRouteInterfaceEntry 1 } 817 inetMRouteInterfaceTtl OBJECT-TYPE 818 SYNTAX Integer32 (0..255) 819 MAX-ACCESS read-write 820 STATUS current 821 DESCRIPTION 822 "The datagram TTL threshold for the interface. Any IP 823 multicast datagrams with a TTL (IPv4) or Hop Count 824 (IPv6) less than this threshold will not be forwarded 825 out the interface. The default value of 0 means all 826 multicast packets are forwarded out the interface." 827 ::= { inetMRouteInterfaceEntry 2 } 829 inetMRouteInterfaceProtocol OBJECT-TYPE 830 SYNTAX IANAipMRouteProtocol 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "The routing protocol running on this interface." 835 ::= { inetMRouteInterfaceEntry 3 } 837 inetMRouteInterfaceRateLimit OBJECT-TYPE 838 SYNTAX Integer32 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "The rate-limit, in kilobits per second, of forwarded 843 multicast traffic on the interface. A rate-limit of 0 844 indicates that no rate limiting is done." 845 DEFVAL { 0 } 846 ::= { inetMRouteInterfaceEntry 4 } 848 inetMRouteInterfaceInMcastOctets OBJECT-TYPE 849 SYNTAX Counter32 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "The number of octets of multicast packets that have 854 arrived on the interface, including framing characters. 855 This object is similar to ifInOctets in the Interfaces 856 MIB, except that only multicast packets are counted." 857 ::= { inetMRouteInterfaceEntry 5 } 859 inetMRouteInterfaceOutMcastOctets OBJECT-TYPE 860 SYNTAX Counter32 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The number of octets of multicast packets that have 865 been sent on the interface." 866 ::= { inetMRouteInterfaceEntry 6 } 868 Thaler,Adams,Siadak Experimental/Expires Dec 2000 16 869 inetMRouteInterfaceHCInMcastOctets OBJECT-TYPE 870 SYNTAX Counter64 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "The number of octets of multicast packets that have 875 arrived on the interface, including framing characters. 876 This object is a 64-bit version of 877 inetMRouteInterfaceInMcastOctets. It is similar to 878 ifHCInOctets in the Interfaces MIB, except that only 879 multicast packets are counted." 880 ::= { inetMRouteInterfaceEntry 7 } 882 inetMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 883 SYNTAX Counter64 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The number of octets of multicast packets that have 888 been sent on the interface. This object is a 64-bit 889 version of inetMRouteInterfaceOutMcastOctets." 890 ::= { inetMRouteInterfaceEntry 8 } 892 -- 893 -- The IP Multicast Scope Boundary Table 894 -- 895 inetMRouteBoundaryTable OBJECT 896 -TYPE 898 SYNTAX SEQUENCE OF InetMRouteBoundaryEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "The (conceptual) table listing the router's scoped 903 multicast address boundaries." 904 ::= { inetMRoute 5 } 906 inetMRouteBoundaryEntry OBJECT-TYPE 907 SYNTAX InetMRouteBoundaryEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "An entry (conceptual row) in the 912 inetMRouteBoundaryTable representing a scoped 913 boundary." 914 INDEX { inetMRouteBoundaryIfIndex, 915 inetMRouteBoundaryAddressType, 916 inetMRouteBoundaryAddress, 917 inetMRouteBoundaryAddressMaskLen } 918 ::= { inetMRouteBoundaryTable 1 } 920 InetMRouteBoundaryEntry ::= SEQUENCE { 921 inetMRouteBoundaryIfIndex InterfaceIndex, 922 inetMRouteBoundaryAddressType InetAddressType, 924 Thaler,Adams,Siadak Experimental/Expires Dec 2000 17 925 inetMRouteBoundaryAddress InetAddress, 926 inetMRouteBoundaryAddressMaskLen INTEGER, 927 inetMRouteBoundaryStatus RowStatus 928 } 930 inetMRouteBoundaryIfIndex OBJECT-TYPE 931 SYNTAX InterfaceIndex 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "The IfIndex value for the interface to which this 936 boundary applies. Packets with a destination address 937 in 938 the associated address/mask range will not be forwarded 939 out this interface." 940 ::= { inetMRouteBoundaryEntry 1 } 942 inetMRouteBoundaryAddressType OBJECT-TYPE 943 SYNTAX InetAddressType 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "A value indicating the address family of the address 948 contained in inetMRouteBoundaryAddress. Legal values 949 correspond to the subset of address families for which 950 multicast forwarding is supported." 951 ::= { inetMRouteBoundaryEntry 2 } 953 inetMRouteBoundaryAddress OBJECT-TYPE 954 SYNTAX InetAddress 955 MAX-ACCESS not-accessible 956 STATUS current 957 DESCRIPTION 958 "The group address which when combined with the 959 corresponding value of inetMRouteBoundaryAddressMaskLen 960 identifies the group range for which the scoped 961 boundary 962 exists. Scoped IPv4 addresses must come from the range 963 239.x.x.x as specified in RFC 2365. Scoped IPv6 964 addresses must come from range ff.nn.nn.nn.nn.nn.nn.nn, 965 where nn encodes the scope type and group identifier as 966 specified in RFC 2373." 967 ::= { inetMRouteBoundaryEntry 3 } 969 inetMRouteBoundaryAddressMaskLen OBJECT-TYPE 970 SYNTAX INTEGER (0..128) 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The length in bits of the mask which when combined 975 with 976 the corresponding value of inetMRouteBoundaryAddress 978 Thaler,Adams,Siadak Experimental/Expires Dec 2000 18 979 identifies the group range for which the scoped 980 boundary 981 exists." 982 ::= { inetMRouteBoundaryEntry 4 } 984 inetMRouteBoundaryStatus OBJECT-TYPE 985 SYNTAX RowStatus 986 MAX-ACCESS read-create 987 STATUS current 988 DESCRIPTION 989 "The status of this row, by which new entries may be 990 created, or old entries deleted from this table." 991 ::= { inetMRouteBoundaryEntry 5 } 993 -- 994 -- The IP Multicast Scope Name Table 995 -- 997 inetMRouteScopeNameTable OBJECT-TYPE 998 SYNTAX SEQUENCE OF InetMRouteScopeNameEntry 999 MAX-ACCESS not-accessible 1000 STATUS current 1001 DESCRIPTION 1002 "The (conceptual) table listing the multicast scope 1003 names." 1004 ::= { inetMRoute 6 } 1006 inetMRouteScopeNameEntry OBJECT-TYPE 1007 SYNTAX InetMRouteScopeNameEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "An entry (conceptual row) in the 1012 inetMRouteScopeNameTable representing a multicast scope 1013 name." 1014 INDEX { inetMRouteScopeNameAddressType, 1015 inetMRouteScopeNameAddress, 1016 inetMRouteScopeNameAddressMaskLen, 1017 IMPLIED inetMRouteScopeNameLanguage } 1018 ::= { inetMRouteScopeNameTable 1 } 1020 InetMRouteScopeNameEntry ::= SEQUENCE { 1021 inetMRouteScopeNameAddressType InetAddressType, 1022 inetMRouteScopeNameAddress InetAddress, 1023 inetMRouteScopeNameAddressMaskLen INTEGER, 1024 inetMRouteScopeNameLanguage LanguageTag, 1025 inetMRouteScopeNameString SnmpAdminString, 1026 inetMRouteScopeNameDefault TruthValue, 1027 inetMRouteScopeNameStatus RowStatus 1028 } 1030 inetMRouteScopeNameAddressType OBJECT-TYPE 1031 SYNTAX InetAddressType 1033 Thaler,Adams,Siadak Experimental/Expires Dec 2000 19 1034 MAX-ACCESS not-accessible 1035 STATUS current 1036 DESCRIPTION 1037 "A value indicating the address family of the address 1038 contained in inetMRouteScopeNameAddressType. Legal 1039 values correspond to the subset of address families for 1040 which multicast forwarding is supported." 1041 ::= { inetMRouteScopeNameEntry 1 } 1043 inetMRouteScopeNameAddress OBJECT-TYPE 1044 SYNTAX InetAddress 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "The group address which when combined with the 1049 corresponding value of 1050 inetMRouteScopeNameAddressMaskLen 1051 identifies the group range associated with the 1052 multicast 1053 scope. Scoped IPv4 addresses must come from the range 1054 239.x.x.x. Scoped IPv6 addresses must come from 1055 range ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the 1056 scope type and group identifier as specified in RFC 1057 2373." 1058 ::= { inetMRouteScopeNameEntry 2 } 1060 inetMRouteScopeNameAddressMaskLen OBJECT-TYPE 1061 SYNTAX INTEGER (0..128) 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "The length in bits of the mask which when combined 1066 with the corresponding value of 1067 inetMRouteScopeNameAddress identifies the group range 1068 associated with the multicast scope." 1069 ::= { inetMRouteScopeNameEntry 3 } 1071 inetMRouteScopeNameLanguage OBJECT-TYPE 1072 SYNTAX LanguageTag 1073 MAX-ACCESS not-accessible 1074 STATUS current 1075 DESCRIPTION 1076 "The RFC 1766-style language tag associated with the 1077 scope name." 1078 ::= { inetMRouteScopeNameEntry 4 } 1080 inetMRouteScopeNameString OBJECT-TYPE 1081 SYNTAX SnmpAdminString 1082 MAX-ACCESS read-create 1083 STATUS current 1084 DESCRIPTION 1085 "The textual name associated with the multicast scope. 1086 The value of this object should be suitable for 1088 Thaler,Adams,Siadak Experimental/Expires Dec 2000 20 1089 displaying to end-users, such as when allocating a 1090 multicast address in this scope. When no name is 1091 specified, the default value of this object for IPv4 1092 should be the string 239.x.x.x/y with x and y 1093 replaced appropriately to describe the address and mask 1094 length associated with the scope. Scoped IPv6 addresses 1095 must come from range ff.nn.nn.nn.nn.nn.nn.nn, where nn 1096 encodes the scope type and group identifier." 1098 ::= { inetMRouteScopeNameEntry 5 } 1100 inetMRouteScopeNameDefault OBJECT-TYPE 1101 SYNTAX TruthValue 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "If true, indicates a preference that the name in the 1106 following language should be used by applications if no 1107 name is available in a desired language." 1108 DEFVAL { false } 1109 ::= { inetMRouteScopeNameEntry 6 } 1111 inetMRouteScopeNameStatus OBJECT-TYPE 1112 SYNTAX RowStatus 1113 MAX-ACCESS read-create 1114 STATUS current 1115 DESCRIPTION 1116 "The status of this row, by which new entries may be 1117 created, or old entries deleted from this table." 1118 ::= { inetMRouteScopeNameEntry 7 } 1119 -- conformance information 1121 inetMRouteMIBConformance 1122 OBJECT IDENTIFIER ::= { inetMRouteStdMIB 2 } 1123 inetMRouteMIBCompliances 1124 OBJECT IDENTIFIER ::= { inetMRouteMIBConformance 1125 1 } 1126 inetMRouteMIBGroups OBJECT IDENTIFIER ::= { 1127 inetMRouteMIBConformance 2 } 1129 -- compliance statements 1131 inetMRouteMIBCompliance MODULE-COMPLIANCE 1132 STATUS current 1133 DESCRIPTION 1134 "The compliance statement for the IP Multicast MIB." 1135 MODULE -- this module 1136 MANDATORY-GROUPS { inetMRouteMIBBasicGroup, 1137 inetMRouteMIBRouteGroup} 1139 GROUP inetMRouteMIBBoundaryGroup 1140 DESCRIPTION 1141 "This group is mandatory if the router supports 1143 Thaler,Adams,Siadak Experimental/Expires Dec 2000 21 1144 administratively-scoped multicast address boundaries." 1146 OBJECT inetMRouteBoundaryStatus 1147 MIN-ACCESS read-only 1148 DESCRIPTION 1149 "Write access is not required." 1151 OBJECT inetMRouteScopeNameStatus 1152 MIN-ACCESS read-only 1153 DESCRIPTION 1154 "Write access is not required." 1156 GROUP inetMRouteMIBHCInterfaceGroup 1157 DESCRIPTION 1158 "This group is mandatory only for those network 1159 interfaces for which the value of the corresponding 1160 instance of ifSpeed is greater than 20,000,000 1161 bits/second." 1163 ::= { inetMRouteMIBCompliances 1 } 1165 -- units of conformance 1166 inetMRouteMIBBasicGroup OBJECT-GROUP 1167 OBJECTS { inetMRouteEnabled, inetMRouteEntryCount, 1168 inetMRouteUpstreamNeighborType, 1169 inetMRouteUpstreamNeighbor, 1170 inetMRouteInIfIndex, 1171 inetMRouteUpTime, inetMRouteExpiryTime, 1172 inetMRouteNextHopPruned, 1173 inetMRouteNextHopUpTime, 1174 inetMRouteNextHopExpiryTime, 1175 inetMRouteNextHopProtocol, 1176 inetMRouteNextHopPkts, 1177 inetMRouteInterfaceTtl, 1178 inetMRouteInterfaceProtocol, 1179 inetMRouteInterfaceRateLimit, 1180 inetMRouteInterfaceInMcastOctets, 1181 inetMRouteInterfaceOutMcastOctets, 1182 inetMRouteProtocol 1183 } 1184 STATUS current 1185 DESCRIPTION 1186 "A collection of objects to support basic management of 1187 IP Multicast routing." 1188 ::= { inetMRouteMIBGroups 1 } 1190 inetMRouteMIBHopCountGroup OBJECT-GROUP 1191 OBJECTS { inetMRouteNextHopClosestMemberHops } 1192 STATUS current 1193 DESCRIPTION 1194 "A collection of objects to support management of the 1195 use of hop counts in IP Multicast routing." 1196 ::= { inetMRouteMIBGroups 2 } 1198 Thaler,Adams,Siadak Experimental/Expires Dec 2000 22 1199 inetMRouteMIBBoundaryGroup OBJECT-GROUP 1200 OBJECTS { inetMRouteBoundaryStatus, inetMRouteScopeNameString, 1201 inetMRouteScopeNameDefault, inetMRouteScopeNameStatus 1202 } 1203 STATUS current 1204 DESCRIPTION 1205 "A collection of objects to support management of 1206 scoped 1207 multicast address boundaries." 1208 ::= { inetMRouteMIBGroups 3 } 1210 inetMRouteMIBPktsOutGroup OBJECT-GROUP 1211 OBJECTS { inetMRouteNextHopPkts } 1212 STATUS current 1213 DESCRIPTION 1214 "A collection of objects to support management of 1215 packet 1216 counters for each outgoing interface entry of a route." 1217 ::= { inetMRouteMIBGroups 4 } 1219 inetMRouteMIBHCInterfaceGroup OBJECT-GROUP 1220 OBJECTS { inetMRouteInterfaceHCInMcastOctets, 1221 inetMRouteInterfaceHCOutMcastOctets, 1222 inetMRouteHCOctets } 1223 STATUS current 1224 DESCRIPTION 1225 "A collection of objects providing information specific 1226 to high speed (greater than 20,000,000 bits/second) 1227 network interfaces." 1228 ::= { inetMRouteMIBGroups 5 } 1230 inetMRouteMIBRouteGroup OBJECT-GROUP 1231 OBJECTS { inetMRouteRtProto, inetMRouteRtAddressType, 1232 inetMRouteRtAddress, 1233 inetMRouteRtMaskLen , inetMRouteRtType } 1234 STATUS current 1235 DESCRIPTION 1236 "A collection of objects providing information on the 1237 relationship between multicast routing information, 1238 and the IP Forwarding Table." 1239 ::= { inetMRouteMIBGroups 6 } 1241 inetMRouteMIBPktsGroup OBJECT-GROUP 1242 OBJECTS { inetMRoutePkts, inetMRouteDifferentInIfPackets, 1243 inetMRouteOctets } 1244 STATUS current 1245 DESCRIPTION 1246 "A collection of objects to support management of 1247 packet 1248 counters for each forwarding entry." 1249 ::= { inetMRouteMIBGroups 7 } 1251 Thaler,Adams,Siadak Experimental/Expires Dec 2000 23 1252 END 1254 6. IANA Considerations 1255 The ipMRouteRtProto, ipMRouteNextHopProtocol, 1256 ipMRouteInterfaceProtocol, and ipMRouteProtocol use textual 1257 conventions imported from the IANA-RTPROTO-MIB. The purpose of 1258 defining these textual conventions in a separate MIB module is to 1259 allow additional values to be defined without having to issue a new 1260 version of this document. The Internet Assigned Numbers Authority 1261 (IANA) is responsible for the assignment of all Internet numbers, 1262 including various SNMP- related numbers; it will administer the 1263 values associated with these textual conventions. The rules for 1264 additions or changes to the IANA-RTPROTO-MIB are outlined in the 1265 DESCRIPTION clause associated with its MODULE-IDENTITY statement. 1266 The current versions of the IANA-RTPROTO-MIB can be accessed from 1267 the IANA home page at: "http://www.iana.org/". 1269 7. Security Considerations 1271 This MIB contains readable objects whose values provide information 1272 related to multicast routing, including information on what 1273 machines are sending to which groups. There are also a number of 1274 objects that have a MAX-ACCESS clause of read-write and/or read- 1275 create, such as those which allow an administrator to configure 1276 multicast boundaries. 1278 While unauthorized access to the readable objects is relatively 1279 innocuous, unauthorized access to the write-able objects could 1280 cause a denial of service, or could cause wider distribution of 1281 packets intended only for local distribution. Hence, the support 1282 for SET operations in a non-secure environment without proper 1283 protection can have a negative effect on network operations. 1285 SNMPv1 by itself is such an insecure environment. Even if the 1286 network itself is secure (for example by using IPSec), even then, 1287 there is no control as to who on the secure network is allowed to 1288 access and SET (change/create/delete) the objects in this MIB. 1290 It is recommended that the implementers consider the security 1291 features as provided by the SNMPv3 framework. Specifically, the 1292 use of the User-based Security Model RFC 2574 [20] and the View- 1293 based Access Control Model RFC 2575 [23] is recommended. 1295 It is then a customer/user responsibility to ensure that the SNMP 1296 entity giving access to this MIB, is properly configured to give 1297 access to those objects only to those principals (users) that have 1298 legitimate rights to access them. 1300 8. Intellectual Property Notice 1302 The IETF takes no position regarding the validity or scope of any 1304 Thaler,Adams,Siadak Experimental/Expires Dec 2000 24 1305 intellectual property or other rights that might be claimed to 1306 pertain to the implementation or use of the technology described in 1307 this document or the extent to which any license under such rights 1308 might or might not be available; neither does it represent that it 1309 has made any effort to identify any such rights. Information on 1310 the IETF's procedures with respect to rights in standards-track and 1311 standards-related documentation can be found in BCP-11. Copies of 1312 claims of rights made available for publication and any assurances 1313 of licenses to be made available, or the result of an attempt made 1314 to obtain a general license or permission for the use of such 1315 proprietary rights by implementers or users of this specification 1316 can be obtained from the IETF Secretariat. 1318 The IETF invites any interested party to bring to its attention any 1319 copyrights, patents or patent applications, or other proprietary 1320 rights which may cover technology that may be required to practice 1321 this standard. Please address the information to the IETF 1322 Executive 1323 Director. 1325 10. Acknowledgements 1327 This MIB module was updated based on feedback from the IETF's 1328 Inter- 1329 Domain Multicast Routing (IDMR) Working Group. 1331 11. Authors' Addresses 1333 Dave Thaler 1334 Microsoft Corporation 1335 One Microsoft Way 1336 Redmond, WA 98052-6399 1337 Phone: +1 425 703 8835 1338 EMail: dthaler@dthaler.microsoft.com 1340 Andrew Adams 1341 Merit Network, Inc. 1342 4251 Plymouth Rd. 1343 Ann Arbor, MI 48105-2785 1344 Phone: +1 734 763-6378 1345 EMail: ala@merit.edu 1347 William Siadak 1348 Merit Network, Inc. 1349 4251 Plymouth Rd. 1350 Ann Arbor, MI 48105-2785 1351 Phone: +1 734 936 2035 1352 EMail: wfs@merit.edu 1354 12. References 1356 Thaler,Adams,Siadak Experimental/Expires Dec 2000 25 1357 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1358 9, RFC 2026, October 1996. 1360 2 Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1361 thesis, Electrical Engineering Dept., Stanford University, 1362 December 1991. 1364 3 Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1365 Multicast Routing Protocol", RFC 1075, November 1988. 1367 4 Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, 1368 S.,Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1369 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1370 Specification", RFC 2362, June 1998. 1372 5 Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1373 and L. Wei, "Protocol Independent Multicast Version 2, Dense 1374 Mode Specification". Work in progress, May 1997. 1376 6 Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1378 7 Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1379 Routing", RFC 2189, September 1997. 1381 8 McCloghrie K., Farinacci D, Thaler D., _IPv4 Multicast Routing 1382 MIB_,Internet Draft, January 31, 2000 1384 9 Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1385 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1386 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1387 April 1999. 1389 10 Rose, M., and K. McCloghrie, "Structure and Identification of 1390 Management Information for TCP/IP-based Internets", RFC 1155, 1391 STD 16, Performance Systems International, Hughes LAN Systems, 1392 May 1990. 1394 11 Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1395 1212, STD 16, Performance Systems International, Hughes LAN 1396 Systems, March 1991. 1398 12 M. Rose, "A Convention for Defining Traps for use with the 1399 SNMP", RFC 1215, Performance Systems International, March 1991. 1401 13 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1402 M., and S. Waldbusser, "Structure of Management Information 1403 Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, 1404 TU Braunschweig, SNMP Research, First Virtual Holdings, 1405 International Network Services, April 1999. 1406 14 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1407 M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 1409 Thaler,Adams,Siadak Experimental/Expires Dec 2000 26 1410 2579, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 1411 Research, First Virtual Holdings, International Network 1412 Services, April 1999. 1414 15 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1415 M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 1416 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 1417 Research, First Virtual Holdings, International Network 1418 Services, April 1999. 1420 16 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1421 Network Management Protocol", RFC 1157, STD 15, SNMP Research, 1422 Performance Systems International, Performance Systems 1423 International, MIT Laboratory for Computer Science, May 1990. 1425 17 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1426 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1427 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1428 Inc., International Network Services, January 1996. 1430 18 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1431 "Transport Mappings for Version 2 of the Simple Network 1432 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1433 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1434 Network Services, January 1996. 1436 19 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1437 Processing and Dispatching for the Simple Network Management 1438 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 1439 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1440 April 1999. 1442 20 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1443 for version 3 of the Simple Network Management Protocol 1444 (SNMPv3)", RFC 2574, IBM T. J. Watson Research, April 1999. 1446 21 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1447 Operations for Version 2 of the Simple Network Management 1448 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 1449 Systems, Inc., Dover Beach Consulting, Inc., International 1450 Network Services, January 1996. 1452 22 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1453 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1454 Systems, April 1999. 1456 23 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1457 Control Model (VACM) for the Simple Network Management Protocol 1458 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, 1459 Inc., Cisco Systems, Inc., April 1999. 1461 Thaler,Adams,Siadak Experimental/Expires Dec 2000 27 1462 24 Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1463 23, July 1998. 1465 11. Full Copyright Statement 1467 Copyright (C) The Internet Society (1999). All Rights Reserved. 1468 This document and translations of it may be copied and furnished to 1469 others, and derivative works that comment on or otherwise explain it 1470 or assist in its implmentation may be prepared, copied, published 1471 and distributed, in whole or in part, without restriction of any 1472 kind, provided that the above copyright notice and this paragraph 1473 are included on all such copies and derivative works. However, this 1474 document itself may not be modified in any way, such as by removing 1475 the copyright notice or references to the Internet Society or other 1476 Internet organizations, except as needed for the purpose of 1477 developing Internet standards in which case the procedures for 1478 copyrights defined in the Internet Standards process must be 1479 followed, or as required to translate it into languages other than 1480 English. 1482 The limited permissions granted above are perpetual and will not 1483 berevoked by the Internet Society or its successors or assigns. 1485 This document and the information contained herein is provided on an 1486 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1487 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1488 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1489 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1490 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1492 Table of Contents 1493 1. Abstract........................................................1 1494 2. Introduction....................................................1 1495 3. The SNMP Management Framework...................................1 1496 4. Overview........................................................2 1497 5. Definitions.....................................................3 1498 6. IANA Considerations............................................24 1499 7. Security Considerations........................................24 1500 8. Intellectual Property Notice...................................24 1501 10. Acknowledgements..............................................25 1502 11. Authors' Addresses............................................25 1503 12. References....................................................25 1504 11. Full Copyright Statement......................................28 1506 Thaler,Adams,Siadak Experimental/Expires Dec 2000 28