BGP as an MVPN PE-CE Protocol
draft-ietf-bess-mvpn-pe-ce-01
| Document | Type |
Expired Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Keyur Patel , Eric C. Rosen , Yakov Rekhter | ||
| Last updated | 2018-04-11 (Latest revision 2015-10-05) | ||
| Replaces | draft-ietf-l3vpn-mvpn-pe-ce | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Parked 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
When a Service Provider offers BGP/MPLS IP VPN service to its customers, RFCs 6513 and 6514 describe protocols and procedures that the Service Provider can use in order to carry the customer's IP multicast traffic from one customer site to others. BGP can be used to carry customer multicast routing information from one Provider Edge (PE) router to another, but it is assumed that PIM is running on the interface between a Customer Edge (CE) router and a PE router. This document specifies protocols and procedures that, under certain conditions, allow customer multicast routing information to carried between PE and CE via BGP. This can eliminate the need to run PIM on the PE-CE interfaces, potentially eliminating the need to run PIM on the PE routers at all.
Authors
Keyur Patel
Eric C. Rosen
Yakov Rekhter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)