Clarification on Flooding

Paresh Khatri <pkhatri@AAPT.COM.AU> Wed, 11 June 2003 22:55 UTC

Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Disposition: inline
Message-ID: <see84015.009@aapt-gwia2.aapt.com.au>
Date: Thu, 12 Jun 2003 08:55:34 +1000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Paresh Khatri <pkhatri@AAPT.COM.AU>
Subject: Clarification on Flooding
Comments: To: OSPF@.EASE.LSOFT.COM
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 8bit

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