Re: new LSA

Erblichs <erblichs@EARTHLINK.NET> Thu, 15 August 2002 07: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 DAA15484 for <ospf-archive@LISTS.IETF.ORG>; Thu, 15 Aug 2002 03:06:38 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <8.006D5E56@cherry.ease.lsoft.com>; Thu, 15 Aug 2002 3:07:56 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 109077 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 15 Aug 2002 03:07:54 -0400
Received: from 207.217.120.50 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 15 Aug 2002 03:07:54 -0400
Received: from user-2ivfj2i.dialup.mindspring.com ([165.247.204.82] helo=earthlink.net) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17fEjb-00026T-00 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 15 Aug 2002 00:07:55 -0700
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <20020814085042.96790.qmail@mail.com> <3D5B2086.9000906@redback.com> <3D5B49F8.A518DA7@earthlink.net> <3D5B4A31.4050901@redback.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <3D5B5612.D3F43030@earthlink.net>
Date: Thu, 15 Aug 2002 00:19:46 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Erblichs <erblichs@EARTHLINK.NET>
Subject: Re: new LSA
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Acee,

        Then what would / could you do with this information? Could it
        be useful in anyway? Have you ever heard of anyone really
        interested in this type of information?

        Mitchell Erblich
        ======================


Acee Lindem wrote:
>
> Erblichs wrote:
>
> > Acee,
> >
> >         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.
>
> Mitchell,
>
> Wasn't the original question whether this could be done without the
> previous LSA?
>
> >
> >         What would you say we can now do with this additional information?
>
> If you had the previous LSA you could definitely determine what had
> changed between the two versions.
>
> >
> >         Mitchell Erblich
> >         ===================
> >
> >
> > Acee Lindem wrote:
> >
> >>Beatriz Silva wrote:
> >>
> >>
> >>>Hi everybody !
> >>>
> >>>I would like to know if it is possible (in OSPF v2) to identify, just by examining the LSA, what is the change the LSA is signaling. I want to identify if for example an router LSA was sent because the cost of one of the links was changed, or if it was because one of the links went down .... This, without having the previous LSAs, just by looking at the newly received LSA. Is it possible ? How  ?
> >>>
> >>>
> >>Beatriz,
> >>
> >>AFAIK, there is no way to determine what has changed without a previous version
> >>of the LSA.
> >>
> >>
> >>>Thank you very much,
> >>>Beatriz
> >>>
> >>>--
> >>>__________________________________________________________
> >>>Sign-up for your own FREE Personalized E-mail at Mail.com
> >>>http://www.mail.com/?sr=signup
> >>>
> >>>
> >>>
> >>--
> >>Acee
> >>
> >
>
> --
> Acee