Title: ASBR VRF Context for BGP/MPLS IP VPN IETF-65
1ASBR VRF Context for BGP/MPLS IP VPNIETF-65
- draft-kulmala-l3vpn-interas-option-d-02.txt
Marko Kulmala Ville Hallivuori Martin
Halstead Jyrki Soini Jim Guichard
2Draft Overview and History
ABSTRACT This option combines per VPN VRFs at the
Autonomous System Border Router (ASBR) as
described in 'Option A' with the redistribution
of labeled VPN-IPv4 routes as described in
'Option B'. In addition, this option allows for a
data plane consisting of two methods of traffic
forwarding between attached ASBR pairs.
- Combination of Multi-AS options a and b,
targeted at Multi-AS MPLS IP VPN (RFC 4364)
service extensions. - MP-eBGP peering between ASBRs
- ASBR has a minimum of a VRF per VPN
- Hierarchical per-VPN admission control at the AS
border - Allows VPN topology hiding, traffic load
balancing, path optimization, route
summarization, route capping etc. - Trust model of Option B remained specifically
MPLS based data plane addressed in this draft - Added new authors
3Operation Shared Interface Forwarding
MP-eBGP peer plus global labeled interface
AS 1
AS 2
CE1
CE2
VRF1 _at_ PE1
VRF4_at_ PE2
VRF3 _at_ ASBR2
VRF 2 _at_ ASBR1
VPN Membership Domain
VPN Membership Domain
VPN Membership Domain
4Operation Private Interface Forwarding
MP-eBGP peer
AS 1
AS 2
Back-to-back VRF Attachment Circuit
CE1
CE2
VRF1 _at_ PE1
VRF4_at_ PE2
VRF3 _at_ ASBR2
VRF 2 _at_ ASBR1
VPN Membership Domain
VPN Membership Domain
VPN Membership Domain
5What is covered in this Draft?
draft-kulmala-l3vpn-interas-option-d-02.txt
- Updated the following sections
- Reference Model
- Operation section
- Deployment Considerations
- Comparison of current RFC 4364 Multi-AS options
- Security section
6Next steps
draft-kulmala-l3vpn-interas-option-d-02.txt
- More discussion on the list particularity from
Service Providers wanting to partner at Layer 3 - Adopt the ID as a WG Document