datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

PIM Group-to-Rendezvous-Point Mapping
draft-ietf-pim-group-rp-mapping-10

RFC
Document Stream: IETF
Last updated: 2011-01-27
Replaces: draft-joshi-pim-group-rp-mapping
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6226
IANA Action State: No IC 
Responsible AD: Adrian Farrel
Send notices to: pim-chairs@tools.ietf.org, draft-ietf-pim-group-rp-mapping@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-pim-group-rp-mapping.

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.

Authors:
David McWalter <david@mcwalter.eu>
Andy Kessler <kessler@cisco.com>
Bharat Joshi <bharat_joshi@infosys.com>

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