IETF Logo Mail Archive

Re: Next steps for rfc6874bis

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 12 August 2021 19:35 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 C05043A476B for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 12:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 qz_Lz_UIFVgg for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 12:35:04 -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 62E783A4763 for <ipv6@ietf.org>; Thu, 12 Aug 2021 12:35:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 98095389A9; Thu, 12 Aug 2021 15:39:45 -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 FqY26SodO9I9; Thu, 12 Aug 2021 15:39:39 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6F31238996; Thu, 12 Aug 2021 15:39:39 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C4C60A0; Thu, 12 Aug 2021 15:34:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Smith <markzzzsmith@gmail.com>, Kerry Lynn <kerlyn=40ieee.org@dmarc.ietf.org>, 6man <ipv6@ietf.org>
Subject: Re: Next steps for rfc6874bis
In-Reply-To: <CAO42Z2z05rVv8eEEjxzW+QN1fwonr1hovhVY1sYhRZuj+FjtXQ@mail.gmail.com>
References: <667b9ebb-3c99-8c5b-fa57-796e5bb84b4c@gmail.com> <3269d750-2e97-9bb2-550a-94b652d689a4@foobar.org> <1ea4c0e5-fd7c-c39a-28a6-681f6c40af8c@gmail.com> <27470.1628692112@localhost> <406d13b3-4b30-1a1a-5cd7-27a36157a3ea@gmail.com> <31519.1628777761@localhost> <CABOxzu0k9siJ_JuERi9COgt966iP4Xe3Yq=AcpXOFL14qSW3UQ@mail.gmail.com> <CAO42Z2z05rVv8eEEjxzW+QN1fwonr1hovhVY1sYhRZuj+FjtXQ@mail.gmail.com>
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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 12 Aug 2021 15:34:53 -0400
Message-ID: <18299.1628796893@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zd70zhyqQXX2BBVPLTEWyzmAKAE>
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: Thu, 12 Aug 2021 19:35:10 -0000

Mark Smith <markzzzsmith@gmail.com> wrote:
    > Non-technical end users shouldn't be exposed or have to even enter IPv6
    > addresses, including link-locals. While convenient to be able to enter
    > them into a URL field in a browser, it shouldn't be a common thing to
    > do.

USers also want a pony.

    > For user friendly end user access to device web GUIs over link-local
    > addresses, the devices announcing themselves via MDNS would be better.
    > I have a laser printer that already uses MDNS to announce its IPv6
    > address.

When that doesn't work, and a technical support person arrives to debug the
situation,  they are going to put an IPv6 LL in in order to determine what's
up.

    > For technical users who need to enter link-local addresses and
    > interface/zone IDs, having a technical dialog box, with separate IPv6
    > address and interface/zone ID fields, hidden away under more technical
    > menu options (like Firefox's "More Tools" menu) should be adequate to
    > resolve this thread's issue by avoiding it.

I agree: It doesn't even have to be the Location bar.
They could be some special box that is opened up, that can't do search.

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

v2.23.0 | Report a Bug | By Email