Re: Clarification on Flooding
Parag Deshpande <paragdeshpande@SDKSOFT.COM> Wed, 11 June 2003 23:43 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 TAA09639 for <ospf-archive@LISTS.IETF.ORG>; Wed, 11 Jun 2003 19:43:17 -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 <13.00A0EC55@cherry.ease.lsoft.com>; Wed, 11 Jun 2003 19:43:18 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45347176 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 11 Jun 2003 19:43:17 -0400
Received: from 63.231.195.115 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 11 Jun 2003 19:33:15 -0400
Received: (qmail 19736 invoked by uid 0); 11 Jun 2003 23:33:14 -0000
Received: from mpls-pop-08.inet.qwest.net (63.231.195.8) by mpls-qmqp-04.inet.qwest.net with QMQP; 11 Jun 2003 23:33:14 -0000
Received: from 0-1pool174-4.nas18.minneapolis1.mn.us.da.qwest.net (HELO charita) (67.4.174.4) by mpls-pop-08.inet.qwest.net with SMTP; 11 Jun 2003 23:33:14 -0000
References: <see84015.009@aapt-gwia2.aapt.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <052101c33071$e0a42f80$cbc8c8c8@sdksoft.com>
Date: Wed, 11 Jun 2003 18:33:35 -0500
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Parag Deshpande <paragdeshpande@SDKSOFT.COM>
Subject: Re: Clarification on Flooding
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
From my understanding this is what it means - A router requests an lsa when either the lsa is not present in its db or the db copy is older. When router receives a DD packet that contains a new/newer lsa it would request that lsa from the nbr. In this case the nbr sent an lsa which is either same or older which either means that the request created was incorrect or the nbr misbehaved, hence the Database exchange must restart. Parag ----- Original Message ----- From: Paresh Khatri <pkhatri@AAPT.COM.AU> To: <OSPF@PEACH.EASE.LSOFT.COM> Sent: Wednesday, June 11, 2003 5:55 PM Subject: Clarification on Flooding HI all, Would someone be able to explain the following clause in RFC2328 to me ? This is in Section 13. Flooding Procedure: Page 145 (6) Else, if there is an instance of the LSA on the sending neighbor's Link state request list, an error has occurred in the Database Exchange process. In this case, restart the Database Exchange process by generating the neighbor event BadLSReq for the sending neighbor and stop processing the Link State Update packet. Why is this an error ? If the LSA is on the Link state request list for the neighbor, are we not expecting that LSA from that neighbor ? All responses appreciated. Paresh Khatri.
- Clarification on Flooding Paresh Khatri
- Re: Clarification on Flooding Parag Deshpande
- Re: Clarification on Flooding Acee Lindem
- Re: Clarification on Flooding Paresh Khatri