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

-----Original Message----- From: MEURIC Julien RD-CORE-LAN Sent: Friday, June 13, 2008 10:34 AM To: zzx-adrian at olddog.co.uk; l1vpn at ietf.org; ospf at ietf.org Hi all. With respect to the v2-based solution, the v3 ID says: "The notable

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, DFrom ospf-bounces at ietf.org Fri Jun 13 05:32:11 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 8A3483A69CA; Fri, 13 Jun 2008 05:32:11 -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 B22A83A69C1 for <ospf at core3.amsl.com>; Fri, 13 Jun 2008 05:32:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.224

tests=[AWL=-0.226, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6] 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 WTrYTb4BI6Nt for <ospf at core3.amsl.com>; Fri, 13 Jun 2008 05:32:09 -0700 (PDT) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 540303A6883 for <ospf at ietf.org>; Fri, 13 Jun 2008 05:32:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 3C9D99E8B59 for <ospf at ietf.org>; Fri, 13 Jun 2008 05:32:41 -0700 (PDT) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13107-09 for <ospf at ietf.org>; Fri, 13 Jun 2008 05:32:41 -0700 (PDT) Received: from [IPv6???1] (login005.redback.com [155.53.12.64]) by prattle.redback.com (Postfix) with ESMTP id B785B9E8B58 for <ospf at ietf.org>; Fri, 13 Jun 2008 05:32:40 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v753.1) To: OSPF List <ospf at ietf.org> Message-Id: <6B379377-5E32-4A43-8AA5-D243BD43EF61 at redback.com> References: <7DBAFEC6A76F3E42817DF1EBE64CB02605A39163 at ftrdmel2> From: Acee Lindem <acee at redback.com> Date: Fri, 13 Jun 2008 08:32:39 -0400 X-Mailer: Apple Mail (2.753.1) X-Virus-Scanned: by amavisd-new at redback.com Subject: [OSPF] Fwd: [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: multipart/mixed; boundary="===============0839407282==" Sender: ospf-bounces at ietf.org Errors-To: ospf-bounces at ietf.org

Begin forwarded message:

-----Original Message-----
From: MEURIC Julien RD-CORE-LAN
Sent: Friday, June 13, 2008 10:34 AM
To: zzx-adrian at olddog.co.uk; l1vpn at ietf.org; ospf at 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 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