IETF Logo Mail Archive

Re: [Sidrops] Andrew Alston's Discuss on draft-ietf-sidrops-rov-no-rr-06: (with DISCUSS)

Randy Bush <randy@psg.com> Fri, 26 August 2022 20:19 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD0BC14F72A; Fri, 26 Aug 2022 13:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vc4ybkfmiCZX; Fri, 26 Aug 2022 13:19:47 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C040CC14F719; Fri, 26 Aug 2022 13:19:47 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from <randy@psg.com>) id 1oRfns-0005yH-VO; Fri, 26 Aug 2022 20:19:45 +0000
Date: Fri, 26 Aug 2022 13:19:44 -0700
Message-ID: <m2a67qlpun.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andrew Alston - IETF <andrew-ietf@liquid.tech>
Cc: The IESG <iesg@ietf.org>, draft-ietf-sidrops-rov-no-rr@ietf.org, SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <AM7PR03MB645132A6E8E833013C988573EE759@AM7PR03MB6451.eurprd03.prod.outlook.com>
References: <166143374280.8949.4490792736652212362@ietfa.amsl.com> <m2bks8mbeu.wl-randy@psg.com> <AM7PR03MB645132A6E8E833013C988573EE759@AM7PR03MB6451.eurprd03.prod.outlook.com>
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/sidrops/B8yiReGQcxLvC6HfW7120JuWrI0>
Subject: Re: [Sidrops] Andrew Alston's Discuss on draft-ietf-sidrops-rov-no-rr-06: (with DISCUSS)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2022 20:19:48 -0000

andrew:

hack suggested by a friend now in rev-07

   If the BGP speaker's equipment has insufficient resources to support
   either of the two proposed options (keeping a full AdjRibIn or at
   least the dropped routes), the equipment should either be replaced
   with capable equipment or not use ROV.  I.e.  the configuration
   setting in Section 4 should only be used in very well known and
   controlled circumstances.  Such circumstances could include
   operational work-arounds such as the informed consent of the affected
   peers.

randy

v2.23.0 | Report a Bug | By Email