draft-ietf-pim-bsr-mib-06.txt   rfc5240.txt 
PIM WG B. Joshi Network Working Group B. Joshi
Internet-Draft Infosys Technologies Ltd. Request for Comments: 5240 Infosys Technologies Ltd.
Expires: November 6, 2008 R. Bijlani Category: Standards Track R. Bijlani
May 5, 2008 Protocol Independent Multicast (PIM) Bootstrap Router MIB
PIM Bootstrap Router MIB
draft-ietf-pim-bsr-mib-06.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 6, 2008.
Copyright Notice Status of This Memo
Copyright (C) The IETF Trust (2008). This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing the Bootstrap Router (BSR) mechanism for PIM (Protocol managing the Bootstrap Router (BSR) mechanism for PIM (Protocol
Independent Multicast). Independent Multicast).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 22 9.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Bootstrap Router (BSR) mechanism for PIM [RFC4601], [RFC5059]. Bootstrap Router (BSR) mechanism for PIM [RFC4601], [RFC5059].
This document was created by moving some of the PIM BSR specific MIB This document was created by moving some of the PIM BSR-specific MIB
tables from one of the earlier version of PIM MIB [RFC5060]. tables from one of the earlier versions of PIM MIB [RFC5060].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410[RFC3410]. RFC 3410[RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 42 skipping to change at page 2, line 42
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
This MIB module contains four tables. The tables are: This MIB module contains four tables. The tables are:
1. The Candidate-RP Table, which contains one row for each multicast 1. The Candidate-RP Table, which contains one row for each multicast
group address prefix for which the local router is configured to group address prefix for which the local router is configured to
advertise itself as a Candidate-RP. This table exists on routers advertise itself as a Candidate-RP (C-RP). This table exists on
that are configured as Candidate-RP. routers that are configured as Candidate-RP.
2. The Elected BSR RP-Set Table, which contains one row for each 2. The Elected BSR RP-Set Table, which contains one row for each
Group-to-RP mapping that was received in C-RP advertisements. Group-to-RP mapping that was received in C-RP advertisements.
This table exists on a router that is an elected BSR. This table exists on a router that is an elected BSR (E-BSR).
3. The Candidate-BSR Table, which contains one row for each 3. The Candidate-BSR Table, which contains one row for each
Candidate-BSR configuration for the local router. This table Candidate-BSR configuration for the local router. This table
exists on routers that are configured as Candidate-BSR. exists on routers that are configured as Candidate-BSR.
4. The Elected BSR Table, which contains one row for each elected 4. The Elected-BSR Table, which contains one row for each elected
BSR. This table exists on a router that is an elected BSR. BSR. This table exists on a router that is an elected BSR.
This MIB module uses textual conventions defined in the INET-ADDRESS- This MIB module uses textual conventions defined in the INET-ADDRESS-
MIB [RFC4001]. MIB [RFC4001].
5. Definitions 5. Definitions
PIM-BSR-MIB DEFINITIONS ::= BEGIN PIM-BSR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
skipping to change at page 4, line 44 skipping to change at page 3, line 40
"IETF Protocol Independent Multicast (PIM) Working Group" "IETF Protocol Independent Multicast (PIM) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pim@ietf.org "Email: pim@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/pim-charter.html" http://www.ietf.org/html.charters/pim-charter.html"
DESCRIPTION DESCRIPTION
"The MIB module for management of the Bootstrap Router "The MIB module for management of the Bootstrap Router
(BSR) mechanism for PIM routers. (BSR) mechanism for PIM routers.
Copyright (C) The IETF Trust (2008). This version Copyright (C) The IETF Trust (2008). This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC 5240; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note DESCRIPTION "Initial version, published as RFC 5240."
DESCRIPTION "Initial version, published as RFC yyyy." ::= { mib-2 172 }
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note
-- --
-- Top-level structure -- Top-level structure
-- --
pimBsrNotifications OBJECT IDENTIFIER ::= { pimBsrMIB 0 } pimBsrNotifications OBJECT IDENTIFIER ::= { pimBsrMIB 0 }
pimBsrObjects OBJECT IDENTIFIER ::= { pimBsrMIB 1 } pimBsrObjects OBJECT IDENTIFIER ::= { pimBsrMIB 1 }
-- --
-- Conformance Information -- Conformance Information
-- --
pimBsrConformance OBJECT IDENTIFIER ::= { pimBsrMIB 2 } pimBsrConformance OBJECT IDENTIFIER ::= { pimBsrMIB 2 }
pimBsrCompliances OBJECT IDENTIFIER ::= { pimBsrConformance 1 } pimBsrCompliances OBJECT IDENTIFIER ::= { pimBsrConformance 1 }
pimBsrGroups OBJECT IDENTIFIER ::= { pimBsrConformance 2 } pimBsrGroups OBJECT IDENTIFIER ::= { pimBsrConformance 2 }
-- --
-- The BSR Candidate-RP Table -- The BSR Candidate-RP Table
skipping to change at page 7, line 44 skipping to change at page 6, line 34
"The time remaining before the local router next sends "The time remaining before the local router next sends
a Candidate-RP-Advertisement to the elected BSR for a Candidate-RP-Advertisement to the elected BSR for
this zone." this zone."
::= { pimBsrCandidateRPEntry 6 } ::= { pimBsrCandidateRPEntry 6 }
pimBsrCandidateRPPriority OBJECT-TYPE pimBsrCandidateRPPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority for this Candidate RP advertised in "The priority for this Candidate-RP advertised in
Candidate-RP-Advertisements." Candidate-RP-Advertisements."
REFERENCE "RFC5059 section 3.2" REFERENCE "RFC 5059, section 3.2"
DEFVAL { 192 } DEFVAL { 192 }
::= { pimBsrCandidateRPEntry 7 } ::= { pimBsrCandidateRPEntry 7 }
pimBsrCandidateRPAdvInterval OBJECT-TYPE pimBsrCandidateRPAdvInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..26214) SYNTAX Unsigned32 (1..26214)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Candidate RP generates Candidate-RP-Advertisements "A Candidate-RP generates Candidate-RP-Advertisements
periodically. This object represents the time interval periodically. This object represents the time interval
in seconds between two consecutive advertisements." in seconds between two consecutive advertisements."
REFERENCE "RFC5059 section 3.2 and section 5" REFERENCE "RFC 5059, sections 3.2 and 5"
DEFVAL { 60 } DEFVAL { 60 }
::= { pimBsrCandidateRPEntry 8 } ::= { pimBsrCandidateRPEntry 8 }
pimBsrCandidateRPHoldtime OBJECT-TYPE pimBsrCandidateRPHoldtime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Holdtime for this Candidate RP. The amount of time (in "Holdtime for this Candidate-RP. The amount of time (in
seconds) this Candidate-RP entry is valid. seconds) this Candidate-RP entry is valid.
This object's value can be zero only when this C-RP is This object's value can be zero only when this C-RP is
shutting down" shutting down."
REFERENCE "RFC5059 section 4.2" REFERENCE "RFC 5059, section 4.2"
DEFVAL { 150 } DEFVAL { 150 }
::= { pimBsrCandidateRPEntry 9 } ::= { pimBsrCandidateRPEntry 9 }
pimBsrCandidateRPStatus OBJECT-TYPE pimBsrCandidateRPStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table. created, or old entries deleted from this table.
This status object can be set to active(1) without This status object can be set to active(1) without
setting any other columnar objects in this entry setting any other columnar objects in this entry.
All writable objects in this entry can be modified All writable objects in this entry can be modified
when the status of this entry is active(1)." when the status of this entry is active(1)."
::= { pimBsrCandidateRPEntry 10 } ::= { pimBsrCandidateRPEntry 10 }
pimBsrCandidateRPStorageType OBJECT-TYPE pimBsrCandidateRPStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 9, line 29 skipping to change at page 8, line 18
SYNTAX SEQUENCE OF PimBsrElectedBSRRPSetEntry SYNTAX SEQUENCE OF PimBsrElectedBSRRPSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing BSR-specific information "The (conceptual) table listing BSR-specific information
about PIM group mappings learned via C-RP advertisements about PIM group mappings learned via C-RP advertisements
or created locally using configurations. This table is or created locally using configurations. This table is
maintained only on the Elected BSR. maintained only on the Elected BSR.
An Elected BSR uses this table to create Bootstrap An Elected BSR uses this table to create Bootstrap
Messages after applying a local policy to include some messages after applying a local policy to include some
or all of the group mappings in this table." or all of the group mappings in this table."
::= { pimBsrObjects 2 } ::= { pimBsrObjects 2 }
pimBsrElectedBSRRPSetEntry OBJECT-TYPE pimBsrElectedBSRRPSetEntry OBJECT-TYPE
SYNTAX PimBsrElectedBSRRPSetEntry SYNTAX PimBsrElectedBSRRPSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the "An entry (conceptual row) in the
skipping to change at page 10, line 24 skipping to change at page 9, line 13
DESCRIPTION DESCRIPTION
"The Inet address type of the IP multicast group "The Inet address type of the IP multicast group
prefix." prefix."
::= { pimBsrElectedBSRRPSetEntry 2 } ::= { pimBsrElectedBSRRPSetEntry 2 }
pimBsrElectedBSRGrpMappingGrpAddr OBJECT-TYPE pimBsrElectedBSRGrpMappingGrpAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE (4|8|16|20)) SYNTAX InetAddress (SIZE (4|8|16|20))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address which, when combined "The IP multicast group address that, when combined
with pimBsrElectedBSRGrpMappingGrpPrefixLen, gives the with pimBsrElectedBSRGrpMappingGrpPrefixLen, gives the
group prefix for this mapping. The InetAddressType is group prefix for this mapping. The InetAddressType is
given by the pimBsrElectedBSRGrpMappingAddrType object. given by the pimBsrElectedBSRGrpMappingAddrType object.
This address object is only significant up to This address object is only significant up to
pimBsrElectedBSRGrpMappingGrpPrefixLen bits. The pimBsrElectedBSRGrpMappingGrpPrefixLen bits. The
remainder of the address bits are zero. This is remainder of the address bits are zero. This is
especially important for this field, which is part of especially important for this field, which is part of
the index of this entry. Any non-zero bits would the index of this entry. Any non-zero bits would
signify an entirely different entry." signify an entirely different entry."
skipping to change at page 11, line 22 skipping to change at page 10, line 11
::= { pimBsrElectedBSRRPSetEntry 5 } ::= { pimBsrElectedBSRRPSetEntry 5 }
pimBsrElectedBSRRPSetPriority OBJECT-TYPE pimBsrElectedBSRRPSetPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority for RP. Numerically higher values for "The priority for RP. Numerically higher values for
this object indicate lower priorities, with the value this object indicate lower priorities, with the value
zero denoting the highest priority." zero denoting the highest priority."
REFERENCE "RFC5059 section 4.1" REFERENCE "RFC 5059, section 4.1"
::= { pimBsrElectedBSRRPSetEntry 6 } ::= { pimBsrElectedBSRRPSetEntry 6 }
pimBsrElectedBSRRPSetHoldtime OBJECT-TYPE pimBsrElectedBSRRPSetHoldtime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The holdtime for RP" "The holdtime for RP"
REFERENCE "RFC5059 section 4.1" REFERENCE "RFC 5059, section 4.1"
::= { pimBsrElectedBSRRPSetEntry 7 } ::= { pimBsrElectedBSRRPSetEntry 7 }
pimBsrElectedBSRRPSetExpiryTime OBJECT-TYPE pimBsrElectedBSRRPSetExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum time remaining before this entry will be "The minimum time remaining before this entry will be
aged out. The value zero indicates that this entry will aged out. The value zero indicates that this entry will
never be aged out." never be aged out."
skipping to change at page 12, line 50 skipping to change at page 11, line 39
pimBsrCandidateBSRStatus RowStatus, pimBsrCandidateBSRStatus RowStatus,
pimBsrCandidateBSRStorageType StorageType pimBsrCandidateBSRStorageType StorageType
} }
pimBsrCandidateBSRZoneIndex OBJECT-TYPE pimBsrCandidateBSRZoneIndex OBJECT-TYPE
SYNTAX InetZoneIndex (1..4294967295) SYNTAX InetZoneIndex (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The zone index uniquely identifies the zone on a "The zone index uniquely identifies the zone on a
device to which this Candidate BSR is attached. There is device to which this Candidate-BSR is attached. There is
one entry for each zone in ipMcastZoneTable. Scope-level one entry for each zone in ipMcastZoneTable. Scope-level
information for this zone can be extracted from information for this zone can be extracted from
ipMcastZoneTable in IP Multicast MIB [RFC5132]. ipMcastZoneTable in IP Multicast MIB [RFC5132].
Zero is a special value used to request the default zone Zero is a special value used to request the default zone
for a given scope. Zero is not a valid value for this for a given scope. Zero is not a valid value for this
object." object."
::= { pimBsrCandidateBSREntry 1 } ::= { pimBsrCandidateBSREntry 1 }
skipping to change at page 14, line 34 skipping to change at page 13, line 23
Value of this object is zero if Value of this object is zero if
pimBsrCandidateBSRElectedBSR is 'FALSE'." pimBsrCandidateBSRElectedBSR is 'FALSE'."
::= { pimBsrCandidateBSREntry 7 } ::= { pimBsrCandidateBSREntry 7 }
pimBsrCandidateBSRStatus OBJECT-TYPE pimBsrCandidateBSRStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may "The status of this row, by which new entries may
be created, or old entries deleted from this table. be created or old entries deleted from this table.
This status object can be set to active(1) without This status object can be set to active(1) without
setting any other columnar objects in this entry setting any other columnar objects in this entry.
All writable objects in this entry can be modified All writable objects in this entry can be modified
when the status of this entry is active(1)." when the status of this entry is active(1)."
::= { pimBsrCandidateBSREntry 8 } ::= { pimBsrCandidateBSREntry 8 }
pimBsrCandidateBSRStorageType OBJECT-TYPE pimBsrCandidateBSRStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 15, line 48 skipping to change at page 14, line 37
pimBsrElectedBSRZoneIndex OBJECT-TYPE pimBsrElectedBSRZoneIndex OBJECT-TYPE
SYNTAX InetZoneIndex (1..4294967295) SYNTAX InetZoneIndex (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The zone index uniquely identifies the zone on a "The zone index uniquely identifies the zone on a
device to which this Elected BSR is attached. There device to which this Elected BSR is attached. There
is one entry for each zone in ipMcastZoneTable. is one entry for each zone in ipMcastZoneTable.
Scope-level information for this zone can be extracted Scope-level information for this zone can be extracted
from ipMcastZoneTable in IP MCAST MIB. from ipMcastZoneTable in IP Multicast MIB [RFC5132].
Zero is a special value used to request the default zone Zero is a special value used to request the default zone
for a given scope. Zero is not a valid value for this for a given scope. Zero is not a valid value for this
object." object."
::= { pimBsrElectedBSREntry 1 } ::= { pimBsrElectedBSREntry 1 }
pimBsrElectedBSRAddressType OBJECT-TYPE pimBsrElectedBSRAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 17, line 18 skipping to change at page 16, line 6
-- --
pimBsrElectedBSRLostElection NOTIFICATION-TYPE pimBsrElectedBSRLostElection NOTIFICATION-TYPE
OBJECTS { pimBsrElectedBSRAddressType, OBJECTS { pimBsrElectedBSRAddressType,
pimBsrElectedBSRAddress, pimBsrElectedBSRAddress,
pimBsrElectedBSRPriority } pimBsrElectedBSRPriority }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pimBsrElectedBSRLostElection notification should be "A pimBsrElectedBSRLostElection notification should be
generated when current E-BSR lost election to a new generated when current E-BSR lost election to a new
Candidate BSR. Only an E-BSR should generate this Candidate-BSR. Only an E-BSR should generate this
notification. notification.
This notification is generated when This notification is generated when
pimBsrCandidateBSRElectedBSR becomes FALSE." pimBsrCandidateBSRElectedBSR becomes FALSE."
REFERENCE "RFC5059 section 3.1" REFERENCE "RFC 5059, section 3.1"
::= { pimBsrNotifications 1 } ::= { pimBsrNotifications 1 }
pimBsrCandidateBSRWinElection NOTIFICATION-TYPE pimBsrCandidateBSRWinElection NOTIFICATION-TYPE
OBJECTS { pimBsrCandidateBSRElectedBSR } OBJECTS { pimBsrCandidateBSRElectedBSR }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pimBsrCandidateBSRWinElection notification should be "A pimBsrCandidateBSRWinElection notification should be
generated when a C-BSR wins BSR Election. Only an generated when a C-BSR wins BSR Election. Only an
E-BSR should generate this notification. E-BSR should generate this notification.
This notification is generated when This notification is generated when
pimBsrCandidateBSRElectedBSR becomes TRUE." pimBsrCandidateBSRElectedBSR becomes TRUE."
REFERENCE "RFC5059 section 3.1" REFERENCE "RFC 5059, section 3.1"
::= { pimBsrNotifications 2 } ::= { pimBsrNotifications 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
pimBsrCompliance MODULE-COMPLIANCE pimBsrCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for PIM routers that implement "The compliance statement for PIM routers that implement
skipping to change at page 19, line 18 skipping to change at page 18, line 8
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o A new Candidate BSR with high priority or modification of priority o A new Candidate-BSR with high priority or modification of priority
of an existing candidate BSR can take over the functionality of ( bsrCandidateBSRPriority ) of an existing Candidate-BSR can take
Elected BSR, which can prevent and disrupt the services. over the functionality of an Elected BSR, which can prevent and
disrupt the services.
o A new Candidate RP with lower priority or modification of priority o A new Candidate-RP with lower priority or modification of priority
of an existing Candidate RP can force other routers to select ( bsrCandidateRPPriority ) of an existing Candidate-RP can force
itself for a particular group prefix. This can prevent and other routers to select itself for a particular group prefix.
disrupt the services provided through this group prefix. This can prevent and disrupt the services provided through this
group prefix.
The following are the read-write and read-create objects defined in The following are the read-write and read-create objects defined in
this MIB module: this MIB module:
bsrCandidateRPBidir bsrCandidateRPBidir
bsrCandidateRPPriority bsrCandidateRPPriority
bsrCandidateRPAdvInterval bsrCandidateRPAdvInterval
bsrCandidateRPHoldtime bsrCandidateRPHoldtime
bsrCandidateBSRAddressType bsrCandidateBSRAddressType
bsrCandidateBSRAddress bsrCandidateBSRAddress
skipping to change at page 20, line 17 skipping to change at page 19, line 4
pimBsrElectedBSRRPSetHoldtime pimBsrElectedBSRRPSetHoldtime
pimBsrElectedBSRRPSetExpiryTime pimBsrElectedBSRRPSetExpiryTime
pimBsrElectedBSRRPSetGrpBidir pimBsrElectedBSRRPSetGrpBidir
pimBsrCandidateBSRElectedBSR pimBsrCandidateBSRElectedBSR
pimBsrCandidateBSRBootstrapTimer pimBsrCandidateBSRBootstrapTimer
pimBsrElectedBSRAddressType pimBsrElectedBSRAddressType
pimBsrElectedBSRAddress pimBsrElectedBSRAddress
pimBsrElectedBSRPriority pimBsrElectedBSRPriority
pimBsrElectedBSRHashMaskLength pimBsrElectedBSRHashMaskLength
pimBsrElectedBSRExpiryTime pimBsrElectedBSRExpiryTime
In this MIB module, possible effects that can be induced by GET In this MIB module, possible effects that can be induced by GET
operations include: operations include:
o Determination of Elected BSR, Candidate BSRs and Candidate RPs in o Determination of Elected BSR, Candidate-BSRs, and Candidate-RPs in
the Multicast Network topology. This information may be sensitive the Multicast Network topology. This information may be sensitive
and may be used in preparation for DoS attacks including any of and may be used in preparation for Denial-of-Service (DoS) attacks
the attacks described above. including any of the attacks described above.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
there is still no control over whom on the secure network is allowed there is still no control over whom on the secure network is allowed
to access (read/change/create/delete) the objects in this MIB module. to access (read/change/create/delete) the objects in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
skipping to change at page 20, line 51 skipping to change at page 19, line 37
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to access (read/change/create/delete) them. rights to access (read/change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
pimBsrMIB { mib-2 XXX } pimBsrMIB { mib-2 172 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
8. Acknowledgments 8. Acknowledgments
This MIB module is based on the original work in [RFC5060] by R. This MIB module is based on the original work in [RFC5060] by R.
Sivaramu, J. Lingard and B. Joshi. Sivaramu, J. Lingard, and B. Joshi.
Many thanks to Bill Fenner, Stig Venaas, Nidhi Bhaskar, David Many thanks to Bill Fenner, Stig Venaas, Nidhi Bhaskar, David
Mcwalter, David Harrington and J. W. Atwood for their feedback on Mcwalter, David Harrington, and J. W. Atwood for their feedback on
this MIB module. this MIB module.
Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have
been used for comparison while editing this MIB module. been used for comparison while editing this MIB module.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 23, line 13 skipping to change at page 22, line 13
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Authors' Addresses Authors' Addresses
Bharat Joshi Bharat Joshi
Infosys Technologies Ltd. Infosys Technologies Ltd.
44 Electronics City, Hosur Road 44 Electronics City, Hosur Road
Bangalore 560 100 Bangalore 560 100
India India
Email: bharat_joshi@infosys.com EMail: bharat_joshi@infosys.com
URI: http://www.infosys.com/ URI: http://www.infosys.com/
Raina Bijlani Raina Bijlani
Email: rainab@gmail.com EMail: rainab@gmail.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 24, line 28 skipping to change at line 993
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2008). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 43 change blocks. 
103 lines changed or deleted 83 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/