IPv6 Using MPLS Vladimir Settey

IPv6 Solutions using MPLS
Vladimir Settey
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 1
•  IPv6 only
IPv6 is the only protocol operating in the network
•  Dual Stack
IPv4 and IPv6 operates in tandem over shared or dedicated links
•  Tunneling over IPv4 and MPLS

IPv6 is confined to the edge of the IPv4 / MPLS core
•  Protocol Translation (NAT64, NAT46, DNS64, etc.)

Allow IPv6-only devices to communicate with IPv4-only devices
Dual Stack App IPv4 + IPv6 Edge IPv6 + IPv4 Core IPv4 and/or IPv4 edge
CE PE P P PE CE
IPv4
IPv6 IPv4 / IPv6 IPv4 configured interface

IPv4 Core
IPv6
Some or all interfaces in cloud

dual configured IPv6 configured interface
•  All P + PE routers are capable of IPv4+IPv6 support

•  Two IGPs supporting IPv4 and IPv6
•  Memory considerations for larger routing tables
•  Native IPv6 multicast support
•  All IPv6 traffic routed in global space
•  Good for content distribution and global services (Internet)
Dual Stack App IPv4 + IPv6 Edge IPv6 + IPv4 Core IPv4 and/or IPv4 edge
CE PE P P PE CE
IPv4
IPv6 IPv4 / IPv6 IPv4 configured interface

IPv4 Core
IPv6
Some or all interfaces in cloud

dual configured IPv6 configured interface
CE#
ipv6 unicast-routing
interface Ethernet0
ip address 192.168.99.1 255.255.255.0
ipv6 address 2001:db8:213:1::1/64
Customer Access Aggregation Edge Core
IP/MPLS
IPv6oPPP
IPv4oPPP
BNG
PP
IPv4|v6oP
•  Native Dual-Stack IPv4/IPv6 service on RG LAN side

•  No changes in existing Access/Aggregation Infrastructure
•  One PPPoE session per Address Family (IPv4 or IPv6) or one PPPoE session
carrying both IPv4 and IPv6 NCPs running as ships in the night
Dual stack must not consume extra BNG session state
•  SLAAC or DHCPv6 can be used to number the WAN link with a Global address
•  DHCPv6-PD is used to delegate a prefix for the Home Network
•  Radius IPv6 attributes as per RFC 3162
BNG Radius DHCPv6
Routed RG Ethernet or DSL Access Node
AAA
PPPoE
PPP LCP
RADIUS "user1“
Access-Request Line-id
RADIUS Framed-Protocol PPP

Access-Accept User-Name “user1”
Service-Type Framed
PPP IPv6CP (Optional) framed-ipv6-prefix
Link Local SLAAC + Default ICMPv6 Router Advertisement

route to BNG installed RA with O-bit
(Optional) Prefix
DHCPv6 Solicit
PD + DNS DHCPv6 Relay Forward
Relay-fwd
DHCPv6 Relay Reply
DHCPv6 Reply* Relay-Reply
SLAAC PD=2001:DB8:AAAA::/56
ICMPv6 RA 、DNS server= 2001:DB8:BB:
2001:DB8: RA with O-bit
AAAA::1 + :1
Prefix=2001:DB8:AAAA::/64
Default
route
installed DHCPv6 Request
DNS
DHCPv6 Response * Assuming DHCPv6 rapid
DNS=2001:DB8:BB::1 commit is in effect
IPv6 over MPLS Pseudowires
IPv6 over IPv4 over MPLS
IPv6 Transit using MPLS 6PE
IPv6 VPN using MPLS 6VPE
IPv6 IPv6 VC Tunnel IPv6
Packet Packet Label Label Packet
IPv6 Network MPLS IPv4 Backbone IPv6 Network
CE PE P P PE CE
IPv6 Pseudowire
IPv6
IPv4
MPLS
IPv6 Pseudowire IPv6
IPv6 only CE ATM, Frame, Ethernet Interface
•  No impact on existing MPLS Core (IPv6 unaware)

•  CE routers need only be single stack IPv6 aware
•  P2P PWs or P2MP PWs (VPLS) supported at PE
•  Good for interconnecting discrete customer islands
•  Sub-Optimal Multicast support, Full Mesh required
•  Many CE interface typed supported – Ethernet, ATM, Frame Relay
IPv6 IPv6 VC Tunnel IPv6
Packet Packet Label Label Packet
CE PE P P PE CE
IPv6 Pseudowire
IPv6
IPv4
MPLS
IPv6 Pseudowire IPv6
IPv6 only CE ATM, Frame, Ethernet Interface

