Re: [Idr] Fwd: New Version Notification for draft-spaghetti-idr-bgp-sendholdtimer-05.txt

Nick Hilliard <nick@foobar.org> Thu, 04 August 2022 10:51 UTC

Return-Path: <nick@foobar.org>
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 EB1A8C13CCCD for <idr@ietfa.amsl.com>; Thu, 4 Aug 2022 03:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-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 8BdoZIas62OQ for <idr@ietfa.amsl.com>; Thu, 4 Aug 2022 03:51:19 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89CA9C13CCCB for <idr@ietf.org>; Thu, 4 Aug 2022 03:51:17 -0700 (PDT)
Received: from cupcake.local (unknown [89.101.195.156]) by mail.netability.ie (Postfix) with ESMTPSA id 47F959CE9A; Thu, 4 Aug 2022 11:51:14 +0100 (IST)
To: "UTTARO, JAMES" <ju1738@att.com>
Cc: "idr@ietf. org" <idr@ietf.org>
References: <CAOj+MME7XnW7kDXL4muh4Qp1UvabQ9amUoU0Sn3h2axqKzswzA@mail.gmail.com> <77F3E1F0-486F-47DF-ABE4-EFDB9C2FB6D8@gmail.com> <CAOj+MMGR4f3eLEDZY++1m4Lpo9joG4L9OrWbeF6kREn-9a9onA@mail.gmail.com> <c6e44213-7667-0f67-71a4-634411cd102b@foobar.org> <CAOj+MMFajL6E42WCzC0ZqrfSBZjU-0B=ZzmtvCRPkuMzU8z5QA@mail.gmail.com> <Yun6e5jSb0OYZGAX@shrubbery.net> <CAOj+MMFRJr=cs+5DVOp72BVn_j3NgANwNftyj=jRbdsvPpg-wA@mail.gmail.com> <YurtQXcUaUWfgN5w@shrubbery.net> <CAOj+MMF_VqXYETXPZWpnfQRi9FuV5=wMS7G-df+QKRmXEwa6rQ@mail.gmail.com> <YutxvHezmcPbN45l@diehard.n-r-g.com> <MW4PR02MB739411EDDEAEA648B22B2B82C69F9@MW4PR02MB7394.namprd02.prod.outlook.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <2fb5e778-71e2-10b8-f0ae-07042bdbf7d1@foobar.org>
Date: Thu, 04 Aug 2022 11:51:12 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.56
MIME-Version: 1.0
In-Reply-To: <MW4PR02MB739411EDDEAEA648B22B2B82C69F9@MW4PR02MB7394.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/RjCT4QG1BBaNmvPr_Q3sY7OVPnI>
Subject: Re: [Idr] Fwd: New Version Notification for draft-spaghetti-idr-bgp-sendholdtimer-05.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 04 Aug 2022 10:51:22 -0000

UTTARO, JAMES wrote on 04/08/2022 10:57:
> [Jim U>] There have been multiple dual failures of route reflectors
> that have resulted very large outages. When both of the RRs servicing
> some subset of PEs are compromised it has been due to an event such
> as a bad actor PE spewing BGP message that RRs in a given cluster
> cannot handle, malformed update  etc.... In these cases adding
> tertiary etc. RRs will not address will not help. As there is no
> issue in the forwarding plane for these FOUs ( NH Viability )
> compromising thousands of customers by tearing down the their VPNs is
> not acceptable
yep, for sure there are situations where GR is a really sound technical 
idea.  In regard to Robert's concerns, RS's aren't necessarily included 
in that category.  If a network abruptly drops off an RS, this shouldn't 
affect reachability, even if it may affect other quality parameters 
(latency, etc).  The same can't be said of RRs.

Nick