BGP-MPLS VPN extension for IPv 4 IPv 6 Hybrid

BGP-MPLS VPN extension for IPv 4/IPv 6 Hybrid Network Defeng Li 77 cronux. leed 0621@huawei. com Huawei Technologies

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Justification – IPv 6 can’t take the place of IPv 4 in the global network in one night, it must co-exist with IPv 4 in a long period, then backbone and sites of inter-provider L 3 VPN will often be IPv 4/IPv 6 hybrid. – IPv 4/IPv 6 Hybrid VPN isn’t addressed elsewhere. • Purpose – Proposes some methods for IPv 4/IPv 6 hybrid VPN – Open to accommodate other methods in the future version 2

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Contents – Case 1: Both of VPN Backbone and sites are IPv 4/IPv 6 Hybrid • Method 1 • Method 2 – Case 2: IPv 4 backbone with IPv 4/IPv 6 hybrid VPN sites • Most Concepts inherited from RFC 2547 bis – – – RD Route Target VRF MP-BGP … 3

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Method 1 for Case 1 4

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Route Distribution (Method 1 for Case 1) – Both IPv 4 routes and IPv 6 routes are distributed between CE-PE, BGP 4+, IS-ISv 6 and OSPFv 3 can carry IPv 4/ IPv 6 routes simultaneously. – Every two of PEs and ASBR 1 in IPv 4 AS establish MP -IBGP based on IPv 4; – Every two of PEs and ASBR 2 in IPv 6 AS establish MP -IBGP based on IPv 6; – ASBR 1 and ASBR 2 establish MP-EBGP based on IPv 6; – VPN-IPv 4 routes and VPN-IPv 6 routes can be piggybacked on the same MP-BGP; – PEs maintain VPN-IPv 4 routes and VPN-IPv 6 routes in respective VRFs, they are differentiated by the AFI of the routes received. 5

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Address Requirements (Method 1 for Case 1) – – – Should support two AFI, 1 for IPv 4 and 2 for IPv 6, SAFI: 128; Two IPv 4 sites communicate with IPv 4 address; Two IPv 6 sites communicate with IPv 6 address; One IPv 4 site and one IPv 6 site communicate with IPv 6 address; IPv 4 address A. B. C. D/Mask mapped to 0: : A: B: C: D/(96+MASK) IPv 6 address if necessary; – PEs and ASBRs should support IPv 4/IPv 6 dual-stack and maintain both VPN-IPv 4 routes and VPN-IPv 6 routes; – CEs in IPv 4 sites which have relations only to other IPv 4 sites can support only IPv 4 protocol and maintain IPv 4 VPN routes, otherwise CE should support IPv 4/IPv 6 dual-stack; 6

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Label Distribution (Method 1 for Case 1) – Inherited from RFC 2547 bis in every AS; – MP-EBGP between ASBR 1 and ASBR 2 distributes the labels, and LSPs in AS 1 and AS 2 can be sticked ; • Packet Forwarding (Method 1 for Case 1) – Packets between sites-PE are forwarded following the IP protocol of the respective version(IPv 4/IPv 6) – In the backbone packets can be forwarded on the sticked LSP 7

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Method 2 for Case 1 8

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Address Requirements (Method 2 for Case 1) – Same with Method 1; • Route Distribution (Method 2 for Case 1) – Every two of PEs in DAS establish MP-IBGP based on IPv 4; – Every two of PEs and ASBR 2 in PAS establish MP-IBGP based on IPv 6; – Every PE in DAS and ASBR 2 establish multi-hop MP-EBGP based on IPv 4; – VPN routes need to be distributed to sites connected to neighboring AS are distributed by such multi-hop MP-EBGP; • Same with method 1 in other aspects. 9

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Case 2: IPv 4 backbone and IPv 4/IPv 6 hybrid VPN sites 10

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Characteristics of Case 2 – Needs no VPN-IPv 6 AFI in the backbone; – PE assigns private IPv 4 addresses for IPv 6 site, and supports private IPv 4 address NAT-PT; – Extend MP-BGP protocol by adding an Extended Community attribute: If-V 6 -Site to identify IPv 6 sites; – IPv 6 routes are mapped to IPv 4 NAT-PT prefix at PE and true IPv 6 routes are distributed across backbone as the “value” of If-V 6 -Site attribute of IPv 4 NAT-PT prefix through MP-BGP; 11

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Characteristics of Case 2 – PE maintains IPv 4 routes, IPv 6 mapped NAT-PT IPv 4 routes and true IPv 6 routes; – Communication between IPv 4 site and IPv 6 site needs NAT-PT translation; – Communication between two IPv 6 sites use true IPv 6 routes at PE; – Different routes are selected at Ingress PE according to IPv 4/IPv 6 types of Source/Destination sites when forwarding. 12

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 • Judgement of IPv 4/IPv 6 sites – Whether the sites is IPv 6 can be identified by the address of the interface between CE and PE, then PE can set the related fields in If-V 6 -Site attribute when distributing the VPN routes across backbone, and whether the remote site is IPv 6 can be identified by If-V 6 -Site attribute attached to VPN routes received. • If-V 6 -Site (TLV) Extended Community Attribute 0 1 2 3 0123456789012345678901 +-+-+-+-+-+-+-+-+-+-+-+-+-+|T| length | | +-+-+-+-+-+-+-+-+| | IPv 6 Route 1… | | +-+-+-+-+-+-+-+-+-+-+-+-+-+| IPv 6 Routen… |. . . | +-+-+-+-+-+-+-+-+-+-+-+-+- 13

draft-defeng-l 3 vpn-ipv 4 -ipv 6 -hybrid-01 What’s Next ? l l Can it be accepted as the baseline of wg draft? Accommodate more mechanism to this draft to address IPv 4/IPv 6 hybrid VPN. 14

15