Layer 3 Virtual Private Networks (l3vpn) Internet Drafts
| Architecture for the Use of PE-PE IPsec Tunnels in BGP/MPLS IP VPNs | |||||||||||||||||
|
In BGP/MPLS IP Virtual Private Networks (VPNs), VPN data packets traveling from one Provider Edge (PE) router to another generally carry two MPLS labels, an "inner" label that corresponds to a VPN- specific route, and an "outer" label that corresponds to a Label Switched Path (LSP) between the PE routers. In some circumstances, it is desirable to support the same type of VPN architecture, but using an IPsec Security Association in place of that LSP. The "outer" MPLS label would thus be replaced by an IP/IPsec header. This enables the VPN packets to be carried securely over non-MPLS networks, using standard IPsec authentication and/or encryption functions to protect them. This draft specifies the procedures which are specific to support of BGP/MPLS IP VPNs using the IPsec encapsulation. | ||||||||||||||||
| Multicast in MPLS/BGP IP VPNs | |||||||||||||||||
|
In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual Private Network) to travel from one VPN site to another, special protocols and procedures must be implemented by the VPN Service Provider. These protocols and procedures are specified in this document. | ||||||||||||||||
| BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs | |||||||||||||||||
|
This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in [MVPN]. | ||||||||||||||||
| Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN | |||||||||||||||||
|
Some service providers want to build a service which guarantees QoS or bandwidth from a local CE to a remote CE through the network. Today, customers expect to run triple play services through BGP/MPLS IP-VPNs. As a result, their requirements for end-to-end QoS of applications are increasing. Depending on the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.), an end-to-end native RSVP path and/or an end-to-end MPLS TE LSP are required, and they need to meet some constraints. This document describes service provider requirements for supporting customer RSVP and RSVP-TE over a BGP/MPLS VPN. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Layer 3 Virtual Private Networks (l3vpn)
Last Modified: 2008-07-18
Additional information is available at tools.ietf.org/wg/l3vpn
Chair(s):
Routing Area Director(s):
Routing Area Advisor:
Mailing Lists:
General Discussion: l3vpn@ietf.orgTo Subscribe: https://www1.ietf.org/mailman/listinfo/l3vpn
Archive: http://www.ietf.org/mail-archive/web/l3vpn/index.html
Description of Working Group:
This working group is responsible for defining and specifying alimited number of solutions for supporting provider-provisioned
Layer-3 (routed) Virtual Private Networks (L3VPNs).
The WG is responsible for standardization of the following solutions:
1. BGP/MPLS IP VPNs (based on RFC 2547)
2. IP VPNs using Virtual Routers
3. CE-based VPNs using IPsec
The following VPN deployment scenarios will be considered by the WG:
1. Internet-wide: VPN sites attached to arbitrary points in
the Internet
2. Single service provider (SP)/single AS: VPN sites attached to
the network of a single provider within the scope of a single
AS
3. Single SP/multiple AS'es: VPN sites attached to the network
of a single provider consisting of multiple AS'es
4. Cooperating SPs: VPN sites attached to networks of different
providers that cooperate with each other to provide VPN service
The WG will address deployment of the following features in a VPN
environment:
1. IP Multicast
2. IPv6
As part of this effort the WG will work on the following tasks
(additional work items will require rechartering):
1. Requirements and framework for Layer 3 VPNs
2. Solution documents for each approach listed above (including
applicability statements)
3. MIB definitions for each approach
4. Security mechanisms for each approach
As a general rule, the WG will not create new protocols, but will
provide functional requirements for extensions of the existing
protocols that will be discussed in the protocol-specific WGs. L3VPN
WG will review proposed protocol extensions for L3VPNs before they are
recommended to appropriate protocol-specific WGs.
As stated above, the WG will define an IPv6 over BGP / MPLS VPN
solution. This will include a forwarding plane component and a
control plane component. In the forwarding plane, IPv6 datagrams will
be encapsulated within an MPLS header. If any aspect of IPv6
forwarding over MPLS is as yet undefined, the L3VPN WG will defer to
the MPLS and appropriate IPv6 WGs. On the control plane, BGP
extensions may also need to be defined. In this respect, the L3VPN WG
will defer to the IDR and appropriate IPv6 WGs.
QoS support is excluded from the charter at this time. It may be
considered for inclusion in an updated charter at a later time. Future
work items may also include OAM support.
Goals and Milestones:
| Done | Submit L3 VPN Requirements Document to IESG for publication as Info | |
| Done | Submit Generic Requirements Document to IESG for publication as Info | |
| Done | Submit L3 VPN Framework Document to IESG for publication as Info | |
| Done | Submit VPN Security Analysis to IESG for publication as Info (draft-fang-ppvpn-security-framework-00) | |
| Done | Submit BGP/MPLS VPNs specification and AS to IESG for publication as PS (draft-ietf-ppvpn-rfc2547bis-03, draft-ietf-ppvpn-as2547-01) | |
| Done | Submit CE-based specification and AS to IESG for publication as PS (draft-ietf-ppvpn-ce-based-03, draft-declercq-ppvpn-ce-based-sol-00, draft-declercq-ppvpn-ce-based-as-01) | |
| Done | Submit Virtual Router specification and AS to IESG for publication as PS (draft-ietf-ppvpn-vpn-vr-03, draft-ietf-ppvpn-as-vr-01) | |
| Done | Submit BGP as an Auto-Discovery Mechanism for publication as PS (draft-ietf-ppvpn-bgpvpn-auto-05.txt) | |
| Done | Submit specification of using GRE for PE-PE encapsulation in BGP/MPLS VPNs to IESG for publication as PS (draft-ietf-ppvpn-gre-ip-2547-02) | |
| Done | Submit VPN MIB Textual Conventions to IESG for publication as PS (draft-ietf-ppvpn-tc-mib-02) | |
| Done | Submit MPLS/BGP VPN MIB to IESG for publication as PS (draft-ietf-ppvpn-mpls-vpn-mib-05) | |
| Done | Submit VR MIB to IESG for publication as PS (draft-ietf-ppvpn-vr-mib-04) | |
| Done | Submit specification of using IPSEC for PE-PE encapsulation in BGP/MPLS VPNs to IESG for publication as PS (draft-ietf-ppvpn-ipsec-2547-03) | |
| Done | Submit specification of OSPF as the PE/CE Protocol in BGP/MPLS VPNs for publication (draft-ietf-l3vpn-ospf-2547-xx.txt) | |
| Done | Submit specification of IPv6 over BGP/MPLS VPNs for publication | |
| Feb 2008 | Submit specification of IPv4 multicast over BGP/MPLS VPNs for publication |
Internet-Drafts:
Architecture for the Use of PE-PE IPsec Tunnels in BGP/MPLS IP VPNs (43083 bytes)Multicast in MPLS/BGP IP VPNs (220690 bytes)
BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs (131159 bytes)
Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN (55507 bytes)
Request For Comments:
Generic Requirements for Provider Provisioned Virtual Private Networks (RFC 3809) (60576 bytes)Provider Provisioned Virtual Private Network (VPN) Terminology (RFC 4026) (42124 bytes)
Service requirements for Layer 3 Provider Provisioned Virtual Private Networks (RFC 4031) (118568 bytes)
A Framework for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs) (RFC 4110) (204159 bytes)
Security Framework for Provider Provisioned Virtual Private Networks (PPVPNs) (RFC 4111) (106626 bytes)
Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management (RFC 4176) (46348 bytes)
Definition of Textual Conventions for Virtual Private Network (VPN) Management (RFC 4265) (10976 bytes)
Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs) (RFC 4365) (77924 bytes)
BGP/MPLS IP Virtual Private Networks (VPNs) (RFC 4364) (116446 bytes) obsoletes RFC 2547/ updated by RFC 4577,RFC 4684
MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base (RFC 4382) (85594 bytes)
OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) (RFC 4577) (61515 bytes) updates RFC 4364
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN (RFC 4659) (42090 bytes)
Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protcol (IP) Virtual Private Networks (VPNs) (RFC 4684) (28475 bytes) updates RFC 4364
Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks (RFC 4797) (18985 bytes)
Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private (PPVPNs) (RFC 4834) (80341 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
