Re: [IPv6] Multi6 (no longer RFC 6724 shouldn't prefer partial reachability over reachability)

Nick Buraglio <buraglio@forwardingplane.net> Fri, 24 November 2023 21:18 UTC

Return-Path: <buraglio@forwardingplane.net>
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 E1736C14F6EC for <ipv6@ietfa.amsl.com>; Fri, 24 Nov 2023 13:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=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, 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 (1024-bit key) header.d=forwardingplane.net
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 Nb4irQiZ1P8i for <ipv6@ietfa.amsl.com>; Fri, 24 Nov 2023 13:18:33 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 CB9D7C14F739 for <ipv6@ietf.org>; Fri, 24 Nov 2023 13:18:33 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-4237346c6efso11751311cf.0 for <ipv6@ietf.org>; Fri, 24 Nov 2023 13:18:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1700860713; x=1701465513; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=l6BCf0peeZMVscmEO4oVgk2kV9njdZptsqgnTBRdmbs=; b=izCdIiSBTuGlEgUF6rjiBYI2Wzhx1B3fonieiuVfzb+BdOELjFXLWXKKkQVdPY1Jna 8SSSdddj5eae+q+pAMsVII27IA3CPnQ09HA+3XrErsuWTImjS0CDGnqCi6UM3HRbf/HP 16QNmqT9tv5mPdXc9oDlHhqqPhFx7t5cd/3r4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700860713; x=1701465513; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=l6BCf0peeZMVscmEO4oVgk2kV9njdZptsqgnTBRdmbs=; b=wvRT25OBIJ1fBJ+AMwnUJCQjQkhiYAfJtqnCV0XFc98ZcCeVR/LGY8NDb08U0DLlgM vr/yiCdY97EuZd+wu8RvJAQHhvmoa7vI3GZcN4BLuCgsmNDSnD3eJ5lF0rePRXo/zcq+ A2D/mF3QcMghDcOiWo7qQRR2lDVNlZUAW/Ugsnsw8z4FUL79jZpKJEu4p0s66XI6SjcR LUjw76lqmllmaPeu2+/MYVw9ljX1pEpdswdbeblGmN9DyFCelGn8ty0JUZPCahJP8r5y 4IXKf5PItOQdmB/eEulyXjKjqztzcWqlpsMWUx7Qkxdeq8Cp9gzc16MqoFFXRlI8X1Go f81w==
X-Gm-Message-State: AOJu0YzNEy+kR5sBcmuue3mtm5cw3f9Okv0ophgkiLGi767hNQRl0e+J vmB8d3uWnT2BrRqp2Z278qN9Hbj0VspwHEAYJOkPdB+zUdEYnNA8Xf4=
X-Google-Smtp-Source: AGHT+IEfyqZ45XVEP7e31OD/BDt1xfdokj953AOfov30bwMkbUgdRTMp9bqqnPbbCPgeHLXQsaEHF4YTWn1cSnkp9Zg=
X-Received: by 2002:ac8:7f14:0:b0:423:90d9:5bd5 with SMTP id f20-20020ac87f14000000b0042390d95bd5mr5686548qtk.8.1700860712843; Fri, 24 Nov 2023 13:18:32 -0800 (PST)
MIME-Version: 1.0
References: <CAPt1N1kjd+m3KL-KCQY=2DWZrug=g8_zdtacF9Aja7dQ9zjnUQ@mail.gmail.com> <1BA9C21A-8EDC-4E69-8749-3C703CAB678B@employees.org> <CAPt1N1kFQpkkVNtk57_T3FTnVKhtqgm9Z6VGJDzOXo4KJvccSA@mail.gmail.com> <94FC0A0F-AD2C-4630-B509-2DAE57205B50@employees.org> <CAPt1N1mPNYBfM-RBGULo+mAf4cSqr5=4GsdAeL3_C5YyWNsSAA@mail.gmail.com> <e75aa1ac-b7c0-a9c4-7577-45a213afaff8@gmail.com>
In-Reply-To: <e75aa1ac-b7c0-a9c4-7577-45a213afaff8@gmail.com>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Fri, 24 Nov 2023 15:18:21 -0600
Message-ID: <CACMsEX_MSd6fMqmcHxOM+Gs6r==tAPjZUO1XY_=_Ejd7TQg8-w@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009a1024060aec7e05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eShigFP2z0qn30DJrjVnIYIvkk4>
Subject: Re: [IPv6] Multi6 (no longer 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: Fri, 24 Nov 2023 21:18:38 -0000

On Tue, Nov 21, 2023 at 9:58 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 22-Nov-23 03:38, Ted Lemon wrote:
> > Well, e.g. in a stub network with DHCPv6 PD, if the customer site is
> multi-homed for resiliency, it would be nice if that worked. This would
> require the device on the stub network to try both source prefixes, so it
> probably doesn’t work at the moment, but we are talking about what remains
> to do to make it work.
>
> I'm now deeply certain that getting rid of getaddrinfo() as the basic tool
> for address selection is essential to make it work. Trying all possible
> {source, destination} pairs is necessary.
>

The deeper we go here the more evident this is to me, too. getaddrinfo()
feels like the limit to almost all of the issues we've been discussing.


>
>     Brian
>
>
> > It’s not clear to me that this is the killer app, or even the right
> approach, but I don’t see the problem that you do with exploring this: my
> motivation certainly isn’t to avoid paying for enterprise-grade routers
> other than in the sense that clearly they wouldn’t make economic sense in
> this application.
> >
> > I do realize that if we made this work in the home, it would have
> implications for the enterprise market in the long run, but that’s a path
> we’ve all trod many times before, and I don’t think we should factor that
> concern into our evaluation of what the right approach to the problem is.
> >
> > Op di 21 nov 2023 om 09:23 schreef Ole Troan <otroan@employees.org
> <mailto:otroan@employees.org>>
> >
> >      > Remember that my target market is end users, not enterprise. What
> sort of routers can an end user buy that will automatically do what you
> suggest?
> >
> >
> >     What sort of host and applications can an end user buy that supports
> MPMH?
> >
> >     O.
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>