BGP as an MVPN PE-CE Protocol

Document Type Replaced Internet-Draft (individual)
Authors Keyur Patel  , Yakov Rekhter  , Eric Rosen 
Last updated 2013-10-14 (latest revision 2013-07-09)
Replaced by draft-ietf-l3vpn-mvpn-pe-ce
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-l3vpn-mvpn-pe-ce
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


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.


Keyur Patel (
Yakov Rekhter (
Eric Rosen (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)