Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-00.txt
Karsten Thomann <karsten_thomann@linfre.de> Sat, 15 February 2014 12:22 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 A43121A01DC for <ospf@ietfa.amsl.com>; Sat, 15 Feb 2014 04:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 TUDGNFAUsOfd for <ospf@ietfa.amsl.com>; Sat, 15 Feb 2014 04:22:19 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) by ietfa.amsl.com (Postfix) with ESMTP id 26C9F1A00D5 for <ospf@ietf.org>; Sat, 15 Feb 2014 04:22:19 -0800 (PST)
Received: from linne.localnet (91.97.110.48) by linfreserv.linfre (Axigen) with (AES256-SHA encrypted) ESMTPSA id 036BA3; Sat, 15 Feb 2014 13:22:07 +0100
From: Karsten Thomann <karsten_thomann@linfre.de>
To: ospf@ietf.org
Date: Sat, 15 Feb 2014 13:22:11 +0100
Message-ID: <22830726.PZv4OAbFD0@linne>
User-Agent: KMail/4.10.4 (Windows/6.1; KDE/4.10.4; i686; ; )
In-Reply-To: <D15BB47E-2576-4AB9-83F2-3CA4CB282A5C@gmail.com>
References: <D15BB47E-2576-4AB9-83F2-3CA4CB282A5C@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart8146481.33cAHHMDrd"
Content-Transfer-Encoding: 7bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 8
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/DF8YztoRPkKQqi1MpNmXjDFgBuU
Subject: Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-00.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: Sat, 15 Feb 2014 12:22:22 -0000
Am Montag, 10. Februar 2014, 14:33:05 schrieb RJ Atkinson: > Earlier, Karsten Thomann wrote, in part: > > I don't know if i have missed that part, but what would happen if OSPFv3 > > is running over IPv4 and there are two (or more) IPv6 Islands already > > deployed within the network, should there be any LSA flooding checks, > > like do not flood LSA with IPv6 networks over IPv4 only links, or should > > the route > > calculation/installation of the information simply fail > > as there is no valid path? > > The OSPF deployments I am familiar with did not "auto deploy" > or "self deploy". Instead, all of the OSPF deployments that I am > familiar with had engineers making deliberate decisions about how > to configure the OSPF deployment, and also how to configure the > OSPF routers in that deployment. I know that such deployments are normally well planned, but as there is already a draft about ospfv3 autoconfig, even if it is not designed to be used in company networks. > One deployment option, already deployed in some places, is to run > "ships in the night". In this model, the IPv4 topology exclusively > uses OSPFv2 over IPv4 and the IPv6 topology exclusively uses OSPFv3 > over IPv6. For some sites, that is a good option. A number of my > clients are very interested in this new I-D because it optimises > their IPv6 transition strategy. > > For some sites, IPv6 transition is simplified, optimised, and also > cost-reduced by using OSPFv3 over IPv4 initially, and carrying both > IPv4 prefixes and IPv6 prefixes inside that one OSPFv3 deployment > (i.e. using the Address Family extension to keep the prefixes clearly > differentiated within a single OSPFv3 deployment). This can lower > operational costs because one can get by with managing only OSPFv3, > rather than having to manage both OSPFv2 and OSPFv3. > > If one's "IPv6 islands" (to use your term) are really dual-stack > (aside: having dual-stack rather than IPv6-only would be expected > and normal if another part of one's OSPF deployment is using > OSPF over IPv4), then EITHER the whole deployment should be configured > to run over IPv4 XOR the whole deployment should be configured > to run over IPv6. > > Having different "IPv4 islands" and "IPv6 islands" is an explicit choice > of a configuration engineer or design engineer. That probably is not > the optimal deployment choice for an engineer to make. It definitely > is NOT a choice that I would make or that I would recommend to my clients. I would not do it either, but I have already seen some strange ospf designs..., and as mentioned it is a case which can happen with ospf autoconfiguration, but we don't need to discuss it further as it is for homenetworks > From the descriptions and definitions in the draft, it would not be > "normal" or "expected" to mix IPv6 transport with IPv4 transport > within a single OSPFv3 deployment. > > > Is there any explicit preference over which version the adjacency > > is build if v4 and v6 is available in that specific part of the network? > > The choice of preferred OSPF transport really is something that the > configuration engineer ought to configure. As the details of configuring > any IP router are outside the scope of the IETF, I am not sure that > this I-D properly can or should say very more than it already says. > > Perhaps the I-D could add clarifying text along these lines > somewhere in Section 2: > > "Implementers of OSPFv3 over IPv4 SHOULD add a configuration > knob to let the router administrator select whether a given > OSPFv3-enabled interface should use OSPFv3 over IPv4 or > OSPFv3 over IPv6. Except when an OSPFv3 deployment is being > transitioned from using IPv4 transmission to using IPv6 > transmission, it is RECOMMENDED that all routers within an > OSPFv3 deployment use the same IP version for OSPFv3 packet > transmission." > > > What should happen when an IPv4 Link gets v6 added, graceful reestablish > > the adjacency over IPv6, or wait until forced protocol switch? > > See my answer just above. > > I would expect that any router that implements this I-D also would implement > a configuration knob to indicate whether IPv4 transmission or IPv6 > transmission is preferred. Over time, a configuration engineer might > change this (e.g. manually change from IPv4 transmission to IPv6 > transmission AFTER an entire IPv4 network has been > deployed-with/converted-to dual-stack IPv4 and IPv6). > > Yours, > > Ran Atkinson Thanks for the detailed anwsers, I'm satisfied with the addition. Kind regards, Karsten > > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf
- Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-0… RJ Atkinson
- Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-0… Karsten Thomann
- Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-0… Acee Lindem
- Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-0… Karsten Thomann
- Re: [OSPF] draft-chen-ospf-transition-to-ospfv3-0… Acee Lindem