Re: Extensions to OSPF for Advertising Optional Router Capabilities

Acee Lindem <acee@REDBACK.COM> Thu, 03 July 2003 03:15 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id XAA12766 for <ospf-archive@LISTS.IETF.ORG>; Wed, 2 Jul 2003 23:15:04 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM ( by (LSMTP for Digital Unix v1.1b) with SMTP id <>; Wed, 2 Jul 2003 23:14:58 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47438200 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 2 Jul 2003 23:04:19 -0400
Received: from by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 2 Jul 2003 23:04:19 -0400
Received: from ( []) by (Postfix) with ESMTP id 1723713BF66 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 2 Jul 2003 20:04:18 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <000001c233b6$2d1042a0$>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <>
Date: Wed, 02 Jul 2003 23:03:17 -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: Extensions to OSPF for Advertising Optional Router Capabilities
Precedence: list
Content-Transfer-Encoding: 7bit

Vivek Dubey wrote:
> 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
> policy."
> 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 ??

Hi Vivek,

I don't think this type of translation is necessary. Also, it is
somewhat counter to the goal of limiting the LSAs advertised into
a stub/NSSA area. If a very compelling application comes along then
maybe we could consider it in the future.


> E.g
> 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.
> thanks,
> vivek
> -----Original Message-----
> From: Mailing List []On Behalf Of Acee
> Lindem
> Sent: Wednesday, 2 July 2003 1:01 AM
> To:
> 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)
> <>
> Thanks,
> --
> Acee
> ***************************************************************************
> 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.
> ***************************************************************************