idnits 2.17.1 draft-ietf-pim-bsr-mib-00.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 949. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 926. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 933. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 939. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (August 23, 2006) is 6453 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) == Unused Reference: 'RFC2365' is defined on line 847, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 850, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mboned-ip-mcast-mib' is defined on line 887, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) == Outdated reference: A later version (-10) exists of draft-ietf-pim-mib-v2-06 == Outdated reference: A later version (-12) exists of draft-ietf-pim-sm-bsr-08 == Outdated reference: A later version (-07) exists of draft-ietf-mboned-ip-mcast-mib-03 Summary: 4 errors (**), 0 flaws (~~), 9 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: February 24, 2007 R. Bijlani 5 Cisco Systems 6 August 23, 2006 8 PIM Bootstrap Router MIB 9 draft-ietf-pim-bsr-mib-00.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 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 26 material 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 This Internet-Draft will expire on February 24, 2007. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document defines a portion of the Management Information Base 43 (MIB) for use with network management protocols in the Internet 44 community. In particular, it describes managed objects used for 45 managing the Bootstrap Router (BSR) mechanism for PIM. 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 . . . . . . . . . . . . . . . . . . . 17 55 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 56 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 57 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 58 9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 59 9.2. Informative References . . . . . . . . . . . . . . . . . . 20 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 61 Intellectual Property and Copyright Statements . . . . . . . . . . 22 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. [I-D.ietf-pim-sm-v2-new], 69 [I-D.ietf-pim-sm-bsr]. 71 This document was created by moving some of the PIM BSR specific MIB 72 tables from one of the earlier version of PIM MIB draft [I-D.ietf- 73 pim-mib-v2]. 75 2. The Internet-Standard Management Framework 77 For a detailed overview of the documents that describe the current 78 Internet-Standard Management Framework, please refer to section 7 of 79 RFC 3410[RFC3410]. 81 Managed objects are accessed via a virtual information store, termed 82 the Management Information Base or MIB. MIB objects are generally 83 accessed through the Simple Network Management Protocol (SNMP). 84 Objects in the MIB are defined using the mechanisms defined in the 85 Structure of Management Information (SMI). This memo specifies a MIB 86 module that is compliant to the SMIv2, which is described in STD 58, 87 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 88 [RFC2580]. 90 3. Conventions 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119 [RFC2119]. 96 4. Overview 98 This MIB module contains four tables. The tables are: 100 1. The BSR Candidate-RP Table, which contains one row for each 101 multicast group address prefix for which the local router is to 102 advertise itself as a Candidate-RP. 104 2. The BSR Elected BSR RP-Set Table, which contains one row for each 105 Group-to-RP mapping that was received in C-RP advertisements. 107 3. The BSR Candidate-BSR Table, which contains one row for each 108 Candidate-BSR configuration for the local router. 110 4. The BSR Elected BSR Table, which contains one row for each 111 elected BSR. 113 This MIB module uses textual conventions defined in the IF-MIB 114 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 116 5. Definitions 118 PIM-BSR-MIB DEFINITIONS ::= BEGIN 120 IMPORTS 121 MODULE-IDENTITY, OBJECT-TYPE, 122 NOTIFICATION-TYPE, 123 mib-2, Unsigned32, TimeTicks FROM SNMPv2-SMI 124 RowStatus, TruthValue FROM SNMPv2-TC 125 MODULE-COMPLIANCE, OBJECT-GROUP, 126 NOTIFICATION-GROUP FROM SNMPv2-CONF 127 InetAddressType, 128 InetAddressPrefixLength, 129 InetAddress, 130 InetZoneIndex FROM INET-ADDRESS-MIB; 132 pimBsrMIB MODULE-IDENTITY 133 LAST-UPDATED "200606160000Z" -- 16 June 2006 134 ORGANIZATION "IETF PIM Working Group" 135 CONTACT-INFO 136 "Email: pim@ietf.org" 137 DESCRIPTION 138 "The MIB module for management of the Bootstrap Router 139 (BSR) mechanism for PIM routers. 141 Copyright (C) The Internet Society (2006). This version 142 of this MIB module is part of RFC yyyy; see the RFC 143 itself for full legal notices." 144 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 145 REVISION "200608230000Z" -- 23 August 2006 146 DESCRIPTION "Initial version, published as RFC yyyy." 147 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 148 ::= { mib-2 XXX } 149 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 151 -- 152 -- Top-level structure 153 -- 155 pimBsrMIBObjects OBJECT IDENTIFIER ::= { pimBsrMIB 1 } 156 pimBsrTraps OBJECT IDENTIFIER ::= { pimBsrMIBObjects 0 } 157 pimBsr OBJECT IDENTIFIER ::= { pimBsrMIBObjects 1 } 159 -- 160 -- The BSR Candidate-RP Table 161 -- 163 bsrCandidateRPTable OBJECT-TYPE 164 SYNTAX SEQUENCE OF BsrCandidateRPEntry 165 MAX-ACCESS not-accessible 166 STATUS current 167 DESCRIPTION 168 "The (conceptual) table listing the IP multicast group 169 prefixes for which the local router is to advertise 170 itself as a Candidate-RP." 171 ::= { pimBsr 1 } 173 bsrCandidateRPEntry OBJECT-TYPE 174 SYNTAX BsrCandidateRPEntry 175 MAX-ACCESS not-accessible 176 STATUS current 177 DESCRIPTION 178 "An entry (conceptual row) in the bsrCandidateRPTable." 179 INDEX { bsrCandidateRPAddressType, 180 bsrCandidateRPAddress, 181 bsrCandidateRPGroupAddress, 182 bsrCandidateRPGroupPrefixLength } 183 ::= { bsrCandidateRPTable 1 } 185 BsrCandidateRPEntry ::= SEQUENCE { 186 bsrCandidateRPAddressType InetAddressType, 187 bsrCandidateRPAddress InetAddress, 188 bsrCandidateRPGroupAddress InetAddress, 189 bsrCandidateRPGroupPrefixLength InetAddressPrefixLength, 190 bsrCandidateRPBidir TruthValue, 191 bsrCandidateRPAdvTimer TimeTicks, 192 bsrCandidateRPPriority Unsigned32, 193 bsrCandidateRPAdvInterval Unsigned32, 194 bsrCandidateRPHoldtime Unsigned32, 195 bsrCandidateRPStatus RowStatus 196 } 198 bsrCandidateRPAddressType OBJECT-TYPE 199 SYNTAX InetAddressType 200 MAX-ACCESS not-accessible 201 STATUS current 202 DESCRIPTION 203 "The Inet address type of the Candidate-RP." 204 ::= { bsrCandidateRPEntry 1 } 206 bsrCandidateRPAddress OBJECT-TYPE 207 SYNTAX InetAddress (SIZE (4|8|16|20)) 208 MAX-ACCESS not-accessible 209 STATUS current 210 DESCRIPTION 211 "The (unicast) address which will be advertised as a 212 Candidate-RP. The InetAddressType is given by the 213 bsrCandidateRPAddressType object." 214 ::= { bsrCandidateRPEntry 2 } 216 bsrCandidateRPGroupAddress OBJECT-TYPE 217 SYNTAX InetAddress (SIZE (4|8|16|20)) 218 MAX-ACCESS not-accessible 219 STATUS current 220 DESCRIPTION 221 "The IP multicast group address which, when combined with 222 the corresponding value of 223 bsrCandidateRPGroupPrefixLength, identifies a group 224 prefix for which the local router will advertise itself 225 as a Candidate-RP. The InetAddressType is given by the 226 bsrCandidateRPAddressType object." 227 ::= { bsrCandidateRPEntry 3 } 229 bsrCandidateRPGroupPrefixLength OBJECT-TYPE 230 SYNTAX InetAddressPrefixLength (4..128) 231 MAX-ACCESS not-accessible 232 STATUS current 233 DESCRIPTION 234 "The multicast group address mask which, when combined 235 with the corresponding value of 236 bsrCandidateRPGroupAddress, identifies a group prefix 237 for which the local router will advertise itself as a 238 Candidate-RP. The InetAddressType is given by the 239 bsrCandidateRPAddressType object." 240 ::= { bsrCandidateRPEntry 4 } 242 bsrCandidateRPBidir OBJECT-TYPE 243 SYNTAX TruthValue 244 MAX-ACCESS read-create 245 STATUS current 246 DESCRIPTION 247 "If this object is set to TRUE, this group range is 248 advertised with this RP as a BIDIR-PIM group range. If 249 it is set to FALSE, it is advertised as a PIM-SM group 250 range." 251 DEFVAL { false } 252 ::= { bsrCandidateRPEntry 5 } 254 bsrCandidateRPAdvTimer OBJECT-TYPE 255 SYNTAX TimeTicks 256 MAX-ACCESS read-only 257 STATUS current 258 DESCRIPTION 259 "The time remaining before the local router next sends 260 a Candidate-RP-Advertisement to the elected BSR for 261 this zone." 262 ::= { bsrCandidateRPEntry 6 } 264 bsrCandidateRPPriority OBJECT-TYPE 265 SYNTAX Unsigned32 (0..255) 266 MAX-ACCESS read-create 267 STATUS current 268 DESCRIPTION 269 "The priority for this Candidate RP advertised in 270 Candidate-RP-Advertisements." 271 REFERENCE "I-D.ietf-pim-sm-bsr section 3.2" 272 DEFVAL { 192 } 273 ::= { bsrCandidateRPEntry 7 } 275 bsrCandidateRPAdvInterval OBJECT-TYPE 276 SYNTAX Unsigned32 (0..26214) 277 MAX-ACCESS read-create 278 STATUS current 279 DESCRIPTION 280 "A Candidate RP generates Candidate-RP-Advertisements 281 periodically. This object represents the time interval 282 in seconds between two consecutive advertisements." 284 REFERENCE "I-D.ietf-pim-sm-bsr section 3.2 and section 5" 285 DEFVAL { 60 } 287 ::= { bsrCandidateRPEntry 8 } 289 bsrCandidateRPHoldtime OBJECT-TYPE 290 SYNTAX Unsigned32 (0..65535) 291 MAX-ACCESS read-create 292 STATUS current 293 DESCRIPTION 294 "Holdtime for this Candidate RP. The amount of time (in 295 seconds) this Candidate-RP entry is valid." 297 REFERENCE "I-D.ietf-pim-sm-bsr section 4.2" 298 DEFVAL { 150 } 300 ::= { bsrCandidateRPEntry 9 } 302 bsrCandidateRPStatus OBJECT-TYPE 303 SYNTAX RowStatus 304 MAX-ACCESS read-create 305 STATUS current 306 DESCRIPTION 307 "The status of this row, by which new entries may be 308 created, or old entries deleted from this table." 310 ::= { bsrCandidateRPEntry 10 } 312 -- 313 -- The BSR Elected BSR RP-Set Table 314 -- 316 bsrElectedBSRRPSetTable OBJECT-TYPE 317 SYNTAX SEQUENCE OF BsrElectedBSRRPSetEntry 318 MAX-ACCESS not-accessible 319 STATUS current 320 DESCRIPTION 321 "The (conceptual) table listing BSR-specific information 322 about PIM group mappings learned via C-RP advertisements 323 or created locally using configurations. This table is 324 maintained only on the Elected BSR. 326 An Elected BSR uses this table to create Bootstrap 327 Messages after applying a local policy to include some 328 or all of the group mappings in this table." 330 ::= { pimBsr 2 } 332 bsrElectedBSRRPSetEntry OBJECT-TYPE 333 SYNTAX BsrElectedBSRRPSetEntry 334 MAX-ACCESS not-accessible 335 STATUS current 336 DESCRIPTION 337 "An entry (conceptual row) in the 338 bsrElectedBSRRPSetTable." 339 INDEX { bsrElectedBSRGrpMappingAddrType, 340 bsrElectedBSRGrpMappingGrpAddr, 341 bsrElectedBSRGrpMappingGrpPrefixLen, 342 bsrElectedBSRGrpMappingRPAddr } 343 ::= { bsrElectedBSRRPSetTable 1 } 345 BsrElectedBSRRPSetEntry ::= SEQUENCE { 346 bsrElectedBSRGrpMappingAddrType InetAddressType, 347 bsrElectedBSRGrpMappingGrpAddr InetAddress, 348 bsrElectedBSRGrpMappingGrpPrefixLen InetAddressPrefixLength, 349 bsrElectedBSRGrpMappingRPAddr InetAddress, 350 bsrElectedBSRRPSetPriority Unsigned32, 351 bsrElectedBSRRPSetHoldtime Unsigned32, 352 bsrElectedBSRRPSetExpiryTime TimeTicks, 353 bsrElectedBSRRPSetGrpBidir TruthValue 354 } 356 bsrElectedBSRGrpMappingAddrType OBJECT-TYPE 357 SYNTAX InetAddressType 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "The Inet address type of the IP multicast group 362 prefix." 363 ::= { bsrElectedBSRRPSetEntry 2 } 365 bsrElectedBSRGrpMappingGrpAddr OBJECT-TYPE 366 SYNTAX InetAddress (SIZE (4|8|16|20)) 367 MAX-ACCESS not-accessible 368 STATUS current 369 DESCRIPTION 370 "The IP multicast group address which, when combined 371 with bsrElectedBSRGrpMappingGrpPrefixLen, gives the group 372 prefix for this mapping. The InetAddressType is given 373 by the bsrElectedBSRGrpMappingAddrType object. 375 This address object is only significant up to 376 bsrGroupMappingGrpPrefixLength bits. The remainder 377 of the address bits are zero. This is especially 378 important for this field, which is part of the index of 379 this entry. Any non-zero bits would signify an entirely 380 different entry." 381 ::= { bsrElectedBSRRPSetEntry 3 } 383 bsrElectedBSRGrpMappingGrpPrefixLen OBJECT-TYPE 384 SYNTAX InetAddressPrefixLength (4..128) 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "The multicast group prefix length, which, when combined 389 with bsrElectedBSRGrpMappingGrpAddr, gives the group 390 prefix for this mapping. The InetAddressType is given by 391 the bsrElectedBSRGrpMappingAddrType object. If 392 bsrElectedBSRGrpMappingAddrType is 'ipv4' or 'ipv4z', 393 this object must be in the range 4..32. If 394 bsrElectedBSRGrpMappingAddrType is 'ipv6' or 'ipv6z', 395 this object must be in the range 8..128." 396 ::= { bsrElectedBSRRPSetEntry 4 } 398 bsrElectedBSRGrpMappingRPAddr OBJECT-TYPE 399 SYNTAX InetAddress (SIZE (4|8|16|20)) 400 MAX-ACCESS not-accessible 401 STATUS current 402 DESCRIPTION 403 "The IP address of the RP to be used for groups within 404 this group prefix. The InetAddressType is given by the 405 bsrElectedBSRGrpMappingAddrType object." 406 ::= { bsrElectedBSRRPSetEntry 5 } 408 bsrElectedBSRRPSetPriority OBJECT-TYPE 409 SYNTAX Unsigned32 (0..255) 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The priority for RP". Numerically higher values for 414 this object indicate lower priorities, with the value 415 zero denoting the highest priority." 416 ::= { bsrElectedBSRRPSetEntry 6 } 418 bsrElectedBSRRPSetHoldtime OBJECT-TYPE 419 SYNTAX Unsigned32 (0..65535) 420 UNITS "seconds" 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The holdtime for RP" 425 ::= { bsrElectedBSRRPSetEntry 7 } 427 bsrElectedBSRRPSetExpiryTime OBJECT-TYPE 428 SYNTAX TimeTicks 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The minimum time remaining before this entry will be 433 aged out. The value zero indicates that this entry will 434 never be aged out." 435 ::= { bsrElectedBSRRPSetEntry 8 } 437 bsrElectedBSRRPSetGrpBidir OBJECT-TYPE 438 SYNTAX TruthValue 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "If this object is TRUE, this group range with this 443 RP is a BIDIR-PIM group range. If it is set to FALSE, 444 it is a PIM-SM group range." 445 ::= { bsrElectedBSRRPSetEntry 9 } 447 -- 448 -- The BSR Candidate-BSR Table 449 -- 451 bsrCandidateBSRTable OBJECT-TYPE 452 SYNTAX SEQUENCE OF BsrCandidateBSREntry 453 MAX-ACCESS not-accessible 454 STATUS current 455 DESCRIPTION 456 "The (conceptual) table containing Candidate-BSR 457 configuration for the local router. The table contains 458 one row for each zone for which the local router is 459 to advertise itself as a Candidate-BSR." 460 ::= { pimBsr 3 } 462 bsrCandidateBSREntry OBJECT-TYPE 463 SYNTAX BsrCandidateBSREntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "An entry (conceptual row) in the bsrCandidateBSRTable." 468 INDEX { bsrCandidateBSRZoneIndex } 469 ::= { bsrCandidateBSRTable 1 } 471 BsrCandidateBSREntry ::= SEQUENCE { 472 bsrCandidateBSRZoneIndex InetZoneIndex, 473 bsrCandidateBSRAddressType InetAddressType, 474 bsrCandidateBSRAddress InetAddress, 475 bsrCandidateBSRPriority Unsigned32, 476 bsrCandidateBSRHashMaskLength Unsigned32, 477 bsrCandidateBSRElectedBSR TruthValue, 478 bsrCandidateBSRBootstrapTimer TimeTicks, 479 bsrCandidateBSRStatus RowStatus 480 } 482 bsrCandidateBSRZoneIndex OBJECT-TYPE 483 SYNTAX InetZoneIndex 484 MAX-ACCESS not-accessible 485 STATUS current 486 DESCRIPTION 487 "The zone index uniquely identifies the zone on 488 a device with which this Candidate BSR is attached. 490 There is one entry for each zone in ipMcastZoneTable. 491 Scope-level information for this zone can be extracted 492 from ipMcastZoneTable in IP MCAST MIB" 493 ::= { bsrCandidateBSREntry 1 } 495 bsrCandidateBSRAddressType OBJECT-TYPE 496 SYNTAX InetAddressType 497 MAX-ACCESS read-create 498 STATUS current 499 DESCRIPTION 500 "The address type of the Candidate-BSR." 501 ::= { bsrCandidateBSREntry 2 } 503 bsrCandidateBSRAddress OBJECT-TYPE 504 SYNTAX InetAddress 505 MAX-ACCESS read-create 506 STATUS current 507 DESCRIPTION 508 "The (unicast) address which the local router will 509 use to advertise itself as a Candidate-BSR. The 510 InetAddressType is given by the 511 bsrCandidateBSRAddressType object." 512 ::= { bsrCandidateBSREntry 3 } 514 bsrCandidateBSRPriority OBJECT-TYPE 515 SYNTAX Unsigned32 (0..255) 516 MAX-ACCESS read-create 517 STATUS current 518 DESCRIPTION 519 "The priority value for the local router as a 520 Candidate-BSR for this zone. Numerically higher 521 values for this object indicate higher priorities." 522 DEFVAL { 0 } 523 ::= { bsrCandidateBSREntry 4 } 525 bsrCandidateBSRHashMaskLength OBJECT-TYPE 526 SYNTAX Unsigned32 (0..128) 527 MAX-ACCESS read-create 528 STATUS current 529 DESCRIPTION 530 "The hash mask length (used in the RP hash function) 531 that the local router will advertise in its Bootstrap 532 messages for this zone. This object defaults 533 to 30 if bsrCandidateBSRAddressType is 'ipv4' or 'ipv4z' 534 , and defaults to 126 if bsrCandidateBSRAddressType is 535 'ipv6' or 'ipv6z'." 536 ::= { bsrCandidateBSREntry 5 } 538 bsrCandidateBSRElectedBSR OBJECT-TYPE 539 SYNTAX TruthValue 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "Whether the local router is the elected BSR for this 544 zone." 545 ::= { bsrCandidateBSREntry 6 } 547 bsrCandidateBSRBootstrapTimer OBJECT-TYPE 548 SYNTAX TimeTicks 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The time remaining before the local router next 553 originates a Bootstrap message for this zone. 554 Value of this object is zero if 555 bsrCandidateBSRElectedBSR is 'FALSE'." 556 ::= { bsrCandidateBSREntry 7 } 558 bsrCandidateBSRStatus OBJECT-TYPE 559 SYNTAX RowStatus 560 MAX-ACCESS read-create 561 STATUS current 562 DESCRIPTION 563 "The status of this row, by which new entries may 564 be created, or old entries deleted from this table." 565 ::= { bsrCandidateBSREntry 8 } 567 -- 568 -- The BSR Elected-BSR Table 569 -- 571 bsrElectedBSRTable OBJECT-TYPE 572 SYNTAX SEQUENCE OF BsrElectedBSREntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "The (conceptual) table containing information about 577 elected BSRs. The table contains one row for each 578 zone for which there is an elected BSR." 579 ::= { pimBsr 4 } 581 bsrElectedBSREntry OBJECT-TYPE 582 SYNTAX BsrElectedBSREntry 583 MAX-ACCESS not-accessible 584 STATUS current 585 DESCRIPTION 586 "An entry (conceptual row) in the bsrElectedBSRTable." 587 INDEX { bsrElectedBSRZoneIndex } 588 ::= { bsrElectedBSRTable 1 } 590 BsrElectedBSREntry ::= SEQUENCE { 591 bsrElectedBSRZoneIndex InetZoneIndex, 592 bsrElectedBSRAddressType InetAddressType, 593 bsrElectedBSRAddress InetAddress, 594 bsrElectedBSRPriority Unsigned32, 595 bsrElectedBSRHashMaskLength Unsigned32, 596 bsrElectedBSRExpiryTime TimeTicks 597 } 599 bsrElectedBSRZoneIndex OBJECT-TYPE 600 SYNTAX InetZoneIndex 601 MAX-ACCESS not-accessible 602 STATUS current 603 DESCRIPTION 604 "The zone index uniquely identifies the zone on a 605 device with which this Elected BSR is attached. There 606 is one entry for each zone in ipMcastZoneTable. 607 Scope-level information for this zone can be extracted 608 from ipMcastZoneTable in IP MCAST MIB" 609 ::= { bsrElectedBSREntry 1 } 611 bsrElectedBSRAddressType OBJECT-TYPE 612 SYNTAX InetAddressType 613 MAX-ACCESS not-accessible 614 STATUS current 615 DESCRIPTION 616 "The address type of the elected BSR." 617 ::= { bsrElectedBSREntry 2 } 619 bsrElectedBSRAddress OBJECT-TYPE 620 SYNTAX InetAddress (SIZE (4|8|16|20)) 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "The (unicast) address of the elected BSR. The 625 InetAddressType is given by the bsrElectedBSRAddressType 626 object." 627 ::= { bsrElectedBSREntry 3 } 629 bsrElectedBSRPriority OBJECT-TYPE 630 SYNTAX Unsigned32 (0..255) 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The priority value for the elected BSR for this address 635 type. Numerically higher values for this object indicate 636 higher priorities." 637 ::= { bsrElectedBSREntry 4 } 639 bsrElectedBSRHashMaskLength OBJECT-TYPE 640 SYNTAX Unsigned32 (0..128) 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The hash mask length (used in the RP hash function) 645 advertised by the elected BSR for this zone." 646 ::= { bsrElectedBSREntry 5 } 648 bsrElectedBSRExpiryTime OBJECT-TYPE 649 SYNTAX TimeTicks 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "The minimum time remaining before the elected BSR for 654 this zone will be declared down." 655 ::= { bsrElectedBSREntry 6 } 657 -- 658 -- PIM BSR Traps 659 -- 661 bsrElectedBSRLostElection NOTIFICATION-TYPE 662 OBJECTS { bsrCandidateBSRElectedBSR } 663 STATUS current 664 DESCRIPTION 665 "A bsrElectedBSRLostElection trap should be generated 666 when current E-BSR lost election to a new Candidate 667 BSR. Only an E-BSR should generate this trap. 669 This notification is generated when 670 bsrCandidateBSRElectedBSR becomes FALSE." 672 REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" 673 ::= { pimBsrTraps 1 } 675 bsrCandidateBSRWinElection NOTIFICATION-TYPE 676 OBJECTS { bsrCandidateBSRElectedBSR } 677 STATUS current 678 DESCRIPTION 679 "A bsrCandidateBSRWinElection trap should be generated 680 when a C-BSR wins BSR Election. Only an E-BSR should 681 generate this trap. 683 This notification is generated when 684 bsrCandidateBSRElectedBSR becomes TRUE" 686 REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" 687 ::= { pimBsrTraps 2 } 689 -- 690 -- Conformance Information 691 -- 693 pimBsrMIBConformance OBJECT IDENTIFIER ::= { pimBsrMIB 2 } 694 pimBsrMIBCompliances OBJECT IDENTIFIER ::= { pimBsrMIBConformance 1 } 695 pimBsrMIBGroups OBJECT IDENTIFIER ::= { pimBsrMIBConformance 2 } 697 -- 698 -- Compliance Statements 699 -- 701 pimBsrMIBCompliance MODULE-COMPLIANCE 702 STATUS current 703 DESCRIPTION 704 "The compliance statement for PIM routers which implement 705 Bootstrap Router (BSR) mechanism." 706 MODULE -- this module 707 MANDATORY-GROUPS { pimBsrObjectGroup } 709 GROUP pimBsrDiagnosticsGroup 710 DESCRIPTION 711 "This group is optional." 713 ::= { pimBsrMIBCompliances 1 } 715 -- 716 -- Units of Conformance 717 -- 719 pimBsrObjectGroup OBJECT-GROUP 720 OBJECTS { bsrCandidateRPBidir, 721 bsrCandidateRPAdvTimer, 722 bsrCandidateRPPriority, 723 bsrCandidateRPAdvInterval, 724 bsrCandidateRPHoldtime, 725 bsrCandidateRPStatus, 726 bsrElectedBSRRPSetPriority, 727 bsrElectedBSRRPSetHoldtime, 728 bsrElectedBSRRPSetExpiryTime, 729 bsrElectedBSRRPSetGrpBidir, 730 bsrCandidateBSRAddress, 731 bsrCandidateBSRPriority, 732 bsrCandidateBSRHashMaskLength, 733 bsrCandidateBSRElectedBSR, 734 bsrCandidateBSRBootstrapTimer, 735 bsrCandidateBSRStatus, 736 bsrElectedBSRAddress, 737 bsrElectedBSRPriority, 738 bsrElectedBSRHashMaskLength, 739 bsrElectedBSRExpiryTime } 740 STATUS current 741 DESCRIPTION 742 "A collection of objects for managing the Bootstrap 743 Router (BSR) mechanism for PIM routers." 744 ::= { pimBsrMIBGroups 1 } 746 pimBsrDiagnosticsGroup NOTIFICATION-GROUP 747 NOTIFICATIONS { bsrElectedBSRLostElection, 748 bsrCandidateBSRWinElection } 749 STATUS current 750 DESCRIPTION 751 "Objects providing additional diagnostics related to 752 Bootstrap Router (BSR) mechanism for PIM routers." 753 ::= { pimBsrMIBGroups 2 } 755 END 757 6. Security Considerations 759 SNMP versions prior to SNMPv3 did not include adequate security. 760 Even if the network itself is secure (for example by using IPSec), 761 there is still no control over whom on the secure network is allowed 762 to access (read/change/create/delete) the objects in this MIB module. 763 The support for SET operations in a non-secure environment without 764 proper protection can have a negative effect on network operations. 766 In this MIB module, possible effects that can be induced by SET 767 operations on writable objects include: 769 o A new Candidate BSR with high priority or modification of priority 770 of an existing candidate BSR can takeover the functionality of 771 Elected BSR which can prevent and disrupt the services. 773 o A new Candidate RP with lower priority or modification of priority 774 of an existing Candidate RP can force other routers to select 775 itself for a particular group prefix. This can prevent and 776 disrupt the services provided through this group prefix. 778 The following are the read-write and read-create objects defined in 779 this MIB module: 781 bsrCandidateRPBidir 782 bsrCandidateRPPriority 783 bsrCandidateRPAdvInterval 784 bsrCandidateRPHoldtime 785 bsrCandidateBSRAddressType 786 bsrCandidateBSRAddress 787 bsrCandidateBSRPriority 788 bsrCandidateBSRHashMaskLength 790 Some of the readable objects in this MIB module (i.e., objects with a 791 MAX-ACCESS other than not-accessible) may be considered sensitive or 792 vulnerable in some network environments. It is thus important to 793 control even GET and/or NOTIFY access to these objects and possibly 794 to even encrypt the values of these objects when sending them over 795 the network via SNMP. 797 In this MIB module, possible effects that can be induced by GET 798 and/or NOTIFY operations include: 800 o Determination of Elected BSR, Candidate BSRs and Candidate RPs in 801 the Multicast Network topology. This information may be sensitive 802 and may be used in preparation for DoS attacks including any of 803 the attacks described above. 805 SNMP versions prior to SNMPv3 did not include adequate security. 806 Even if the network itself is secure (for example by using IPSec), 807 there is still no control over whom on the secure network is allowed 808 to access (read/change/create/delete) the objects in this MIB module. 810 It is RECOMMENDED that implementers consider the security features as 811 provided by the SNMPv3 framework (see [RFC3410], section 8), 812 including full support for the SNMPv3 cryptographic mechanisms (for 813 authentication and privacy). 815 Further, deployment of SNMP versions prior to SNMPv3 is NOT 816 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 817 enable cryptographic security. It is then a customer/operator 818 responsibility to ensure that the SNMP entity giving access to an 819 instance of this MIB module is properly configured to give access to 820 the objects only to those principals (users) that have legitimate 821 rights to access (read/change/create/delete) them. 823 7. IANA Considerations 825 PIM-BSR-MIB should be rooted under the mib-2 subtree. IANA is 826 requested to assign { mib-2 XXX } to the PIM-BSR-MIB module specified 827 in this document. 829 8. Acknowledgments 831 This MIB module is based on the original work in 832 [I-D.ietf-pim-mib-v2] by R. Sivaramu, J. Lingard and B. Joshi. 834 Many thanks to Stig, Nidhi and David Mcwalter for their feedback on 835 this MIB module. 837 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 838 been used for comparison while editing this MIB module. 840 9. References 842 9.1. Normative References 844 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 845 Requirement Levels", BCP 14, RFC 2119, March 1997. 847 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 848 RFC 2365, July 1998. 850 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 851 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 852 October 1998. 854 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 855 Schoenwaelder, Ed., "Structure of Management Information 856 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 858 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 859 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 860 STD 58, RFC 2579, April 1999. 862 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 863 "Conformance Statements for SMIv2", STD 58, RFC 2580, 864 April 1999. 866 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 867 MIB", RFC 2863, June 2000. 869 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 870 Schoenwaelder, "Textual Conventions for Internet Network 871 Addresses", RFC 4001, February 2005. 873 [I-D.ietf-pim-sm-v2-new] 874 Fenner, B., "Protocol Independent Multicast - Sparse Mode 875 (PIM-SM): Protocol Specification (Revised)", 876 draft-ietf-pim-sm-v2-new-12 (work in progress), 877 March 2006. 879 [I-D.ietf-pim-mib-v2] 880 Lingard, J., "Protocol Independent Multicast MIB", 881 draft-ietf-pim-mib-v2-06 (work in progress), April 2006. 883 [I-D.ietf-pim-sm-bsr] 884 Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", 885 draft-ietf-pim-sm-bsr-08 (work in progress), May 2006. 887 [I-D.ietf-mboned-ip-mcast-mib] 888 McWalter, D., "IP Multicast MIB", 889 draft-ietf-mboned-ip-mcast-mib-03 (work in progress), 890 August 2006. 892 9.2. Informative References 894 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 895 "Introduction and Applicability Statements for Internet- 896 Standard Management Framework", RFC 3410, December 2002. 898 Authors' Addresses 900 Bharat joshi 901 Infosys Technologies Ltd. 902 44 Electronics City, Hosur Road 903 Bangalore 560 100 904 India 906 Email: bharat_joshi@infosys.com 907 URI: http://www.infosys.com/ 909 Raina Bijlani 910 Cisco Systems 911 170 W.Tasman Drive 912 San Jose CA 95134 913 USA 915 Email: rainab@cisco.com 917 Intellectual Property Statement 919 The IETF takes no position regarding the validity or scope of any 920 Intellectual Property Rights or other rights that might be claimed to 921 pertain to the implementation or use of the technology described in 922 this document or the extent to which any license under such rights 923 might or might not be available; nor does it represent that it has 924 made any independent effort to identify any such rights. Information 925 on the procedures with respect to rights in RFC documents can be 926 found in BCP 78 and BCP 79. 928 Copies of IPR disclosures made to the IETF Secretariat and any 929 assurances of licenses to be made available, or the result of an 930 attempt made to obtain a general license or permission for the use of 931 such proprietary rights by implementers or users of this 932 specification can be obtained from the IETF on-line IPR repository at 933 http://www.ietf.org/ipr. 935 The IETF invites any interested party to bring to its attention any 936 copyrights, patents or patent applications, or other proprietary 937 rights that may cover technology that may be required to implement 938 this standard. Please address the information to the IETF at 939 ietf-ipr@ietf.org. 941 Disclaimer of Validity 943 This document and the information contained herein are provided on an 944 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 945 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 946 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 947 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 948 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 949 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 951 Copyright Statement 953 Copyright (C) The Internet Society (2006). This document is subject 954 to the rights, licenses and restrictions contained in BCP 78, and 955 except as set forth therein, the authors retain all their rights. 957 Acknowledgment 959 Funding for the RFC Editor function is currently provided by the 960 Internet Society.