6PE_6VPE_LACNIC

© 2007 Cisco Systems, Inc. All rights reserved. Cisco PubliclIPv6 over MPLS 1

IPv6 over MPLS

6PE and 6VPE

Hernán Contreras G.

Consulting Systems Engineer

Cisco Systems Chile

© 2007 Cisco Systems, Inc. All rights reserved. Cisco Publicl 2IPv6 over MPLS

IPv6 over MPLS

� Many service providers have already deployed MPLS in their IPv4 backbone for various reasons

� MPLS can be used to facilitate IPv6 integration

� Dual stack PE routers accommodating both IPv4 and IPv6 client networks

� IPv4 or MPLS core infrastructure is IPv6-unaware

� Benefits from MPLS features such as FRR, TE

IPv4 IPv4

IPv6 IPv6IPv4/MPLSBackbonePE

4/6PE4/6

inter-PE MPLS Tunnel (LSP)

P (4)


MPLS Tunnels – 6PE/6VPE

� IPv6 packets transported from 6PE to 6PE over Label Switch Path

RFC 4798: IPv6 provider edge router (6PE) over MPLS offers global IPv6 connectivity across IP/MPLS backbone (PSN)

RFC 4659: IPv6 VPN provider edge (6VPE) over MPLS offers global or VPN IPv6 connectivity across IP/MPLS backbone (PSN)

� BGP exchanges “external” client prefixes, labels, etc.

IPv6prefixes +Label for 6PE

VPNv6 prefixes for 6VPE

� In both cases backbone runs IPv4 control plane (plus label control for MPLS forwarding used)

IPv6 IPv6IPv4/MPLSBackbonePE

4/6PE4/6

MP-BGP w/ IPv6+labels IPv6IPv6

IPv6 NLRI redistribution

IPv6 NLRI redistribution


IPv6 over MPLS Tunnels

� Dual Protocol PE is encapsulating the IPv6 packet into MPLS packets

� MPLS Core remains IPv4

� Optionally PE provide VPN services for IPv6 (network virtualization)

IPv4/MPLSIPv6

Network

IPv6

Network

Tunnel: IPv6 in MPLS packet

IPv6

HostDual-Stack

PE Router

Dual-Stack

PE Router

IPv6

Host

IPv6 HeaderIPv6 HeaderMPLS HeaderMPLS Header

IPv6 HeaderIPv6 HeaderTransport Header

Transport Header DataData

DataDataTransport Header

Transport Header


v4

v6 v6

CE

CE

6PE

6PE 6PE

6PE

192.254.10.0

2001:CAFE::

2003:1::

192.76.10.0

145.95.0.0

2001:F00D::

2001:DB8::

Dual Stack IPv4-IPv6 RoutersDual Stack IPv4-IPv6 Routers

v6

v4

v4

v6

CE

IPv6 Provider Edge Router (6PE) over MPLS

� 6PEs must support dual stack IPv4+IPv6 (6PE)

� IPv6 addresses exist in global table of PE routers only

� IPv6 reachability exchanged among 6PEs via iBGP (MP-BGP)

IPv6 AF (2) + Label SAFI (4) used to exchange prefixes between PEs

� IPv6 packets transported from 6PE to 6PE inside MPLS (label switching)

� Core uses IPv4 control plane (LDPv4, TEv4, IGPv4, MP-BGP)

iBGP (MBGP) Sessions

IPv4MPLS

P P

P P

IPv6 global connectivity over and IPv4-MPLS core


6PE-1 Configuration (IOS)

200.10.10.2 Is the Remote 6PE

2001:DB8:1::1 Is the Local CE

6PE-1

2001:DB8::

6PE-2iBGP Session

Send Labels Along with IPv6 Prefixes by Means of MP-BGP

CE-1

router bgp 100

bgp router-id 200.10.10.1

no synchronization

no bgp default ipv4 unicast

neighbor 2001:DB8:1::1 remote-as 65014

