Re: Routing IPv4 with OSPFv3
Vincent Jardin <jardin@6WIND.COM> Mon, 19 August 2002 09:54 UTC
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26713 for <ospf-archive@LISTS.IETF.ORG>; Mon, 19 Aug 2002 05:54:32 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.006DEBEA@cherry.ease.lsoft.com>; Mon, 19 Aug 2002 5:55:50 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 124833 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 19 Aug 2002 05:55:46 -0400
Received: from 212.234.238.114 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 19 Aug 2002 05:45:46 -0400
Received: from intranet.6wind.com (intranet.6wind.com [10.0.0.113]) by givenchy.6wind.com (Postfix) with ESMTP id 46D47862 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 19 Aug 2002 11:54:38 +0200 (CEST)
Received: from 6wind.com (intranet.6wind.com [10.0.0.113]) by intranet.6wind.com (Postfix) with ESMTP id 0B6E3B4FA for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 19 Aug 2002 11:45:39 +0200 (CEST)
X-Mailer: Mozilla 4.72 [fr] (X11; U; Linux 2.2.14-6.1.1smp i686)
X-Accept-Language: fr, en
MIME-Version: 1.0
References: <3D5B4B88.215EA127@arc.corp.mot.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <3D60BE42.2B403ECD@6wind.com>
Date: Mon, 19 Aug 2002 11:45:39 +0200
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Vincent Jardin <jardin@6WIND.COM>
Organization: http://www.6WIND.net
Subject: Re: Routing IPv4 with OSPFv3
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 8bit
Arthur Dimitrelis a écrit : > > Greetings, > > I'm interested in people's opinions and experiences in using OSPFv3 (aka > OSPF for IPv6) for routing IPv4. > > My understanding from reading the OSPFv3 specification (RFC2740) is that > OSPFv3 is designed with a degree of protocol independence. By this I > mean that you could, in principle, use OSPFv3 to route any protocol > family you chose, just so long as you were able to map addressing > information to the topology (and of course your OSPF code knew how to > set up the correct forwarding state for your given protocol family). The > topology-to-address mapping for IPv6 is done using OSPFv3's > Intra-area-prefix-LSAs, but the spec makes no mention of how you might > map IPv4 addressing information to a network topology. > > So, my questions are: > - Regarding OSPFv3 - is the bulk of it protocol agnostic, or is it just > my imagination? Was it the intention of the protocol authors to create a > protocol that could easily route multiple protocol families, or just > IPv6? > - Is there any interest out there in using OSPFv3 to route IPv4? According to me, if there is a single routing protocol for both IPv4 and IPv6, the routers that support only an IPvX could be detected. Some tunnels could be used to route through them. The endpoints of these tunnels could be the routers that support both IPv4 and IPv6. My understanding of the section 3.8 of the Integrated IS-IS RFC-1195 is that IS-IS supports this kind of feature that is described by the ISO/10589. However, who needs this repairing function ? Regards, Vincent
- Routing IPv4 with OSPFv3 Arthur Dimitrelis
- Re: Routing IPv4 with OSPFv3 Yasuhiro Ohara
- Re: Routing IPv4 with OSPFv3 Vincent Jardin
- Re: Routing IPv4 with OSPFv3 Naiming Shen
- Re: Routing IPv4 with OSPFv3 Li, Ke Qin (Peter)
- Re: Routing IPv4 with OSPFv3 Manral, Vishwas