[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OSPF] [L1vpn] Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
Hi Adrian.
In that case, if nothing precludes future reconsideration, then the answer is obvious... Anyway, I rely on the chairs (and maybe ADs) to take the appropriate decision about this minor issue.
Cheers,
Julien
-----Original Message-----
From: Adrian Farrel [mailto:adrian at olddog.co.uk]
Hi Julien,
My thinking on Experimental was simply that we have absolutely no
implementation experience of this work. Neither the author nor the WG chairs
have experience of implementing OSPFv3, and as far as we know, no-one has
any plans to implement L1VPN autodiscovery with OSPFv3.
I think that the way things go is that once someone has implemented (or
preferably when we have multiple implementations) we can come back, make any
changes to the work that are necessary, and republish as standards track.
Cheers,
Adrian
----- Original Message -----
From: <julien.meuric at orange-ftgroup.com>
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 implFrom ospf-bounces at ietf.org Mon Jun 16 05:08:09 2008
Return-Path: <ospf-bounces at ietf.org>
X-Original-To: ospf-archive at optimus.ietf.org
Delivered-To: ietfarch-ospf-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 0151A3A6AB0;
Mon, 16 Jun 2008 05:08:09 -0700 (PDT)
X-Original-To: ospf at core3.amsl.com
Delivered-To: ospf at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 348EE3A677C;
Mon, 16 Jun 2008 05:08:08 -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 WiZt0ICPAa6K; Mon, 16 Jun 2008 05:08:07 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
[195.101.245.16])
by core3.amsl.com (Postfix) with ESMTP id 806233A690A;
Mon, 16 Jun 2008 05:08:04 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 16 Jun 2008 14:08:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 16 Jun 2008 14:08:43 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02605A708DE at ftrdmel2>
In-Reply-To: <017301c8cee1$293790d0$d106a8c0 at your029b8cecfe>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [L1vpn]
Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
Thread-Index: AcjO4TB9+JxJhDZRSv2AOjAbaaMQTgAxtafg
References: <20080611190002.04D7A3A6861 at core3.amsl.com>
<00f001c8cc25$ca146690$d106a8c0 at your029b8cecfe>
<7DBAFEC6A76F3E42817DF1EBE64CB02605A39144 at ftrdmel2>
<017301c8cee1$293790d0$d106a8c0 at your029b8cecfe>
From: <julien.meuric at orange-ftgroup.com>
To: <adrian at olddog.co.uk>,
<l1vpn at ietf.org>,
<ospf at ietf.org>
X-OriginalArrivalTime: 16 Jun 2008 12:08:44.0507 (UTC)
FILETIME=[B9494AB0:01C8CFA9]
Subject: Re: [OSPF] [L1vpn]
Reviewrequested:draft-ietf-l1vpn-ospfv3-auto-discovery-00.txt
X-BeenThere: ospf at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
<mailto:ospf-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf at ietf.org>
List-Help: <mailto:ospf-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
<mailto:ospf-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces at ietf.org
Errors-To: ospf-bounces at ietf.org
Hi Adrian.
In that case, if nothing precludes future reconsideration, then the answer is obvious... Anyway, I rely on the chairs (and maybe ADs) to take the appropriate decision about this minor issue.
Cheers,
Julien
-----Original Message-----
From: Adrian Farrel [mailto:adrian at olddog.co.uk]
Hi Julien,
My thinking on Experimental was simply that we have absolutely no
implementation experience of this work. Neither the author nor the WG chairs
have experience of implementing OSPFv3, and as far as we know, no-one has
any plans to implement L1VPN autodiscovery with OSPFv3.
I think that the way things go is that once someone has implemented (or
preferably when we have multiple implementations) we can come back, make any
changes to the work that are necessary, and republish as standards track.
Cheers,
Adrian
----- Original Message -----
From: <julien.meuric at orange-ftgroup.com>
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 emented 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 at ietf.org [mailto:l1vpn-bounces at 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 at ietf.org
https://www.ietf.org/mailman/listinfo/l1vpn
_______________________________________________
OSPF mailing list
OSPF at ietf.org
https://www.ietf.org/mailman/listinfo/ospf
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 at ietf.org [mailto:l1vpn-bounces at 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 at ietf.org
https://www.ietf.org/mailman/listinfo/l1vpn
_______________________________________________
OSPF mailing list
OSPF at ietf.org
https://www.ietf.org/mailman/listinfo/ospf