neighbor 200.10.10.2 remote-as 100

neighbor 200.10.10.2 update-source Loopback0

!

address-family ipv6

neighbor 200.10.10.2 activate

neighbor 200.10.10.2 send-label

neighbor 2001:DB8:1::1 activate

redistribute connected

no synchronization

exit-address-family


6PE-1 Configuration (IOS-XR)

200.10.10.2 Is the Remote 6PE

2001:DB8:1::1 Is the Local CE

6PE-1

2001:DB8::

6PE-2iBGP Session

Send Labels Along with IPv6 Prefixes by Means of MP-BGP

CE-1

router bgp 100bgp router-id 200.10.10.1!address-family ipv6 unicastredistribute connectedallocate-label all!neighbor 200.10.10.2remote-as 100update-source Loopback0!address-family ipv6 labeled-unicast

neighbor 2001:DB8:1::1

remote-as 65014

address-family ipv6 unicast


6PE Routing And Label Distribution Example

IPv4MPLS

IPv4MPLS

CE3

IPv6IPv6

IPv6IPv6

6PE3 P P 6PE4 CE4

IPv6IPv6

IPv6IPv6

IPv6Packet

MPLS IPv4 BackboneIPv6 Network IPv6 Network

BGPLabel

IPv6Packet

LDPLabel

IPv6Packet

CE1 CE26PE1 P P 6PE2

200.10.10.1 200.11.11.1

2001:db8::2001:f00d::

LDPv4 {Pop}

MP-eBGP

LDPv4 {27} LDPv4 {48}

MP-eBGP IPv6 MP-iBGP

Advertises2001:f00d::

to 6PE1

Advertises2001:f00d:: to 6PE2

BGP Next Hop ::ffff:200.10.10.1Label Binding {65}

Binds label{Pop} to

200.10.10.1

Binds label{27} to

200.10.10.1

Binds label{48} to

200.10.10.1

Advertises2001:f00d::

to CE2

IGPv4 IGPv4 IGPv4

200.10.10.1reachable




6PE-1

6PE Routing/Label Distribution

6PE-2

P1 P2

2001:F00D::

2001:DB8::

200.10.10.1

200.11.11.1

IGPv4 Advertises Reachability of 200.10.10.1

IGPv6 or MP-BGP Advertising 2001:F00D::

IGP or MP-BGP Advertising 2001:F00D::

6PE-2 Sends MP-iBGP Advertisement to 6PE-1 Which Says:

2001:F00D:: Is Reachable

Via BGP Next Hop = 200.10.10.1 (6PE-2)

Bind BGP Label to 2001:F00D:: (*)

IPv6 Next Hop Is an IPv4 Mapped IPv6 Address Built from 200.10.10.1

LDPv4 Binds Label to 200.10.10.1

LDPv4 Binds Label to 200.10.10.1

LDPv4 Binds Implicit-Null (i.e.

Pop) to 200.10.10.1


6PE Routing Information

6PE-1# show bgp ipv6 unicast label 2001:F00D::/64BGP routing table entry for 2001:F00D::/64, version 2Paths: (1 available, best #1, table Global-IPv6-Table)Not advertised to any peerLocal::FFFF:200.10.10.1 (metric 10) from 200.10.10.1 (192.168.254.1)Origin incomplete, metric 0, localpref 100, valid, internal, best

6PE-1# show route ipv6 2001:F00D::/64

B 2800:F00D::/64 [200/0]

via ::ffff:200.10.10.1 (nexthop in vrf default), 00:02:29


6PE Forwarding Information 6PE-1# sh bgp ipv6 uni labels 2001:F00D::/64Network Next Hop Rcvd Label Local Label*>i20001:F00D::/64 200.10.10.1 65 16269

6PE-1# sh cef ipv6 2001:F00D::/64

2001:F00D::/64, version 0, internal 0x40040001 (0x796d3a08) [1], 0x0 (0x0), 0x4100 (0x796fd478)

