Connecting Multicast Domains
draft-ietf-mboned-mcast-connect-00
| Document | Type |
Expired Internet-Draft
(mboned WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Bradley Cain | ||
| Last updated | 2000-03-02 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
New deployment of multicast routing in Internet Service Provider networks is through the use of the PIM-SM [PIMSM], MSDP [MSDP], and MBGP [MBGP] protocols. This informational document describes several solutions for the connection of different types of multicast routing domains. In particular, the problems and solutions for the connection of a stub intra-domain multicast routing domain to a transit (ISP) PIM-SM domain are addressed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)