Layer 1 Virtual Private Networks (l1vpn) Internet Drafts
| Layer 1 VPN Basic Mode | |||||||||||||||||
|
This document describes the Basic Mode of Layer 1 VPNs (L1VPN BM). L1VPN Basic mode is a port-based VPN. In L1VPN Basic Mode (BM), the basic unit of service is a Label Switched Path (LSP) between a pair of customer ports within a given VPN port-topology. This document defines the operational model using either provisioning or a VPN auto-discovery mechanism, and the signaling extensions for the L1VPN BM. | ||||||||||||||||
| OSPF Based Layer 1 VPN Auto-Discovery | |||||||||||||||||
|
This document defines an Open Shortest Path First (OSPF) based Layer-1 Virtual Private Network (L1VPN) auto-discovery mechanism. This mechanism enables provider edge (PE) devices using OSPF to dynamically learn about existence of each other, and attributes of configured customer edge (CE) links and their associations with L1VPNs. This document builds on L1VPN framework and requirements, and provides a L1VPN basic mode auto-discovery mechanism. | ||||||||||||||||
| Applicability Statement for Layer 1 Virtual Private Networks (L1VPNs) Basic Mode | |||||||||||||||||
|
This document provides an applicability statement on the use of Generalized Multiprotocol Label Switching (GMPLS) protocols and mechanisms to support Basic Mode Layer 1 Virtual Private Networks (L1VPNs). L1VPNs provide customer services and connectivity at layer 1 over layer 1 networks. The operation of L1VPNs is divided into the Basic Mode and the Enhanced Mode where the Basic Mode of operation does not feature any exchange of routing information between the layer 1 network and the customer domain. This document examines how GMPLS protocols can be used to satisfy the requirements of a Basic Mode L1VPN. T.Takeda, et al. Expires October 2008 [page 1] draft-ietf-l1vpn-applicability-basic-mode-05.txt April 2008 | ||||||||||||||||
| OSPFv3 Based Layer 1 VPN Auto-Discovery | |||||||||||||||||
|
This document defines an Open Shortest Path First (OSPF) version 3 based Layer-1 Virtual Private Network (L1VPN) auto-discovery mechanism. This document parallels the existing OSPF version 2 L1VPN auto-discovery mechanism. The notable functional difference is the support of IPv6. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Layer 1 Virtual Private Networks (l1vpn)
Last Modified: 2008-04-14
Additional information is available at tools.ietf.org/wg/l1vpn
Chair(s):
Routing Area Director(s):
Routing Area Advisor:
Mailing Lists:
General Discussion: l1vpn@ietf.orgTo Subscribe: https://www1.ietf.org/mailman/listinfo/l1vpn
Archive: http://www.ietf.org/mail-archive/web/l1vpn/index.html
Description of Working Group:
The L1VPN Working Group's task is to specify mechanisms necessary forproviding layer-1 VPN services (establishment of layer-1 connections
between CE devices) over a GMPLS-enabled transport service-provider
network.
The following two service models will be addressed:
1. Basic mode: the CE-PE interface's functional repertoire is limited
to
path setup signalling only. Provider's network is not involved in
distribution of customer network's routing information.
2. Enhanced mode: the CE-PE interface provides the signaling
capabilities as in the Basic mode, plus permits limited exchange of
information between the control planes of the provider and the customer
to help such functions as discovery of reachability information in
remote sites, or parameters of the part of the provider's network
dedicated to the customer.
The WG will work on the following items:
1. Framework document defining the reference network model, L1VPN
service model, fundamental assumptions, and terminology.
2. Specification of the L1VPN signaling functionality between the
customer and the provider network to support the basic mode.
3. Specification of the L1VPN signaling and routing functionality
within
the provider network to support the basic mode.
4. OAM features and MIB modules and/or extensions required for the
basic
mode.
5. Specification of the L1VPN signaling and routing functionality
between the customer and the provider network to support the extended
mode.
6. Specification of the L1VPN signaling and routing functionality
within
the provider network to support the extended mode.
7. OAM features and MIB modules and/or extensions required for the
extended mode.
8. Applicability guidelines to compare the basic and extended modes.
At this point the WG will address the single-AS scenario only. The
multi-AS/provider scenario may be considered in future.
Protocol extensions required for L1VPN will be done in cooperation with
MPLS, CCAMP, OSPF, IS-IS, IDR, L3VPN, and other WGs where necessary.
L1VPN WG shall also cooperate with ITU-T SG13 through the established
IETF process, and use documents Y.1312 and Y.1313 (describing L1VPN
requirements and network architectures) as input to its design process.
The documents will be available at the IETF liaison web-site.
Goals and Milestones:
| Done | Submit first Internet Draft of L1VPN framework | |
| Done | Submit first Internet Drafts of basic mode specifications | |
| Dec 2005 | Submit first Internet Drafts of MIB modules for basic mode | |
| Done | Submit basic mode specifications to IESG for publication as Proposed Standard | |
| Jun 2006 | Submit first Internet Drafts of enhanced mode specifications | |
| Aug 2006 | Submit MIB modules for basic mode to IESG for publication as Proposed Standard | |
| Dec 2006 | Submit enhanced mode specifications to IESG for publication as Proposed Standard | |
| Done | Submit L1VPN framework to IESG for publication as Informational RFC | |
| Aug 2007 | Submit MIB modules for enhanced mode to IESG for publication as Proposed Standard | |
| Dec 2007 | Recharter or disband |
Internet-Drafts:
Layer 1 VPN Basic Mode (60294 bytes)OSPF Based Layer 1 VPN Auto-Discovery (24669 bytes)
Applicability Statement for Layer 1 Virtual Private Networks (L1VPNs) Basic Mode (44691 bytes)
OSPFv3 Based Layer 1 VPN Auto-Discovery (21763 bytes)
Request For Comments:
Framework and Requirements for Layer 1 Virtual Private Networks (RFC 4847) (85807 bytes)BGP-based Auto-Discovery for Layer-1 VPNs (RFC 5195) (21480 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