Prefix Len 64, traffic index 0, precedence routine (0)

via ::ffff:200.10.10.1, 3 dependencies, recursive

next hop ::ffff:200.10.10.1 via ::ffff:200.10.10.1:0

local label 16269

next hop 192.168.1.5 Te1/2 labels imposed {48 65}

6PE-1# show mpls forwarding 200.10.10.1

Local Outgoing Prefix Bytes Label Outgoing Next Hop

Label Label or VC or Tunnel Id Switched interface

39 48 200.10.10.1/32 0 Te1/2 192.168.1.5


6PE Label Forwarding

IPv4MPLS

IPv4MPLS

CE3

IPv6IPv6

IPv6IPv6

6PE3 P P 6PE4 CE4

IPv6IPv6

IPv6IPv6

IPv6Packet

MPLS IPv4 BackboneIPv6 Network IPv6 Network

BGPLabel

IPv6Packet

LDPLabel

IPv6Packet

CE1 CE26PE1 P P 6PE2

200.10.10.1 200.11.11.1

2001:db8::2001:f00d::

IPv6 MPLS

2001:f00d::2001:f00d::

{65}

{48}

MPLS

2001:f00d::

{65}

MPLS

2001:f00d::

{65}

{27}

IPv6

2001:f00d::

Value

2001:f00d::::ffff:200.10.10.1200.10.10.1{48}

IPv6 Prefix:BGP NH:

IPv4 NH:LDP Label:

Item

LDP IPv4 Label

BGP IPv6 Label

IPv6 Prefix


6PE-1

6PE-2

IPv6 Forwarding and Label Imposition:� 6PE-1 receives an IPv6 packet

� Lookup is done on IPv6 prefix

� Result is:Label binded by MP-BGP to 2001:F00D::

Label1 binded by LDP/IGPv4 to the IPv4 address of BGP next hop (6PE-2)

6PE Forwarding (6PE-1)

2001:F00D::

2001:DB8::

IPv6 Packet

MP-BGP Label

LDP/v4 Label1 to 6PE-2

P1 P2

IPv6 Packet

to 2001:F00D::1


6PE-2

2001:F00D::

2001:DB8::

P1 P2

IPv6 PacketMP-BGP Label

LDP/v4 Label2 to 6PE-2

6PE Forwarding (P1)

6PE-1

IPv6-UNaware MPLS Label Switching:� P1 receives an MPLS packet

� Lookup is done on Label1

� Result is Label2


6PE-2

2001:F00D::

2001:DB8::

P1 P2

6PE-1

IPv6 PacketMP-BGP Label

6PE Forwarding (P2)

IPv6-UNaware MPLS Label Switching:� P2 receives an MPLS packet

� Lookup is done on Label2

�Result includes Pop label (PHP), if used


6PE-2

2001:F00D::

2001:DB8::

P1 P2

6PE-1

6PE Forwarding (6PE-2)

� MPLS label forwarding:

� 6PE-2 receives an MPLS packet

� Lookup is done on label

� Result is:Pop label and do IPv6 lookup on v6 destination


6PE Benefits

� IPv6 global table connectivity for different sites

� Incremental deployment possible

Only upgrade the PE routers which have to provide IPv6 connectivity

� Core network (Ps) untouched

no HW/SW upgrade, no configuration change

� IPv6 traffic inherits MPLS benefits

� Each site can be v4-only, v4VPN-only, v4+v6, v4VPN+v6

� P routers won’t be able to send ICMPv6 messages (TTL expired, traceroute)

� No VRF configuration


IPv4MPLS

IPv4MPLS

IPv6 VPN 6VPE (RFC 4659)

IPv4IPv6

IPv4IPv6

P P

IPv6Packet

MPLS IPv4 BackboneIPv6/IPv4 Network IPv6/IPv4 Network

VPNLabel

IPv6Packet

LDPLabel

IPv6Packet

CE1 6VPE1

