WG Action: RECHARTER: Layer 3 Virtual Private Networks (l3vpn)

[The IESG <[e-mail]>]

The charter of the Layer 3 Virtual Private Networks (l3vpn) working group 
in the Internet Area of the IETF has been updated. For additional information, 
please contact the Area Directors or the working group Chairs. 

Layer 3 Virtual Private Networks (l3vpn)
========================================

Current Status: Active Working Group

Chair(s):
Rick Wilder <[e-mail]>
Ross Callon <[e-mail]>
Ronald Bonica <[e-mail]>

Internet Area Director(s):
Thomas Narten <[e-mail]>
Margaret Wasserman <[e-mail]>

Internet Area Advisor:
Thomas Narten <[e-mail]>

Technical Advisor(s):
Alex Zinin <[e-mail]>

Mailing Lists:
General Discussion: [e-mail]
To Subscribe: https://www1.ietf.org/mailman/listinfo/l3vpn
Archive: https://www1.ietf.org/mail-archive/working-groups/l3vpn/current/maillist.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)  
Aug 04 Submit VPN MIB Textual Conventions to IESG for publication as PS 
	(draft-ietf-ppvpn-tc-mib-02)  
Aug 04 Submit MPLS/BGP VPN MIB to IESG for publication as PS 
	(draft-ietf-ppvpn-mpls-vpn-mib-05)  
Aug 04 Submit VR MIB to IESG for publication as PS (draft-ietf-ppvpn-vr-mib-04)  
Aug 04 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)  
Aug 04 Submit specification of OSPF as the PE/CE Protocol in BGP/MPLS VPNs for 
	publication (draft-rosen-vpns-ospf-bgp-mpls-06.txt)  
Dec 04 Submit specification of CE Route Authentication to IESG for publication 
	as PS (draft-ietf-ppvpn-l3vpn-auth-03)  
Dec 04 Submit specification of IPv6 over BGP/MPLS VPNs for publication  
Dec 04 Submit specification of IPv4 multicast over BGP/MPLS VPNs for publication  



_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ietf-announce