Connecting Multicast Domains
draft-ietf-mboned-mcast-connect-00
| Document | Type | Expired Internet-Draft (mboned WG) | |
|---|---|---|---|
| Last updated | 2000-03-02 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mboned-mcast-connect-00.txt
https://www.ietf.org/archive/id/draft-ietf-mboned-mcast-connect-00.txt
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.)