idnits 2.17.1 draft-ietf-idmr-multicast-routmib-10.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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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 (22 July 1999) is 9045 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 46 == Unused Reference: '17' is defined on line 1169, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1172, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1177, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1181, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1183, 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: 20 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 January 2000 cisco Systems 4 Dave Thaler 5 Microsoft 6 22 July 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 1. Abstract 37 This memo defines an experimental portion of the Management Information 38 Base (MIB) for use with network management protocols in the Internet 39 community. In particular, it describes managed objects used for 40 managing IP Multicast Routing for IPv4, independent of the specific 41 multicast routing protocol in use. 43 2. Introduction 45 This MIB describes objects used for managing IP Multicast Routing [16], 46 independent of the specific multicast routing protocol [17-21] in use. 47 Managed objects specific to particular multicast routing protocols are 48 specified elsewhere. Similarly, this MIB does not support management of 49 multicast routing for other address families, including IPv6. Such 50 management may be supported by other MIBs. 52 3. The SNMP Management Framework 54 The SNMP Management Framework presently consists of five major 55 components: 57 o An overall architecture, described in RFC 2571 [1]. 59 o Mechanisms for describing and naming objects and events for the 60 purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in RFC 62 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 63 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 65 o Message protocols for transferring management information. The 66 first version of the SNMP message protocol is called SNMPv1 and 67 described in RFC 1157 [8]. A second version of the SNMP message 68 protocol, which is not an Internet standards track protocol, is 69 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 70 The third version of the message protocol is called SNMPv3 and 71 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 73 o Protocol operations for accessing management information. The first 74 set of protocol operations and associated PDU formats is described 75 in RFC 1157 [8]. A second set of protocol operations and associated 76 PDU formats is described in RFC 1905 [13]. 78 o A set of fundamental applications described in RFC 2573 [14] and 79 the view-based access control mechanism described in RFC 2575 [15]. 81 Managed objects are accessed via a virtual information store, termed the 82 Management Information Base or MIB. Objects in the MIB are defined 83 using the mechanisms defined in the SMI. 85 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 86 conforming to the SMIv1 can be produced through the appropriate 87 translations. The resulting translated MIB must be semantically 88 equivalent, except where objects or events are omitted because no 89 translation is possible (use of Counter64). Some machine readable 90 information in SMIv2 will be converted into textual descriptions in 91 SMIv1 during the translation process. However, this loss of machine 92 readable information is not considered to change the semantics of the 93 MIB. 95 3.1. Object Definitions 97 Managed objects are accessed via a virtual information store, termed the 98 Management Information Base or MIB. Objects in the MIB are defined 99 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 100 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 101 an administratively assigned name. The object type together with an 102 object instance serves to uniquely identify a specific instantiation of 103 the object. For human convenience, we often use a textual string, 104 termed the descriptor, to refer to the object type. 106 4. Overview 108 This MIB module contains one scalar and five tables. The tables are: 110 (1) the IP Multicast Route Table containing multicast routing 111 information for IP datagrams sent by particular sources to the IP 112 multicast groups known to a router. 114 (2) the IP Multicast Routing Next Hop Table containing information on 115 the next-hops for the routing IP multicast datagrams. Each entry 116 is one of a list of next-hops on outgoing interfaces for particular 117 sources sending to a particular multicast group address. 119 (3) the IP Multicast Routing Interface Table containing multicast 120 routing information specific to interfaces. 122 (4) the IP Multicast Scope Boundary Table containing the boundaries 123 configured for multicast scopes [22]. 125 (5) the IP Multicast Scope Name Table containing human-readable names 126 of multicast scope. 128 5. Definitions 130 IPMROUTE-MIB DEFINITIONS ::= BEGIN 132 IMPORTS 133 -- NOTE TO RFC EDITOR: When this document is published as 134 -- an RFC, change 'experimental' to 'mib-2' in the 135 -- following import, and delete this comment 136 MODULE-IDENTITY, OBJECT-TYPE, experimental, 137 Integer32, Counter32, Counter64, Gauge32, 138 IpAddress, TimeTicks FROM SNMPv2-SMI 139 RowStatus, TEXTUAL-CONVENTION, 140 TruthValue, DisplayString FROM SNMPv2-TC 141 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 142 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 143 InterfaceIndexOrZero, 144 InterfaceIndex FROM IF-MIB; 146 ipMRouteMIB MODULE-IDENTITY 147 LAST-UPDATED "9907221200Z" -- July 22, 1999 148 ORGANIZATION "IETF IDMR Working Group" 149 CONTACT-INFO 150 " Dave Thaler 151 Microsoft Corporation 152 One Microsoft Way 153 Redmond, WA 98052-6399 154 US 156 Phone: +1 425 703 8835 157 EMail: dthaler@dthaler.microsoft.com" 158 DESCRIPTION 159 "The MIB module for management of IP Multicast routing, but 160 independent of the specific multicast routing protocol in 161 use." 162 REVISION "9907221200Z" -- July 22, 1999 163 DESCRIPTION 164 "Initial version, published as RFC xxxx (to be filled in by 165 RFC-Editor)." 166 ::= { experimental 60 } 167 -- NOTE TO RFC EDITOR: When this document is published as 168 -- an RFC, change '{ experimental 60 }' to '{ mib-2 XX }' 169 -- where XX is assigned by IANA, and delete this comment. 171 -- Textual Conventions 172 IpMRouteProtocol ::= TEXTUAL-CONVENTION 173 STATUS current 174 DESCRIPTION 175 "The multicast routing protocol. Inclusion of values for 176 multicast routing protocols is not intended to imply that 177 those protocols need be supported." 178 SYNTAX INTEGER { 179 other(1), -- none of the following 180 local(2), -- e.g., manually configured 181 netmgmt(3), -- set via net.mgmt protocol 182 dvmrp(4), 183 mospf(5), 184 pimSparseDense(6), -- PIMv1, both DM and SM 185 cbt(7), 186 pimSparseMode(8), -- PIM-SM 187 pimDenseMode(9), -- PIM-DM 188 igmpOnly(10), 189 bgmp(11), 190 msdp(12) 191 } 193 -- Top-level structure of the MIB 195 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 } 197 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 198 -- the IP Multicast Routing MIB-Group 199 -- 200 -- a collection of objects providing information about 201 -- IP Multicast Groups 203 ipMRouteEnable OBJECT-TYPE 204 SYNTAX INTEGER { enabled(1), disabled(2) } 205 MAX-ACCESS read-write 206 STATUS current 207 DESCRIPTION 208 "The enabled status of IP Multicast routing on this router." 209 ::= { ipMRoute 1 } 211 ipMRouteEntryCount OBJECT-TYPE 212 SYNTAX Gauge32 213 MAX-ACCESS read-only 214 STATUS current 215 DESCRIPTION 216 "The number of rows in the ipMRouteTable. This can be used 217 to monitor the multicast routing table size." 218 ::= { ipMRoute 7 } 220 ipMRouteTable OBJECT-TYPE 221 SYNTAX SEQUENCE OF IpMRouteEntry 222 MAX-ACCESS not-accessible 223 STATUS current 224 DESCRIPTION 225 "The (conceptual) table containing multicast routing 226 information for IP datagrams sent by particular sources to 227 the IP multicast groups known to this router." 228 ::= { ipMRoute 2 } 230 ipMRouteEntry OBJECT-TYPE 231 SYNTAX IpMRouteEntry 232 MAX-ACCESS not-accessible 233 STATUS current 234 DESCRIPTION 235 "An entry (conceptual row) containing the multicast routing 236 information for IP datagrams from a particular source and 237 addressed to a particular IP multicast group address. 238 Discontinuities in counters in this entry can be detected by 239 observing the value of ipMRouteUpTime." 240 INDEX { ipMRouteGroup, 241 ipMRouteSource, 242 ipMRouteSourceMask } 243 ::= { ipMRouteTable 1 } 245 IpMRouteEntry ::= SEQUENCE { 246 ipMRouteGroup IpAddress, 247 ipMRouteSource IpAddress, 248 ipMRouteSourceMask IpAddress, 249 ipMRouteUpstreamNeighbor IpAddress, 250 ipMRouteInIfIndex InterfaceIndexOrZero, 251 ipMRouteUpTime TimeTicks, 252 ipMRouteExpiryTime TimeTicks, 253 ipMRoutePkts Counter32, 254 ipMRouteDifferentInIfPackets Counter32, 255 ipMRouteOctets Counter32, 256 ipMRouteProtocol IpMRouteProtocol, 257 ipMRouteRtProto INTEGER, 258 ipMRouteRtAddress IpAddress, 259 ipMRouteRtMask IpAddress, 260 ipMRouteRtType INTEGER, 261 ipMRouteHCOctets Counter64 262 } 264 ipMRouteGroup OBJECT-TYPE 265 SYNTAX IpAddress 266 MAX-ACCESS not-accessible 267 STATUS current 268 DESCRIPTION 269 "The IP multicast group address for which this entry 270 contains multicast routing information." 271 ::= { ipMRouteEntry 1 } 273 ipMRouteSource OBJECT-TYPE 274 SYNTAX IpAddress 275 MAX-ACCESS not-accessible 276 STATUS current 277 DESCRIPTION 278 "The network address which when combined with the 279 corresponding value of ipMRouteSourceMask identifies the 280 sources for which this entry contains multicast routing 281 information." 282 ::= { ipMRouteEntry 2 } 284 ipMRouteSourceMask OBJECT-TYPE 285 SYNTAX IpAddress 286 MAX-ACCESS not-accessible 287 STATUS current 288 DESCRIPTION 289 "The network mask which when combined with the corresponding 290 value of ipMRouteSource identifies the sources for which 291 this entry contains multicast routing information." 292 ::= { ipMRouteEntry 3 } 294 ipMRouteUpstreamNeighbor OBJECT-TYPE 295 SYNTAX IpAddress 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The address of the upstream neighbor (e.g., RPF neighbor) 300 from which IP datagrams from these sources to this multicast 301 address are received, or 0.0.0.0 if the upstream neighbor is 302 unknown (e.g., in CBT)." 303 ::= { ipMRouteEntry 4 } 305 ipMRouteInIfIndex OBJECT-TYPE 306 SYNTAX InterfaceIndexOrZero 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The value of ifIndex for the interface on which IP 311 datagrams sent by these sources to this multicast address 312 are received. A value of 0 indicates that datagrams are not 313 subject to an incoming interface check, but may be accepted 314 on multiple interfaces (e.g., in CBT)." 315 ::= { ipMRouteEntry 5 } 317 ipMRouteUpTime OBJECT-TYPE 318 SYNTAX TimeTicks 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The time since the multicast routing information 323 represented by this entry was learned by the router." 324 ::= { ipMRouteEntry 6 } 326 ipMRouteExpiryTime OBJECT-TYPE 327 SYNTAX TimeTicks 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The minimum amount of time remaining before this entry will 332 be aged out. The value 0 indicates that the entry is not 333 subject to aging." 334 ::= { ipMRouteEntry 7 } 336 ipMRoutePkts OBJECT-TYPE 337 SYNTAX Counter32 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "The number of packets which this router has received from 342 these sources and addressed to this multicast group 343 address." 344 ::= { ipMRouteEntry 8 } 346 ipMRouteDifferentInIfPackets OBJECT-TYPE 347 SYNTAX Counter32 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The number of packets which this router has received from 352 these sources and addressed to this multicast group address, 353 which were dropped because they were not received on the 354 interface indicated by ipMRouteInIfIndex. Packets which are 355 not subject to an incoming interface check (e.g., using CBT) 356 are not counted." 357 ::= { ipMRouteEntry 9 } 359 ipMRouteOctets OBJECT-TYPE 360 SYNTAX Counter32 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The number of octets contained in IP datagrams which were 365 received from these sources and addressed to this multicast 366 group address, and which were forwarded by this router." 367 ::= { ipMRouteEntry 10 } 369 ipMRouteProtocol OBJECT-TYPE 370 SYNTAX IpMRouteProtocol 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The multicast routing protocol via which this multicast 375 forwarding entry was learned." 376 ::= { ipMRouteEntry 11 } 378 ipMRouteRtProto OBJECT-TYPE 379 SYNTAX INTEGER { 380 other (1), -- not specified 381 local (2), -- local interface 382 netmgmt (3), -- static route 383 icmp (4), -- result of ICMP Redirect 384 -- the following are all dynamic 385 -- routing protocols 386 egp (5), -- Exterior Gateway Protocol 387 ggp (6), -- Gateway-Gateway Protocol 388 hello (7), -- FuzzBall HelloSpeak 389 rip (8), -- Berkeley RIP or RIP-II 390 isIs (9), -- Dual IS-IS 391 esIs (10), -- ISO 9542 392 ciscoIgrp (11), -- Cisco IGRP 393 bbnSpfIgp (12), -- BBN SPF IGP 394 ospf (13), -- Open Shortest Path First 395 bgp (14), -- Border Gateway Protocol 396 idpr (15), -- InterDomain Policy Routing 397 ciscoEigrp (16), -- Cisco EIGRP 398 dvmrp (17) -- DVMRP 399 } 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The routing mechanism via which the route used to find the 404 upstream or parent interface for this multicast forwarding 405 entry was learned. Inclusion of values for routing 406 protocols is not intended to imply that those protocols need 407 be supported." 408 ::= { ipMRouteEntry 12 } 410 ipMRouteRtAddress OBJECT-TYPE 411 SYNTAX IpAddress 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The address portion of the route used to find the upstream 416 or parent interface for this multicast forwarding entry." 417 ::= { ipMRouteEntry 13 } 419 ipMRouteRtMask OBJECT-TYPE 420 SYNTAX IpAddress 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The mask associated with the route used to find the upstream 425 or parent interface for this multicast forwarding entry." 426 ::= { ipMRouteEntry 14 } 428 ipMRouteRtType OBJECT-TYPE 429 SYNTAX INTEGER { 430 unicast (1), -- Unicast route used in multicast RIB 431 multicast (2) -- Multicast route 432 } 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The reason the given route was placed in the (logical) 437 multicast Routing Information Base (RIB). A value of 438 unicast means that the route would normally be placed only 439 in the unicast RIB, but was placed in the multicast RIB 440 (instead or in addition) due to local configuration, such as 441 when running PIM over RIP. A value of multicast means that 442 the route was explicitly added to the multicast RIB by the 443 routing protocol, such as DVMRP or Multiprotocol BGP." 444 ::= { ipMRouteEntry 15 } 446 ipMRouteHCOctets OBJECT-TYPE 447 SYNTAX Counter64 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The number of octets contained in IP datagrams which were 452 received from these sources and addressed to this multicast 453 group address, and which were forwarded by this router. 454 This object is a 64-bit version of ipMRouteOctets." 456 ::= { ipMRouteEntry 16 } 458 -- 459 -- The IP Multicast Routing Next Hop Table 460 -- 462 ipMRouteNextHopTable OBJECT-TYPE 463 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "The (conceptual) table containing information on the next- 468 hops on outgoing interfaces for routing IP multicast 469 datagrams. Each entry is one of a list of next-hops on 470 outgoing interfaces for particular sources sending to a 471 particular multicast group address." 472 ::= { ipMRoute 3 } 474 ipMRouteNextHopEntry OBJECT-TYPE 475 SYNTAX IpMRouteNextHopEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "An entry (conceptual row) in the list of next-hops on 480 outgoing interfaces to which IP multicast datagrams from 481 particular sources to a IP multicast group address are 482 routed. Discontinuities in counters in this entry can be 483 detected by observing the value of ipMRouteUpTime." 484 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 485 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 486 ipMRouteNextHopAddress } 487 ::= { ipMRouteNextHopTable 1 } 489 IpMRouteNextHopEntry ::= SEQUENCE { 490 ipMRouteNextHopGroup IpAddress, 491 ipMRouteNextHopSource IpAddress, 492 ipMRouteNextHopSourceMask IpAddress, 493 ipMRouteNextHopIfIndex InterfaceIndex, 494 ipMRouteNextHopAddress IpAddress, 495 ipMRouteNextHopState INTEGER, 496 ipMRouteNextHopUpTime TimeTicks, 497 ipMRouteNextHopExpiryTime TimeTicks, 498 ipMRouteNextHopClosestMemberHops Integer32, 499 ipMRouteNextHopProtocol IpMRouteProtocol, 500 ipMRouteNextHopPkts Counter32 501 } 503 ipMRouteNextHopGroup OBJECT-TYPE 504 SYNTAX IpAddress 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "The IP multicast group for which this entry specifies a 509 next-hop on an outgoing interface." 510 ::= { ipMRouteNextHopEntry 1 } 512 ipMRouteNextHopSource OBJECT-TYPE 513 SYNTAX IpAddress 514 MAX-ACCESS not-accessible 515 STATUS current 516 DESCRIPTION 517 "The network address which when combined with the 518 corresponding value of ipMRouteNextHopSourceMask identifies 519 the sources for which this entry specifies a next-hop on an 520 outgoing interface." 521 ::= { ipMRouteNextHopEntry 2 } 523 ipMRouteNextHopSourceMask OBJECT-TYPE 524 SYNTAX IpAddress 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "The network mask which when combined with the corresponding 529 value of ipMRouteNextHopSource identifies the sources for 530 which this entry specifies a next-hop on an outgoing 531 interface." 532 ::= { ipMRouteNextHopEntry 3 } 534 ipMRouteNextHopIfIndex OBJECT-TYPE 535 SYNTAX InterfaceIndex 536 MAX-ACCESS not-accessible 537 STATUS current 538 DESCRIPTION 539 "The ifIndex value of the interface for the outgoing 540 interface for this next-hop." 541 ::= { ipMRouteNextHopEntry 4 } 543 ipMRouteNextHopAddress OBJECT-TYPE 544 SYNTAX IpAddress 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "The address of the next-hop specific to this entry. For 549 most interfaces, this is identical to ipMRouteNextHopGroup. 550 NBMA interfaces, however, may have multiple next-hop 551 addresses out a single outgoing interface." 552 ::= { ipMRouteNextHopEntry 5 } 554 ipMRouteNextHopState OBJECT-TYPE 555 SYNTAX INTEGER { pruned(1), forwarding(2) } 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "An indication of whether the outgoing interface and next- 560 hop represented by this entry is currently being used to 561 forward IP datagrams. The value 'forwarding' indicates it 562 is currently being used; the value 'pruned' indicates it is 563 not." 564 ::= { ipMRouteNextHopEntry 6 } 566 ipMRouteNextHopUpTime OBJECT-TYPE 567 SYNTAX TimeTicks 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The time since the multicast routing information 572 represented by this entry was learned by the router." 573 ::= { ipMRouteNextHopEntry 7 } 575 ipMRouteNextHopExpiryTime OBJECT-TYPE 576 SYNTAX TimeTicks 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The minimum amount of time remaining before this entry will 581 be aged out. If ipMRouteNextHopState is pruned(1), the 582 remaining time until the prune expires and the state reverts 583 to forwarding(2). Otherwise, the remaining time until this 584 entry is removed from the table. The time remaining may be 585 copied from ipMRouteExpiryTime if the protocol in use for 586 this entry dos not specify next-hop timers. The value 0 587 indicates that the entry is not subject to aging." 588 ::= { ipMRouteNextHopEntry 8 } 590 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 591 SYNTAX Integer32 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "The minimum number of hops between this router and any 596 member of this IP multicast group reached via this next-hop 597 on this outgoing interface. Any IP multicast datagrams for 598 the group which have a TTL less than this number of hops 599 will not be forwarded to this next-hop." 600 ::= { ipMRouteNextHopEntry 9 } 602 ipMRouteNextHopProtocol OBJECT-TYPE 603 SYNTAX IpMRouteProtocol 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The routing mechanism via which this next-hop was learned." 608 ::= { ipMRouteNextHopEntry 10 } 610 ipMRouteNextHopPkts OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The number of packets which have been forwarded using this 616 route." 617 ::= { ipMRouteNextHopEntry 11 } 619 -- 620 -- The Multicast Routing Interface Table 621 -- 623 ipMRouteInterfaceTable OBJECT-TYPE 624 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "The (conceptual) table containg multicast routing 629 information specific to interfaces." 630 ::= { ipMRoute 4 } 632 ipMRouteInterfaceEntry OBJECT-TYPE 633 SYNTAX IpMRouteInterfaceEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "An entry (conceptual row) containing the multicast routing 638 information for a particular interface." 639 INDEX { ipMRouteInterfaceIfIndex } 640 ::= { ipMRouteInterfaceTable 1 } 642 IpMRouteInterfaceEntry ::= SEQUENCE { 643 ipMRouteInterfaceIfIndex InterfaceIndex, 644 ipMRouteInterfaceTtl Integer32, 645 ipMRouteInterfaceProtocol IpMRouteProtocol, 646 ipMRouteInterfaceRateLimit Integer32, 647 ipMRouteInterfaceInMcastOctets Counter32, 648 ipMRouteInterfaceOutMcastOctets Counter32, 649 ipMRouteInterfaceHCInMcastOctets Counter64, 650 ipMRouteInterfaceHCOutMcastOctets Counter64 651 } 653 ipMRouteInterfaceIfIndex OBJECT-TYPE 654 SYNTAX InterfaceIndex 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "The ifIndex value of the interface for which this entry 659 contains information." 660 ::= { ipMRouteInterfaceEntry 1 } 662 ipMRouteInterfaceTtl OBJECT-TYPE 663 SYNTAX Integer32 (0..255) 664 MAX-ACCESS read-write 665 STATUS current 666 DESCRIPTION 667 "The datagram TTL threshold for the interface. Any IP 668 multicast datagrams with a TTL less than this threshold will 669 not be forwarded out the interface. The default value of 0 670 means all multicast packets are forwarded out the 671 interface." 672 ::= { ipMRouteInterfaceEntry 2 } 674 ipMRouteInterfaceProtocol OBJECT-TYPE 675 SYNTAX IpMRouteProtocol 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The routing protocol running on this interface." 680 ::= { ipMRouteInterfaceEntry 3 } 682 ipMRouteInterfaceRateLimit OBJECT-TYPE 683 SYNTAX Integer32 684 MAX-ACCESS read-write 685 STATUS current 686 DESCRIPTION 687 "The rate-limit, in kilobits per second, of forwarded 688 multicast traffic on the interface. A rate-limit of 0 689 indicates that no rate limiting is done." 690 DEFVAL { 0 } 691 ::= { ipMRouteInterfaceEntry 4 } 693 ipMRouteInterfaceInMcastOctets OBJECT-TYPE 694 SYNTAX Counter32 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "The number of octets of multicast packets that have arrived 699 on the interface, including framing characters. This object 700 is similar to ifInOctets in the Interfaces MIB, except that 701 only multicast packets are counted." 702 ::= { ipMRouteInterfaceEntry 5 } 704 ipMRouteInterfaceOutMcastOctets OBJECT-TYPE 705 SYNTAX Counter32 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "The number of octets of multicast packets that have been 710 sent on the interface." 711 ::= { ipMRouteInterfaceEntry 6 } 713 ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE 714 SYNTAX Counter64 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "The number of octets of multicast packets that have arrived 719 on the interface, including framing characters. This object 720 is a 64-bit version of ipMRouteInterfaceInMcastOctets. It 721 is similar to ifHCInOctets in the Interfaces MIB, except 722 that only multicast packets are counted." 723 ::= { ipMRouteInterfaceEntry 7 } 725 ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 726 SYNTAX Counter64 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "The number of octets of multicast packets that have been 731 sent on the interface. This object is a 64-bit version of 732 ipMRouteInterfaceOutMcastOctets." 733 ::= { ipMRouteInterfaceEntry 8 } 735 -- 736 -- The IP Multicast Scope Boundary Table 737 -- 739 ipMRouteBoundaryTable OBJECT-TYPE 740 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "The (conceptual) table listing the router's scoped 745 multicast address boundaries." 746 ::= { ipMRoute 5 } 748 ipMRouteBoundaryEntry OBJECT-TYPE 749 SYNTAX IpMRouteBoundaryEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "An entry (conceptual row) in the ipMRouteBoundaryTable 754 representing a scoped boundary." 755 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 756 ipMRouteBoundaryAddressMask } 757 ::= { ipMRouteBoundaryTable 1 } 759 IpMRouteBoundaryEntry ::= SEQUENCE { 760 ipMRouteBoundaryIfIndex InterfaceIndex, 761 ipMRouteBoundaryAddress IpAddress, 762 ipMRouteBoundaryAddressMask IpAddress, 763 ipMRouteBoundaryStatus RowStatus 764 } 766 ipMRouteBoundaryIfIndex OBJECT-TYPE 767 SYNTAX InterfaceIndex 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "The IfIndex value for the interface to which this boundary 772 applies. Packets with a destination address in the 773 associated address/mask range will not be forwarded out this 774 interface." 775 ::= { ipMRouteBoundaryEntry 1 } 777 ipMRouteBoundaryAddress OBJECT-TYPE 778 SYNTAX IpAddress 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "The group address which when combined with the 783 corresponding value of ipMRouteBoundaryAddressMask 784 identifies the group range for which the scoped boundary 785 exists. Scoped addresses must come from the range 239.x.x.x 786 as specified in RFC 2365." 787 ::= { ipMRouteBoundaryEntry 2 } 789 ipMRouteBoundaryAddressMask OBJECT-TYPE 790 SYNTAX IpAddress 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "The group address mask which when combined with the 795 corresponding value of ipMRouteBoundaryAddress identifies 796 the group range for which the scoped boundary exists." 797 ::= { ipMRouteBoundaryEntry 3 } 799 ipMRouteBoundaryStatus OBJECT-TYPE 800 SYNTAX RowStatus 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The status of this row, by which new entries may be 805 created, or old entries deleted from this table." 806 ::= { ipMRouteBoundaryEntry 4 } 808 -- 809 -- The IP Multicast Scope Name Table 810 -- 812 ipMRouteScopeNameTable OBJECT-TYPE 813 SYNTAX SEQUENCE OF IpMRouteScopeNameEntry 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "The (conceptual) table listing the multicast scope names." 818 ::= { ipMRoute 6 } 820 ipMRouteScopeNameEntry OBJECT-TYPE 821 SYNTAX IpMRouteScopeNameEntry 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "An entry (conceptual row) in the ipMRouteScopeNameTable 826 representing a multicast scope name." 827 INDEX { ipMRouteScopeNameAddress, 828 ipMRouteScopeNameAddressMask, 829 IMPLIED ipMRouteScopeNameLanguage } 830 ::= { ipMRouteScopeNameTable 1 } 832 IpMRouteScopeNameEntry ::= SEQUENCE { 833 ipMRouteScopeNameAddress IpAddress, 834 ipMRouteScopeNameAddressMask IpAddress, 835 ipMRouteScopeNameLanguage DisplayString, 836 ipMRouteScopeNameString SnmpAdminString, 837 ipMRouteScopeNameDefault TruthValue, 838 ipMRouteScopeNameStatus RowStatus 839 } 841 ipMRouteScopeNameAddress OBJECT-TYPE 842 SYNTAX IpAddress 843 MAX-ACCESS not-accessible 844 STATUS current 845 DESCRIPTION 846 "The group address which when combined with the 847 corresponding value of ipMRouteScopeNameAddressMask 848 identifies the group range associated with the multicast 849 scope. Scoped addresses must come from the range 850 239.x.x.x." 851 ::= { ipMRouteScopeNameEntry 1 } 853 ipMRouteScopeNameAddressMask OBJECT-TYPE 854 SYNTAX IpAddress 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "The group address mask which when combined with the 859 corresponding value of ipMRouteScopeNameAddress identifies 860 the group range associated with the multicast scope." 861 ::= { ipMRouteScopeNameEntry 2 } 863 ipMRouteScopeNameLanguage OBJECT-TYPE 864 SYNTAX DisplayString (SIZE (1..100)) 865 MAX-ACCESS not-accessible 866 STATUS current 867 DESCRIPTION 868 "An RFC 1766-style language tag, with all alphabetic 869 characters converted to lowercase. This restriction is 870 intended to make the lexical ordering imposed by SNMP useful 871 when applied to language tags. Note that it is 872 theoretically possible for a valid language tag to exceed 873 the allowed length of this object, and thus be impossible to 874 represent in this table. Sampling of language tags in 875 current use on the Internet suggests that this limit does 876 not pose a serious problem in practice." 877 ::= { ipMRouteScopeNameEntry 3 } 879 ipMRouteScopeNameString OBJECT-TYPE 880 SYNTAX SnmpAdminString 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The textual name associated with the multicast scope. The 885 value of this object should be suitable for displaying to 886 end-users, such as when allocating a multicast address in 887 this scope. When no name is specified, the default value of 888 this object should be the string 239.x.x.x/y with x and y 889 replaced appropriately to describe the address and mask 890 length associated with the scope." 891 ::= { ipMRouteScopeNameEntry 4 } 893 ipMRouteScopeNameDefault OBJECT-TYPE 894 SYNTAX TruthValue 895 MAX-ACCESS read-create 896 STATUS current 897 DESCRIPTION 898 "If true, indicates a preference that the name in the 899 following language should be used by applications if no name 900 is available in a desired language." 901 DEFVAL { false } 902 ::= { ipMRouteScopeNameEntry 5 } 904 ipMRouteScopeNameStatus OBJECT-TYPE 905 SYNTAX RowStatus 906 MAX-ACCESS read-create 907 STATUS current 908 DESCRIPTION 909 "The status of this row, by which new entries may be 910 created, or old entries deleted from this table." 911 ::= { ipMRouteScopeNameEntry 6 } 913 -- conformance information 915 ipMRouteMIBConformance 916 OBJECT IDENTIFIER ::= { ipMRouteMIB 2 } 917 ipMRouteMIBCompliances 918 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 919 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 921 -- compliance statements 923 ipMRouteMIBCompliance MODULE-COMPLIANCE 924 STATUS current 925 DESCRIPTION 926 "The compliance statement for the IP Multicast MIB." 927 MODULE -- this module 928 MANDATORY-GROUPS { ipMRouteMIBBasicGroup, 929 ipMRouteMIBRouteGroup} 931 GROUP ipMRouteMIBBoundaryGroup 932 DESCRIPTION 933 "This group is mandatory if the router supports 934 administratively-scoped multicast address boundaries." 936 OBJECT ipMRouteBoundaryStatus 937 MIN-ACCESS read-only 938 DESCRIPTION 939 "Write access is not required." 941 OBJECT ipMRouteScopeNameStatus 942 MIN-ACCESS read-only 943 DESCRIPTION 944 "Write access is not required." 946 GROUP ipMRouteMIBHCInterfaceGroup 947 DESCRIPTION 948 "This group is mandatory only for those network interfaces 949 for which the value of the corresponding instance of ifSpeed 950 is greater than 20,000,000 bits/second." 952 ::= { ipMRouteMIBCompliances 1 } 954 -- units of conformance 955 ipMRouteMIBBasicGroup OBJECT-GROUP 956 OBJECTS { ipMRouteEnable, ipMRouteEntryCount, 957 ipMRouteUpstreamNeighbor, ipMRouteInIfIndex, 958 ipMRouteUpTime, ipMRouteExpiryTime, 959 ipMRouteNextHopState, 960 ipMRouteNextHopUpTime, 961 ipMRouteNextHopExpiryTime, 962 ipMRouteNextHopProtocol, 963 ipMRouteNextHopPkts, 964 ipMRouteInterfaceTtl, 965 ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, 966 ipMRouteInterfaceInMcastOctets, 967 ipMRouteInterfaceOutMcastOctets, 968 ipMRouteProtocol 969 } 970 STATUS current 971 DESCRIPTION 972 "A collection of objects to support basic management of IP 973 Multicast routing." 974 ::= { ipMRouteMIBGroups 1 } 976 ipMRouteMIBHopCountGroup OBJECT-GROUP 977 OBJECTS { ipMRouteNextHopClosestMemberHops } 978 STATUS current 979 DESCRIPTION 980 "A collection of objects to support management of the use of 981 hop counts in IP Multicast routing." 982 ::= { ipMRouteMIBGroups 2 } 984 ipMRouteMIBBoundaryGroup OBJECT-GROUP 985 OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString, 986 ipMRouteScopeNameDefault, ipMRouteScopeNameStatus } 987 STATUS current 988 DESCRIPTION 989 "A collection of objects to support management of scoped 990 multicast address boundaries." 991 ::= { ipMRouteMIBGroups 3 } 993 ipMRouteMIBPktsOutGroup OBJECT-GROUP 994 OBJECTS { ipMRouteNextHopPkts } 995 STATUS current 996 DESCRIPTION 997 "A collection of objects to support management of packet 998 counters for each outgoing interface entry of a route." 999 ::= { ipMRouteMIBGroups 4 } 1001 ipMRouteMIBHCInterfaceGroup OBJECT-GROUP 1002 OBJECTS { ipMRouteInterfaceHCInMcastOctets, 1003 ipMRouteInterfaceHCOutMcastOctets, 1004 ipMRouteHCOctets } 1005 STATUS current 1006 DESCRIPTION 1007 "A collection of objects providing information specific to 1008 high speed (greater than 20,000,000 bits/second) network 1009 interfaces." 1010 ::= { ipMRouteMIBGroups 5 } 1012 ipMRouteMIBRouteGroup OBJECT-GROUP 1013 OBJECTS { ipMRouteRtProto, ipMRouteRtAddress, 1014 ipMRouteRtMask, ipMRouteRtType } 1015 STATUS current 1016 DESCRIPTION 1017 "A collection of objects providing information on the 1018 relationship between multicast routing information, and the 1019 IP Forwarding Table." 1020 ::= { ipMRouteMIBGroups 6 } 1022 ipMRouteMIBPktsGroup OBJECT-GROUP 1023 OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, 1024 ipMRouteOctets } 1025 STATUS current 1026 DESCRIPTION 1027 "A collection of objects to support management of packet 1028 counters for each forwarding entry." 1029 ::= { ipMRouteMIBGroups 7 } 1031 END 1032 6. Security Considerations 1034 This MIB contains readable objects whose values provide information 1035 related to multicast routing, including information on what machines are 1036 sending to which groups. There are also a number of objects that have a 1037 MAX-ACCESS clause of read-write and/or read-create, such as those which 1038 allow an administrator to configure multicast boundaries. 1040 While unauthorized access to the readable objects is relatively 1041 innocuous, unauthorized access to the write-able objects could cause a 1042 denial of service, or could cause wider distribution of packets intended 1043 only for local distribution. Hence, the support for SET operations in a 1044 non-secure environment without proper protection can have a negative 1045 effect on network operations. 1047 SNMPv1 by itself is such an insecure environment. Even if the network 1048 itself is secure (for example by using IPSec), even then, there is no 1049 control as to who on the secure network is allowed to access and SET 1050 (change/create/delete) the objects in this MIB. 1052 It is recommended that the implementers consider the security features 1053 as provided by the SNMPv3 framework. Specifically, the use of the 1054 User-based Security Model RFC 2574 [12] and the View-based Access 1055 Control Model RFC 2575 [15] is recommended. 1057 It is then a customer/user responsibility to ensure that the SNMP entity 1058 giving access to this MIB, is properly configured to give access to 1059 those objects only to those principals (users) that have legitimate 1060 rights to access them. 1062 7. Acknowledgements 1064 This MIB module was updated based on feedback from the IETF's Inter- 1065 Domain Multicast Routing (IDMR) Working Group. 1067 8. Authors' Addresses 1069 Keith McCloghrie 1070 cisco Systems, Inc. 1071 170 West Tasman Drive 1072 San Jose, CA 95134-1706 1073 Phone: +1 408 526 5260 1074 EMail: kzm@cisco.com 1076 Dino Farinacci 1077 cisco Systems, Inc. 1078 170 West Tasman Drive 1079 San Jose, CA 95134-1706 1080 Phone: +1 408 526 4696 1081 EMail: dino@cisco.com 1083 Dave Thaler 1084 Microsoft Corporation 1085 One Microsoft Way 1086 Redmond, WA 98052-6399 1087 Phone: +1 425 703 8835 1088 EMail: dthaler@microsoft.com 1090 9. References 1092 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1093 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1094 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1095 1999. 1097 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1098 Management Information for TCP/IP-based Internets", RFC 1155, STD 1099 16, Performance Systems International, Hughes LAN Systems, May 1100 1990. 1102 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1103 STD 16, Performance Systems International, Hughes LAN Systems, 1104 March 1991. 1106 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1107 RFC 1215, Performance Systems International, March 1991. 1109 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1110 and S. Waldbusser, "Structure of Management Information Version 2 1111 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1112 Braunschweig, SNMP Research, First Virtual Holdings, International 1113 Network Services, April 1999. 1115 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1116 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1117 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1118 Virtual Holdings, International Network Services, April 1999. 1120 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1121 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1122 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1123 First Virtual Holdings, International Network Services, April 1999. 1125 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1126 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1127 Systems International, Performance Systems International, MIT 1128 Laboratory for Computer Science, May 1990. 1130 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1131 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1132 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1133 International Network Services, January 1996. 1135 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1136 Mappings for Version 2 of the Simple Network Management Protocol 1137 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1138 Dover Beach Consulting, Inc., International Network Services, 1139 January 1996. 1141 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1142 Processing and Dispatching for the Simple Network Management 1143 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1144 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1146 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1147 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1148 2574, IBM T. J. Watson Research, April 1999. 1150 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1151 Operations for Version 2 of the Simple Network Management Protocol 1152 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1153 Dover Beach Consulting, Inc., International Network Services, 1154 January 1996. 1156 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1157 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1158 Systems, April 1999. 1160 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1161 Control Model (VACM) for the Simple Network Management Protocol 1162 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1163 Cisco Systems, Inc., April 1999. 1165 [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1166 thesis, Electrical Engineering Dept., Stanford University, December 1167 1991. 1169 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1170 Multicast Routing Protocol", RFC 1075, November 1988. 1172 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1173 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1174 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1175 Specification", RFC 2362, June 1998. 1177 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1178 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1179 Specification". Work in progress, May 1997. 1181 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1183 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1184 Routing", RFC 2189, September 1997. 1186 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1187 23, July 1998. 1189 10. Full Copyright Statement 1191 Copyright (C) The Internet Society (1999). All Rights Reserved. 1193 This document and translations of it may be copied and furnished to 1194 others, and derivative works that comment on or otherwise explain it or 1195 assist in its implmentation may be prepared, copied, published and 1196 distributed, in whole or in part, without restriction of any kind, 1197 provided that the above copyright notice and this paragraph are included 1198 on all such copies and derivative works. However, this document itself 1199 may not be modified in any way, such as by removing the copyright notice 1200 or references to the Internet Society or other Internet organizations, 1201 except as needed for the purpose of developing Internet standards in 1202 which case the procedures for copyrights defined in the Internet 1203 Standards process must be followed, or as required to translate it into 1204 languages other than English. 1206 The limited permissions granted above are perpetual and will not be 1207 revoked by the Internet Society or its successors or assigns. 1209 This document and the information contained herein is provided on an "AS 1210 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1211 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1212 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1213 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1214 FITNESS FOR A PARTICULAR PURPOSE. 1216 Table of Contents 1218 1 Abstract ........................................................ 2 1219 2 Introduction .................................................... 2 1220 3 The SNMP Management Framework ................................... 2 1221 3.1 Object Definitions ............................................ 3 1222 4 Overview ........................................................ 3 1223 5 Definitions ..................................................... 5 1224 6 Security Considerations ......................................... 27 1225 7 Acknowledgements ................................................ 27 1226 8 Authors' Addresses .............................................. 27 1227 9 References ...................................................... 28 1228 10 Full Copyright Statement ....................................... 30