idnits 2.17.1 draft-ietf-idmr-multicast-routmib-14.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 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 (7 July 2000) is 8666 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 1333, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1336, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1341, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1345, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1347, 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 (~~), 7 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 January 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 7 July 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 July 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 July 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 July 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 169 Draft IPv4 Multicast Routing MIB July 2000 171 DISPLAY-HINT "100a" 172 STATUS current 173 DESCRIPTION 174 "An RFC 1766-style language tag, with all alphabetic 175 characters converted to lowercase. This restriction is 176 intended to make the lexical ordering imposed by SNMP useful 177 when applied to language tags. Note that it is 178 theoretically possible for a valid language tag to exceed 179 the allowed length of this syntax, and thus be impossible to 180 represent with this syntax. Sampling of language tags in 181 current use on the Internet suggests that this limit does 182 not pose a serious problem in practice." 183 SYNTAX OCTET STRING (SIZE (1..100)) 185 -- Top-level structure of the MIB 187 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 } 189 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 190 Draft IPv4 Multicast Routing MIB July 2000 192 -- the IP Multicast Routing MIB-Group 193 -- 194 -- a collection of objects providing information about 195 -- IP Multicast Groups 197 ipMRouteEnable OBJECT-TYPE 198 SYNTAX INTEGER { enabled(1), disabled(2) } 199 MAX-ACCESS read-write 200 STATUS current 201 DESCRIPTION 202 "The enabled status of IP Multicast routing on this router." 203 ::= { ipMRoute 1 } 205 ipMRouteEntryCount OBJECT-TYPE 206 SYNTAX Gauge32 207 MAX-ACCESS read-only 208 STATUS current 209 DESCRIPTION 210 "The number of rows in the ipMRouteTable. This can be used 211 to monitor the multicast routing table size." 212 ::= { ipMRoute 7 } 214 ipMRouteTable OBJECT-TYPE 215 SYNTAX SEQUENCE OF IpMRouteEntry 216 MAX-ACCESS not-accessible 217 STATUS current 218 DESCRIPTION 219 "The (conceptual) table containing multicast routing 220 information for IP datagrams sent by particular sources to 221 the IP multicast groups known to this router." 222 ::= { ipMRoute 2 } 224 Draft IPv4 Multicast Routing MIB July 2000 226 ipMRouteEntry OBJECT-TYPE 227 SYNTAX IpMRouteEntry 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION 231 "An entry (conceptual row) containing the multicast routing 232 information for IP datagrams from a particular source and 233 addressed to a particular IP multicast group address. 234 Discontinuities in counters in this entry can be detected by 235 observing the value of ipMRouteUpTime." 236 INDEX { ipMRouteGroup, 237 ipMRouteSource, 238 ipMRouteSourceMask } 239 ::= { ipMRouteTable 1 } 241 IpMRouteEntry ::= SEQUENCE { 242 ipMRouteGroup IpAddress, 243 ipMRouteSource IpAddress, 244 ipMRouteSourceMask IpAddress, 245 ipMRouteUpstreamNeighbor IpAddress, 246 ipMRouteInIfIndex InterfaceIndexOrZero, 247 ipMRouteUpTime TimeTicks, 248 ipMRouteExpiryTime TimeTicks, 249 ipMRoutePkts Counter32, 250 ipMRouteDifferentInIfPackets Counter32, 251 ipMRouteOctets Counter32, 252 ipMRouteProtocol IANAipMRouteProtocol, 253 ipMRouteRtProto IANAipRouteProtocol, 254 ipMRouteRtAddress IpAddress, 255 ipMRouteRtMask IpAddress, 256 ipMRouteRtType INTEGER, 257 ipMRouteHCOctets Counter64 258 } 260 ipMRouteGroup OBJECT-TYPE 261 SYNTAX IpAddress 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "The IP multicast group address for which this entry 266 contains multicast routing information." 267 ::= { ipMRouteEntry 1 } 269 ipMRouteSource OBJECT-TYPE 270 SYNTAX IpAddress 272 Draft IPv4 Multicast Routing MIB July 2000 274 MAX-ACCESS not-accessible 275 STATUS current 276 DESCRIPTION 277 "The network address which when combined with the 278 corresponding value of ipMRouteSourceMask identifies the 279 sources for which this entry contains multicast routing 280 information." 281 ::= { ipMRouteEntry 2 } 283 ipMRouteSourceMask OBJECT-TYPE 284 SYNTAX IpAddress 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "The network mask which when combined with the corresponding 289 value of ipMRouteSource identifies the sources for which 290 this entry contains multicast routing information." 291 ::= { ipMRouteEntry 3 } 293 ipMRouteUpstreamNeighbor OBJECT-TYPE 294 SYNTAX IpAddress 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The address of the upstream neighbor (e.g., RPF neighbor) 299 from which IP datagrams from these sources to this multicast 300 address are received, or 0.0.0.0 if the upstream neighbor is 301 unknown (e.g., in CBT)." 302 ::= { ipMRouteEntry 4 } 304 ipMRouteInIfIndex OBJECT-TYPE 305 SYNTAX InterfaceIndexOrZero 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The value of ifIndex for the interface on which IP 310 datagrams sent by these sources to this multicast address 311 are received. A value of 0 indicates that datagrams are not 312 subject to an incoming interface check, but may be accepted 313 on multiple interfaces (e.g., in CBT)." 314 ::= { ipMRouteEntry 5 } 316 ipMRouteUpTime OBJECT-TYPE 317 SYNTAX TimeTicks 318 MAX-ACCESS read-only 320 Draft IPv4 Multicast Routing MIB July 2000 322 STATUS current 323 DESCRIPTION 324 "The time since the multicast routing information 325 represented by this entry was learned by the router." 326 ::= { ipMRouteEntry 6 } 328 ipMRouteExpiryTime OBJECT-TYPE 329 SYNTAX TimeTicks 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The minimum amount of time remaining before this entry will 334 be aged out. The value 0 indicates that the entry is not 335 subject to aging." 336 ::= { ipMRouteEntry 7 } 338 ipMRoutePkts OBJECT-TYPE 339 SYNTAX Counter32 340 MAX-ACCESS read-only 341 STATUS current 342 DESCRIPTION 343 "The number of packets which this router has received from 344 these sources and addressed to this multicast group 345 address." 346 ::= { ipMRouteEntry 8 } 348 ipMRouteDifferentInIfPackets OBJECT-TYPE 349 SYNTAX Counter32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "The number of packets which this router has received from 354 these sources and addressed to this multicast group address, 355 which were dropped because they were not received on the 356 interface indicated by ipMRouteInIfIndex. Packets which are 357 not subject to an incoming interface check (e.g., using CBT) 358 are not counted." 359 ::= { ipMRouteEntry 9 } 361 ipMRouteOctets OBJECT-TYPE 362 SYNTAX Counter32 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The number of octets contained in IP datagrams which were 368 Draft IPv4 Multicast Routing MIB July 2000 370 received from these sources and addressed to this multicast 371 group address, and which were forwarded by this router." 372 ::= { ipMRouteEntry 10 } 374 ipMRouteProtocol OBJECT-TYPE 375 SYNTAX IANAipMRouteProtocol 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "The multicast routing protocol via which this multicast 380 forwarding entry was learned." 381 ::= { ipMRouteEntry 11 } 383 ipMRouteRtProto OBJECT-TYPE 384 SYNTAX IANAipRouteProtocol 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The routing mechanism via which the route used to find the 389 upstream or parent interface for this multicast forwarding 390 entry was learned. Inclusion of values for routing 391 protocols is not intended to imply that those protocols need 392 be supported." 393 ::= { ipMRouteEntry 12 } 395 ipMRouteRtAddress OBJECT-TYPE 396 SYNTAX IpAddress 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The address portion of the route used to find the upstream 401 or parent interface for this multicast forwarding entry." 402 ::= { ipMRouteEntry 13 } 404 ipMRouteRtMask OBJECT-TYPE 405 SYNTAX IpAddress 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The mask associated with the route used to find the upstream 410 or parent interface for this multicast forwarding entry." 411 ::= { ipMRouteEntry 14 } 413 ipMRouteRtType OBJECT-TYPE 414 SYNTAX INTEGER { 416 Draft IPv4 Multicast Routing MIB July 2000 418 unicast (1), -- Unicast route used in multicast RIB 419 multicast (2) -- Multicast route 420 } 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The reason the given route was placed in the (logical) 425 multicast Routing Information Base (RIB). A value of 426 unicast means that the route would normally be placed only 427 in the unicast RIB, but was placed in the multicast RIB 428 (instead or in addition) due to local configuration, such as 429 when running PIM over RIP. A value of multicast means that 430 the route was explicitly added to the multicast RIB by the 431 routing protocol, such as DVMRP or Multiprotocol BGP." 432 ::= { ipMRouteEntry 15 } 434 ipMRouteHCOctets OBJECT-TYPE 435 SYNTAX Counter64 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The number of octets contained in IP datagrams which were 440 received from these sources and addressed to this multicast 441 group address, and which were forwarded by this router. 442 This object is a 64-bit version of ipMRouteOctets." 443 ::= { ipMRouteEntry 16 } 445 Draft IPv4 Multicast Routing MIB July 2000 447 -- 448 -- The IP Multicast Routing Next Hop Table 449 -- 451 ipMRouteNextHopTable OBJECT-TYPE 452 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 453 MAX-ACCESS not-accessible 454 STATUS current 455 DESCRIPTION 456 "The (conceptual) table containing information on the next- 457 hops on outgoing interfaces for routing IP multicast 458 datagrams. Each entry is one of a list of next-hops on 459 outgoing interfaces for particular sources sending to a 460 particular multicast group address." 461 ::= { ipMRoute 3 } 463 ipMRouteNextHopEntry OBJECT-TYPE 464 SYNTAX IpMRouteNextHopEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "An entry (conceptual row) in the list of next-hops on 469 outgoing interfaces to which IP multicast datagrams from 470 particular sources to a IP multicast group address are 471 routed. Discontinuities in counters in this entry can be 472 detected by observing the value of ipMRouteUpTime." 473 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 474 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 475 ipMRouteNextHopAddress } 476 ::= { ipMRouteNextHopTable 1 } 478 Draft IPv4 Multicast Routing MIB July 2000 480 IpMRouteNextHopEntry ::= SEQUENCE { 481 ipMRouteNextHopGroup IpAddress, 482 ipMRouteNextHopSource IpAddress, 483 ipMRouteNextHopSourceMask IpAddress, 484 ipMRouteNextHopIfIndex InterfaceIndex, 485 ipMRouteNextHopAddress IpAddress, 486 ipMRouteNextHopState INTEGER, 487 ipMRouteNextHopUpTime TimeTicks, 488 ipMRouteNextHopExpiryTime TimeTicks, 489 ipMRouteNextHopClosestMemberHops Integer32, 490 ipMRouteNextHopProtocol IANAipMRouteProtocol, 491 ipMRouteNextHopPkts Counter32 492 } 494 ipMRouteNextHopGroup OBJECT-TYPE 495 SYNTAX IpAddress 496 MAX-ACCESS not-accessible 497 STATUS current 498 DESCRIPTION 499 "The IP multicast group for which this entry specifies a 500 next-hop on an outgoing interface." 501 ::= { ipMRouteNextHopEntry 1 } 503 ipMRouteNextHopSource OBJECT-TYPE 504 SYNTAX IpAddress 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "The network address which when combined with the 509 corresponding value of ipMRouteNextHopSourceMask identifies 510 the sources for which this entry specifies a next-hop on an 511 outgoing interface." 512 ::= { ipMRouteNextHopEntry 2 } 514 ipMRouteNextHopSourceMask OBJECT-TYPE 515 SYNTAX IpAddress 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "The network mask which when combined with the corresponding 520 value of ipMRouteNextHopSource identifies the sources for 521 which this entry specifies a next-hop on an outgoing 522 interface." 523 ::= { ipMRouteNextHopEntry 3 } 525 Draft IPv4 Multicast Routing MIB July 2000 527 ipMRouteNextHopIfIndex OBJECT-TYPE 528 SYNTAX InterfaceIndex 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "The ifIndex value of the interface for the outgoing 533 interface for this next-hop." 534 ::= { ipMRouteNextHopEntry 4 } 536 ipMRouteNextHopAddress OBJECT-TYPE 537 SYNTAX IpAddress 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "The address of the next-hop specific to this entry. For 542 most interfaces, this is identical to ipMRouteNextHopGroup. 543 NBMA interfaces, however, may have multiple next-hop 544 addresses out a single outgoing interface." 545 ::= { ipMRouteNextHopEntry 5 } 547 ipMRouteNextHopState OBJECT-TYPE 548 SYNTAX INTEGER { pruned(1), forwarding(2) } 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "An indication of whether the outgoing interface and next- 553 hop represented by this entry is currently being used to 554 forward IP datagrams. The value 'forwarding' indicates it 555 is currently being used; the value 'pruned' indicates it is 556 not." 557 ::= { ipMRouteNextHopEntry 6 } 559 ipMRouteNextHopUpTime OBJECT-TYPE 560 SYNTAX TimeTicks 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "The time since the multicast routing information 565 represented by this entry was learned by the router." 566 ::= { ipMRouteNextHopEntry 7 } 568 ipMRouteNextHopExpiryTime OBJECT-TYPE 569 SYNTAX TimeTicks 570 MAX-ACCESS read-only 571 STATUS current 573 Draft IPv4 Multicast Routing MIB July 2000 575 DESCRIPTION 576 "The minimum amount of time remaining before this entry will 577 be aged out. If ipMRouteNextHopState is pruned(1), the 578 remaining time until the prune expires and the state reverts 579 to forwarding(2). Otherwise, the remaining time until this 580 entry is removed from the table. The time remaining may be 581 copied from ipMRouteExpiryTime if the protocol in use for 582 this entry dos not specify next-hop timers. The value 0 583 indicates that the entry is not subject to aging." 584 ::= { ipMRouteNextHopEntry 8 } 586 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 587 SYNTAX Integer32 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "The minimum number of hops between this router and any 592 member of this IP multicast group reached via this next-hop 593 on this outgoing interface. Any IP multicast datagrams for 594 the group which have a TTL less than this number of hops 595 will not be forwarded to this next-hop." 596 ::= { ipMRouteNextHopEntry 9 } 598 ipMRouteNextHopProtocol OBJECT-TYPE 599 SYNTAX IANAipMRouteProtocol 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "The routing mechanism via which this next-hop was learned." 604 ::= { ipMRouteNextHopEntry 10 } 606 ipMRouteNextHopPkts OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The number of packets which have been forwarded using this 612 route." 613 ::= { ipMRouteNextHopEntry 11 } 615 Draft IPv4 Multicast Routing MIB July 2000 617 -- 618 -- The Multicast Routing Interface Table 619 -- 621 ipMRouteInterfaceTable OBJECT-TYPE 622 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "The (conceptual) table containg multicast routing 627 information specific to interfaces." 628 ::= { ipMRoute 4 } 630 ipMRouteInterfaceEntry OBJECT-TYPE 631 SYNTAX IpMRouteInterfaceEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "An entry (conceptual row) containing the multicast routing 636 information for a particular interface." 637 INDEX { ipMRouteInterfaceIfIndex } 638 ::= { ipMRouteInterfaceTable 1 } 640 IpMRouteInterfaceEntry ::= SEQUENCE { 641 ipMRouteInterfaceIfIndex InterfaceIndex, 642 ipMRouteInterfaceTtl Integer32, 643 ipMRouteInterfaceProtocol IANAipMRouteProtocol, 644 ipMRouteInterfaceRateLimit Integer32, 645 ipMRouteInterfaceInMcastOctets Counter32, 646 ipMRouteInterfaceOutMcastOctets Counter32, 647 ipMRouteInterfaceHCInMcastOctets Counter64, 648 ipMRouteInterfaceHCOutMcastOctets Counter64 649 } 651 ipMRouteInterfaceIfIndex OBJECT-TYPE 652 SYNTAX InterfaceIndex 653 MAX-ACCESS not-accessible 654 STATUS current 655 DESCRIPTION 656 "The ifIndex value of the interface for which this entry 657 contains information." 658 ::= { ipMRouteInterfaceEntry 1 } 660 ipMRouteInterfaceTtl OBJECT-TYPE 661 SYNTAX Integer32 (0..255) 663 Draft IPv4 Multicast Routing MIB July 2000 665 MAX-ACCESS read-write 666 STATUS current 667 DESCRIPTION 668 "The datagram TTL threshold for the interface. Any IP 669 multicast datagrams with a TTL less than this threshold will 670 not be forwarded out the interface. The default value of 0 671 means all multicast packets are forwarded out the 672 interface." 673 ::= { ipMRouteInterfaceEntry 2 } 675 ipMRouteInterfaceProtocol OBJECT-TYPE 676 SYNTAX IANAipMRouteProtocol 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The routing protocol running on this interface." 681 ::= { ipMRouteInterfaceEntry 3 } 683 ipMRouteInterfaceRateLimit OBJECT-TYPE 684 SYNTAX Integer32 685 MAX-ACCESS read-write 686 STATUS current 687 DESCRIPTION 688 "The rate-limit, in kilobits per second, of forwarded 689 multicast traffic on the interface. A rate-limit of 0 690 indicates that no rate limiting is done." 691 DEFVAL { 0 } 692 ::= { ipMRouteInterfaceEntry 4 } 694 ipMRouteInterfaceInMcastOctets OBJECT-TYPE 695 SYNTAX Counter32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The number of octets of multicast packets that have arrived 700 on the interface, including framing characters. This object 701 is similar to ifInOctets in the Interfaces MIB, except that 702 only multicast packets are counted." 703 ::= { ipMRouteInterfaceEntry 5 } 705 ipMRouteInterfaceOutMcastOctets OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 711 Draft IPv4 Multicast Routing MIB July 2000 713 "The number of octets of multicast packets that have been 714 sent on the interface." 715 ::= { ipMRouteInterfaceEntry 6 } 717 ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE 718 SYNTAX Counter64 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The number of octets of multicast packets that have arrived 723 on the interface, including framing characters. This object 724 is a 64-bit version of ipMRouteInterfaceInMcastOctets. It 725 is similar to ifHCInOctets in the Interfaces MIB, except 726 that only multicast packets are counted." 727 ::= { ipMRouteInterfaceEntry 7 } 729 ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 730 SYNTAX Counter64 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The number of octets of multicast packets that have been 735 sent on the interface. This object is a 64-bit version of 736 ipMRouteInterfaceOutMcastOctets." 737 ::= { ipMRouteInterfaceEntry 8 } 739 Draft IPv4 Multicast Routing MIB July 2000 741 -- 742 -- The IP Multicast Scope Boundary Table 743 -- 745 ipMRouteBoundaryTable OBJECT-TYPE 746 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "The (conceptual) table listing the router's scoped 751 multicast address boundaries." 752 ::= { ipMRoute 5 } 754 ipMRouteBoundaryEntry OBJECT-TYPE 755 SYNTAX IpMRouteBoundaryEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "An entry (conceptual row) in the ipMRouteBoundaryTable 760 representing a scoped boundary." 761 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 762 ipMRouteBoundaryAddressMask } 763 ::= { ipMRouteBoundaryTable 1 } 765 IpMRouteBoundaryEntry ::= SEQUENCE { 766 ipMRouteBoundaryIfIndex InterfaceIndex, 767 ipMRouteBoundaryAddress IpAddress, 768 ipMRouteBoundaryAddressMask IpAddress, 769 ipMRouteBoundaryStatus RowStatus 770 } 772 ipMRouteBoundaryIfIndex OBJECT-TYPE 773 SYNTAX InterfaceIndex 774 MAX-ACCESS not-accessible 775 STATUS current 776 DESCRIPTION 777 "The IfIndex value for the interface to which this boundary 778 applies. Packets with a destination address in the 779 associated address/mask range will not be forwarded out this 780 interface." 781 ::= { ipMRouteBoundaryEntry 1 } 783 ipMRouteBoundaryAddress OBJECT-TYPE 784 SYNTAX IpAddress 785 MAX-ACCESS not-accessible 787 Draft IPv4 Multicast Routing MIB July 2000 789 STATUS current 790 DESCRIPTION 791 "The group address which when combined with the 792 corresponding value of ipMRouteBoundaryAddressMask 793 identifies the group range for which the scoped boundary 794 exists. Scoped addresses must come from the range 239.x.x.x 795 as specified in RFC 2365." 796 ::= { ipMRouteBoundaryEntry 2 } 798 ipMRouteBoundaryAddressMask OBJECT-TYPE 799 SYNTAX IpAddress 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "The group address mask which when combined with the 804 corresponding value of ipMRouteBoundaryAddress identifies 805 the group range for which the scoped boundary exists." 806 ::= { ipMRouteBoundaryEntry 3 } 808 ipMRouteBoundaryStatus OBJECT-TYPE 809 SYNTAX RowStatus 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "The status of this row, by which new entries may be 814 created, or old entries deleted from this table." 815 ::= { ipMRouteBoundaryEntry 4 } 817 -- 818 -- The IP Multicast Scope Name Table 819 -- 821 ipMRouteScopeNameTable OBJECT-TYPE 822 SYNTAX SEQUENCE OF IpMRouteScopeNameEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "The (conceptual) table listing the multicast scope names." 827 ::= { ipMRoute 6 } 829 ipMRouteScopeNameEntry OBJECT-TYPE 830 SYNTAX IpMRouteScopeNameEntry 831 MAX-ACCESS not-accessible 832 STATUS current 834 Draft IPv4 Multicast Routing MIB July 2000 836 DESCRIPTION 837 "An entry (conceptual row) in the ipMRouteScopeNameTable 838 representing a multicast scope name." 839 INDEX { ipMRouteScopeNameAddress, 840 ipMRouteScopeNameAddressMask, 841 IMPLIED ipMRouteScopeNameLanguage } 842 ::= { ipMRouteScopeNameTable 1 } 844 IpMRouteScopeNameEntry ::= SEQUENCE { 845 ipMRouteScopeNameAddress IpAddress, 846 ipMRouteScopeNameAddressMask IpAddress, 847 ipMRouteScopeNameLanguage LanguageTag, 848 ipMRouteScopeNameString SnmpAdminString, 849 ipMRouteScopeNameDefault TruthValue, 850 ipMRouteScopeNameStatus RowStatus 851 } 853 ipMRouteScopeNameAddress OBJECT-TYPE 854 SYNTAX IpAddress 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "The group address which when combined with the 859 corresponding value of ipMRouteScopeNameAddressMask 860 identifies the group range associated with the multicast 861 scope. Scoped addresses must come from the range 862 239.x.x.x." 863 ::= { ipMRouteScopeNameEntry 1 } 865 ipMRouteScopeNameAddressMask OBJECT-TYPE 866 SYNTAX IpAddress 867 MAX-ACCESS not-accessible 868 STATUS current 869 DESCRIPTION 870 "The group address mask which when combined with the 871 corresponding value of ipMRouteScopeNameAddress identifies 872 the group range associated with the multicast scope." 873 ::= { ipMRouteScopeNameEntry 2 } 875 ipMRouteScopeNameLanguage OBJECT-TYPE 876 SYNTAX LanguageTag 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "The RFC 1766-style language tag associated with the scope 882 Draft IPv4 Multicast Routing MIB July 2000 884 name." 885 ::= { ipMRouteScopeNameEntry 3 } 887 ipMRouteScopeNameString OBJECT-TYPE 888 SYNTAX SnmpAdminString 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "The textual name associated with the multicast scope. The 893 value of this object should be suitable for displaying to 894 end-users, such as when allocating a multicast address in 895 this scope. When no name is specified, the default value of 896 this object should be the string 239.x.x.x/y with x and y 897 replaced appropriately to describe the address and mask 898 length associated with the scope." 899 ::= { ipMRouteScopeNameEntry 4 } 901 ipMRouteScopeNameDefault OBJECT-TYPE 902 SYNTAX TruthValue 903 MAX-ACCESS read-create 904 STATUS current 905 DESCRIPTION 906 "If true, indicates a preference that the name in the 907 following language should be used by applications if no name 908 is available in a desired language." 909 DEFVAL { false } 910 ::= { ipMRouteScopeNameEntry 5 } 912 ipMRouteScopeNameStatus OBJECT-TYPE 913 SYNTAX RowStatus 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "The status of this row, by which new entries may be 918 created, or old entries deleted from this table." 919 ::= { ipMRouteScopeNameEntry 6 } 921 Draft IPv4 Multicast Routing MIB July 2000 923 -- conformance information 925 ipMRouteMIBConformance 926 OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 } 927 ipMRouteMIBCompliances 928 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 929 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 931 -- compliance statements 933 ipMRouteMIBCompliance MODULE-COMPLIANCE 934 STATUS current 935 DESCRIPTION 936 "The compliance statement for the IP Multicast MIB." 937 MODULE -- this module 938 MANDATORY-GROUPS { ipMRouteMIBBasicGroup, 939 ipMRouteMIBRouteGroup} 941 GROUP ipMRouteMIBBoundaryGroup 942 DESCRIPTION 943 "This group is mandatory if the router supports 944 administratively-scoped multicast address boundaries." 946 OBJECT ipMRouteBoundaryStatus 947 MIN-ACCESS read-only 948 DESCRIPTION 949 "Write access is not required." 951 OBJECT ipMRouteScopeNameStatus 952 MIN-ACCESS read-only 953 DESCRIPTION 954 "Write access is not required." 956 GROUP ipMRouteMIBHCInterfaceGroup 957 DESCRIPTION 958 "This group is mandatory only for those network interfaces 959 for which the value of the corresponding instance of ifSpeed 960 is greater than 20,000,000 bits/second." 962 ::= { ipMRouteMIBCompliances 1 } 964 -- units of conformance 965 Draft IPv4 Multicast Routing MIB July 2000 967 ipMRouteMIBBasicGroup OBJECT-GROUP 968 OBJECTS { ipMRouteEnable, ipMRouteEntryCount, 969 ipMRouteUpstreamNeighbor, ipMRouteInIfIndex, 970 ipMRouteUpTime, ipMRouteExpiryTime, 971 ipMRouteNextHopState, 972 ipMRouteNextHopUpTime, 973 ipMRouteNextHopExpiryTime, 974 ipMRouteNextHopProtocol, 975 ipMRouteNextHopPkts, 976 ipMRouteInterfaceTtl, 977 ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, 978 ipMRouteInterfaceInMcastOctets, 979 ipMRouteInterfaceOutMcastOctets, 980 ipMRouteProtocol 981 } 982 STATUS current 983 DESCRIPTION 984 "A collection of objects to support basic management of IP 985 Multicast routing." 986 ::= { ipMRouteMIBGroups 1 } 988 ipMRouteMIBHopCountGroup OBJECT-GROUP 989 OBJECTS { ipMRouteNextHopClosestMemberHops } 990 STATUS current 991 DESCRIPTION 992 "A collection of objects to support management of the use of 993 hop counts in IP Multicast routing." 994 ::= { ipMRouteMIBGroups 2 } 996 ipMRouteMIBBoundaryGroup OBJECT-GROUP 997 OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString, 998 ipMRouteScopeNameDefault, ipMRouteScopeNameStatus } 999 STATUS current 1000 DESCRIPTION 1001 "A collection of objects to support management of scoped 1002 multicast address boundaries." 1003 ::= { ipMRouteMIBGroups 3 } 1005 ipMRouteMIBPktsOutGroup OBJECT-GROUP 1006 OBJECTS { ipMRouteNextHopPkts } 1007 STATUS current 1008 DESCRIPTION 1009 "A collection of objects to support management of packet 1010 counters for each outgoing interface entry of a route." 1011 ::= { ipMRouteMIBGroups 4 } 1013 Draft IPv4 Multicast Routing MIB July 2000 1015 ipMRouteMIBHCInterfaceGroup OBJECT-GROUP 1016 OBJECTS { ipMRouteInterfaceHCInMcastOctets, 1017 ipMRouteInterfaceHCOutMcastOctets, 1018 ipMRouteHCOctets } 1019 STATUS current 1020 DESCRIPTION 1021 "A collection of objects providing information specific to 1022 high speed (greater than 20,000,000 bits/second) network 1023 interfaces." 1024 ::= { ipMRouteMIBGroups 5 } 1026 ipMRouteMIBRouteGroup OBJECT-GROUP 1027 OBJECTS { ipMRouteRtProto, ipMRouteRtAddress, 1028 ipMRouteRtMask, ipMRouteRtType } 1029 STATUS current 1030 DESCRIPTION 1031 "A collection of objects providing information on the 1032 relationship between multicast routing information, and the 1033 IP Forwarding Table." 1034 ::= { ipMRouteMIBGroups 6 } 1036 ipMRouteMIBPktsGroup OBJECT-GROUP 1037 OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, 1038 ipMRouteOctets } 1039 STATUS current 1040 DESCRIPTION 1041 "A collection of objects to support management of packet 1042 counters for each forwarding entry." 1043 ::= { ipMRouteMIBGroups 7 } 1045 END 1046 Draft IPv4 Multicast Routing MIB July 2000 1048 6. IANA Considerations 1050 The ipMRouteRtProto, ipMRouteNextHopProtocol, ipMRouteInterfaceProtocol, 1051 and ipMRouteProtocol use textual conventions imported from the IANA- 1052 RTPROTO-MIB. The purpose of defining these textual conventions in a 1053 separate MIB module is to allow additional values to be defined without 1054 having to issue a new version of this document. The Internet Assigned 1055 Numbers Authority (IANA) is responsible for the assignment of all 1056 Internet numbers, including various SNMP-related numbers; it will 1057 administer the values associated with these textual conventions. 1059 The rules for additions or changes to the IANA-RTPROTO-MIB are outlined 1060 in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. 1062 The current versions of the IANA-RTPROTO-MIB can be accessed from the 1063 IANA home page at: "http://www.iana.org/". 1065 7. Security Considerations 1067 This MIB contains readable objects whose values provide information 1068 related to multicast routing, including information on what machines are 1069 sending to which groups. There are also a number of objects that have a 1070 MAX-ACCESS clause of read-write and/or read-create, such as those which 1071 allow an administrator to configure multicast boundaries. 1073 While unauthorized access to the readable objects is relatively 1074 innocuous, unauthorized access to the write-able objects could cause a 1075 denial of service, or could cause wider distribution of packets intended 1076 only for local distribution. Hence, the support for SET operations in a 1077 non-secure environment without proper protection can have a negative 1078 effect on network operations. 1080 SNMPv1 by itself is such an insecure environment. Even if the network 1081 itself is secure (for example by using IPSec), even then, there is no 1082 control as to who on the secure network is allowed to access and SET 1083 (change/create/delete) the objects in this MIB. 1085 It is recommended that the implementers consider the security features 1086 as provided by the SNMPv3 framework. Specifically, the use of the User- 1087 based Security Model RFC 2574 [12] and the View-based Access Control 1088 Model RFC 2575 [15] is recommended. 1090 It is then a customer/user responsibility to ensure that the SNMP entity 1091 giving access to this MIB, is properly configured to give access to 1092 Draft IPv4 Multicast Routing MIB July 2000 1094 those objects only to those principals (users) that have legitimate 1095 rights to access them. 1097 8. IANA Routing Protocol Registration MIB 1099 This appendix defines the initial content of the IANA-RTPROTO-MIB. 1101 NOTE TO RFC-EDITOR: This section should be removed from this document 1102 prior to its publication, at which time this MIB will be administered by 1103 IANA. 1105 IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN 1107 IMPORTS 1108 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1109 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1111 ianaipRouteProtocol MODULE-IDENTITY 1112 LAST-UPDATED "200001311200Z" -- January 31, 2000 1113 ORGANIZATION "IANA" 1114 CONTACT-INFO 1115 " Internet Assigned Numbers Authority 1116 Internet Corporation for Assigned Names and Numbers 1117 4676 Admiralty Way, Suite 330 1118 Marina del Rey, CA 90292-6601 1120 Phone: +1 310 823 9358 1121 EMail: iana@iana.org" 1122 DESCRIPTION 1123 "This MIB module defines the IANAipRouteProtocol and 1124 IANAipMRouteProtocol textual conventions for use in MIBs 1125 which need to identify unicast or multicast routing 1126 mechanisms. 1128 Any additions or changes to the contents of this MIB module 1129 require either publication of an RFC, or Designated Expert 1130 Review as defined in the Guidelines for Writing IANA 1131 Considerations Section document. The Designated Expert will 1132 be selected by the IESG Area Director(s) of the Routing 1133 Area." 1134 ::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA 1136 IANAipRouteProtocol ::= TEXTUAL-CONVENTION 1137 STATUS current 1139 Draft IPv4 Multicast Routing MIB July 2000 1141 DESCRIPTION 1142 "A mechanism for learning routes. Inclusion of values for 1143 routing protocols is not intended to imply that those 1144 protocols need be supported." 1145 SYNTAX INTEGER { 1146 other (1), -- not specified 1147 local (2), -- local interface 1148 netmgmt (3), -- static route 1149 icmp (4), -- result of ICMP Redirect 1151 -- the following are all dynamic 1152 -- routing protocols 1154 egp (5), -- Exterior Gateway Protocol 1155 ggp (6), -- Gateway-Gateway Protocol 1156 hello (7), -- FuzzBall HelloSpeak 1157 rip (8), -- Berkeley RIP or RIP-II 1158 isIs (9), -- Dual IS-IS 1159 esIs (10), -- ISO 9542 1160 ciscoIgrp (11), -- Cisco IGRP 1161 bbnSpfIgp (12), -- BBN SPF IGP 1162 ospf (13), -- Open Shortest Path First 1163 bgp (14), -- Border Gateway Protocol 1164 idpr (15), -- InterDomain Policy Routing 1165 ciscoEigrp (16), -- Cisco EIGRP 1166 dvmrp (17) -- DVMRP 1167 } 1169 IANAipMRouteProtocol ::= TEXTUAL-CONVENTION 1170 STATUS current 1171 DESCRIPTION 1172 "The multicast routing protocol. Inclusion of values for 1173 multicast routing protocols is not intended to imply that 1174 those protocols need be supported." 1175 SYNTAX INTEGER { 1176 other(1), -- none of the following 1177 local(2), -- e.g., manually configured 1178 netmgmt(3), -- set via net.mgmt protocol 1179 dvmrp(4), 1180 mospf(5), 1181 pimSparseDense(6), -- PIMv1, both DM and SM 1182 cbt(7), 1183 pimSparseMode(8), -- PIM-SM 1184 pimDenseMode(9), -- PIM-DM 1185 igmpOnly(10), 1187 Draft IPv4 Multicast Routing MIB July 2000 1189 bgmp(11), 1190 msdp(12) 1191 } 1193 END 1195 9. Intellectual Property Notice 1197 The IETF takes no position regarding the validity or scope of any 1198 intellectual property or other rights that might be claimed to pertain 1199 to the implementation or use of the technology described in this 1200 document or the extent to which any license under such rights might or 1201 might not be available; neither does it represent that it has made any 1202 effort to identify any such rights. Information on the IETF's 1203 procedures with respect to rights in standards-track and standards- 1204 related documentation can be found in BCP-11. Copies of claims of 1205 rights made available for publication and any assurances of licenses to 1206 be made available, or the result of an attempt made to obtain a general 1207 license or permission for the use of such proprietary rights by 1208 implementers or users of this specification can be obtained from the 1209 IETF Secretariat. 1211 The IETF invites any interested party to bring to its attention any 1212 copyrights, patents or patent applications, or other proprietary rights 1213 which may cover technology that may be required to practice this 1214 standard. Please address the information to the IETF Executive 1215 Director. 1217 10. Acknowledgements 1219 This MIB module was updated based on feedback from the IETF's Inter- 1220 Domain Multicast Routing (IDMR) Working Group. 1222 11. Authors' Addresses 1224 Keith McCloghrie 1225 cisco Systems, Inc. 1226 170 West Tasman Drive 1227 San Jose, CA 95134-1706 1228 Phone: +1 408 526 5260 1230 Draft IPv4 Multicast Routing MIB July 2000 1232 EMail: kzm@cisco.com 1234 Dino Farinacci 1235 cisco Systems, Inc. 1236 170 West Tasman Drive 1237 San Jose, CA 95134-1706 1238 Phone: +1 408 526 4696 1239 EMail: dino@cisco.com 1241 Dave Thaler 1242 Microsoft Corporation 1243 One Microsoft Way 1244 Redmond, WA 98052-6399 1245 Phone: +1 425 703 8835 1246 EMail: dthaler@microsoft.com 1248 12. References 1250 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1251 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1252 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1253 1999. 1255 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1256 Management Information for TCP/IP-based Internets", RFC 1155, STD 1257 16, Performance Systems International, Hughes LAN Systems, May 1258 1990. 1260 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1261 STD 16, Performance Systems International, Hughes LAN Systems, 1262 March 1991. 1264 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1265 RFC 1215, Performance Systems International, March 1991. 1267 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1268 and S. Waldbusser, "Structure of Management Information Version 2 1269 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1270 Braunschweig, SNMP Research, First Virtual Holdings, International 1271 Network Services, April 1999. 1273 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1274 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1275 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1277 Draft IPv4 Multicast Routing MIB July 2000 1279 Virtual Holdings, International Network Services, April 1999. 1281 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1282 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1283 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1284 First Virtual Holdings, International Network Services, April 1999. 1286 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1287 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1288 Systems International, Performance Systems International, MIT 1289 Laboratory for Computer Science, May 1990. 1291 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1292 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1293 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1294 International Network Services, January 1996. 1296 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1297 Mappings for Version 2 of the Simple Network Management Protocol 1298 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1299 Dover Beach Consulting, Inc., International Network Services, 1300 January 1996. 1302 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1303 Processing and Dispatching for the Simple Network Management 1304 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1305 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1307 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1308 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1309 2574, IBM T. J. Watson Research, April 1999. 1311 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1312 Operations for Version 2 of the Simple Network Management Protocol 1313 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1314 Dover Beach Consulting, Inc., International Network Services, 1315 January 1996. 1317 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1318 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1319 Systems, April 1999. 1321 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1322 Control Model (VACM) for the Simple Network Management Protocol 1323 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1325 Draft IPv4 Multicast Routing MIB July 2000 1327 Cisco Systems, Inc., April 1999. 1329 [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1330 thesis, Electrical Engineering Dept., Stanford University, December 1331 1991. 1333 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1334 Multicast Routing Protocol", RFC 1075, November 1988. 1336 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1337 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1338 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1339 Specification", RFC 2362, June 1998. 1341 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1342 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1343 Specification". Work in progress, May 1997. 1345 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1347 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1348 Routing", RFC 2189, September 1997. 1350 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1351 23, July 1998. 1353 13. Full Copyright Statement 1355 Copyright (C) The Internet Society (1999). All Rights Reserved. 1357 This document and translations of it may be copied and furnished to 1358 others, and derivative works that comment on or otherwise explain it or 1359 assist in its implmentation may be prepared, copied, published and 1360 distributed, in whole or in part, without restriction of any kind, 1361 provided that the above copyright notice and this paragraph are included 1362 on all such copies and derivative works. However, this document itself 1363 may not be modified in any way, such as by removing the copyright notice 1364 or references to the Internet Society or other Internet organizations, 1365 except as needed for the purpose of developing Internet standards in 1366 which case the procedures for copyrights defined in the Internet 1367 Standards process must be followed, or as required to translate it into 1368 languages other than English. 1370 Draft IPv4 Multicast Routing MIB July 2000 1372 The limited permissions granted above are perpetual and will not be 1373 revoked by the Internet Society or its successors or assigns. 1375 This document and the information contained herein is provided on an "AS 1376 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1377 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1378 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1379 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1380 FITNESS FOR A PARTICULAR PURPOSE. 1382 Table of Contents 1384 1 Abstract ........................................................ 2 1385 2 Introduction .................................................... 2 1386 3 The SNMP Management Framework ................................... 2 1387 4 Overview ........................................................ 3 1388 5 Definitions ..................................................... 4 1389 6 IANA Considerations ............................................. 26 1390 7 Security Considerations ......................................... 26 1391 8 IANA Routing Protocol Registration MIB .......................... 27 1392 9 Intellectual Property Notice .................................... 29 1393 10 Acknowledgements ............................................... 29 1394 11 Authors' Addresses ............................................. 29 1395 12 References ..................................................... 30 1396 13 Full Copyright Statement ....................................... 32