rfc5060-v3.txt | rfc5060.txt | |||
---|---|---|---|---|
Network Working Group R. Sivaramu | Network Working Group R. Sivaramu | |||
Request for Comments: 5060 Cisco Systems | Request for Comments: 5060 Cisco Systems | |||
Category: Standards Track J. Lingard | Category: Standards Track J. Lingard | |||
Arastra, Inc | Arastra, Inc | |||
D. McWalter | D. McWalter | |||
Data Connection Ltd | Data Connection Ltd | |||
B. Joshi | B. Joshi | |||
Infosys Technologies Ltd | Infosys Technologies Ltd | |||
A. Kessler | ||||
Cisco Systems | ||||
November 2007 | November 2007 | |||
Protocol Independent Multicast MIB | Protocol Independent Multicast MIB | |||
Status of This Memo | Status of This Memo | |||
This document specifies an Internet standards track protocol for the | This document specifies an Internet standards track protocol for the | |||
Internet community, and requests discussion and suggestions for | Internet community, and requests discussion and suggestions for | |||
improvements. Please refer to the current edition of the "Internet | improvements. Please refer to the current edition of the "Internet | |||
Official Protocol Standards" (STD 1) for the standardization state | Official Protocol Standards" (STD 1) for the standardization state | |||
skipping to change at page 2, line 12 | skipping to change at page 2, line 12 | |||
where the two documents overlap. This document does not obsolete RFC | where the two documents overlap. This document does not obsolete RFC | |||
2934. | 2934. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
3. The Internet-Standard Management Framework . . . . . . . . . . 3 | 3. The Internet-Standard Management Framework . . . . . . . . . . 3 | |||
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 | 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 82 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 83 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 87 | |||
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 86 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 87 | |||
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87 | |||
9.1. Normative References . . . . . . . . . . . . . . . . . . . 87 | 9.1. Normative References . . . . . . . . . . . . . . . . . . . 87 | |||
9.2. Informative References . . . . . . . . . . . . . . . . . . 88 | 9.2. Informative References . . . . . . . . . . . . . . . . . . 88 | |||
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 | |||
Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601], | Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601], | |||
skipping to change at page 62, line 39 | skipping to change at page 62, line 39 | |||
REFERENCE "RFC 4601 section 3.7, RFC 3569, and | REFERENCE "RFC 4601 section 3.7, RFC 3569, and | |||
'IP Multicast MIB' (August 2007) ipMcastSsmRangeTable" | 'IP Multicast MIB' (August 2007) ipMcastSsmRangeTable" | |||
DEFVAL { asm } | DEFVAL { asm } | |||
::= { pimStaticRPEntry 5 } | ::= { pimStaticRPEntry 5 } | |||
pimStaticRPOverrideDynamic OBJECT-TYPE | pimStaticRPOverrideDynamic OBJECT-TYPE | |||
SYNTAX TruthValue | SYNTAX TruthValue | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Whether this static RP configuration will override RP | "Whether this static RP configuration will override other | |||
information learned dynamically for groups in this group | group mappings in this group prefix. If this object is | |||
prefix." | TRUE, then it will override: | |||
- RP information learned dynamically for groups in this | ||||
group prefix. | ||||
- RP information configured in pimStaticRPTable with | ||||
pimStaticRPOverrideDynamic set to FALSE. | ||||
See pimGroupMappingTable for details." | ||||
DEFVAL { false } | DEFVAL { false } | |||
::= { pimStaticRPEntry 6 } | ::= { pimStaticRPEntry 6 } | |||
pimStaticRPPrecedence OBJECT-TYPE | pimStaticRPPrecedence OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value for pimGroupMappingPrecedence to be used for this | "The value for pimGroupMappingPrecedence to be used for this | |||
static RP configuration. This allows fine control over | static RP configuration. This allows fine control over | |||
skipping to change at page 67, line 31 | skipping to change at page 67, line 39 | |||
created and destroyed according to some other mechanism | created and destroyed according to some other mechanism | |||
not specified here. | not specified here. | |||
Given the collection of rows in this table at any point in | Given the collection of rows in this table at any point in | |||
time, the PIM mode and RP address to use for a particular | time, the PIM mode and RP address to use for a particular | |||
group is determined using the following algorithm. | group is determined using the following algorithm. | |||
1. From the set of all rows, the subset whose group prefix | 1. From the set of all rows, the subset whose group prefix | |||
contains the group in question are selected. | contains the group in question are selected. | |||
2. If there are no such rows, the behavior is undefined. | 2. If there are no such rows, then the group mapping is | |||
undefined. | ||||
3. From the selected subset of rows, the subset that have | ||||
the greatest value of pimGroupMappingGrpPrefixLength are | ||||
selected. | ||||
4. If there are multiple selected rows, and a subset is | 3. If there are multiple selected rows, and a subset is | |||
defined by pimStaticRPTable (pimGroupMappingOrigin value | defined by pimStaticRPTable (pimGroupMappingOrigin value | |||
of 'configRp') with pimStaticRPOverrideDynamic set to | of 'configRp') with pimStaticRPOverrideDynamic set to | |||
TRUE, then this subset is selected. | TRUE, then this subset is selected. | |||
4. From the selected subset of rows, the subset that have | ||||
the greatest value of pimGroupMappingGrpPrefixLength are | ||||
selected. | ||||
5. If there are still multiple selected rows, the subset | 5. If there are still multiple selected rows, the subset | |||
that has the highest precedence (the lowest numerical | that has the highest precedence (the lowest numerical | |||
value for pimGroupMappingPrecedence) is selected. | value for pimGroupMappingPrecedence) is selected. | |||
6. If there are still multiple selected rows, the row | 6. If there are still multiple selected rows, the row | |||
selected is implementation dependent; the implementation | selected is implementation dependent; the implementation | |||
might or might not apply the PIM hash function to select | might or might not apply the PIM hash function to select | |||
the row. | the row. | |||
7. The group mode to use is given by the value of | 7. The group mode to use is given by the value of | |||
skipping to change at page 90, line 4 | skipping to change at page 90, line 4 | |||
EMail: dmcw@dataconnection.com | EMail: dmcw@dataconnection.com | |||
Bharat Joshi | Bharat Joshi | |||
Infosys Technologies Ltd | Infosys Technologies Ltd | |||
Electronic City | Electronic City | |||
Bangalore 560 100 | Bangalore 560 100 | |||
India | India | |||
EMail: bharat_joshi@infosys.com | EMail: bharat_joshi@infosys.com | |||
Andrew Kessler | ||||
Cisco Systems | ||||
425 E. Tasman Drive | ||||
San Jose, CA 95134 | ||||
USA | ||||
EMail: kessler@cisco.com | ||||
Full Copyright Statement | Full Copyright Statement | |||
Copyright (C) The IETF Trust (2007). | Copyright (C) The IETF Trust (2007). | |||
This document is subject to the rights, licenses and restrictions | This document is subject to the rights, licenses and restrictions | |||
contained in BCP 78, and except as set forth therein, the authors | contained in BCP 78, and except as set forth therein, the authors | |||
retain all their rights. | retain all their rights. | |||
This document and the information contained herein are provided on an | This document and the information contained herein are provided on an | |||
End of changes. 7 change blocks. | ||||
12 lines changed or deleted | 30 lines changed or added | |||
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |