PPVPN (or ...) draft-martini-l2circuit-trans-mpls-05.txt

[Eric Rosen <erosen@cisco.com>]

NAME OF I-D:

http://www.ietf.org/internet-drafts/draft-martini-l2circuit-trans-mpls-05.txt

SUMMARY

This  document specifies  edge-node  procedures for  transporting frames  of
various  layer  2  protocols  across  an IP  backbone.   It  also  specifies
extensions to the MPLS signaling protocol LDP which enable such frames to be
carried across the network in MPLS label switched paths. 

RELATED DOCUMENTS

http://www.ietf.org/internet-drafts/draft-rosen-ppvpn-l2vpn-00.txt
http://www.ietf.org/internet-drafts/draft-martini-l2circuit-encap-mpls-01.txt

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

This draft may need to be split up into several drafts in order to match the
new organization of the sub-ip area and the transport area.  

It is  required by the L2VPN  work in PPVPN.   Part of it may  be considered
"common  control protocol", but  this part  may also  be considered  to fall
under the charter of the PWE3 WG in the transport area. 

Part of the draft defines extensions to LDP for the particular case in which
MPLS is used in the backbone.  Arguably  this should be taken up by the MPLS
WG at the request  of the CCAMP group and/or the PWE3  group.  While it does
not appear to be  in the charter of the MPLS group to  take up this work, it
does appear to be in the charter of these other groups to ask the MPLS group
to take up this work, so go figure.

WHY IS IT TARGETED AT THIS WG

I have targeted this  summary at the PPVPN WG because the  work is needed to
support one of the work items called  out in the PPVPN WG charter (L2 VPNs),
and it is not  clear which WG or WGs should actually  be responsible for the
technical content of the draft. 

It may make  the most sense to  have this work split among  the PPVPN, MPLS,
and PWE3 WGs.  

JUSTIFICATION

One or another  of the above-mentioned WGs should consider  this draft as it
is needed to support one of the work items in the PPVPN WG charter.