1. PCEP extensions for a BGP/MPLS IP-VPN
draft-kumaki-murai-pce-pcep-extension-l3vpn-05.txt
Kenji Kumaki KDDI Corporation
Tomoki Murai Furukawa Network Solution Corp.
Tomohiro Yamagata　　KDDI Corporation
Chikara Sasaki KDDI R&D Labs
March 2010
77th

2. Motivation
Some Service Providers will deploy services that request QoS guarantees from a local CE to a remote CE across the network.
draft-ietf-l3vpn-e2e-rsvp-te-reqts [RFC Ed Queue]
A VPN customer desires their MPLS TE LSPs for interconnectivity between BGP/MPLS IP-VPN sites.
The PCE architecture is the most suitable to calculate MPLS TE LSPs between BGP/MPLS IP-VPN sites.
March 2010
77th

3. Problem Statement ? ? PCReq message BGP/MPLS IP-VPN PCRep message
CE 1 C0 C4
CE 5 C3
CE 2
CE 6 C7
PE 1 P
PE 2
PCE 1
PCE 2
VPN 1
VPN 2
VPN 2: MPLS TE LSPs
VPN 1: MPLS TE LSPs
PCReq message ? ?
PCRep message
The PCE2 can’t distinguish PCReq messages between the VPN1 and the VPN2 when it sends them to the same destination.
The PCE 2 can’t calculate an appropriate TE LSP between CEs per a VPN.
The PCE1 can’t distinguish PCRep messages between the VPN1 and the VPN2 when it sends them to the same destination.
The PCE1 can’t reply the PCRep messages corresponding to the PCReq messages from PCC/PCE.
March 2010
77th

4. PCEP Extensions
The new Object-Types for VPN-IPv4 address and VPN-IPv6 address in END-POINTS object.
A new END-POINTS object consists of the original source/destination IPv4/IPv6 address and the Route Distinguisher(RD).
March 2010
77th

5. Handling BGP/MPLS IP-VPN Identify VPN Identify VPN PCE 1 PCE 2 VPN 1
END-POINTS object
IPv4/IPv6 address
PCReq message
VPN-IPv4/IPv6 address
Identify VPN
BGP/MPLS IP-VPN CE
CE (PCC)
PCE 1
PCE 2
VPN 1
PCRep message
END-POINTS object
VPN-IPv4/IPv6 address
Identify VPN
VPN 1
Ingress PE P P
Egress PE
CE (PCC) CE
VPN 2
VPN 2
PCReq messages
An ingress PE (PCE1) puts VPN-IPv4/IPv6 address in the END-POINTS object and send the PCReq message to an egress PE.
An egress PE (PCE2) Identifies a VPN from the VPN-IPv4/IPv6 address in the END-POINTS object.
PCRep messages
An egress PE(PCE2) can look up the new END-POINTS object associated with the PCReq message and puts VPN-IPv4/IPv6 address in the END-POINTS object and send the PCRep message to an egress PE.
An ingress PE (PCE1) Identifies a VPN from the VPN-IPv4/IPv6 address in the END-POINTS object.
March 2010
77th

6. Recent Update Updated text for clarity and readability Minor edit
rewrite abstract, introduction and problem statement
Include step by step procedure of PCReq message processing at Ingress PE(PCE)
remove section 3 on terminology
Minor edit
change the notation of head-end/tail-end router from CE to C in Fig. 1
change the title of 4.2 from "Handling" to "PCE capabilities“
IANA Consideration
The values 3 and 4 are suggested.
March 2010
77th 6

7. Next Steps Need more comments and feedback from WG
Request WG to accept this I-D as a WG document
March 2010
77th