IETF Logo Mail Archive

Re: [Lucid] Please clarify the i's in Appendix A

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 21 March 2015 17:45 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: lucid@ietfa.amsl.com
Delivered-To: lucid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6163F1A1BA2 for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 10:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 QMtovVPwq4Nn for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 10:45:15 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40B3A1A1B2B for <lucid@ietf.org>; Sat, 21 Mar 2015 10:45:15 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-905d.meeting.ietf.org [31.133.144.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 04C7D8A031 for <lucid@ietf.org>; Sat, 21 Mar 2015 17:45:13 +0000 (UTC)
Date: Sat, 21 Mar 2015 12:45:17 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150321174516.GC6841@mx1.yitter.info>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se> <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/KoyIqZVmNxKgb9M6MFhit8VpFz0>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
X-BeenThere: lucid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Locale-free UniCode Identifiers \(LUCID\)" <lucid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lucid>, <mailto:lucid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lucid/>
List-Post: <mailto:lucid@ietf.org>
List-Help: <mailto:lucid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lucid>, <mailto:lucid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2015 17:45:16 -0000

Hi,

On Fri, Mar 20, 2015 at 06:51:52AM +0000, Shawn Steele wrote:
> U+0130 is disallowed,

Ok.

> however most implementations do mapping for lookup,

Yes.

> in which case U+0130 changes to U+0069 + U+0307, due to the application of NFKC + Casefolding.

> http://www.unicode.org/Public/idna/8.0.0/IdnaMappingTable.txt 

What you're saying, actually, is that "most implementations" do
casefolding of upper-case input strings prior to IDNA processing
according to an approach that Unicode has (in this case pre-?)
published?  I'm just trying to understand.

> Or is lucid only concerned with the case where no mapping is applied?

I think we have to worry about cases where input strings are the
result of mapping, yes, but _before_ we tackle the really hard cases
can we sort out the merely hard cases?

Thanks,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email