Re: Detecting inactive neighbors over demand circuit
Acee Lindem <acee@REDBACK.COM> Wed, 18 August 2004 21:02 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 RAA16493 for <ospf-archive@LISTS.IETF.ORG>; Wed, 18 Aug 2004 17:02:36 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <16.00E4FE7F@cherry.ease.lsoft.com>; Wed, 18 Aug 2004 17:02:35 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 31351454 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 18 Aug 2004 17:02:33 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 18 Aug 2004 17:02:33 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 62A5BB58806 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 18 Aug 2004 14:02:33 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08345-06 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 18 Aug 2004 14:02:33 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.51]) by prattle.redback.com (Postfix) with SMTP id 9DE54B58805 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 18 Aug 2004 14:02:31 -0700 (PDT)
References: <20040809140300.08666790034@ws1-14.us4.outblaze.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID: <025401c48566$ad096910$0202a8c0@aceeinspiron>
Date: Wed, 18 Aug 2004 17:02:29 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Detecting inactive neighbors over demand circuit
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Hi Anu, The draft doesn't specify that you have to use a router LSA, it simply uses it as an example (draft-ietf-ospf-dc-07.txt). Also note that link LSAs are not flooded over virtual links (which are demand circuits by default). Having said that, a link LSA would seem like a good choice for probing on a non-virtual OSPFv3 interface. Note that this draft has been around for quite some time and is currently in the RFC editor's queue. Thanks, Acee ----- Original Message ----- From: "armstrong mathiayalagan" <arms@YOURS.COM> To: <OSPF@PEACH.EASE.LSOFT.COM> Sent: Monday, August 09, 2004 10:02 AM Subject: Detecting inactive neighbors over demand circuit > Hi, > This draft recommends (May clause) Router LSA to be flooded for Neighbor > probing. > With respect to the applicability of this draft to OSPFv3, I feel Link LSA > is a good choice for using in neighbor probing than Router LSA. > In Demand Circuit, there are more chances for having LSAs of different > sequence number at both ends. > If neighbor probing uses Router LSA, if the Router LSA is having higher > sequence number than the neighbors database, then the neighbor will flood > these LSA in all the non demand circuit interface. This can be avoided by > using Link LSA. > Comments are welcome. > > Regards, > Anu > -- > ___________________________________________________________ > Sign-up for Ads Free at Mail.com > http://promo.mail.com/adsfreejump.htm
- Detecting inactive neighbors over demand circuit armstrong mathiayalagan
- Re: Detecting inactive neighbors over demand circ… Erblichs
- Re: Detecting inactive neighbors over demand circ… Acee Lindem