Re: [Idr] Bug in RFC 7911 (add-paths) and tie-breaking

Nick Hilliard <nick@foobar.org> Sat, 26 June 2021 17:53 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 50C8E3A1EC2; Sat, 26 Jun 2021 10:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.238
X-Spam-Level:
X-Spam-Status: No, score=-2.238 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.338, 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 75JjCAz3athi; Sat, 26 Jun 2021 10:53:44 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4198C3A1EC0; Sat, 26 Jun 2021 10:53:43 -0700 (PDT)
X-Envelope-To: idr@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 15QHrcPO059355 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jun 2021 18:53:39 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Cc: "idr@ietf. org" <idr@ietf.org>
References: <F689CF63-236D-401D-9C8E-AC1C39CDE772@juniper.net> <20210626144948.GD14665@pfrc.org> <395B392F-DB11-4363-8459-B817EA7C0647@juniper.net>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <13414c73-d458-d63b-7703-0c6f5ed38608@foobar.org>
Date: Sat, 26 Jun 2021 18:53:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.48
MIME-Version: 1.0
In-Reply-To: <395B392F-DB11-4363-8459-B817EA7C0647@juniper.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WlTGqV-WdwNq3NelKDH8u9FaQLQ>
Subject: Re: [Idr] Bug in RFC 7911 (add-paths) and tie-breaking
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: Sat, 26 Jun 2021 17:53:47 -0000

John Scudder wrote on 26/06/2021 16:13:
> The point of the path-id tie-break, if we did it, would be to make
> the outcome fully specified in all cases, even those missed by
> fast-conn-restore.
^^^^ that.  It's operationally important to have an option to have 
deterministic routing.

Nick