Re: Seeming contradiction on forwarding addresses?

Acee Lindem <acee@REDBACK.COM> Mon, 13 October 2003 21:53 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 RAA01113 for <ospf-archive@LISTS.IETF.ORG>; Mon, 13 Oct 2003 17:53:10 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <10.00C0B3BB@cherry.ease.lsoft.com>; Mon, 13 Oct 2003 17:53:18 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 57780669 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 13 Oct 2003 17:53:17 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 13 Oct 2003 17:53:17 -0400
Received: from redback.com (pptp-6-156.redback.com [155.53.6.156]) by prattle.redback.com (Postfix) with ESMTP id 7B39D52A760 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 13 Oct 2003 14:53:15 -0700 (PDT)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <OFF265FDF3.3179C327-ON85256DBE.0074C84E-85256DBE.007586A6@us.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F8B1ECA.2080000@redback.com>
Date: Mon, 13 Oct 2003 17:53:14 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Seeming contradiction on forwarding addresses?
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <OFF265FDF3.3179C327-ON85256DBE.0074C84E-85256DBE.007586A6@us.ibm.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Mike,

Mike Fox wrote:

>RFC 2328 says, in section 12.4.4.1 regarding forwarding addresses in
>external LSAs:
>
>
>
>>Note that when the forwarding address field is non-
>>zero, it should point to a router belonging to
>>another Autonomous System.
>>
>>
>
>But then when discussing calculation of external routes in section  16.4 it
>says:
>
>
>
>>If the forwarding address is non-zero, look up the
>>forwarding address in the routing table.[24] The matching
>>routing table entry must specify an intra-area or inter-area
>>path; if no such path exists, do nothing with the LSA and
>>consider the next in the list.
>>
>>
>
>So the RFC says that a forwarding address should be to an AS external
>address, but no one can use an external LSA if the only way to reach the
>forwarding address is via an AS External route?  Footnote 24 re-emphasizes
>that point also.  Is there something I am missing here?
>
The  thing here is that the forwarding address is for a router that
provides a path to IPv4 prefixes
outside the OSPF routing domain. However, the forwarding address itself
must be reachable
by an OSPF intra-area or inter-area route (which is by definition part
of the OSPF routing
domain).  In this context, I prefer to use the term OSPF routing domain
rather than AS since
there will often be non-OSPF routes in use within an AS running OSPF as
the IGP.

I hope I've made sense.

Acee



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