Re: [OSPF] FW: New Version Notification for draft-chen-ospf-transition-to-ospfv3-01.txt

Anton Smirnov <asmirnov@cisco.com> Tue, 08 July 2014 11:11 UTC

Return-Path: <asmirnov@cisco.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 61B031B27E5 for <ospf@ietfa.amsl.com>; Tue, 8 Jul 2014 04:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 vEkJpEyqCxg1 for <ospf@ietfa.amsl.com>; Tue, 8 Jul 2014 04:11:25 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE6651B27F7 for <ospf@ietf.org>; Tue, 8 Jul 2014 04:11:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2618; q=dns/txt; s=iport; t=1404817877; x=1406027477; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=ZyCBr0N5tPwZkNZ06ZaU6Z9H55lclNVfVkyU8ONlH/Q=; b=SSqqn9NYEA1Mm2GKr0iWrcn70QlfQf/oWKImnyQ2SsEVDRzvqYl139jM 5wXW5ezMcG70iG23IbLwaukLgpoc8Pntpv2bJ7cZL0Em4xvnp6Ebi7I62 vEHBU/K8pUQI0GuQATM52m7rRO+a+da601PPWmd/Rh2MsQRSq8I7xBAMC w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwHAJXRu1OtJssW/2dsb2JhbABZg2BTvnqHRAGBK3WEAwEBAQQBAQE1NgkBDQQLEQQBAQEJFggHCQMCAQIBFR8IAQgGAQwGAgEBBYg5CAXJEBePKQaEPQEEllyEGoFIkkSCAYFEOy8
X-IronPort-AV: E=Sophos;i="5.01,625,1400025600"; d="scan'208";a="106549376"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 08 Jul 2014 11:11:09 +0000
Received: from as-lnx.cisco.com (ams-asmirnov-8714.cisco.com [10.55.140.85]) (authenticated bits=0) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s68BB94P001635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 8 Jul 2014 11:11:09 GMT
Message-ID: <53BBD1CD.9070406@cisco.com>
Date: Tue, 08 Jul 2014 13:11:09 +0200
From: Anton Smirnov <asmirnov@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Ing-Wher Chen <ing-wher.chen@ericsson.com>, "ospf@ietf.org" <ospf@ietf.org>
References: <20140702132630.1320.28041.idtracker@ietfa.amsl.com> <BF6E0BD839774345977891C597F8B50C67D3EE@eusaamb109.ericsson.se>
In-Reply-To: <BF6E0BD839774345977891C597F8B50C67D3EE@eusaamb109.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Authenticated-User: asmirnov
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/enFUocwmPjAemTKpQak-IcIEaAg
Subject: Re: [OSPF] FW: New Version Notification for draft-chen-ospf-transition-to-ospfv3-01.txt
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, 08 Jul 2014 11:11:32 -0000

    Hi Helen,
    I believe encapsulation choice is per-link decision, i.e. there 
shouldn't be any problems in running IPv4 AF OSPFv3 over IPv4 on one 
link of a router and IPv4 AF OSPFv3 over IPv6 on another link as long as 
all routers connected to each link use the same encapsulation.
    Likewise, if IPv4 AF VL packets themselves are IPv4-encapsulated it 
shouldn't matter if physical links are using IPv6 or IPv4 encapsulation. 
The draft's text could be more clear on this aspect.

Anton


On 07/02/2014 04:02 PM, Ing-Wher Chen wrote:
> Hello,
>
> Acee, Ran, and I have updated the following draft to address the feedback at the last meeting and on the mailing list.  In particular, a new section on IPv4 use case has been added, and the edits that Karsten suggested back on Feb. 17, 2014 have also been incorporated.
>
> Thanks,
> Helen
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Wednesday, July 02, 2014 9:27 AM
> To: R. Atkinson; Ing-Wher Chen; Ing-Wher Chen; Acee Lindem; Acee Lindem
> Subject: New Version Notification for draft-chen-ospf-transition-to-ospfv3-01.txt
>
>
> A new version of I-D, draft-chen-ospf-transition-to-ospfv3-01.txt
> has been successfully submitted by I. Chen and posted to the IETF repository.
>
> Name:		draft-chen-ospf-transition-to-ospfv3
> Revision:	01
> Title:		OSPFv3 over IPv4 for IPv6 Transition
> Document date:	2014-07-02
> Group:		Individual Submission
> Pages:		9
> URL:            http://www.ietf.org/internet-drafts/draft-chen-ospf-transition-to-ospfv3-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-chen-ospf-transition-to-ospfv3/
> Htmlized:       http://tools.ietf.org/html/draft-chen-ospf-transition-to-ospfv3-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-chen-ospf-transition-to-ospfv3-01
>
> Abstract:
>     This document defines a mechanism to use IPv4 to transport OSPFv3
>     packets, in order to facilitate transition from IPv4-only to IPv6 and
>     dual-stack within a routing domain.  Using OSPFv3 over IPv4 with the
>     existing OSPFv3 Address Family extension can simplify transition from
>     an OSFPv2 IPv4-only routing domain to an OSPFv3 dual-stack routing
>     domain.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
>