Re: [OSPF] Database Exchange Summary List Optimization

Richard Ogier <ogier@earthlink.net> Thu, 26 October 2006 01:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcuL0-0001xc-Qn; Wed, 25 Oct 2006 21:47:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcuKz-0001xS-Hd for ospf@ietf.org; Wed, 25 Oct 2006 21:47:17 -0400
Received: from pop-savannah.atl.sa.earthlink.net ([207.69.195.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcuKy-0000FY-8I for ospf@ietf.org; Wed, 25 Oct 2006 21:47:17 -0400
Received: from dialup-4.243.131.195.dial1.sanfrancisco1.level3.net ([4.243.131.195] helo=earthlink.net) by pop-savannah.atl.sa.earthlink.net with esmtp (Exim 3.36 #1) id 1GcuKw-0001Al-00 for ospf@ietf.org; Wed, 25 Oct 2006 21:47:15 -0400
Message-ID: <454013A1.6070203@earthlink.net>
Date: Wed, 25 Oct 2006 18:47:13 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] Database Exchange Summary List Optimization
References: <44B7E563.3000706@cisco.com> <44B7E6D0.6030304@cisco.com> <44BD1FE6.2030202@earthlink.net> <44CAAB32.4B2A546D@earthlink.net> <44DB9074.8000700@earthlink.net> <44EE1D00.50502@cisco.com> <44F724CB.50100@earthlink.net> <Pine.LNX.4.64.0609041353380.1936@sheen.jakma.org> <44FDE7DD.6E016C98@earthlink.net> <44FDF3E9.50003@cisco.com> <44FE4E2F.BEAE45EA@earthlink.net> <44FF3450.2010708@cisco.com> <44FF5762.1A02E52@earthlink.net> <450183CE.4010805@earthlink.net> <450A1EE9.71A61D19@earthlink.net> <45194A5F.9060404@earthlink.net>
Content-Type: text/plain; charset="ISO-8859-2"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

As indicated in my message of 9/26/06, I submitted the following draft
update which removes Options B and C from the database exchange
summary list optimization.
http://www.ietf.org/internet-drafts/draft-ogier-ospf-dbex-opt-02.txt

Recall that Option A requires the summary list to be fully updated
(by processing all LSAs listed in the received DD packet) before
the next DD packet is sent in response.
Option A is no longer optional, but is part of the specification
in Section 2.  In addition, the draft clarifies that the new
step (which updates the summary list) may be performed either
before or after the router looks up the listed LSA in its database
and possibly adds the LSA to the Link state request list.
(See the last two paragraphs of Section 2.)
The point is that the summary list must be fully updated before
the next DD packet is sent, but other processing of a received
DD packet need not be done at the same time.
As a result, the spec no longer assumes that the router has
looked up the listed LSA in its database before deciding whether
to remove the LSA from the summary list.  Such details are
left to the implementation.

Richard


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf