PPVPN/MPLS draft-rosen-ppvpn-l2-signaling-00.txt

[Eric Rosen <erosen@cisco.com>]

NAME OF I-D:

http://www.ietf.org/internet-drafts/draft-rosen-ppvpn-l2-signaling-00.txt

SUMMARY

This document shows how to extend the techniques of draft-martini-l2circuit-
trans-mpls-07.txt   to   support   signaling   not   only   for   individual
point-to-point circuits, but also for  transparent LAN L2VPNs and other full
mesh  L2VPNs.  It  also specifies  the information  which would  need  to be
obtained via an auto-discovery procedure in order for the signaling to begin.


RELATED DOCUMENTS

http://www.ietf.org/internet-drafts/draft-martini-l2circuit-trans-mpls-07.txt
http://www.ietf.org/internet-drafts/draft-lasserre-tls-mpls-00.txt
http://www.ietf.org/internet-drafts/draft-vkompella-ppvpn-vpsn-mpls-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-ppvpn-l2vpn-00.txt

WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK

Parts of  it fit into the  MPLS area (the  LDP extensions), parts of  it fit
into the PPVPN area (the requirements that justify the LDP extensions).

WHY IS IT TARGETED AT THIS WG

Insofar as this draft specifies the information which needs to be carried in
a signaling  protocol, and  the information which  needs to be  provided via
auto-discovery, it  is specifying requirements on the  signaling for L2VPNs.
This falls in the area of the PPVPN WG. 

Insofar as this  draft specifies extensions to LDP that  are needed to carry
out the signaling, it falls in the area of the MPLS WG.

JUSTIFICATION

If the PPVPN is going to specify provider-based L2VPN procedures, then it is
necessary for there  to be a specification of  the signaling requirements to
support those procedures, and of the actual signaling protocol used.