idnits 2.17.1 draft-ietf-idmr-multicast-routmib-09.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: ---------------------------------------------------------------------------- ** 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 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 June 1999) is 9076 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 1159, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1162, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1167, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1171, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1173, 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: 21 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 December 1999 cisco Systems 4 Dave Thaler 5 Microsoft 6 22 June 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, 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 "9906221200Z" -- June 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 "9906221200Z" -- June 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 } 192 -- Top-level structyre of the MIB 194 ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 } 196 ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } 197 -- the IP Multicast Routing MIB-Group 198 -- 199 -- a collection of objects providing information about 200 -- IP Multicast Groups 202 ipMRouteEnable OBJECT-TYPE 203 SYNTAX INTEGER { enabled(1), disabled(2) } 204 MAX-ACCESS read-write 205 STATUS current 206 DESCRIPTION 207 "The enabled status of IP Multicast routing on this router." 208 ::= { ipMRoute 1 } 210 ipMRouteTable OBJECT-TYPE 211 SYNTAX SEQUENCE OF IpMRouteEntry 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "The (conceptual) table containing multicast routing 216 information for IP datagrams sent by particular sources to 217 the IP multicast groups known to this router." 218 ::= { ipMRoute 2 } 220 ipMRouteEntry OBJECT-TYPE 221 SYNTAX IpMRouteEntry 222 MAX-ACCESS not-accessible 223 STATUS current 224 DESCRIPTION 225 "An entry (conceptual row) containing the multicast routing 226 information for IP datagrams from a particular source and 227 addressed to a particular IP multicast group address. 228 Discontinuities in counters in this entry can be detected by 229 observing the value of ipMRouteUpTime." 230 INDEX { ipMRouteGroup, 231 ipMRouteSource, 232 ipMRouteSourceMask } 233 ::= { ipMRouteTable 1 } 235 IpMRouteEntry ::= SEQUENCE { 236 ipMRouteGroup IpAddress, 237 ipMRouteSource IpAddress, 238 ipMRouteSourceMask IpAddress, 239 ipMRouteUpstreamNeighbor IpAddress, 240 ipMRouteInIfIndex InterfaceIndexOrZero, 241 ipMRouteUpTime TimeTicks, 242 ipMRouteExpiryTime TimeTicks, 243 ipMRoutePkts Counter32, 244 ipMRouteDifferentInIfPackets Counter32, 245 ipMRouteOctets Counter32, 246 ipMRouteProtocol IpMRouteProtocol, 247 ipMRouteRtProto INTEGER, 248 ipMRouteRtAddress IpAddress, 249 ipMRouteRtMask IpAddress, 250 ipMRouteRtType INTEGER, 251 ipMRouteHCOctets Counter64 252 } 254 ipMRouteGroup OBJECT-TYPE 255 SYNTAX IpAddress 256 MAX-ACCESS not-accessible 257 STATUS current 258 DESCRIPTION 259 "The IP multicast group address for which this entry 260 contains multicast routing information." 261 ::= { ipMRouteEntry 1 } 263 ipMRouteSource OBJECT-TYPE 264 SYNTAX IpAddress 265 MAX-ACCESS not-accessible 266 STATUS current 267 DESCRIPTION 268 "The network address which when combined with the 269 corresponding value of ipMRouteSourceMask identifies the 270 sources for which this entry contains multicast routing 271 information." 272 ::= { ipMRouteEntry 2 } 274 ipMRouteSourceMask OBJECT-TYPE 275 SYNTAX IpAddress 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "The network mask which when combined with the corresponding 280 value of ipMRouteSource identifies the sources for which 281 this entry contains multicast routing information." 282 ::= { ipMRouteEntry 3 } 284 ipMRouteUpstreamNeighbor OBJECT-TYPE 285 SYNTAX IpAddress 286 MAX-ACCESS read-only 287 STATUS current 288 DESCRIPTION 289 "The address of the upstream neighbor (e.g., RPF neighbor) 290 from which IP datagrams from these sources to this multicast 291 address are received, or 0.0.0.0 if the upstream neighbor is 292 unknown (e.g., in CBT)." 293 ::= { ipMRouteEntry 4 } 295 ipMRouteInIfIndex OBJECT-TYPE 296 SYNTAX InterfaceIndexOrZero 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The value of ifIndex for the interface on which IP 301 datagrams sent by these sources to this multicast address 302 are received. A value of 0 indicates that datagrams are not 303 subject to an incoming interface check, but may be accepted 304 on multiple interfaces (e.g., in CBT)." 305 ::= { ipMRouteEntry 5 } 307 ipMRouteUpTime OBJECT-TYPE 308 SYNTAX TimeTicks 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The time since the multicast routing information 313 represented by this entry was learned by the router." 314 ::= { ipMRouteEntry 6 } 316 ipMRouteExpiryTime OBJECT-TYPE 317 SYNTAX TimeTicks 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "The minimum amount of time remaining before this entry will 322 be aged out. The value 0 indicates that the entry is not 323 subject to aging." 324 ::= { ipMRouteEntry 7 } 326 ipMRoutePkts OBJECT-TYPE 327 SYNTAX Counter32 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The number of packets which this router has received from 332 these sources and addressed to this multicast group 333 address." 334 ::= { ipMRouteEntry 8 } 336 ipMRouteDifferentInIfPackets 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 address, 343 which were dropped because they were not received on the 344 interface indicated by ipMRouteInIfIndex. Packets which are 345 not subject to an incoming interface check (e.g., using CBT) 346 are not counted." 347 ::= { ipMRouteEntry 9 } 349 ipMRouteOctets OBJECT-TYPE 350 SYNTAX Counter32 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The number of octets contained in IP datagrams which were 355 received from these sources and addressed to this multicast 356 group address, and which were forwarded by this router." 357 ::= { ipMRouteEntry 10 } 359 ipMRouteProtocol OBJECT-TYPE 360 SYNTAX IpMRouteProtocol 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The multicast routing protocol via which this multicast 365 forwarding entry was learned." 366 ::= { ipMRouteEntry 11 } 368 ipMRouteRtProto OBJECT-TYPE 369 SYNTAX INTEGER { 370 other (1), -- not specified 371 local (2), -- local interface 372 netmgmt (3), -- static route 373 icmp (4), -- result of ICMP Redirect 374 -- the following are all dynamic 375 -- routing protocols 376 egp (5), -- Exterior Gateway Protocol 377 ggp (6), -- Gateway-Gateway Protocol 378 hello (7), -- FuzzBall HelloSpeak 379 rip (8), -- Berkeley RIP or RIP-II 380 isIs (9), -- Dual IS-IS 381 esIs (10), -- ISO 9542 382 ciscoIgrp (11), -- Cisco IGRP 383 bbnSpfIgp (12), -- BBN SPF IGP 384 ospf (13), -- Open Shortest Path First 385 bgp (14), -- Border Gateway Protocol 386 idpr (15), -- InterDomain Policy Routing 387 ciscoEigrp (16), -- Cisco EIGRP 388 dvmrp (17) -- DVMRP 389 } 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The routing mechanism via which the route used to find the 394 upstream or parent interface for this multicast forwarding 395 entry was learned. Inclusion of values for routing 396 protocols is not intended to imply that those protocols need 397 be supported." 398 ::= { ipMRouteEntry 12 } 400 ipMRouteRtAddress OBJECT-TYPE 401 SYNTAX IpAddress 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The address portion of the route used to find the upstream 406 or parent interface for this multicast forwarding entry." 407 ::= { ipMRouteEntry 13 } 409 ipMRouteRtMask OBJECT-TYPE 410 SYNTAX IpAddress 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The mask associated with the route used to find the upstream 415 or parent interface for this multicast forwarding entry." 417 ::= { ipMRouteEntry 14 } 419 ipMRouteRtType OBJECT-TYPE 420 SYNTAX INTEGER { 421 unicast (1), -- Unicast route used in multicast RIB 422 multicast (2) -- Multicast route 423 } 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The reason the given route was placed in the (logical) 428 multicast Routing Information Base (RIB). A value of 429 unicast means that the route would normally be placed only 430 in the unicast RIB, but was placed in the multicast RIB 431 (instead or in addition) due to local configuration, such as 432 when running PIM over RIP. A value of multicast means that 433 the route was explicitly added to the multicast RIB by the 434 routing protocol, such as DVMRP or Multiprotocol BGP." 435 ::= { ipMRouteEntry 15 } 437 ipMRouteHCOctets OBJECT-TYPE 438 SYNTAX Counter64 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The number of octets contained in IP datagrams which were 443 received from these sources and addressed to this multicast 444 group address, and which were forwarded by this router. 445 This object is a 64-bit version of ipMRouteOctets." 446 ::= { ipMRouteEntry 16 } 448 -- 449 -- The IP Multicast Routing Next Hop Table 450 -- 452 ipMRouteNextHopTable OBJECT-TYPE 453 SYNTAX SEQUENCE OF IpMRouteNextHopEntry 454 MAX-ACCESS not-accessible 455 STATUS current 456 DESCRIPTION 457 "The (conceptual) table containing information on the next- 458 hops on outgoing interfaces for routing IP multicast 459 datagrams. Each entry is one of a list of next-hops on 460 outgoing interfaces for particular sources sending to a 461 particular multicast group address." 462 ::= { ipMRoute 3 } 464 ipMRouteNextHopEntry OBJECT-TYPE 465 SYNTAX IpMRouteNextHopEntry 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "An entry (conceptual row) in the list of next-hops on 470 outgoing interfaces to which IP multicast datagrams from 471 particular sources to a IP multicast group address are 472 routed. Discontinuities in counters in this entry can be 473 detected by observing the value of ipMRouteUpTime." 474 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 475 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 476 ipMRouteNextHopAddress } 477 ::= { ipMRouteNextHopTable 1 } 479 IpMRouteNextHopEntry ::= SEQUENCE { 480 ipMRouteNextHopGroup IpAddress, 481 ipMRouteNextHopSource IpAddress, 482 ipMRouteNextHopSourceMask IpAddress, 483 ipMRouteNextHopIfIndex InterfaceIndex, 484 ipMRouteNextHopAddress IpAddress, 485 ipMRouteNextHopState INTEGER, 486 ipMRouteNextHopUpTime TimeTicks, 487 ipMRouteNextHopExpiryTime TimeTicks, 488 ipMRouteNextHopClosestMemberHops Integer32, 489 ipMRouteNextHopProtocol IpMRouteProtocol, 490 ipMRouteNextHopPkts Counter32 491 } 493 ipMRouteNextHopGroup OBJECT-TYPE 494 SYNTAX IpAddress 495 MAX-ACCESS not-accessible 496 STATUS current 497 DESCRIPTION 498 "The IP multicast group for which this entry specifies a 499 next-hop on an outgoing interface." 500 ::= { ipMRouteNextHopEntry 1 } 502 ipMRouteNextHopSource OBJECT-TYPE 503 SYNTAX IpAddress 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "The network address which when combined with the 508 corresponding value of ipMRouteNextHopSourceMask identifies 509 the sources for which this entry specifies a next-hop on an 510 outgoing interface." 511 ::= { ipMRouteNextHopEntry 2 } 513 ipMRouteNextHopSourceMask OBJECT-TYPE 514 SYNTAX IpAddress 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "The network mask which when combined with the corresponding 519 value of ipMRouteNextHopSource identifies the sources for 520 which this entry specifies a next-hop on an outgoing 521 interface." 522 ::= { ipMRouteNextHopEntry 3 } 524 ipMRouteNextHopIfIndex OBJECT-TYPE 525 SYNTAX InterfaceIndex 526 MAX-ACCESS not-accessible 527 STATUS current 528 DESCRIPTION 529 "The ifIndex value of the interface for the outgoing 530 interface for this next-hop." 531 ::= { ipMRouteNextHopEntry 4 } 533 ipMRouteNextHopAddress OBJECT-TYPE 534 SYNTAX IpAddress 535 MAX-ACCESS not-accessible 536 STATUS current 537 DESCRIPTION 538 "The address of the next-hop specific to this entry. For 539 most interfaces, this is identical to ipMRouteNextHopGroup. 540 NBMA interfaces, however, may have multiple next-hop 541 addresses out a single outgoing interface." 542 ::= { ipMRouteNextHopEntry 5 } 544 ipMRouteNextHopState OBJECT-TYPE 545 SYNTAX INTEGER { pruned(1), forwarding(2) } 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "An indication of whether the outgoing interface and next- 550 hop represented by this entry is currently being used to 551 forward IP datagrams. The value 'forwarding' indicates it 552 is currently being used; the value 'pruned' indicates it is 553 not." 554 ::= { ipMRouteNextHopEntry 6 } 556 ipMRouteNextHopUpTime OBJECT-TYPE 557 SYNTAX TimeTicks 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The time since the multicast routing information 562 represented by this entry was learned by the router." 563 ::= { ipMRouteNextHopEntry 7 } 565 ipMRouteNextHopExpiryTime OBJECT-TYPE 566 SYNTAX TimeTicks 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The minimum amount of time remaining before this entry will 571 be aged out. If ipMRouteNextHopState is pruned(1), the 572 remaining time until the prune expires and the state reverts 573 to forwarding(2). Otherwise, the remaining time until this 574 entry is removed from the table. The time remaining may be 575 copied from ipMRouteExpiryTime if the protocol in use for 576 this entry dos not specify next-hop timers. The value 0 577 indicates that the entry is not subject to aging." 578 ::= { ipMRouteNextHopEntry 8 } 580 ipMRouteNextHopClosestMemberHops OBJECT-TYPE 581 SYNTAX Integer32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The minimum number of hops between this router and any 586 member of this IP multicast group reached via this next-hop 587 on this outgoing interface. Any IP multicast datagrams for 588 the group which have a TTL less than this number of hops 589 will not be forwarded to this next-hop." 590 ::= { ipMRouteNextHopEntry 9 } 592 ipMRouteNextHopProtocol OBJECT-TYPE 593 SYNTAX IpMRouteProtocol 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The routing mechanism via which this next-hop was learned." 598 ::= { ipMRouteNextHopEntry 10 } 600 ipMRouteNextHopPkts OBJECT-TYPE 601 SYNTAX Counter32 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The number of packets which have been forwarded using this 606 route." 607 ::= { ipMRouteNextHopEntry 11 } 609 -- 610 -- The Multicast Routing Interface Table 611 -- 613 ipMRouteInterfaceTable OBJECT-TYPE 614 SYNTAX SEQUENCE OF IpMRouteInterfaceEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "The (conceptual) table containg multicast routing 619 information specific to interfaces." 620 ::= { ipMRoute 4 } 622 ipMRouteInterfaceEntry OBJECT-TYPE 623 SYNTAX IpMRouteInterfaceEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "An entry (conceptual row) containing the multicast routing 628 information for a particular interface." 629 INDEX { ipMRouteInterfaceIfIndex } 630 ::= { ipMRouteInterfaceTable 1 } 632 IpMRouteInterfaceEntry ::= SEQUENCE { 633 ipMRouteInterfaceIfIndex InterfaceIndex, 634 ipMRouteInterfaceTtl Integer32, 635 ipMRouteInterfaceProtocol IpMRouteProtocol, 636 ipMRouteInterfaceRateLimit Integer32, 637 ipMRouteInterfaceInMcastOctets Counter32, 638 ipMRouteInterfaceOutMcastOctets Counter32, 639 ipMRouteInterfaceHCInMcastOctets Counter64, 640 ipMRouteInterfaceHCOutMcastOctets Counter64 641 } 643 ipMRouteInterfaceIfIndex OBJECT-TYPE 644 SYNTAX InterfaceIndex 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "The ifIndex value of the interface for which this entry 649 contains information." 650 ::= { ipMRouteInterfaceEntry 1 } 652 ipMRouteInterfaceTtl OBJECT-TYPE 653 SYNTAX Integer32 (0..255) 654 MAX-ACCESS read-write 655 STATUS current 656 DESCRIPTION 657 "The datagram TTL threshold for the interface. Any IP 658 multicast datagrams with a TTL less than this threshold will 659 not be forwarded out the interface. The default value of 0 660 means all multicast packets are forwarded out the 661 interface." 662 ::= { ipMRouteInterfaceEntry 2 } 664 ipMRouteInterfaceProtocol OBJECT-TYPE 665 SYNTAX IpMRouteProtocol 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The routing protocol running on this interface." 670 ::= { ipMRouteInterfaceEntry 3 } 672 ipMRouteInterfaceRateLimit OBJECT-TYPE 673 SYNTAX Integer32 674 MAX-ACCESS read-write 675 STATUS current 676 DESCRIPTION 677 "The rate-limit, in kilobits per second, of forwarded 678 multicast traffic on the interface. A rate-limit of 0 679 indicates that no rate limiting is done." 680 DEFVAL { 0 } 681 ::= { ipMRouteInterfaceEntry 4 } 683 ipMRouteInterfaceInMcastOctets OBJECT-TYPE 684 SYNTAX Counter32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "The number of octets of multicast packets that have arrived 689 on the interface, including framing characters. This object 690 is similar to ifInOctets in the Interfaces MIB, except that 691 only multicast packets are counted." 692 ::= { ipMRouteInterfaceEntry 5 } 694 ipMRouteInterfaceOutMcastOctets OBJECT-TYPE 695 SYNTAX Counter32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The number of octets of multicast packets that have been 700 sent on the interface." 701 ::= { ipMRouteInterfaceEntry 6 } 703 ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE 704 SYNTAX Counter64 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "The number of octets of multicast packets that have arrived 709 on the interface, including framing characters. This object 710 is a 64-bit version of ipMRouteInterfaceInMcastOctets. It 711 is similar to ifHCInOctets in the Interfaces MIB, except 712 that only multicast packets are counted." 713 ::= { ipMRouteInterfaceEntry 7 } 715 ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE 716 SYNTAX Counter64 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The number of octets of multicast packets that have been 721 sent on the interface. This object is a 64-bit version of 722 ipMRouteInterfaceOutMcastOctets." 723 ::= { ipMRouteInterfaceEntry 8 } 725 -- 726 -- The IP Multicast Scope Boundary Table 727 -- 729 ipMRouteBoundaryTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF IpMRouteBoundaryEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "The (conceptual) table listing the router's scoped 735 multicast address boundaries." 736 ::= { ipMRoute 5 } 738 ipMRouteBoundaryEntry OBJECT-TYPE 739 SYNTAX IpMRouteBoundaryEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "An entry (conceptual row) in the ipMRouteBoundaryTable 744 representing a scoped boundary." 745 INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, 746 ipMRouteBoundaryAddressMask } 747 ::= { ipMRouteBoundaryTable 1 } 749 IpMRouteBoundaryEntry ::= SEQUENCE { 750 ipMRouteBoundaryIfIndex InterfaceIndex, 751 ipMRouteBoundaryAddress IpAddress, 752 ipMRouteBoundaryAddressMask IpAddress, 753 ipMRouteBoundaryStatus RowStatus 754 } 756 ipMRouteBoundaryIfIndex OBJECT-TYPE 757 SYNTAX InterfaceIndex 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "The IfIndex value for the interface to which this boundary 762 applies. Packets with a destination address in the 763 associated address/mask range will not be forwarded out this 764 interface." 765 ::= { ipMRouteBoundaryEntry 1 } 767 ipMRouteBoundaryAddress OBJECT-TYPE 768 SYNTAX IpAddress 769 MAX-ACCESS not-accessible 770 STATUS current 771 DESCRIPTION 772 "The group address which when combined with the 773 corresponding value of ipMRouteBoundaryAddressMask 774 identifies the group range for which the scoped boundary 775 exists. Scoped addresses must come from the range 239.x.x.x 776 as specified in RFC 2365." 777 ::= { ipMRouteBoundaryEntry 2 } 779 ipMRouteBoundaryAddressMask OBJECT-TYPE 780 SYNTAX IpAddress 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "The group address mask which when combined with the 785 corresponding value of ipMRouteBoundaryAddress identifies 786 the group range for which the scoped boundary exists." 787 ::= { ipMRouteBoundaryEntry 3 } 789 ipMRouteBoundaryStatus OBJECT-TYPE 790 SYNTAX RowStatus 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "The status of this row, by which new entries may be 795 created, or old entries deleted from this table." 796 ::= { ipMRouteBoundaryEntry 4 } 798 -- 799 -- The IP Multicast Scope Name Table 800 -- 802 ipMRouteScopeNameTable OBJECT-TYPE 803 SYNTAX SEQUENCE OF IpMRouteScopeNameEntry 804 MAX-ACCESS not-accessible 805 STATUS current 806 DESCRIPTION 807 "The (conceptual) table listing the multicast scope names." 808 ::= { ipMRoute 6 } 810 ipMRouteScopeNameEntry OBJECT-TYPE 811 SYNTAX IpMRouteScopeNameEntry 812 MAX-ACCESS not-accessible 813 STATUS current 814 DESCRIPTION 815 "An entry (conceptual row) in the ipMRouteScopeNameTable 816 representing a multicast scope name." 817 INDEX { ipMRouteScopeNameAddress, 818 ipMRouteScopeNameAddressMask, 819 IMPLIED ipMRouteScopeNameLanguage } 820 ::= { ipMRouteScopeNameTable 1 } 822 IpMRouteScopeNameEntry ::= SEQUENCE { 823 ipMRouteScopeNameAddress IpAddress, 824 ipMRouteScopeNameAddressMask IpAddress, 825 ipMRouteScopeNameLanguage DisplayString, 826 ipMRouteScopeNameString SnmpAdminString, 827 ipMRouteScopeNameDefault TruthValue, 828 ipMRouteScopeNameStatus RowStatus 829 } 831 ipMRouteScopeNameAddress OBJECT-TYPE 832 SYNTAX IpAddress 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "The group address which when combined with the 837 corresponding value of ipMRouteScopeNameAddressMask 838 identifies the group range associated with the multicast 839 scope. Scoped addresses must come from the range 840 239.x.x.x." 841 ::= { ipMRouteScopeNameEntry 1 } 843 ipMRouteScopeNameAddressMask OBJECT-TYPE 844 SYNTAX IpAddress 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "The group address mask which when combined with the 849 corresponding value of ipMRouteScopeNameAddress identifies 850 the group range associated with the multicast scope." 851 ::= { ipMRouteScopeNameEntry 2 } 853 ipMRouteScopeNameLanguage OBJECT-TYPE 854 SYNTAX DisplayString (SIZE (1..255)) 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "An RFC 1766-style language tag, with all alphabetic 859 characters converted to lowercase. This restriction is 860 intended to make the lexical ordering imposed by SNMP useful 861 when applied to language tags. Note that it is 862 theoretically possible for a valid language tag to exceed 863 the allowed length of an SNMP object identifier, and thus be 864 impossible to represent in this table. Sampling of language 865 tags in current use on the Internet suggests that this limit 866 does not pose a serious problem in practice." 867 ::= { ipMRouteScopeNameEntry 3 } 869 ipMRouteScopeNameString OBJECT-TYPE 870 SYNTAX SnmpAdminString 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "The textual name associated with the multicast scope. The 875 value of this object should be suitable for displaying to 876 end-users, such as when allocating a multicast address in 877 this scope. When no name is specified, the default value of 878 this object should be the string 239.x.x.x/y with x and y 879 replaced appropriately to describe the address and mask 880 length associated with the scope." 881 ::= { ipMRouteScopeNameEntry 4 } 883 ipMRouteScopeNameDefault OBJECT-TYPE 884 SYNTAX TruthValue 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "If true, indicates a preference that the name in the 889 following language should be used by applications if no name 890 is available in a desired language." 891 DEFVAL { false } 892 ::= { ipMRouteScopeNameEntry 5 } 894 ipMRouteScopeNameStatus OBJECT-TYPE 895 SYNTAX RowStatus 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "The status of this row, by which new entries may be 900 created, or old entries deleted from this table." 901 ::= { ipMRouteScopeNameEntry 6 } 903 -- conformance information 905 ipMRouteMIBConformance 906 OBJECT IDENTIFIER ::= { ipMRouteMIB 2 } 907 ipMRouteMIBCompliances 908 OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } 909 ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } 911 -- compliance statements 913 ipMRouteMIBCompliance MODULE-COMPLIANCE 914 STATUS current 915 DESCRIPTION 916 "The compliance statement for the IP Multicast MIB." 917 MODULE -- this module 918 MANDATORY-GROUPS { ipMRouteMIBBasicGroup, 919 ipMRouteMIBRouteGroup} 921 GROUP ipMRouteMIBBoundaryGroup 922 DESCRIPTION 923 "This group is mandatory if the router supports 924 administratively-scoped multicast address boundaries." 926 OBJECT ipMRouteBoundaryStatus 927 MIN-ACCESS read-only 928 DESCRIPTION 929 "Write access is not required." 931 OBJECT ipMRouteScopeNameStatus 932 MIN-ACCESS read-only 933 DESCRIPTION 934 "Write access is not required." 936 GROUP ipMRouteMIBHCInterfaceGroup 937 DESCRIPTION 938 "This group is mandatory only for those network interfaces 939 for which the value of the corresponding instance of ifSpeed 940 is greater than 20,000,000 bits/second." 942 ::= { ipMRouteMIBCompliances 1 } 944 -- units of conformance 945 ipMRouteMIBBasicGroup OBJECT-GROUP 946 OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor, 947 ipMRouteInIfIndex, 948 ipMRouteUpTime, ipMRouteExpiryTime, 949 ipMRouteNextHopState, 950 ipMRouteNextHopUpTime, 951 ipMRouteNextHopExpiryTime, 952 ipMRouteNextHopProtocol, 953 ipMRouteNextHopPkts, 954 ipMRouteInterfaceTtl, 955 ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, 956 ipMRouteInterfaceInMcastOctets, 957 ipMRouteInterfaceOutMcastOctets, 958 ipMRouteProtocol 959 } 960 STATUS current 961 DESCRIPTION 962 "A collection of objects to support basic management of IP 963 Multicast routing." 964 ::= { ipMRouteMIBGroups 1 } 966 ipMRouteMIBHopCountGroup OBJECT-GROUP 967 OBJECTS { ipMRouteNextHopClosestMemberHops } 968 STATUS current 969 DESCRIPTION 970 "A collection of objects to support management of the use of 971 hop counts in IP Multicast routing." 972 ::= { ipMRouteMIBGroups 2 } 974 ipMRouteMIBBoundaryGroup OBJECT-GROUP 975 OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString, 976 ipMRouteScopeNameDefault, ipMRouteScopeNameStatus } 977 STATUS current 978 DESCRIPTION 979 "A collection of objects to support management of scoped 980 multicast address boundaries." 981 ::= { ipMRouteMIBGroups 3 } 983 ipMRouteMIBPktsOutGroup OBJECT-GROUP 984 OBJECTS { ipMRouteNextHopPkts } 985 STATUS current 986 DESCRIPTION 987 "A collection of objects to support management of packet 988 counters for each outgoing interface entry of a route." 989 ::= { ipMRouteMIBGroups 4 } 991 ipMRouteMIBHCInterfaceGroup OBJECT-GROUP 992 OBJECTS { ipMRouteInterfaceHCInMcastOctets, 993 ipMRouteInterfaceHCOutMcastOctets, 994 ipMRouteHCOctets } 995 STATUS current 996 DESCRIPTION 997 "A collection of objects providing information specific to 998 high speed (greater than 20,000,000 bits/second) network 999 interfaces." 1000 ::= { ipMRouteMIBGroups 5 } 1002 ipMRouteMIBRouteGroup OBJECT-GROUP 1003 OBJECTS { ipMRouteRtProto, ipMRouteRtAddress, 1004 ipMRouteRtMask, ipMRouteRtType } 1005 STATUS current 1006 DESCRIPTION 1007 "A collection of objects providing information on the 1008 relationship between multicast routing information, and the 1009 IP Forwarding Table." 1010 ::= { ipMRouteMIBGroups 6 } 1012 ipMRouteMIBPktsGroup OBJECT-GROUP 1013 OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, 1014 ipMRouteOctets } 1015 STATUS current 1016 DESCRIPTION 1017 "A collection of objects to support management of packet 1018 counters for each forwarding entry." 1019 ::= { ipMRouteMIBGroups 7 } 1021 END 1022 6. Security Considerations 1024 This MIB contains readable objects whose values provide information 1025 related to multicast routing, including information on what machines are 1026 sending to which groups. There are also a number of objects that have a 1027 MAX-ACCESS clause of read-write and/or read-create, such as those which 1028 allow an administrator to configure multicast boundaries. 1030 While unauthorized access to the readable objects is relatively 1031 innocuous, unauthorized access to the write-able objects could cause a 1032 denial of service, or could cause wider distribution of packets intended 1033 only for local distribution. Hence, the support for SET operations in a 1034 non-secure environment without proper protection can have a negative 1035 effect on network operations. 1037 SNMPv1 by itself is such an insecure environment. Even if the network 1038 itself is secure (for example by using IPSec), even then, there is no 1039 control as to who on the secure network is allowed to access and SET 1040 (change/create/delete) the objects in this MIB. 1042 It is recommended that the implementers consider the security features 1043 as provided by the SNMPv3 framework. Specifically, the use of the 1044 User-based Security Model RFC 2574 [12] and the View-based Access 1045 Control Model RFC 2575 [15] is recommended. 1047 It is then a customer/user responsibility to ensure that the SNMP entity 1048 giving access to this MIB, is properly configured to give access to 1049 those objects only to those principals (users) that have legitimate 1050 rights to access them. 1052 7. Acknowledgements 1054 This MIB module was updated based on feedback from the IETF's Inter- 1055 Domain Multicast Routing (IDMR) Working Group. 1057 8. Authors' Addresses 1059 Keith McCloghrie 1060 cisco Systems, Inc. 1061 170 West Tasman Drive 1062 San Jose, CA 95134-1706 1063 Phone: +1 408 526 5260 1064 EMail: kzm@cisco.com 1066 Dino Farinacci 1067 cisco Systems, Inc. 1068 170 West Tasman Drive 1069 San Jose, CA 95134-1706 1070 Phone: +1 408 526 4696 1071 EMail: dino@cisco.com 1073 Dave Thaler 1074 Microsoft Corporation 1075 One Microsoft Way 1076 Redmond, WA 98052-6399 1077 Phone: +1 425 703 8835 1078 EMail: dthaler@microsoft.com 1080 9. References 1082 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1083 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1084 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1085 1999. 1087 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1088 Management Information for TCP/IP-based Internets", RFC 1155, STD 1089 16, Performance Systems International, Hughes LAN Systems, May 1090 1990. 1092 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1093 STD 16, Performance Systems International, Hughes LAN Systems, 1094 March 1991. 1096 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1097 RFC 1215, Performance Systems International, March 1991. 1099 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1100 and S. Waldbusser, "Structure of Management Information Version 2 1101 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1102 Braunschweig, SNMP Research, First Virtual Holdings, International 1103 Network Services, April 1999. 1105 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1106 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1107 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1108 Virtual Holdings, International Network Services, April 1999. 1110 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1111 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1112 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1113 First Virtual Holdings, International Network Services, April 1999. 1115 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1116 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1117 Systems International, Performance Systems International, MIT 1118 Laboratory for Computer Science, May 1990. 1120 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1121 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1122 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1123 International Network Services, January 1996. 1125 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1126 Mappings for Version 2 of the Simple Network Management Protocol 1127 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1128 Dover Beach Consulting, Inc., International Network Services, 1129 January 1996. 1131 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1132 Processing and Dispatching for the Simple Network Management 1133 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1134 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1136 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1137 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1138 2574, IBM T. J. Watson Research, April 1999. 1140 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1141 Operations for Version 2 of the Simple Network Management Protocol 1142 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1143 Dover Beach Consulting, Inc., International Network Services, 1144 January 1996. 1146 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1147 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1148 Systems, April 1999. 1150 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1151 Control Model (VACM) for the Simple Network Management Protocol 1152 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1153 Cisco Systems, Inc., April 1999. 1155 [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD 1156 thesis, Electrical Engineering Dept., Stanford University, December 1157 1991. 1159 [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1160 Multicast Routing Protocol", RFC 1075, November 1988. 1162 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1163 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1164 "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol 1165 Specification", RFC 2362, June 1998. 1167 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1168 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1169 Specification". Work in progress, May 1997. 1171 [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. 1173 [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast 1174 Routing", RFC 2189, September 1997. 1176 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP 1177 23, July 1998. 1179 10. Full Copyright Statement 1181 Copyright (C) The Internet Society (1999). All Rights Reserved. 1183 This document and translations of it may be copied and furnished to 1184 others, and derivative works that comment on or otherwise explain it or 1185 assist in its implmentation may be prepared, copied, published and 1186 distributed, in whole or in part, without restriction of any kind, 1187 provided that the above copyright notice and this paragraph are included 1188 on all such copies and derivative works. However, this document itself 1189 may not be modified in any way, such as by removing the copyright notice 1190 or references to the Internet Society or other Internet organizations, 1191 except as needed for the purpose of developing Internet standards in 1192 which case the procedures for copyrights defined in the Internet 1193 Standards process must be followed, or as required to translate it into 1194 languages other than English. 1196 The limited permissions granted above are perpetual and will not be 1197 revoked by the Internet Society or its successors or assigns. 1199 This document and the information contained herein is provided on an "AS 1200 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1201 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1202 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1203 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1204 FITNESS FOR A PARTICULAR PURPOSE. 1206 Table of Contents 1208 1 Abstract ........................................................ 2 1209 2 Introduction .................................................... 2 1210 3 The SNMP Management Framework ................................... 2 1211 3.1 Object Definitions ............................................ 3 1212 4 Overview ........................................................ 3 1213 5 Definitions ..................................................... 5 1214 6 Security Considerations ......................................... 27 1215 7 Acknowledgements ................................................ 27 1216 8 Authors' Addresses .............................................. 27 1217 9 References ...................................................... 28 1218 10 Full Copyright Statement ....................................... 30