[OSPF] Extensions to OSPF for Advertising Optional Router Capabilities
"Abhay D.S" <abhayds@acm.org> Thu, 09 November 2006 08:19 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gi583-0001Lo-BT; Thu, 09 Nov 2006 03:19:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gi581-0001Lf-24 for ospf@ietf.org; Thu, 09 Nov 2006 03:19:17 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gi57x-0004cb-WA for ospf@ietf.org; Thu, 09 Nov 2006 03:19:17 -0500
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8G00ABQFP99N@szxga02-in.huawei.com> for ospf@ietf.org; Thu, 09 Nov 2006 16:31:57 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0J8G00B8HFP8OL@szxga02-in.huawei.com> for ospf@ietf.org; Thu, 09 Nov 2006 16:31:57 +0800 (CST)
Received: from [127.0.0.1] ([10.111.34.184]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0J8G00MGQF39KZ@szxml03-in.huawei.com> for ospf@ietf.org; Thu, 09 Nov 2006 16:18:48 +0800 (CST)
Date: Thu, 09 Nov 2006 16:11:48 +0800
From: "Abhay D.S" <abhayds@acm.org>
To: ospf@ietf.org
Message-id: <4552E2C4.8090903@acm.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_yI4IiBjElKq9p/GuLz7jag)"
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Subject: [OSPF] Extensions to OSPF for Advertising Optional Router Capabilities
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: abhayds@acm.org
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 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 Any comments , - Abhay
_______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- Extensions to OSPF for Advertising Optional Route… Acee Lindem
- Re: Extensions to OSPF for Advertising Optional R… Vivek Dubey
- Re: Extensions to OSPF for Advertising Optional R… Acee Lindem
- [OSPF] Extensions to OSPF for Advertising Optiona… Abhay D.S
- Re: [OSPF] Extensions to OSPF for Advertising Opt… Acee Lindem
- Re: [OSPF] Extensions to OSPF for Advertising Opt… Abhay D.S
- [OSPF] Extensions to OSPF for Advertising Optiona… Erblichs
- Re: [OSPF] Extensions to OSPF for Advertising Opt… Acee Lindem