Re: Maximum Prefix Limit

Enke Chen <enke@redback.com> Wed, 16 January 2002 05:38 UTC

Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id AAA21624 for <idr-archive@nic.merit.edu>; Wed, 16 Jan 2002 00:38:15 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 120DC912AF; Wed, 16 Jan 2002 00:37:36 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id D9E80912B0; Wed, 16 Jan 2002 00:37:35 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id EC5DC912AF for <idr@trapdoor.merit.edu>; Wed, 16 Jan 2002 00:37:34 -0500 (EST)
Received: by segue.merit.edu (Postfix) id CA2A35DDC1; Wed, 16 Jan 2002 00:37:34 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by segue.merit.edu (Postfix) with ESMTP id 5FC445DDA0 for <idr@merit.edu>; Wed, 16 Jan 2002 00:37:34 -0500 (EST)
Received: from popserv1.redback.com (popserv1.redback.com [155.53.12.56]) by prattle.redback.com (Postfix) with ESMTP id C66AB1DCC62; Tue, 15 Jan 2002 21:37:33 -0800 (PST)
Received: from redback.com (fall.redback.com [155.53.36.220]) by popserv1.redback.com (Postfix) with ESMTP id DC01615D3C1; Tue, 15 Jan 2002 21:37:31 -0800 (PST)
To: Manav Bhatia <mnvbhatia@yahoo.com>
Cc: idr@merit.edu
Subject: Re: Maximum Prefix Limit
In-Reply-To: Message from "Manav Bhatia" <mnvbhatia@yahoo.com> of "Wed, 16 Jan 2002 10:58:43 +0530." <03b001c19e4e$aa86e750$b4036c6b@Manav>
Date: Tue, 15 Jan 2002 21:37:30 -0800
From: Enke Chen <enke@redback.com>
Message-Id: <20020116053731.DC01615D3C1@popserv1.redback.com>
Sender: owner-idr@merit.edu
Precedence: bulk

Hi, Manav:
Regarding the CEASE subcode, please see the following draft:

       draft-ietf-idr-cease-subcode-00.txt

-- Enke

> Message-ID: <03b001c19e4e$aa86e750$b4036c6b@Manav>
> Reply-To: "Manav Bhatia" <mnvbhatia@yahoo.com>
> From: "Manav Bhatia" <mnvbhatia@yahoo.com>
> To: <idr@merit.edu>
> Subject: Maximum Prefix Limit
> Date: Wed, 16 Jan 2002 10:58:43 +0530
> MIME-Version: 1.0
> 
> Hi,
> 
> I am working on BGP implementation of the "maximum prefix limit" feature
> which is like a protection mechanism against route leaking. A warning flag
> will be raised once the number of prefixes start exceeding some percentage
> for the user to do something about it. If nothing happens and the limit
> reaches a configured threshold then the BGP session will be torn down.
> 
> - In the current draft there is no mechanism for the other end to know of
> the reason why the session went down in the first place. IF this is
> achieved then the admin at the other end can take some actions to alleviate
> the situation.
> 
> - Should  the BGP session be restarted after some configured Idle Timer
> expiration?
> 
> This can result in consistent route flappings which is highly undesirable.
> 
> - Should the BGP session be freezed until a manual Restart is given?
> 
> - Should there be counters for individual SAFI or should there be a
> consolidated one for the entire AFI?
> 
> We must have a mechanism wherein we can inform admin guys in the network
> leaking routes causing an overflow for us. This issue was brought up some
> time back in the list but i saw no apparent conclusion to the whole
> discussion ;-)
> 
> Is there any intention of introducing a new cease sub-code in the
> NOTIFICATION message which will inform both the parties of the reason why
> the session was brought down!
> 
> Regards,
> Manav
> 
> 
> 
> ----
> "When you are courting a nice girl an hour seems like a second. When you
> sit on a red-hot cinder a second seems like an hour. That's relativity."
> 
> -Albert Einstein, on relativity
> 
> 
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>