2.3.6 Layer 2 Virtual Private Networks (l2vpn)

Last Modified: 2003-07-09

Chair(s):
Rick Wilder <rick@rhwilder.net>
Vach Kompella <vkompella@timetra.com>
Loa Andersson <loa@pi.se>
Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Margaret Wasserman <mrw@windriver.com>
Internet Area Advisor:
Thomas Narten <narten@us.ibm.com>
Technical Advisor(s):
Russell Housley <housley@vigilsec.com>
Alex Zinin <zinin@psg.com>
Mailing Lists:
General Discussion: l2vpn@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/l2vpn
Archive: https://www1.ietf.org/mail-archive/working-groups/l2vpn/current/maillist.html
Description of Working Group:
Alex Zinin is the routing advisor.
Russ Housley is the security advisor.

This working group is responsible for defining and specifying a
limited number of solutions for supporting provider-provisioned
layer-2 virtual private networks (L2VPNs).

The WG is responsible for standardization of the following solutions:

1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
  across an IP and an MPLS-enabled IP network, allowing standard
  Ethernet devices communicate with each other as if they were
  connected to a common LAN segment.
 
2. Virtual Private Wire Service (VPWS)--L2 service that provides L2
  point-to-point connectivity (e.g. Frame Relay DLCI, ATM VPI/VCI,
  point-to-point Ethernet) across an IP and an MPLS-enabled IP network.

3. IP-only L2 VPNs--L2 service across an IP and an MPLS-enabled
  IP network, allowing standard IP devices to communicate with each
  other as if they were connected to a common LAN segment or a point-
  to-point circuit.

The WG will address intra-AS scenarios only at this point (other
scenarios will be considered for inclusion in the updated charter when
the current one is completed.)
     
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.
As a specific example, this WG will not define new encapsulation
mechanism, but will use those defined in the PWE3 WG.
L2VPN WG will review proposed protocol extensions for L2VPNs before
they are recommended to appropriate protocol-specific WGs.

The WG will work on the following items. Adding new work items will
require rechartering.

1. Discovery of PEs participating in L2 service, and topology of
  required connectivity

2. Signaling of l2vpn related information for the purpose of
  setup and maintenance of l2vpn circuits. As much as possible
  PWE3 signaling procedures should be used

3. Solution documents (providing the framework for a specific
  solution, should include info on how discovery, signaling,
  and encaps work together, include security, AS as a separate
  document)

4. MIBs
     
5. L2VPN-specific OAM extensions--extensions to existing OAM
  solutions for VPLS, VPWS, and IP-only L2VPNs.

Where necessary, the WG will coordinate its activities with IEEE 802.1
Goals and Milestones:
Jul 03  Submit L2 requirements to IESG for publication as Informational RFC
Jul 03  Submit L2 framework to IESG for publication as Informational RFC
Jul 03  Identify VPLS and VPWS solutions for the WG
Aug 03  Submit an I-D describing MIB for VPLS
Aug 03  Submit an I-D describing MIB for VPWS
Aug 03  Submit an I-D on OAM for VPLS
Aug 03  Submit an I-D on OAM for VPWS
Dec 03  Submit VPLS solution documents to IESG
Dec 03  Submit VPWS solution documents to IESG
Jan 04  Submit IP-only L2VPN solution documents to IESG
Feb 04  Submit MIB for VPLS to IESG
Feb 04  Submit MIB for VPWS to IESG
Mar 04  Submit OAM for VPWS to IESG
Mar 04  Submit OAM for VPLS to IESG
Apr 04  Submit OAM for IP L2VPN to IESG
Internet-Drafts:
  • - draft-ietf-l2vpn-vpls-requirements-00.txt
  • - draft-ietf-l2vpn-l2-framework-00.txt
  • - draft-ietf-l2vpn-requirements-00.txt
  • - draft-ietf-l2vpn-vpls-bgp-00.txt
  • - draft-ietf-l2vpn-vpls-ldp-00.txt
  • No Request For Comments

    Current Meeting Report

    None received.

    Slides

    None received.