Re: [OSPF] Extensions to OSPF for Advertising Optional Router Capabilities

Acee Lindem <acee@cisco.com> Mon, 27 November 2006 22:11 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Googo-0003TV-71; Mon, 27 Nov 2006 17:11:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Googm-0003TI-NK for ospf@ietf.org; Mon, 27 Nov 2006 17:11:00 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Googl-00009Z-BL for ospf@ietf.org; Mon, 27 Nov 2006 17:11:00 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-4.cisco.com with ESMTP; 27 Nov 2006 14:10:58 -0800
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kARMAwVT007063; Mon, 27 Nov 2006 17:10:58 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kARMAvDM013226; Mon, 27 Nov 2006 17:10:57 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Nov 2006 17:10:57 -0500
Received: from [10.82.224.37] ([10.82.224.37]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Nov 2006 17:10:57 -0500
Message-ID: <456B6270.3080203@cisco.com>
Date: Mon, 27 Nov 2006 17:10:56 -0500
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: abhayds@acm.org
Subject: Re: [OSPF] Extensions to OSPF for Advertising Optional Router Capabilities
References: <4552E2C4.8090903@acm.org>
In-Reply-To: <4552E2C4.8090903@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Nov 2006 22:10:57.0436 (UTC) FILETIME=[E9F875C0:01C71270]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2434; t=1164665458; x=1165529458; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acee@cisco.com; z=From:=20Acee=20Lindem=20<acee@cisco.com> |Subject:=20Re=3A=20[OSPF]=20Extensions=20to=20OSPF=20for=20Advertising=2 0Optional=20Router=09Capabilities |Sender:=20 |To:=20abhayds@acm.org; bh=iKNhni2+aa3HnY9n72DiVsZ7q7KGYRvNFUPeNPGkUpM=; b=LzoippOQk5AZB2y0xCqkIutSE6NuCgTO0e8WtCG655zu5TKLkM9IiV6uoij4mLt4h8sUU21J GXiFO/zU/P0h0UfFS6DUFFcTYUpar4pUmVzcb/BpubLOJ8+DRr5sNrHl;
Authentication-Results: rtp-dkim-2; header.From=acee@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: ospf@ietf.org
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

Hi Abhay,

Abhay D.S wrote:
>
> hi acee, and other neighbors in the AS,
>
>   5.  Flooding Scope of the Router Information LSA
>
>   The flooding scope for a Router Information LSA is determined by the
>   LSA type.  For OSPFv2, type 9 (link-scoped), type 10 (area-scoped),
>   or a type 11 (AS-scoped) opaque LSA may be flooded.  For OSPFv3, the
>   S1 and S2 bits in the LSA type determine flooding scope.  If AS wide
>   flooding scope is chosen, the originating router should also
>   advertise area scoped LSA(s) into any attached NSSA area(s).  An OSPF
>   router MAY advertise different capabilities when both NSSA area
>   scoped LSA(s) and an AS scoped LSA are advertised.  This allows
>   functional capabilities to be limited in scope.  For example, a
>   router may be an area border router but only support traffic
>   engineering (TE) in a subset of its attached areas.
>
>   *The choice of flooding scope is made by the advertising router and is
>   a matter of local policy.
>   *This specification, takes OSPFv2 to new levels of  intelligence.
>   Flooding scope MAY  also be policed. Such as only a subset of 
> capabilities to be
>   advertised  from capability subset in each scope.
>
>   Such as when a router becomes ASBR, ABR or just an Internal Area 
> Router, GR capable
>   Overloaded, busy for example (if you receive a busy bit) (add to 
> capability set ?). Busy and Free
>   capability  might be used by CSPF. ( You might have just edited the 
> new specification for the TE Addresses
>   for all OSPF interfaces). You might read the relation.
>
>   You might want to add a section, IMPACT:   Where in you might add 
> the impact
>    Action: Router shall perform only those actions upon reception of 
> these capability information
Since the draft defines a generic mechanism for advertising router 
capabilities and
the action an OSPF router would take is specific to a capability, I 
don't think this is
necessary. Note that all the bits in the OSPF Router Informational 
Capabilities TLV
are informational and no explicit action is necessary.

Thanks,
Acee
>
>   Any comments ,
>   - Abhay
>  
>
>
>  
>  
>  
>   
>  
> ------------------------------------------------------------------------
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf
>   

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf