PIM Group-to-Rendezvous-Point Mapping
RFC 6226
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Each Protocol Independent Multicast - Sparse Mode (PIM-SM) router in a PIM domain that supports Any … Received changes through RFC Editor sync (changed abstract to '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]') |
2015-10-14
|
(System) | Notify list changed from pim-chairs@ietf.org, draft-ietf-pim-group-rp-mapping@ietf.org to (None) |
2011-05-09
|
Cindy Morgan | State changed to RFC Published from RFC Ed Queue. |
2011-05-09
|
Cindy Morgan | [Note]: changed to 'RFC 6226' |
2011-05-06
|
(System) | RFC published |