idnits 2.17.1 draft-ietf-idmr-multicast-routmib-03.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-19) 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 (9 June 1996) is 10176 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' ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '8') -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 15 errors (**), 0 flaws (~~), 1 warning (==), 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 December 1996 cisco Systems 4 Dave Thaler 5 University of Michigan 6 9 June 1996 8 IP Multicast Routing MIB 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are valid for a maximum of six months and may be 19 updated, replaced, or obsoleted by other documents at any time. It is 20 inappropriate to use Internet Drafts as reference material or to cite 21 them other than as a "work in progress". 23 1. Introduction 25 This memo defines an experimental portion of the Management Information 26 Base (MIB) for use with network management protocols in the Internet 27 community. In particular, it describes managed objects used for 28 managing IP Multicast Routing [5], independent of the specific multicast 29 routing protocol [6,7,8,9] in use. Managed objects specific to 30 particular multicast routing protocols are specified elsewhere. 32 Draft IP Multicast Routing MIB June 1996 34 2. Revision History 36 A record of changes which will be removed before publication. 38 9 June 40 (1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts. 42 (2) updated references, etc. 44 28 March 46 (1) renamed ipMRouteNextHopClosestMember to 47 ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes 48 to ipMRouteDifferentInIfPacket. 50 26 February 52 (1) added ipMRouteNextHopAddress as a INDEX variable for the 53 ipMRouteNextHopTable. 55 (2) added ipMRouteNextHopClosestMember and ipMRouteNextHopProtocol 57 (3) added ipMRouteMIBHopCountGroup. 59 (4) specified that an expiry-time of zero means that an entry is not 60 subject to aging. 62 (5) added references for MOSPF and CBT. 64 4 February 66 (1) removed ipMRouteOutList 68 (2) Modified ipMRouteNextHopTable to be INDEX-ed by 69 ipMRouteNextHopGroup, ipMRouteNextHopSource, 70 ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex. 72 (3) added ipMRouteProtocol 74 (4) replaced "RPF" terminology with "Upstream neighbor". 76 15 July - initial version. 78 Draft IP Multicast Routing MIB June 1996 80 3. The SNMP Network Management Framework 82 The SNMP Network Management Framework presently consists of three major 83 components. They are: 85 o RFC 1902 [1] which defines the SMI, the mechanisms used for 86 describing and naming objects for the purpose of management. 88 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 89 objects for the Internet suite of protocols. 91 o RFC 1157 [3] and RFC 1905 [4] which define two versions of the 92 protocol used for network access to managed objects. 94 The Framework permits new objects to be defined for the purpose of 95 experimentation and evaluation. 97 3.1. Object Definitions 99 Managed objects are accessed via a virtual information store, termed the 100 Management Information Base or MIB. Objects in the MIB are defined 101 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 102 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 103 an administratively assigned name. The object type together with an 104 object instance serves to uniquely identify a specific instantiation of 105 the object. For human convenience, we often use a textual string, 106 termed the descriptor, to refer to the object type. 108 Draft IP Multicast Routing MIB June 1996 110 4. Overview 112 This MIB module contains one scalar and four tables. The tables are: 114 (1) the IP Multicast Route Table containing multicast routing 115 information for IP datagrams sent by particular sources to the IP 116 multicast groups known to a router; 118 (2) the IP Multicast Routing Next Hop Table containing information on 119 the next hops for the routing IP multicast datagrams. Each entry 120 is one of a list of next hops on outgoing interfaces for particular 121 sources sending to a particular multicast group address." 123 (3) the IP Multicast Routing Interface Table containing multicast 124 routing information specific to interfaces. 126 (4) the IP Multicast Scoped Boundary Table containing the scoped 127 multicast address boundaries. 129 Draft IP Multicast Routing MIB June 1996 131 5. Definitions 133 IPMROUTE-MIB DEFINITIONS ::= BEGIN 135 IMPORTS 136 MODULE-IDENTITY, OBJECT-TYPE, experimental, 137 Integer32, Counter32, 138 IpAddress, TimeTicks FROM SNMPv2-SMI 139 RowStatus FROM SNMPv2-TC 140 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 142 ipMRouteMIB MODULE-IDENTITY 143 LAST-UPDATED "9604282359Z" 144 ORGANIZATION "IETF IDMR Working Group." 145 CONTACT-INFO 146 " Keith McCloghrie 147 Cisco Systems, Inc. 148 170 West Tasman Drive 149 San Jose, CA 95134-1706 150 US 152 Phone: +1 408 526 5260 153 EMail: kzm@cisco.com" 154 DESCRIPTION 155 "The MIB module for management of IP Multicast routing, but 156 independent of the specific multicast routing protocol in 157 use." 158 ::= { experimental 60 } 160 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 } 162 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 163 Draft IP Multicast Routing MIB June 1996 165 -- the IP Multicast Routing MIB-Group 166 -- 167 -- a collection of objects providing information about 168 -- IP Multicast Groups 170 ipMRouteEnable OBJECT-TYPE 171 SYNTAX INTEGER { enabled(1), disabled(2) } 172 MAX-ACCESS read-write 173 STATUS current 174 DESCRIPTION 175 "The enabled status of IP Multicast routing on this router." 176 ::= { ipMRoute 1 } 178 ipMRouteTable OBJECT-TYPE 179 SYNTAX SEQUENCE OF IpMRouteEntry 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "The (conceptual) table containing multicast routing 184 information for IP datagrams sent by particular sources to 185 the IP multicast groups known to this router." 186 ::= { ipMRoute 2 } 188 ipMRouteEntry OBJECT-TYPE 189 SYNTAX IpMRouteEntry 190 MAX-ACCESS not-accessible 191 STATUS current 192 DESCRIPTION 193 "An entry (conceptual row) containing the multicast routing 194 information for IP datagrams from a particular source and 195 addressed to a particular IP multicast group address." 196 INDEX { ipMRouteGroup, 197 ipMRouteSource, 198 ipMRouteSourceMask } 199 ::= { ipMRouteTable 1 } 201 Draft IP Multicast Routing MIB June 1996 203 IpMRouteEntry ::= SEQUENCE { 204 ipMRouteGroup IpAddress, 205 ipMRouteSource IpAddress, 206 ipMRouteSourceMask IpAddress, 207 ipMRouteUpstreamNeighbor IpAddress, 208 ipMRouteInIfIndex Integer32, 209 ipMRouteUpTime TimeTicks, 210 ipMRouteExpiryTime TimeTicks, 211 ipMRoutePkts Counter32, 212 ipMRouteDifferentInIfPackets Counter32, 213 ipMRouteOctets Counter32, 214 ipMRouteProtocol INTEGER 215 } 217 ipMRouteGroup OBJECT-TYPE 218 SYNTAX IpAddress 219 MAX-ACCESS not-accessible 220 STATUS current 221 DESCRIPTION 222 "The IP multicast group address for which this entry 223 contains multicast routing information." 224 ::= { ipMRouteEntry 1 } 226 ipMRouteSource OBJECT-TYPE 227 SYNTAX IpAddress 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION 231 "The network address which when combined with the 232 corresponding value of ipMRouteSourceMask identifies the 233 sources for which this entry contains multicast routing 234 information." 235 ::= { ipMRouteEntry 2 } 237 ipMRouteSourceMask OBJECT-TYPE 238 SYNTAX IpAddress 239 MAX-ACCESS not-accessible 240 STATUS current 241 DESCRIPTION 242 "The network mask which when combined with the corresponding 243 value of ipMRouteSource identifies the sources for which 244 this entry contains multicast routing information." 245 ::= { ipMRouteEntry 3 } 247 ipMRouteUpstreamNeighbor OBJECT-TYPE 248 Draft IP Multicast Routing MIB June 1996 250 SYNTAX IpAddress 251 MAX-ACCESS read-only 252 STATUS current 253 DESCRIPTION 254 "The address of the upstream neighbor (e.g., RPF neighbor) 255 from which IP datagrams from these sources to this multicast 256 address are received." 257 ::= { ipMRouteEntry 4 } 259 ipMRouteInIfIndex OBJECT-TYPE 260 SYNTAX Integer32 261 MAX-ACCESS read-only 262 STATUS current 263 DESCRIPTION 264 "The value of ifIndex for the interface on which IP 265 datagrams sent by these sources to this multicast address 266 are received." 267 ::= { ipMRouteEntry 5 } 269 ipMRouteUpTime OBJECT-TYPE 270 SYNTAX TimeTicks 271 MAX-ACCESS read-only 272 STATUS current 273 DESCRIPTION 274 "The time since the multicast routing information 275 represented by this entry was learned by the router." 276 ::= { ipMRouteEntry 6 } 278 ipMRouteExpiryTime OBJECT-TYPE 279 SYNTAX TimeTicks 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "The minimum amount of time remaining before this entry will 284 be aged out. The value 0 indicates that the entry is not 285 subject to aging." 286 ::= { ipMRouteEntry 7 } 288 ipMRoutePkts OBJECT-TYPE 289 SYNTAX Counter32 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The number of packets which this router has received from 294 these sources and addressed to this multicast group 296 Draft IP Multicast Routing MIB June 1996 298 address." 299 ::= { ipMRouteEntry 8 } 301 ipMRouteDifferentInIfPackets OBJECT-TYPE 302 SYNTAX Counter32 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "The number of packets which this router has received from 307 these sources and addressed to this multicast group address, 308 which were not received from the interface indicated by 309 ipMRouteInIfIndex." 310 ::= { ipMRouteEntry 9 } 312 ipMRouteOctets OBJECT-TYPE 313 SYNTAX Counter32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The number of octets contained in IP datagrams which were 318 received from these sources and addressed to this multicast 319 group address, and which were forwarded by this router." 320 ::= { ipMRouteEntry 10 } 322 ipMRouteProtocol OBJECT-TYPE 323 SYNTAX INTEGER { 324 other(1), -- none of the following 325 local(2), -- e.g., manually configured 326 netmgmt(3), -- set via net.mgmt protocol 327 dvmrp(4), 328 mospf(5), 329 pim(6), 330 cbt(7) 331 } 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The routing mechanism via which this route was learned." 336 ::= { ipMRouteEntry 11 } 338 Draft IP Multicast Routing MIB June 1996 340 -- 341 -- The IP Multicast Routing Next Hop Table 342 -- 344 ipMRouteNextHopTable OBJECT-TYPE 345 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 346 MAX-ACCESS not-accessible 347 STATUS current 348 DESCRIPTION 349 "The (conceptual) table containing information on the next 350 hops on outgoing interfaces for routing IP multicast 351 datagrams. Each entry is one of a list of next hops on 352 outgoing interfaces for particular sources sending to a 353 particular multicast group address." 354 ::= { ipMRoute 3 } 356 ipMRouteNextHopEntry OBJECT-TYPE 357 SYNTAX IpMRouteNextHopEntry 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "An entry (conceptual row) in the list of next hops on 362 outgoing interfaces to which IP multicast datagrams from 363 particular sources to a IP multicast group address are 364 routed." 365 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 366 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 367 ipMRouteNextHopAddress } 368 ::= { ipMRouteNextHopTable 1 } 370 Draft IP Multicast Routing MIB June 1996 372 IpMRouteNextHopEntry ::= SEQUENCE { 373 ipMRouteNextHopGroup IpAddress, 374 ipMRouteNextHopSource IpAddress, 375 ipMRouteNextHopSourceMask IpAddress, 376 ipMRouteNextHopIfIndex Integer32, 377 ipMRouteNextHopAddress IpAddress, 378 ipMRouteNextHopState INTEGER, 379 ipMRouteNextHopUpTime TimeTicks, 380 ipMRouteNextHopExpiryTime TimeTicks, 381 ipMRouteNextHopClosestMemberHops Integer32, 382 ipMRouteNextHopProtocol INTEGER, 383 ipMRouteNextHopPkts Counter32 384 } 386 ipMRouteNextHopGroup OBJECT-TYPE 387 SYNTAX IpAddress 388 MAX-ACCESS not-accessible 389 STATUS current 390 DESCRIPTION 391 "The IP multicast group for which this entry specifies a 392 next hop on an outgoing interface." 393 ::= { ipMRouteNextHopEntry 1 } 395 ipMRouteNextHopSource OBJECT-TYPE 396 SYNTAX IpAddress 397 MAX-ACCESS not-accessible 398 STATUS current 399 DESCRIPTION 400 "The network address which when combined with the 401 corresponding value of ipMRouteNextHopSourceMask identifies 402 the sources for which this entry specifies a next hop on an 403 outgoing interface." 404 ::= { ipMRouteNextHopEntry 2 } 406 ipMRouteNextHopSourceMask OBJECT-TYPE 407 SYNTAX IpAddress 408 MAX-ACCESS not-accessible 409 STATUS current 410 DESCRIPTION 411 "The network mask which when combined with the corresponding 412 value of ipMRouteNextHopSource identifies the sources for 413 which this entry specifies a next hop on an outgoing 414 interface." 415 ::= { ipMRouteNextHopEntry 3 } 417 Draft IP Multicast Routing MIB June 1996 419 ipMRouteNextHopIfIndex OBJECT-TYPE 420 SYNTAX Integer32 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION 424 "The ifIndex value of the interface for the outgoing 425 interface for this next hop." 426 ::= { ipMRouteNextHopEntry 4 } 428 ipMRouteNextHopAddress OBJECT-TYPE 429 SYNTAX IpAddress 430 MAX-ACCESS not-accessible 431 STATUS current 432 DESCRIPTION 433 "The address of the next hop." 434 ::= { ipMRouteNextHopEntry 5 } 436 ipMRouteNextHopState OBJECT-TYPE 437 SYNTAX INTEGER { pruned(1), forwarding(2) } 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "An indication of whether the outgoing interface and next 442 hop represented by this entry is currently being used to 443 forward IP datagrams. The value 'forwarding' indicates it 444 is currently being used; the value 'pruned' indicates it is 445 not." 446 ::= { ipMRouteNextHopEntry 6 } 448 ipMRouteNextHopUpTime OBJECT-TYPE 449 SYNTAX TimeTicks 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "The time since the multicast routing information 454 represented by this entry was learned by the router." 455 ::= { ipMRouteNextHopEntry 7 } 457 ipMRouteNextHopExpiryTime OBJECT-TYPE 458 SYNTAX TimeTicks 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The minimum amount of time remaining before this entry will 463 be aged out. The value 0 indicates that the entry is not 465 Draft IP Multicast Routing MIB June 1996 467 subject to aging." 468 ::= { ipMRouteNextHopEntry 8 } 470 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 471 SYNTAX Integer32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The minimum number of hops between this router and any 476 member of this IP multicast group reached via this next hop 477 on this outgoing interface. Any IP multicast datagrams for 478 the group which have a TTL less than this number of hops 479 will not be forwarded to this next hop." 480 ::= { ipMRouteNextHopEntry 9 } 482 ipMRouteNextHopProtocol OBJECT-TYPE 483 SYNTAX INTEGER { 484 other(1), -- none of the following 485 local(2), -- e.g., manually configured 486 netmgmt(3), -- set via net.mgmt protocol 487 dvmrp(4), 488 mospf(5), 489 pim(6), 490 cbt(7) 491 } 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The routing mechanism via which this route was learned." 496 ::= { ipMRouteNextHopEntry 10 } 498 ipMRouteNextHopPkts OBJECT-TYPE 499 SYNTAX Counter32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The number of packets which have been forwarded using this 504 route." 505 ::= { ipMRouteNextHopEntry 11 } 507 Draft IP Multicast Routing MIB June 1996 509 -- 510 -- The Multicast Routing Interface Table 511 -- 513 ipMRouteInterfaceTable OBJECT-TYPE 514 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "The (conceptual) table containg multicast routing 519 information specific to interfaces." 520 ::= { ipMRoute 4 } 522 ipMRouteInterfaceEntry OBJECT-TYPE 523 SYNTAX IpMRouteInterfaceEntry 524 MAX-ACCESS not-accessible 525 STATUS current 526 DESCRIPTION 527 "An entry (conceptual row) containing the multicast routing 528 information for a particular interface." 529 INDEX { ipMRouteInterfaceIfIndex } 530 ::= { ipMRouteInterfaceTable 1 } 532 IpMRouteInterfaceEntry ::= SEQUENCE { 533 ipMRouteInterfaceIfIndex Integer32, 534 ipMRouteInterfaceTtl Integer32 535 } 537 ipMRouteInterfaceIfIndex OBJECT-TYPE 538 SYNTAX Integer32 539 MAX-ACCESS not-accessible 540 STATUS current 541 DESCRIPTION 542 "The ifIndex value of the interface for which this entry 543 contains information." 544 ::= { ipMRouteInterfaceEntry 1 } 546 ipMRouteInterfaceTtl OBJECT-TYPE 547 SYNTAX Integer32 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "The datagram TTL threshold for the interface. Any IP 552 multicast datagrams with a TTL less than this threshold will 553 not be forwarded out the interface. The default value of 0 555 Draft IP Multicast Routing MIB June 1996 557 means all multicast packets are forwarded out interface." 558 ::= { ipMRouteInterfaceEntry 2 } 560 -- 561 -- The IP Multicast Scoped Boundary Table 562 -- 564 ipMRouteBoundaryTable OBJECT-TYPE 565 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "The (conceptual) table listing the router's scoped 570 multicast address boundaries." 571 ::= { ipMRoute 5 } 573 ipMRouteBoundaryEntry OBJECT-TYPE 574 SYNTAX IpMRouteBoundaryEntry 575 MAX-ACCESS not-accessible 576 STATUS current 577 DESCRIPTION 578 "An entry (conceptual row) in the 579 ipMRouteBoundaryTable representing a scoped 580 boundary." 581 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 582 ipMRouteBoundaryAddressMask } 583 ::= { ipMRouteBoundaryTable 1 } 585 IpMRouteBoundaryEntry ::= SEQUENCE { 586 ipMRouteBoundaryIfIndex Integer32, 587 ipMRouteBoundaryAddress IpAddress, 588 ipMRouteBoundaryAddressMask IpAddress, 589 ipMRouteBoundaryStatus RowStatus 590 } 592 ipMRouteBoundaryIfIndex OBJECT-TYPE 593 SYNTAX Integer32 594 MAX-ACCESS not-accessible 595 STATUS current 596 DESCRIPTION 597 "The IfIndex value for the interface to which 598 this boundary applies. Packets with a 599 destination address in the associated 601 Draft IP Multicast Routing MIB June 1996 603 address/mask range will not be forwarded out this 604 interface." 605 ::= { ipMRouteBoundaryEntry 1 } 607 ipMRouteBoundaryAddress OBJECT-TYPE 608 SYNTAX IpAddress 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "The group address which when combined with the 613 corresponding value of ipMRouteBoundaryAddressMask 614 identifies the group range for which the scoped 615 boundary exists. Scoped addresses must come from 616 the range 239.x.x.x." 617 ::= { ipMRouteBoundaryEntry 2 } 619 ipMRouteBoundaryAddressMask OBJECT-TYPE 620 SYNTAX IpAddress 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "The group address mask which when combined with 625 the corresponding value of ipMRouteBoundaryAddress 626 identifies the group range for which the scoped 627 boundary exists." 628 ::= { ipMRouteBoundaryEntry 3 } 630 ipMRouteBoundaryStatus OBJECT-TYPE 631 SYNTAX RowStatus 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "The status of this row, by which new entries may be 636 created, or old entries deleted from this table." 637 ::= { ipMRouteBoundaryEntry 4 } 639 Draft IP Multicast Routing MIB June 1996 641 -- conformance information 643 ipMRouteMIBConformance 644 OBJECT IDENTIFIER ::= { ipMRouteMIB 2 } 645 ipMRouteMIBCompliances 646 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 647 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 649 -- compliance statements 651 ipMRouteMIBCompliance MODULE-COMPLIANCE 652 STATUS current 653 DESCRIPTION 654 "The compliance statement for the IP Multicast MIB." 655 MODULE -- this module 656 MANDATORY-GROUPS { ipMRouteMIBBasicGroup } 658 GROUP ipMRouteMIBBoundaryGroup 659 DESCRIPTION 660 "This group is only required to support management of 661 scoped multicast address boundaries." 663 OBJECT ipMRouteBoundaryStatus 664 MIN-ACCESS read-only 665 DESCRIPTION 666 "Write access is not required." 668 ::= { ipMRouteMIBCompliances 1 } 670 -- units of conformance 672 ipMRouteMIBBasicGroup OBJECT-GROUP 673 OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor, 674 ipMRouteInIfIndex, 675 ipMRouteUpTime, ipMRouteExpiryTime, 676 ipMRoutePkts, ipMRouteDifferentInIfPackets, 677 ipMRouteOctets, 678 ipMRouteNextHopState, 679 ipMRouteNextHopUpTime, 680 ipMRouteNextHopExpiryTime, 681 ipMRouteNextHopProtocol, 682 ipMRouteNextHopPkts, 683 ipMRouteInterfaceTtl, 685 Draft IP Multicast Routing MIB June 1996 687 ipMRouteProtocol 688 } 689 STATUS current 690 DESCRIPTION 691 "A collection of objects to support basic management of 692 IP Multicast routing." 693 ::= { ipMRouteMIBGroups 1 } 695 ipMRouteMIBHopCountGroup OBJECT-GROUP 696 OBJECTS { ipMRouteNextHopClosestMemberHops } 697 STATUS current 698 DESCRIPTION 699 "A collection of objects to support management of the use 700 of hop counts in IP Multicast routing." 701 ::= { ipMRouteMIBGroups 2 } 703 ipMRouteMIBBoundaryGroup OBJECT-GROUP 704 OBJECTS { ipMRouteBoundaryStatus } 705 STATUS current 706 DESCRIPTION 707 "A collection of objects to support management of scoped 708 multicast address boundaries." 709 ::= { ipMRouteMIBGroups 3 } 711 END 713 Draft IP Multicast Routing MIB June 1996 715 6. Acknowledgements 717 This MIB module was updated based on feedback from the IETF's Inter- 718 Domain Multicast Routing (IDMR) Working Group. 720 7. References 722 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 723 S. Waldbusser, "Structure of Management Information for version 2 724 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 725 January 1996. 727 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 728 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 729 RFC 1213, March 1991. 731 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 732 Management Protocol", RFC 1157, May 1990. 734 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 735 S. Waldbusser, "Protocol Operations for version 2 of the Simple 736 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 738 [5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 739 thesis, Electrical Engineering Dept., Stanford University, December 740 1991. 742 [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 743 Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman, 744 Stanford University, November 1988. 746 [7] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 747 L. Wei, "Protocol Independent Multicast (PIM): Protocol 748 Specification", Xerox, University of Southern California, Cisco 749 Systems, Lawrence Berkeley Laboratory, January 1995. 751 [8] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March 752 1994. 754 [9] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural 755 Overview and Specification", University College London, November 756 1994. 758 Draft IP Multicast Routing MIB June 1996 760 8. Security Considerations 762 Security issues are not discussed in this memo. 764 9. Authors' Address 766 Keith McCloghrie 767 cisco Systems, Inc. 768 170 West Tasman Drive 769 San Jose, CA 95134-1706 770 Phone: +1 408 526 5260 771 EMail: kzm@cisco.com 773 Dino Farinacci 774 cisco Systems, Inc. 775 170 West Tasman Drive 776 San Jose, CA 95134-1706 777 Phone: +1 408 526 4696 778 EMail: dino@cisco.com 780 Dave Thaler 781 Department of Electrical Engineering and Computer Science 782 University of Michigan 783 1301 Beal Ave. 784 Ann Arbor, MI 48109-2122 785 Phone: +1 313 763 5243 786 EMail: thalerd@eecs.umich.edu 788 Draft IP Multicast Routing MIB June 1996 790 Table of Contents 792 1 Introduction .................................................... 1 793 2 Revision History ................................................ 2 794 3 The SNMP Network Management Framework ........................... 3 795 3.1 Object Definitions ............................................ 3 796 4 Overview ........................................................ 4 797 5 Definitions ..................................................... 5 798 6 Acknowledgements ................................................ 19 799 7 References ...................................................... 19 800 8 Security Considerations ......................................... 20 801 9 Authors' Address ................................................ 20