Layer 3 Virtual Private Networks (l3vpn) ---------------------------------------- Charter Last Modified: 2006-03-30 Current Status: Active Working Group Chair(s): Rick Wilder Ronald Bonica Internet Area Director(s): Jari Arkko Mark Townsley Internet Area Advisor: Mark Townsley Technical Advisor(s): Alex Zinin Mailing Lists: General Discussion:l3vpn@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/l3vpn Archive: http://www.ietf.org/mail-archive/web/l3vpn/index.html Description of Working Group: Alex Zinin is the routing advisor. This working group is responsible for defining and specifying a limited 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 Aug 2006 Submit specification of IPv4 multicast over BGP/MPLS VPNs for publication Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jul 2001 Dec 2005 An Architecture for Provider Provisioned CE-based Virtual Private Networks using IPsec Jul 2001 Aug 2005 BGP-MPLS IP VPN extension for IPv6 VPN Jul 2001 Aug 2005 Architecture for the Use of PE-PE IPsec Tunnels in BGP/MPLS IP VPNs Jul 2001 Aug 2005 Use of PE-PE GRE or IP in BGP/MPLS IP Virtual Private Networks Jul 2001 Apr 2006 Using BGP as an Auto-Discovery Mechanism for VR-based Layer-3 VPNs Jul 2001 Mar 2006 Network based IP VPN Architecture Using Virtual Routers Sep 2001 Aug 2005 Virtual Router Management Information Base Using SMIv2 Aug 2002 Feb 2004 Applicability Statement for Virtual Router-based Layer 3 PPVPN approaches Jan 2004 Jan 2004 Applicability Statement for Provider Provisioned CE-based Virtual Private Networks using IPsec Jun 2004 Jun 2005 Constrained VPN Route Distribution Feb 2005 May 2006 Requirements for Multicast in L3 Provider-Provisioned VPNs Jun 2005 Jun 2006 Multicast in MPLS/BGP IP VPNs Aug 2006 Aug 2006 BGP Encodings for Multicast in MPLS/BGP IP VPNs Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC3809 I Jun 2004 Generic Requirements for Provider Provisioned Virtual Private Networks RFC4026 I Mar 2005 Provider Provisioned Virtual Private Network (VPN) Terminology RFC4031 I Apr 2005 Service requirements for Layer 3 Provider Provisioned Virtual Private Networks RFC4110 I Jul 2005 A Framework for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs) RFC4111 I Jul 2005 Security Framework for Provider Provisioned Virtual Private Networks (PPVPNs) RFC4176 I Oct 2005 Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management RFC4265Standard Dec 2005 Definition of Textual Conventions for Virtual Private Network (VPN) Management RFC4364Standard Feb 2006 BGP/MPLS IP Virtual Private Networks (VPNs) RFC4365 I Feb 2006 Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs) RFC4382Standard Feb 2006 MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base RFC4577 PS Jun 2006 OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)