IETF Logo Mail Archive

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

Shawn Steele <Shawn.Steele@microsoft.com> Fri, 20 March 2015 06:51 UTC

Return-Path: <Shawn.Steele@microsoft.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 10A451B2C51 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 23:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 viuJNYXHY1V7 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 23:51:54 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0139.outbound.protection.outlook.com [65.55.169.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A00A21B2C50 for <lucid@ietf.org>; Thu, 19 Mar 2015 23:51:54 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1377.namprd03.prod.outlook.com (25.163.81.11) with Microsoft SMTP Server (TLS) id 15.1.118.21; Fri, 20 Mar 2015 06:51:52 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Fri, 20 Mar 2015 06:51:52 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Patrik Fältström <paf@frobbit.se>
Thread-Topic: [Lucid] Please clarify the i's in Appendix A
Thread-Index: AdBin+ZuKs3zpeT0SS+0IvxOVk8XSgAMoPgAAAEwJGA=
Date: Fri, 20 Mar 2015 06:51:52 +0000
Message-ID: <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se>
In-Reply-To: <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.34.94.236]
authentication-results: frobbit.se; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1377;
x-microsoft-antispam-prvs: <BLUPR03MB1377BD1D85FF5F3CDCCBBB15820E0@BLUPR03MB1377.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(51704005)(62966003)(99286002)(15975445007)(77156002)(102836002)(74316001)(110136001)(86362001)(76576001)(2656002)(86612001)(87936001)(54356999)(50986999)(122556002)(2950100001)(92566002)(19580405001)(19580395003)(40100003)(66066001)(33656002)(46102003)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1377; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1377; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1377;
x-forefront-prvs: 05214FD68E
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2015 06:51:52.4641 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1377
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/BjSmPwNa2-_vn-wF6qC40MHAGwA>
Cc: "lucid@ietf.org" <lucid@ietf.org>
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: Fri, 20 Mar 2015 06:51:56 -0000

U+0130 is disallowed, however most implementations do mapping for lookup, 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 

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

-Shawn

-----Original Message-----
From: Patrik Fältström [mailto:paf@frobbit.se] 
Sent: Thursday, March 19, 2015 10:55 PM
To: Shawn Steele
Cc: lucid@ietf.org
Subject: Re: [Lucid] Please clarify the i's in Appendix A


> On 20 mar 2015, at 01:01, Shawn Steele <Shawn.Steele@microsoft.com> wrote:
> 
> IDNA makes this worse by mapping İ U+0130 to U+0069 + U+0307, apparently to get a visual effect.  It seems peculiar to me that there would need to be an exception to the existing exception.

Can you please clarify?

IDNA do not include mapping, so I presume you mean "IDNA would make this worse IF it mapped..."?

   Patrik

v2.23.0 | Report a Bug | By Email