idnits 2.17.1 draft-ietf-idmr-multicast-routmib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (25 March 1997) is 9892 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) -- Possible downref: Non-RFC (?) normative reference: ref. '5' ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '6') -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '9') -- Possible downref: Non-RFC (?) normative reference: ref. '10' Summary: 15 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDMR Working Group Keith McCloghrie 3 INTERNET-DRAFT Dino Farinacci 4 Expires September 1997 cisco Systems 5 Dave Thaler 6 University of Michigan 7 25 March 1997 9 IP Multicast Routing MIB 10 12 Status of this Memo 14 This document is an Internet Draft. Internet Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet Drafts. 19 Internet Drafts are valid for a maximum of six months and may be 20 updated, replaced, or obsoleted by other documents at any time. It is 21 inappropriate to use Internet Drafts as reference material or to cite 22 them other than as a "work in progress". 24 1. Introduction 26 This memo defines an experimental portion of the Management Information 27 Base (MIB) for use with network management protocols in the Internet 28 community. In particular, it describes managed objects used for 29 managing IP Multicast Routing [5], independent of the specific multicast 30 routing protocol [6,7,8,9,10] in use. Managed objects specific to 31 particular multicast routing protocols are specified elsewhere. 33 Draft IP Multicast Routing MIB March 1997 35 2. Revision History 37 A record of changes which will be removed before publication. 39 26 March 41 (1) added ipMRouteInterfaceProtocol. 43 added protocol values for PIM-DM, PIM-SM, and IGMP-only links. 45 26 November 47 (1) moved ipMRouteNextHopPkts to its own conformance group. 49 9 June 51 (1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts. 53 (2) updated references, etc. 55 28 March 57 (1) renamed ipMRouteNextHopClosestMember to 58 ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes 59 to ipMRouteDifferentInIfPacket. 61 26 February 63 (1) added ipMRouteNextHopAddress as a INDEX variable for the 64 ipMRouteNextHopTable. 66 (2) added ipMRouteNextHopClosestMember and ipMRouteNextHopProtocol 68 (3) added ipMRouteMIBHopCountGroup. 70 (4) specified that an expiry-time of zero means that an entry is not 71 subject to aging. 73 (5) added references for MOSPF and CBT. 75 4 February 77 (1) removed ipMRouteOutList 78 Draft IP Multicast Routing MIB March 1997 80 (2) Modified ipMRouteNextHopTable to be INDEX-ed by 81 ipMRouteNextHopGroup, ipMRouteNextHopSource, 82 ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex. 84 (3) added ipMRouteProtocol 86 (4) replaced "RPF" terminology with "Upstream neighbor". 88 15 July - initial version. 90 Draft IP Multicast Routing MIB March 1997 92 3. The SNMP Network Management Framework 94 The SNMP Network Management Framework presently consists of three major 95 components. They are: 97 o RFC 1902 [1] which defines the SMI, the mechanisms used for 98 describing and naming objects for the purpose of management. 100 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 101 objects for the Internet suite of protocols. 103 o RFC 1157 [3] and RFC 1905 [4] which define two versions of the 104 protocol used for network access to managed objects. 106 The Framework permits new objects to be defined for the purpose of 107 experimentation and evaluation. 109 3.1. Object Definitions 111 Managed objects are accessed via a virtual information store, termed the 112 Management Information Base or MIB. Objects in the MIB are defined 113 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 114 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 115 an administratively assigned name. The object type together with an 116 object instance serves to uniquely identify a specific instantiation of 117 the object. For human convenience, we often use a textual string, 118 termed the descriptor, to refer to the object type. 120 Draft IP Multicast Routing MIB March 1997 122 4. Overview 124 This MIB module contains one scalar and four tables. The tables are: 126 (1) the IP Multicast Route Table containing multicast routing 127 information for IP datagrams sent by particular sources to the IP 128 multicast groups known to a router; 130 (2) the IP Multicast Routing Next Hop Table containing information on 131 the next hops for the routing IP multicast datagrams. Each entry 132 is one of a list of next hops on outgoing interfaces for particular 133 sources sending to a particular multicast group address." 135 (3) the IP Multicast Routing Interface Table containing multicast 136 routing information specific to interfaces. 138 (4) the IP Multicast Scoped Boundary Table containing the scoped 139 multicast address boundaries. 141 Draft IP Multicast Routing MIB March 1997 143 5. Definitions 145 IPMROUTE-MIB DEFINITIONS ::= BEGIN 147 IMPORTS 148 MODULE-IDENTITY, OBJECT-TYPE, experimental, 149 Integer32, Counter32, 150 IpAddress, TimeTicks FROM SNMPv2-SMI 151 RowStatus FROM SNMPv2-TC 152 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 154 ipMRouteMIB MODULE-IDENTITY 155 LAST-UPDATED "9703261620Z" 156 ORGANIZATION "IETF IDMR Working Group." 157 CONTACT-INFO 158 " Keith McCloghrie 159 Cisco Systems, Inc. 160 170 West Tasman Drive 161 San Jose, CA 95134-1706 162 US 164 Phone: +1 408 526 5260 165 EMail: kzm@cisco.com" 166 DESCRIPTION 167 "The MIB module for management of IP Multicast routing, but 168 independent of the specific multicast routing protocol in 169 use." 170 ::= { experimental 60 } 172 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 } 174 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 175 Draft IP Multicast Routing MIB March 1997 177 -- the IP Multicast Routing MIB-Group 178 -- 179 -- a collection of objects providing information about 180 -- IP Multicast Groups 182 ipMRouteEnable OBJECT-TYPE 183 SYNTAX INTEGER { enabled(1), disabled(2) } 184 MAX-ACCESS read-write 185 STATUS current 186 DESCRIPTION 187 "The enabled status of IP Multicast routing on this router." 188 ::= { ipMRoute 1 } 190 ipMRouteTable OBJECT-TYPE 191 SYNTAX SEQUENCE OF IpMRouteEntry 192 MAX-ACCESS not-accessible 193 STATUS current 194 DESCRIPTION 195 "The (conceptual) table containing multicast routing 196 information for IP datagrams sent by particular sources to 197 the IP multicast groups known to this router." 198 ::= { ipMRoute 2 } 200 ipMRouteEntry OBJECT-TYPE 201 SYNTAX IpMRouteEntry 202 MAX-ACCESS not-accessible 203 STATUS current 204 DESCRIPTION 205 "An entry (conceptual row) containing the multicast routing 206 information for IP datagrams from a particular source and 207 addressed to a particular IP multicast group address." 208 INDEX { ipMRouteGroup, 209 ipMRouteSource, 210 ipMRouteSourceMask } 211 ::= { ipMRouteTable 1 } 213 Draft IP Multicast Routing MIB March 1997 215 IpMRouteEntry ::= SEQUENCE { 216 ipMRouteGroup IpAddress, 217 ipMRouteSource IpAddress, 218 ipMRouteSourceMask IpAddress, 219 ipMRouteUpstreamNeighbor IpAddress, 220 ipMRouteInIfIndex Integer32, 221 ipMRouteUpTime TimeTicks, 222 ipMRouteExpiryTime TimeTicks, 223 ipMRoutePkts Counter32, 224 ipMRouteDifferentInIfPackets Counter32, 225 ipMRouteOctets Counter32, 226 ipMRouteProtocol INTEGER 227 } 229 ipMRouteGroup OBJECT-TYPE 230 SYNTAX IpAddress 231 MAX-ACCESS not-accessible 232 STATUS current 233 DESCRIPTION 234 "The IP multicast group address for which this entry 235 contains multicast routing information." 236 ::= { ipMRouteEntry 1 } 238 ipMRouteSource OBJECT-TYPE 239 SYNTAX IpAddress 240 MAX-ACCESS not-accessible 241 STATUS current 242 DESCRIPTION 243 "The network address which when combined with the 244 corresponding value of ipMRouteSourceMask identifies the 245 sources for which this entry contains multicast routing 246 information." 247 ::= { ipMRouteEntry 2 } 249 ipMRouteSourceMask OBJECT-TYPE 250 SYNTAX IpAddress 251 MAX-ACCESS not-accessible 252 STATUS current 253 DESCRIPTION 254 "The network mask which when combined with the corresponding 255 value of ipMRouteSource identifies the sources for which 256 this entry contains multicast routing information." 257 ::= { ipMRouteEntry 3 } 259 ipMRouteUpstreamNeighbor OBJECT-TYPE 260 Draft IP Multicast Routing MIB March 1997 262 SYNTAX IpAddress 263 MAX-ACCESS read-only 264 STATUS current 265 DESCRIPTION 266 "The address of the upstream neighbor (e.g., RPF neighbor) 267 from which IP datagrams from these sources to this multicast 268 address are received." 269 ::= { ipMRouteEntry 4 } 271 ipMRouteInIfIndex OBJECT-TYPE 272 SYNTAX Integer32 273 MAX-ACCESS read-only 274 STATUS current 275 DESCRIPTION 276 "The value of ifIndex for the interface on which IP 277 datagrams sent by these sources to this multicast address 278 are received." 279 ::= { ipMRouteEntry 5 } 281 ipMRouteUpTime OBJECT-TYPE 282 SYNTAX TimeTicks 283 MAX-ACCESS read-only 284 STATUS current 285 DESCRIPTION 286 "The time since the multicast routing information 287 represented by this entry was learned by the router." 288 ::= { ipMRouteEntry 6 } 290 ipMRouteExpiryTime OBJECT-TYPE 291 SYNTAX TimeTicks 292 MAX-ACCESS read-only 293 STATUS current 294 DESCRIPTION 295 "The minimum amount of time remaining before this entry will 296 be aged out. The value 0 indicates that the entry is not 297 subject to aging." 298 ::= { ipMRouteEntry 7 } 300 ipMRoutePkts OBJECT-TYPE 301 SYNTAX Counter32 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "The number of packets which this router has received from 306 these sources and addressed to this multicast group 308 Draft IP Multicast Routing MIB March 1997 310 address." 311 ::= { ipMRouteEntry 8 } 313 ipMRouteDifferentInIfPackets OBJECT-TYPE 314 SYNTAX Counter32 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The number of packets which this router has received from 319 these sources and addressed to this multicast group address, 320 which were not received from the interface indicated by 321 ipMRouteInIfIndex." 322 ::= { ipMRouteEntry 9 } 324 ipMRouteOctets OBJECT-TYPE 325 SYNTAX Counter32 326 MAX-ACCESS read-only 327 STATUS current 328 DESCRIPTION 329 "The number of octets contained in IP datagrams which were 330 received from these sources and addressed to this multicast 331 group address, and which were forwarded by this router." 332 ::= { ipMRouteEntry 10 } 334 ipMRouteProtocol OBJECT-TYPE 335 SYNTAX INTEGER { 336 other(1), -- none of the following 337 local(2), -- e.g., manually configured 338 netmgmt(3), -- set via net.mgmt protocol 339 dvmrp(4), 340 mospf(5), 341 pimSparseDense(6), -- PIMv1, both DM and SM 342 cbt(7), 343 pimSparseMode(8), -- PIM-SMv2 344 pimDenseMode(9), -- PIM-DMv2 345 igmpOnly(10) 346 } 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "The routing mechanism via which this route was learned." 351 ::= { ipMRouteEntry 11 } 353 Draft IP Multicast Routing MIB March 1997 355 -- 356 -- The IP Multicast Routing Next Hop Table 357 -- 359 ipMRouteNextHopTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "The (conceptual) table containing information on the next 365 hops on outgoing interfaces for routing IP multicast 366 datagrams. Each entry is one of a list of next hops on 367 outgoing interfaces for particular sources sending to a 368 particular multicast group address." 369 ::= { ipMRoute 3 } 371 ipMRouteNextHopEntry OBJECT-TYPE 372 SYNTAX IpMRouteNextHopEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "An entry (conceptual row) in the list of next hops on 377 outgoing interfaces to which IP multicast datagrams from 378 particular sources to a IP multicast group address are 379 routed." 380 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 381 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 382 ipMRouteNextHopAddress } 383 ::= { ipMRouteNextHopTable 1 } 385 Draft IP Multicast Routing MIB March 1997 387 IpMRouteNextHopEntry ::= SEQUENCE { 388 ipMRouteNextHopGroup IpAddress, 389 ipMRouteNextHopSource IpAddress, 390 ipMRouteNextHopSourceMask IpAddress, 391 ipMRouteNextHopIfIndex Integer32, 392 ipMRouteNextHopAddress IpAddress, 393 ipMRouteNextHopState INTEGER, 394 ipMRouteNextHopUpTime TimeTicks, 395 ipMRouteNextHopExpiryTime TimeTicks, 396 ipMRouteNextHopClosestMemberHops Integer32, 397 ipMRouteNextHopProtocol INTEGER, 398 ipMRouteNextHopPkts Counter32 399 } 401 ipMRouteNextHopGroup OBJECT-TYPE 402 SYNTAX IpAddress 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "The IP multicast group for which this entry specifies a 407 next hop on an outgoing interface." 408 ::= { ipMRouteNextHopEntry 1 } 410 ipMRouteNextHopSource OBJECT-TYPE 411 SYNTAX IpAddress 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "The network address which when combined with the 416 corresponding value of ipMRouteNextHopSourceMask identifies 417 the sources for which this entry specifies a next hop on an 418 outgoing interface." 419 ::= { ipMRouteNextHopEntry 2 } 421 ipMRouteNextHopSourceMask OBJECT-TYPE 422 SYNTAX IpAddress 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "The network mask which when combined with the corresponding 427 value of ipMRouteNextHopSource identifies the sources for 428 which this entry specifies a next hop on an outgoing 429 interface." 430 ::= { ipMRouteNextHopEntry 3 } 432 Draft IP Multicast Routing MIB March 1997 434 ipMRouteNextHopIfIndex OBJECT-TYPE 435 SYNTAX Integer32 436 MAX-ACCESS not-accessible 437 STATUS current 438 DESCRIPTION 439 "The ifIndex value of the interface for the outgoing 440 interface for this next hop." 441 ::= { ipMRouteNextHopEntry 4 } 443 ipMRouteNextHopAddress OBJECT-TYPE 444 SYNTAX IpAddress 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "The address of the next hop." 449 ::= { ipMRouteNextHopEntry 5 } 451 ipMRouteNextHopState OBJECT-TYPE 452 SYNTAX INTEGER { pruned(1), forwarding(2) } 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "An indication of whether the outgoing interface and next 457 hop represented by this entry is currently being used to 458 forward IP datagrams. The value 'forwarding' indicates it 459 is currently being used; the value 'pruned' indicates it is 460 not." 461 ::= { ipMRouteNextHopEntry 6 } 463 ipMRouteNextHopUpTime OBJECT-TYPE 464 SYNTAX TimeTicks 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The time since the multicast routing information 469 represented by this entry was learned by the router." 470 ::= { ipMRouteNextHopEntry 7 } 472 ipMRouteNextHopExpiryTime OBJECT-TYPE 473 SYNTAX TimeTicks 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The minimum amount of time remaining before this entry will 478 be aged out. The value 0 indicates that the entry is not 480 Draft IP Multicast Routing MIB March 1997 482 subject to aging." 483 ::= { ipMRouteNextHopEntry 8 } 485 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 486 SYNTAX Integer32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The minimum number of hops between this router and any 491 member of this IP multicast group reached via this next hop 492 on this outgoing interface. Any IP multicast datagrams for 493 the group which have a TTL less than this number of hops 494 will not be forwarded to this next hop." 495 ::= { ipMRouteNextHopEntry 9 } 497 ipMRouteNextHopProtocol OBJECT-TYPE 498 SYNTAX INTEGER { 499 other(1), -- none of the following 500 local(2), -- e.g., manually configured 501 netmgmt(3), -- set via net.mgmt protocol 502 dvmrp(4), 503 mospf(5), 504 pimSparseDense(6), -- PIMv1, both DM and SM 505 cbt(7), 506 pimSparseMode(8), -- PIM-SMv2 507 pimDenseMode(9), -- PIM-DMv2 508 igmpOnly(10) 509 } 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "The routing mechanism via which this route was learned." 514 ::= { ipMRouteNextHopEntry 10 } 516 ipMRouteNextHopPkts OBJECT-TYPE 517 SYNTAX Counter32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The number of packets which have been forwarded using this 522 route." 523 ::= { ipMRouteNextHopEntry 11 } 525 Draft IP Multicast Routing MIB March 1997 527 -- 528 -- The Multicast Routing Interface Table 529 -- 531 ipMRouteInterfaceTable OBJECT-TYPE 532 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 533 MAX-ACCESS not-accessible 534 STATUS current 535 DESCRIPTION 536 "The (conceptual) table containg multicast routing 537 information specific to interfaces." 538 ::= { ipMRoute 4 } 540 ipMRouteInterfaceEntry OBJECT-TYPE 541 SYNTAX IpMRouteInterfaceEntry 542 MAX-ACCESS not-accessible 543 STATUS current 544 DESCRIPTION 545 "An entry (conceptual row) containing the multicast routing 546 information for a particular interface." 547 INDEX { ipMRouteInterfaceIfIndex } 548 ::= { ipMRouteInterfaceTable 1 } 550 IpMRouteInterfaceEntry ::= SEQUENCE { 551 ipMRouteInterfaceIfIndex Integer32, 552 ipMRouteInterfaceTtl Integer32, 553 ipMRouteInterfaceProtocol INTEGER 554 } 556 ipMRouteInterfaceIfIndex OBJECT-TYPE 557 SYNTAX Integer32 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "The ifIndex value of the interface for which this entry 562 contains information." 563 ::= { ipMRouteInterfaceEntry 1 } 565 ipMRouteInterfaceTtl OBJECT-TYPE 566 SYNTAX Integer32 567 MAX-ACCESS read-write 568 STATUS current 569 DESCRIPTION 570 "The datagram TTL threshold for the interface. Any IP 571 multicast datagrams with a TTL less than this threshold will 573 Draft IP Multicast Routing MIB March 1997 575 not be forwarded out the interface. The default value of 0 576 means all multicast packets are forwarded out the 577 interface." 578 ::= { ipMRouteInterfaceEntry 2 } 580 ipMRouteInterfaceProtocol OBJECT-TYPE 581 SYNTAX INTEGER { 582 other(1), -- none of the following 583 local(2), -- e.g., static routing 584 netmgmt(3), -- set via net.mgmt protocol 585 dvmrp(4), 586 mospf(5), 587 pimSparseDense(6), -- PIMv1, both DM and SM 588 cbt(7), 589 pimSparseMode(8), -- PIM-SMv2 590 pimDenseMode(9), -- PIM-DMv2 591 igmpOnly(10) 592 } 593 MAX-ACCESS read-write 594 STATUS current 595 DESCRIPTION 596 "The routing protocol running on this interface." 597 ::= { ipMRouteInterfaceEntry 3 } 599 -- 600 -- The IP Multicast Scoped Boundary Table 601 -- 603 ipMRouteBoundaryTable OBJECT-TYPE 604 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "The (conceptual) table listing the router's scoped 609 multicast address boundaries." 610 ::= { ipMRoute 5 } 612 ipMRouteBoundaryEntry OBJECT-TYPE 613 SYNTAX IpMRouteBoundaryEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "An entry (conceptual row) in the 618 ipMRouteBoundaryTable representing a scoped 620 Draft IP Multicast Routing MIB March 1997 622 boundary." 623 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 624 ipMRouteBoundaryAddressMask } 625 ::= { ipMRouteBoundaryTable 1 } 627 IpMRouteBoundaryEntry ::= SEQUENCE { 628 ipMRouteBoundaryIfIndex Integer32, 629 ipMRouteBoundaryAddress IpAddress, 630 ipMRouteBoundaryAddressMask IpAddress, 631 ipMRouteBoundaryStatus RowStatus 632 } 634 ipMRouteBoundaryIfIndex OBJECT-TYPE 635 SYNTAX Integer32 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "The IfIndex value for the interface to which 640 this boundary applies. Packets with a 641 destination address in the associated 642 address/mask range will not be forwarded out this 643 interface." 644 ::= { ipMRouteBoundaryEntry 1 } 646 ipMRouteBoundaryAddress OBJECT-TYPE 647 SYNTAX IpAddress 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "The group address which when combined with the 652 corresponding value of ipMRouteBoundaryAddressMask 653 identifies the group range for which the scoped 654 boundary exists. Scoped addresses must come from 655 the range 239.x.x.x." 656 ::= { ipMRouteBoundaryEntry 2 } 658 ipMRouteBoundaryAddressMask OBJECT-TYPE 659 SYNTAX IpAddress 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "The group address mask which when combined with 664 the corresponding value of ipMRouteBoundaryAddress 665 identifies the group range for which the scoped 666 boundary exists." 668 Draft IP Multicast Routing MIB March 1997 670 ::= { ipMRouteBoundaryEntry 3 } 672 ipMRouteBoundaryStatus OBJECT-TYPE 673 SYNTAX RowStatus 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "The status of this row, by which new entries may be 678 created, or old entries deleted from this table." 679 ::= { ipMRouteBoundaryEntry 4 } 681 Draft IP Multicast Routing MIB March 1997 683 -- conformance information 685 ipMRouteMIBConformance 686 OBJECT IDENTIFIER ::= { ipMRouteMIB 2 } 687 ipMRouteMIBCompliances 688 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 689 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 691 -- compliance statements 693 ipMRouteMIBCompliance MODULE-COMPLIANCE 694 STATUS current 695 DESCRIPTION 696 "The compliance statement for the IP Multicast MIB." 697 MODULE -- this module 698 MANDATORY-GROUPS { ipMRouteMIBBasicGroup } 700 GROUP ipMRouteMIBBoundaryGroup 701 DESCRIPTION 702 "This group is only required to support management of 703 scoped multicast address boundaries." 705 OBJECT ipMRouteBoundaryStatus 706 MIN-ACCESS read-only 707 DESCRIPTION 708 "Write access is not required." 710 ::= { ipMRouteMIBCompliances 1 } 712 -- units of conformance 714 ipMRouteMIBBasicGroup OBJECT-GROUP 715 OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor, 716 ipMRouteInIfIndex, 717 ipMRouteUpTime, ipMRouteExpiryTime, 718 ipMRoutePkts, ipMRouteDifferentInIfPackets, 719 ipMRouteOctets, 720 ipMRouteNextHopState, 721 ipMRouteNextHopUpTime, 722 ipMRouteNextHopExpiryTime, 723 ipMRouteNextHopProtocol, 724 ipMRouteNextHopPkts, 725 ipMRouteInterfaceTtl, 727 Draft IP Multicast Routing MIB March 1997 729 ipMRouteInterfaceProtocol, 730 ipMRouteProtocol 731 } 732 STATUS current 733 DESCRIPTION 734 "A collection of objects to support basic management of 735 IP Multicast routing." 736 ::= { ipMRouteMIBGroups 1 } 738 ipMRouteMIBHopCountGroup OBJECT-GROUP 739 OBJECTS { ipMRouteNextHopClosestMemberHops } 740 STATUS current 741 DESCRIPTION 742 "A collection of objects to support management of the use 743 of hop counts in IP Multicast routing." 744 ::= { ipMRouteMIBGroups 2 } 746 ipMRouteMIBBoundaryGroup OBJECT-GROUP 747 OBJECTS { ipMRouteBoundaryStatus } 748 STATUS current 749 DESCRIPTION 750 "A collection of objects to support management of scoped 751 multicast address boundaries." 752 ::= { ipMRouteMIBGroups 3 } 754 ipMRouteMIBPktsOutGroup OBJECT-GROUP 755 OBJECTS { ipMRouteNextHopPkts } 756 STATUS current 757 DESCRIPTION 758 "A collection of objects to support management of packet 759 counters for each outgoing interface entry of a route." 760 ::= { ipMRouteMIBGroups 4 } 762 END 763 Draft IP Multicast Routing MIB March 1997 765 6. Acknowledgements 767 This MIB module was updated based on feedback from the IETF's Inter- 768 Domain Multicast Routing (IDMR) Working Group. 770 7. References 772 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 773 S. Waldbusser, "Structure of Management Information for version 2 774 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 775 January 1996. 777 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 778 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 779 RFC 1213, March 1991. 781 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 782 Management Protocol", RFC 1157, May 1990. 784 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 785 S. Waldbusser, "Protocol Operations for version 2 of the Simple 786 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 788 [5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 789 thesis, Electrical Engineering Dept., Stanford University, December 790 1991. 792 [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 793 Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman, 794 Stanford University, November 1988. 796 [7] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 797 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 798 "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol 799 Specification", November 1996. 801 [8] Estrin, D., Farinacci, D., Jacobson, V., Liu, C., Wei, L., Sharma, 802 P., and A. Helmy, "Protocol Independent Multicast - Dense Mode 803 (PIM-DM): Protocol Specification", January 1996. 805 [9] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March 806 1994. 808 Draft IP Multicast Routing MIB March 1997 810 [10] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural 811 Overview and Specification", University College London, November 812 1994. 814 8. Security Considerations 816 Security issues are not discussed in this memo. 818 9. Authors' Address 820 Keith McCloghrie 821 cisco Systems, Inc. 822 170 West Tasman Drive 823 San Jose, CA 95134-1706 824 Phone: +1 408 526 5260 825 EMail: kzm@cisco.com 827 Dino Farinacci 828 cisco Systems, Inc. 829 170 West Tasman Drive 830 San Jose, CA 95134-1706 831 Phone: +1 408 526 4696 832 EMail: dino@cisco.com 834 Dave Thaler 835 Department of Electrical Engineering and Computer Science 836 University of Michigan 837 1301 Beal Ave. 838 Ann Arbor, MI 48109-2122 839 Phone: +1 313 763 5243 840 EMail: thalerd@eecs.umich.edu 842 Draft IP Multicast Routing MIB March 1997 844 Table of Contents 846 1 Introduction .................................................... 1 847 2 Revision History ................................................ 2 848 3 The SNMP Network Management Framework ........................... 4 849 3.1 Object Definitions ............................................ 4 850 4 Overview ........................................................ 5 851 5 Definitions ..................................................... 6 852 6 Acknowledgements ................................................ 21 853 7 References ...................................................... 21 854 8 Security Considerations ......................................... 22 855 9 Authors' Address ................................................ 22