Re: OSPFv3 fwd'ing address

Acee Lindem <acee@CISCO.COM> Sat, 06 August 2005 15:52 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E1Qxx-0005Ob-9B for ospf-archive@megatron.ietf.org; Sat, 06 Aug 2005 11:52:05 -0400
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 LAA28747 for <ospf-archive@LISTS.IETF.ORG>; Sat, 6 Aug 2005 11:52:02 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <19.010C10CD@cherry.ease.lsoft.com>; Sat, 6 Aug 2005 11:52:04 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 81629401 for OSPF@PEACH.EASE.LSOFT.COM; Sat, 6 Aug 2005 11:52:02 -0400
Received: from 64.102.122.149 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Sat, 6 Aug 2005 11:52:02 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 06 Aug 2005 11:52:02 -0400
X-IronPort-AV: i="3.95,172,1120449600"; d="scan'208"; a="65494288:sNHT30407520"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j76FpvT8009097 for <OSPF@PEACH.EASE.LSOFT.COM>; Sat, 6 Aug 2005 11:51:59 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 6 Aug 2005 11:52:08 -0400
Received: from [10.86.242.179] ([10.86.242.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 6 Aug 2005 11:51:58 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <OF06940A42.8EB24A30-ON85257053.0067A0D7-85257053.0068512B@us.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Aug 2005 15:51:58.0459 (UTC) FILETIME=[C7076CB0:01C59A9E]
Message-ID: <42F4AD6B.4090207@cisco.com>
Date: Sat, 06 Aug 2005 08:30:35 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: OSPFv3 fwd'ing address
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <OF06940A42.8EB24A30-ON85257053.0067A0D7-85257053.0068512B@us.ibm.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Mike,

Mike Fox wrote:

>Naiming Shen wrote:
>
>  
>
>>But if we think of this problem in another way, this 'nexthop' is only
>>an internal state within the router, what does anyone care if
>>I use a true 'link-local' address as a nexthop, or use the global
>>address as the nexthop which passed by the OSPF forwarding address?
>>I would not implement the IPv6 forwarding in a way to only
>>accept the link-local as nexthops.
>>    
>>
>
>That's how we implemented it.  For the AS-External forwarding address, our 
>implementation will accept any non-link-local address that is reachable 
>using the OSPF protocol.  As a user of an AS-External LSA we will send 
>packets for the external destination to the specified forwarding address 
>(if provided) and we assumed others would do the same, so as long as 
>routers in the AS can route to that forwarding address, it should work. 
>
>This significantly limits its usefulness, but it does work.  The place we 
>expect to see this used the most is for external default routes.  On our 
>platform the user can specify that an ASBR is to advertise an external 
>default route, and the user can optionally specify a forwarding address to 
>use on that route, with the restrictions that it can't be a link-local 
>address and it has to be an address or prefix that is routable in the OSPF 
>domain. 
>  
>
I don't see any problems with this as long as a global IPv6 address is 
available - either as the
next-hop gateway in the redistributed route or explicitly specified. I 
could document this case. .

>Mike
>-----------------------------------------------------------------------
>Enterprise Network Solutions
>-----------------------------------------------------------------------
>Research Triangle Park, NC  USA
>  
>