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

heasley <heas@shrubbery.net> Mon, 26 April 2021 21:26 UTC

Return-Path: <heas@shrubbery.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C53B3A30C3 for <idr@ietfa.amsl.com>; Mon, 26 Apr 2021 14:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jJ5AlBIFa3yd for <idr@ietfa.amsl.com>; Mon, 26 Apr 2021 14:26:11 -0700 (PDT)
Received: from sea.shrubbery.net (sea.shrubbery.net [129.250.47.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2792A3A30C1 for <idr@ietf.org>; Mon, 26 Apr 2021 14:26:11 -0700 (PDT)
Received: by sea.shrubbery.net (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 <heas@shrubbery.net>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>, maelmans@juniper.net, max@stucchi.ch
Message-ID: <YIcv8m8AIWMt54QZ@shrubbery.net>
References: <161843563034.11054.13811966622190622752@ietfa.amsl.com> <CAOj+MMH=cCgtn7cL=HvOjQOMH1B9tmjOYOT04jXE9oky4SuevQ@mail.gmail.com> <YHhJTB51/joiz9Pg@snel> <CAOj+MMEFOGm=hCQcZNAUoN8vsPeVT3gqnjsQihUMJo4AOObZfw@mail.gmail.com> <YINENaRdV/EP4Wm9@shrubbery.net> <CAOj+MMGH8oLdtWje=X2b3WC5DF72X6TEYuU-x2Df-UtDPA21Ew@mail.gmail.com> <CABNhwV0BX1gu58WgHKE2w+_fGbMi4dOGURWSZai_aFfWN+qp_g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABNhwV0BX1gu58WgHKE2w+_fGbMi4dOGURWSZai_aFfWN+qp_g@mail.gmail.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
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: <https://mailarchive.ietf.org/arch/msg/idr/r_0MaP6g7JW5XqIO-4205RxNfRY>
Subject: Re: [Idr] I-D Action: draft-sas-idr-maxprefix-inbound-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=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?