Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt

Michael Richardson <mcr@sandelman.ca> Tue, 06 July 2021 18:43 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 29CF73A3130 for <ipv6@ietfa.amsl.com>; Tue, 6 Jul 2021 11:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7lF1YltPoet for <ipv6@ietfa.amsl.com>; Tue, 6 Jul 2021 11:43:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BF663A312F for <ipv6@ietf.org>; Tue, 6 Jul 2021 11:43:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 203E4389CA; Tue, 6 Jul 2021 14:45:49 -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 S2ARpKTZtcKJ; Tue, 6 Jul 2021 14:45:46 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E9E50389C8; Tue, 6 Jul 2021 14:45:45 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1D4302B3; Tue, 6 Jul 2021 14:43:17 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Jared Mauch <jared@puck.nether.net>
cc: Andrew Cady <andy@cryptonomic.net>, 6MAN WG <ipv6@ietf.org>
Subject: Re: I-D Action: draft-carpenter-6man-rfc6874bis-00.txt
In-Reply-To: <4361E676-A90C-49C0-8191-EC0358715D57@puck.nether.net>
References: <162545101341.19246.8566193740265797873@ietfa.amsl.com> <95a7dbe5-e0a3-4676-9dcc-005ff53725e0@gmail.com> <CA+9kkMD3iSgo-KMM5Ed8bVnVCu_G3f2kB6zHKoOx2ta=x8QucA@mail.gmail.com> <CANMZLAbmdWHDRBPpHgy_e4_0-WUVW2gjnbXWwu2pF_xi-S0vWQ@mail.gmail.com> <87a6n13y0j.fsf@ungleich.ch> <CA+9kkMBx4F0FGZasdk11ogyCOwQZecAEkO4JbECDr4osySN-4w@mail.gmail.com> <20210706152527.j47rcxas5nwz5d63@zukertort.childrenofmay.org> <CA+9kkMDGQxFD6v=NJaDXRdRJ3jaRriTnhnyKeK3cG=jaosQhBQ@mail.gmail.com> <20210706161859.2wdw7mkeg4b7nd66@zukertort.childrenofmay.org> <28125.1625590441@localhost> <4361E676-A90C-49C0-8191-EC0358715D57@puck.nether.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Tue, 06 Jul 2021 14:43:17 -0400
Message-ID: <24399.1625596997@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OsPiIdvQau1t_IJhtrf1aHxTFgo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Jul 2021 18:43:28 -0000

Jared Mauch <jared@puck.nether.net> wrote:
    >> On Jul 6, 2021, at 12:54 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    >>
    >> You can argue forever that they are wrong, and yet, here we are, ten years
    >> later, without anything working.

    > I have a general concern here that this is why network equipment that
    > comes with a default IP address will continue to live on in IPv4 land,
    > and may never see IPv6 configuration as a result.  I’m sure someone
    > will suggest using mDNS to go to https://myrouter.local/ or similar,
    > but the complexity introduced by link-local here is unlikely to see
    > significant changes as a result on either side, we are in a classic
    > standoff situation.

    > I hate to say it but mDNS is likely the way to go for many things, but
    > you may not be able to tell the difference between raspberrypi.local vs
    > raspberrypi-2.local which can often be a challenge.

And no HTTPS.