Embedding the Address of RP in IPv6 Multicast Address
draft-savola-mboned-mcast-rpaddr-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pekka Savola , Brian Haberman | ||
| Last updated | 2003-05-22 | ||
| 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
As has been noticed, there is exists a huge deployment problem with global, interdomain IPv6 multicast: Protocol Independent Multicast - Sparse Mode (PIM-SM) Rendezvous Points (RPs) have no way of communicating the information about multicast sources to other multicast domains, as there is no Multicast Source Discovery Protocol (MSDP), and the whole interdomain Any Source Multicast model is rendered unusable; SSM avoids these problems. This memo outlines a way to embed the address of the RP in the multicast address, solving the interdomain multicast problem. The problem is three-fold: specify an address format, adjust the operational procedures and configuration if necessary, and modify PIM-SM implementations of those who want to join or send to a group (Designated Routers) or provide one (Rendezvous Points). In consequence, there would be no need for interdomain MSDP, and even intra-domain RP configuration could be simplified. This memo updatres RFC 3306.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)