PIM Group-to-RP Mapping

Document Type Replaced Internet-Draft (individual)
Authors Bharat Joshi  , David McWalter  , Andy Kessler 
Last updated 2008-06-11
Replaced by RFC 6226
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-pim-group-rp-mapping
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Each PIM-SM router in a PIM Domain which supports ASM maintains Group-to-RP mappings which are used to identify a RP for a specific multicast group. PIM-SM has defined an algorithm to choose a RP from the Group-to-RP mappings learned using various mechanisms. This algorithm does not allow administrator to override a specific Group-to-RP mapping with the static Group-to-RP mapping which an administrator would want to use. This algorithm also does not consider the PIM mode and the mechanism through which a Group-to-RP mapping was learned. This document first explains the requirements to extend the Group-to-RP mapping algorithm and then proposes the new algorithm.


Bharat Joshi (bharat_joshi@infosys.com)
David McWalter (dmcw@dataconnection.com)
Andy Kessler (kessler@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)