[L1vpn] Draft liaison to SG13 from L1VPN

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 23 November 2005 15:09 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EewFW-0007Uu-92; Wed, 23 Nov 2005 10:09:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EewFU-0007UF-G0 for l1vpn@megatron.ietf.org; Wed, 23 Nov 2005 10:09:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13041 for <l1vpn@ietf.org>; Wed, 23 Nov 2005 10:08:48 -0500 (EST)
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EewYM-00079c-Lm for l1vpn@ietf.org; Wed, 23 Nov 2005 10:28:59 -0500
Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by ranger.systems.pipex.net (Postfix) with ESMTP id 0A67DE000625; Wed, 23 Nov 2005 15:09:02 +0000 (GMT)
Received: from Puppy ([217.158.132.123] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 23 Nov 2005 14:57:38 +0000
Message-ID: <051301c5f03e$b7c11490$fb849ed9@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: l1vpn@ietf.org
Date: Wed, 23 Nov 2005 14:57:16 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 23 Nov 2005 14:57:40.0073 (UTC) FILETIME=[3FE7ED90:01C5F03E]
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit
Cc: Bill Fenner <fenner@research.att.com>, Scott Bradner <sob@harvard.edu>
Subject: [L1vpn] Draft liaison to SG13 from L1VPN
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Sender: l1vpn-bounces@lists.ietf.org
Errors-To: l1vpn-bounces@lists.ietf.org

Hi,

In Vancouver we reminded ourselves that we should send ITU-T SG13 a
liaison to let them know how we are progressing.

Below is a draft. please comment by the 30th of November.

Thanks,
Adrian
 ========
From: IETF L1VPN Working Group
To: ITU-T Study Group 13
For: Information

Subject: Status of Layer One VPN Work in the IETF

The L1VPN Working Group would like to take this opportunity to inform
ITU-T Study Group 13 of its progress on the development of protocol
solutions for Layer One VPNs.

The L1VPN Working Group was chartered in the summer of this year. You can
see the details of the scope of work for the working group at
http://www.ietf.org/html.charters/l1vpn-charter.html.

The working group has so far produced two documents:

http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-00.txt
presents a framework for L1VPNs and draws much of its material from
Recommendations Y.1312 and Y.1313. The purpose of this framework is to aid
in developing and standardizing protocols and mechanisms to support
interoperable L1VPNs. The document examines motivations for L1VPNs, high
level (service level) requirements, and outlines some of the architectural
models that might be used to build L1VPNs.

http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-applicability-00.txt
provides an applicability analysis on the use of Generalized Multiprotocol
Label Switching (GMPLS) protocols and mechanisms to satisfy the
requirements of Layer 1 Virtual Private Networks (L1VPNs). In addition,
this document identifies areas where additional protocol extensions or
procedures are needed to satisfy the requirements of L1VPNs, and provides
guidelines for potential extensions. The intention is that, as new
protocol extensions are developed to meet the requirements identified here
and in the framework document, this document will convert to being a
simple applicability statement.

The working group believes that these two documents are largely stable,
and is now working to develop protocol solutions for the "Basic Mode"
L1VPN. This mode of operation involves only signaling protocol exchanges
(i.e. no routing) between CE and PE in the network.

Two Internet-Drafts currently exist in support of the protocol extensions
needed for the Basic Mode as identified in the applicability draft:

http://www.ietf.org/internet-drafts/draft-fedyk-l1vpn-basic-mode-00.txt
describes an operational model using either provisioning or a VPN
auto-discovery mechanism and defines signaling extensions for the L1VPN
Basic Mode.

http://www.ietf.org/internet-drafts/draft-ouldbrahim-l1vpn-bgp-auto-discovery-00.txt
defines a BGP-based auto-discovery mechanism for Layer One VPNs that
allows the provider network devices to dynamically discover the set of PEs
having ports attached to CEs member of the same VPN.

The working group is likely to adopt work items based on these
Internet-Drafts in the near future.

A further work item to provide an OSPF-based auto-discovery mechanism is
being developed but is not available at this time.

The L1VPN Working Group would like to encourage the involvement of all
interested parties through the open mailing list. Subscription details can
be found at the charter page
(http://www.ietf.org/html.charters/l1vpn-charter.html).

The review and feedback of Study Group 13 on any of this work would also
be most welcome.

 Regards,
Tomonori Takeda
Hamid Ould-Brahim
Adrian Farrel
(L1VPN Working Group co-chairs)


_______________________________________________
L1vpn mailing list
L1vpn@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/l1vpn