Re: ospfv3 - Route Entry
Acee Lindem <acee@CISCO.COM> Fri, 24 June 2005 16:42 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 MAA23475 for <ospf-archive@LISTS.IETF.ORG>; Fri, 24 Jun 2005 12:42:08 -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 <2.0108D219@cherry.ease.lsoft.com>; Fri, 24 Jun 2005 12:42:07 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 76690693 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 24 Jun 2005 12:42:05 -0400
Received: from 171.68.10.86 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Fri, 24 Jun 2005 12:42:05 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by sj-iport-4.cisco.com with ESMTP; 24 Jun 2005 09:42:04 -0700
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 j5OGg4bd027357 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 24 Jun 2005 12:42:04 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 24 Jun 2005 12:42:01 -0400
Received: from [10.82.242.173] ([10.82.242.173]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 24 Jun 2005 12:41:21 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <20050623052807.2138.qmail@mailweb34.rediffmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jun 2005 16:41:21.0151 (UTC) FILETIME=[8D2B18F0:01C578DB]
Message-ID: <42BC37D6.7090501@cisco.com>
Date: Fri, 24 Jun 2005 12:41:58 -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 - Route Entry
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <20050623052807.2138.qmail@mailweb34.rediffmail.com>
Precedence: list
Content-Transfer-Encoding: 7bit
Vivek Dubey wrote: >Hi, > > Hi Vivek, >RFC 2328: Section 11 >-------------------- >Destination Type: Router entries are kept for area border routers and AS boundary routers > >draft-ietf-ospf-ospfv3-update-04 >-------------------------------- >Section 3.3 The Routing table Structure: >An entry for each router in the area is kept > ><vivek> Calculation of reachability to stub networks and prefixes described in intra-area-prefix LSA is I guess similar. What's the need to maintain an entry for each router in the area ? > > Other implementations are possible. As you know, the OSPFv3 intra-area SPF calculation is done in 2 phases. First a Shortest Path Tree (SPT) is built from the router and network LSAs. In the second phase, the intra-area-prefix-LSAs are examined and routes are added to the routing table for reachable prefixes based on whether the reference LSA is reachable (among other checks). So, one either needs to lookup the route to the corresponding node in the SPT or the reference LSA. RFC 2740 chose the former and I think it is more straight forward. Thanks, Acee >Thanks >Vivek > > > > >
- ospfv3 - Route Entry Vivek Dubey
- Re: ospfv3 - Route Entry Acee Lindem
- Re: ospfv3 - Route Entry Vivek Dubey
- Re: ospfv3 - Route Entry Acee Lindem