%% You should probably cite draft-ietf-bess-mvpn-pe-ce instead of this I-D. @techreport{ietf-l3vpn-mvpn-pe-ce-02, number = {draft-ietf-l3vpn-mvpn-pe-ce-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-l3vpn-mvpn-pe-ce/02/}, author = {Keyur Patel and Yakov Rekhter and Eric C. Rosen}, title = {{BGP as an MVPN PE-CE Protocol}}, pagetotal = 13, year = 2014, month = oct, day = 15, 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.}, }