[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PPVPN draft-rosen-ppvpn-l2vpn-00.txt
- To: idsummary@subip.ietf.org
- Subject: PPVPN draft-rosen-ppvpn-l2vpn-00.txt
- From: Eric Rosen <erosen@cisco.com>
- Date: Thu, 10 May 2001 11:28:42 -0400
- Delivery-date: Thu, 10 May 2001 08:29:23 -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-rosen-ppvpn-l2vpn-00.txt
SUMMARY
Service Providers may offer a "Layer 2 VPN Service" over an IP backbone by
provisioning point-to-point "virtual circuits" that run through IP
tunnels. This document discusses the signaling, encapsulation, and
configuration issues that arise. Its purpose is to provide an architecture
which allows different kinds of point-to- point virtual circuits to be
provided through different kinds of IP tunnels.
RELATED DOCUMENTS
http://www.ietf.org/internet-drafts/draft-ouldbrahim-bgpvpn-auto-01.txt
draft-martini-l2circuit-encap-mpls-01.txt
draft-martini-l2circuit-trans-mpls-05.txt
draft-kompella-mpls-l2vpn-02.txt
draft-rosen-rfc2547bis-03.txt
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
This work fits squarely in the PPVPN box.
WHY IS IT TARGETED AT THIS WG
It addresses the following work item from the PPVPN WG charter:
"The working group is expected to consider at least three
specific approaches including ... port-based VPNs (i.e.,
where the SP provides a Layer 2 interface, such as Frame
Relay or ATM, to the VPN customer, while using IP-based
mechanisms in the provider infrastructure"
JUSTIFICATION
The WG should consider this document as it specifically addresses one of the
work items called out in the charter.