IETF Logo Mail Archive

Re: Next steps for rfc6874bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 August 2021 21:30 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 5B5BB3A19EB for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uE8-5f5uWcCy for <ipv6@ietfa.amsl.com>; Thu, 12 Aug 2021 14:30:57 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A358F3A19E7 for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:30:57 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id a8so12056529pjk.4 for <ipv6@ietf.org>; Thu, 12 Aug 2021 14:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=7zX1elllshIS9jg8m+W1okD1hv/14E1RUbwU1F20gNI=; b=VQNbXbYQSoI11GxWLSpXRc7ONlbU+sblWW/JJwwHkksPhZZ/WwWVg10BtYZHICwmhz 7U6NPv8Sb8VZNzD+DrMQUYhXRoHTRdyre8EyV7OaDIazKJW/ILQLUX+HguLmbi6zncZ2 2gN+J7wbTyLySQqJbqb+u9oHozCgnYKYv5kR4Y4xg4BIigTB2j7ROHNIP67v29S3dq/B /qbm4ZYwUv8Ne3ffRPx4uQMNEalVXIGOz+gkfXCj7SZkhp91xjdwOCV9mrjBkot/9A6l OsdA0f+VXfIW4p2gkx/RBoeno1RNPUdIQdAdFqwnyheLeybKObzlLl1H3OIsL5HsFFwN GyAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=7zX1elllshIS9jg8m+W1okD1hv/14E1RUbwU1F20gNI=; b=q7jrrxvXBRLCVWA5+96NrB1WspHRb/fhaENngKfHMPeqipWJggU/uo5zXyLLpFMW+q l5vjm3OauoLggr13Gq6NLPf8k+PpxHnx9QLmgb5zUW6CHUGouv5DB8kxYWZmUTrksj+c xtDkWkij1d/FXBXBP8lRhPAc+l7i0ZOxnKSOiQXGvHGhyHfMm1jjQhcRLOFdRXx5sYVb Hox20m+ULyZoDU9ATliCAKJuOg4127/xHKbvOS9x840qfBbje9437OJtPQOpie+1Gizr c61TRECJAgon3mLvrbqMfCsGVpGpb1u1HaMuC4IxfkkjeVIxAS3/iwW5H3yr96zTKkzW o4mg==
X-Gm-Message-State: AOAM532G7O0Dbj/7T4y13Ude5wwkhGuh4Dr8XDs04yrgDlurBAzP3uu8 7I2QIy8C3m86b00il6FtiS+k7A1E9r46hw==
X-Google-Smtp-Source: ABdhPJw6ypm2eYu+ZEu6o6GcJneleJat18mJTjd4QCAgPXDZ2MCo4OOxaRipD4rccvta5zEFva5UFA==
X-Received: by 2002:a17:902:8207:b029:12c:cf1b:340f with SMTP id x7-20020a1709028207b029012ccf1b340fmr5181502pln.8.1628803855833; Thu, 12 Aug 2021 14:30:55 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id w9sm3796597pja.16.2021.08.12.14.30.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Aug 2021 14:30:55 -0700 (PDT)
Subject: Re: Next steps for rfc6874bis
To: Michael Richardson <mcr+ietf@sandelman.ca>, Mark Smith <markzzzsmith@gmail.com>, Kerry Lynn <kerlyn=40ieee.org@dmarc.ietf.org>, 6man <ipv6@ietf.org>
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> <18299.1628796893@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e0b6e664-9ad0-0303-cc41-7e09e8848058@gmail.com>
Date: Fri, 13 Aug 2021 09:30:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <18299.1628796893@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Tfrv6SB02SRwZszF6TZ7plkXymc>
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 21:30:59 -0000

On 13-Aug-21 07:34, Michael Richardson wrote:
> 
> 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.

That seems like a red herring to me, as far as the current draft is
concerned. (But then, I use a frozen-in-time Firefox version with all
search options switched off.)

   Brian

v2.23.0 | Report a Bug | By Email