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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 26 November 2023 18:07 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 CC4F8C14CF1E for <ipv6@ietfa.amsl.com>; Sun, 26 Nov 2023 10:07:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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 (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 yu-n19HemLWV for <ipv6@ietfa.amsl.com>; Sun, 26 Nov 2023 10:07:44 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA4AFC151522 for <ipv6@ietf.org>; Sun, 26 Nov 2023 10:07:44 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [77.39.186.42]) by relay.sandelman.ca (Postfix) with ESMTPS id 146981F4A5; Sun, 26 Nov 2023 18:07:43 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="Z91os18x"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id BBDFDA0E9B; Sun, 26 Nov 2023 19:07:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1701022061; bh=LvFsUWRCA0UZuYJTttpC3z6XKWtSosE0sHQ8mbpnfcM=; h=From:To:Subject:In-reply-to:References:Date:From; b=Z91os18x8A8p61wScnbrUCjit0BxOV4YixeYg9NzZxTnABoeITXx9PLf80guhxjDT o8xLIbI+UEpCH81IP6YIDMWk3Z1f+sgCizss2rJevLAz6CuEKUegc9/XAqoF606dBe VDl6QKxcWSl5E87/qoyqp+z+DsH9S6JNOun4vH6KS667YCq/ty17ssTLFaaBDZRCXh nz0UP/B7KodsV9r5Q3ZMO1JgArh/QLHpBxgRA+LaOksjBVXOWJqLIjFHOIFBSPhyqo QwNNPuPsj4d3fT7HZM7MoV10crJtH7xchTpVBaUFDVShqilkXVykDtH41mvbvLSH0I diwHxLsxcgj+Q==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id B9A31A0E9A; Sun, 26 Nov 2023 19:07:41 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Kyle Rose <krose@krose.org>, 6man WG <ipv6@ietf.org>
In-reply-to: <CAJU8_nUO_TiSJ62vEmpHtRV5khkF0r4EfvxhzizFxJKjUzkhcQ@mail.gmail.com>
References: <CAJU8_nV2QoGjZoegcUSXELqgeqW6OheTt32qq6YQ5XV0g5MPQw@mail.gmail.com> <10D22CA5-CD7A-471A-B4A9-21B77D16F5F7@employees.org> <CAJU8_nVQFvp_5ZnkByCvBeA7wFz9J5FVAeud2CD1Xd4UkyL_3Q@mail.gmail.com> <4202668E-EEBE-4FA6-9801-F2A9FC92CBD8@tiesel.net> <CAO42Z2y9g3ebZ2VuXDFSK71p3X2VMVQu2=h+sXSVhcfvvxn-Qg@mail.gmail.com> <CACMsEX8q7dmRAVXuOZFVS+z_hrks=n0ChBHR4Bz9gB9ryF0ZAA@mail.gmail.com> <CAO42Z2yFiKs09K-O+SxDytLst_Uu4MAae65PTgz3URLnc5MnQw@mail.gmail.com> <CAE=N4xcFU+87wXy8NkHuO7rZ-T7Z7VmTkfcYFJH3PAJ+8+NPww@mail.gmail.com> <CAJU8_nWEAwzEw-2RpYxyf-i8x_0t8AS5O4GQ8=uB0GGYDFB5jA@mail.gmail.com> <a24c332c-e949-32cc-f660-a4434aab4eef@gmail.com> <CAJU8_nUmuxZc8USDTZPJ-nQ05K3joYcXgVsExZBo6GDioWW4mg@mail.gmail.com> <458732.1701012011@dyas> <CAJU8_nUO_TiSJ62vEmpHtRV5khkF0r4EfvxhzizFxJKjUzkhcQ@mail.gmail.com>
Comments: In-reply-to Kyle Rose <krose@krose.org> message dated "Sun, 26 Nov 2023 10:59:14 -0500."
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: Sun, 26 Nov 2023 19:07:41 +0100
Message-ID: <463252.1701022061@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hwZ3xSrojkIAxMFxO6PdIMQ4EfI>
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: Sun, 26 Nov 2023 18:07:50 -0000

Kyle Rose <krose@krose.org> wrote:
    >> But, you as an operator, would be deleting those announcements based
    >> upon your well configured BCP38.  So, it's really is entirely under
    >> your control, which I agree with you: is a better.
    >>

    > I am not referring to leaking routes, but to leaking rendezvous
    > information, i.e., DNS. In a world in which operators run recursive

Ah, thank you for the clarification!

    > resolvers that clients can be assumed to use when on your network, you
    > maybe can configure yours to drop all external address records
    > referring to ULA or 1918 space, but we're now in a world in which
    > privacy (via DoH/DoQ) and end-to-end integrity (via DNSSEC) have been
    > prioritized over operability, so you have to assume you won't have full
    > control over what DNS entries a client sees. This has implications for
    > the set of trade-offs involved in misconfigurations, especially when
    > the naive user blames you for something not working even when it's
    > mostly not under your control.

I completely agree, and it's one reason why I think split-horizon DNS is a
failed experiment.  Please use internal.example.com, and I really wish more
people would ask the ADD WG to make that the primary suggestion going
forward.  (The IETF has never before defined what split-horizon DNS is. It
goes back to Cheswick&Bellovin's _Firewalls_ book of ~1990, and perhaps before)

    > With border routers sending ICMP
    > unreachable rejections, working Happy Eyeballs would hopefully make
    > failover transparent, but "hopefully" is doing a lot of heavy lifting
    > in that expectation.

I think that HE is a very specific mechanism :-)
Trying all addresses and having ICMPs ought to be enough, even if it might be slower.

    > Anyway, I consider this an acceptable set of trade-offs, but there is a
    > discussion to be had about the implications that would benefit from the
    > experience of big-time operators who have run into a much broader set
    > of issues than I have.

We are in agreement here then.


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