Re: new LSA

Naiming Shen <naiming@REDBACK.COM> Thu, 15 August 2002 16:55 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 MAA04588 for <ospf-archive@LISTS.IETF.ORG>; Thu, 15 Aug 2002 12:55:38 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <10.006D6BD5@cherry.ease.lsoft.com>; Thu, 15 Aug 2002 12:56:58 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 111723 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 15 Aug 2002 12:56:54 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 15 Aug 2002 12:56:54 -0400
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 31F6D1DCC60; Thu, 15 Aug 2002 09:56:57 -0700 (PDT)
Message-ID: <20020815165657.31F6D1DCC60@prattle.redback.com>
Date: Thu, 15 Aug 2002 09:56:57 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Naiming Shen <naiming@REDBACK.COM>
Subject: Re: new LSA
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: Mail from Dave Katz <dkatz@JUNIPER.NET> dated Thu, 15 Aug 2002 08:46:19 PDT <200208151546.g7FFkJR68983@cirrus.juniper.net>
Precedence: list

 ]         Lets assume that we modify the LSA comparison code sections
 ]         and we keep the older LSA versions for a short time assuming
 ]         we have the memory available.
 ]
 ]         What would you say we can now do with this additional information?
 ]
 ] Not a whole lot, since you cannot rely upon hearing every version of
 ] every LSA, only the latest one.  There are a number of scenarios
 ] in which an LSA being flooded can be overtaken by a newer version,
 ] and thus the older one may not be delivered to everyone.

If router X received LSAs from router A with version a, b, c and d;
router Y only received a and d. If both X and Y decide to do version/
content comparison, it just means X is going to do 3 times, and Y
is going to do one time only. But the end result should be the same
since they all get the finally version of d. Unless the version/
content comparison code has problem.

thanks.
- Naiming