idnits 2.17.1 draft-ietf-pim-bsr-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1015. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 992. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 999. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1005. 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (April 30, 2008) is 5812 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 4601 (Obsoleted by RFC 7761) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PIM WG B. Joshi 3 Internet-Draft Infosys Technologies Ltd. 4 Expires: November 1, 2008 R. Bijlani 5 April 30, 2008 7 PIM Bootstrap Router MIB 8 draft-ietf-pim-bsr-mib-05.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on November 1, 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2008). 39 Abstract 41 This document defines a portion of the Management Information Base 42 (MIB) for use with network management protocols in the Internet 43 community. In particular, it describes managed objects used for 44 managing the Bootstrap Router (BSR) mechanism for PIM (Protocol 45 Independent Multicast). 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 55 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 56 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 57 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 58 9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 59 9.2. Informative References . . . . . . . . . . . . . . . . . . 22 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 61 Intellectual Property and Copyright Statements . . . . . . . . . . 24 63 1. Introduction 65 This memo defines a portion of the Management Information Base (MIB) 66 for use with network management protocols in the Internet community. 67 In particular, it describes managed objects used for managing the 68 Bootstrap Router (BSR) mechanism for PIM [RFC4601], [RFC5059]. 70 This document was created by moving some of the PIM BSR specific MIB 71 tables from one of the earlier version of PIM MIB [RFC5060]. 73 2. The Internet-Standard Management Framework 75 For a detailed overview of the documents that describe the current 76 Internet-Standard Management Framework, please refer to section 7 of 77 RFC 3410[RFC3410]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. MIB objects are generally 81 accessed through the Simple Network Management Protocol (SNMP). 82 Objects in the MIB are defined using the mechanisms defined in the 83 Structure of Management Information (SMI). This memo specifies a MIB 84 module that is compliant to the SMIv2, which is described in STD 58, 85 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 86 [RFC2580]. 88 3. Conventions 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC 2119 [RFC2119]. 94 4. Overview 96 This MIB module contains four tables. The tables are: 98 1. The Candidate-RP Table, which contains one row for each multicast 99 group address prefix for which the local router is configured to 100 advertise itself as a Candidate-RP. This table exists on routers 101 that are configured as Candidate-RP. 103 2. The Elected BSR RP-Set Table, which contains one row for each 104 Group-to-RP mapping that was received in C-RP advertisements. 105 This table exists on a router that is an elected BSR. 107 3. The Candidate-BSR Table, which contains one row for each 108 Candidate-BSR configuration for the local router. This table 109 exists on routers that are configured as Candidate-BSR. 111 4. The Elected BSR Table, which contains one row for each elected 112 BSR. This table exists on a router that is an elected BSR. 114 This MIB module uses textual conventions defined in the INET-ADDRESS- 115 MIB [RFC4001]. 117 5. Definitions 119 PIM-BSR-MIB DEFINITIONS ::= BEGIN 121 IMPORTS 122 MODULE-IDENTITY, OBJECT-TYPE, 123 NOTIFICATION-TYPE, 124 mib-2, Unsigned32, TimeTicks FROM SNMPv2-SMI 125 RowStatus, TruthValue, 126 StorageType FROM SNMPv2-TC 127 MODULE-COMPLIANCE, OBJECT-GROUP, 128 NOTIFICATION-GROUP FROM SNMPv2-CONF 129 InetAddressType, 130 InetAddressPrefixLength, 131 InetAddress, 132 InetZoneIndex FROM INET-ADDRESS-MIB; 134 pimBsrMIB MODULE-IDENTITY 135 LAST-UPDATED "200804300000Z" -- 30 April 2008 136 ORGANIZATION 137 "IETF Protocol Independent Multicast (PIM) Working Group" 138 CONTACT-INFO 139 "Email: pim@ietf.org 140 WG charter: 141 http://www.ietf.org/html.charters/pim-charter.html" 142 DESCRIPTION 143 "The MIB module for management of the Bootstrap Router 144 (BSR) mechanism for PIM routers. 146 Copyright (C) The IETF Trust (2008). This version 147 of this MIB module is part of RFC yyyy; see the RFC 148 itself for full legal notices." 149 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 150 REVISION "200804300000Z" -- 30 April 2008 151 DESCRIPTION "Initial version, published as RFC yyyy." 152 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 153 ::= { mib-2 XXX } 154 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 156 -- 157 -- Top-level structure 158 -- 160 pimBsrNotifications OBJECT IDENTIFIER ::= { pimBsrMIB 0 } 161 pimBsrObjects OBJECT IDENTIFIER ::= { pimBsrMIB 1 } 163 -- 164 -- Conformance Information 165 -- 167 pimBsrConformance OBJECT IDENTIFIER ::= { pimBsrMIB 2 } 168 pimBsrCompliances OBJECT IDENTIFIER ::= { pimBsrConformance 1 } 169 pimBsrGroups OBJECT IDENTIFIER ::= { pimBsrConformance 2 } 171 -- 172 -- The BSR Candidate-RP Table 173 -- 175 pimBsrCandidateRPTable OBJECT-TYPE 176 SYNTAX SEQUENCE OF PimBsrCandidateRPEntry 177 MAX-ACCESS not-accessible 178 STATUS current 179 DESCRIPTION 180 "The (conceptual) table listing the IP multicast group 181 prefixes for which the local router is to advertise 182 itself as a Candidate-RP." 183 ::= { pimBsrObjects 1 } 185 pimBsrCandidateRPEntry OBJECT-TYPE 186 SYNTAX PimBsrCandidateRPEntry 187 MAX-ACCESS not-accessible 188 STATUS current 189 DESCRIPTION 190 "An entry (conceptual row) in the 191 pimBsrCandidateRPTable." 192 INDEX { pimBsrCandidateRPAddressType, 193 pimBsrCandidateRPAddress, 194 pimBsrCandidateRPGroupAddress, 195 pimBsrCandidateRPGroupPrefixLength } 196 ::= { pimBsrCandidateRPTable 1 } 198 PimBsrCandidateRPEntry ::= SEQUENCE { 199 pimBsrCandidateRPAddressType InetAddressType, 200 pimBsrCandidateRPAddress InetAddress, 201 pimBsrCandidateRPGroupAddress InetAddress, 202 pimBsrCandidateRPGroupPrefixLength InetAddressPrefixLength, 203 pimBsrCandidateRPBidir TruthValue, 204 pimBsrCandidateRPAdvTimer TimeTicks, 205 pimBsrCandidateRPPriority Unsigned32, 206 pimBsrCandidateRPAdvInterval Unsigned32, 207 pimBsrCandidateRPHoldtime Unsigned32, 208 pimBsrCandidateRPStatus RowStatus, 209 pimBsrCandidateRPStorageType StorageType 210 } 212 pimBsrCandidateRPAddressType OBJECT-TYPE 213 SYNTAX InetAddressType 214 MAX-ACCESS not-accessible 215 STATUS current 216 DESCRIPTION 217 "The Inet address type of the Candidate-RP." 218 ::= { pimBsrCandidateRPEntry 1 } 220 pimBsrCandidateRPAddress OBJECT-TYPE 221 SYNTAX InetAddress (SIZE (4|8|16|20)) 222 MAX-ACCESS not-accessible 223 STATUS current 224 DESCRIPTION 225 "The (unicast) address that will be advertised as a 226 Candidate-RP. The InetAddressType is given by the 227 pimBsrCandidateRPAddressType object." 228 ::= { pimBsrCandidateRPEntry 2 } 230 pimBsrCandidateRPGroupAddress OBJECT-TYPE 231 SYNTAX InetAddress (SIZE (4|8|16|20)) 232 MAX-ACCESS not-accessible 233 STATUS current 234 DESCRIPTION 235 "The IP multicast group address that, when combined with 236 the corresponding value of 237 pimBsrCandidateRPGroupPrefixLength, identifies a group 238 prefix for which the local router will advertise itself 239 as a Candidate-RP. The InetAddressType is given by the 240 pimBsrCandidateRPAddressType object. 242 This address object is only significant up to 243 pimBsrCandidateRPGroupPrefixLength bits. The 244 remainder of the address bits are zero. This is 245 especially important for this field, which is part of 246 the index of this entry. Any non-zero bits would 247 signify an entirely different entry." 248 ::= { pimBsrCandidateRPEntry 3 } 250 pimBsrCandidateRPGroupPrefixLength OBJECT-TYPE 251 SYNTAX InetAddressPrefixLength (4..128) 252 MAX-ACCESS not-accessible 253 STATUS current 254 DESCRIPTION 255 "The multicast group address mask that, when combined 256 with the corresponding value of 257 pimBsrCandidateRPGroupAddress, identifies a group prefix 258 for which the local router will advertise itself as a 259 Candidate-RP. The InetAddressType is given by the 260 pimBsrCandidateRPAddressType object." 261 ::= { pimBsrCandidateRPEntry 4 } 263 pimBsrCandidateRPBidir OBJECT-TYPE 264 SYNTAX TruthValue 265 MAX-ACCESS read-create 266 STATUS current 267 DESCRIPTION 268 "If this object is set to TRUE, this group range is 269 advertised with this RP as a BIDIR-PIM group range. If 270 it is set to FALSE, it is advertised as a PIM-SM group 271 range." 272 DEFVAL { false } 273 ::= { pimBsrCandidateRPEntry 5 } 275 pimBsrCandidateRPAdvTimer OBJECT-TYPE 276 SYNTAX TimeTicks 277 MAX-ACCESS read-only 278 STATUS current 279 DESCRIPTION 280 "The time remaining before the local router next sends 281 a Candidate-RP-Advertisement to the elected BSR for 282 this zone." 283 ::= { pimBsrCandidateRPEntry 6 } 285 pimBsrCandidateRPPriority OBJECT-TYPE 286 SYNTAX Unsigned32 (0..255) 287 MAX-ACCESS read-create 288 STATUS current 289 DESCRIPTION 290 "The priority for this Candidate RP advertised in 291 Candidate-RP-Advertisements." 292 REFERENCE "RFC5059 section 3.2" 293 DEFVAL { 192 } 294 ::= { pimBsrCandidateRPEntry 7 } 296 pimBsrCandidateRPAdvInterval OBJECT-TYPE 297 SYNTAX Unsigned32 (1..26214) 298 UNITS "seconds" 299 MAX-ACCESS read-create 300 STATUS current 301 DESCRIPTION 302 "A Candidate RP generates Candidate-RP-Advertisements 303 periodically. This object represents the time interval 304 in seconds between two consecutive advertisements." 306 REFERENCE "RFC5059 section 3.2 and section 5" 307 DEFVAL { 60 } 309 ::= { pimBsrCandidateRPEntry 8 } 311 pimBsrCandidateRPHoldtime OBJECT-TYPE 312 SYNTAX Unsigned32 (0..65535) 313 UNITS "seconds" 314 MAX-ACCESS read-create 315 STATUS current 316 DESCRIPTION 317 "Holdtime for this Candidate RP. The amount of time (in 318 seconds) this Candidate-RP entry is valid. 320 This object's value can be zero only when this C-RP is 321 shutting down" 323 REFERENCE "RFC5059 section 4.2" 324 DEFVAL { 150 } 326 ::= { pimBsrCandidateRPEntry 9 } 328 pimBsrCandidateRPStatus OBJECT-TYPE 329 SYNTAX RowStatus 330 MAX-ACCESS read-create 331 STATUS current 332 DESCRIPTION 333 "The status of this row, by which new entries may be 334 created, or old entries deleted from this table. 336 This status object can be set to active(1) without 337 setting any other columnar objects in this entry 339 All writable objects in this entry can be modified 340 when the status of this entry is active(1)." 342 ::= { pimBsrCandidateRPEntry 10 } 344 pimBsrCandidateRPStorageType OBJECT-TYPE 345 SYNTAX StorageType 346 MAX-ACCESS read-create 347 STATUS current 348 DESCRIPTION 349 "The storage type for this row. Rows having the value 350 'permanent' need not allow write-access to any columnar 351 objects in the row." 352 DEFVAL { nonVolatile } 353 ::= { pimBsrCandidateRPEntry 11 } 355 -- 356 -- The BSR Elected BSR RP-Set Table 357 -- 359 pimBsrElectedBSRRPSetTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF PimBsrElectedBSRRPSetEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "The (conceptual) table listing BSR-specific information 365 about PIM group mappings learned via C-RP advertisements 366 or created locally using configurations. This table is 367 maintained only on the Elected BSR. 369 An Elected BSR uses this table to create Bootstrap 370 Messages after applying a local policy to include some 371 or all of the group mappings in this table." 373 ::= { pimBsrObjects 2 } 375 pimBsrElectedBSRRPSetEntry OBJECT-TYPE 376 SYNTAX PimBsrElectedBSRRPSetEntry 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "An entry (conceptual row) in the 381 pimBsrElectedBSRRPSetTable." 382 INDEX { pimBsrElectedBSRGrpMappingAddrType, 383 pimBsrElectedBSRGrpMappingGrpAddr, 384 pimBsrElectedBSRGrpMappingGrpPrefixLen, 385 pimBsrElectedBSRGrpMappingRPAddr } 386 ::= { pimBsrElectedBSRRPSetTable 1 } 388 PimBsrElectedBSRRPSetEntry ::= SEQUENCE { 389 pimBsrElectedBSRGrpMappingAddrType InetAddressType, 390 pimBsrElectedBSRGrpMappingGrpAddr InetAddress, 391 pimBsrElectedBSRGrpMappingGrpPrefixLen InetAddressPrefixLength, 392 pimBsrElectedBSRGrpMappingRPAddr InetAddress, 393 pimBsrElectedBSRRPSetPriority Unsigned32, 394 pimBsrElectedBSRRPSetHoldtime Unsigned32, 395 pimBsrElectedBSRRPSetExpiryTime TimeTicks, 396 pimBsrElectedBSRRPSetGrpBidir TruthValue 397 } 399 pimBsrElectedBSRGrpMappingAddrType OBJECT-TYPE 400 SYNTAX InetAddressType 401 MAX-ACCESS not-accessible 402 STATUS current 403 DESCRIPTION 404 "The Inet address type of the IP multicast group 405 prefix." 406 ::= { pimBsrElectedBSRRPSetEntry 2 } 408 pimBsrElectedBSRGrpMappingGrpAddr OBJECT-TYPE 409 SYNTAX InetAddress (SIZE (4|8|16|20)) 410 MAX-ACCESS not-accessible 411 STATUS current 412 DESCRIPTION 413 "The IP multicast group address which, when combined 414 with pimBsrElectedBSRGrpMappingGrpPrefixLen, gives the 415 group prefix for this mapping. The InetAddressType is 416 given by the pimBsrElectedBSRGrpMappingAddrType object. 418 This address object is only significant up to 419 pimBsrElectedBSRGrpMappingGrpPrefixLen bits. The 420 remainder of the address bits are zero. This is 421 especially important for this field, which is part of 422 the index of this entry. Any non-zero bits would 423 signify an entirely different entry." 424 ::= { pimBsrElectedBSRRPSetEntry 3 } 426 pimBsrElectedBSRGrpMappingGrpPrefixLen OBJECT-TYPE 427 SYNTAX InetAddressPrefixLength (4..128) 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "The multicast group prefix length that, when combined 432 with pimBsrElectedBSRGrpMappingGrpAddr, gives the group 433 prefix for this mapping. The InetAddressType is given by 434 the pimBsrElectedBSRGrpMappingAddrType object. If 435 pimBsrElectedBSRGrpMappingAddrType is 'ipv4' or 'ipv4z', 436 this object must be in the range 4..32. If 437 pimBsrElectedBSRGrpMappingAddrType is 'ipv6' or 'ipv6z', 438 this object must be in the range 8..128." 439 ::= { pimBsrElectedBSRRPSetEntry 4 } 441 pimBsrElectedBSRGrpMappingRPAddr OBJECT-TYPE 442 SYNTAX InetAddress (SIZE (4|8|16|20)) 443 MAX-ACCESS not-accessible 444 STATUS current 445 DESCRIPTION 446 "The IP address of the RP to be used for groups within 447 this group prefix. The InetAddressType is given by the 448 pimBsrElectedBSRGrpMappingAddrType object." 449 ::= { pimBsrElectedBSRRPSetEntry 5 } 451 pimBsrElectedBSRRPSetPriority OBJECT-TYPE 452 SYNTAX Unsigned32 (0..255) 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "The priority for RP. Numerically higher values for 457 this object indicate lower priorities, with the value 458 zero denoting the highest priority." 459 REFERENCE "RFC5059 section 4.1" 460 ::= { pimBsrElectedBSRRPSetEntry 6 } 462 pimBsrElectedBSRRPSetHoldtime OBJECT-TYPE 463 SYNTAX Unsigned32 (0..65535) 464 UNITS "seconds" 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The holdtime for RP" 469 REFERENCE "RFC5059 section 4.1" 470 ::= { pimBsrElectedBSRRPSetEntry 7 } 472 pimBsrElectedBSRRPSetExpiryTime OBJECT-TYPE 473 SYNTAX TimeTicks 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The minimum time remaining before this entry will be 478 aged out. The value zero indicates that this entry will 479 never be aged out." 480 ::= { pimBsrElectedBSRRPSetEntry 8 } 482 pimBsrElectedBSRRPSetGrpBidir OBJECT-TYPE 483 SYNTAX TruthValue 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "If this object is TRUE, this group range with this 488 RP is a BIDIR-PIM group range. If it is set to FALSE, 489 it is a PIM-SM group range." 490 ::= { pimBsrElectedBSRRPSetEntry 9 } 492 -- 493 -- The BSR Candidate-BSR Table 494 -- 496 pimBsrCandidateBSRTable OBJECT-TYPE 497 SYNTAX SEQUENCE OF PimBsrCandidateBSREntry 498 MAX-ACCESS not-accessible 499 STATUS current 500 DESCRIPTION 501 "The (conceptual) table containing Candidate-BSR 502 configuration for the local router. The table contains 503 one row for each zone for which the local router is 504 to advertise itself as a Candidate-BSR." 505 ::= { pimBsrObjects 3 } 507 pimBsrCandidateBSREntry OBJECT-TYPE 508 SYNTAX PimBsrCandidateBSREntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 "An entry (conceptual row) in the 513 pimBsrCandidateBSRTable." 514 INDEX { pimBsrCandidateBSRZoneIndex } 515 ::= { pimBsrCandidateBSRTable 1 } 517 PimBsrCandidateBSREntry ::= SEQUENCE { 518 pimBsrCandidateBSRZoneIndex InetZoneIndex, 519 pimBsrCandidateBSRAddressType InetAddressType, 520 pimBsrCandidateBSRAddress InetAddress, 521 pimBsrCandidateBSRPriority Unsigned32, 522 pimBsrCandidateBSRHashMaskLength Unsigned32, 523 pimBsrCandidateBSRElectedBSR TruthValue, 524 pimBsrCandidateBSRBootstrapTimer TimeTicks, 525 pimBsrCandidateBSRStatus RowStatus, 526 pimBsrCandidateBSRStorageType StorageType 527 } 529 pimBsrCandidateBSRZoneIndex OBJECT-TYPE 530 SYNTAX InetZoneIndex 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "The zone index uniquely identifies the zone on a 535 device to which this Candidate BSR is attached. There is 536 one entry for each zone in ipMcastZoneTable. Scope-level 537 information for this zone can be extracted from 538 ipMcastZoneTable in IP Multicast MIB [RFC5132]." 539 ::= { pimBsrCandidateBSREntry 1 } 541 pimBsrCandidateBSRAddressType OBJECT-TYPE 542 SYNTAX InetAddressType 543 MAX-ACCESS read-create 544 STATUS current 545 DESCRIPTION 546 "The address type of the Candidate-BSR." 547 ::= { pimBsrCandidateBSREntry 2 } 549 pimBsrCandidateBSRAddress OBJECT-TYPE 550 SYNTAX InetAddress 551 MAX-ACCESS read-create 552 STATUS current 553 DESCRIPTION 554 "The (unicast) address that the local router will 555 use to advertise itself as a Candidate-BSR. The 556 InetAddressType is given by the 557 pimBsrCandidateBSRAddressType object." 558 ::= { pimBsrCandidateBSREntry 3 } 560 pimBsrCandidateBSRPriority OBJECT-TYPE 561 SYNTAX Unsigned32 (0..255) 562 MAX-ACCESS read-create 563 STATUS current 564 DESCRIPTION 565 "The priority value for the local router as a 566 Candidate-BSR for this zone. Numerically higher 567 values for this object indicate higher priorities." 568 DEFVAL { 0 } 569 ::= { pimBsrCandidateBSREntry 4 } 571 pimBsrCandidateBSRHashMaskLength OBJECT-TYPE 572 SYNTAX Unsigned32 (0..128) 573 MAX-ACCESS read-create 574 STATUS current 575 DESCRIPTION 576 "The hash mask length (used in the RP hash function) 577 that the local router will advertise in its Bootstrap 578 messages for this zone. This object defaults 579 to 30 if pimBsrCandidateBSRAddressType is 'ipv4' or 580 'ipv4z' , and defaults to 126 if 581 pimBsrCandidateBSRAddressType is 'ipv6' or 'ipv6z'." 582 ::= { pimBsrCandidateBSREntry 5 } 584 pimBsrCandidateBSRElectedBSR OBJECT-TYPE 585 SYNTAX TruthValue 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "Whether the local router is the elected BSR for this 590 zone." 591 ::= { pimBsrCandidateBSREntry 6 } 593 pimBsrCandidateBSRBootstrapTimer OBJECT-TYPE 594 SYNTAX TimeTicks 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "The time remaining before the local router next 599 originates a Bootstrap message for this zone. 600 Value of this object is zero if 601 pimBsrCandidateBSRElectedBSR is 'FALSE'." 602 ::= { pimBsrCandidateBSREntry 7 } 604 pimBsrCandidateBSRStatus OBJECT-TYPE 605 SYNTAX RowStatus 606 MAX-ACCESS read-create 607 STATUS current 608 DESCRIPTION 609 "The status of this row, by which new entries may 610 be created, or old entries deleted from this table. 612 This status object can be set to active(1) without 613 setting any other columnar objects in this entry 615 All writable objects in this entry can be modified 616 when the status of this entry is active(1)." 617 ::= { pimBsrCandidateBSREntry 8 } 619 pimBsrCandidateBSRStorageType OBJECT-TYPE 620 SYNTAX StorageType 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "The storage type for this row. Rows having the value 625 'permanent' need not allow write-access to any columnar 626 objects in the row." 627 DEFVAL { nonVolatile } 628 ::= { pimBsrCandidateBSREntry 9 } 630 -- 631 -- The BSR Elected-BSR Table 632 -- 633 pimBsrElectedBSRTable OBJECT-TYPE 634 SYNTAX SEQUENCE OF PimBsrElectedBSREntry 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION 638 "The (conceptual) table containing information about 639 elected BSRs. The table contains one row for each 640 zone for which there is an elected BSR." 641 ::= { pimBsrObjects 4 } 643 pimBsrElectedBSREntry OBJECT-TYPE 644 SYNTAX PimBsrElectedBSREntry 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "An entry (conceptual row) in the 649 pimBsrElectedBSRTable." 650 INDEX { pimBsrElectedBSRZoneIndex } 651 ::= { pimBsrElectedBSRTable 1 } 653 PimBsrElectedBSREntry ::= SEQUENCE { 654 pimBsrElectedBSRZoneIndex InetZoneIndex, 655 pimBsrElectedBSRAddressType InetAddressType, 656 pimBsrElectedBSRAddress InetAddress, 657 pimBsrElectedBSRPriority Unsigned32, 658 pimBsrElectedBSRHashMaskLength Unsigned32, 659 pimBsrElectedBSRExpiryTime TimeTicks 660 } 662 pimBsrElectedBSRZoneIndex OBJECT-TYPE 663 SYNTAX InetZoneIndex 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "The zone index uniquely identifies the zone on a 668 device to which this Elected BSR is attached. There 669 is one entry for each zone in ipMcastZoneTable. 670 Scope-level information for this zone can be extracted 671 from ipMcastZoneTable in IP MCAST MIB." 672 ::= { pimBsrElectedBSREntry 1 } 674 pimBsrElectedBSRAddressType OBJECT-TYPE 675 SYNTAX InetAddressType 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The address type of the elected BSR." 680 ::= { pimBsrElectedBSREntry 2 } 682 pimBsrElectedBSRAddress OBJECT-TYPE 683 SYNTAX InetAddress (SIZE (4|8|16|20)) 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The (unicast) address of the elected BSR. The 688 InetAddressType is given by the 689 pimBsrElectedBSRAddressType object." 690 ::= { pimBsrElectedBSREntry 3 } 692 pimBsrElectedBSRPriority OBJECT-TYPE 693 SYNTAX Unsigned32 (0..255) 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The priority value for the elected BSR for this address 698 type. Numerically higher values for this object indicate 699 higher priorities." 700 ::= { pimBsrElectedBSREntry 4 } 702 pimBsrElectedBSRHashMaskLength OBJECT-TYPE 703 SYNTAX Unsigned32 (0..128) 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The hash mask length (used in the RP hash function) 708 advertised by the elected BSR for this zone." 709 ::= { pimBsrElectedBSREntry 5 } 711 pimBsrElectedBSRExpiryTime OBJECT-TYPE 712 SYNTAX TimeTicks 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "The minimum time remaining before the elected BSR for 717 this zone will be declared down." 718 ::= { pimBsrElectedBSREntry 6 } 720 -- 721 -- PIM BSR Notifications 722 -- 724 pimBsrElectedBSRLostElection NOTIFICATION-TYPE 725 OBJECTS { pimBsrElectedBSRAddressType, 726 pimBsrElectedBSRAddress, 727 pimBsrElectedBSRPriority } 728 STATUS current 729 DESCRIPTION 730 "A pimBsrElectedBSRLostElection notification should be 731 generated when current E-BSR lost election to a new 732 Candidate BSR. Only an E-BSR should generate this 733 notification. 735 This notification is generated when 736 pimBsrCandidateBSRElectedBSR becomes FALSE." 738 REFERENCE "RFC5059 section 3.1" 739 ::= { pimBsrNotifications 1 } 741 pimBsrCandidateBSRWinElection NOTIFICATION-TYPE 742 OBJECTS { pimBsrCandidateBSRElectedBSR } 743 STATUS current 744 DESCRIPTION 745 "A pimBsrCandidateBSRWinElection notification should be 746 generated when a C-BSR wins BSR Election. Only an 747 E-BSR should generate this notification. 749 This notification is generated when 750 pimBsrCandidateBSRElectedBSR becomes TRUE." 752 REFERENCE "RFC5059 section 3.1" 753 ::= { pimBsrNotifications 2 } 755 -- 756 -- Compliance Statements 757 -- 759 pimBsrCompliance MODULE-COMPLIANCE 760 STATUS current 761 DESCRIPTION 762 "The compliance statement for PIM routers that implement 763 the Bootstrap Router (BSR) mechanism." 764 MODULE -- this module 765 MANDATORY-GROUPS { pimBsrObjectGroup } 767 GROUP pimBsrDiagnosticsGroup 768 DESCRIPTION 769 "This group is optional." 771 ::= { pimBsrCompliances 1 } 773 -- 774 -- Units of Conformance 775 -- 777 pimBsrObjectGroup OBJECT-GROUP 778 OBJECTS { pimBsrCandidateRPBidir, 779 pimBsrCandidateRPAdvTimer, 780 pimBsrCandidateRPPriority, 781 pimBsrCandidateRPAdvInterval, 782 pimBsrCandidateRPHoldtime, 783 pimBsrCandidateRPStatus, 784 pimBsrCandidateRPStorageType, 785 pimBsrElectedBSRRPSetPriority, 786 pimBsrElectedBSRRPSetHoldtime, 787 pimBsrElectedBSRRPSetExpiryTime, 788 pimBsrElectedBSRRPSetGrpBidir, 789 pimBsrCandidateBSRAddress, 790 pimBsrCandidateBSRAddressType, 791 pimBsrCandidateBSRPriority, 792 pimBsrCandidateBSRHashMaskLength, 793 pimBsrCandidateBSRElectedBSR, 794 pimBsrCandidateBSRBootstrapTimer, 795 pimBsrCandidateBSRStatus, 796 pimBsrCandidateBSRStorageType, 797 pimBsrElectedBSRAddress, 798 pimBsrElectedBSRAddressType, 799 pimBsrElectedBSRPriority, 800 pimBsrElectedBSRHashMaskLength, 801 pimBsrElectedBSRExpiryTime } 802 STATUS current 803 DESCRIPTION 804 "A collection of objects for managing the Bootstrap 805 Router (BSR) mechanism for PIM routers." 806 ::= { pimBsrGroups 1 } 808 pimBsrDiagnosticsGroup NOTIFICATION-GROUP 809 NOTIFICATIONS { pimBsrElectedBSRLostElection, 810 pimBsrCandidateBSRWinElection } 811 STATUS current 812 DESCRIPTION 813 "Objects providing additional diagnostics related to 814 the Bootstrap Router (BSR) mechanism for PIM routers." 815 ::= { pimBsrGroups 2 } 817 END 819 6. Security Considerations 821 There are a number of management objects defined in this MIB module 822 with a MAX-ACCESS clause of read-write and/or read-create. Such 823 objects may be considered sensitive or vulnerable in some network 824 environments. The support for SET operations in a non-secure 825 environment without proper protection can have a negative effect on 826 network operations. These are the tables and objects and their 827 sensitivity/vulnerability: 829 o A new Candidate BSR with high priority or modification of priority 830 of an existing candidate BSR can take over the functionality of 831 Elected BSR, which can prevent and disrupt the services. 833 o A new Candidate RP with lower priority or modification of priority 834 of an existing Candidate RP can force other routers to select 835 itself for a particular group prefix. This can prevent and 836 disrupt the services provided through this group prefix. 838 The following are the read-write and read-create objects defined in 839 this MIB module: 841 bsrCandidateRPBidir 842 bsrCandidateRPPriority 843 bsrCandidateRPAdvInterval 844 bsrCandidateRPHoldtime 845 bsrCandidateBSRAddressType 846 bsrCandidateBSRAddress 847 bsrCandidateBSRPriority 848 bsrCandidateBSRHashMaskLength 850 Some of the readable objects in this MIB module (i.e., objects with a 851 MAX-ACCESS other than not-accessible) may be considered sensitive or 852 vulnerable in some network environments. It is thus important to 853 control even GET and/or NOTIFY access to these objects and possibly 854 to even encrypt the values of these objects when sending them over 855 the network via SNMP. These are the tables and objects and their 856 sensitivity/vulnerability: 858 pimBsrCandidateRPAdvTimer 859 pimBsrElectedBSRRPSetPriority 860 pimBsrElectedBSRRPSetHoldtime 861 pimBsrElectedBSRRPSetExpiryTime 862 pimBsrElectedBSRRPSetGrpBidir 863 pimBsrCandidateBSRElectedBSR 864 pimBsrCandidateBSRBootstrapTimer 865 pimBsrElectedBSRAddressType 866 pimBsrElectedBSRAddress 867 pimBsrElectedBSRPriority 868 pimBsrElectedBSRHashMaskLength 869 pimBsrElectedBSRExpiryTime 870 In this MIB module, possible effects that can be induced by GET 871 operations include: 873 o Determination of Elected BSR, Candidate BSRs and Candidate RPs in 874 the Multicast Network topology. This information may be sensitive 875 and may be used in preparation for DoS attacks including any of 876 the attacks described above. 878 SNMP versions prior to SNMPv3 did not include adequate security. 879 Even if the network itself is secure (for example by using IPSec), 880 there is still no control over whom on the secure network is allowed 881 to access (read/change/create/delete) the objects in this MIB module. 883 It is RECOMMENDED that implementers consider the security features as 884 provided by the SNMPv3 framework (see [RFC3410], section 8), 885 including full support for the SNMPv3 cryptographic mechanisms (for 886 authentication and privacy). 888 Further, deployment of SNMP versions prior to SNMPv3 is NOT 889 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 890 enable cryptographic security. It is then a customer/operator 891 responsibility to ensure that the SNMP entity giving access to an 892 instance of this MIB module is properly configured to give access to 893 the objects only to those principals (users) that have legitimate 894 rights to access (read/change/create/delete) them. 896 7. IANA Considerations 898 The MIB module in this document uses the following IANA-assigned 899 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 901 Descriptor OBJECT IDENTIFIER value 902 ---------- ----------------------- 903 pimBsrMIB { mib-2 XXX } 905 Editor's Note (to be removed prior to publication): the IANA is 906 requested to assign a value for "XXX" under the 'mib-2' subtree and 907 to record the assignment in the SMI Numbers registry. When the 908 assignment has been made, the RFC Editor is asked to replace "XXX" 909 (here and in the MIB module) with the assigned value and to remove 910 this note. 912 8. Acknowledgments 914 This MIB module is based on the original work in [RFC5060] by R. 915 Sivaramu, J. Lingard and B. Joshi. 917 Many thanks to Bill Fenner, Stig Venaas, Nidhi Bhaskar, David 918 Mcwalter, David Harrington and J. W. Atwood for their feedback on 919 this MIB module. 921 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 922 been used for comparison while editing this MIB module. 924 9. References 926 9.1. Normative References 928 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 929 Requirement Levels", BCP 14, RFC 2119, March 1997. 931 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 932 Schoenwaelder, Ed., "Structure of Management Information 933 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 935 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 936 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 937 STD 58, RFC 2579, April 1999. 939 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 940 "Conformance Statements for SMIv2", STD 58, RFC 2580, 941 April 1999. 943 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 944 Schoenwaelder, "Textual Conventions for Internet Network 945 Addresses", RFC 4001, February 2005. 947 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 948 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 949 Protocol Specification (Revised)", RFC 4601, August 2006. 951 [RFC5060] Sivaramu, R., Lingard, J., McWalter, D., Joshi, B., and A. 952 Kessler, "Protocol Independent Multicast MIB", RFC 5060, 953 January 2008. 955 [RFC5059] Bhaskar, N., Gall, A., Lingard, J., and S. Venaas, 956 "Bootstrap Router (BSR) Mechanism for Protocol Independent 957 Multicast (PIM)", RFC 5059, January 2008. 959 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 960 MIB", RFC 5132, December 2007. 962 9.2. Informative References 964 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 965 "Introduction and Applicability Statements for Internet- 966 Standard Management Framework", RFC 3410, December 2002. 968 Authors' Addresses 970 Bharat Joshi 971 Infosys Technologies Ltd. 972 44 Electronics City, Hosur Road 973 Bangalore 560 100 974 India 976 Email: bharat_joshi@infosys.com 977 URI: http://www.infosys.com/ 979 Raina Bijlani 981 Email: rainab@gmail.com 983 Intellectual Property Statement 985 The IETF takes no position regarding the validity or scope of any 986 Intellectual Property Rights or other rights that might be claimed to 987 pertain to the implementation or use of the technology described in 988 this document or the extent to which any license under such rights 989 might or might not be available; nor does it represent that it has 990 made any independent effort to identify any such rights. Information 991 on the procedures with respect to rights in RFC documents can be 992 found in BCP 78 and BCP 79. 994 Copies of IPR disclosures made to the IETF Secretariat and any 995 assurances of licenses to be made available, or the result of an 996 attempt made to obtain a general license or permission for the use of 997 such proprietary rights by implementers or users of this 998 specification can be obtained from the IETF on-line IPR repository at 999 http://www.ietf.org/ipr. 1001 The IETF invites any interested party to bring to its attention any 1002 copyrights, patents or patent applications, or other proprietary 1003 rights that may cover technology that may be required to implement 1004 this standard. Please address the information to the IETF at 1005 ietf-ipr@ietf.org. 1007 Disclaimer of Validity 1009 This document and the information contained herein are provided on an 1010 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1011 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1012 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1013 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1014 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1015 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1017 Copyright Statement 1019 Copyright (C) The IETF Trust (2008). This document is subject to the 1020 rights, licenses and restrictions contained in BCP 78, and except as 1021 set forth therein, the authors retain all their rights. 1023 Acknowledgment 1025 Funding for the RFC Editor function is currently provided by the 1026 Internet Society.