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

Karsten Thomann <karsten_thomann@linfre.de> Thu, 28 August 2014 06:52 UTC

Return-Path: <karsten_thomann@linfre.de>
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 AD7C31A047B for <ospf@ietfa.amsl.com>; Wed, 27 Aug 2014 23:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.22
X-Spam-Level:
X-Spam-Status: No, score=-2.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-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 ybKhTQeASK1r for <ospf@ietfa.amsl.com>; Wed, 27 Aug 2014 23:52:48 -0700 (PDT)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0CFE1A040E for <ospf@ietf.org>; Wed, 27 Aug 2014 23:52:47 -0700 (PDT)
Received: from [10.43.66.140] (194.163.249.24) by linfreserv.linfre (Axigen) with (AES256-SHA encrypted) ESMTPSA id 217998; Thu, 28 Aug 2014 08:52:37 +0200
Message-ID: <53FED1B4.8020202@linfre.de>
Date: Thu, 28 Aug 2014 08:52:36 +0200
From: Karsten Thomann <karsten_thomann@linfre.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ospf@ietf.org
References: <CFFEF972.15D3%acee@cisco.com> <784545c5caf4452cb2bdfc70fff2418d@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <784545c5caf4452cb2bdfc70fff2418d@BY2PR05MB079.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 5
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/WOWlOG1XP96P2cJXMbZCKsV1ZK8
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: Thu, 28 Aug 2014 06:52:49 -0000

Support

It eases the transition to ipv6 and avoids running two protocols without 
yet enabled but planned IPv6.

Am 25.08.2014 23:57, schrieb Jeffrey (Zhaohui) Zhang:
> I read the draft and support its adoption.
>
> Jeffrey
>
>> -----Original Message-----
>> From: Acee Lindem (acee) [mailto:acee@cisco.com]
>> Sent: Wednesday, July 30, 2014 4:39 PM
>> To: Ing-Wher Chen; ospf@ietf.org
>> Subject: Re: [OSPF] WG adoption---draft-chen-ospf-transition-to-ospfv3?
>>
>> Hi Helen,
>> As an author, I would certainly support this work. I think it is clearly
>> in the OSPF WG¹s best interest to facilitate migration to a single
>> version. When that happens will be dependent on numerous factors
>> including
>> requirements, deployments, and how well we facilitate it.
>> Thanks,
>> Acee
>>
>> On 7/22/14, 8:53 PM, "Ing-Wher Chen" <ing-wher.chen@ericsson.com> 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