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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 17 November 2023 14:26 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 E2F79C1519B6 for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2023 06:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 pP8kXpxI1gIe for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2023 06:26:08 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21CCEC1519B8 for <ipv6@ietf.org>; Fri, 17 Nov 2023 06:25:40 -0800 (PST)
Received: from dyas.sandelman.ca (dslb-002-202-003-214.002.202.pools.vodafone-ip.de [2.202.3.214]) by relay.sandelman.ca (Postfix) with ESMTPS id 4E2881F45B; Fri, 17 Nov 2023 14:25:39 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 588F4A1BD6; Fri, 17 Nov 2023 15:25:23 +0100 (CET)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 55ED3A1BCF; Fri, 17 Nov 2023 15:25:23 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ole Troan <otroan@employees.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>
In-reply-to: <8031DEBD-BC22-480E-91FF-8F9EC1EDC2A7@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>
Comments: In-reply-to Ole Troan <otroan@employees.org> message dated "Fri, 17 Nov 2023 08:11:17 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 17 Nov 2023 15:25:23 +0100
Message-ID: <4124157.1700231123@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1kBwSOYYoIEhMwbYLrHLTEZ1Md8>
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: Fri, 17 Nov 2023 14:26:09 -0000

Ole Troan <otroan@employees.org> wrote:
    >> To work well, we need some kind of system-wide _give me a socket to "name"_
    >> daemon, which does all the getaddrinfo() work, knows the list of
    >> (per-provider-domain) network addresses, and can cache all of that info.

    > I thought this idea had lots of promise:

    > https://datatracker.ietf.org/doc/html/draft-ubillos-name-based-sockets-03

That has some on-the-wire implications, as I read it.
There is also this effort:..damn... it was presented at RIPE last year, but I
can't find it.

It not that it is so hard to do, it's that it takes some perserverance to get
it upstreamed into all sorts of desktop OSs, embedded OSs, and to patch the
API into the dozens of tools that need it.

I think it's a 7-10 year duration effort, requiring 1/3 FTE.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*