Re: [IPv6] RFC 6724 shouldn't prefer partial reachability over reachability

Ole Troan <otroan@employees.org> Tue, 21 November 2023 11:45 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78ED0C151520 for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2023 03:45:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=employees.org
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 efJvkepxfrYv for <ipv6@ietfa.amsl.com>; Tue, 21 Nov 2023 03:45:39 -0800 (PST)
Received: from proxmox01.kjsl.com (proxmox01.kjsl.com [204.87.183.6]) (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 875CFC151096 for <ipv6@ietf.org>; Tue, 21 Nov 2023 03:45:39 -0800 (PST)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 0FDEBE53FE; Tue, 21 Nov 2023 11:45:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=employees.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:from:from:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=prox2023; bh=Z+95BT5/JTpKUU4A 111H9Umz7A33PYtPeDAJ/7hNltw=; b=ZxF2ahBonxghMoaN9wy/kBwyjVHo8uqW Ivp5FQOcCocyj4yILVHEklIc8E5aJcKzvOJwyygPrzhOsy8JeNG6XPcxvcAiZF+i 1zkbj8yeqzrSBfKt1+TGvKAT1QY48XtXjrGqjulo/sH87vXLK+ThW6b0APrAqM1k pTx9mRyS4qAHCtdIJFEyj1q0lyKSSsYrQKgh2eiCDoZqX/EoGVRUuDm+4l7QWUsa i3TGfXlPVBKGcNxfz2iyKSPSxMmS9Qi5b8iptfz5W1chAlhFJ2LGUER39ehBag8y j8Z/JReqtZEqVGLjTi6XeNhAmykf5OldhSGfknHUNbKdz4cVO7Amww==
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id E33FFE4002; Tue, 21 Nov 2023 11:45:38 +0000 (UTC)
Received: from smtpclient.apple (ti0389q160-4360.bb.online.no [82.164.52.60]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id E00DD4E11ADD; Tue, 21 Nov 2023 11:45:37 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CACMsEX9RiUDKWL+47GaxQ9Q36bBjMqiTgJ16Ob+5FPbGAxNozQ@mail.gmail.com>
Date: Tue, 21 Nov 2023 12:45:25 +0100
Cc: "Philipp S. Tiesel" <philipp@tiesel.net>, Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFDEB5DE-8C15-4A3E-B79D-C686925CF6A3@employees.org>
References: <CAKD1Yr2uD+XE+HA6vs3BfEchpWr5H2NEeoXLrXm7-U9_ckw1sA@mail.gmail.com> <CAN-Dau2Nw21wUm-mjxq3bnYczPJbApVhcZZ6oie+HiB4yvr_PQ@mail.gmail.com> <CAKD1Yr1z2x8iKXYQtPVifj-XkP7MeRq=NWe0gdWBGC1aS_j0Mg@mail.gmail.com> <CACMsEX8f_qmpZ898vKLy_56Jy1WKEju94fYEz5fuV4Pc3iJ=tw@mail.gmail.com> <CAKD1Yr1tZa0W=617hQrgYYqmUbfgFp7EhmvgqKzaBvF=r=5FuA@mail.gmail.com> <CAJU8_nUOjrO5FPPXTCNeA-9YuSPT7SmGkiM82DGiMacyfntV6w@mail.gmail.com> <CAN-Dau0FP31h3s+Fzbam7GJg-rNGsX3m8Hx3k=+895NT0a4iqw@mail.gmail.com> <CAPt1N1=_BmOZNvOc00qdhS84REnr-thBFgrjcixsEc=+jMSOfg@mail.gmail.com> <CAN-Dau1A4=5Q6mckZ35T_Gs1ty=zSAYUOS+1-nw1rAD2eH+o9w@mail.gmail.com> <CAO42Z2yU+uHDP-xi_D6tCA45UmSiCQ2bZSUe38edEWs5o_YCeg@mail.gmail.com> <CAKD1Yr2YW-ZeyooT6tzmjoE2WJAcUcohf2C6CMj3e41J8XaLvQ@mail.gmail.com> <4106220.1700174829@dyas> <8031DEBD-BC22-480E-91FF-8F9EC1EDC2A7@employees.org> <4124157.1700231123@dyas> <17E321B1-B65C-4761-96C1-D69598AB9D53@tiesel.net> <CACMsEX9RiUDKWL+47GaxQ9Q36bBjMqiTgJ16Ob+5FPbGAxNozQ@mail.gmail.com>
To: Nick Buraglio <buraglio@forwardingplane.net>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/g-IXfRvahdmF5GGyco-GdSAnYi4>
Subject: Re: [IPv6] RFC 6724 shouldn't prefer partial reachability over reachability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Nov 2023 11:45:43 -0000

> The more I think about it, the more I am thinking that it may be a deployable solution for multihoming, with all of the details in appropriate stages of hand waving.

The more I think about it, the less I think it is deployable.

MHMP:
- Rule 5.5 support in all hosts (which as Lorenzo alluded to is complicated)
- Application changes to handle failover
- No multi-homing policy available to the network
- Only works when hosts are directly connected to exit routers. _Any_ other topology requires routers to do SADR or SADR like behaviour

I don’t see any realistic way where MHMP can be made deployable.

I’d rather we focus on the multi-homing mechanisms that could work.

Cheers,
Ole