IETF Logo Mail Archive

Re: RFC6724-bis?

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 22 September 2022 16:54 UTC

Return-Path: <mcr@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 D463AC1522C4 for <ipv6@ietfa.amsl.com>; Thu, 22 Sep 2022 09:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 gyl1qCqErnif for <ipv6@ietfa.amsl.com>; Thu, 22 Sep 2022 09:54:53 -0700 (PDT)
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 399BAC14F744 for <ipv6@ietf.org>; Thu, 22 Sep 2022 09:54:52 -0700 (PDT)
Received: from dooku.sandelman.ca (dynamic-077-011-150-065.77.11.pool.telefonica.de [77.11.150.65]) by relay.sandelman.ca (Postfix) with ESMTPS id EE4EC1F4AF; Thu, 22 Sep 2022 16:54:50 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 643181A01CD; Thu, 22 Sep 2022 18:54:47 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Smith <markzzzsmith@gmail.com>, Ted Lemon <mellon@fugue.com>, 6man WG <ipv6@ietf.org>
Subject: Re: RFC6724-bis?
In-reply-to: <CAO42Z2xZ_-mDh66A9DK+3ieEqGMqW0Pt+mZzVOmzz4cDRUTEXA@mail.gmail.com>
References: <66892DC8-6DA4-4DC8-85B0-E1E1647CD9F7@gmail.com> <CAM5+tA9kttCKrZaoB7UzNdE6TU1qGNMaxDmWvFtRvpB4A8+WHA@mail.gmail.com> <8FE71499-D155-4853-A964-6617F6EA2069@gmail.com> <CAM5+tA9QuYxVs+NXBD3dAYr_Y=95bWt63WjmEMDOfegL0Z4otA@mail.gmail.com> <CAM5+tA_hg2sXXsYw6Tcx-ytRAMkKQcFw8a3N7SfEXwbuPm0LMw@mail.gmail.com> <00ea3b70-ba8e-b6ef-e1ce-fdd56828f506@gmail.com> <CAPt1N1=_9Rwj-HnUZKWfatARbHWptArmSAV-qdi8MKyoBf9R0A@mail.gmail.com> <CAO42Z2xZ_-mDh66A9DK+3ieEqGMqW0Pt+mZzVOmzz4cDRUTEXA@mail.gmail.com>
Comments: In-reply-to Mark Smith <markzzzsmith@gmail.com> message dated "Fri, 23 Sep 2022 01:00:01 +0930."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 22 Sep 2022 18:54:47 +0200
Message-ID: <371784.1663865687@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/23JnRr2GLVgMXnA1Y5TIWVo7wrM>
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, 22 Sep 2022 16:54:53 -0000

I think that Mark is really asking why we aren't doing happy eyeballs *in the
kernel*, (or at least, below the typical application interface).  Of course,
that requires new APIs that take a struct addrinfo, rather than a sockaddr.

The other thing that I wonder is why RAs announce a ::/0 route, when I rather
wonder if the router ought to know better about it's connectivity, should
really be advertising a route to 2000::/3.

I don't think this really solves the ULA vs IPv4 etc. issue, but I keep
thinking that it would make some of the dicussion clearer, but it would also
result in no route to host more clearly for all the other empty spaces.


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

v2.23.0 | Report a Bug | By Email