Re: [IPv6] Fwd: I-D Action: draft-carpenter-6man-zone-ui-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 15 February 2024 19:42 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 20E23C14F698 for <ipv6@ietfa.amsl.com>; Thu, 15 Feb 2024 11:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Level:
X-Spam-Status: No, score=-7.196 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.091, 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, 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=gmail.com
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 aFF1BPdIgTdz for <ipv6@ietfa.amsl.com>; Thu, 15 Feb 2024 11:42:35 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 29963C14F5F8 for <ipv6@ietf.org>; Thu, 15 Feb 2024 11:42:35 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-1d911c2103aso8549435ad.0 for <ipv6@ietf.org>; Thu, 15 Feb 2024 11:42:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708026154; x=1708630954; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=EF7xnFF2Ve0k14lj/WA2SkE0gaq4EcstnIzEl7oTvVI=; b=jIX62Psy/WPTeOW/GZcsgGu2+Soj1fhAlIqiFJdpbzh9ozXqbiGCDRil9UVA3XJsf1 OKFDpLC38r2gClpH/GL0P0IMohyyJ4yyQ6ijg08a5v++l2S0ndzwKwlVjGGih3TXzbzV x91cyukordXvJQeN5kIVEL80q0OIh8ahtNBhj0XcpNKkey0GxEbbarB0ScTC+O5LGyCT st0Vikq6qUeI+wOMtLVlDXgb9LllgnAu2dVXGDK1u6fNSiZSMsYQtTZXfl1TAVkL1M38 dHYK/rceorrGezGjeyDWboCxXPdwy65dJPt5e4JYtgACfrQ0pAAJz2TiX3ceZJABq558 A9hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708026154; x=1708630954; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EF7xnFF2Ve0k14lj/WA2SkE0gaq4EcstnIzEl7oTvVI=; b=jyRHDNOY5z3NONr3LteWpSQacLZGLLCubzcO9uh2J55V0IiVsIyS5dels+dMfOFK2M njh6UsmxgzwEUWre46g3Mq1e/Y2+e9bcbVTJb6niCwPKdOhhojuqlulobAgHc0OVZchb KImwA6xxV/61ZwNMO7ziLg04NXj/Z/JhZlD3jzm8d7FEx34VQLkBNhraluTrmYatkhke IrTkp1C2MnduoSCXcZ48XzYbTldlPJrp1JL8LUvDtl2t8iQ8UBF1bkNpovh67SxJnxMr K5PtzwoNVgZmNCx3PupKpe61EKqNDJmeSbXAwGNYRFEC+clhAlfs5jKfK9LYxHBqP3k6 FIpg==
X-Forwarded-Encrypted: i=1; AJvYcCVT7jwtk2UJ8ykQCx4Sw+KQp1POX3Bm36B2DsOc89B4bYofpaVG7rOVn0Mv1vz5yQXn28yrDRApUsHEQAfU
X-Gm-Message-State: AOJu0YwqD1j1D1dx/ckRhQ8c5QrdweX5UupnILuaX++9RdIRx1TXfyA7 bL4pZzQKVTogSFrSZgHJUNckXEDiwyLayYQN+9xPLUeDPisKy7ro
X-Google-Smtp-Source: AGHT+IHUxpQ3rQ86I44r6xKxMwzrDGAqnpPwWf1sN5zMwh20DIC1mr9/giX7Tvd+1YVKGIQUagu27Q==
X-Received: by 2002:a17:902:e884:b0:1db:a376:4566 with SMTP id w4-20020a170902e88400b001dba3764566mr387868plg.15.1708026154301; Thu, 15 Feb 2024 11:42:34 -0800 (PST)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id t4-20020a170902a5c400b001da1ecb05f9sm1613998plq.240.2024.02.15.11.42.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Feb 2024 11:42:33 -0800 (PST)
Message-ID: <48f81e14-1a8a-888d-43c8-db54de2f94fc@gmail.com>
Date: Fri, 16 Feb 2024 08:42:30 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, 6man <ipv6@ietf.org>
References: <170534827865.59933.11111230460163352539@ietfa.amsl.com> <2767dad8-0b85-16c6-0dfb-124a2c977675@gmail.com> <CABNhwV1jQD5pizF_9H3n7n+hU=rFDs_Qx7yw8OCyT1hEF2H6ng@mail.gmail.com> <5561c863-179a-8de8-5e15-7509f818550f@gmail.com> <8AB5A2E9-D893-4551-9291-9F2EB28D7908@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <8AB5A2E9-D893-4551-9291-9F2EB28D7908@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/2VAsYNTlVi_6dlOiOYYRkBHAJmw>
Subject: Re: [IPv6] Fwd: I-D Action: draft-carpenter-6man-zone-ui-00.txt
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, 15 Feb 2024 19:42:39 -0000

Éric,

Thanks. With your AD hat partially on, do you think that an Informational document can request the IESG to obsolete a Proposed Standard?

If so, I'd personally be happy to make this draft informational and change the RFC2119 keywords to plain English. That would clarify that it is, as David Schinazi says, aspirational.

Regards
    Brian

