RP Relocation in PIM-SM Multicast
draft-atwood-pim-sm-rp-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | J. William Atwood , Ritesh Mukherjee | ||
| Last updated | 2002-07-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Protocol Independent Multicast-Sparse Mode (PIM-SM) protocol uses a core-based tree to forward multicast datagrams to members of a multicast group. Currently there is no method for relocating the core or Rendezvous Point (RP) for a group. Administratively chosen RP's lead to low performance as the sources and receivers in the multicast group join and leave the group. This draft presents a mechanism for dynamically relocating the RP to a position that minimizes the tree cost and improves performance.
Authors
J. William Atwood
Ritesh Mukherjee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)