Re: [I18nrp] FW: Comment on ICANN strategic plan 2021-2025

John C Klensin <john@jck.com> Fri, 01 February 2019 01:05 UTC

Return-Path: <john@jck.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083D2131196 for <i18nrp@ietfa.amsl.com>; Thu, 31 Jan 2019 17:05:19 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 EMex0t4FP1Vt for <i18nrp@ietfa.amsl.com>; Thu, 31 Jan 2019 17:05:17 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 232FD131195 for <i18nrp@ietf.org>; Thu, 31 Jan 2019 17:05:17 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1gpNGd-000IDL-SK; Thu, 31 Jan 2019 20:05:15 -0500
Date: Thu, 31 Jan 2019 20:05:08 -0500
From: John C Klensin <john@jck.com>
To: Larry Masinter <LMM@acm.org>, i18nrp@ietf.org
Message-ID: <7B87BC4F1BB92AC5739FDA96@PSB>
In-Reply-To: <5c50afac.1c69fb81.a259.967d@mx.google.com>
References: <5c50ae44.1c69fb81.7e074.ce72@mx.google.com> <5c50afac.1c69fb81.a259.967d@mx.google.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/o2XZJk_6DVwheYdcj1hXZJSEfR0>
Subject: Re: [I18nrp] FW: Comment on ICANN strategic plan 2021-2025
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2019 01:05:19 -0000


--On Tuesday, January 29, 2019 11:55 -0800 Larry Masinter
<LMM@acm.org> wrote:

>...
> b) Aids to use of IDN.  The current focus on TLD selection in
> ICANN priorities for IDN development should be expanded to
> include a focus on other barriers to actual USE of IDNs
> embedded in other globally unique identifiers, including email
> addresses and URLs. In particular, someone choosing components
> of an identifier needs some way of easily assessing the
> usability of the entire identifier for the full range of uses
> of that identifier, including comparison, recognition, and
> transcription. There is a gap between the development of TLD
> rules and the actual end-users that should be addressed in the
> timeframe of this strategic plan.

Are you aware that ICANN has a relatively large and well-funded
activity called "Universal Acceptance" that is chartered to
address several (probably most) of the issues you list above?
See www.uasg.tech. for more information.  I'm sure they would
appreciate your contributions and other help.

    john