CE# CE#
interface ethernet0/0.10 interface ethernet0/0.10
encapsulation dot1q 10 encapsulation dot1q 10
ipv6 address 2001:100::72A/64 ipv6 address 2001:100::72E/64
PE# PE#
interface loopback0 interface loopback0
ip address 200.10.10.1 255.255.255.0 ip address 200.11.11.1 255.255.255.0
Interface ethernet0/0.10 Interface ethernet0/0.10

encapsulation dot1q 10 encapsulation dot1q 10
xconnect 200.11.11.1 100 encap mpls xconnect 200.10.10.1 100 encap mpls
IPv6 IPv6 IPv4 Tunnel IPv6
Packet Packet Header Label Packet
CE PE P P PE CE
IPv6 Manual Tunnel over LSP
IPv6
IPv4
MPLS
IPv6 Manual Tunnel over LSP IPv6
•  Uses manual tunnel configuration

•  Tunnel in Tunnel Method (P2P tunnels)
Manual Tunnel running over Label Switch Path (protocol=41)
Double encapsulation, first IPv4 then into MPLS frame (tunnel overhead)
Tunnels terminate on PE
•  CE routers single stack, PE must be dual stack
•  MP-BGP can be run over tunnel to distribute IPv6 routes between PE routers
•  Good for interconnecting discrete customer islands
IPv6 IPv6 IPv4 Tunnel IPv6
Packet Packet Header Label Packet
CE PE P P PE CE
IPv6 Manual Tunnel over LSP
IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 Manual Tunnel over LSP IPv6

interface tunnel100 interface tunnel100

ipv6 address 2001:100::1/64 ipv6 address 2001:100::2/64
tunnel source loopback0 tunnel source loopback0
tunnel destination 200.11.11.1 tunnel destination 200.10.10.1
tunnel mode ipv6ip tunnel mode ipv6ip
router bgp 100 router bgp 100

neighbor 2001:100::2 remote-as 100 neighbor 2001:100::1 remote-as 100
address-family ipv6 address-family ipv6

neighbor 2001:100:2 activate neighbor 2001:100:1 activate
IPv6 IPv6 BGP Label LDP Label IPv6
CE3 6PE3 P P 6PE4 CE4

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P 6PE2 CE2 2001:db8::

2001:f00d::
iBGP exchange IPv6
•  6PEs must support dual stack IPv4+IPv6 (acts as normal IPv4 PE)
•  IPv6 packets transported from 6PE to 6PE over Label Switch Path
•  IPv6 addresses exist in global table of PE routers only
IPv6 addresses exchanged between 6PE using MP-BGP session
•  Core uses IPv4 control plane (LDPv4, TEv4, IGPv4, MP-BGP)
•  Benefits from MPLS features such as FRR, TE

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P 6PE2 CE2 2001:db8::

2001:f00d::
iBGP exchange IPv6
•  Connects IPv6 islands over MPLS core (transits edge to edge)
•  Transition mechanism for providing unicast IPv6 access
•  Co-existence mechanism for combining IPv4 and IPv6 services
•  As other IPv6 “tunnel” technologies, enables services such as:
IPv6 Internet Access
Peer-to-peer connectivity
Access to IPv6 services supplied by the SP itself (e.g. 3GPP R5)

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P 6PE2 CE2 2001:db8::

2001:f00d::
MP-iBGP
MP-eBGP MP-eBGP
IGPv4  IGPv4  IGPv4 
200.10.10.1 200.10.10.1 200.10.10.1
reachable reachable reachable
LDP {POP}  LDP {27}  LDP {48} 

Bind Label {POP} Bind Label {27} Bind Label {48}
To 200.10.10.1 To 200.10.10.1 To 200.10.10.1
MP-eBGP  IPv6 MP-iBGP  MP-eBGP 

Advertise 2001:f00d:: Advertises 2001:f00d:: to 6PE2 Advertise 2001:f00d::
to 6PE1 BGP Next-Hop ::ffff.200.10.10.1, Label Binding {65} to CE2
•  LDP Label
Outer label that provides connectivity to the destination 6PE
•  MP-BGP Label
Inner label used by egress 6PE for IPv6 forwarding
Older IOS use pool of 16 labels shared amongst all IPv6 prefixes
P routers hash this label if payload is not IPv4 for load balancing
IOS that support MFI [12.4(20)T & XR] use per prefix labels
Some code also allows IPv4 P-routers to hash IPv6 addresses
This label needed to avoid PHP dropping IPv6 packet
•  BGP Label also referred to as “Aggregate IPv6 Label”

