Re: [OSPF] WG adoption---draft-chen-ospf-transition-to-ospfv3?

Manav Bhatia <manavbhatia@gmail.com> Tue, 26 August 2014 14:38 UTC

Return-Path: <manavbhatia@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0231A86EB for <ospf@ietfa.amsl.com>; Tue, 26 Aug 2014 07:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNeyFZeMFaZQ for <ospf@ietfa.amsl.com>; Tue, 26 Aug 2014 07:37:58 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 471311A86E9 for <ospf@ietf.org>; Tue, 26 Aug 2014 07:37:58 -0700 (PDT)
Received: by mail-oi0-f47.google.com with SMTP id x69so10771691oia.6 for <ospf@ietf.org>; Tue, 26 Aug 2014 07:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q+5lEb3xdFGAETcENwPl9etBjttFkr6v0GDYOPCldeg=; b=e6+eOfNE7a1KMDjcmjJIPZtyQan4UGbr3wzpqB6q9CsLROiAZv7lyra9pelKfs5e5r gTfjKEu6+4wJxJH3NwcoBOafkHh3In31MWLrHxSIOQ4ttk6HntD7gG6Rs9b9Ii9Hkyal WOsEw5RvpT96uDZeRYVdjFpgmfpQr6LJ9FHLZeAXc8pq1leagcQn5phq6aqwSzvU0vmE hmY+5xX7Trn5YHyJ67/sYHNWiIahcs2Pl2Yfy4F8skx7XGhMSyjMjJs2WpT6ApVbwXll JePwSy9x+S7L/i4ESycNr2nQUy+UAGWt9KD+/8AgKeouJMlOteKxZh5Lc7MPiYsOeuQB 3kbg==
MIME-Version: 1.0
X-Received: by 10.182.65.65 with SMTP id v1mr14597883obs.58.1409063877747; Tue, 26 Aug 2014 07:37:57 -0700 (PDT)
Received: by 10.76.154.100 with HTTP; Tue, 26 Aug 2014 07:37:57 -0700 (PDT)
In-Reply-To: <53FB88C5.4010008@cisco.com>
References: <BF6E0BD839774345977891C597F8B50C68D51D@eusaamb109.ericsson.se> <53FB88C5.4010008@cisco.com>
Date: Tue, 26 Aug 2014 20:07:57 +0530
Message-ID: <CAG1kdoivAoW7On6Ox3VG+xHKT+u+bp5CUCkto-6bhvfCDK1H9A@mail.gmail.com>
From: Manav Bhatia <manavbhatia@gmail.com>
To: Abhay Roy <akr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/yIZ_vuchx-_u29YwBmG7jHBQ3hI
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] WG adoption---draft-chen-ospf-transition-to-ospfv3?
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Aug 2014 14:38:00 -0000

Support!

Cheers, Manav

On Tue, Aug 26, 2014 at 12:34 AM, Abhay Roy <akr@cisco.com> wrote:
> We have strong support from all the authors to accept this work ;-)
>
> Can a few non-authors also chime in with their thoughts/support?
>
> Speaking as a WG member, I support this work because it also fixes the
> Virtual Link limitation we left unsupported in RFC5838 for IPv4 Unicast AF.
>
> Regards,
> -Abhay
>
>
> On 7/22/14, 5:53 PM, Ing-Wher Chen wrote:
>>
>> Hello,
>>
>> I'd like to ask if the working group would adopt and help improve and
>> refine
>> the following draft:
>>
>> <https://datatracker.ietf.org/doc/draft-chen-ospf-transition-to-ospfv3/>
>>
>> This document describes a mechanism to transport OSPfv3 over IPv4.
>> The mechanism allows devices to migrate to OSPFv3 first, which would help
>> with transition to IPv6 later.
>>
>> The latest -01 version addresses an earlier question by including
>> an IPv4-only use case in which deployed devices cannot communicate
>> in IPv6 but would benefit from using the mechanism proposed in this draft
>> to transition to OSPFv3 for now.  Until all devices can communicate using
>> IPv6,
>> consolidating to OSPFv3 can still reduce operational complexity and cost.
>>
>> Thanks,
>> Helen
>>
>> _______________________________________________
>> OSPF mailing list
>> OSPF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ospf
>
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf