[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PPVPN draft-martini-l2circuit-encap-mpls-01.txt
- To: idsummary@subip.ietf.org
- Subject: PPVPN draft-martini-l2circuit-encap-mpls-01.txt
- From: Eric Rosen <erosen@cisco.com>
- Date: Thu, 17 May 2001 10:43:44 -0400
- Delivery-date: Thu, 17 May 2001 07:44:18 -0700
- Envelope-to: idsummary-data@psg.com
- Reply-to: erosen@cisco.com
- User-Agent: EMH/1.10.0 WEMI/1.13.2 (Mochimune) FLIM/1.12.1(Nishinokyō) Emacs/20.6 (sparc-sun-solaris2.5.1)MULE/4.0 (HANANOEN)
NAME OF I-D:
http://www.ietf.org/internet-drafts/draft-martini-l2circuit-encap-mpls-01.txt
SUMMARY
This document specifies the encapsulation for transporting the frames of
various data link layers through tunnels across an IP backbone, when using
the procedures described in draft-martini-l2circuit-trans-mpls. An
encapsulation which is independent of the tunneling methodology is defined,
and the way in which this is further encapsulated inside an MPLS frame is
defined.
RELATED DOCUMENTS
http://www.ietf.org/internet-drafts/draft-rosen-ppvpn-l2vpn-00.txt
http://www.ietf.org/internet-drafts/draft-martini-l2circuit-trans-mpls-05.txt
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
This is required by the L2VPN work of the PPVPN WG. However, it is not
clear where a specification of encapsulation formats fits in the picture, or
even whether this is not in the province of sub-ip at all, but rather
entirely in the province of the PWE3 WG of the transport area.
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.
This id summary was prepared in order to maximize the change that the draft
actually gets assigned somewhere.
JUSTIFICATION
This draft as it is needed to support one of the work items in the PPVPN WG
charter.