Re: Extensions to OSPF for Advertising Optional Router Capabilities

Vivek Dubey <vivekd@FUTURE.FUTSOFT.COM> Wed, 02 July 2003 08:31 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id EAA28439 for <ospf-archive@LISTS.IETF.ORG>; Wed, 2 Jul 2003 04:31:19 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM ( by (LSMTP for Digital Unix v1.1b) with SMTP id <>; Wed, 2 Jul 2003 4:31:19 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47323881 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 2 Jul 2003 04:31:17 -0400
Received: from by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 2 Jul 2003 04:31:16 -0400
Received: from (unverified) by (Content Technologies SMTPRS 2.0.15) with ESMTP id <> for <>; Wed, 02 Jul 2003 14:12:21 +0530
Received: from vivekd ( []) by (8.12.2/8.12.2) with SMTP id h628QI0r014465 for <>; Wed, 2 Jul 2003 13:56:19 +0530
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <000001c233b6$2d1042a0$>
Date: Thu, 25 Jul 2002 14:05:03 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vivek Dubey <vivekd@FUTURE.FUTSOFT.COM>
Subject: Re: Extensions to OSPF for Advertising Optional Router Capabilities
In-Reply-To: <>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Acee,
"If a type 11 opaque LSA
is chosen, the originating router should also advertise type 10
LSA(s) into any attached NSSA/stub area(s). The choice of flooding
scope is made by the advertising router and is a matter of local

Taking it otherwise, if NSSA ABR or ABR with attached STUB area
receives a Type 11 capability LSA (from some other router), should
it originate a Type 10 for its attached NSSA/STUB ??

Suppose Router R1(with attached NSSA/STUB) implements a policy "A"
and decides to originate Type 11 capability LSA (it will originate Type 10
attached in NSSA/STUB).

Another router R2(with no attached NSSA/STUB) in same AS implements
same policy "A" and originated Type 11 capability LSA.
Now should router R1 on receiving this LSA pass on this information
into attached NSSA/STUB areas?

Since the policy which decided the scope is same in both routers,
isn't capability info is of interest to routers internal to STUB/NSSA.


-----Original Message-----
From: Mailing List []On Behalf Of Acee
Sent: Wednesday, 2 July 2003 1:01 AM
Subject: Extensions to OSPF for Advertising Optional Router Capabilities

I've respun the subject draft with some minor corrections.
We've discussed it at the last three IETFs and there has been
some (although light) discussion on the OSPF List. There are now
at least three proposed applications. Unless there is
vehement opposition, we intend to add this as a WG document shortly
after the Vienna IETF (when the window for new drafts opens again)



This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.