IETF Logo Mail Archive

Re: [Idr] Fwd: I-D Action: draft-sas-idr-maxprefix-outbound-00.txt

Randy Bush <randy@psg.com> Wed, 07 October 2020 14:00 UTC

Return-Path: <randy@psg.com>
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 5E30E3A08FF for <idr@ietfa.amsl.com>; Wed, 7 Oct 2020 07:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 WCSgBe2trC_i for <idr@ietfa.amsl.com>; Wed, 7 Oct 2020 07:00:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0969E3A08EB for <idr@ietf.org>; Wed, 7 Oct 2020 07:00:49 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1kQ9zp-0001KG-By; Wed, 07 Oct 2020 14:00:45 +0000
Date: Wed, 07 Oct 2020 07:00:44 -0700
Message-ID: <m2zh4yb0fn.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ben Maddison <benm@workonline.africa>
Cc: Warren Kumari <warren@kumari.net>, idr <idr@ietf.org>
In-Reply-To: <20201007075148.em5nenss2zm4pfyl@benm-laptop>
References: <160147241917.18722.10402627847451321205@ietfa.amsl.com> <CALxNLBj0Y6yLa963_6zGgiLJNyhGikRrDMB4ySSVUD3T-o6nog@mail.gmail.com> <CABNhwV2isC3o2h2nr45RTnMhRRrDe1nuyyrj9z611_rOYEL_Eg@mail.gmail.com> <CAHw9_iLRX9sYOw+Tyb9PO0_N6ZHqmW8B+SkOArXyY12qOEXqww@mail.gmail.com> <20201007075148.em5nenss2zm4pfyl@benm-laptop>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/tL73xCgyPVLOmElusNZoEBD-Mk0>
Subject: Re: [Idr] Fwd: I-D Action: draft-sas-idr-maxprefix-outbound-00.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: Wed, 07 Oct 2020 14:00:51 -0000

> I'm with Warren on this.
> If the log that the warning level generates goes unnoticed, then it's highly
> likely that whatever byzantine forwarding issue the "clipping" creates
> will do so too, and possibly persist for a long time.
> 
> I wouldn't want to be the on-call engineer in the middle of the night
> that has to make the logical leap from a ticket that says "we're seeing
> a weird-looking traceroute ..." to "we have half-tripped someone else's
> max-prefix limit".
> 
> Additionally there is also no guarantee that in the event of a leak the
> "leaked" prefixes are the ones that are "clipped". It's just as likely
> that you end up with the worst case scenario of causing an outage for
> the legit prefixes *and* allowing the leak to persist!

consider me horrified.  this is a disaster that will not wait long
to happen.

[ i would have thought this obvious, but decided that saying nothing
  might be unwise.  sorry for the mailbox clutter. ]

randy

v2.31.3 | Report a Bug | By Email | System Status