Re: [I18nrp] Mappings for IDNA2008 ?

Nico Williams <nico@cryptonector.com> Tue, 05 February 2019 00:59 UTC

Return-Path: <nico@cryptonector.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 2DB2C130EE7 for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 cgCSOq2WjTcn for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:59:23 -0800 (PST)
Received: from bisque.maple.relay.mailchannels.net (bisque.maple.relay.mailchannels.net [23.83.214.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 279DD130DD3 for <i18nrp@ietf.org>; Mon, 4 Feb 2019 16:59:23 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 176EA124532; Tue, 5 Feb 2019 00:59:22 +0000 (UTC)
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (unknown [100.96.35.77]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id B7786124488; Tue, 5 Feb 2019 00:59:21 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Tue, 05 Feb 2019 00:59:22 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Daffy-Cellar: 07d8ad1e51339127_1549328361913_683478879
X-MC-Loop-Signature: 1549328361913:1164727231
X-MC-Ingress-Time: 1549328361912
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTP id 6A99E81941; Mon, 4 Feb 2019 16:59:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=w0Fa1G/eDqZQl7 b8GXuFt77B0QU=; b=WAHbatxKuo/a7VVMd+L8YttQIygCvATQmviH1+w8yTXFRK fECbWmhtOdACdXOySHMlM1i3lVv6FNstcc+GsotbsVJ/NfQxTTbIuLJsdKixygBm 32p11tERjl64G06coPzZ0JPhd84ZxyeX8iDfYP4ChLLz1qbsyiqiB0jX+CXns=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTPSA id C610081961; Mon, 4 Feb 2019 16:59:19 -0800 (PST)
Date: Mon, 4 Feb 2019 18:59:17 -0600
X-DH-BACKEND: pdx1-sub0-mail-a70
From: Nico Williams <nico@cryptonector.com>
To: John Levine <johnl@taugh.com>
Cc: i18nrp@ietf.org, asmusf@ix.netcom.com
Message-ID: <20190205005916.GE4108@localhost>
References: <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@ix.netcom.com> <20190205002555.1AFBA200DC1DB1@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190205002555.1AFBA200DC1DB1@ary.qy>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtledrkeehgddvkecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/uz26hADuSDyzuZGCuXVK_m1CmYQ>
Subject: Re: [I18nrp] Mappings for IDNA2008 ?
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, 05 Feb 2019 00:59:25 -0000

On Mon, Feb 04, 2019 at 07:25:54PM -0500, John Levine wrote:
> In article <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@ix.netcom.com>; you write:
> >> Are there any published IDNA2008 mappings?  As far as I can tell,
> >> everyone uses one from UTS46 by default, and it's not very good.
> >>
> >Examples of its badness, please.
> 
> As I understand it:
> 
> If you speak Turkish, the case folding is wrong.

So, IDNA says not to case-fold.  So users need to get case right -- oof.
Now, mostly users are accustomed to seeing domainnames in lower-case,
and type them in that way.  Sadly, mobile UIs stupidly up-case the first
letter (yay!), so if we don't at least down-case that first letter, we
have a problem for IDNs (ASCII labels are matched case-insensitively, so
they're OK; it's only IDNs that have this problem).

Now, if you never up-case, and only down-case, and if the user enters
the i or dotless i in lower-case, then there's no case folding issue for
Turkish.

The Turkish issue is academic, not a real issue.

Now, IF we could get all the broken mobile URI entry UIs in the world to
stop up-casing the first letters domainnames, then we could just train
users to enter domainnames in lower-case (or whatever case mix is
appropriate) and we'd have no problem...

...except users are not going to remember correct mix-case domainnames,
so case folding is basically necessary.  That there are a few ambiguous
cases like the Turkish dotless i seems like one of those "tough, deal
with it" moments.

Nico
--