Cooperation register mechanism in Anycast RP
draft-yao-pim-cooperation-register-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yao Chunyan , Haibo Wen | ||
| Last updated | 2007-03-20 | ||
| 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
Anycast RP (Rendezvous Point) protocol [N2] is designed to provide load balancing and failover for RP. However, there is no cooperation mechanism among anycast RP members when sending Register-Stop to DR and transferringRegisters among anycast RP members. The former results in the subscribers under some Anycast RP members having multicast service interruption and the latter leads to bandwidth waste among Anycast RP members due to trashy Registers. This specification solves these problems by giving the cooperation mechanism among anycast RP members.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)