IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sat, 10 March 2018 18:29 UTC

Return-Path: <johnl@iecc.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 B555F124E15 for <idna-update@ietfa.amsl.com>; Sat, 10 Mar 2018 10:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=LTXopEXC; dkim=pass (1536-bit key) header.d=taugh.com header.b=Ov48At4J
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 2tE78hgZc5BO for <idna-update@ietfa.amsl.com>; Sat, 10 Mar 2018 10:29:10 -0800 (PST)
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 BA081124235 for <idna-update@ietf.org>; Sat, 10 Mar 2018 10:29:09 -0800 (PST)
Received: (qmail 26384 invoked from network); 10 Mar 2018 18:29:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=670e.5aa423f4.k1803; bh=QZOIgitTWW2Fb2W0lVzhzC31HbSwM7OKpc89gaaTzLY=; b=LTXopEXCl6Hjni4pBiUhavhYELznxYZP2jb2YIDvQjvBLNfhukgfDhu/XHT2il2kGGEXOF3W263Q9FC0K2FQU144seVlfDgotVWMRSyJr8AKzAOW2Q0g8aRzkQIFT1WJYb9rzjeGs6sKaNxGWaimvrOzGEy77GdW6Yptm51CY2VSIMAhKMoSOmSgPywedzMWHBAR8YTDFU0cAQp/ezaTb9W8t2Sj/el0vMP0ZDe/5Ixi8yEv/wh1RwOwyWbAdMUl
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=670e.5aa423f4.k1803; bh=QZOIgitTWW2Fb2W0lVzhzC31HbSwM7OKpc89gaaTzLY=; b=Ov48At4J/IKL5CWWAUUU5o3ZpO1t4QPWQVDdFhqS2zALg//uJD2VUVxBrEggcO303lGvyf2QRb0raSxO9Ou4pBQgsIKGvVVS2t8TXSjzTpwy6M3KlqWgOFBVw/t203vlPBWRaPKkD2zgmAVylHr9ukM4JKAlemfIfjW+61b6NlWxhwl+kNdo56IJC2dDXLhJ1/KmuzTACjXkyKnb/ZnBFsoVAzXj5GLU87BZi/KNef5azln76jLM34zhqpuVaY6q
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 10 Mar 2018 18:29:08 -0000
Received: by ary.qy (Postfix, from userid 501) id 56AE82216259; Sat, 10 Mar 2018 13:29:07 -0500 (EST)
Date: 10 Mar 2018 13:29:07 -0500
Message-Id: <20180310182908.56AE82216259@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: idna-update@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <D26CE952D968BBEC0AB96A76@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/p2Y_7Wn4hD71jWMh0SNjRJLr0YA>
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: Sat, 10 Mar 2018 18:29:11 -0000

In article <D26CE952D968BBEC0AB96A76@PSB> you write:
>The latter would probably quickly reach the point that attempts
>to apply the LGR to labels at the second level and beyond would
>encourage non-compliance and daring ICANN to do anything about
>it.     

I'm confused.  Every gTLD and many ccTLDS have language and script
rules that limit what 2LDs they will accept.  When I was looking at
gTLD applications, the rules all looked pretty reasonable, give or
take what you think is a reasonable approach to handling variants.

What am I missing?  I realize that below the 2LDs anything goes.

R's,
John

v2.8.7 | Report a Bug | By Email