On 15-Feb-24 22:15, Eric Vyncke (evyncke) wrote:
> [Top posting and without any special hat]
> 
> Brian and Bob, this is a good idea to move forward and keep this valuable feature of IPv6: LLA
> 
> Like David S, I do not think that this is the IETF remit to specify UI though, i.e., an informational document seems more adequate to me (again as individual).
> 
> BTW, I often enter URLs without a keyboard with 1- or 2-dimension QR code. Should this be part of the I-D as well ? (more complex than having 2 boxes to enter data) as QR codes are often printed on stickers on IoT devices
> 
> Just my 0,01 EUR
> 
> -éric
> 
> 
> On 12/02/2024, 23:15, "ipv6 on behalf of Brian E Carpenter" <ipv6-bounces@ietf.org <mailto:ipv6-bounces@ietf.org> on behalf of brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
> 
> Were there any other comments on this draft? Are there people who disagree with this new approach? If not, is it appropriate to consider WG adoption already?
> 
> 
> Regards
> Brian Carpenter
> 
> 
> On 26-Jan-24 14:01, Gyan Mishra wrote:
>>
>> I read the draft and it looks good and makes sense.
>>
>> Thanks
>>
>>
>>
>>
>> <http://www.verizon.com/> <http://www.verizon.com/&gt;>
>>
>> *Gyan Mishra*
>>
>> /Network Solutions A//rchitect /
>>
>> /Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> <mailto:gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>>//
>> /
>>
>> /M 301 502-1347
>>
>> /
>>
>>
>>
>>
>> On Mon, Jan 15, 2024 at 2:58 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com> <mailto:brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>> wrote:
>>
>> Hi,
>>
>> As the WG may have noticed, draft-ietf-6man-rfc6874bis has been stuck in the IESG since March 2023, despite multiple revisions and discussions with the ADs and other objectors, particularly those in the W3C and browser (WHATWG**) communities.
>>
>> We (Brian and Bob) have reluctantly concluded that the disconnects on this topic between the IETF, the W3C and WHATWG are such that an acceptable compromise cannot be reached.
>>
>> We therefore propose to transform the discussion by withdrawing rfc6874bis and RFC6874, and replacing them by a generic requirement that when a user interface supports the input of IPv6 addresses, it MUST support the input of link-local addresses with interface IDs (a.k.a. zone IDs). How any particular software tool does this is a choice for its implementer.
>>
>> A first draft has just been submitted, please comment. It intentionally makes no reference whatever to browser or other web issues.
>>
>> Regards
>> Brian Carpenter
>> Bob Hinden
>>
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-carpenter-6man-zone-ui-00.txt
>> Date: Mon, 15 Jan 2024 11:51:18 -0800
>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
>> Reply-To: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
>> To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org> <mailto:i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>
>>
>> Internet-Draft draft-carpenter-6man-zone-ui-00.txt is now available.
>>
>> Title: Entering IPv6 Zone Identifiers in User Interfaces
>> Authors: Brian Carpenter
>> Robert M. Hinden
>> Name: draft-carpenter-6man-zone-ui-00.txt
>> Pages: 7
>> Dates: 2024-01-15
>>
>> Abstract:
>>
>> This document describes how the zone identifier of an IPv6 scoped
>> address, defined in the IPv6 Scoped Address Architecture (RFC 4007),
>> should be entered into a user interface. It obsoletes RFC 6874.
>>
>> Discussion Venue
>>
>> This note is to be removed before publishing as an RFC.
>>
>> Discussion of this document takes place on the 6MAN mailing list
>> (ipv6@ietf.org <mailto:ipv6@ietf.org> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>>), which is archived at
>> https://mailarchive.ietf.org/arch/browse/ipv6/ <https://mailarchive.ietf.org/arch/browse/ipv6/> <https://mailarchive.ietf.org/arch/browse/ipv6/> <https://mailarchive.ietf.org/arch/browse/ipv6/&gt;>
>> (https://mailarchive.ietf.org/arch/browse/ipv6/ <https://mailarchive.ietf.org/arch/browse/ipv6/> <https://mailarchive.ietf.org/arch/browse/ipv6/> <https://mailarchive.ietf.org/arch/browse/ipv6/&gt;>).
>>
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-6man-zone-ui/ <https://datatracker.ietf.org/doc/draft-carpenter-6man-zone-ui/> <https://datatracker.ietf.org/doc/draft-carpenter-6man-zone-ui/> <https://datatracker.ietf.org/doc/draft-carpenter-6man-zone-ui/&gt;>
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-carpenter-6man-zone-ui-00.html <https://www.ietf.org/archive/id/draft-carpenter-6man-zone-ui-00.html> <https://www.ietf.org/archive/id/draft-carpenter-6man-zone-ui-00.html> <https://www.ietf.org/archive/id/draft-carpenter-6man-zone-ui-00.html&gt;>
>>
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org> <mailto:I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>>
>> https://www.ietf.org/mailman/listinfo/i-d-announce <https://www.ietf.org/mailman/listinfo/i-d-announce> <https://www.ietf.org/mailman/listinfo/i-d-announce> <https://www.ietf.org/mailman/listinfo/i-d-announce&gt;>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org <mailto:ipv6@ietf.org> <mailto:ipv6@ietf.org <mailto:ipv6@ietf.org>>
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 <https://www.ietf.org/mailman/listinfo/ipv6> <https://www.ietf.org/mailman/listinfo/ipv6> <https://www.ietf.org/mailman/listinfo/ipv6&gt;>
>> --------------------------------------------------------------------
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 <https://www.ietf.org/mailman/listinfo/ipv6>
> --------------------------------------------------------------------
> 
> 
>