BGP as an MVPN PE-CE Protocol
draft-ietf-l3vpn-mvpn-pe-ce-02

Document Type Replaced Internet-Draft (bess WG)
Last updated 2014-10-22 (latest revision 2014-10-15)
Replaces draft-keyupate-l3vpn-mvpn-pe-ce
Replaced by draft-ietf-bess-mvpn-pe-ce
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestones: Oct 2014 - Submit specification..., Apr 2015 - Submit specification... )
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-mvpn-pe-ce
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-l3vpn-mvpn-pe-ce-02.txt

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 (keyupate@cisco.com)
Yakov Rekhter (yakov@juniper.net)
Eric Rosen (erosen@juniper.net)

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