Re: [IPv6] PvD (RFC 8801) is not relevant to MHMP

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 02 December 2022 20:32 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 625C3C14CEE1 for <ipv6@ietfa.amsl.com>; Fri, 2 Dec 2022 12:32:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=sandelman.ca
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 bdO18jLDo91n for <ipv6@ietfa.amsl.com>; Fri, 2 Dec 2022 12:32:41 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 24C09C14F722 for <ipv6@ietf.org>; Fri, 2 Dec 2022 12:32:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0A2581800F; Fri, 2 Dec 2022 15:58:53 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yK0i6fvUq-JV; Fri, 2 Dec 2022 15:58:52 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 57DA11800E; Fri, 2 Dec 2022 15:58:52 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1670014732; bh=i7CEIV4JMC2EzvlRI6HftCZd30h9/NWZZ41iGc3b6Kk=; h=From:To:Subject:In-Reply-To:References:Date:From; b=TUbJrv9GkbbcYIOeuKG7bz6+cr0WSNIWggbyVfXsxWvUKi7vHWAyv8nJbrovKUpGP 7BD4lQIzQBxTrqQI+qy/yZlE9c7cclj4dHZYmiQIpa4qLA4RJReCmFrs/0Qy9q+eAZ jKzWO2gMyFtsvy3VzLUWcW/jOrOrK30zsDDoViQaChKRP3F+jA0kwoXCw1hMdIxx7V Bzbl7KQOMOVEjfexD7fkQCAZkYw8wZ7U3FKuitUxch0N7iQCmWrEtQMjkq3Hg2vcyD Vk7jmU/JxHy9ybnZyAoqmQrWxi9FuC0pONbN5vUMCdjoppLligi86l9Fsy2zeqQXJe 4prtvjlf9gElg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DD9052D2; Fri, 2 Dec 2022 15:32:37 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>, "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <CAPt1N1kBNEzm1f2YmSLE5HY-eaRO6qemi5duyJyrqMAtGMTuCQ@mail.gmail.com>
References: <8e49314ba8304b54be88fc365987a97c@huawei.com> <15402.1669922453@localhost> <d51350ad-0d1d-c046-707f-5fa3ecd2813e@gmail.com> <29096.1669924918@localhost> <624493d2d8f84d8cafc6b84690ef4728@huawei.com> <CAPt1N1mRsjo21E=3662o+KhNha50DTWnANMa6m7ttqqROF+b=w@mail.gmail.com> <6cce7e2c-4108-c85c-2a34-2d2ac0f28b42@gmail.com> <CAPt1N1kBNEzm1f2YmSLE5HY-eaRO6qemi5duyJyrqMAtGMTuCQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 02 Dec 2022 15:32:37 -0500
Message-ID: <3051.1670013157@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RpZ7BpVg4toSTI9y3SKpM3t59l4>
Subject: Re: [IPv6] PvD (RFC 8801) is not relevant to MHMP
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, 02 Dec 2022 20:32:45 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > What we were talking about was a slightly different thing, though:
    > getaddrinfo() as defined in the POSIX world is synchronous and doesn't
    > have a way to specify a context for the lookup, so it handles
    > multi-home situations really poorly, just as an example.

Agreed.
But, it's not it's synchronous nature that's the root of the problem, which I
think you are agreeing with.

    > Fixing this
    > requires an API that's higher-level than the sockets API anyway. If we
    > want to describe that API, I think that's fine, but historically we've
    > gotten substantial pushback when we've tried.

    > We did actually at one
    > point try to define an MPvD API, but got a lot of pushback on it and
    > never finished the work. It's a pretty hard problem to do this well.

I'm not really convinced that the PvD work could ever succeed as it never
quite had the right people at the table.
I think that we would face the same problem today, but at least we have some
benefit of much more experience of these variety of proprietary interfaces.

I don't think that the IETF is the right place to do this work, btw.
But, we do need to be involved as a stakeholder and reviewer.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide