Re: [L1vpn] Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt

<julien.meuric@orange-ftgroup.com> Fri, 13 June 2008 08:34 UTC

Return-Path: <l1vpn-bounces@ietf.org>
X-Original-To: l1vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l1vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 865203A6B42; Fri, 13 Jun 2008 01:34:03 -0700 (PDT)
X-Original-To: l1vpn@core3.amsl.com
Delivered-To: l1vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 118EF28C14E; Fri, 13 Jun 2008 01:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lD8l0ZDSKkvA; Fri, 13 Jun 2008 01:34:01 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 8FEF33A6B41; Fri, 13 Jun 2008 01:34:00 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jun 2008 10:34:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 13 Jun 2008 10:34:29 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605A39144@ftrdmel2>
In-Reply-To: <00f001c8cc25$ca146690$d106a8c0@your029b8cecfe>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [L1vpn] Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
Thread-Index: AcjMJfYp6YG5ljmvQU6YosiN0zkMjQBCA/PA
References: <20080611190002.04D7A3A6861@core3.amsl.com> <00f001c8cc25$ca146690$d106a8c0@your029b8cecfe>
From: julien.meuric@orange-ftgroup.com
To: adrian@olddog.co.uk, l1vpn@ietf.org, ospf@ietf.org
X-OriginalArrivalTime: 13 Jun 2008 08:34:30.0057 (UTC) FILETIME=[4C32A190:01C8CD30]
Subject: Re: [L1vpn] Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
X-BeenThere: l1vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@ietf.org>
List-Help: <mailto:l1vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: l1vpn-bounces@ietf.org
Errors-To: l1vpn-bounces@ietf.org

Hi all.

With respect to the v2-based solution, the v3 ID says: "The notable
functional difference is the support of IPv6." If it's actually the only
difference (I haven't deeply reviewed the new ID yet), is there a point
to make the draft Experimental? It is indeed likely to be implemented in
a longer term than the former one, but it is mainly a matter of schedule
towards IPv6. As the feature itself should look like the OSPFv2-based
solution, I'm rather in favor of "Standards Track", but maybe you have
some other reasons in mind (speed up publishing process?).

Regards,

Julien


-----Original Message-----
From: l1vpn-bounces@ietf.org [mailto:l1vpn-bounces@ietf.org] On Behalf
Of Adrian Farrel

L1VPN and OSPF working groups,

During the IESG review of draft-ietf-l1vpn-ospf-auto-discovery-06.txt,
the 
IESG asked the L1VPN working group to consider how to use OSPFv3 to
provide 
IPv6-compliant auto-discovery for layer one VPNs. They agreed to let us
do 
this work in a separate draft.

Lou Berger has kindly turned the handle and this is the result.

We intend to move forward toward WG last call with this work quite
quickly, 
and so we would appreciate you review, comments, and feedback.

To start the discussion, please comment on whether you believe this
draft 
should be Standards Track (as currently marked) or Experimental? It
seems 
that there are no immediate plans for any implementation that would
verify 
that the document is correct or stable.

Many thanks,
Adrian

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
> This draft is a work item of the Layer 1 Virtual Private Networks
Working 
> Group of the IETF.
>
> Title           : OSPFv3 Based Layer 1 VPN Auto-Discovery
> Author(s)       : L. Berger
> Filename        : draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
> Pages           : 11
> Date            : 2008-06-11
>
> 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.
>
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospfv3-auto-discove
ry-00.txt


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