P P

10.1.1.0/24

2001:db8:beef:1::/64

VRF

200.10.10.1 200.11.11.1

CE2

IPv4IPv6

IPv4IPv6

VRF

10.1.2.0/24

2001:db8:beef:2::/64

172.16.3.0/30

2001:db8:cafe:3::/64

172.16.1.0.0/30

2001:db8:cafe:1::/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

6VPE2


6VPE: BGP-MPLS VPN extension for IPv6 (RFC 4659)

VPN YELLOW

VPN YELLOW

VPN BLUE

v4 and v6 VPNVPN BLUE

v6 Only

v6 Only

v4 and v6 VPN

VPN YELLOW

VPN BLUE

v6 Only

v4 and v6 VPN

MPLS VPNs

P P

P P

iBGP (MBGP) Sessions

Layer-3 VPNs for IPv6 customers

Apply all RFC4364bis mechanisms to IPv6 VPNs:

• IPv6-VPN reachability exchanged among PEs via MP-BGP

• New BGP address family: AFI=2 (IPv6”), SAFI=128 (VPN)

• NLRI in the form of <length, VPN-IPv6-prefix, label>

• 192bits Address (24 Byte) including the 64 bits route distinguisher (8 Bytes)

and the 128 bits IPv6 address (16 Bytes)

• Nexthop is carried as RD:v4-mapped-v6-address

• VRFs, RT, SOO, RRs,…operate exactly as with IPv4-VPN IPv6 packets

<RD:IPv6>


6VPE Configuration (IOS)New Multi-AF VRF Configuration

CE1-BLUE

VRF GREEN

CE1

6VPE1

vrf definition GREENrd 200:1!address-family ipv4route-target export 200:1route-target import 200:1exit-address-family!address-family ipv6route-target export 200:1route-target import 200:1exit-address-family

IPv4IPv6

IPv4IPv6

VRF172.16.1.0/30

2001:db8:cafe:1::/64

� New VRF AF definition

Allows address-families

Each with unique or common policies

� vrf upgrade-cli multi-af-mode {common-policies | non-common-policies} [vrf <name>]

This command can update existing VRF definitions

interface Ethernet0/0Description Link to CE1vrf forwarding GREENip address 172.16.1.1 255.255.255.0ipv6 address 2001:db8:cafe:1::1/64


6VPE Configuration (IOS-XR)New Multi-AF VRF Configuration

CE1-BLUE

VRF GREEN

CE1

6VPE1

IPv4IPv6

IPv4IPv6

VRF172.16.1.0/30

2001:db8:cafe:1::/64

interface Ethernet0/0vrf GREENipv4 address 172.16.1.2 255.255.255.0ipv6 address 2001:db80:cafe:1::1/64dot1q vlan 2

vrf GREEN!address-family ipv4 unicastimport route-target200:1!export route-target200:1!

address-family ipv6 unicastimport route-target200:1!export route-target200:1!


6VPE MP-BGP Configuration (IOS)

CE1-BLUE

VRF GREEN

CE1

6VPE1

IPv4IPv6

IPv4IPv6

VRF172.16.1.0/30

2001:db8:cafe:1::/64

router bgp 100neighbor 200.10.10.2 remote-as 100neighbor 200.10.10.2 update-source lo0!address-family ipv4 �� Internet Routesneighbor 200.10.10.2 activateno auto-summaryno synchronizationexit-address-family!address-family vpnv4 �� To 6VPE2neighbor 200.10.10.2 activateneighbor 200.10.10.2 send-community extexit-address-family

address-family vpnv6 �� To 6VPE2neighbor 200.10.10.2 activateneighbor 200.10.10.2 send-community extexit-address-family!address-family ipv4 vrf GREEN �� To CE1redistribute connectedneighbor 172.16.1.1 remote-as 500neighbor 172.16.1.1 activateexit-address-family!address-family ipv6 vrf GREEN �� To CE1neighbor 2001:db8:cafe:1::1 remote-as 500neighbor 2001:db8:cafe:1::1 activateexit-address-family

