IETF Logo Mail Archive

[IPv6]Re: Last Call: <draft-ietf-6man-zone-ui-05.txt> (Entering IPv6 Zone Identifiers in User Interfaces) to Proposed Standard

Jürgen Schönwälder <jschoenwaelder@constructor.university> Sat, 04 January 2025 13:03 UTC

Return-Path: <jschoenwaelder@constructor.university>
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 8D69AC14F60A; Sat, 4 Jan 2025 05:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.241
X-Spam-Level:
X-Spam-Status: No, score=-1.241 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 sGEWiFTmhOQo; Sat, 4 Jan 2025 05:03:49 -0800 (PST)
Received: from beadg.de (beadg.de [178.254.54.206]) by ietfa.amsl.com (Postfix) with ESMTP id 0B44CC14F5F9; Sat, 4 Jan 2025 05:03:45 -0800 (PST)
Received: from localhost (firewallix.jacobs-university.de [212.201.44.246]) by beadg.de (Postfix) with ESMTPSA id 8F20D16A047; Sat, 4 Jan 2025 14:03:43 +0100 (CET)
Date: Sat, 04 Jan 2025 14:03:42 +0100
From: Jürgen Schönwälder <jschoenwaelder@constructor.university>
To: last-call@ietf.org
Message-ID: <Z3kxrlchb2mIdaGA@alice.eecs.jacobs-university.de>
Mail-Followup-To: last-call@ietf.org, IETF-Announce <ietf-announce@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-zone-ui@ietf.org, furry13@gmail.com, ipv6@ietf.org
References: <173558207998.1082330.2098681525141025323@dt-datatracker-65f549669d-2xld9>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <173558207998.1082330.2098681525141025323@dt-datatracker-65f549669d-2xld9>
Message-ID-Hash: WMFJ5OMXXUZQDRM4YMC4IHEEBUDIU2YO
X-Message-ID-Hash: WMFJ5OMXXUZQDRM4YMC4IHEEBUDIU2YO
X-MailFrom: jschoenwaelder@constructor.university
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IETF-Announce <ietf-announce@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-zone-ui@ietf.org, ipv6@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: Jürgen Schönwälder <jschoenwaelder@constructor.university>
Subject: [IPv6]Re: Last Call: <draft-ietf-6man-zone-ui-05.txt> (Entering IPv6 Zone Identifiers in User Interfaces) to Proposed Standard
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XDxKbs-Yyz8CUdQHH62pHOIc8Ts>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

On Mon, Dec 30, 2024 at 10:07:59AM -0800, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document: - 'Entering IPv6 Zone Identifiers in User
> Interfaces'
>   <draft-ietf-6man-zone-ui-05.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2025-01-13. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>

Section 3 says:

   The zone identifiers that can be used are limited by the
   host operating system, since [RFC4007] only specifies that they are
   coded in ASCII, without specifying a maximum length.

Section	6 says:

   RFC 4007 does not specify the character set allowed in a zone
   identifier.

So either RFC 4007 says the zone identifier is ASCII or it does not.
My reading of RFC 4007 is that it is silent about the character set,
but perhaps I missed the spot where it says otherwise.

/js

-- 
Jürgen Schönwälder              Constructor University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany

v2.30.2 | Report a Bug | By Email | System Status