Why recalculation from scratch?

"Liu B." <binl@EEE-FS7.BHAM.AC.UK> Wed, 14 August 2002 16:45 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 MAA16441 for <ospf-archive@LISTS.IETF.ORG>; Wed, 14 Aug 2002 12:45:40 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <10.006D4005@cherry.ease.lsoft.com>; Wed, 14 Aug 2002 12:46:59 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 107036 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 14 Aug 2002 12:46:59 -0400
Received: from 147.188.128.54 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 14 Aug 2002 12:46:59 -0400
Received: from bham.ac.uk ([147.188.128.127]) by mailer3.bham.ac.uk with esmtp (Exim 3.16 #2) id 17f1IQ-00009W-00 for OSPF@discuss.microsoft.com; Wed, 14 Aug 2002 17:46:58 +0100
Received: from eee-fs7.bham.ac.uk ([147.188.145.131] helo=bham-eee-fs7.bham.ac.uk) by bham.ac.uk with esmtp (Exim 3.16 #3) id 17f1IQ-0005x3-00 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 14 Aug 2002 17:46:58 +0100
Received: by BHAM-EEE-FS7 with Internet Mail Service (5.5.2653.19) id <QMAY778F>; Wed, 14 Aug 2002 17:46:58 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <B036F14C7A7FD511827000805FFEA8AD0C9E8B@BHAM-EEE-FS7>
Date: Wed, 14 Aug 2002 17:46:57 +0100
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Liu B." <binl@EEE-FS7.BHAM.AC.UK>
Subject: Why recalculation from scratch?
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

Hello there,

I noticed that in "The New Routing Algorithm for the ARPANET" [John M.
McQuillan], lots of work had been done on how to avoid recalculation from
scratch in link state routing. Why OSPF does recalculate from scratch? Does
it mean that CPU cost is negligible?

Many thanks.

Bin