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

Ing-Wher Chen <ing-wher.chen@ericsson.com> Wed, 23 July 2014 00:53 UTC

Return-Path: <ing-wher.chen@ericsson.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 5E5C41A02E1 for <ospf@ietfa.amsl.com>; Tue, 22 Jul 2014 17:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 dQ50TTPcMFO1 for <ospf@ietfa.amsl.com>; Tue, 22 Jul 2014 17:53:34 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6973F1A0109 for <ospf@ietf.org>; Tue, 22 Jul 2014 17:53:32 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-dc-53ceb228296e
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E7.BF.25146.922BEC35; Tue, 22 Jul 2014 20:49:13 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Tue, 22 Jul 2014 20:53:25 -0400
From: Ing-Wher Chen <ing-wher.chen@ericsson.com>
To: "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: WG adoption---draft-chen-ospf-transition-to-ospfv3?
Thread-Index: Ac+mD1WqrJdjlPOzRKKgH+V1PVvBIw==
Date: Wed, 23 Jul 2014 00:53:25 +0000
Message-ID: <BF6E0BD839774345977891C597F8B50C68D51D@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUyuXRPgq7mpnPBBlcfCFi03LvH7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJ7dF9gKfrBWtH9bwdbA+IGli5GTQ0LAROLwgp1sELaYxIV7 64FsLg4hgaOMEhdWfGeHcJYzSszddRCsik3AQGLDxy1MILaIgLLElr39YHFhARuJzZsOsUPE HSXen1sFZetJnPv/gxnEZhFQldj9cBNQLwcHr4C3RMN8OZAwI9Di76fWgI1kFhCXuPVkPhPE QQISS/acZ4awRSVePv7HCmErSUxaeo4Vol5HYsHuT2wQtrbEsoWvwep5BQQlTs58wjKBUXgW krGzkLTMQtIyC0nLAkaWVYwcpcWpZbnpRoabGIGBfEyCzXEH44JPlocYBTgYlXh4FczOBQux JpYVV+YeYpTmYFES59WsnhcsJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgXH6D9HkI+0MxyMN XBryj/lXC8Q8FedWm3PYm6vIdUrrB+lsgQfha3+Uz2dQm8n/3i8hx//ESfsHGYfkHq0TvjGN 9VI3X36MwiLLTW5umiw/5vzjSv9fvOnIjG3FefO3vfd0YWebczW5nffvFWH2x037TQSa7x+f PU3s9qyZep5/PndmKhVPaFZiKc5INNRiLipOBAC97+ksRQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/LybTyHPTYdeAey_OaQ0u4Ig6ALs
Subject: [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: Wed, 23 Jul 2014 00:53:35 -0000

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