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

Acee Lindem <acee@lindem.com> Sun, 13 July 2014 11:18 UTC

Return-Path: <acee@lindem.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 E9BAA1B2A67 for <ospf@ietfa.amsl.com>; Sun, 13 Jul 2014 04:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 YOyztgzkPNSo for <ospf@ietfa.amsl.com>; Sun, 13 Jul 2014 04:18:19 -0700 (PDT)
Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) by ietfa.amsl.com (Postfix) with ESMTP id 2508E1B2A5C for <ospf@ietf.org>; Sun, 13 Jul 2014 04:18:19 -0700 (PDT)
Received: from [65.190.6.125] ([65.190.6.125:33956] helo=[10.0.1.6]) by cdptpa-oedge01 (envelope-from <acee@lindem.com>) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 0C/16-17895-AFA62C35; Sun, 13 Jul 2014 11:18:18 +0000
From: Acee Lindem <acee@lindem.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3D0B468C-BC89-4D74-83A7-5F79BBD67944"
Date: Sun, 13 Jul 2014 07:18:17 -0400
Message-Id: <A65F736F-AB3E-4616-A48C-822C7B2ADB6A@lindem.com>
To: Anton Smirnov <asmirnov@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
X-RR-Connecting-IP: 107.14.168.118:25
X-Cloudmark-Score: 0
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/7YAAsNbzDWcDNjuQhw0k5B-AwvY
Cc: OSPF List <ospf@ietf.org>, Ing-Wher Chen <ing-wher.chen@ericsson.com>
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: Sun, 13 Jul 2014 11:18:21 -0000

Hi Anton, 
On Jul 8, 2014, at 7:11 AM, Anton Smirnov <asmirnov@cisco.com> wrote:

> 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.

Yes - this should be possible for OSPF interfaces and could be useful if one wants to use standard IPv6 encapsulation in all cases except a particular interface that doesn’t support IPv6 (as described in section 3). 

> 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.

Since the virtual link endpoint is determined dynamical and a virtual link is only considered up when there is reachability in the transit area, OSPF for an address family differing from the encapsulation cannot work without mechanisms outside the protocol., Hence, this isn’t something that will included in the scope of this draft. 

Thanks,
Acee 



> 
> 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.
>> 
>> 
>> 
>> 
>> Pl