idnits 2.17.1 draft-ietf-idmr-pim-mib-11.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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. 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 (10 July 2000) is 8663 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 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' -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDMR Working Group Keith McCloghrie 3 INTERNET-DRAFT Dino Farinacci 4 Expires January 2001 cisco Systems 5 Dave Thaler 6 Microsoft 7 Bill Fenner 8 AT&T Labs 9 10 July 2000 11 Protocol Independent Multicast MIB for IPv4 12 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with all 17 provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering Task 20 Force (IETF), its areas, and its working groups. Note that other groups 21 may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference material 26 or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (2000). All Rights Reserved. 38 Draft PIM MIB July 2000 40 1. Abstract 42 This memo defines a portion of the Management Information Base (MIB) for 43 use with network management protocols in the Internet community. In 44 particular, it describes managed objects used for managing the Protocol 45 Independent Multicast (PIM) protocol for IPv4. 47 2. Introduction 49 This memo defines a portion of the Management Information Base (MIB) for 50 use with network management protocols in the Internet community. In 51 particular, it describes managed objects used for managing the Protocol 52 Independent Multicast (PIM) protocol [16,17,18,19]. This MIB module is 53 applicable to IPv4 multicast routers which implement PIM. This MIB does 54 not support management of PIM for other address families, including 55 IPv6. Such management may be supported by other MIBs. 57 3. The SNMP Network Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in RFC 2271 [1]. 64 o Mechanisms for describing and naming objects and events for the 65 purpose of management. The first version of this Structure of 66 Management Information (SMI) is called SMIv1 and described in RFC 67 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 68 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 70 o Message protocols for transferring management information. The 71 first version of the SNMP message protocol is called SNMPv1 and 72 described in RFC 1157 [8]. A second version of the SNMP message 73 protocol, which is not an Internet standards track protocol, is 74 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 75 The third version of the message protocol is called SNMPv3 and 76 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 78 o Protocol operations for accessing management information. The first 79 set of protocol operations and associated PDU formats is described 80 in RFC 1157 [8]. A second set of protocol operations and associated 81 PDU formats is described in RFC 1905 [13]. 83 Draft PIM MIB July 2000 85 o A set of fundamental applications described in RFC 2573 [14] and 86 the view-based access control mechanism described in RFC 2575 [15]. 88 Managed objects are accessed via a virtual information store, termed the 89 Management Information Base or MIB. Objects in the MIB are defined 90 using the mechanisms defined in the SMI. 92 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 93 conforming to the SMIv1 can be produced through the appropriate 94 translations. The resulting translated MIB must be semantically 95 equivalent, except where objects or events are omitted because no 96 translation is possible (use of Counter64). Some machine readable 97 information in SMIv2 will be converted into textual descriptions in 98 SMIv1 during the translation process. However, this loss of machine 99 readable information is not considered to change the semantics of the 100 MIB. 102 4. Overview 104 This MIB module contains one scalar and eight tables. Some of the 105 objects in these tables are deprecated. This MIB contains deprecated 106 objects since they are necessary for managing PIMv1 routers, but PIMv1 107 itself is obsoleted by PIMv2 [18,19]. 109 The tables contained in this MIB are: 111 (1) The PIM Interface Table contains one row for each of the router's 112 PIM interfaces. 114 (2) The PIM Neighbor Table contains one row for each of the router's 115 PIM neighbors. 117 (3) The PIM IP Multicast Route Table contains one row for each 118 multicast routing entry whose incoming interface is running PIM. 120 (4) The PIM Next Hop Table which contains one row for each outgoing 121 interface list entry in the multicast routing table whose 122 interface is running PIM, and whose state is pruned. 124 (5) The (deprecated) PIM RP Table contains the PIM (version 1) 125 information for IP multicast groups which is common to all RPs of 126 a group. 128 Draft PIM MIB July 2000 130 (6) The PIM RP-Set Table contains the PIM (version 2) information for 131 sets of candidate Rendezvous Points (RPs) for IP multicast group 132 addresses with particular address prefixes. 134 (7) The PIM Candidate-RP Table contains the IP multicast groups for 135 which the local router is to advertise itself as a Candidate-RP. 136 If this table is empty, then the local router advertises itself 137 as a Candidate-RP for all groups. 139 (8) The PIM Component Table contains one row for each of the PIM 140 domains to which the router is connected. 142 Draft PIM MIB July 2000 144 5. Definitions 146 PIM-MIB DEFINITIONS ::= BEGIN 148 IMPORTS 149 MODULE-IDENTITY, OBJECT-TYPE, experimental, 150 NOTIFICATION-TYPE, 151 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 152 RowStatus, TruthValue FROM SNMPv2-TC 153 MODULE-COMPLIANCE, OBJECT-GROUP, 154 NOTIFICATION-GROUP FROM SNMPv2-CONF 155 ipMRouteGroup, ipMRouteSource, 156 ipMRouteSourceMask, ipMRouteNextHopGroup, 157 ipMRouteNextHopSource, ipMRouteNextHopSourceMask, 158 ipMRouteNextHopIfIndex, 159 ipMRouteNextHopAddress FROM IPMROUTE-STD-MIB 160 InterfaceIndex FROM IF-MIB; 162 pimMIB MODULE-IDENTITY 163 LAST-UPDATED "200007101200Z" -- July 10, 2000 164 ORGANIZATION "IETF IDMR Working Group." 165 CONTACT-INFO 166 " Dave Thaler 167 Microsoft Corporation 168 One Microsoft Way 169 Redmond, WA 98052-6399 170 US 172 Phone: +1 425 703 8835 173 EMail: dthaler@dthaler.microsoft.com" 174 DESCRIPTION 175 "The MIB module for management of PIM routers." 176 REVISION "200007071200Z" -- July 10, 2000 177 DESCRIPTION 178 "Initial version, published as RFC xxxx (to be filled in by 179 RFC-Editor)." 180 ::= { experimental 61 } 182 pimMIBObjects OBJECT IDENTIFIER ::= { pimMIB 1 } 184 pimTraps OBJECT IDENTIFIER ::= { pimMIBObjects 0 } 186 pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 } 188 pimJoinPruneInterval OBJECT-TYPE 189 Draft PIM MIB July 2000 191 SYNTAX Integer32 192 UNITS "seconds" 193 MAX-ACCESS read-write 194 STATUS current 195 DESCRIPTION 196 "The default interval at which periodic PIM-SM Join/Prune 197 messages are to be sent." 198 ::= { pim 1 } 200 Draft PIM MIB July 2000 202 -- The PIM Interface Table 204 pimInterfaceTable OBJECT-TYPE 205 SYNTAX SEQUENCE OF PimInterfaceEntry 206 MAX-ACCESS not-accessible 207 STATUS current 208 DESCRIPTION 209 "The (conceptual) table listing the router's PIM interfaces. 210 IGMP and PIM are enabled on all interfaces listed in this 211 table." 212 ::= { pim 2 } 214 pimInterfaceEntry OBJECT-TYPE 215 SYNTAX PimInterfaceEntry 216 MAX-ACCESS not-accessible 217 STATUS current 218 DESCRIPTION 219 "An entry (conceptual row) in the pimInterfaceTable." 220 INDEX { pimInterfaceIfIndex } 221 ::= { pimInterfaceTable 1 } 223 PimInterfaceEntry ::= SEQUENCE { 224 pimInterfaceIfIndex InterfaceIndex, 225 pimInterfaceAddress IpAddress, 226 pimInterfaceNetMask IpAddress, 227 pimInterfaceMode INTEGER, 228 pimInterfaceDR IpAddress, 229 pimInterfaceHelloInterval Integer32, 230 pimInterfaceStatus RowStatus, 231 pimInterfaceJoinPruneInterval Integer32, 232 pimInterfaceCBSRPreference Integer32 233 } 235 pimInterfaceIfIndex OBJECT-TYPE 236 SYNTAX InterfaceIndex 237 MAX-ACCESS not-accessible 238 STATUS current 239 DESCRIPTION 240 "The ifIndex value of this PIM interface." 241 ::= { pimInterfaceEntry 1 } 243 pimInterfaceAddress OBJECT-TYPE 244 SYNTAX IpAddress 245 MAX-ACCESS read-only 246 STATUS current 248 Draft PIM MIB July 2000 250 DESCRIPTION 251 "The IP address of the PIM interface." 252 ::= { pimInterfaceEntry 2 } 254 pimInterfaceNetMask OBJECT-TYPE 255 SYNTAX IpAddress 256 MAX-ACCESS read-only 257 STATUS current 258 DESCRIPTION 259 "The network mask for the IP address of the PIM interface." 260 ::= { pimInterfaceEntry 3 } 262 pimInterfaceMode OBJECT-TYPE 263 SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) } 264 MAX-ACCESS read-create 265 STATUS current 266 DESCRIPTION 267 "The configured mode of this PIM interface. A value of 268 sparseDense is only valid for PIMv1." 269 DEFVAL { dense } 270 ::= { pimInterfaceEntry 4 } 272 pimInterfaceDR OBJECT-TYPE 273 SYNTAX IpAddress 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The Designated Router on this PIM interface. For point-to- 278 point interfaces, this object has the value 0.0.0.0." 279 ::= { pimInterfaceEntry 5 } 281 pimInterfaceHelloInterval OBJECT-TYPE 282 SYNTAX Integer32 283 UNITS "seconds" 284 MAX-ACCESS read-create 285 STATUS current 286 DESCRIPTION 287 "The frequency at which PIM Hello messages are transmitted 288 on this interface." 289 DEFVAL { 30 } 290 ::= { pimInterfaceEntry 6 } 292 pimInterfaceStatus OBJECT-TYPE 293 SYNTAX RowStatus 294 MAX-ACCESS read-create 296 Draft PIM MIB July 2000 298 STATUS current 299 DESCRIPTION 300 "The status of this entry. Creating the entry enables PIM 301 on the interface; destroying the entry disables PIM on the 302 interface." 303 ::= { pimInterfaceEntry 7 } 305 pimInterfaceJoinPruneInterval OBJECT-TYPE 306 SYNTAX Integer32 307 UNITS "seconds" 308 MAX-ACCESS read-create 309 STATUS current 310 DESCRIPTION 311 "The frequency at which PIM Join/Prune messages are 312 transmitted on this PIM interface. The default value of 313 this object is the pimJoinPruneInterval." 314 ::= { pimInterfaceEntry 8 } 316 pimInterfaceCBSRPreference OBJECT-TYPE 317 SYNTAX Integer32 (-1..255) 318 MAX-ACCESS read-create 319 STATUS current 320 DESCRIPTION 321 "The preference value for the local interface as a candidate 322 bootstrap router. The value of -1 is used to indicate that 323 the local interface is not a candidate BSR interface." 324 DEFVAL { 0 } 325 ::= { pimInterfaceEntry 9 } 327 -- The PIM Neighbor Table 329 pimNeighborTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF PimNeighborEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "The (conceptual) table listing the router's PIM neighbors." 335 ::= { pim 3 } 337 pimNeighborEntry OBJECT-TYPE 338 SYNTAX PimNeighborEntry 339 MAX-ACCESS not-accessible 340 STATUS current 341 DESCRIPTION 343 Draft PIM MIB July 2000 345 "An entry (conceptual row) in the pimNeighborTable." 346 INDEX { pimNeighborAddress } 347 ::= { pimNeighborTable 1 } 349 PimNeighborEntry ::= SEQUENCE { 350 pimNeighborAddress IpAddress, 351 pimNeighborIfIndex InterfaceIndex, 352 pimNeighborUpTime TimeTicks, 353 pimNeighborExpiryTime TimeTicks, 354 pimNeighborMode INTEGER 355 } 357 pimNeighborAddress OBJECT-TYPE 358 SYNTAX IpAddress 359 MAX-ACCESS not-accessible 360 STATUS current 361 DESCRIPTION 362 "The IP address of the PIM neighbor for which this entry 363 contains information." 364 ::= { pimNeighborEntry 1 } 366 pimNeighborIfIndex OBJECT-TYPE 367 SYNTAX InterfaceIndex 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The value of ifIndex for the interface used to reach this 372 PIM neighbor." 373 ::= { pimNeighborEntry 2 } 375 pimNeighborUpTime OBJECT-TYPE 376 SYNTAX TimeTicks 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "The time since this PIM neighbor (last) became a neighbor 381 of the local router." 382 ::= { pimNeighborEntry 3 } 384 pimNeighborExpiryTime OBJECT-TYPE 385 SYNTAX TimeTicks 386 MAX-ACCESS read-only 387 STATUS current 388 DESCRIPTION 389 "The minimum time remaining before this PIM neighbor will be 391 Draft PIM MIB July 2000 393 aged out." 394 ::= { pimNeighborEntry 4 } 396 pimNeighborMode OBJECT-TYPE 397 SYNTAX INTEGER { dense(1), sparse(2) } 398 MAX-ACCESS read-only 399 STATUS deprecated 400 DESCRIPTION 401 "The active PIM mode of this neighbor. This object is 402 deprecated for PIMv2 routers since all neighbors on the 403 interface must be either dense or sparse as determined by 404 the protocol running on the interface." 405 ::= { pimNeighborEntry 5 } 407 -- 408 -- The PIM IP Multicast Route Table 409 -- 411 pimIpMRouteTable OBJECT-TYPE 412 SYNTAX SEQUENCE OF PimIpMRouteEntry 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "The (conceptual) table listing PIM-specific information on 417 a subset of the rows of the ipMRouteTable defined in the IP 418 Multicast MIB." 419 ::= { pim 4 } 421 pimIpMRouteEntry OBJECT-TYPE 422 SYNTAX PimIpMRouteEntry 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "An entry (conceptual row) in the pimIpMRouteTable. There 427 is one entry per entry in the ipMRouteTable whose incoming 428 interface is running PIM." 429 INDEX { ipMRouteGroup, ipMRouteSource, ipMRouteSourceMask } 430 ::= { pimIpMRouteTable 1 } 432 PimIpMRouteEntry ::= SEQUENCE { 433 pimIpMRouteUpstreamAssertTimer TimeTicks, 434 pimIpMRouteAssertMetric Integer32, 435 pimIpMRouteAssertMetricPref Integer32, 436 pimIpMRouteAssertRPTBit TruthValue, 437 pimIpMRouteFlags BITS 439 Draft PIM MIB July 2000 441 } 443 pimIpMRouteUpstreamAssertTimer OBJECT-TYPE 444 SYNTAX TimeTicks 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The time remaining before the router changes its upstream 449 neighbor back to its RPF neighbor. This timer is called the 450 Assert timer in the PIM Sparse and Dense mode specification. 451 A value of 0 indicates that no Assert has changed the 452 upstream neighbor away from the RPF neighbor." 453 ::= { pimIpMRouteEntry 1 } 455 pimIpMRouteAssertMetric OBJECT-TYPE 456 SYNTAX Integer32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The metric advertised by the assert winner on the upstream 461 interface, or 0 if no such assert is in received." 462 ::= { pimIpMRouteEntry 2 } 464 pimIpMRouteAssertMetricPref OBJECT-TYPE 465 SYNTAX Integer32 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The preference advertised by the assert winner on the 470 upstream interface, or 0 if no such assert is in effect." 471 ::= { pimIpMRouteEntry 3 } 473 pimIpMRouteAssertRPTBit OBJECT-TYPE 474 SYNTAX TruthValue 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "The value of the RPT-bit advertised by the assert winner on 479 the upstream interface, or false if no such assert is in 480 effect." 481 ::= { pimIpMRouteEntry 4 } 483 pimIpMRouteFlags OBJECT-TYPE 484 SYNTAX BITS { 485 rpt(0), 487 Draft PIM MIB July 2000 489 spt(1) 490 } 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "This object describes PIM-specific flags related to a 495 multicast state entry. See the PIM Sparse Mode 496 specification for the meaning of the RPT and SPT bits." 497 ::= { pimIpMRouteEntry 5 } 499 -- 500 -- The PIM Next Hop Table 501 -- 503 pimIpMRouteNextHopTable OBJECT-TYPE 504 SYNTAX SEQUENCE OF PimIpMRouteNextHopEntry 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "The (conceptual) table listing PIM-specific information on 509 a subset of the rows of the ipMRouteNextHopTable defined in 510 the IP Multicast MIB." 511 ::= { pim 7 } 513 pimIpMRouteNextHopEntry OBJECT-TYPE 514 SYNTAX PimIpMRouteNextHopEntry 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "An entry (conceptual row) in the pimIpMRouteNextHopTable. 519 There is one entry per entry in the ipMRouteNextHopTable 520 whose interface is running PIM and whose 521 ipMRouteNextHopState is pruned(1)." 522 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 523 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 524 ipMRouteNextHopAddress } 525 ::= { pimIpMRouteNextHopTable 1 } 527 PimIpMRouteNextHopEntry ::= SEQUENCE { 528 pimIpMRouteNextHopPruneReason INTEGER 529 } 531 pimIpMRouteNextHopPruneReason OBJECT-TYPE 532 SYNTAX INTEGER { 533 other (1), 535 Draft PIM MIB July 2000 537 prune (2), 538 assert (3) 539 } 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "This object indicates why the downstream interface was 544 pruned, whether in response to a PIM prune message or due to 545 PIM Assert processing." 546 ::= { pimIpMRouteNextHopEntry 2 } 548 -- The PIM RP Table 550 pimRPTable OBJECT-TYPE 551 SYNTAX SEQUENCE OF PimRPEntry 552 MAX-ACCESS not-accessible 553 STATUS deprecated 554 DESCRIPTION 555 "The (conceptual) table listing PIM version 1 information 556 for the Rendezvous Points (RPs) for IP multicast groups. 557 This table is deprecated since its function is replaced by 558 the pimRPSetTable for PIM version 2." 559 ::= { pim 5 } 561 pimRPEntry OBJECT-TYPE 562 SYNTAX PimRPEntry 563 MAX-ACCESS not-accessible 564 STATUS deprecated 565 DESCRIPTION 566 "An entry (conceptual row) in the pimRPTable. There is one 567 entry per RP address for each IP multicast group." 568 INDEX { pimRPGroupAddress, pimRPAddress } 569 ::= { pimRPTable 1 } 571 Draft PIM MIB July 2000 573 PimRPEntry ::= SEQUENCE { 574 pimRPGroupAddress IpAddress, 575 pimRPAddress IpAddress, 576 pimRPState INTEGER, 577 pimRPStateTimer TimeTicks, 578 pimRPLastChange TimeTicks, 579 pimRPRowStatus RowStatus 580 } 582 pimRPGroupAddress OBJECT-TYPE 583 SYNTAX IpAddress 584 MAX-ACCESS not-accessible 585 STATUS deprecated 586 DESCRIPTION 587 "The IP multicast group address for which this entry 588 contains information about an RP." 589 ::= { pimRPEntry 1 } 591 pimRPAddress OBJECT-TYPE 592 SYNTAX IpAddress 593 MAX-ACCESS not-accessible 594 STATUS deprecated 595 DESCRIPTION 596 "The unicast address of the RP." 597 ::= { pimRPEntry 2 } 599 pimRPState OBJECT-TYPE 600 SYNTAX INTEGER { up(1), down(2) } 601 MAX-ACCESS read-only 602 STATUS deprecated 603 DESCRIPTION 604 "The state of the RP." 605 ::= { pimRPEntry 3 } 607 pimRPStateTimer OBJECT-TYPE 608 SYNTAX TimeTicks 609 MAX-ACCESS read-only 610 STATUS deprecated 611 DESCRIPTION 612 "The minimum time remaining before the next state change. 613 When pimRPState is up, this is the minimum time which must 614 expire until it can be declared down. When pimRPState is 615 down, this is the time until it will be declared up (in 616 order to retry)." 617 ::= { pimRPEntry 4 } 619 Draft PIM MIB July 2000 621 pimRPLastChange OBJECT-TYPE 622 SYNTAX TimeTicks 623 MAX-ACCESS read-only 624 STATUS deprecated 625 DESCRIPTION 626 "The value of sysUpTime at the time when the corresponding 627 instance of pimRPState last changed its value." 628 ::= { pimRPEntry 5 } 630 pimRPRowStatus OBJECT-TYPE 631 SYNTAX RowStatus 632 MAX-ACCESS read-create 633 STATUS deprecated 634 DESCRIPTION 635 "The status of this row, by which new entries may be 636 created, or old entries deleted from this table." 637 ::= { pimRPEntry 6 } 639 -- The PIM RP-Set Table 641 pimRPSetTable OBJECT-TYPE 642 SYNTAX SEQUENCE OF PimRPSetEntry 643 MAX-ACCESS not-accessible 644 STATUS current 645 DESCRIPTION 646 "The (conceptual) table listing PIM information for 647 candidate Rendezvous Points (RPs) for IP multicast groups. 648 When the local router is the BSR, this information is 649 obtained from received Candidate-RP-Advertisements. When 650 the local router is not the BSR, this information is 651 obtained from received RP-Set messages." 652 ::= { pim 6 } 654 pimRPSetEntry OBJECT-TYPE 655 SYNTAX PimRPSetEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "An entry (conceptual row) in the pimRPSetTable." 660 INDEX { pimRPSetComponent, pimRPSetGroupAddress, 661 pimRPSetGroupMask, pimRPSetAddress } 662 ::= { pimRPSetTable 1 } 664 PimRPSetEntry ::= SEQUENCE { 665 Draft PIM MIB July 2000 667 pimRPSetGroupAddress IpAddress, 668 pimRPSetGroupMask IpAddress, 669 pimRPSetAddress IpAddress, 670 pimRPSetHoldTime Integer32, 671 pimRPSetExpiryTime TimeTicks, 672 pimRPSetComponent Integer32 673 } 675 pimRPSetGroupAddress OBJECT-TYPE 676 SYNTAX IpAddress 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "The IP multicast group address which, when combined with 681 pimRPSetGroupMask, gives the group prefix for which this 682 entry contains information about the Candidate-RP." 683 ::= { pimRPSetEntry 1 } 685 pimRPSetGroupMask OBJECT-TYPE 686 SYNTAX IpAddress 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The multicast group address mask which, when combined with 691 pimRPSetGroupAddress, gives the group prefix for which this 692 entry contains information about the Candidate-RP." 693 ::= { pimRPSetEntry 2 } 695 pimRPSetAddress OBJECT-TYPE 696 SYNTAX IpAddress 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The IP address of the Candidate-RP." 701 ::= { pimRPSetEntry 3 } 703 pimRPSetHoldTime OBJECT-TYPE 704 SYNTAX Integer32 (0..255) 705 UNITS "seconds" 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "The holdtime of a Candidate-RP. If the local router is not 710 the BSR, this value is 0." 711 ::= { pimRPSetEntry 4 } 713 Draft PIM MIB July 2000 715 pimRPSetExpiryTime OBJECT-TYPE 716 SYNTAX TimeTicks 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The minimum time remaining before the Candidate-RP will be 721 declared down. If the local router is not the BSR, this 722 value is 0." 723 ::= { pimRPSetEntry 5 } 725 pimRPSetComponent OBJECT-TYPE 726 SYNTAX Integer32 (1..255) 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 " A number uniquely identifying the component. Each 731 protocol instance connected to a separate domain should have 732 a different index value." 733 ::= { pimRPSetEntry 6 } 735 -- 736 -- Note: { pim 8 } through { pim 10 } were used in older versions 737 -- of this MIB. Since some earlier versions of this MIB have been 738 -- widely-deployed, these values must not be used in the future, 739 -- as long the MIB is rooted under { experimental 61 }. 740 -- 741 Draft PIM MIB July 2000 743 -- The PIM Candidate-RP Table 745 pimCandidateRPTable OBJECT-TYPE 746 SYNTAX SEQUENCE OF PimCandidateRPEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "The (conceptual) table listing the IP multicast groups for 751 which the local router is to advertise itself as a 752 Candidate-RP when the value of pimComponentCRPHoldTime is 753 non-zero. If this table is empty, then the local router 754 will advertise itself as a Candidate-RP for all groups 755 (providing the value of pimComponentCRPHoldTime is non- 756 zero)." 757 ::= { pim 11 } 759 pimCandidateRPEntry OBJECT-TYPE 760 SYNTAX PimCandidateRPEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "An entry (conceptual row) in the pimCandidateRPTable." 765 INDEX { pimCandidateRPGroupAddress, 766 pimCandidateRPGroupMask } 767 ::= { pimCandidateRPTable 1 } 769 PimCandidateRPEntry ::= SEQUENCE { 770 pimCandidateRPGroupAddress IpAddress, 771 pimCandidateRPGroupMask IpAddress, 772 pimCandidateRPAddress IpAddress, 773 pimCandidateRPRowStatus RowStatus 774 } 776 pimCandidateRPGroupAddress OBJECT-TYPE 777 SYNTAX IpAddress 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "The IP multicast group address which, when combined with 782 pimCandidateRPGroupMask, identifies a group prefix for which 783 the local router will advertise itself as a Candidate-RP." 784 ::= { pimCandidateRPEntry 1 } 786 pimCandidateRPGroupMask OBJECT-TYPE 787 SYNTAX IpAddress 789 Draft PIM MIB July 2000 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "The multicast group address mask which, when combined with 795 pimCandidateRPGroupMask, identifies a group prefix for which 796 the local router will advertise itself as a Candidate-RP." 797 ::= { pimCandidateRPEntry 2 } 799 pimCandidateRPAddress OBJECT-TYPE 800 SYNTAX IpAddress 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The (unicast) address of the interface which will be 805 advertised as a Candidate-RP." 806 ::= { pimCandidateRPEntry 3 } 808 pimCandidateRPRowStatus OBJECT-TYPE 809 SYNTAX RowStatus 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "The status of this row, by which new entries may be 814 created, or old entries deleted from this table." 815 ::= { pimCandidateRPEntry 4 } 817 -- The PIM Component Table 819 pimComponentTable OBJECT-TYPE 820 SYNTAX SEQUENCE OF PimComponentEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "The (conceptual) table containing objects specific to a PIM 825 domain. One row exists for each domain to which the router 826 is connected. A PIM-SM domain is defined as an area of the 827 network over which Bootstrap messages are forwarded. 828 Typically, a PIM-SM router will be a member of exactly one 829 domain. This table also supports, however, routers which 830 may form a border between two PIM-SM domains and do not 831 forward Bootstrap messages between them." 832 ::= { pim 12 } 834 pimComponentEntry OBJECT-TYPE 835 SYNTAX PimComponentEntry 837 Draft PIM MIB July 2000 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "An entry (conceptual row) in the pimComponentTable." 843 INDEX { pimComponentIndex } 844 ::= { pimComponentTable 1 } 846 PimComponentEntry ::= SEQUENCE { 847 pimComponentIndex Integer32, 848 pimComponentBSRAddress IpAddress, 849 pimComponentBSRExpiryTime TimeTicks, 850 pimComponentCRPHoldTime Integer32, 851 pimComponentStatus RowStatus 852 } 854 pimComponentIndex OBJECT-TYPE 855 SYNTAX Integer32 (1..255) 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "A number uniquely identifying the component. Each protocol 860 instance connected to a separate domain should have a 861 different index value. Routers that only support membership 862 in a single PIM-SM domain should use a pimComponentIndex 863 value of 1." 864 ::= { pimComponentEntry 1 } 866 pimComponentBSRAddress OBJECT-TYPE 867 SYNTAX IpAddress 868 MAX-ACCESS read-only 869 STATUS current 870 DESCRIPTION 871 "The IP address of the bootstrap router (BSR) for the local 872 PIM region." 873 ::= { pimComponentEntry 2 } 875 pimComponentBSRExpiryTime OBJECT-TYPE 876 SYNTAX TimeTicks 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "The minimum time remaining before the bootstrap router in 881 the local domain will be declared down. For candidate BSRs, 882 this is the time until the component sends an RP-Set 883 message. For other routers, this is the time until it may 885 Draft PIM MIB July 2000 887 accept an RP-Set message from a lower candidate BSR." 888 ::= { pimComponentEntry 3 } 890 pimComponentCRPHoldTime OBJECT-TYPE 891 SYNTAX Integer32 (0..255) 892 UNITS "seconds" 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "The holdtime of the component when it is a candidate RP in 897 the local domain. The value of 0 is used to indicate that 898 the local system is not a Candidate-RP." 899 DEFVAL { 0 } 900 ::= { pimComponentEntry 4 } 902 pimComponentStatus OBJECT-TYPE 903 SYNTAX RowStatus 904 MAX-ACCESS read-create 905 STATUS current 906 DESCRIPTION 907 "The status of this entry. Creating the entry creates 908 another protocol instance; destroying the entry disables a 909 protocol instance." 910 ::= { pimComponentEntry 5 } 912 -- PIM Traps 914 pimNeighborLoss NOTIFICATION-TYPE 915 OBJECTS { 916 pimNeighborIfIndex 917 } 918 STATUS current 919 DESCRIPTION 920 "A pimNeighborLoss trap signifies the loss of an adjacency 921 with a neighbor. This trap should be generated when the 922 neighbor timer expires, and the router has no other 923 neighbors on the same interface with a lower IP address than 924 itself." 925 ::= { pimTraps 1 } 927 Draft PIM MIB July 2000 929 -- conformance information 931 pimMIBConformance OBJECT IDENTIFIER ::= { pimMIB 2 } 932 pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } 933 pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } 935 -- compliance statements 937 pimV1MIBCompliance MODULE-COMPLIANCE 938 STATUS deprecated 939 DESCRIPTION 940 "The compliance statement for routers running PIMv1 and 941 implementing the PIM MIB." 942 MODULE -- this module 943 MANDATORY-GROUPS { pimV1MIBGroup } 945 ::= { pimMIBCompliances 1 } 947 pimSparseV2MIBCompliance MODULE-COMPLIANCE 948 STATUS current 949 DESCRIPTION 950 "The compliance statement for routers running PIM Sparse 951 Mode and implementing the PIM MIB." 952 MODULE -- this module 953 MANDATORY-GROUPS { pimV2MIBGroup } 955 GROUP pimV2CandidateRPMIBGroup 956 DESCRIPTION 957 "This group is mandatory if the router is capable of being a 958 Candidate RP." 960 OBJECT pimInterfaceStatus 961 MIN-ACCESS read-only 962 DESCRIPTION 963 "Write access is not required." 965 ::= { pimMIBCompliances 2 } 967 pimDenseV2MIBCompliance MODULE-COMPLIANCE 968 STATUS current 969 DESCRIPTION 970 "The compliance statement for routers running PIM Dense Mode 971 and implementing the PIM MIB." 972 MODULE -- this module 974 Draft PIM MIB July 2000 976 MANDATORY-GROUPS { pimDenseV2MIBGroup } 978 OBJECT pimInterfaceStatus 979 MIN-ACCESS read-only 980 DESCRIPTION 981 "Write access is not required." 983 ::= { pimMIBCompliances 3 } 985 -- units of conformance 987 pimNotificationGroup NOTIFICATION-GROUP 988 NOTIFICATIONS { pimNeighborLoss } 989 STATUS current 990 DESCRIPTION 991 "A collection of notifications for signaling important PIM 992 events." 993 ::= { pimMIBGroups 1 } 995 pimV2MIBGroup OBJECT-GROUP 996 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 997 pimNeighborUpTime, pimNeighborExpiryTime, 998 pimInterfaceAddress, pimInterfaceNetMask, 999 pimInterfaceDR, pimInterfaceHelloInterval, 1000 pimInterfaceStatus, pimInterfaceJoinPruneInterval, 1001 pimInterfaceCBSRPreference, pimInterfaceMode, 1002 pimRPSetHoldTime, pimRPSetExpiryTime, 1003 pimComponentBSRAddress, pimComponentBSRExpiryTime, 1004 pimComponentCRPHoldTime, pimComponentStatus, 1005 pimIpMRouteFlags, pimIpMRouteUpstreamAssertTimer 1006 } 1007 STATUS current 1008 DESCRIPTION 1009 "A collection of objects to support management of PIM Sparse 1010 Mode (version 2) routers." 1011 ::= { pimMIBGroups 2 } 1013 pimDenseV2MIBGroup OBJECT-GROUP 1014 OBJECTS { pimNeighborIfIndex, 1015 pimNeighborUpTime, pimNeighborExpiryTime, 1016 pimInterfaceAddress, pimInterfaceNetMask, 1017 pimInterfaceDR, pimInterfaceHelloInterval, 1018 pimInterfaceStatus, pimInterfaceMode 1019 } 1021 Draft PIM MIB July 2000 1023 STATUS current 1024 DESCRIPTION 1025 "A collection of objects to support management of PIM Dense 1026 Mode (version 2) routers." 1027 ::= { pimMIBGroups 5 } 1029 pimV2CandidateRPMIBGroup OBJECT-GROUP 1030 OBJECTS { pimCandidateRPAddress, 1031 pimCandidateRPRowStatus 1032 } 1033 STATUS current 1034 DESCRIPTION 1035 "A collection of objects to support configuration of which 1036 groups a router is to advertise itself as a Candidate-RP." 1037 ::= { pimMIBGroups 3 } 1039 pimV1MIBGroup OBJECT-GROUP 1040 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 1041 pimNeighborUpTime, pimNeighborExpiryTime, 1042 pimNeighborMode, 1043 pimInterfaceAddress, pimInterfaceNetMask, 1044 pimInterfaceJoinPruneInterval, pimInterfaceStatus, 1045 pimInterfaceMode, pimInterfaceDR, 1046 pimInterfaceHelloInterval, 1047 pimRPState, pimRPStateTimer, 1048 pimRPLastChange, pimRPRowStatus 1049 } 1050 STATUS deprecated 1051 DESCRIPTION 1052 "A collection of objects to support management of PIM 1053 (version 1) routers." 1054 ::= { pimMIBGroups 4 } 1056 pimNextHopGroup OBJECT-GROUP 1057 OBJECTS { pimIpMRouteNextHopPruneReason } 1058 STATUS current 1059 DESCRIPTION 1060 "A collection of optional objects to provide per-next hop 1061 information for diagnostic purposes. Supporting this group 1062 may add a large number of instances to a tree walk, but the 1063 information in this group can be extremely useful in 1064 tracking down multicast connectivity problems." 1065 ::= { pimMIBGroups 6 } 1067 pimAssertGroup OBJECT-GROUP 1068 Draft PIM MIB July 2000 1070 OBJECTS { pimIpMRouteAssertMetric, pimIpMRouteAssertMetricPref, 1071 pimIpMRouteAssertRPTBit } 1072 STATUS current 1073 DESCRIPTION 1074 "A collection of optional objects to provide extra 1075 information about the assert election process. There is no 1076 protocol reason to keep such information, but some 1077 implementations may already keep this information and make 1078 it available. These objects can also be very useful in 1079 debugging connectivity or duplicate packet problems, 1080 especially if the assert winner does not support the PIM and 1081 IP Multicast MIBs." 1082 ::= { pimMIBGroups 7 } 1084 END 1085 Draft PIM MIB July 2000 1087 6. Security Considerations 1089 This MIB contains readable objects whose values provide information 1090 related to multicast routing, including information on the network 1091 topology. There are also a number of objects that have a MAX-ACCESS 1092 clause of read-write and/or read-create, which allow an administrator to 1093 configure PIM in the router. 1095 While unauthorized access to the readable objects is relatively 1096 innocuous, unauthorized access to the write-able objects could cause a 1097 denial of service. Hence, the support for SET operations in a non- 1098 secure environment without proper protection can have a negative effect 1099 on network operations. 1101 SNMPv1 by itself is such an insecure environment. Even if the network 1102 itself is secure (for example by using IPSec), even then, there is no 1103 control as to who on the secure network is allowed to access and SET 1104 (change/create/delete) the objects in this MIB. 1106 It is recommended that the implementers consider the security features 1107 as provided by the SNMPv3 framework. Specifically, the use of the User- 1108 based Security Model RFC 2274 [12] and the View-based Access Control 1109 Model RFC 2275 [15] is recommended. 1111 It is then a customer/user responsibility to ensure that the SNMP entity 1112 giving access to this MIB, is properly configured to give access to 1113 those objects only to those principals (users) that have legitimate 1114 rights to access them. 1116 7. Intellectual Property Notice 1118 The IETF takes no position regarding the validity or scope of any 1119 intellectual property or other rights that might be claimed to pertain 1120 to the implementation or use of the technology described in this 1121 document or the extent to which any license under such rights might or 1122 might not be available; neither does it represent that it has made any 1123 effort to identify any such rights. Information on the IETF's 1124 procedures with respect to rights in standards-track and standards- 1125 related documentation can be found in BCP-11. Copies of claims of 1126 rights made available for publication and any assurances of licenses to 1127 be made available, or the result of an attempt made to obtain a general 1128 license or permission for the use of such proprietary rights by 1129 implementers or users of this specification can be obtained from the 1130 Draft PIM MIB July 2000 1132 IETF Secretariat. 1134 The IETF invites any interested party to bring to its attention any 1135 copyrights, patents or patent applications, or other proprietary rights 1136 which may cover technology that may be required to practice this 1137 standard. Please address the information to the IETF Executive 1138 Director. 1140 8. Acknowledgements 1142 This MIB module has been updated based on feedback from the IETF's 1143 Inter-Domain Multicast Routing (IDMR) Working Group. 1145 9. Authors' Addresses 1147 Keith McCloghrie 1148 cisco Systems, Inc. 1149 170 West Tasman Drive 1150 San Jose, CA 95134-1706 1151 Phone: +1 408 526 5260 1152 EMail: kzm@cisco.com 1154 Dino Farinacci 1155 cisco Systems, Inc. 1156 170 West Tasman Drive 1157 San Jose, CA 95134-1706 1158 Phone: +1 408 526 4696 1159 EMail: dino@cisco.com 1161 Dave Thaler 1162 Microsoft Corporation 1163 One Microsoft Way 1164 Redmond, WA 98052-6399 1165 Phone: +1 425 703 8835 1166 EMail: dthaler@microsoft.com 1168 Bill Fenner 1169 AT&T Labs - Research 1170 75 Willow Rd. 1171 Menlo Park, CA 94025 1172 Phone: +1 650 330 7893 1174 Draft PIM MIB July 2000 1176 Email: fenner@research.att.com 1178 10. References 1180 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1181 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1182 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1183 1999. 1185 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1186 Management Information for TCP/IP-based Internets", RFC 1155, STD 1187 16, Performance Systems International, Hughes LAN Systems, May 1188 1990. 1190 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1191 STD 16, Performance Systems International, Hughes LAN Systems, 1192 March 1991. 1194 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1195 RFC 1215, Performance Systems International, March 1991. 1197 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1198 and S. Waldbusser, "Structure of Management Information Version 2 1199 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1200 Braunschweig, SNMP Research, First Virtual Holdings, International 1201 Network Services, April 1999. 1203 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1204 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1205 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1206 Virtual Holdings, International Network Services, April 1999. 1208 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1209 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1210 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1211 First Virtual Holdings, International Network Services, April 1999. 1213 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1214 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1215 Systems International, Performance Systems International, MIT 1216 Laboratory for Computer Science, May 1990. 1218 Draft PIM MIB July 2000 1220 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1221 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1222 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1223 International Network Services, January 1996. 1225 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1226 Mappings for Version 2 of the Simple Network Management Protocol 1227 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1228 Dover Beach Consulting, Inc., International Network Services, 1229 January 1996. 1231 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1232 Processing and Dispatching for the Simple Network Management 1233 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1234 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1236 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1237 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1238 2574, IBM T. J. Watson Research, April 1999. 1240 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1241 Operations for Version 2 of the Simple Network Management Protocol 1242 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1243 Dover Beach Consulting, Inc., International Network Services, 1244 January 1996. 1246 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1247 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1248 Systems, April 1999. 1250 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1251 Control Model (VACM) for the Simple Network Management Protocol 1252 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1253 Cisco Systems, Inc., April 1999. 1255 [16] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1256 L. Wei, "Protocol Independent Multicast (PIM): Motivation and 1257 Architecture", January 1995. 1259 [17] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1260 L. Wei, "Protocol Independent Multicast (PIM): Protocol 1261 Specification", January 1995. 1263 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1264 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1266 Draft PIM MIB July 2000 1268 "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol 1269 Specification", RFC 2362, June 1998. 1271 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1272 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1273 Specification". Work in Progress, May 1997. 1275 11. Full Copyright Statement 1277 Copyright (C) The Internet Society (2000). All Rights Reserved. 1279 This document and translations of it may be copied and furnished to 1280 others, and derivative works that comment on or otherwise explain it or 1281 assist in its implmentation may be prepared, copied, published and 1282 distributed, in whole or in part, without restriction of any kind, 1283 provided that the above copyright notice and this paragraph are included 1284 on all such copies and derivative works. However, this document itself 1285 may not be modified in any way, such as by removing the copyright notice 1286 or references to the Internet Society or other Internet organizations, 1287 except as needed for the purpose of developing Internet standards in 1288 which case the procedures for copyrights defined in the Internet 1289 Standards process must be followed, or as required to translate it into 1290 languages other than English. 1292 The limited permissions granted above are perpetual and will not be 1293 revoked by the Internet Society or its successors or assigns. 1295 This document and the information contained herein is provided on an "AS 1296 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1297 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1298 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1299 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1300 FITNESS FOR A PARTICULAR PURPOSE. 1302 Table of Contents 1304 1 Abstract ........................................................ 2 1305 2 Introduction .................................................... 2 1306 3 The SNMP Network Management Framework ........................... 2 1307 4 Overview ........................................................ 3 1308 5 Definitions ..................................................... 5 1309 6 Security Considerations ......................................... 27 1310 Draft PIM MIB July 2000 1312 7 Intellectual Property Notice .................................... 27 1313 8 Acknowledgements ................................................ 28 1314 9 Authors' Addresses .............................................. 28 1315 10 References ..................................................... 29 1316 11 Full Copyright Statement ....................................... 31