idnits 2.17.1 draft-mcwalter-pim-bsr-mib-01.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 808. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 785. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 792. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 798. ** 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 (June 16, 2006) is 6524 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 711, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 714, 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 Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF B. Joshi 3 Internet-Draft Infosys Technologies Ltd. 4 Expires: December 18, 2006 D. McWalter 5 Data Connection Ltd 6 June 16, 2006 8 PIM Bootstrap Router MIB 9 draft-mcwalter-pim-bsr-mib-01.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 December 18, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it describes managed objects used for managing the 45 Bootstrap Router (BSR) mechanism for PIM. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 54 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 55 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 56 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 57 8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 58 8.2. Informative References . . . . . . . . . . . . . . . . . . 17 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 60 Intellectual Property and Copyright Statements . . . . . . . . . . 19 62 1. Introduction 64 This memo defines a portion of the Management Information Base (MIB) 65 for use with network management protocols in the Internet community. 66 In particular, it describes managed objects used for managing the 67 Bootstrap Router (BSR) mechanism for PIM. [I-D.ietf-pim-sm-v2-new], 68 [I-D.ietf-pim-sm-bsr]. 70 This draft was created by the removal of BSR MIB support from the 71 draft PIM MIB [I-D.ietf-pim-mib-v2]. 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in [RFC2119]. 77 2. The Internet-Standard Management Framework 79 For a detailed overview of the documents that describe the current 80 Internet-Standard Management Framework, please refer to section 7 of 81 [RFC3410]. 83 Managed objects are accessed via a virtual information store, termed 84 the Management Information Base or MIB. MIB objects are generally 85 accessed through the Simple Network Management Protocol (SNMP). 86 Objects in the MIB are defined using the mechanisms defined in the 87 Structure of Management Information (SMI). This memo specifies a MIB 88 module that is compliant to the SMIv2, which is described in STD 58, 89 [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 91 3. Overview 93 This MIB module contains four tables. The tables are: 95 1. The BSR Candidate-RP Table, which contains one row for each 96 multicast group address prefix for which the local router is to 97 advertise itself as a Candidate-RP. 99 2. The BSR RP-Set Table, which contains one row for each group 100 mapping that was learned via BSR. 102 3. The BSR Candidate-BSR Table, which contains one roe for each 103 Candidate-BSR configuration for the local router. 105 4. The BSR Elected BSR Table, which contains one row for each 106 elected BSR. 108 This MIB module uses textual conventions defined in the IF-MIB 109 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 111 4. Definitions 113 PIM-BSR-MIB DEFINITIONS ::= BEGIN 115 IMPORTS 116 MODULE-IDENTITY, OBJECT-TYPE, 117 mib-2, Unsigned32, TimeTicks FROM SNMPv2-SMI 118 RowStatus, TruthValue FROM SNMPv2-TC 119 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 120 InetAddressType, 121 InetAddressPrefixLength, 122 InetAddress FROM INET-ADDRESS-MIB 124 pimBsrMIB MODULE-IDENTITY 125 LAST-UPDATED "200606160000Z" -- 16 June 2006 126 ORGANIZATION "IETF PIM Working Group" 127 CONTACT-INFO 128 "Email: pim@ietf.org" 129 DESCRIPTION 130 "The MIB module for management of the Bootstrap Router 131 (BSR) mechanism for PIM routers. 133 Copyright (C) The Internet Society (2006). This version 134 of this MIB module is part of RFC yyyy; see the RFC 135 itself for full legal notices." 136 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 137 REVISION "200606160000Z" -- 16 June 2006 138 DESCRIPTION "Initial version, published as RFC yyyy." 139 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 140 ::= { mib-2 XXX } 141 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 143 -- 144 -- Top-level structure 145 -- 147 pimBsrMIBObjects OBJECT IDENTIFIER ::= { pimBsrMIB 1 } 148 pimBsrTraps OBJECT IDENTIFIER ::= { pimBsrMIBObjects 0 } 149 pimBsr OBJECT IDENTIFIER ::= { pimBsrMIBObjects 1 } 151 -- 152 -- The BSR Candidate-RP Table 153 -- 154 bsrCandidateRPTable OBJECT-TYPE 155 SYNTAX SEQUENCE OF BsrCandidateRPEntry 156 MAX-ACCESS not-accessible 157 STATUS current 158 DESCRIPTION 159 "The (conceptual) table listing the IP multicast group 160 prefixes for which the local router is to advertise 161 itself as a Candidate-RP." 162 ::= { pimBsr 1 } 164 bsrCandidateRPEntry OBJECT-TYPE 165 SYNTAX BsrCandidateRPEntry 166 MAX-ACCESS not-accessible 167 STATUS current 168 DESCRIPTION 169 "An entry (conceptual row) in the bsrCandidateRPTable." 170 INDEX { bsrCandidateRPAddressType, 171 bsrCandidateRPAddress, 172 bsrCandidateRPGroupAddress, 173 bsrCandidateRPGroupPrefixLength } 174 ::= { bsrCandidateRPTable 1 } 176 BsrCandidateRPEntry ::= SEQUENCE { 177 bsrCandidateRPAddressType InetAddressType, 178 bsrCandidateRPAddress InetAddress, 179 bsrCandidateRPGroupAddress InetAddress, 180 bsrCandidateRPGroupPrefixLength InetAddressPrefixLength, 181 bsrCandidateRPBidir TruthValue, 182 bsrCandidateRPAdvTimer TimeTicks 183 bsrCandidateRPStatus RowStatus 184 } 186 bsrCandidateRPAddressType OBJECT-TYPE 187 SYNTAX InetAddressType 188 MAX-ACCESS not-accessible 189 STATUS current 190 DESCRIPTION 191 "The Inet address type of the Candidate-RP." 192 ::= { bsrCandidateRPEntry 1 } 194 bsrCandidateRPAddress OBJECT-TYPE 195 SYNTAX InetAddress (SIZE (4|8|16|20)) 196 MAX-ACCESS not-accessible 197 STATUS current 198 DESCRIPTION 199 "The (unicast) address which will be advertised as a 200 Candidate-RP. The InetAddressType is given by the 201 bsrCandidateRPAddressType object." 203 ::= { bsrCandidateRPEntry 2 } 205 bsrCandidateRPGroupAddress OBJECT-TYPE 206 SYNTAX InetAddress (SIZE (4|8|16|20)) 207 MAX-ACCESS not-accessible 208 STATUS current 209 DESCRIPTION 210 "The IP multicast group address which, when combined with 211 the corresponding value of 212 bsrCandidateRPGroupPrefixLength, identifies a group 213 prefix for which the local router will advertise itself 214 as a Candidate-RP. The InetAddressType is given by the 215 bsrCandidateRPAddressType object." 216 ::= { bsrCandidateRPEntry 3 } 218 bsrCandidateRPGroupPrefixLength OBJECT-TYPE 219 SYNTAX InetAddressPrefixLength (4..128) 220 MAX-ACCESS not-accessible 221 STATUS current 222 DESCRIPTION 223 "The multicast group address mask which, when combined 224 with the corresponding value of 225 bsrCandidateRPGroupAddress, identifies a group prefix 226 for which the local router will advertise itself as a 227 Candidate-RP. The InetAddressType is given by the 228 bsrCandidateRPAddressType object." 229 ::= { bsrCandidateRPEntry 4 } 231 bsrCandidateRPBidir OBJECT-TYPE 232 SYNTAX TruthValue 233 MAX-ACCESS read-create 234 STATUS current 235 DESCRIPTION 236 "If this object is set to TRUE, this group range is 237 advertised with this RP as a BIDIR-PIM group range. If 238 it is set to FALSE, it is advertised as a PIM-SM group 239 range." 240 DEFVAL { FALSE } 241 ::= { bsrCandidateRPEntry 5 } 243 bsrCandidateRPAdvTimer OBJECT-TYPE 244 SYNTAX TimeTicks 245 MAX-ACCESS read-only 246 STATUS current 247 DESCRIPTION 248 "The time remaining before the local router next sends 249 a Candidate-RP-Advertisement to the elected BSR for 250 this address type." 252 ::= { bsrCandidateRPEntry 7 } 254 bsrCandidateRPStatus OBJECT-TYPE 255 SYNTAX RowStatus 256 MAX-ACCESS read-create 257 STATUS current 258 DESCRIPTION 259 "The status of this row, by which new entries may be 260 created, or old entries deleted from this table." 262 ::= { bsrCandidateRPEntry 8 } 264 -- 265 -- The BSR RP-Set Table 266 -- 268 bsrRPSetTable OBJECT-TYPE 269 SYNTAX SEQUENCE OF BsrRPSetEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "The (conceptual) table listing BSR-specific information 274 about PIM group mappings learned via BSR. There is one 275 entry in this table for every entry in the 276 pimGroupMappingTable with a pimGroupMappingOrigin value 277 of 'bsr'. [I-D.ietf-pim-mib-v2]" 278 ::= { pimBsr 2 } 280 bsrRPSetEntry OBJECT-TYPE 281 SYNTAX BsrRPSetEntry 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "An entry (conceptual row) in the bsrRPSetTable." 286 INDEX { bsrGroupMappingAddressType, 287 bsrGroupMappingGrpAddress, 288 bsrGroupMappingGrpPrefixLength, 289 bsrGroupMappingRPAddress } 290 ::= { bsrRPSetTable 1 } 292 BsrRPSetEntry ::= SEQUENCE { 293 bsrGroupMappingAddressType InetAddressType, 294 bsrGroupMappingGrpAddress InetAddress, 295 bsrGroupMappingGrpPrefixLength InetAddressPrefixLength, 296 bsrGroupMappingRPAddress InetAddress, 297 bsrRPSetPriority Unsigned32, 298 bsrRPSetHoldtime Unsigned32, 299 bsrRPSetExpiryTime TimeTicks 301 } 303 bsrGroupMappingAddressType OBJECT-TYPE 304 SYNTAX InetAddressType 305 MAX-ACCESS not-accessible 306 STATUS current 307 DESCRIPTION 308 "The Inet address type of the IP multicast group 309 prefix." 310 ::= { bsrRPSetEntry 2 } 312 bsrGroupMappingGrpAddress OBJECT-TYPE 313 SYNTAX InetAddress (SIZE (4|8|16|20)) 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "The IP multicast group address which, when combined 318 with bsrGroupMappingGrpPrefixLength, gives the group 319 prefix for this mapping. The InetAddressType is given 320 by the bsrGroupMappingAddressType object. 322 This address object is only significant up to 323 bsrGroupMappingGrpPrefixLength bits. The remainder 324 of the address bits are zero. This is especially 325 important for this field, which is part of the index of 326 this entry. Any non-zero bits would signify an entirely 327 different entry." 328 ::= { bsrRPSetEntry 3 } 330 bsrGroupMappingGrpPrefixLength OBJECT-TYPE 331 SYNTAX InetAddressPrefixLength (4..128) 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "The multicast group prefix length, which, when combined 336 with bsrGroupMappingGrpAddress, gives the group prefix 337 for this mapping. The InetAddressType is given by the 338 bsrGroupMappingAddressType object. If 339 bsrGroupMappingAddressType is 'ipv4' or 'ipv4z', this 340 object must be in the range 4..32. If 341 bsrGroupMappingAddressType is 'ipv6' or 'ipv6z', this 342 object must be in the range 8..128." 343 ::= { bsrRPSetEntry 4 } 345 bsrGroupMappingRPAddress OBJECT-TYPE 346 SYNTAX InetAddress (SIZE (4|8|16|20)) 347 MAX-ACCESS not-accessible 348 STATUS current 349 DESCRIPTION 350 "The IP address of the RP to be used for groups within 351 this group prefix. The InetAddressType is given by the 352 bsrGroupMappingAddressType object." 353 ::= { bsrRPSetEntry 5 } 355 bsrRPSetPriority OBJECT-TYPE 356 SYNTAX Unsigned32 (0..255) 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The RP Priority from the PIM Candidate-RP-Advertisement 361 message or PIM Bootstrap message by which this RP was 362 learned. Numerically higher values for this object 363 indicate lower priorities, with the value zero denoting 364 the highest priority." 365 ::= { bsrRPSetEntry 6 } 367 bsrRPSetHoldtime OBJECT-TYPE 368 SYNTAX Unsigned32 (0..65535) 369 UNITS "seconds" 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The RP Holdtime from the PIM Candidate-RP-Advertisement 374 message or PIM Bootstrap message by which this RP was 375 learned." 376 ::= { bsrRPSetEntry 7 } 378 bsrRPSetExpiryTime OBJECT-TYPE 379 SYNTAX TimeTicks 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "The minimum time remaining before this entry will be 384 aged out. The value zero indicates that this entry will 385 never be aged out." 386 ::= { bsrRPSetEntry 8 } 388 -- 389 -- The BSR Candidate-BSR Table 390 -- 392 bsrCandidateBSRTable OBJECT-TYPE 393 SYNTAX SEQUENCE OF BsrCandidateBSREntry 394 MAX-ACCESS not-accessible 395 STATUS current 396 DESCRIPTION 397 "The (conceptual) table containing Candidate-BSR 398 configuration for the local router. The table contains 399 one row for each address family for which the local 400 router is to advertise itself as a Candidate-BSR." 401 ::= { pimBsr 3 } 403 bsrCandidateBSREntry OBJECT-TYPE 404 SYNTAX BsrCandidateBSREntry 405 MAX-ACCESS not-accessible 406 STATUS current 407 DESCRIPTION 408 "An entry (conceptual row) in the bsrCandidateBSRTable." 409 INDEX { bsrCandidateBSRAddressType } 410 ::= { bsrCandidateBSRTable 1 } 412 BsrCandidateBSREntry ::= SEQUENCE { 413 bsrCandidateBSRAddressType InetAddressType, 414 bsrCandidateBSRAddress InetAddress, 415 bsrCandidateBSRPriority Unsigned32, 416 bsrCandidateBSRHashMaskLength Unsigned32, 417 bsrCandidateBSRElectedBSR TruthValue, 418 bsrCandidateBSRBootstrapTimer TimeTicks, 419 bsrCandidateBSRStatus RowStatus 420 } 422 bsrCandidateBSRAddressType OBJECT-TYPE 423 SYNTAX InetAddressType 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "The address type of the Candidate-BSR." 428 ::= { bsrCandidateBSREntry 1 } 430 bsrCandidateBSRAddress OBJECT-TYPE 431 SYNTAX InetAddress 432 MAX-ACCESS read-create 433 STATUS current 434 DESCRIPTION 435 "The (unicast) address which the local router will 436 use to advertise itself as a Candidate-BSR. The 437 InetAddressType is given by the 438 bsrCandidateBSRAddressType object." 439 ::= { bsrCandidateBSREntry 2 } 441 bsrCandidateBSRPriority OBJECT-TYPE 442 SYNTAX Unsigned32 (0..255) 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "The priority value for the local router as a 447 Candidate-BSR for this address type. Numerically higher 448 values for this object indicate higher priorities." 449 DEFVAL { 0 } 450 ::= { bsrCandidateBSREntry 3 } 452 bsrCandidateBSRHashMaskLength OBJECT-TYPE 453 SYNTAX Unsigned32 (0..128) 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "The hash mask length (used in the RP hash function) 458 that the local router will advertise in its Bootstrap 459 messages for this address type. This object defaults 460 to 30 if bsrCandidateBSRAddressType is 'ipv4' or 'ipv4z' 461 , and defaults to 126 if bsrCandidateBSRAddressType is 462 'ipv6' or 'ipv6z'." 463 -- DEFVAL { 30 or 126 } 464 ::= { bsrCandidateBSREntry 4 } 466 bsrCandidateBSRElectedBSR OBJECT-TYPE 467 SYNTAX TruthValue 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "Whether the local router is the elected BSR for this 472 address type." 473 ::= { bsrCandidateBSREntry 5 } 475 bsrCandidateBSRBootstrapTimer OBJECT-TYPE 476 SYNTAX TimeTicks 477 MAX-ACCESS read-only 478 STATUS current 479 DESCRIPTION 480 "The time remaining before the local router next 481 originates a Bootstrap message for this address type. 482 Value of this object is zero if 483 bsrCandidateBSRElectedBSR is 'FALSE'." 484 ::= { bsrCandidateBSREntry 6 } 486 bsrCandidateBSRStatus OBJECT-TYPE 487 SYNTAX RowStatus 488 MAX-ACCESS read-create 489 STATUS current 490 DESCRIPTION 491 "The status of this row, by which new entries may 492 be created, or old entries deleted from this table." 494 ::= { bsrCandidateBSREntry 7 } 496 -- 497 -- The BSR Elected-BSR Table 498 -- 500 bsrElectedBSRTable OBJECT-TYPE 501 SYNTAX SEQUENCE OF BsrElectedBSREntry 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "The (conceptual) table containing information about 506 elected BSRs. The table contains one row for each 507 address family for which there is an elected BSR." 508 ::= { pimBsr 4 } 510 bsrElectedBSREntry OBJECT-TYPE 511 SYNTAX BsrElectedBSREntry 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "An entry (conceptual row) in the bsrElectedBSRTable." 516 INDEX { bsrElectedBSRAddressType } 517 ::= { bsrElectedBSRTable 1 } 519 BsrElectedBSREntry ::= SEQUENCE { 520 bsrElectedBSRAddressType InetAddressType, 521 bsrElectedBSRAddress InetAddress, 522 bsrElectedBSRPriority Unsigned32, 523 bsrElectedBSRHashMaskLength Unsigned32, 524 bsrElectedBSRExpiryTime TimeTicks, 525 } 527 bsrElectedBSRAddressType OBJECT-TYPE 528 SYNTAX InetAddressType 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "The address type of the elected BSR." 533 ::= { bsrElectedBSREntry 1 } 535 bsrElectedBSRAddress OBJECT-TYPE 536 SYNTAX InetAddress (SIZE (4|8|16|20)) 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "The (unicast) address of the elected BSR. The 541 InetAddressType is given by the bsrElectedBSRAddressType 542 object." 543 ::= { bsrElectedBSREntry 2 } 545 bsrElectedBSRPriority OBJECT-TYPE 546 SYNTAX Unsigned32 (0..255) 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The priority value for the elected BSR for this address 551 type. Numerically higher values for this object indicate 552 higher priorities." 553 ::= { bsrElectedBSREntry 3 } 555 bsrElectedBSRHashMaskLength OBJECT-TYPE 556 SYNTAX Unsigned32 (0..128) 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The hash mask length (used in the RP hash function) 561 advertised by the elected BSR for this address type." 562 ::= { bsrElectedBSREntry 4 } 564 bsrElectedBSRExpiryTime OBJECT-TYPE 565 SYNTAX TimeTicks 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "The minimum time remaining before the elected BSR for 570 this address type will be declared down." 571 ::= { bsrElectedBSREntry 5 } 573 -- 574 -- PIM BSR Traps 575 -- 577 bsrElectedBSRLostElection NOTIFICATION-TYPE 578 OBJECTS { bsrCandidateBSRElectedBSR } 579 STATUS current 580 DESCRIPTION 581 "A bsrElectedBSRLostElection trap should be generated 582 when current E-BSR lost election to a new Candidate 583 BSR 584 current E-BSR, start sending BootStrap Messages. Only 585 an E-BSR should generate this trap. 587 This notification is generated when 588 bsrCandidateBSRElectedBSR becomes FALSE." 590 REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" 591 ::= { pimBsrTraps 1 } 593 bsrCandidateBSRWinElection NOTIFICATION-TYPE 594 OBJECTS { bsrCandidateBSRElectedBSR } 595 STATUS current 596 DESCRIPTION 597 "A bsrCandidateBSRWinElection trap should be generated 598 when a C-BSR wins BSR Election. Only an E-BSR should 599 generate this trap. 601 This notification is generated when 602 bsrCandidateBSRElectedBSR becomes TRUE" 604 REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" 605 ::= { pimBsrTraps 2 } 607 -- 608 -- Conformance Information 609 -- 611 pimBsrMIBConformance OBJECT IDENTIFIER ::= { pimBsrMIB 2 } 612 pimBsrMIBCompliances OBJECT IDENTIFIER ::= { pimBsrMIBConformance 1 } 613 pimBsrMIBGroups OBJECT IDENTIFIER ::= { pimBsrMIBConformance 2 } 615 -- 616 -- Compliance Statements 617 -- 619 pimBsrMIBCompliance MODULE-COMPLIANCE 620 STATUS current 621 DESCRIPTION 622 "The compliance statement for PIM routers which implement 623 the PIM BSR MIB." 624 MODULE -- this module 625 MANDATORY-GROUPS { pimBsrObjectGroup } 627 GROUP pimBsrDiagnosticsGroup 628 DESCRIPTION 629 "This group is optional." 631 ::= { pimBsrMIBCompliances 1 } 633 -- 634 -- Units of Conformance 635 -- 637 pimBsrObjectGroup OBJECT-GROUP 638 OBJECTS { bsrCandidateRPBidir, 639 bsrCandidateRPAdvTimer, 640 bsrCandidateRPStatus, 641 bsrRPSetPriority, 642 bsrRPSetHoldtime, 643 bsrRPSetExpiryTime, 644 bsrCandidateBSRAddress, 645 bsrCandidateBSRPriority, 646 bsrCandidateBSRHashMaskLength, 647 bsrCandidateBSRElectedBSR, 648 bsrCandidateBSRBootstrapTimer, 649 bsrCandidateBSRStatus, 650 bsrElectedBSRAddress, 651 bsrElectedBSRPriority, 652 bsrElectedBSRHashMaskLength, 653 bsrElectedBSRExpiryTime } 654 STATUS current 655 DESCRIPTION 656 "A collection of objects for managing PIM routers." 657 ::= { pimBsrMIBGroups 1 } 659 pimBsrDiagnosticsGroup OBJECT-GROUP 660 OBJECTS { bsrElectedBSRLostElection, 661 bsrCandidateBSRWinElection } 662 STATUS current 663 DESCRIPTION 664 "Objects providing additonal diagnostics related to BSR 665 mechanism of PIM router." 666 ::= { pimBsrMIBGroups 2 } 668 END 670 5. Security Considerations 672 SNMP versions prior to SNMPv3 did not include adequate security. 673 Even if the network itself is secure (for example by using IPSec), 674 there is still no control over whom on the secure network is allowed 675 to access (read/change/create/delete) the objects in this MIB module. 677 It is RECOMMENDED that implementers consider the security features as 678 provided by the SNMPv3 framework (see [RFC3410], section 8), 679 including full support for the SNMPv3 cryptographic mechanisms (for 680 authentication and privacy). 682 Further, deployment of SNMP versions prior to SNMPv3 is NOT 683 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 684 enable cryptographic security. It is then a customer/operator 685 responsibility to ensure that the SNMP entity giving access to an 686 instance of this MIB module is properly configured to give access to 687 the objects only to those principals (users) that have legitimate 688 rights to access (read/change/create/delete) them. 690 6. IANA Considerations 692 PIM-BSR-MIB should be rooted under the mib-2 subtree. IANA is 693 requested to assign { mib-2 XXX } to the PIM-BSR-MIB module specified 694 in this document. 696 7. Acknowledgements 698 This MIB module is based on the original work in 699 [I-D.ietf-pim-mib-v2] by R. Sivaramu, J. Lingard and B. Joshi. 701 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 702 been used for comparison while editing this MIB module. 704 8. References 706 8.1. Normative References 708 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 709 Requirement Levels", BCP 14, RFC 2119, March 1997. 711 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 712 RFC 2365, July 1998. 714 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 715 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 716 October 1998. 718 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 719 Schoenwaelder, Ed., "Structure of Management Information 720 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 722 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 723 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 724 STD 58, RFC 2579, April 1999. 726 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 727 "Conformance Statements for SMIv2", STD 58, RFC 2580, 728 April 1999. 730 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 731 MIB", RFC 2863, June 2000. 733 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 734 Schoenwaelder, "Textual Conventions for Internet Network 735 Addresses", RFC 4001, February 2005. 737 [I-D.ietf-pim-sm-v2-new] 738 Fenner, B., "Protocol Independent Multicast - Sparse Mode 739 (PIM-SM): Protocol Specification (Revised)", 740 draft-ietf-pim-sm-v2-new-12 (work in progress), 741 March 2006. 743 [I-D.ietf-pim-mib-v2] 744 Lingard, J., "Protocol Independent Multicast MIB", 745 draft-ietf-pim-mib-v2-06 (work in progress), April 2006. 747 [I-D.ietf-pim-sm-bsr] 748 Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", 749 draft-ietf-pim-sm-bsr-08 (work in progress), May 2006. 751 8.2. Informative References 753 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 754 "Introduction and Applicability Statements for Internet- 755 Standard Management Framework", RFC 3410, December 2002. 757 Authors' Addresses 759 Bharat joshi 760 Infosys Technologies Ltd. 761 44 Electronics City, Hosur Road 762 Bangalore 560 100 763 India 765 Email: bharat_joshi@infosys.com 766 URI: http://www.infosys.com/ 768 David McWalter 769 Data Connection Ltd 770 100 Church Street 771 Enfield EN2 6BQ 772 UK 774 Email: dmcw@dataconnection.com 776 Intellectual Property Statement 778 The IETF takes no position regarding the validity or scope of any 779 Intellectual Property Rights or other rights that might be claimed to 780 pertain to the implementation or use of the technology described in 781 this document or the extent to which any license under such rights 782 might or might not be available; nor does it represent that it has 783 made any independent effort to identify any such rights. Information 784 on the procedures with respect to rights in RFC documents can be 785 found in BCP 78 and BCP 79. 787 Copies of IPR disclosures made to the IETF Secretariat and any 788 assurances of licenses to be made available, or the result of an 789 attempt made to obtain a general license or permission for the use of 790 such proprietary rights by implementers or users of this 791 specification can be obtained from the IETF on-line IPR repository at 792 http://www.ietf.org/ipr. 794 The IETF invites any interested party to bring to its attention any 795 copyrights, patents or patent applications, or other proprietary 796 rights that may cover technology that may be required to implement 797 this standard. Please address the information to the IETF at 798 ietf-ipr@ietf.org. 800 Disclaimer of Validity 802 This document and the information contained herein are provided on an 803 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 804 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 805 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 806 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 807 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 808 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 810 Copyright Statement 812 Copyright (C) The Internet Society (2006). This document is subject 813 to the rights, licenses and restrictions contained in BCP 78, and 814 except as set forth therein, the authors retain all their rights. 816 Acknowledgment 818 Funding for the RFC Editor function is currently provided by the 819 Internet Society.