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

Larry Masinter <LMM@acm.org> Tue, 29 January 2019 19:55 UTC

Return-Path: <masinter@gmail.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 88125130FF9 for <i18nrp@ietfa.amsl.com>; Tue, 29 Jan 2019 11:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 nmvnp9_vh3WO for <i18nrp@ietfa.amsl.com>; Tue, 29 Jan 2019 11:55:26 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 88E6C130FF6 for <i18nrp@ietf.org>; Tue, 29 Jan 2019 11:55:26 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id g62so10146663pfd.12 for <i18nrp@ietf.org>; Tue, 29 Jan 2019 11:55:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:sender:mime-version:to:from:subject:date:importance :in-reply-to:references; bh=yUTsDok6VUQIhhZ26SB5ximSV/+NADCwGEGIUbFxBu4=; b=Cr5ln3LnGO8ti9ZYXVFlRoTItYApNGZV2gspnWfCUWd8G+DtI9B/aYV+sZkEWc0yRW DZaDOfLUinUindAj/noASgS8fYCFECmbNQEe0K6s/L9AOReJVKx8DkyyX3p8JhN2XIl1 hXdYf41sVGYNQuvIINHbw2j23Ah39xOlKWILJvqUp6Hca0322rEm1c4KrNus67HuSgQH tMZ/7xUMyWrYFwzpsHdHKLHL4iTKfUBTWno6vyhltvWdpcvqXRnENGB8Sn/Adkir5l24 9gAITKfO62UpCwJryvzQxcMfJvcZBIKWyF08xaFVPfo5pG4JRlQaw6tT/IOsJs/HZBTc sYWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:sender:mime-version:to:from:subject :date:importance:in-reply-to:references; bh=yUTsDok6VUQIhhZ26SB5ximSV/+NADCwGEGIUbFxBu4=; b=ARgQ9QYfWSgsOjkscIfu9XNJT3konaf4RPQX5cnLanHhRQCKspXPb5QRpkSsAudjr+ WuyYwldStFN50TDeesoTyx0iDAplS2qIkj+DeZ2rdItEgllIXDQ1LQeFD0UOrpGfl0K1 iTr3vigX23OyGHifkuoUW7UIkn76yH5PwptES1ycGL8L8Pnt+nte7rFCJyq4yQvkNN4R f7NnJ9S6Y+gPrYMI0EjSNG5AjLc6yZx3s6z+gIrIlV2zsgDu9jczwdkLlTA5S4KucmXJ HRL1PmYmcfZEHAM4bNgnJEVEphekWCfXuwBKfbrjHL+nSoe0cJzDheA4U1d4CKvB8CFB lO8g==
X-Gm-Message-State: AJcUukdc/2Q23rAxNIIEw+uok5LZ3boSWewPWushp1zu2+iZuX/P6lX5 N968Lq3a/B2dbIbDc/SyM++rg5l5
X-Google-Smtp-Source: ALg8bN7tMCA+DOb4+tKK4QszuYAR7Fm3PgAJwQkARnPJ26U4bDxMBUWuaDieL59kzmzqW3qmn5aqnA==
X-Received: by 2002:a62:5ec5:: with SMTP id s188mr27019145pfb.145.1548791725563; Tue, 29 Jan 2019 11:55:25 -0800 (PST)
Received: from ?IPv6:::ffff:192.150.23.129? (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id g190sm53999383pgc.28.2019.01.29.11.55.24 for <i18nrp@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 11:55:24 -0800 (PST)
Message-ID: <5c50afac.1c69fb81.a259.967d@mx.google.com>
Sender: Larry Masinter <masinter@gmail.com>
MIME-Version: 1.0
To: "i18nrp@ietf.org" <i18nrp@ietf.org>
From: Larry Masinter <LMM@acm.org>
Date: Tue, 29 Jan 2019 11:55:24 -0800
Importance: normal
X-Priority: 3
In-Reply-To: <5c50ae44.1c69fb81.7e074.ce72@mx.google.com>
References: <5c50ae44.1c69fb81.7e074.ce72@mx.google.com>
Content-Type: multipart/alternative; boundary="_C0A2359C-C293-4E49-8C02-2CD3B03B256A_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/FCU65ShYBmq3sXtn3ANT_NNiVVs>
Subject: [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: Tue, 29 Jan 2019 19:55:29 -0000

FYI

From: Larry Masinter
Sent: Tuesday, January 29, 2019 11:49 AM
To: comments-strategic-plan-20dec18@icann.org
Subject: Comment on ICANN strategic plan 2021-2025

In the area of global unique identifiers, there are two areas where a relatively small investment would go a long way toward the security and governance of unique identifier systems.

a) Improvements to usability of IANA registries, e.g., through use of open source infrastructure. IANA registries, especially around the web-relevant registries, currently have poor participation, and I believe much of the non-use is because the processes for updating, using, commenting, reviewing those registries are cumbersome compared to the alternatives (WikiPedia, Open Source registries, etc.)  I’d suggest as a strategic management of IANA should include some effort to survey the uses, select additional technology, analyze the transparency and effectiveness of the registration methods. I think I would include MIME types and URI schemes, but also look at requirements of communities that currently maintain Internet-wide registries outside of IANA.
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.

Larry
--
https://LarryMasinter.net#URL