Aggregate labels execute “pop label + IPv6 lookup” at egress 6PE
•  BGP NH is a “Special Use” IPv4 to IPv6 Mapped Address

Fixed Value : IPv4 Loopback of 6PE  ::ffff:A.B.C.D (e.g. ::ffff:200.10.10.1)

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P CE2 2001:db8::

2001:f00d:: Item Value
IPv6 Prefix: 2001:f00d::
BGP Label: {65}

BGP NH: ::ffff:200.10.10.1
IPv4 NH: 200.10.10.1
LDP Label: {48}
 IPv6  MPLS  MPLS  MPLS  IPv6

{27} {48} LDP IPv4 Label
{65} {65} {65} BGP IPv6 Label
2001:f00d:: 2001:f00d:: 2001:f00d:: 2001:f00d:: 2001:f00d:: IPv6 Prefix

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P CE2 2001:db8::

2001:f00d::
ipv6 cef ipv6 cef
! !
! !
router bgp 100 router bgp 100
neighbor 2001:f00d:1::1 remote-as 65014 neighbor 2001:DB8:1::1 remote-as 65015
neighbor 200.11.11.1 remote-as 100 neighbor 200.10.10.1 remote-as 100
neighbor 200.11.11.1 update-source lo0 neighbor 200.10.10.1 update-source lo0
! !
address-family ipv6 address-family ipv6
neighbor 200.11.11.1 activate  6PE2 neighbor 200.10.10.1 activate  6PE1
neighbor 200.11.11.1 send-label neighbor 200.10.10.1 send-label
neighbor 2001:f00d:1::1 activate  CE1 neighbor 2001:DB8:1::1 activate  CE2

IPv6 IPv6
IPv4
200.10.10.1 MPLS 200.11.11.1
IPv6 IPv6
CE1 6PE1 P P CE2 2001:db8::

2001:f00d::
6PE-2#show ipv6 route

B 2001:F00D::/64 [200/0]
via ::FFFF:200.10.10.1, IPv6-mpls
6PE-1#show ipv6 cef internal #hidden command

[snip]
2001:F00D::/64,
nexthop ::FFFF:200.10.10.1
fast tag rewrite with F0/1, 10.12.0.1, tags imposed {48 65}
IPv6/IPv4 Network MPLS IPv4 Backbone IPv6/IPv4 Network
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1
IPv4 VRF IPv4 VRF IPv4

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
•  For VPN customers, IPv6 VPN service is exactly as IPv4 VPN service
•  6PE is “like VPN” but prefixes are in global table, 6VPE is true VPN
•  6VPE enables services such as:

IPv6 VPN Access
Carriers Supporting Carrier
Access to IPv6 services supplied by the SP itself
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
•  6VPE uses existing IPv4 MPLS infrastructure to provide IPv6 VPN

Core uses IPv4 control plane (LDPv4, TEv4, IGPv4)
•  PEs must support dual stack IPv4+IPv6
•  Offers same architectural features as MPLS-VPN for IPv4
•  RTs, VRFs, RDs are appended to IPv6 to form VPNv6 address

MP-BGP distributed both VPN address families
BGP NH uses IPv4 to IPv6 mapped address format ::ffff:A.B.C.D
VRF can contain both VPNv4 and VPNv6 routes
•  Solution suitable for IPv6 support to enterprises and government with VPN
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
ipv6 unicast-routing router bgp 500

ipv6 cef neighbor 2001:db8:cafe:1::2 remote-as 100
! neighbor 172.16.1.2 remote-as 100
interface Ethernet0/0 !
description Link to PE1 address-family ipv4
ip address 172.16.1.1 255.255.255.0 redistribute eigrp 100
ipv6 address 2001:db8:cafe:1::1/64 neighbor 172.16.1.2 activate  6VPE1
! exit-address-family
interface Ethernet1/0 !
description to GREEN LAN address-family ipv6
ip address 10.1.1.1 255.255.255.0 neighbor 2001:db8:cafe:1::2 activate  6VPE1
ipv6 address 2001:db8:beef:1::1/64 redistribute rip GREEN
ipv6 rip GREEN enable exit-address-family
 continues ...
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
vrf definition GREEN

