Incremental update of Fletcher's checksum

Igor Miroshnik <IgorM@RADLAN.COM> Sat, 13 September 2003 15:06 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 LAA21034 for <ospf-archive@LISTS.IETF.ORG>; Sat, 13 Sep 2003 11:06:10 -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 <19.00B7E5B0@cherry.ease.lsoft.com>; Sat, 13 Sep 2003 11:06:11 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 54898474 for OSPF@PEACH.EASE.LSOFT.COM; Sat, 13 Sep 2003 11:06:10 -0400
Received: from 209.119.0.100 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Sat, 13 Sep 2003 11:06:10 -0400
Received: from PEACH.EASE.LSOFT.COM (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <11.00B7E613@cherry.ease.lsoft.com>; Sat, 13 Sep 2003 11:06:10 -0400
Message-ID: <LISTSERV%2003091311061035@PEACH.EASE.LSOFT.COM>
Date: Sat, 13 Sep 2003 11:06:10 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Igor Miroshnik <IgorM@RADLAN.COM>
Subject: Incremental update of Fletcher's checksum
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

Dear All,

Why should one wish to bother with this? Well, I thought not to issue a new
LSA if it differs from the predecessor merely in the sequence number.
(Unless the sequence is promoted on purpose.) The checksum comparison is a
reasonable first measure for decision on identity of two instances. Thus,
one would first compute the checksum for the old instance with the old
sequence number, and then, if needed, do the same with the next sequence
number. Doing the things incrementally would save some effort.

1) May the Fletcher's checksum be updated incrementally?
2) Does anybody know another way to effectively determine the need of
promoting the sequence?

Thanks,
Igor