6VPE1MP-iBGPSession


6VPE MP-BGP Configuration (IOS-XR)

CE1-BLUE

VRF GREEN

CE1

6VPE1

IPv4IPv6

IPv4IPv6

VRF172.16.1.0/30

2001:db8:cafe:1::/64

router bgp 100bgp router-id 192.168.0.6!address-family vpnv4 unicast!address-family vpnv6 unicast!neighbor 200.10.10.2remote-as 100update-source Loopback0

!address-family vpnv4 unicast!address-family vpnv6 unicast!

vrf GREENrd 200:1!address-family ipv6 unicastredistribute connected!neighbor 2001:db80:cafe:1::2remote-as 500address-family ipv6 unicastroute-policy pass inroute-policy pass out!

6VPE1MP-iBGPSession


6VPE: IPv4 Routing/Label Distribution

6VPE-2

6VPE-1

P1 P2

2001:BEEF:1::

2001:BEEF:1::

192.254.10.17

IGPv4 advertises reachability of 200.10.10.2

Regular IPv4 routing and IPv4 Label Distribution

For reachability of 6VPEs

LDPv4 binds label2 to 200.10.10.2

LDPv4 binds label1 to 200.10.10.2

LDPv4 binds Implicit-Null (ie pop) to 200.10.10.2

Site-1

Site-1

mpls ldp

router-id 200.10.10.1mpls ldp

router-id 200.10.10.2


6VPE VRF Routing/Label Distribution (MP-BGP)

2001:BEEF:1::

• Regular IPv6 vrf routing between PE-CE (eBGP, Static, OSPFv3)

• MP-BGP VPNv6 routing PE-to-PE

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

200.10.10.2

6VPE-2 sends MP-iBGP advertisement to 6VPE-1 which says:

2001:BEEF:2:: reachable

via BGP Next Hop = ::FFFF:200.10.10.2 (6VPE-2)

bind BGP 16010 to 2001:BEEF:2::

e-BGP advertising 2001:BEEF:1::

e-BGP advertising 2001:BEEF:1::

Site-1

Site-1

200.10.10.1MP-iBGP Session


IPv4MPLS

IPv4MPLS

6VPE1 BGP VPNv6 Table

IPv4IPv6

IPv4IPv6

P P


CE1 6VPE1

P P

10.1.1.0/24

2001:beef:1::/64

VRF

200.10.10.1 200.10.10.2

CE2

IPv4IPv6

IPv4IPv6

VRF

10.1.2.0/24

2001:beef:2::/64

172.16.2.0.0/30

2001:db8:cafe:2::/64

172.16.1.0/30

2001:db8:cafe:1::/64

6VPE1#show bgp vpnv6 unicast all Network Next Hop Metric LocPrf Weight PathRoute Distinguisher: 200:1 (default for vrf GREEN)*> 2001:beef:1::/64

2001:db8:cafe:1::1 �� Route from CE10 0 500 ?

*>i2001:beef:2::/64::FFFF:200.10.10.2 �� Route from CE2 via 6VPE2

0 100 0 506 ?*>i2001:db8:cafe:2::/64

::FFFF:200.10.10.2 �� PE/CE Connected route from 6VPE20 100 0 ?

6VPE2

IPv4-MappedIPv6 Address(IPv4-Based LSP Setup)


IPv4MPLS

IPv4MPLS

6VPE2 IPv6 VRF Routes (IOS)

IPv4IPv6

IPv4IPv6

P P


CE1 6VPE1

P P

10.1.1.0/24

2001:beef:1::/64

VRF

200.10.10.1 200.10.10.2

CE2

IPv4IPv6

IPv4IPv6

VRF

10.1.2.0/24

2001:beef:2::/64

172.16.2.0.0/30

2001:db8:cafe:2::/64

172.16.1.0/30

