draft-ietf-pim-group-rp-mapping-09.txt   draft-ietf-pim-group-rp-mapping-10.txt 
PIM Working Group B. Joshi PIM Working Group B. Joshi
Internet-Draft Infosys Technologies Ltd. Internet-Draft Infosys Technologies Ltd.
Updates: 4601 (if approved) A. Kessler Updates: 4601 (if approved) A. Kessler
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: July 16, 2011 D. McWalter Expires: August 1, 2011 D. McWalter
January 12, 2011 January 28, 2011
PIM Group-to-RP Mapping PIM Group-to-RP Mapping
draft-ietf-pim-group-rp-mapping-09.txt draft-ietf-pim-group-rp-mapping-10.txt
Abstract Abstract
Each PIM-SM router in a Protocol Independent Multicast (PIM) Domain Each PIM-SM router in a Protocol Independent Multicast (PIM) Domain
which supports Any Source Multicast (ASM) maintains Group-to-RP which supports Any Source Multicast (ASM) maintains Group-to-RP
mappings which are used to identify a Rendezvous Point(RP) for a mappings which are used to identify a Rendezvous Point(RP) for a
specific multicast group. PIM-SM has defined an algorithm to choose specific multicast group. PIM-SM has defined an algorithm to choose
a RP from the Group-to-RP mappings learned using various mechanisms. a RP from the Group-to-RP mappings learned using various mechanisms.
This algorithm does not consider the PIM mode and the mechanism This algorithm does not consider the PIM mode and the mechanism
through which a Group-to-RP mapping was learned. through which a Group-to-RP mapping was learned.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 16, 2011. This Internet-Draft will expire on August 1, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 33 skipping to change at page 3, line 33
PIM-STD-MIB [RFC5060] includes a number of objects to allow an PIM-STD-MIB [RFC5060] includes a number of objects to allow an
administrator to set the precedence for Group-to-RP mappings which administrator to set the precedence for Group-to-RP mappings which
are learned statically or dynamically and stored in the are learned statically or dynamically and stored in the
'pimGroupMappingTable'. The Management Information Base (MIB) module 'pimGroupMappingTable'. The Management Information Base (MIB) module
also defines an algorithm that can be applied to the data contained also defines an algorithm that can be applied to the data contained
in the 'pimGroupMappingTable' to determine Group-to-RP mappings. in the 'pimGroupMappingTable' to determine Group-to-RP mappings.
However, this algorithm is not completely deterministic, because it However, this algorithm is not completely deterministic, because it
includes an implementation-specific 'precedence' value. includes an implementation-specific 'precedence' value.
Network Management stations will be able to deduce which RPs will be
selected by applying the algorithm from this document to the list of
Group-to-RP mappings from the 'pimGroupMappingTable'. The algorithm
provides MIB visibility into how routers will apply Group-to-RP
mappings and also fixes the protocol inconsistency with how different
vendors select the Group-to-RP mappings to create multicast
forwarding state.
Embedded-RP as defined in section-7.1 of Embedded-RP address in IPv6 Embedded-RP as defined in section-7.1 of Embedded-RP address in IPv6
Multicast address [RFC3956], mentions that to avoid loops and Multicast address [RFC3956], mentions that to avoid loops and
inconsistencies, for addresses in the range FF70::/12, the inconsistencies, for addresses in the range FF70::/12, the
Embedded-RP mapping must be considered the longest possible match and Embedded-RP mapping must be considered the longest possible match and
higher priority than any other mechanism. higher priority than any other mechanism.
2. Terminology 2. Terminology
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
skipping to change at page 10, line 7 skipping to change at page 10, line 7
* If the remaining Group-to-RP mappings were NOT learned from * If the remaining Group-to-RP mappings were NOT learned from
BSR we continue the algorithm with the next step. BSR we continue the algorithm with the next step.
10. From the remaining set of Group-to-RP Mappings we will select 10. From the remaining set of Group-to-RP Mappings we will select
the RP with the highest IP address (numerically greater). This the RP with the highest IP address (numerically greater). This
will serve as a final tiebreaker. will serve as a final tiebreaker.
7. Interpretation of MIB Objects 7. Interpretation of MIB Objects
As described in [RFC5060] the Group-to-RP mapping information is
summarized in the pimGroupMappingTable. The precedence value is
stored in the 'pimGroupMappingPrecedence' object which covers both
the dynamically learned Group-to-RP mapping information as well as
the static configuration. For static configurations, the
'pimGroupMappingPrecedence' object uses the value of the
'pimStaticRPPrecedence' object from the pimStaticRPTable table.
The algorithm defined in this document does not use the concept of The algorithm defined in this document does not use the concept of
precedence and therefore the values configured in the precedence and therefore the values configured in the
'pimGroupMappingPrecedence' and 'pimStaticRPPrecedence' objects of 'pimGroupMappingPrecedence' and 'pimStaticRPPrecedence' objects in
the 'pimGroupMappingTable' table in the PIM-STD-MIB module [RFC5060] the PIM-STD-MIB module [RFC5060] are not applicable to the new
are not applicable to the new algorithm. The objects still retain algorithm. The objects still retain their meaning for 'legacy'
their meaning for 'legacy' implementations, but since the algorithm implementations, but since the algorithm defined in this document is
defined in this document is to be used in preference to that found in to be used in preference to that found in PIM-SM [RFC4601] and PIM-
PIM-SM [RFC4601] and PIM-STD-MIB [RFC5060], the usage of these fields STD-MIB [RFC5060], the values of these objects will be ignored on
will decline as implementations are upgraded to support the new implementations that support the new algorithm.
algorithm.
8. Clarification for MIB Objects 8. Clarification for MIB Objects
An implementation of this specification can continue to be managed An implementation of this specification can continue to be managed
using the PIM-STD-MIB [RFC5060]. When a Group-to-RP mapping entry is using the PIM-STD-MIB [RFC5060]. When a Group-to-RP mapping entry is
created in the pimGroupMappingTable with RP address type in the created in the pimGroupMappingTable with RP address type in the
pimGroupMappingRPAddressType object is set to unknown(0), and the PIM pimGroupMappingRPAddressType object is set to unknown(0), and the PIM
Mode in the pimGroupMappingPimMode object is set to either ssm(2) or Mode in the pimGroupMappingPimMode object is set to either ssm(2) or
dm(5) to represent group ranges for SSM or Dense mode. dm(5) to represent group ranges for SSM or Dense mode.
 End of changes. 6 change blocks. 
12 lines changed or deleted 27 lines changed or added

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