rd 200:1 •  New VRF AF definition
!
< Common RT policies go here > Allows address-families
!
address-family ipv4 Each with unique or common policies
route-target export 200:1
route-target import 200:1 vrf upgrade-cli multi-af-mode
exit-address-family {common-policies | non-common-
!
address-family ipv6
policies} [vrf <name>]
route-target export
route-target import
200:1
200:1
This command can update existing
exit-address-family VRF definitions
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
ipv6 unicast-routing !
ipv6 cef interface Ethernet2/0
! description Link to Core Network
interface Loopback0 ip address 192.168.1.1 255.255.255.252
ip address 200.10.10.1 mpls ip
255.255.255.255 !
! router ospf 1
interface Ethernet0/0 log-adjacency-changes
Description Link to CE1 redistribute connected subnets
vrf forwarding GREEN passive-interface Loopback0
ip address 172.16.1.2 255.255.255.0 network 192.168.1.0 0.0.0.255 area 0
ipv6 address 2001:db8:cafe:1::2/64
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
router bgp 100 address-family vpnv6  To 6VPE2

neighbor 200.11.11.1 remote-as 100 neighbor 200.11.11.1 activate
neighbor 200.11.11.1 update-source lo0 neighbor 200.11.11.1 send-community ext
address-family ipv4  Internet Routes !
neighbor 200.11.11.1 activate address-family ipv4 vrf GREEN  To CE1
no auto-summary redistribute connected
no synchronization neighbor 172.16.1.1 remote-as 500
exit-address-family neighbor 172.16.1.1 activate
address-family vpnv4  To 6VPE2 !
neighbor 200.11.11.1 activate address-family ipv6 vrf GREEN  To CE1
neighbor 200.11.11.1 send-community ext neighbor 2001:db8:cafe:1::1 remote-as 500
exit-address-family neighbor 2001:db8:cafe:1::1 activate
exit-address-family
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
6VPE2#show ipv6 route vrf GREEN

B 2001:db8:beef:1::/64 [200/0]
via 200.10.10.1%Default-IP-Routing-Table, indirectly connected
B 2001:db8:beef:2::/64 [20/0]
via FE80::A8BB:CCFF:FE01:FA00, Ethernet1/0
B 2001:db8:cafe:1::/64 [200/0]
via 200.10.10.1%Default-IP-Routing-Table, indirectly connected
C 2001:db8:cafe:3::/64 [0/0]
via Ethernet1/0, directly connected
L 2001:db8:cafe:3::2/128 [0/0]
via Ethernet1/0, receive
L FF00::/8 [0/0]
via Null0, receive
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
6VPE1#show bgp vpnv6 unicast all

Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 200:1 (default for vrf GREEN)
*> 2001:db8:beef:1::/64
2001:db8:cafe:1::1  Route from CE1
0 0 500 ?
*>i2001:db8:beef:2::/64
::FFFF:200.11.11.1  Route from CE2 via 6VPE2
0 100 0 506 ?
*>i2001:db8:cafe:3::/64
::FFFF:200.11.11.1  PE/CE Connected route from 6VPE2
0 100 0 ?
10.1.1.0/24 10.1.2.0/24
2001:db8:beef:1::/64 P 2001:db8:beef:2::/64
200.10.10.1 P 200.11.11.1

IPv6 MPLS IPv6
CE1 6VPE1 6VPE2 CE2
172.16.1.0.0/30 172.16.3.1/30
2001:db8:cafe:1::/64 P P 2001:db8:cafe:3::/64
6VPE1#show mpls forwarding

Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or VC or Tunnel Id Switched interface
16 Pop Label 192.168.1.4/30 0 Et2/0 192.168.1.2
17 16 192.168.1.8/30 0 Et2/0 192.168.1.2
18 Pop Label 200.12.12.1/32 0 Et2/0 192.168.1.2
19 18 200.13.13.1/32 0 Et2/0 192.168.1.2
20 19 200.11.11.1/32 0 Et2/0 192.168.1.2
21 No Label 10.1.1.0/24[V] 0 Et0/0 172.16.1.1
22 Aggregate 172.16.1.0/24[V] 570 GREEN
25 No Label 2001:db8:beef:1::/64[V] \
570 Et0/0 FE80::A8BB:CCFF:FE01:F400
26 Aggregate 2001:db8:cafe:1::/64[V] \
35456 GREEN
•  RFC4659 BGP-MPLS IP Virtual Private Network (VPN) Extension
for IPv6 VPN
•  6VPE adds IPv6 support to IPv4 MPLS VPN feature
•  For end-users: VPNv6 is same as VPNv4 services