2001:db8:cafe:1::/64

6VPE1#show ipv6 route vrf GREENB 2001:beef:2::/64 [200/0]

via 200.10.10.2%Default-IP-Routing-Table, indirectly connectedB 2001:beef:1::/64 [20/0]

via FE80::A8BB:CCFF:FE01:FA00, Ethernet1/0B 2001:db8:cafe:2::/64 [200/0]

via 200.10.10.1%Default-IP-Routing-Table, indirectly connectedC 2001:db8:cafe:1::/64 [0/0]

via Ethernet1/0, directly connectedL 2001:db8:cafe:1::2/128 [0/0]

via Ethernet1/0, receiveL FF00::/8 [0/0]

via Null0, receive

6VPE2


IPv4MPLS

IPv4MPLS

6VPE2 IPv6 VRF Routes (IOS-XR)

IPv4IPv6

IPv4IPv6

P P


CE1 6VPE1

P P

10.1.1.0/24

2001:beef:1::/64

VRF

200.10.10.1 200.10.10.2

CE2

IPv4IPv6

IPv4IPv6

VRF

10.1.2.0/24

2001:beef:2::/64

172.16.2.0.0/30

2001:db8:cafe:2::/64

172.16.1.0/30

2001:db8:cafe:1::/64

PE1#sh route vrf red ipv6

B 2001::beef:2::/64[200/0] via ::ffff:200.10.10.2 (nexthop in vrf default), 07:04:14

C 2001:db80:cafe:1::/64 is directly connected,08:28:12, GigabitEthernet0/0/1/3.1

L 2001:db80:cafe:1::1/128 is directly connected,08:28:12, GigabitEthernet0/0/1/3.1

6VPE2


6VPE Label Stack Forwarding:Populating 6VPE-1 FIB VRF Table (2nd label)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1


2001:BEEF:2:: is reachable

via BGP Next Hop = ::FFFF:200.10.10.2 (6VPE-2)

bind BGP 16010 to 2001:BEEF:2::

???/160102001:BEEF:2::

LabelsPrefix

Site-1

Site-1

vrf GREEN


6VPE Label Stack Forwarding:Populating 6PE-1 FIB VRF Table (1st label)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1


2001:BEEF:2:: is reachable

via BGP Next Hop = 200.10.10.2 (6VPE-2)

bind BGP label 16010 to 2001:BEEF:2::

LDPv4 binds label1to 200.10.10.2 label1/160102001:0421::

LabelsPrefix

Recursion of BGP Next Hop: populate entry with LDP label

Site-1

Site-1


IPv4MPLS

IPv4MPLS

6VPE1 LFIB

IPv4IPv6

IPv4IPv6

P P

IPv6Packet


VPNLabel

IPv6Packet

LDPLabel

IPv6Packet

CE1 6VPE1

P P

10.1.1.0/24

2001:beef:1::/64

VRF

200.10.10.1 200.10.10.2

CE2

IPv4IPv6

IPv4IPv6

VRF

10.1.2.0/24

2001:beef:2::/64

172.16.3.0.0/30

2001:db8:cafe:2::/64

172.16.1.0/30

2001:db8:cafe:1::/64

6VPE2

6VPE1#show mpls forwarding 200.10.10.2Local Outgoing Prefix Outgoing Next Hop Label Label interface17 18 200.10.10.2/32 Et0/0 192.168.1.1

6VPE2#show mpls forwardingLocal Outgoing Prefix Outgoing Next Hop Label Label interface 16010 No Label 2001:BEEF:2::/64 Et0/0 FE80::A8BB:CCFF:FE01:F400

6VPE1#sh ipv6 cef vrf BLUE2001:BEEF:2::/64nexthop 192.168.1.1 Ethernet0/0 label 18 16010


6VPE Forwarding (6VPE-1)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1

IPv6 packet

to 2001:BEEF:2::

IPv6 packet

to 2001:BEEF:2::IGPv4/LDP

