idnits 2.17.1 draft-ietf-idmr-multicast-routmib-12.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 31 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There 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 (19 October 1999) is 8948 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 1257, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1260, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1265, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1271, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1273, 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: 19 errors (**), 0 flaws (~~), 8 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 April 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 19 October 1999 8 IP 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 IP Multicast Routing MIB October 1999 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 IP Multicast Routing MIB October 1999 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 IP Multicast Routing MIB October 1999 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; 139 ipMRouteStdMIB MODULE-IDENTITY 140 LAST-UPDATED "9910191200Z" -- October 19, 1999 141 ORGANIZATION "IETF IDMR Working Group" 142 CONTACT-INFO 143 " Dave Thaler 144 Microsoft Corporation 145 One Microsoft Way 146 Redmond, WA 98052-6399 147 US 149 Phone: +1 425 703 8835 150 EMail: dthaler@dthaler.microsoft.com" 151 DESCRIPTION 152 "The MIB module for management of IP Multicast routing, but 153 independent of the specific multicast routing protocol in 154 use." 155 REVISION "9910191200Z" -- October 19, 1999 156 DESCRIPTION 157 "Initial version, published as RFC xxxx (to be filled in by 158 RFC-Editor)." 159 ::= { mib-2 XX } 160 -- NOTE TO RFC EDITOR: When this document is published as 161 -- an RFC, replace XX with IANA-assigned number, 162 -- and delete this comment. 164 -- Textual Conventions 166 IpMRouteProtocol ::= TEXTUAL-CONVENTION 167 STATUS current 168 DESCRIPTION 170 Draft IP Multicast Routing MIB October 1999 172 "The multicast routing protocol. Inclusion of values for 173 multicast routing protocols is not intended to imply that 174 those protocols need be supported." 175 SYNTAX INTEGER { 176 other(1), -- none of the following 177 local(2), -- e.g., manually configured 178 netmgmt(3), -- set via net.mgmt protocol 179 dvmrp(4), 180 mospf(5), 181 pimSparseDense(6), -- PIMv1, both DM and SM 182 cbt(7), 183 pimSparseMode(8), -- PIM-SM 184 pimDenseMode(9), -- PIM-DM 185 igmpOnly(10), 186 bgmp(11), 187 msdp(12) 188 } 190 LanguageTag ::= TEXTUAL-CONVENTION 191 DISPLAY-HINT "100a" 192 STATUS current 193 DESCRIPTION 194 "An RFC 1766-style language tag, with all alphabetic 195 characters converted to lowercase. This restriction is 196 intended to make the lexical ordering imposed by SNMP useful 197 when applied to language tags. Note that it is 198 theoretically possible for a valid language tag to exceed 199 the allowed length of this syntax, and thus be impossible to 200 represent with this syntax. Sampling of language tags in 201 current use on the Internet suggests that this limit does 202 not pose a serious problem in practice." 203 SYNTAX OCTET STRING (SIZE (1..100)) 205 -- Top-level structure of the MIB 207 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 } 209 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 211 Draft IP Multicast Routing MIB October 1999 213 -- the IP Multicast Routing MIB-Group 214 -- 215 -- a collection of objects providing information about 216 -- IP Multicast Groups 218 ipMRouteEnable OBJECT-TYPE 219 SYNTAX INTEGER { enabled(1), disabled(2) } 220 MAX-ACCESS read-write 221 STATUS current 222 DESCRIPTION 223 "The enabled status of IP Multicast routing on this router." 224 ::= { ipMRoute 1 } 226 ipMRouteEntryCount OBJECT-TYPE 227 SYNTAX Gauge32 228 MAX-ACCESS read-only 229 STATUS current 230 DESCRIPTION 231 "The number of rows in the ipMRouteTable. This can be used 232 to monitor the multicast routing table size." 233 ::= { ipMRoute 7 } 235 ipMRouteTable OBJECT-TYPE 236 SYNTAX SEQUENCE OF IpMRouteEntry 237 MAX-ACCESS not-accessible 238 STATUS current 239 DESCRIPTION 240 "The (conceptual) table containing multicast routing 241 information for IP datagrams sent by particular sources to 242 the IP multicast groups known to this router." 243 ::= { ipMRoute 2 } 245 Draft IP Multicast Routing MIB October 1999 247 ipMRouteEntry OBJECT-TYPE 248 SYNTAX IpMRouteEntry 249 MAX-ACCESS not-accessible 250 STATUS current 251 DESCRIPTION 252 "An entry (conceptual row) containing the multicast routing 253 information for IP datagrams from a particular source and 254 addressed to a particular IP multicast group address. 255 Discontinuities in counters in this entry can be detected by 256 observing the value of ipMRouteUpTime." 257 INDEX { ipMRouteGroup, 258 ipMRouteSource, 259 ipMRouteSourceMask } 260 ::= { ipMRouteTable 1 } 262 IpMRouteEntry ::= SEQUENCE { 263 ipMRouteGroup IpAddress, 264 ipMRouteSource IpAddress, 265 ipMRouteSourceMask IpAddress, 266 ipMRouteUpstreamNeighbor IpAddress, 267 ipMRouteInIfIndex InterfaceIndexOrZero, 268 ipMRouteUpTime TimeTicks, 269 ipMRouteExpiryTime TimeTicks, 270 ipMRoutePkts Counter32, 271 ipMRouteDifferentInIfPackets Counter32, 272 ipMRouteOctets Counter32, 273 ipMRouteProtocol IpMRouteProtocol, 274 ipMRouteRtProto INTEGER, 275 ipMRouteRtAddress IpAddress, 276 ipMRouteRtMask IpAddress, 277 ipMRouteRtType INTEGER, 278 ipMRouteHCOctets Counter64 279 } 281 ipMRouteGroup OBJECT-TYPE 282 SYNTAX IpAddress 283 MAX-ACCESS not-accessible 284 STATUS current 285 DESCRIPTION 286 "The IP multicast group address for which this entry 287 contains multicast routing information." 288 ::= { ipMRouteEntry 1 } 290 ipMRouteSource OBJECT-TYPE 291 SYNTAX IpAddress 293 Draft IP Multicast Routing MIB October 1999 295 MAX-ACCESS not-accessible 296 STATUS current 297 DESCRIPTION 298 "The network address which when combined with the 299 corresponding value of ipMRouteSourceMask identifies the 300 sources for which this entry contains multicast routing 301 information." 302 ::= { ipMRouteEntry 2 } 304 ipMRouteSourceMask OBJECT-TYPE 305 SYNTAX IpAddress 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "The network mask which when combined with the corresponding 310 value of ipMRouteSource identifies the sources for which 311 this entry contains multicast routing information." 312 ::= { ipMRouteEntry 3 } 314 ipMRouteUpstreamNeighbor OBJECT-TYPE 315 SYNTAX IpAddress 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The address of the upstream neighbor (e.g., RPF neighbor) 320 from which IP datagrams from these sources to this multicast 321 address are received, or 0.0.0.0 if the upstream neighbor is 322 unknown (e.g., in CBT)." 323 ::= { ipMRouteEntry 4 } 325 ipMRouteInIfIndex OBJECT-TYPE 326 SYNTAX InterfaceIndexOrZero 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "The value of ifIndex for the interface on which IP 331 datagrams sent by these sources to this multicast address 332 are received. A value of 0 indicates that datagrams are not 333 subject to an incoming interface check, but may be accepted 334 on multiple interfaces (e.g., in CBT)." 335 ::= { ipMRouteEntry 5 } 337 ipMRouteUpTime OBJECT-TYPE 338 SYNTAX TimeTicks 339 MAX-ACCESS read-only 341 Draft IP Multicast Routing MIB October 1999 343 STATUS current 344 DESCRIPTION 345 "The time since the multicast routing information 346 represented by this entry was learned by the router." 347 ::= { ipMRouteEntry 6 } 349 ipMRouteExpiryTime OBJECT-TYPE 350 SYNTAX TimeTicks 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The minimum amount of time remaining before this entry will 355 be aged out. The value 0 indicates that the entry is not 356 subject to aging." 357 ::= { ipMRouteEntry 7 } 359 ipMRoutePkts OBJECT-TYPE 360 SYNTAX Counter32 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The number of packets which this router has received from 365 these sources and addressed to this multicast group 366 address." 367 ::= { ipMRouteEntry 8 } 369 ipMRouteDifferentInIfPackets OBJECT-TYPE 370 SYNTAX Counter32 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The number of packets which this router has received from 375 these sources and addressed to this multicast group address, 376 which were dropped because they were not received on the 377 interface indicated by ipMRouteInIfIndex. Packets which are 378 not subject to an incoming interface check (e.g., using CBT) 379 are not counted." 380 ::= { ipMRouteEntry 9 } 382 ipMRouteOctets OBJECT-TYPE 383 SYNTAX Counter32 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The number of octets contained in IP datagrams which were 389 Draft IP Multicast Routing MIB October 1999 391 received from these sources and addressed to this multicast 392 group address, and which were forwarded by this router." 393 ::= { ipMRouteEntry 10 } 395 ipMRouteProtocol OBJECT-TYPE 396 SYNTAX IpMRouteProtocol 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The multicast routing protocol via which this multicast 401 forwarding entry was learned." 402 ::= { ipMRouteEntry 11 } 404 ipMRouteRtProto OBJECT-TYPE 405 SYNTAX INTEGER { 406 other (1), -- not specified 407 local (2), -- local interface 408 netmgmt (3), -- static route 409 icmp (4), -- result of ICMP Redirect 410 -- the following are all dynamic 411 -- routing protocols 412 egp (5), -- Exterior Gateway Protocol 413 ggp (6), -- Gateway-Gateway Protocol 414 hello (7), -- FuzzBall HelloSpeak 415 rip (8), -- Berkeley RIP or RIP-II 416 isIs (9), -- Dual IS-IS 417 esIs (10), -- ISO 9542 418 ciscoIgrp (11), -- Cisco IGRP 419 bbnSpfIgp (12), -- BBN SPF IGP 420 ospf (13), -- Open Shortest Path First 421 bgp (14), -- Border Gateway Protocol 422 idpr (15), -- InterDomain Policy Routing 423 ciscoEigrp (16), -- Cisco EIGRP 424 dvmrp (17) -- DVMRP 425 } 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "The routing mechanism via which the route used to find the 430 upstream or parent interface for this multicast forwarding 431 entry was learned. Inclusion of values for routing 432 protocols is not intended to imply that those protocols need 433 be supported." 434 ::= { ipMRouteEntry 12 } 436 Draft IP Multicast Routing MIB October 1999 438 ipMRouteRtAddress OBJECT-TYPE 439 SYNTAX IpAddress 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "The address portion of the route used to find the upstream 444 or parent interface for this multicast forwarding entry." 445 ::= { ipMRouteEntry 13 } 447 ipMRouteRtMask OBJECT-TYPE 448 SYNTAX IpAddress 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The mask associated with the route used to find the upstream 453 or parent interface for this multicast forwarding entry." 454 ::= { ipMRouteEntry 14 } 456 ipMRouteRtType OBJECT-TYPE 457 SYNTAX INTEGER { 458 unicast (1), -- Unicast route used in multicast RIB 459 multicast (2) -- Multicast route 460 } 461 MAX-ACCESS read-only 462 STATUS current 463 DESCRIPTION 464 "The reason the given route was placed in the (logical) 465 multicast Routing Information Base (RIB). A value of 466 unicast means that the route would normally be placed only 467 in the unicast RIB, but was placed in the multicast RIB 468 (instead or in addition) due to local configuration, such as 469 when running PIM over RIP. A value of multicast means that 470 the route was explicitly added to the multicast RIB by the 471 routing protocol, such as DVMRP or Multiprotocol BGP." 472 ::= { ipMRouteEntry 15 } 474 ipMRouteHCOctets OBJECT-TYPE 475 SYNTAX Counter64 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The number of octets contained in IP datagrams which were 480 received from these sources and addressed to this multicast 481 group address, and which were forwarded by this router. 482 This object is a 64-bit version of ipMRouteOctets." 484 Draft IP Multicast Routing MIB October 1999 486 ::= { ipMRouteEntry 16 } 488 -- 489 -- The IP Multicast Routing Next Hop Table 490 -- 492 ipMRouteNextHopTable OBJECT-TYPE 493 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "The (conceptual) table containing information on the next- 498 hops on outgoing interfaces for routing IP multicast 499 datagrams. Each entry is one of a list of next-hops on 500 outgoing interfaces for particular sources sending to a 501 particular multicast group address." 502 ::= { ipMRoute 3 } 504 ipMRouteNextHopEntry OBJECT-TYPE 505 SYNTAX IpMRouteNextHopEntry 506 MAX-ACCESS not-accessible 507 STATUS current 508 DESCRIPTION 509 "An entry (conceptual row) in the list of next-hops on 510 outgoing interfaces to which IP multicast datagrams from 511 particular sources to a IP multicast group address are 512 routed. Discontinuities in counters in this entry can be 513 detected by observing the value of ipMRouteUpTime." 514 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 515 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 516 ipMRouteNextHopAddress } 517 ::= { ipMRouteNextHopTable 1 } 519 Draft IP Multicast Routing MIB October 1999 521 IpMRouteNextHopEntry ::= SEQUENCE { 522 ipMRouteNextHopGroup IpAddress, 523 ipMRouteNextHopSource IpAddress, 524 ipMRouteNextHopSourceMask IpAddress, 525 ipMRouteNextHopIfIndex InterfaceIndex, 526 ipMRouteNextHopAddress IpAddress, 527 ipMRouteNextHopState INTEGER, 528 ipMRouteNextHopUpTime TimeTicks, 529 ipMRouteNextHopExpiryTime TimeTicks, 530 ipMRouteNextHopClosestMemberHops Integer32, 531 ipMRouteNextHopProtocol IpMRouteProtocol, 532 ipMRouteNextHopPkts Counter32 533 } 535 ipMRouteNextHopGroup OBJECT-TYPE 536 SYNTAX IpAddress 537 MAX-ACCESS not-accessible 538 STATUS current 539 DESCRIPTION 540 "The IP multicast group for which this entry specifies a 541 next-hop on an outgoing interface." 542 ::= { ipMRouteNextHopEntry 1 } 544 ipMRouteNextHopSource OBJECT-TYPE 545 SYNTAX IpAddress 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "The network address which when combined with the 550 corresponding value of ipMRouteNextHopSourceMask identifies 551 the sources for which this entry specifies a next-hop on an 552 outgoing interface." 553 ::= { ipMRouteNextHopEntry 2 } 555 ipMRouteNextHopSourceMask OBJECT-TYPE 556 SYNTAX IpAddress 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "The network mask which when combined with the corresponding 561 value of ipMRouteNextHopSource identifies the sources for 562 which this entry specifies a next-hop on an outgoing 563 interface." 564 ::= { ipMRouteNextHopEntry 3 } 566 Draft IP Multicast Routing MIB October 1999 568 ipMRouteNextHopIfIndex OBJECT-TYPE 569 SYNTAX InterfaceIndex 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "The ifIndex value of the interface for the outgoing 574 interface for this next-hop." 575 ::= { ipMRouteNextHopEntry 4 } 577 ipMRouteNextHopAddress OBJECT-TYPE 578 SYNTAX IpAddress 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "The address of the next-hop specific to this entry. For 583 most interfaces, this is identical to ipMRouteNextHopGroup. 584 NBMA interfaces, however, may have multiple next-hop 585 addresses out a single outgoing interface." 586 ::= { ipMRouteNextHopEntry 5 } 588 ipMRouteNextHopState OBJECT-TYPE 589 SYNTAX INTEGER { pruned(1), forwarding(2) } 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "An indication of whether the outgoing interface and next- 594 hop represented by this entry is currently being used to 595 forward IP datagrams. The value 'forwarding' indicates it 596 is currently being used; the value 'pruned' indicates it is 597 not." 598 ::= { ipMRouteNextHopEntry 6 } 600 ipMRouteNextHopUpTime OBJECT-TYPE 601 SYNTAX TimeTicks 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The time since the multicast routing information 606 represented by this entry was learned by the router." 607 ::= { ipMRouteNextHopEntry 7 } 609 ipMRouteNextHopExpiryTime OBJECT-TYPE 610 SYNTAX TimeTicks 611 MAX-ACCESS read-only 612 STATUS current 614 Draft IP Multicast Routing MIB October 1999 616 DESCRIPTION 617 "The minimum amount of time remaining before this entry will 618 be aged out. If ipMRouteNextHopState is pruned(1), the 619 remaining time until the prune expires and the state reverts 620 to forwarding(2). Otherwise, the remaining time until this 621 entry is removed from the table. The time remaining may be 622 copied from ipMRouteExpiryTime if the protocol in use for 623 this entry dos not specify next-hop timers. The value 0 624 indicates that the entry is not subject to aging." 625 ::= { ipMRouteNextHopEntry 8 } 627 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 628 SYNTAX Integer32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The minimum number of hops between this router and any 633 member of this IP multicast group reached via this next-hop 634 on this outgoing interface. Any IP multicast datagrams for 635 the group which have a TTL less than this number of hops 636 will not be forwarded to this next-hop." 637 ::= { ipMRouteNextHopEntry 9 } 639 ipMRouteNextHopProtocol OBJECT-TYPE 640 SYNTAX IpMRouteProtocol 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The routing mechanism via which this next-hop was learned." 645 ::= { ipMRouteNextHopEntry 10 } 647 ipMRouteNextHopPkts OBJECT-TYPE 648 SYNTAX Counter32 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "The number of packets which have been forwarded using this 653 route." 654 ::= { ipMRouteNextHopEntry 11 } 656 Draft IP Multicast Routing MIB October 1999 658 -- 659 -- The Multicast Routing Interface Table 660 -- 662 ipMRouteInterfaceTable OBJECT-TYPE 663 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "The (conceptual) table containg multicast routing 668 information specific to interfaces." 669 ::= { ipMRoute 4 } 671 ipMRouteInterfaceEntry OBJECT-TYPE 672 SYNTAX IpMRouteInterfaceEntry 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION 676 "An entry (conceptual row) containing the multicast routing 677 information for a particular interface." 678 INDEX { ipMRouteInterfaceIfIndex } 679 ::= { ipMRouteInterfaceTable 1 } 681 IpMRouteInterfaceEntry ::= SEQUENCE { 682 ipMRouteInterfaceIfIndex InterfaceIndex, 683 ipMRouteInterfaceTtl Integer32, 684 ipMRouteInterfaceProtocol IpMRouteProtocol, 685 ipMRouteInterfaceRateLimit Integer32, 686 ipMRouteInterfaceInMcastOctets Counter32, 687 ipMRouteInterfaceOutMcastOctets Counter32, 688 ipMRouteInterfaceHCInMcastOctets Counter64, 689 ipMRouteInterfaceHCOutMcastOctets Counter64 690 } 692 ipMRouteInterfaceIfIndex OBJECT-TYPE 693 SYNTAX InterfaceIndex 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "The ifIndex value of the interface for which this entry 698 contains information." 699 ::= { ipMRouteInterfaceEntry 1 } 701 ipMRouteInterfaceTtl OBJECT-TYPE 702 SYNTAX Integer32 (0..255) 704 Draft IP Multicast Routing MIB October 1999 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 "The datagram TTL threshold for the interface. Any IP 710 multicast datagrams with a TTL less than this threshold will 711 not be forwarded out the interface. The default value of 0 712 means all multicast packets are forwarded out the 713 interface." 714 ::= { ipMRouteInterfaceEntry 2 } 716 ipMRouteInterfaceProtocol OBJECT-TYPE 717 SYNTAX IpMRouteProtocol 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "The routing protocol running on this interface." 722 ::= { ipMRouteInterfaceEntry 3 } 724 ipMRouteInterfaceRateLimit OBJECT-TYPE 725 SYNTAX Integer32 726 MAX-ACCESS read-write 727 STATUS current 728 DESCRIPTION 729 "The rate-limit, in kilobits per second, of forwarded 730 multicast traffic on the interface. A rate-limit of 0 731 indicates that no rate limiting is done." 732 DEFVAL { 0 } 733 ::= { ipMRouteInterfaceEntry 4 } 735 ipMRouteInterfaceInMcastOctets OBJECT-TYPE 736 SYNTAX Counter32 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "The number of octets of multicast packets that have arrived 741 on the interface, including framing characters. This object 742 is similar to ifInOctets in the Interfaces MIB, except that 743 only multicast packets are counted." 744 ::= { ipMRouteInterfaceEntry 5 } 746 ipMRouteInterfaceOutMcastOctets OBJECT-TYPE 747 SYNTAX Counter32 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 752 Draft IP Multicast Routing MIB October 1999 754 "The number of octets of multicast packets that have been 755 sent on the interface." 756 ::= { ipMRouteInterfaceEntry 6 } 758 ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE 759 SYNTAX Counter64 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The number of octets of multicast packets that have arrived 764 on the interface, including framing characters. This object 765 is a 64-bit version of ipMRouteInterfaceInMcastOctets. It 766 is similar to ifHCInOctets in the Interfaces MIB, except 767 that only multicast packets are counted." 768 ::= { ipMRouteInterfaceEntry 7 } 770 ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 771 SYNTAX Counter64 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The number of octets of multicast packets that have been 776 sent on the interface. This object is a 64-bit version of 777 ipMRouteInterfaceOutMcastOctets." 778 ::= { ipMRouteInterfaceEntry 8 } 780 Draft IP Multicast Routing MIB October 1999 782 -- 783 -- The IP Multicast Scope Boundary Table 784 -- 786 ipMRouteBoundaryTable OBJECT-TYPE 787 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "The (conceptual) table listing the router's scoped 792 multicast address boundaries." 793 ::= { ipMRoute 5 } 795 ipMRouteBoundaryEntry OBJECT-TYPE 796 SYNTAX IpMRouteBoundaryEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "An entry (conceptual row) in the ipMRouteBoundaryTable 801 representing a scoped boundary." 802 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 803 ipMRouteBoundaryAddressMask } 804 ::= { ipMRouteBoundaryTable 1 } 806 IpMRouteBoundaryEntry ::= SEQUENCE { 807 ipMRouteBoundaryIfIndex InterfaceIndex, 808 ipMRouteBoundaryAddress IpAddress, 809 ipMRouteBoundaryAddressMask IpAddress, 810 ipMRouteBoundaryStatus RowStatus 811 } 813 ipMRouteBoundaryIfIndex OBJECT-TYPE 814 SYNTAX InterfaceIndex 815 MAX-ACCESS not-accessible 816 STATUS current 817 DESCRIPTION 818 "The IfIndex value for the interface to which this boundary 819 applies. Packets with a destination address in the 820 associated address/mask range will not be forwarded out this 821 interface." 822 ::= { ipMRouteBoundaryEntry 1 } 824 ipMRouteBoundaryAddress OBJECT-TYPE 825 SYNTAX IpAddress 826 MAX-ACCESS not-accessible 828 Draft IP Multicast Routing MIB October 1999 830 STATUS current 831 DESCRIPTION 832 "The group address which when combined with the 833 corresponding value of ipMRouteBoundaryAddressMask 834 identifies the group range for which the scoped boundary 835 exists. Scoped addresses must come from the range 239.x.x.x 836 as specified in RFC 2365." 837 ::= { ipMRouteBoundaryEntry 2 } 839 ipMRouteBoundaryAddressMask OBJECT-TYPE 840 SYNTAX IpAddress 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "The group address mask which when combined with the 845 corresponding value of ipMRouteBoundaryAddress identifies 846 the group range for which the scoped boundary exists." 847 ::= { ipMRouteBoundaryEntry 3 } 849 ipMRouteBoundaryStatus OBJECT-TYPE 850 SYNTAX RowStatus 851 MAX-ACCESS read-create 852 STATUS current 853 DESCRIPTION 854 "The status of this row, by which new entries may be 855 created, or old entries deleted from this table." 856 ::= { ipMRouteBoundaryEntry 4 } 858 -- 859 -- The IP Multicast Scope Name Table 860 -- 862 ipMRouteScopeNameTable OBJECT-TYPE 863 SYNTAX SEQUENCE OF IpMRouteScopeNameEntry 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "The (conceptual) table listing the multicast scope names." 868 ::= { ipMRoute 6 } 870 ipMRouteScopeNameEntry OBJECT-TYPE 871 SYNTAX IpMRouteScopeNameEntry 872 MAX-ACCESS not-accessible 873 STATUS current 875 Draft IP Multicast Routing MIB October 1999 877 DESCRIPTION 878 "An entry (conceptual row) in the ipMRouteScopeNameTable 879 representing a multicast scope name." 880 INDEX { ipMRouteScopeNameAddress, 881 ipMRouteScopeNameAddressMask, 882 IMPLIED ipMRouteScopeNameLanguage } 883 ::= { ipMRouteScopeNameTable 1 } 885 IpMRouteScopeNameEntry ::= SEQUENCE { 886 ipMRouteScopeNameAddress IpAddress, 887 ipMRouteScopeNameAddressMask IpAddress, 888 ipMRouteScopeNameLanguage LanguageTag, 889 ipMRouteScopeNameString SnmpAdminString, 890 ipMRouteScopeNameDefault TruthValue, 891 ipMRouteScopeNameStatus RowStatus 892 } 894 ipMRouteScopeNameAddress OBJECT-TYPE 895 SYNTAX IpAddress 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "The group address which when combined with the 900 corresponding value of ipMRouteScopeNameAddressMask 901 identifies the group range associated with the multicast 902 scope. Scoped addresses must come from the range 903 239.x.x.x." 904 ::= { ipMRouteScopeNameEntry 1 } 906 ipMRouteScopeNameAddressMask OBJECT-TYPE 907 SYNTAX IpAddress 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "The group address mask which when combined with the 912 corresponding value of ipMRouteScopeNameAddress identifies 913 the group range associated with the multicast scope." 914 ::= { ipMRouteScopeNameEntry 2 } 916 ipMRouteScopeNameLanguage OBJECT-TYPE 917 SYNTAX LanguageTag 918 MAX-ACCESS not-accessible 919 STATUS current 920 DESCRIPTION 921 "The RFC 1766-style language tag associated with the scope 923 Draft IP Multicast Routing MIB October 1999 925 name." 926 ::= { ipMRouteScopeNameEntry 3 } 928 ipMRouteScopeNameString OBJECT-TYPE 929 SYNTAX SnmpAdminString 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "The textual name associated with the multicast scope. The 934 value of this object should be suitable for displaying to 935 end-users, such as when allocating a multicast address in 936 this scope. When no name is specified, the default value of 937 this object should be the string 239.x.x.x/y with x and y 938 replaced appropriately to describe the address and mask 939 length associated with the scope." 940 ::= { ipMRouteScopeNameEntry 4 } 942 ipMRouteScopeNameDefault OBJECT-TYPE 943 SYNTAX TruthValue 944 MAX-ACCESS read-create 945 STATUS current 946 DESCRIPTION 947 "If true, indicates a preference that the name in the 948 following language should be used by applications if no name 949 is available in a desired language." 950 DEFVAL { false } 951 ::= { ipMRouteScopeNameEntry 5 } 953 ipMRouteScopeNameStatus OBJECT-TYPE 954 SYNTAX RowStatus 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "The status of this row, by which new entries may be 959 created, or old entries deleted from this table." 960 ::= { ipMRouteScopeNameEntry 6 } 962 Draft IP Multicast Routing MIB October 1999 964 -- conformance information 966 ipMRouteMIBConformance 967 OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 } 968 ipMRouteMIBCompliances 969 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 970 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 972 -- compliance statements 974 ipMRouteMIBCompliance MODULE-COMPLIANCE 975 STATUS current 976 DESCRIPTION 977 "The compliance statement for the IP Multicast MIB." 978 MODULE -- this module 979 MANDATORY-GROUPS { ipMRouteMIBBasicGroup, 980 ipMRouteMIBRouteGroup} 982 GROUP ipMRouteMIBBoundaryGroup 983 DESCRIPTION 984 "This group is mandatory if the router supports 985 administratively-scoped multicast address boundaries." 987 OBJECT ipMRouteBoundaryStatus 988 MIN-ACCESS read-only 989 DESCRIPTION 990 "Write access is not required." 992 OBJECT ipMRouteScopeNameStatus 993 MIN-ACCESS read-only 994 DESCRIPTION 995 "Write access is not required." 997 GROUP ipMRouteMIBHCInterfaceGroup 998 DESCRIPTION 999 "This group is mandatory only for those network interfaces 1000 for which the value of the corresponding instance of ifSpeed 1001 is greater than 20,000,000 bits/second." 1003 ::= { ipMRouteMIBCompliances 1 } 1005 -- units of conformance 1007 Draft IP Multicast Routing MIB October 1999 1009 ipMRouteMIBBasicGroup OBJECT-GROUP 1010 OBJECTS { ipMRouteEnable, ipMRouteEntryCount, 1011 ipMRouteUpstreamNeighbor, ipMRouteInIfIndex, 1012 ipMRouteUpTime, ipMRouteExpiryTime, 1013 ipMRouteNextHopState, 1014 ipMRouteNextHopUpTime, 1015 ipMRouteNextHopExpiryTime, 1016 ipMRouteNextHopProtocol, 1017 ipMRouteNextHopPkts, 1018 ipMRouteInterfaceTtl, 1019 ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, 1020 ipMRouteInterfaceInMcastOctets, 1021 ipMRouteInterfaceOutMcastOctets, 1022 ipMRouteProtocol 1023 } 1024 STATUS current 1025 DESCRIPTION 1026 "A collection of objects to support basic management of IP 1027 Multicast routing." 1028 ::= { ipMRouteMIBGroups 1 } 1030 ipMRouteMIBHopCountGroup OBJECT-GROUP 1031 OBJECTS { ipMRouteNextHopClosestMemberHops } 1032 STATUS current 1033 DESCRIPTION 1034 "A collection of objects to support management of the use of 1035 hop counts in IP Multicast routing." 1036 ::= { ipMRouteMIBGroups 2 } 1038 ipMRouteMIBBoundaryGroup OBJECT-GROUP 1039 OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString, 1040 ipMRouteScopeNameDefault, ipMRouteScopeNameStatus } 1041 STATUS current 1042 DESCRIPTION 1043 "A collection of objects to support management of scoped 1044 multicast address boundaries." 1045 ::= { ipMRouteMIBGroups 3 } 1047 ipMRouteMIBPktsOutGroup OBJECT-GROUP 1048 OBJECTS { ipMRouteNextHopPkts } 1049 STATUS current 1050 DESCRIPTION 1051 "A collection of objects to support management of packet 1052 counters for each outgoing interface entry of a route." 1053 ::= { ipMRouteMIBGroups 4 } 1055 Draft IP Multicast Routing MIB October 1999 1057 ipMRouteMIBHCInterfaceGroup OBJECT-GROUP 1058 OBJECTS { ipMRouteInterfaceHCInMcastOctets, 1059 ipMRouteInterfaceHCOutMcastOctets, 1060 ipMRouteHCOctets } 1061 STATUS current 1062 DESCRIPTION 1063 "A collection of objects providing information specific to 1064 high speed (greater than 20,000,000 bits/second) network 1065 interfaces." 1066 ::= { ipMRouteMIBGroups 5 } 1068 ipMRouteMIBRouteGroup OBJECT-GROUP 1069 OBJECTS { ipMRouteRtProto, ipMRouteRtAddress, 1070 ipMRouteRtMask, ipMRouteRtType } 1071 STATUS current 1072 DESCRIPTION 1073 "A collection of objects providing information on the 1074 relationship between multicast routing information, and the 1075 IP Forwarding Table." 1076 ::= { ipMRouteMIBGroups 6 } 1078 ipMRouteMIBPktsGroup OBJECT-GROUP 1079 OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, 1080 ipMRouteOctets } 1081 STATUS current 1082 DESCRIPTION 1083 "A collection of objects to support management of packet 1084 counters for each forwarding entry." 1085 ::= { ipMRouteMIBGroups 7 } 1087 END 1089 Draft IP Multicast Routing MIB October 1999 1091 6. Security Considerations 1093 This MIB contains readable objects whose values provide information 1094 related to multicast routing, including information on what machines are 1095 sending to which groups. There are also a number of objects that have a 1096 MAX-ACCESS clause of read-write and/or read-create, such as those which 1097 allow an administrator to configure multicast boundaries. 1099 While unauthorized access to the readable objects is relatively 1100 innocuous, unauthorized access to the write-able objects could cause a 1101 denial of service, or could cause wider distribution of packets intended 1102 only for local distribution. Hence, the support for SET operations in a 1103 non-secure environment without proper protection can have a negative 1104 effect on network operations. 1106 SNMPv1 by itself is such an insecure environment. Even if the network 1107 itself is secure (for example by using IPSec), even then, there is no 1108 control as to who on the secure network is allowed to access and SET 1109 (change/create/delete) the objects in this MIB. 1111 It is recommended that the implementers consider the security features 1112 as provided by the SNMPv3 framework. Specifically, the use of the User- 1113 based Security Model RFC 2574 [12] and the View-based Access Control 1114 Model RFC 2575 [15] is recommended. 1116 It is then a customer/user responsibility to ensure that the SNMP entity 1117 giving access to this MIB, is properly configured to give access to 1118 those objects only to those principals (users) that have legitimate 1119 rights to access them. 1121 7. Intellectual Property Notice 1123 The IETF takes no position regarding the validity or scope of any 1124 intellectual property or other rights that might be claimed to pertain 1125 to the implementation or use of the technology described in this 1126 document or the extent to which any license under such rights might or 1127 might not be available; neither does it represent that it has made any 1128 effort to identify any such rights. Information on the IETF's 1129 procedures with respect to rights in standards-track and standards- 1130 related documentation can be found in BCP-11. Copies of claims of 1131 rights made available for publication and any assurances of licenses to 1132 be made available, or the result of an attempt made to obtain a general 1133 license or permission for the use of such proprietary rights by 1135 Draft IP Multicast Routing MIB October 1999 1137 implementers or users of this specification can be obtained from the 1138 IETF Secretariat. 1140 The IETF invites any interested party to bring to its attention any 1141 copyrights, patents or patent applications, or other proprietary rights 1142 which may cover technology that may be required to practice this 1143 standard. Please address the information to the IETF Executive 1144 Director. 1146 8. Acknowledgements 1148 This MIB module was updated based on feedback from the IETF's Inter- 1149 Domain Multicast Routing (IDMR) Working Group. 1151 9. Authors' Addresses 1153 Keith McCloghrie 1154 cisco Systems, Inc. 1155 170 West Tasman Drive 1156 San Jose, CA 95134-1706 1157 Phone: +1 408 526 5260 1158 EMail: kzm@cisco.com 1160 Dino Farinacci 1161 cisco Systems, Inc. 1162 170 West Tasman Drive 1163 San Jose, CA 95134-1706 1164 Phone: +1 408 526 4696 1165 EMail: dino@cisco.com 1167 Dave Thaler 1168 Microsoft Corporation 1169 One Microsoft Way 1170 Redmond, WA 98052-6399 1171 Phone: +1 425 703 8835 1172 EMail: dthaler@microsoft.com 1174 Draft IP Multicast Routing MIB October 1999 1176 10. References 1178 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1179 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1180 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1181 1999. 1183 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1184 Management Information for TCP/IP-based Internets", RFC 1155, STD 1185 16, Performance Systems International, Hughes LAN Systems, May 1186 1990. 1188 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1189 STD 16, Performance Systems International, Hughes LAN Systems, 1190 March 1991. 1192 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1193 RFC 1215, Performance Systems International, March 1991. 1195 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1196 and S. Waldbusser, "Structure of Management Information Version 2 1197 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1198 Braunschweig, SNMP Research, First Virtual Holdings, International 1199 Network Services, April 1999. 1201 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1202 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1203 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1204 Virtual Holdings, International Network Services, April 1999. 1206 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1207 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1208 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1209 First Virtual Holdings, International Network Services, April 1999. 1211 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1212 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1213 Systems International, Performance Systems International, MIT 1214 Laboratory for Computer Science, May 1990. 1216 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1217 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1218 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1219 International Network Services, January 1996. 1221 Draft IP Multicast Routing MIB October 1999 1223 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1224 Mappings for Version 2 of the Simple Network Management Protocol 1225 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1226 Dover Beach Consulting, Inc., International Network Services, 1227 January 1996. 1229 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1230 Processing and Dispatching for the Simple Network Management 1231 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1232 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1234 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1235 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1236 2574, IBM T. J. Watson Research, April 1999. 1238 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1239 Operations for Version 2 of the Simple Network Management Protocol 1240 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1241 Dover Beach Consulting, Inc., International Network Services, 1242 January 1996. 1244 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1245 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1246 Systems, April 1999. 1248 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1249 Control Model (VACM) for the Simple Network Management Protocol 1250 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1251 Cisco Systems, Inc., April 1999. 1253 [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1254 thesis, Electrical Engineering Dept., Stanford University, December 1255 1991. 1257 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1258 Multicast Routing Protocol", RFC 1075, November 1988. 1260 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1261 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1262 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1263 Specification", RFC 2362, June 1998. 1265 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1266 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1267 Specification". Work in progress, May 1997. 1269 Draft IP Multicast Routing MIB October 1999 1271 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1273 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1274 Routing", RFC 2189, September 1997. 1276 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1277 23, July 1998. 1279 11. Full Copyright Statement 1281 Copyright (C) The Internet Society (1999). All Rights Reserved. 1283 This document and translations of it may be copied and furnished to 1284 others, and derivative works that comment on or otherwise explain it or 1285 assist in its implmentation may be prepared, copied, published and 1286 distributed, in whole or in part, without restriction of any kind, 1287 provided that the above copyright notice and this paragraph are included 1288 on all such copies and derivative works. However, this document itself 1289 may not be modified in any way, such as by removing the copyright notice 1290 or references to the Internet Society or other Internet organizations, 1291 except as needed for the purpose of developing Internet standards in 1292 which case the procedures for copyrights defined in the Internet 1293 Standards process must be followed, or as required to translate it into 1294 languages other than English. 1296 The limited permissions granted above are perpetual and will not be 1297 revoked by the Internet Society or its successors or assigns. 1299 This document and the information contained herein is provided on an "AS 1300 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1301 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1302 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1303 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1304 FITNESS FOR A PARTICULAR PURPOSE. 1306 Table of Contents 1308 1 Abstract ........................................................ 2 1309 2 Introduction .................................................... 2 1310 3 The SNMP Management Framework ................................... 2 1311 4 Overview ........................................................ 3 1313 Draft IP Multicast Routing MIB October 1999 1315 5 Definitions ..................................................... 4 1316 6 Security Considerations ......................................... 26 1317 7 Intellectual Property Notice .................................... 26 1318 8 Acknowledgements ................................................ 27 1319 9 Authors' Addresses .............................................. 27 1320 10 References ..................................................... 28 1321 11 Full Copyright Statement ....................................... 30