QoS, Hub and Spoke, Internet Access, etc…
•  For Providers
Same configuration operation for VPNv4 and VPNv6 VPN
No upgrade of IPv4 MPLS core (IPv6 unaware)
Upgrade of affected PE routers
Thank you.

IPv6 Using MPLS Vladimir Settey

Uploaded by

Copyright:

Available Formats

IPv6 Using MPLS Vladimir Settey

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IPv6 Using MPLS Vladimir Settey

Uploaded by

Copyright:

Available Formats

IPv6 Solutions using MPLS

• Tunneling over IPv4 and MPLS

• Protocol Translation (NAT64, NAT46, DNS64, etc.)

IPv6 IPv4 / IPv6 IPv4 configured interface

Some or all interfaces in cloud

• All P + PE routers are capable of IPv4+IPv6 support

IPv6 IPv4 / IPv6 IPv4 configured interface

Some or all interfaces in cloud

• Native Dual-Stack IPv4/IPv6 service on RG LAN side

RADIUS Framed-Protocol PPP

Link Local SLAAC + Default ICMPv6 Router Advertisement

IPv6 Network MPLS IPv4 Backbone IPv6 Network

IPv6 only CE ATM, Frame, Ethernet Interface

• No impact on existing MPLS Core (IPv6 unaware)

IPv6 Network MPLS IPv4 Backbone IPv6 Network

IPv6 only CE ATM, Frame, Ethernet Interface

Interface ethernet0/0.10 Interface ethernet0/0.10

IPv6 Network MPLS IPv4 Backbone IPv6 Network

• Uses manual tunnel configuration

IPv6 Network MPLS IPv4 Backbone IPv6 Network

interface loopback0 interface loopback0

interface tunnel100 interface tunnel100

router bgp 100 router bgp 100

address-family ipv6 address-family ipv6

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P 6PE2 CE2 2001:db8::

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P 6PE2 CE2 2001:db8::

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P 6PE2 CE2 2001:db8::

LDP {POP}  LDP {27}  LDP {48} 

MP-eBGP  IPv6 MP-iBGP  MP-eBGP 

• BGP Label also referred to as “Aggregate IPv6 Label”

• BGP NH is a “Special Use” IPv4 to IPv6 Mapped Address

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P CE2 2001:db8::

BGP Label: {65}

 IPv6  MPLS  MPLS  MPLS  IPv6

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P CE2 2001:db8::

IPv6 Network MPLS IPv4 Backbone IPv6 Network

CE3 6PE3 P P 6PE4 CE4

CE1 6PE1 P P CE2 2001:db8::

6PE-2#show ipv6 route

6PE-1#show ipv6 cef internal #hidden command

IPv6/IPv4 Network MPLS IPv4 Backbone IPv6/IPv4 Network

IPv4 VRF IPv4 VRF IPv4

• 6VPE enables services such as:

IPv6/IPv4 Network MPLS IPv4 Backbone IPv6/IPv4 Network

IPv4 VRF IPv4 VRF IPv4

• 6VPE uses existing IPv4 MPLS infrastructure to provide IPv6 VPN

• PEs must support dual stack IPv4+IPv6

• Offers same architectural features as MPLS-VPN for IPv4

• RTs, VRFs, RDs are appended to IPv6 to form VPNv6 address

IPv6/IPv4 Network MPLS IPv4 Backbone IPv6/IPv4 Network

•  Tunneling over IPv4 and MPLS

•  Protocol Translation (NAT64, NAT46, DNS64, etc.)

•  All P + PE routers are capable of IPv4+IPv6 support

•  Native Dual-Stack IPv4/IPv6 service on RG LAN side

•  No impact on existing MPLS Core (IPv6 unaware)

•  Uses manual tunnel configuration

•  BGP Label also referred to as “Aggregate IPv6 Label”

•  BGP NH is a “Special Use” IPv4 to IPv6 Mapped Address

•  6VPE enables services such as:

•  6VPE uses existing IPv4 MPLS infrastructure to provide IPv6 VPN

•  PEs must support dual stack IPv4+IPv6

•  Offers same architectural features as MPLS-VPN for IPv4

•  RTs, VRFs, RDs are appended to IPv6 to form VPNv6 address

•  For end-users: VPNv6 is same as VPNv4 services