label1 to 6VPE-2

MP-BGP 16010

to 2001:BEEF:2::

IPv6 Forwarding and Label Imposition:•

6VPE-1 receives an IPv6 packet•

Lookup is done on IPv6 prefix, in vrf yellow•

Result is “push two labels”:

Label 16010 binded by MP-BGP to 2001:BEEF:2::

Label1 binded by LDP/IGPv4 to the IPv4 address of BGP Next Hop (6VPE-2)

Site-1

Site-1

vrf yellow6vpe1#sh ipv6 cef vrf BLUE2001:BEEF:2::/64nexthop 192.168.1.1 Ethernet0/0 label 18 16010


6VPE Forwarding (P1)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1

IPv6 packet

to 2001:BEEF:2::

IPv6 packet


label1 to 6VPE-2

MP-BGP 16010

to 2001:BEEF:2::

IGPv4/LDP

label2 to 6PE-2

Site-1

Site-1

vrf yellow

IPv6 packet

to 2001:BEEF:2::MP-BGP 16010

to 2001:BEEF:2::

IPv6-UNaware MPLS Label Switching:•

P1 receives an MPLS packet•

Lookup is done on Label1•

Result is Label2

P1#show mpls forwarding 200.10.10.1Local Outgoing Prefix Outgoing Next Hop Label Label interface17 18 200.10.10.2/32 Et0/0 192.168.1.5


6VPE Forwarding (P2)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1

IPv6 packet

to 2001:BEEF:2::

IPv6 packet


label1 to 6VPE-2

MP-BGP 16010

to 2001:BEEF:2::

IGPv4/LDP

label2 to 6PE-2

IPv6 packet

to 2001:BEEF:2::MP-BGP 16010

to 2001:BEEF:2::

Site-1

Site-1

vrf yellow

IPv6 packet

to 2001:BEEF:2::MP-BGP 16010

to 2001:BEEF:2::

IPv6-UNaware MPLS Label Switching:•

P2 receives an MPLS packet•

Lookup is done on Label2•

Result is Pop label (Penultimate Hop Popping)

P1#show mpls forwarding 200.10.10.2Local Outgoing Prefix Outgoing Next Hop Label Label interface18 Pop Label 200.10.10.2 Et0/0 192.168.1.9


6VPE Forwarding (6VPE-2)

6VPE-2

6VPE-1

P1 P2

2001:BEEF:2::

2001:BEEF:1::

200.10.10.2

200.10.10.1

IPv6 packet

to 2001:BEEF:2::

IPv6 packet

to 2001:BEEF:2::

IPv6 packet


label1 to 6VPE-2

MP-BGP 16010

to 2001:BEEF:2::

IGPv4/LDP

label2 to 6PE-2

IPv6 packet

to 2001:BEEF:2::MP-BGP 16010

to 2001:BEEF:2::

Site-1

Site-1

vrf yellow

IPv6 packet

to 2001:BEEF:2::MP-BGP 16010

to 2001:BEEF:2::

MPLS Label Pop and IPv6 Forwarding :•

6VPE-2 receives an MPLS packet•

Lookup is done on 16010•

If per-vrf label allocation mode is configured, lookup is done on inner IPv6 destination address in the VRF yellow.

pe1#show mpls forwarding 2001:BEEF:2::/64Local Outgoing Prefix Outgoing Next Hop Label Label interface 16010 No Label 2001:DB8:CAFE:2::/64 Et0/0 FE80::A8BB:CCFF:FE01:F400


6VPE Summary

� RFC4659: BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN

� 6VPE simply adds IPv6 support to current IPv4 MPLS VPN offering

� For end-users: v6-VPN is same as v4-VPN services (QoS, hub and spoke, internet access, etc.)

� For operators:

Same configuration operation for v4 and v6 VPN

No upgrade of IPv4/MPLS core (IPv6 unaware)


Documents

6PE_6VPE_LACNIC