%% You should probably cite rfc6565 instead of this I-D. @techreport{ietf-l3vpn-ospfv3-pece-11, number = {draft-ietf-l3vpn-ospfv3-pece-11}, 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-ospfv3-pece/11/}, author = {Padma Pillay-Esnault and Peter Moyer and Jeff Doyle and Emre Ertekin and Michael Lundberg}, title = {{OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol}}, pagetotal = 20, year = 2012, month = jan, day = 10, abstract = {Many Service Providers (SPs) offer Virtual Private Network (VPN) services to their customers using a technique in which Customer Edge (CE) routers are routing peers of Provider Edge (PE) routers. The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. Support currently exists for both IPv4 and IPv6 VPNs; however, only Open Shortest Path First version 2 (OSPFv2) as PE-CE protocol is specified. This document extends those specifications to support OSPF version 3 (OSPFv3) as a PE-CE routing protocol. The OSPFv3 PE-CE functionality is identical to that of OSPFv2 except for the differences described in this document. {[}STANDARDS-TRACK{]}}, }