%% You should probably cite rfc4659 instead of this I-D. @techreport{ietf-l3vpn-bgp-ipv6-07, number = {draft-ietf-l3vpn-bgp-ipv6-07}, 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-bgp-ipv6/07/}, author = {François Le Faucheur and Jeremy De Clercq and Dirk Ooms and Marco Carugi}, title = {{BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN}}, pagetotal = 18, year = 2005, month = aug, day = 1, abstract = {This document describes a method by which a Service Provider may use its packet-switched backbone to provide Virtual Private Network (VPN) services for its IPv6 customers. This method reuses, and extends where necessary, the "BGP/MPLS IP VPN" method for support of IPv6. In BGP/MPLS IP VPN, "Multiprotocol BGP" is used for distributing IPv4 VPN routes over the service provider backbone, and MPLS is used to forward IPv4 VPN packets over the backbone. This document defines an IPv6 VPN address family and describes the corresponding IPv6 VPN route distribution in "Multiprotocol BGP". This document defines support of the IPv6 VPN service over both an IPv4 and an IPv6 backbone, and for using various tunneling techniques over the core, including MPLS, IP-in-IP, Generic Routing Encapsulation (GRE) and IPsec protected tunnels. The inter-working between an IPv4 site and an IPv6 site is outside the scope of this document. {[}STANDARDS-TRACK{]}}, }