idnits 2.17.1 draft-ietf-idmr-multicast-routmib-13.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 32 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 33 pages 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 is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. 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 (31 January 2000) is 8850 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) -- Looks like a reference, but probably isn't: '17-21' on line 48 == Unused Reference: '17' is defined on line 1335, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1338, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1343, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1347, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1349, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. '16' ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '17') ** Obsolete normative reference: RFC 2362 (ref. '18') (Obsoleted by RFC 4601, RFC 5059) -- Possible downref: Non-RFC (?) normative reference: ref. '19' ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '20') ** Downref: Normative reference to an Historic RFC: RFC 2189 (ref. '21') Summary: 18 errors (**), 0 flaws (~~), 9 warnings (==), 5 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 July 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 31 January 2000 8 IPv4 Multicast Routing MIB 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with all 14 provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering Task 17 Force (IETF), its areas, and its working groups. Note that other groups 18 may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference material 23 or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Copyright Notice 33 Copyright (C) The Internet Society (1999). All Rights Reserved. 35 Draft IPv4 Multicast Routing MIB January 2000 37 1. Abstract 39 This memo defines an experimental portion of the Management Information 40 Base (MIB) for use with network management protocols in the Internet 41 community. In particular, it describes managed objects used for 42 managing IP Multicast Routing for IPv4, independent of the specific 43 multicast routing protocol in use. 45 2. Introduction 47 This MIB describes objects used for managing IP Multicast Routing [16], 48 independent of the specific multicast routing protocol [17-21] in use. 49 Managed objects specific to particular multicast routing protocols are 50 specified elsewhere. Similarly, this MIB does not support management of 51 multicast routing for other address families, including IPv6. Such 52 management may be supported by other MIBs. 54 3. The SNMP Management Framework 56 The SNMP Management Framework presently consists of five major 57 components: 59 o An overall architecture, described in RFC 2571 [1]. 61 o Mechanisms for describing and naming objects and events for the 62 purpose of management. The first version of this Structure of 63 Management Information (SMI) is called SMIv1 and described in RFC 64 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 65 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 67 o Message protocols for transferring management information. The 68 first version of the SNMP message protocol is called SNMPv1 and 69 described in RFC 1157 [8]. A second version of the SNMP message 70 protocol, which is not an Internet standards track protocol, is 71 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 72 The third version of the message protocol is called SNMPv3 and 73 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 75 o Protocol operations for accessing management information. The first 76 set of protocol operations and associated PDU formats is described 77 in RFC 1157 [8]. A second set of protocol operations and associated 78 PDU formats is described in RFC 1905 [13]. 80 Draft IPv4 Multicast Routing MIB January 2000 82 o A set of fundamental applications described in RFC 2573 [14] and 83 the view-based access control mechanism described in RFC 2575 [15]. 85 Managed objects are accessed via a virtual information store, termed the 86 Management Information Base or MIB. Objects in the MIB are defined 87 using the mechanisms defined in the SMI. 89 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 90 conforming to the SMIv1 can be produced through the appropriate 91 translations. The resulting translated MIB must be semantically 92 equivalent, except where objects or events are omitted because no 93 translation is possible (use of Counter64). Some machine readable 94 information in SMIv2 will be converted into textual descriptions in 95 SMIv1 during the translation process. However, this loss of machine 96 readable information is not considered to change the semantics of the 97 MIB. 99 4. Overview 101 This MIB module contains one scalar and five tables. The tables are: 103 (1) the IP Multicast Route Table containing multicast routing 104 information for IP datagrams sent by particular sources to the IP 105 multicast groups known to a router. 107 (2) the IP Multicast Routing Next Hop Table containing information on 108 the next-hops for the routing IP multicast datagrams. Each entry 109 is one of a list of next-hops on outgoing interfaces for 110 particular sources sending to a particular multicast group 111 address. 113 (3) the IP Multicast Routing Interface Table containing multicast 114 routing information specific to interfaces. 116 (4) the IP Multicast Scope Boundary Table containing the boundaries 117 configured for multicast scopes [22]. 119 (5) the IP Multicast Scope Name Table containing human-readable names 120 of multicast scope. 122 Draft IPv4 Multicast Routing MIB January 2000 124 5. Definitions 126 IPMROUTE-STD-MIB DEFINITIONS ::= BEGIN 128 IMPORTS 129 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 130 Integer32, Counter32, Counter64, Gauge32, 131 IpAddress, TimeTicks FROM SNMPv2-SMI 132 RowStatus, TEXTUAL-CONVENTION, 133 TruthValue FROM SNMPv2-TC 134 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 135 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 136 InterfaceIndexOrZero, 137 InterfaceIndex FROM IF-MIB 138 IANAipRouteProtocol, 139 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB; 141 ipMRouteStdMIB MODULE-IDENTITY 142 LAST-UPDATED "200001311200Z" -- January 31, 2000 143 ORGANIZATION "IETF IDMR Working Group" 144 CONTACT-INFO 145 " Dave Thaler 146 Microsoft Corporation 147 One Microsoft Way 148 Redmond, WA 98052-6399 149 US 151 Phone: +1 425 703 8835 152 EMail: dthaler@dthaler.microsoft.com" 153 DESCRIPTION 154 "The MIB module for management of IP Multicast routing, but 155 independent of the specific multicast routing protocol in 156 use." 157 REVISION "200001311200Z" -- January 31, 2000 158 DESCRIPTION 159 "Initial version, published as RFC xxxx (to be filled in by 160 RFC-Editor)." 161 ::= { mib-2 XX } 162 -- NOTE TO RFC EDITOR: When this document is published as 163 -- an RFC, replace XX with IANA-assigned number, 164 -- and delete this comment. 166 -- Textual Conventions 168 LanguageTag ::= TEXTUAL-CONVENTION 170 Draft IPv4 Multicast Routing MIB January 2000 172 DISPLAY-HINT "100a" 173 STATUS current 174 DESCRIPTION 175 "An RFC 1766-style language tag, with all alphabetic 176 characters converted to lowercase. This restriction is 177 intended to make the lexical ordering imposed by SNMP useful 178 when applied to language tags. Note that it is 179 theoretically possible for a valid language tag to exceed 180 the allowed length of this syntax, and thus be impossible to 181 represent with this syntax. Sampling of language tags in 182 current use on the Internet suggests that this limit does 183 not pose a serious problem in practice." 184 SYNTAX OCTET STRING (SIZE (1..100)) 186 -- Top-level structure of the MIB 188 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 } 190 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 192 Draft IPv4 Multicast Routing MIB January 2000 194 -- the IP Multicast Routing MIB-Group 195 -- 196 -- a collection of objects providing information about 197 -- IP Multicast Groups 199 ipMRouteEnable OBJECT-TYPE 200 SYNTAX INTEGER { enabled(1), disabled(2) } 201 MAX-ACCESS read-write 202 STATUS current 203 DESCRIPTION 204 "The enabled status of IP Multicast routing on this router." 205 ::= { ipMRoute 1 } 207 ipMRouteEntryCount OBJECT-TYPE 208 SYNTAX Gauge32 209 MAX-ACCESS read-only 210 STATUS current 211 DESCRIPTION 212 "The number of rows in the ipMRouteTable. This can be used 213 to monitor the multicast routing table size." 214 ::= { ipMRoute 7 } 216 ipMRouteTable OBJECT-TYPE 217 SYNTAX SEQUENCE OF IpMRouteEntry 218 MAX-ACCESS not-accessible 219 STATUS current 220 DESCRIPTION 221 "The (conceptual) table containing multicast routing 222 information for IP datagrams sent by particular sources to 223 the IP multicast groups known to this router." 224 ::= { ipMRoute 2 } 226 Draft IPv4 Multicast Routing MIB January 2000 228 ipMRouteEntry OBJECT-TYPE 229 SYNTAX IpMRouteEntry 230 MAX-ACCESS not-accessible 231 STATUS current 232 DESCRIPTION 233 "An entry (conceptual row) containing the multicast routing 234 information for IP datagrams from a particular source and 235 addressed to a particular IP multicast group address. 236 Discontinuities in counters in this entry can be detected by 237 observing the value of ipMRouteUpTime." 238 INDEX { ipMRouteGroup, 239 ipMRouteSource, 240 ipMRouteSourceMask } 241 ::= { ipMRouteTable 1 } 243 IpMRouteEntry ::= SEQUENCE { 244 ipMRouteGroup IpAddress, 245 ipMRouteSource IpAddress, 246 ipMRouteSourceMask IpAddress, 247 ipMRouteUpstreamNeighbor IpAddress, 248 ipMRouteInIfIndex InterfaceIndexOrZero, 249 ipMRouteUpTime TimeTicks, 250 ipMRouteExpiryTime TimeTicks, 251 ipMRoutePkts Counter32, 252 ipMRouteDifferentInIfPackets Counter32, 253 ipMRouteOctets Counter32, 254 ipMRouteProtocol IANAipMRouteProtocol, 255 ipMRouteRtProto IANAipRouteProtocol, 256 ipMRouteRtAddress IpAddress, 257 ipMRouteRtMask IpAddress, 258 ipMRouteRtType INTEGER, 259 ipMRouteHCOctets Counter64 260 } 262 ipMRouteGroup OBJECT-TYPE 263 SYNTAX IpAddress 264 MAX-ACCESS not-accessible 265 STATUS current 266 DESCRIPTION 267 "The IP multicast group address for which this entry 268 contains multicast routing information." 269 ::= { ipMRouteEntry 1 } 271 ipMRouteSource OBJECT-TYPE 272 SYNTAX IpAddress 274 Draft IPv4 Multicast Routing MIB January 2000 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "The network address which when combined with the 280 corresponding value of ipMRouteSourceMask identifies the 281 sources for which this entry contains multicast routing 282 information." 283 ::= { ipMRouteEntry 2 } 285 ipMRouteSourceMask OBJECT-TYPE 286 SYNTAX IpAddress 287 MAX-ACCESS not-accessible 288 STATUS current 289 DESCRIPTION 290 "The network mask which when combined with the corresponding 291 value of ipMRouteSource identifies the sources for which 292 this entry contains multicast routing information." 293 ::= { ipMRouteEntry 3 } 295 ipMRouteUpstreamNeighbor OBJECT-TYPE 296 SYNTAX IpAddress 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The address of the upstream neighbor (e.g., RPF neighbor) 301 from which IP datagrams from these sources to this multicast 302 address are received, or 0.0.0.0 if the upstream neighbor is 303 unknown (e.g., in CBT)." 304 ::= { ipMRouteEntry 4 } 306 ipMRouteInIfIndex OBJECT-TYPE 307 SYNTAX InterfaceIndexOrZero 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The value of ifIndex for the interface on which IP 312 datagrams sent by these sources to this multicast address 313 are received. A value of 0 indicates that datagrams are not 314 subject to an incoming interface check, but may be accepted 315 on multiple interfaces (e.g., in CBT)." 316 ::= { ipMRouteEntry 5 } 318 ipMRouteUpTime OBJECT-TYPE 319 SYNTAX TimeTicks 320 MAX-ACCESS read-only 322 Draft IPv4 Multicast Routing MIB January 2000 324 STATUS current 325 DESCRIPTION 326 "The time since the multicast routing information 327 represented by this entry was learned by the router." 328 ::= { ipMRouteEntry 6 } 330 ipMRouteExpiryTime OBJECT-TYPE 331 SYNTAX TimeTicks 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The minimum amount of time remaining before this entry will 336 be aged out. The value 0 indicates that the entry is not 337 subject to aging." 338 ::= { ipMRouteEntry 7 } 340 ipMRoutePkts OBJECT-TYPE 341 SYNTAX Counter32 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The number of packets which this router has received from 346 these sources and addressed to this multicast group 347 address." 348 ::= { ipMRouteEntry 8 } 350 ipMRouteDifferentInIfPackets OBJECT-TYPE 351 SYNTAX Counter32 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of packets which this router has received from 356 these sources and addressed to this multicast group address, 357 which were dropped because they were not received on the 358 interface indicated by ipMRouteInIfIndex. Packets which are 359 not subject to an incoming interface check (e.g., using CBT) 360 are not counted." 361 ::= { ipMRouteEntry 9 } 363 ipMRouteOctets OBJECT-TYPE 364 SYNTAX Counter32 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The number of octets contained in IP datagrams which were 370 Draft IPv4 Multicast Routing MIB January 2000 372 received from these sources and addressed to this multicast 373 group address, and which were forwarded by this router." 374 ::= { ipMRouteEntry 10 } 376 ipMRouteProtocol OBJECT-TYPE 377 SYNTAX IANAipMRouteProtocol 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The multicast routing protocol via which this multicast 382 forwarding entry was learned." 383 ::= { ipMRouteEntry 11 } 385 ipMRouteRtProto OBJECT-TYPE 386 SYNTAX IANAipRouteProtocol 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The routing mechanism via which the route used to find the 391 upstream or parent interface for this multicast forwarding 392 entry was learned. Inclusion of values for routing 393 protocols is not intended to imply that those protocols need 394 be supported." 395 ::= { ipMRouteEntry 12 } 397 ipMRouteRtAddress OBJECT-TYPE 398 SYNTAX IpAddress 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The address portion of the route used to find the upstream 403 or parent interface for this multicast forwarding entry." 404 ::= { ipMRouteEntry 13 } 406 ipMRouteRtMask OBJECT-TYPE 407 SYNTAX IpAddress 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The mask associated with the route used to find the upstream 412 or parent interface for this multicast forwarding entry." 413 ::= { ipMRouteEntry 14 } 415 ipMRouteRtType OBJECT-TYPE 416 SYNTAX INTEGER { 418 Draft IPv4 Multicast Routing MIB January 2000 420 unicast (1), -- Unicast route used in multicast RIB 421 multicast (2) -- Multicast route 422 } 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The reason the given route was placed in the (logical) 427 multicast Routing Information Base (RIB). A value of 428 unicast means that the route would normally be placed only 429 in the unicast RIB, but was placed in the multicast RIB 430 (instead or in addition) due to local configuration, such as 431 when running PIM over RIP. A value of multicast means that 432 the route was explicitly added to the multicast RIB by the 433 routing protocol, such as DVMRP or Multiprotocol BGP." 434 ::= { ipMRouteEntry 15 } 436 ipMRouteHCOctets OBJECT-TYPE 437 SYNTAX Counter64 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The number of octets contained in IP datagrams which were 442 received from these sources and addressed to this multicast 443 group address, and which were forwarded by this router. 444 This object is a 64-bit version of ipMRouteOctets." 445 ::= { ipMRouteEntry 16 } 447 Draft IPv4 Multicast Routing MIB January 2000 449 -- 450 -- The IP Multicast Routing Next Hop Table 451 -- 453 ipMRouteNextHopTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "The (conceptual) table containing information on the next- 459 hops on outgoing interfaces for routing IP multicast 460 datagrams. Each entry is one of a list of next-hops on 461 outgoing interfaces for particular sources sending to a 462 particular multicast group address." 463 ::= { ipMRoute 3 } 465 ipMRouteNextHopEntry OBJECT-TYPE 466 SYNTAX IpMRouteNextHopEntry 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "An entry (conceptual row) in the list of next-hops on 471 outgoing interfaces to which IP multicast datagrams from 472 particular sources to a IP multicast group address are 473 routed. Discontinuities in counters in this entry can be 474 detected by observing the value of ipMRouteUpTime." 475 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 476 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 477 ipMRouteNextHopAddress } 478 ::= { ipMRouteNextHopTable 1 } 480 Draft IPv4 Multicast Routing MIB January 2000 482 IpMRouteNextHopEntry ::= SEQUENCE { 483 ipMRouteNextHopGroup IpAddress, 484 ipMRouteNextHopSource IpAddress, 485 ipMRouteNextHopSourceMask IpAddress, 486 ipMRouteNextHopIfIndex InterfaceIndex, 487 ipMRouteNextHopAddress IpAddress, 488 ipMRouteNextHopState INTEGER, 489 ipMRouteNextHopUpTime TimeTicks, 490 ipMRouteNextHopExpiryTime TimeTicks, 491 ipMRouteNextHopClosestMemberHops Integer32, 492 ipMRouteNextHopProtocol IANAipMRouteProtocol, 493 ipMRouteNextHopPkts Counter32 494 } 496 ipMRouteNextHopGroup OBJECT-TYPE 497 SYNTAX IpAddress 498 MAX-ACCESS not-accessible 499 STATUS current 500 DESCRIPTION 501 "The IP multicast group for which this entry specifies a 502 next-hop on an outgoing interface." 503 ::= { ipMRouteNextHopEntry 1 } 505 ipMRouteNextHopSource OBJECT-TYPE 506 SYNTAX IpAddress 507 MAX-ACCESS not-accessible 508 STATUS current 509 DESCRIPTION 510 "The network address which when combined with the 511 corresponding value of ipMRouteNextHopSourceMask identifies 512 the sources for which this entry specifies a next-hop on an 513 outgoing interface." 514 ::= { ipMRouteNextHopEntry 2 } 516 ipMRouteNextHopSourceMask OBJECT-TYPE 517 SYNTAX IpAddress 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "The network mask which when combined with the corresponding 522 value of ipMRouteNextHopSource identifies the sources for 523 which this entry specifies a next-hop on an outgoing 524 interface." 525 ::= { ipMRouteNextHopEntry 3 } 527 Draft IPv4 Multicast Routing MIB January 2000 529 ipMRouteNextHopIfIndex OBJECT-TYPE 530 SYNTAX InterfaceIndex 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "The ifIndex value of the interface for the outgoing 535 interface for this next-hop." 536 ::= { ipMRouteNextHopEntry 4 } 538 ipMRouteNextHopAddress OBJECT-TYPE 539 SYNTAX IpAddress 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "The address of the next-hop specific to this entry. For 544 most interfaces, this is identical to ipMRouteNextHopGroup. 545 NBMA interfaces, however, may have multiple next-hop 546 addresses out a single outgoing interface." 547 ::= { ipMRouteNextHopEntry 5 } 549 ipMRouteNextHopState OBJECT-TYPE 550 SYNTAX INTEGER { pruned(1), forwarding(2) } 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "An indication of whether the outgoing interface and next- 555 hop represented by this entry is currently being used to 556 forward IP datagrams. The value 'forwarding' indicates it 557 is currently being used; the value 'pruned' indicates it is 558 not." 559 ::= { ipMRouteNextHopEntry 6 } 561 ipMRouteNextHopUpTime OBJECT-TYPE 562 SYNTAX TimeTicks 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The time since the multicast routing information 567 represented by this entry was learned by the router." 568 ::= { ipMRouteNextHopEntry 7 } 570 ipMRouteNextHopExpiryTime OBJECT-TYPE 571 SYNTAX TimeTicks 572 MAX-ACCESS read-only 573 STATUS current 575 Draft IPv4 Multicast Routing MIB January 2000 577 DESCRIPTION 578 "The minimum amount of time remaining before this entry will 579 be aged out. If ipMRouteNextHopState is pruned(1), the 580 remaining time until the prune expires and the state reverts 581 to forwarding(2). Otherwise, the remaining time until this 582 entry is removed from the table. The time remaining may be 583 copied from ipMRouteExpiryTime if the protocol in use for 584 this entry dos not specify next-hop timers. The value 0 585 indicates that the entry is not subject to aging." 586 ::= { ipMRouteNextHopEntry 8 } 588 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 589 SYNTAX Integer32 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "The minimum number of hops between this router and any 594 member of this IP multicast group reached via this next-hop 595 on this outgoing interface. Any IP multicast datagrams for 596 the group which have a TTL less than this number of hops 597 will not be forwarded to this next-hop." 598 ::= { ipMRouteNextHopEntry 9 } 600 ipMRouteNextHopProtocol OBJECT-TYPE 601 SYNTAX IANAipMRouteProtocol 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The routing mechanism via which this next-hop was learned." 606 ::= { ipMRouteNextHopEntry 10 } 608 ipMRouteNextHopPkts OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The number of packets which have been forwarded using this 614 route." 615 ::= { ipMRouteNextHopEntry 11 } 617 Draft IPv4 Multicast Routing MIB January 2000 619 -- 620 -- The Multicast Routing Interface Table 621 -- 623 ipMRouteInterfaceTable OBJECT-TYPE 624 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "The (conceptual) table containg multicast routing 629 information specific to interfaces." 630 ::= { ipMRoute 4 } 632 ipMRouteInterfaceEntry OBJECT-TYPE 633 SYNTAX IpMRouteInterfaceEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "An entry (conceptual row) containing the multicast routing 638 information for a particular interface." 639 INDEX { ipMRouteInterfaceIfIndex } 640 ::= { ipMRouteInterfaceTable 1 } 642 IpMRouteInterfaceEntry ::= SEQUENCE { 643 ipMRouteInterfaceIfIndex InterfaceIndex, 644 ipMRouteInterfaceTtl Integer32, 645 ipMRouteInterfaceProtocol IANAipMRouteProtocol, 646 ipMRouteInterfaceRateLimit Integer32, 647 ipMRouteInterfaceInMcastOctets Counter32, 648 ipMRouteInterfaceOutMcastOctets Counter32, 649 ipMRouteInterfaceHCInMcastOctets Counter64, 650 ipMRouteInterfaceHCOutMcastOctets Counter64 651 } 653 ipMRouteInterfaceIfIndex OBJECT-TYPE 654 SYNTAX InterfaceIndex 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "The ifIndex value of the interface for which this entry 659 contains information." 660 ::= { ipMRouteInterfaceEntry 1 } 662 ipMRouteInterfaceTtl OBJECT-TYPE 663 SYNTAX Integer32 (0..255) 665 Draft IPv4 Multicast Routing MIB January 2000 667 MAX-ACCESS read-write 668 STATUS current 669 DESCRIPTION 670 "The datagram TTL threshold for the interface. Any IP 671 multicast datagrams with a TTL less than this threshold will 672 not be forwarded out the interface. The default value of 0 673 means all multicast packets are forwarded out the 674 interface." 675 ::= { ipMRouteInterfaceEntry 2 } 677 ipMRouteInterfaceProtocol OBJECT-TYPE 678 SYNTAX IANAipMRouteProtocol 679 MAX-ACCESS read-only 680 STATUS current 681 DESCRIPTION 682 "The routing protocol running on this interface." 683 ::= { ipMRouteInterfaceEntry 3 } 685 ipMRouteInterfaceRateLimit OBJECT-TYPE 686 SYNTAX Integer32 687 MAX-ACCESS read-write 688 STATUS current 689 DESCRIPTION 690 "The rate-limit, in kilobits per second, of forwarded 691 multicast traffic on the interface. A rate-limit of 0 692 indicates that no rate limiting is done." 693 DEFVAL { 0 } 694 ::= { ipMRouteInterfaceEntry 4 } 696 ipMRouteInterfaceInMcastOctets OBJECT-TYPE 697 SYNTAX Counter32 698 MAX-ACCESS read-only 699 STATUS current 700 DESCRIPTION 701 "The number of octets of multicast packets that have arrived 702 on the interface, including framing characters. This object 703 is similar to ifInOctets in the Interfaces MIB, except that 704 only multicast packets are counted." 705 ::= { ipMRouteInterfaceEntry 5 } 707 ipMRouteInterfaceOutMcastOctets OBJECT-TYPE 708 SYNTAX Counter32 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 713 Draft IPv4 Multicast Routing MIB January 2000 715 "The number of octets of multicast packets that have been 716 sent on the interface." 717 ::= { ipMRouteInterfaceEntry 6 } 719 ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE 720 SYNTAX Counter64 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "The number of octets of multicast packets that have arrived 725 on the interface, including framing characters. This object 726 is a 64-bit version of ipMRouteInterfaceInMcastOctets. It 727 is similar to ifHCInOctets in the Interfaces MIB, except 728 that only multicast packets are counted." 729 ::= { ipMRouteInterfaceEntry 7 } 731 ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 732 SYNTAX Counter64 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The number of octets of multicast packets that have been 737 sent on the interface. This object is a 64-bit version of 738 ipMRouteInterfaceOutMcastOctets." 739 ::= { ipMRouteInterfaceEntry 8 } 741 Draft IPv4 Multicast Routing MIB January 2000 743 -- 744 -- The IP Multicast Scope Boundary Table 745 -- 747 ipMRouteBoundaryTable OBJECT-TYPE 748 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "The (conceptual) table listing the router's scoped 753 multicast address boundaries." 754 ::= { ipMRoute 5 } 756 ipMRouteBoundaryEntry OBJECT-TYPE 757 SYNTAX IpMRouteBoundaryEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "An entry (conceptual row) in the ipMRouteBoundaryTable 762 representing a scoped boundary." 763 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 764 ipMRouteBoundaryAddressMask } 765 ::= { ipMRouteBoundaryTable 1 } 767 IpMRouteBoundaryEntry ::= SEQUENCE { 768 ipMRouteBoundaryIfIndex InterfaceIndex, 769 ipMRouteBoundaryAddress IpAddress, 770 ipMRouteBoundaryAddressMask IpAddress, 771 ipMRouteBoundaryStatus RowStatus 772 } 774 ipMRouteBoundaryIfIndex OBJECT-TYPE 775 SYNTAX InterfaceIndex 776 MAX-ACCESS not-accessible 777 STATUS current 778 DESCRIPTION 779 "The IfIndex value for the interface to which this boundary 780 applies. Packets with a destination address in the 781 associated address/mask range will not be forwarded out this 782 interface." 783 ::= { ipMRouteBoundaryEntry 1 } 785 ipMRouteBoundaryAddress OBJECT-TYPE 786 SYNTAX IpAddress 787 MAX-ACCESS not-accessible 789 Draft IPv4 Multicast Routing MIB January 2000 791 STATUS current 792 DESCRIPTION 793 "The group address which when combined with the 794 corresponding value of ipMRouteBoundaryAddressMask 795 identifies the group range for which the scoped boundary 796 exists. Scoped addresses must come from the range 239.x.x.x 797 as specified in RFC 2365." 798 ::= { ipMRouteBoundaryEntry 2 } 800 ipMRouteBoundaryAddressMask OBJECT-TYPE 801 SYNTAX IpAddress 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "The group address mask which when combined with the 806 corresponding value of ipMRouteBoundaryAddress identifies 807 the group range for which the scoped boundary exists." 808 ::= { ipMRouteBoundaryEntry 3 } 810 ipMRouteBoundaryStatus OBJECT-TYPE 811 SYNTAX RowStatus 812 MAX-ACCESS read-create 813 STATUS current 814 DESCRIPTION 815 "The status of this row, by which new entries may be 816 created, or old entries deleted from this table." 817 ::= { ipMRouteBoundaryEntry 4 } 819 -- 820 -- The IP Multicast Scope Name Table 821 -- 823 ipMRouteScopeNameTable OBJECT-TYPE 824 SYNTAX SEQUENCE OF IpMRouteScopeNameEntry 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "The (conceptual) table listing the multicast scope names." 829 ::= { ipMRoute 6 } 831 ipMRouteScopeNameEntry OBJECT-TYPE 832 SYNTAX IpMRouteScopeNameEntry 833 MAX-ACCESS not-accessible 834 STATUS current 836 Draft IPv4 Multicast Routing MIB January 2000 838 DESCRIPTION 839 "An entry (conceptual row) in the ipMRouteScopeNameTable 840 representing a multicast scope name." 841 INDEX { ipMRouteScopeNameAddress, 842 ipMRouteScopeNameAddressMask, 843 IMPLIED ipMRouteScopeNameLanguage } 844 ::= { ipMRouteScopeNameTable 1 } 846 IpMRouteScopeNameEntry ::= SEQUENCE { 847 ipMRouteScopeNameAddress IpAddress, 848 ipMRouteScopeNameAddressMask IpAddress, 849 ipMRouteScopeNameLanguage LanguageTag, 850 ipMRouteScopeNameString SnmpAdminString, 851 ipMRouteScopeNameDefault TruthValue, 852 ipMRouteScopeNameStatus RowStatus 853 } 855 ipMRouteScopeNameAddress OBJECT-TYPE 856 SYNTAX IpAddress 857 MAX-ACCESS not-accessible 858 STATUS current 859 DESCRIPTION 860 "The group address which when combined with the 861 corresponding value of ipMRouteScopeNameAddressMask 862 identifies the group range associated with the multicast 863 scope. Scoped addresses must come from the range 864 239.x.x.x." 865 ::= { ipMRouteScopeNameEntry 1 } 867 ipMRouteScopeNameAddressMask OBJECT-TYPE 868 SYNTAX IpAddress 869 MAX-ACCESS not-accessible 870 STATUS current 871 DESCRIPTION 872 "The group address mask which when combined with the 873 corresponding value of ipMRouteScopeNameAddress identifies 874 the group range associated with the multicast scope." 875 ::= { ipMRouteScopeNameEntry 2 } 877 ipMRouteScopeNameLanguage OBJECT-TYPE 878 SYNTAX LanguageTag 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "The RFC 1766-style language tag associated with the scope 884 Draft IPv4 Multicast Routing MIB January 2000 886 name." 887 ::= { ipMRouteScopeNameEntry 3 } 889 ipMRouteScopeNameString OBJECT-TYPE 890 SYNTAX SnmpAdminString 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "The textual name associated with the multicast scope. The 895 value of this object should be suitable for displaying to 896 end-users, such as when allocating a multicast address in 897 this scope. When no name is specified, the default value of 898 this object should be the string 239.x.x.x/y with x and y 899 replaced appropriately to describe the address and mask 900 length associated with the scope." 901 ::= { ipMRouteScopeNameEntry 4 } 903 ipMRouteScopeNameDefault OBJECT-TYPE 904 SYNTAX TruthValue 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "If true, indicates a preference that the name in the 909 following language should be used by applications if no name 910 is available in a desired language." 911 DEFVAL { false } 912 ::= { ipMRouteScopeNameEntry 5 } 914 ipMRouteScopeNameStatus OBJECT-TYPE 915 SYNTAX RowStatus 916 MAX-ACCESS read-create 917 STATUS current 918 DESCRIPTION 919 "The status of this row, by which new entries may be 920 created, or old entries deleted from this table." 921 ::= { ipMRouteScopeNameEntry 6 } 923 Draft IPv4 Multicast Routing MIB January 2000 925 -- conformance information 927 ipMRouteMIBConformance 928 OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 } 929 ipMRouteMIBCompliances 930 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 931 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 933 -- compliance statements 935 ipMRouteMIBCompliance MODULE-COMPLIANCE 936 STATUS current 937 DESCRIPTION 938 "The compliance statement for the IP Multicast MIB." 939 MODULE -- this module 940 MANDATORY-GROUPS { ipMRouteMIBBasicGroup, 941 ipMRouteMIBRouteGroup} 943 GROUP ipMRouteMIBBoundaryGroup 944 DESCRIPTION 945 "This group is mandatory if the router supports 946 administratively-scoped multicast address boundaries." 948 OBJECT ipMRouteBoundaryStatus 949 MIN-ACCESS read-only 950 DESCRIPTION 951 "Write access is not required." 953 OBJECT ipMRouteScopeNameStatus 954 MIN-ACCESS read-only 955 DESCRIPTION 956 "Write access is not required." 958 GROUP ipMRouteMIBHCInterfaceGroup 959 DESCRIPTION 960 "This group is mandatory only for those network interfaces 961 for which the value of the corresponding instance of ifSpeed 962 is greater than 20,000,000 bits/second." 964 ::= { ipMRouteMIBCompliances 1 } 966 -- units of conformance 968 Draft IPv4 Multicast Routing MIB January 2000 970 ipMRouteMIBBasicGroup OBJECT-GROUP 971 OBJECTS { ipMRouteEnable, ipMRouteEntryCount, 972 ipMRouteUpstreamNeighbor, ipMRouteInIfIndex, 973 ipMRouteUpTime, ipMRouteExpiryTime, 974 ipMRouteNextHopState, 975 ipMRouteNextHopUpTime, 976 ipMRouteNextHopExpiryTime, 977 ipMRouteNextHopProtocol, 978 ipMRouteNextHopPkts, 979 ipMRouteInterfaceTtl, 980 ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, 981 ipMRouteInterfaceInMcastOctets, 982 ipMRouteInterfaceOutMcastOctets, 983 ipMRouteProtocol 984 } 985 STATUS current 986 DESCRIPTION 987 "A collection of objects to support basic management of IP 988 Multicast routing." 989 ::= { ipMRouteMIBGroups 1 } 991 ipMRouteMIBHopCountGroup OBJECT-GROUP 992 OBJECTS { ipMRouteNextHopClosestMemberHops } 993 STATUS current 994 DESCRIPTION 995 "A collection of objects to support management of the use of 996 hop counts in IP Multicast routing." 997 ::= { ipMRouteMIBGroups 2 } 999 ipMRouteMIBBoundaryGroup OBJECT-GROUP 1000 OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString, 1001 ipMRouteScopeNameDefault, ipMRouteScopeNameStatus } 1002 STATUS current 1003 DESCRIPTION 1004 "A collection of objects to support management of scoped 1005 multicast address boundaries." 1006 ::= { ipMRouteMIBGroups 3 } 1008 ipMRouteMIBPktsOutGroup OBJECT-GROUP 1009 OBJECTS { ipMRouteNextHopPkts } 1010 STATUS current 1011 DESCRIPTION 1012 "A collection of objects to support management of packet 1013 counters for each outgoing interface entry of a route." 1014 ::= { ipMRouteMIBGroups 4 } 1016 Draft IPv4 Multicast Routing MIB January 2000 1018 ipMRouteMIBHCInterfaceGroup OBJECT-GROUP 1019 OBJECTS { ipMRouteInterfaceHCInMcastOctets, 1020 ipMRouteInterfaceHCOutMcastOctets, 1021 ipMRouteHCOctets } 1022 STATUS current 1023 DESCRIPTION 1024 "A collection of objects providing information specific to 1025 high speed (greater than 20,000,000 bits/second) network 1026 interfaces." 1027 ::= { ipMRouteMIBGroups 5 } 1029 ipMRouteMIBRouteGroup OBJECT-GROUP 1030 OBJECTS { ipMRouteRtProto, ipMRouteRtAddress, 1031 ipMRouteRtMask, ipMRouteRtType } 1032 STATUS current 1033 DESCRIPTION 1034 "A collection of objects providing information on the 1035 relationship between multicast routing information, and the 1036 IP Forwarding Table." 1037 ::= { ipMRouteMIBGroups 6 } 1039 ipMRouteMIBPktsGroup OBJECT-GROUP 1040 OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, 1041 ipMRouteOctets } 1042 STATUS current 1043 DESCRIPTION 1044 "A collection of objects to support management of packet 1045 counters for each forwarding entry." 1046 ::= { ipMRouteMIBGroups 7 } 1048 END 1050 Draft IPv4 Multicast Routing MIB January 2000 1052 6. IANA Considerations 1054 The The ipMRouteRtProto, ipMRouteNextHopProtocol, 1055 ipMRouteInterfaceProtocol, and ipMRouteProtocol use textual conventions 1056 imported from the IANA-RTPROTO-MIB. The purpose of defining these 1057 textual conventions in a separate MIB module is to allow additional 1058 values to be defined without having to issue a new version of this 1059 document. The Internet Assigned Numbers Authority (IANA) is responsible 1060 for the assignment of all Internet numbers, including various SNMP- 1061 related numbers; it will administer the values associated with these 1062 textual conventions. 1064 The rules for additions or changes to the IANA-RTPROTO-MIB are outlined 1065 in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. 1067 The current versions of the IANA-RTPROTO-MIB can be accessed from the 1068 IANA home page at: "http://www.iana.org/". 1070 7. Security Considerations 1072 This MIB contains readable objects whose values provide information 1073 related to multicast routing, including information on what machines are 1074 sending to which groups. There are also a number of objects that have a 1075 MAX-ACCESS clause of read-write and/or read-create, such as those which 1076 allow an administrator to configure multicast boundaries. 1078 While unauthorized access to the readable objects is relatively 1079 innocuous, unauthorized access to the write-able objects could cause a 1080 denial of service, or could cause wider distribution of packets intended 1081 only for local distribution. Hence, the support for SET operations in a 1082 non-secure environment without proper protection can have a negative 1083 effect on network operations. 1085 SNMPv1 by itself is such an insecure environment. Even if the network 1086 itself is secure (for example by using IPSec), even then, there is no 1087 control as to who on the secure network is allowed to access and SET 1088 (change/create/delete) the objects in this MIB. 1090 It is recommended that the implementers consider the security features 1091 as provided by the SNMPv3 framework. Specifically, the use of the User- 1092 based Security Model RFC 2574 [12] and the View-based Access Control 1093 Model RFC 2575 [15] is recommended. 1095 Draft IPv4 Multicast Routing MIB January 2000 1097 It is then a customer/user responsibility to ensure that the SNMP entity 1098 giving access to this MIB, is properly configured to give access to 1099 those objects only to those principals (users) that have legitimate 1100 rights to access them. 1102 8. IANA Routing Protocol Registration MIB 1104 This appendix defines the initial content of the IANA-RTPROTO-MIB. 1106 NOTE TO RFC-EDITOR: This section should be removed from this document 1107 prior to its publication, at which time this MIB will be administered by 1108 IANA. 1110 IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN 1112 IMPORTS 1113 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1114 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1116 ianaipRouteProtocol MODULE-IDENTITY 1117 LAST-UPDATED "200001311200Z" -- January 31, 2000 1118 ORGANIZATION "IANA" 1119 CONTACT-INFO 1120 "Internet Assigned Numbers Authority 1122 Postal: USC/Information Sciences Institute 1123 4676 Admiralty Way, Marina del Rey, CA 90292 1125 Tel: +1 310 822 1511 1126 E-Mail: iana@isi.edu" 1127 DESCRIPTION 1128 "This MIB module defines the IANAipRouteProtocol and 1129 IANAipMRouteProtocol textual conventions for use in 1130 MIBs which need to identify unicast or multicast 1131 routing mechanisms. 1133 Any and all requests for additional values require 1134 proper documentation. Possible forms of documentation 1135 include, but are not limited to, RFCs. Other requests 1136 may also be accepted under the advice of a 'designated 1137 expert'. (Contact the IANA for the contact information 1138 of the current expert.)" 1139 ::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA 1141 Draft IPv4 Multicast Routing MIB January 2000 1143 IANAipRouteProtocol ::= TEXTUAL-CONVENTION 1144 STATUS current 1145 DESCRIPTION 1146 "A mechanism for learning routes. Inclusion of values for 1147 routing protocols is not intended to imply that those 1148 protocols need be supported." 1149 SYNTAX INTEGER { 1150 other (1), -- not specified 1151 local (2), -- local interface 1152 netmgmt (3), -- static route 1153 icmp (4), -- result of ICMP Redirect 1155 -- the following are all dynamic 1156 -- routing protocols 1158 egp (5), -- Exterior Gateway Protocol 1159 ggp (6), -- Gateway-Gateway Protocol 1160 hello (7), -- FuzzBall HelloSpeak 1161 rip (8), -- Berkeley RIP or RIP-II 1162 isIs (9), -- Dual IS-IS 1163 esIs (10), -- ISO 9542 1164 ciscoIgrp (11), -- Cisco IGRP 1165 bbnSpfIgp (12), -- BBN SPF IGP 1166 ospf (13), -- Open Shortest Path First 1167 bgp (14), -- Border Gateway Protocol 1168 idpr (15), -- InterDomain Policy Routing 1169 ciscoEigrp (16), -- Cisco EIGRP 1170 dvmrp (17) -- DVMRP 1171 } 1173 IANAipMRouteProtocol ::= TEXTUAL-CONVENTION 1174 STATUS current 1175 DESCRIPTION 1176 "The multicast routing protocol. Inclusion of values for 1177 multicast routing protocols is not intended to imply that 1178 those protocols need be supported." 1179 SYNTAX INTEGER { 1180 other(1), -- none of the following 1181 local(2), -- e.g., manually configured 1182 netmgmt(3), -- set via net.mgmt protocol 1183 dvmrp(4), 1184 mospf(5), 1185 pimSparseDense(6), -- PIMv1, both DM and SM 1186 cbt(7), 1187 pimSparseMode(8), -- PIM-SM 1189 Draft IPv4 Multicast Routing MIB January 2000 1191 pimDenseMode(9), -- PIM-DM 1192 igmpOnly(10), 1193 bgmp(11), 1194 msdp(12) 1195 } 1197 END 1199 9. Intellectual Property Notice 1201 The IETF takes no position regarding the validity or scope of any 1202 intellectual property or other rights that might be claimed to pertain 1203 to the implementation or use of the technology described in this 1204 document or the extent to which any license under such rights might or 1205 might not be available; neither does it represent that it has made any 1206 effort to identify any such rights. Information on the IETF's 1207 procedures with respect to rights in standards-track and standards- 1208 related documentation can be found in BCP-11. Copies of claims of 1209 rights made available for publication and any assurances of licenses to 1210 be made available, or the result of an attempt made to obtain a general 1211 license or permission for the use of such proprietary rights by 1212 implementers or users of this specification can be obtained from the 1213 IETF Secretariat. 1215 The IETF invites any interested party to bring to its attention any 1216 copyrights, patents or patent applications, or other proprietary rights 1217 which may cover technology that may be required to practice this 1218 standard. Please address the information to the IETF Executive 1219 Director. 1221 10. Acknowledgements 1223 This MIB module was updated based on feedback from the IETF's Inter- 1224 Domain Multicast Routing (IDMR) Working Group. 1226 11. Authors' Addresses 1228 Keith McCloghrie 1229 cisco Systems, Inc. 1230 170 West Tasman Drive 1232 Draft IPv4 Multicast Routing MIB January 2000 1234 San Jose, CA 95134-1706 1235 Phone: +1 408 526 5260 1236 EMail: kzm@cisco.com 1238 Dino Farinacci 1239 cisco Systems, Inc. 1240 170 West Tasman Drive 1241 San Jose, CA 95134-1706 1242 Phone: +1 408 526 4696 1243 EMail: dino@cisco.com 1245 Dave Thaler 1246 Microsoft Corporation 1247 One Microsoft Way 1248 Redmond, WA 98052-6399 1249 Phone: +1 425 703 8835 1250 EMail: dthaler@microsoft.com 1252 12. References 1254 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1255 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1256 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1257 1999. 1259 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1260 Management Information for TCP/IP-based Internets", RFC 1155, STD 1261 16, Performance Systems International, Hughes LAN Systems, May 1262 1990. 1264 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1265 STD 16, Performance Systems International, Hughes LAN Systems, 1266 March 1991. 1268 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1269 RFC 1215, Performance Systems International, March 1991. 1271 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1272 and S. Waldbusser, "Structure of Management Information Version 2 1273 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1274 Braunschweig, SNMP Research, First Virtual Holdings, International 1275 Network Services, April 1999. 1277 Draft IPv4 Multicast Routing MIB January 2000 1279 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1280 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1281 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1282 Virtual Holdings, International Network Services, April 1999. 1284 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1285 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1286 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1287 First Virtual Holdings, International Network Services, April 1999. 1289 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1290 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1291 Systems International, Performance Systems International, MIT 1292 Laboratory for Computer Science, May 1990. 1294 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1295 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1296 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1297 International Network Services, January 1996. 1299 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1300 Mappings for Version 2 of the Simple Network Management Protocol 1301 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1302 Dover Beach Consulting, Inc., International Network Services, 1303 January 1996. 1305 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1306 Processing and Dispatching for the Simple Network Management 1307 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1308 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1310 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1311 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1312 2574, IBM T. J. Watson Research, April 1999. 1314 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1315 Operations for Version 2 of the Simple Network Management Protocol 1316 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1317 Dover Beach Consulting, Inc., International Network Services, 1318 January 1996. 1320 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1321 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1322 Systems, April 1999. 1324 Draft IPv4 Multicast Routing MIB January 2000 1326 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1327 Control Model (VACM) for the Simple Network Management Protocol 1328 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1329 Cisco Systems, Inc., April 1999. 1331 [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1332 thesis, Electrical Engineering Dept., Stanford University, December 1333 1991. 1335 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1336 Multicast Routing Protocol", RFC 1075, November 1988. 1338 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1339 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1340 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1341 Specification", RFC 2362, June 1998. 1343 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1344 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1345 Specification". Work in progress, May 1997. 1347 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1349 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1350 Routing", RFC 2189, September 1997. 1352 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1353 23, July 1998. 1355 13. Full Copyright Statement 1357 Copyright (C) The Internet Society (1999). All Rights Reserved. 1359 This document and translations of it may be copied and furnished to 1360 others, and derivative works that comment on or otherwise explain it or 1361 assist in its implmentation may be prepared, copied, published and 1362 distributed, in whole or in part, without restriction of any kind, 1363 provided that the above copyright notice and this paragraph are included 1364 on all such copies and derivative works. However, this document itself 1365 may not be modified in any way, such as by removing the copyright notice 1366 or references to the Internet Society or other Internet organizations, 1367 except as needed for the purpose of developing Internet standards in 1368 which case the procedures for copyrights defined in the Internet 1370 Draft IPv4 Multicast Routing MIB January 2000 1372 Standards process must be followed, or as required to translate it into 1373 languages other than English. 1375 The limited permissions granted above are perpetual and will not be 1376 revoked by the Internet Society or its successors or assigns. 1378 This document and the information contained herein is provided on an "AS 1379 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1380 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1381 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1382 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1383 FITNESS FOR A PARTICULAR PURPOSE. 1385 Table of Contents 1387 1 Abstract ........................................................ 2 1388 2 Introduction .................................................... 2 1389 3 The SNMP Management Framework ................................... 2 1390 4 Overview ........................................................ 3 1391 5 Definitions ..................................................... 4 1392 6 IANA Considerations ............................................. 26 1393 7 Security Considerations ......................................... 26 1394 8 IANA Routing Protocol Registration MIB .......................... 27 1395 9 Intellectual Property Notice .................................... 29 1396 10 Acknowledgements ............................................... 29 1397 11 Authors' Addresses ............................................. 29 1398 12 References ..................................................... 30 1399 13 Full Copyright Statement ....................................... 32