Re: [Idr] I-D Action: draft-sas-idr-maxprefix-inbound-02.txt

heasley <> Mon, 26 April 2021 21:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3C53B3A30C3 for <>; Mon, 26 Apr 2021 14:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jJ5AlBIFa3yd for <>; Mon, 26 Apr 2021 14:26:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2792A3A30C1 for <>; Mon, 26 Apr 2021 14:26:11 -0700 (PDT)
Received: by (Postfix, from userid 7053) id C3A44243D53; Mon, 26 Apr 2021 21:26:10 +0000 (UTC)
Date: Mon, 26 Apr 2021 21:26:10 +0000
From: heasley <>
To: Gyan Mishra <>
Cc: Robert Raszuk <>, "idr@ietf. org" <>,,
Message-ID: <>
References: <> <> <YHhJTB51/joiz9Pg@snel> <> <YINENaRdV/> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
Archived-At: <>
Subject: Re: [Idr] I-D Action: draft-sas-idr-maxprefix-inbound-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Apr 2021 21:26:12 -0000

Sat, Apr 24, 2021 at 12:12:59AM -0400, Gyan Mishra:
> If you make them both the same then it does not help in troubleshooting the
> actual pre policy so has to be a much higher limit then post policy.
> Definitely separate pre and post limit.

The device could *log* (with rate-limit) and discard NLRI that exceed the
limit as in case S2 case A to assist in debugging.  An implementation
might help further by keeping a discard counter.  If S2 case A or B are
used, the limit could be adjusted without disrupting the session.

Unless your peer is so old that it does not support route-refresh, is there
really a value in a limit between pre and post policy?