Re: [IPv6] draft-buraglio-6man-rfc6724-update revision

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 10 August 2023 16:10 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 00C41C14CE51 for <ipv6@ietfa.amsl.com>; Thu, 10 Aug 2023 09:10:16 -0700 (PDT)
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, RCVD_IN_DNSWL_BLOCKED=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=unavailable 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 zvqHr67ouonb for <ipv6@ietfa.amsl.com>; Thu, 10 Aug 2023 09:10:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 0B19EC14CE46 for <ipv6@ietf.org>; Thu, 10 Aug 2023 09:10:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9578B3898C; Thu, 10 Aug 2023 12:10:09 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gRO9JQH4GeSE; Thu, 10 Aug 2023 12:10:08 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id BA6383898B; Thu, 10 Aug 2023 12:10:08 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1691683808; bh=ts93Bg+DcGLScJEgskJhgiYjST2qCikoZcvlu0dPmr0=; h=From:To:Subject:In-Reply-To:References:Date:From; b=h/B+++jt4BIEFyt2Gr0QGWeqc0bPre7ChHrgihZoGZB321qfXMOcNtCf3vZDMUYAM mpzf+RKgs6XU3HPsNwfX3jsUYWKUIDi6s5Z1Tj4ikgg/3sjbVI+noXUPKObKjEJEuQ f4QM082Hwl9zz/kurNVz+6SeN1zsE25uPhFF29NW5u/sb0riqb6F/A5ab+n7G/lJrh hs1OqkWx7660RrgUDBrtPQImi/ywsFKJXlTcg0sXFvOoCJ9n2FnvrEZpHd6TWbxAri klskqggPu2GRZc/SG2SgWkJIhz1rC/lsvwRIi2OBrJgKbUCIVIGpnbTCo9TSpZ/A7i CZjKNNNlQDiJA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B2136238; Thu, 10 Aug 2023 12:10:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>
In-Reply-To: <CO1PR11MB48819BDAC458B59F4E73D4E0D813A@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <a87158b1-a9c1-18a8-569e-d2802af8c753@gmail.com> <4822475B-7BF4-4562-B414-F7CB95EF1520@employees.org> <4a5834a3-daf8-a709-7a75-41aa5b8a8567@gmail.com> <CO1PR11MB48819BDAC458B59F4E73D4E0D813A@CO1PR11MB4881.namprd11.prod.outlook.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: Thu, 10 Aug 2023 12:10:08 -0400
Message-ID: <22421.1691683808@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qEuqiYQj0HVpJDFPULkuk00x3eE>
Subject: Re: [IPv6] draft-buraglio-6man-rfc6724-update revision
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: Thu, 10 Aug 2023 16:10:16 -0000

Pascal Thubert \(pthubert\) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
    > 1) Best Source / Destination address pair: can we choose the
    > destination address independently of the source (and of the route
    > ????), or do we need a global optimization?

No. And even if we could find the global optimum, devices will move and
networks will change, and we'll need to do it again.

Can we reboot SHIM6?
Can we do it with LISP instead?
QUIC.  I remember that SPUD BOF.

But, if we could publish a short RFC (is it a BCP?) that would help move one
step forward, then we should do that.    Will Apple, MS, Google and Ubuntu implement?

    > (assuming God's view): if we knew everything about which source address
    > can reach which destination address (but nothing about routing there
    > though) which pair would we pick?

We would rotate the shield frequencies so the BORG don't catch us :-)

    > and "happy eyeballs" compare / collaborate? Which responsibilities for
    > each?  4) Multihoming and SAS: Should the stack be aware of
    > multihoming? Should it do something like a RHx / tunnel to the
    > appropriate CE based on source selection?

Something in the stack need to know about multihoming, and it needs a OS-wide
view, and we need new "socket" APIs.  There was a talk two RIPEs ago about
efforts there.

    > I'll kick the thread off;

Actually, I think we need a virtual interim (design) meeting.

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