Indication LSA impact

Kalyan Bade <kalyan@JUNIPER.NET> Tue, 10 May 2005 07:23 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 DAA23517 for <ospf-archive@LISTS.IETF.ORG>; Tue, 10 May 2005 03:23:23 -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 <8.0103DD14@cherry.ease.lsoft.com>; Tue, 10 May 2005 3:23:20 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 70039993 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 10 May 2005 03:23:19 -0400
Received: from 207.17.137.120 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Tue, 10 May 2005 03:13:19 -0400
Received: from unknown (HELO alpha.jnpr.net) (172.24.18.126) by kremlin.juniper.net with ESMTP; 10 May 2005 00:13:18 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.92,170,1112598000"; d="scan'208"; a="295980897:sNHT20092912"
Received: from photon.jnpr.net ([172.24.18.198]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 10 May 2005 00:13:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thread-Topic: Indication LSA impact
Thread-Index: AcVVHSLwexLJX/GyQKeKdmv74xhbsgAA5QCw
X-OriginalArrivalTime: 10 May 2005 07:13:18.0399 (UTC) FILETIME=[BDAD1CF0:01C5552F]
Message-ID: <062B922B6EC55149B5A267ECE78E5D4406A5C8A9@photon.jnpr.net>
Date: Tue, 10 May 2005 00:13:17 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Kalyan Bade <kalyan@JUNIPER.NET>
Subject: Indication LSA impact
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable

Folks,

I was going through rfc 1793 (demand circuit extensions for OSPF) and
have a question regarding the generation of indication LSAs and its
impact on the LSAs created/flooded.

Suppose if we have three routers as shown in the setup below.

R0 ------ R1 ------ R2
   Area X    Area Y 

Say if R0 is a DC uncapable router, the area X is considered DC
uncapable. Which means that none of the routers in area X can generate
an area scope/AS scope LSAs with DoNotAge bit set. 

And as per the spec, an indication LSA is generated in area Y and this
makes the area Y also as DC uncapable. So, my question is what is the
rationale behind making area Y as DC uncapable? I understand that any
router in area Y shouldn't generate an AS scope LSA with DoNotAge bit
set, but why should that hold to area scope LSA's?

Thanks,
Kalyan.