%% You should probably cite rfc6226 instead of this I-D. @techreport{ietf-pim-group-rp-mapping-10, number = {draft-ietf-pim-group-rp-mapping-10}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-pim-group-rp-mapping/10/}, author = {David McWalter and Andy Kessler and Bharat Joshi}, title = {{PIM Group-to-Rendezvous-Point Mapping}}, pagetotal = 11, year = 2011, month = jan, day = 27, abstract = {Each Protocol Independent Multicast - Sparse Mode (PIM-SM) router in a PIM domain that supports Any Source Multicast (ASM) maintains Group-to-RP mappings that are used to identify a Rendezvous Point (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 consider the PIM mode and the mechanism through which a Group-to-RP mapping was learned. This document defines a standard algorithm to deterministically choose between several Group-to-RP mappings for a specific group. This document first explains the requirements to extend the Group-to-RP mapping algorithm and then proposes the new algorithm. {[}STANDARDS-TRACK{]}}, }