Re: [Idna-update] IDNA and combining sequences (was: Re: Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>)

"John R Levine" <johnl@taugh.com> Mon, 12 March 2018 15:03 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: idna-update@ietfa.amsl.com
Delivered-To: idna-update@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8422126D05 for <idna-update@ietfa.amsl.com>; Mon, 12 Mar 2018 08:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=qTZsn8zy; dkim=pass (1536-bit key) header.d=taugh.com header.b=D1h5hBRA
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 7MktmdDy4fAl for <idna-update@ietfa.amsl.com>; Mon, 12 Mar 2018 08:03:57 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 5AE51124217 for <idna-update@ietf.org>; Mon, 12 Mar 2018 08:03:57 -0700 (PDT)
Received: (qmail 54916 invoked from network); 12 Mar 2018 15:03:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d682.5aa696dc.k1803; bh=oXHvhIVbCZy+ZMa7zdV+dnSQprSWJ3e+idzyn4C/adk=; b=qTZsn8zy8NohJTTTR+KBd03NEx/nJYicodW10oKg+ks5AmPoWXtcqEcBiPZnYpHkg2SXfYcWh2A5yw1dGZeYy0X/x5BQ3qIpgRcs9yQ9XsEEey6MdpXeCoQpYbUyvdtYvCJXCcFZ5ElL73GGirTRXRrp5XU2WzDoO4B06rRGmsVf4cPoezojBdqeRyHu2UxLHI8BfnhZbXRRWuCcnInAm557Ep1W5zo3Ks2jQTaX/WNIGX31n5TtzvecXtBmdG3y
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d682.5aa696dc.k1803; bh=oXHvhIVbCZy+ZMa7zdV+dnSQprSWJ3e+idzyn4C/adk=; b=D1h5hBRA2taRZoL0WFhbsidRKTnXk918tn0BsZ1JC30RO6T48ux8FnkRMsUfUSH+5TzcISChN5IcsEOGw8G+Zr/XCyrjHrcw7MWffuOJDQHyxrYANVDK5YKMeTdrDkgqbq+4xZlotOogngtZVdkonbmDT9rcdCuKrnDdgmWfmkPB+Zo3lO78w7b/j0E9S57PrfDWNlqY5KyUaVBkcOpILd8IBEb8JCjL6Nc3btFttwEzz1OHF8tba8zn3rt+U2f2
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 12 Mar 2018 15:03:55 -0000
Date: 12 Mar 2018 11:03:54 -0400
Message-ID: <alpine.OSX.2.21.1803121059121.94279@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: idna-update@ietf.org
In-Reply-To: <6FAA2D68A20DF091B0E0086B@JcK-HP5.jck.com>
References: <20180310182908.56AE82216259@ary.qy> <6FAA2D68A20DF091B0E0086B@JcK-HP5.jck.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/zaR-jc78WZeMfsFdF8L1XeuOGr0>
Subject: Re: [Idna-update] IDNA and combining sequences (was: Re: Expiration impending: <draft-klensin-idna-rfc5891bis-01.txt>)
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Internationalized Domain Names in Applications \(IDNA\) implementation and update discussions" <idna-update.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idna-update>, <mailto:idna-update-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update/>
List-Post: <mailto:idna-update@ietf.org>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idna-update>, <mailto:idna-update-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 15:03:59 -0000

> Even though it was generally assumed that
> a registry would not allow labels that did not conform to the
> labels it registered, that was never a requirement that anyone
> expected to be enforced at least up to the time those tables got
> entangled with the new gTLD program.

I've tried some experiments and it appears that gTLDs now enforce the 
script rules.  It is certainly true that there is some grandfathered 
garbage from before the IDNA rules, and ccTLDs do what they do.

> (4) I don't know if you are "missing" it or not, but we need to
> keep in mind that efforts to promote the use of DNAME records in
> the root, at the second level, and elsewhere, have potential bad
> side-effects.

No kidding.  DNAME at the second level was so bad that .cat stopped doing 
it.  There is one DNAME at the root, for the two versions of Taiwan in 
Chinese which as far as I can tell nobody has noticed.  But that seems 
like a separate can of worms.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly