Layer 3 Virtual Private Networks (l3vpn) Concluded WG
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Layer 3 Virtual Private Networks | |
|---|---|---|---|
| Acronym | l3vpn | ||
| Area | Routing Area (rtg) | ||
| State | Concluded | ||
| Charter | charter-ietf-l3vpn-05 Approved | ||
| Dependencies | Document dependency graph (SVG) | ||
| Personnel | Chairs |
Martin Vigoureux
Thomas Morin |
|
| Area Director |
Adrian Farrel
|
||
| Mailing list | Address | l3vpn@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/l3vpn | ||
| Archive | https://mailarchive.ietf.org/arch/search/?email_list=l3vpn | ||
Charter for Working Group
This working group is responsible for defining, specifying and extending
BGP/MPLS IP VPNs solutions (based on RFC4364 and RFC4659) for supporting
provider-provisioned Layer-3 (routed) Virtual Private Networks (L3VPNs).
The WG will continue to extend and enhance RFC4364 and RFC4659 based
solutions so that these solutions can be used to provide IPv4, IPv6, and
MPLS services including multicast.
The following VPN deployment scenarios will be considered by the WG: 1.
Single service provider (SP)/single AS: VPN sites attached to the
network of a single provider within the scope of a single AS.
2. Single SP/multiple AS'es: VPN sites attached to the network of a
single provider consisting of multiple AS'es.
3. Cooperating SPs: VPN sites attached to networks of different
providers that cooperate with each other to provide VPN service.
As part of this effort the WG will work on the following tasks:
1. Additional requirements and framework for Layer 3 VPNs.
2. Solution documents, including applicability statements.
3. MIB definitions.
4. Security mechanisms.
As a general rule, the WG will not create new protocols, but will extend
existing protocols to provide the necessary L3VPN functionality.
Protocol extensions that provide L3VPN functionality will be reviewed by
both the L3VPN WG and by the WG responsible for the protocol being extended.
The WG will continue to extend and enhance the Multicast over BGP/MPLS
VPN solution.
Milestones
| Date | Milestone |
|---|---|
| Oct 2014 |
Submit specification of BGP as an MVPN PE-CE protocol
draft-ietf-l3vpn-mvpn-pe-ce |
| Apr 2014 |
Submit specification of BGP-signaled end-system IP/VPNs to IESG as PS
draft-ietf-l3vpn-end-system |
| Mar 2014 |
Submit specification of a multicast VPN MIB to IESG as PS
draft-ietf-l3vpn-l2l3-vpn-mcast-mib draft-ietf-l3vpn-mvpn-mib |
| Mar 2014 |
Submit specification for extranet support in multicast VPNs to IESG as PS
draft-ietf-l3vpn-mvpn-extranet |
| Mar 2014 |
Submit specification for encoding mLDP FECs in BGP multicast VPN routes to IESG as PS
draft-ietf-l3vpn-mvpn-mldp-nlri |
| Mar 2014 |
Submit specification for multicast VPN bidir P-tunnels to IESG as PS
draft-ietf-l3vpn-mvpn-bidir |
| Done |
Submit specification of mLDP in-band signaling in a VPN context to IESG as PS
draft-ietf-l3vpn-mldp-vrf-in-band-signaling |
| Nov 2013 |
Submit specification of the BGP ACCEPT_OWN Community Attribute to IESG as PS
draft-ietf-l3vpn-acceptown-community |
| Done |
Submit specification of virtual Hub-and-Spoke in BGP/MPLS VPNs to IESG as PS
draft-ietf-l3vpn-virtual-hub |
| Done | Submit specification for S-PMSI A-D route Wildcard selection to IESG as PS |
| Done | Submit specification for using Internal BGP as PE-CE protocol to IESG as PS |
| Done | Submit IPv6 MVPN infrastructure address encoding document to IESG for publication as PS |
| Done | Submit MVPNv6 using PIM & S-PMSIs specification to IESG as PS |
| Done | Submit specification of IPv4 multicast over BGP/MPLS VPNs for publication |
| Done | Submit specification of IPv6 over BGP/MPLS VPNs for publication |
| 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 using IPSEC for PE-PE encapsulation in BGP/MPLS VPNs to IESG for publication as PS (draft-ietf-ppvpn-ipsec-2547-03) |
| Done | Submit VR MIB to IESG for publication as PS (draft-ietf-ppvpn-vr-mib-04) |
| Done | Submit MPLS/BGP VPN MIB to IESG for publication as PS (draft-ietf-ppvpn-mpls-vpn-mib-05) |
| Done | Submit VPN MIB Textual Conventions to IESG for publication as PS (draft-ietf-ppvpn-tc-mib-02) |
| 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 BGP as an Auto-Discovery Mechanism for publication as PS (draft-ietf-ppvpn-bgpvpn-auto-05.txt) |
| 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 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 BGP/MPLS VPNs specification and AS to IESG for publication as PS (draft-ietf-ppvpn-rfc2547bis-03, draft-ietf-ppvpn-as2547-01) |
| Done | Submit VPN Security Analysis to IESG for publication as Info (draft-fang-ppvpn-security-framework-00) |
| Done | Submit L3 VPN Framework Document to IESG for publication as Info |
| Done | Submit Generic Requirements Document to IESG for publication as Info |
| Done | Submit L3 VPN Requirements Document to IESG for publication as Info |