MT Tunnel Discovery and RPF check
draft-wijnands-mt-discovery-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | IJsbrand Wijnands , Gargi Nalawade | ||
| Last updated | 2004-07-22 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-wijnands-mt-discovery-01.txt
Abstract
Multicast Tunnels are built between Provider Edge (PE) routers to allow multicast communication between different site's of a VPN. The MT tunnel has a destination MDT group address that is unique to the VPN. All routers that act as PE's and are configured for a specific VPN join the VPN MDT multicast group in the backbone of the provider network to be able to receive each others packets. Each router is also a sender to the MDT group. How the forwarding of the MDT packets is achieved is depending on the PIM mode of the MDT group. This can be either PIM-Bidir, PIM-SM or PIM SSM. The proposal in this document is related specifically to PIM SSM mode.
Authors
IJsbrand Wijnands
(ice@cisco.com)
Gargi Nalawade
(gargi@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)