[EAI] IDN in Unicode
Shawn Steele <Shawn.Steele@microsoft.com> Fri, 24 April 2015 19:22 UTC
Return-Path: <Shawn.Steele@microsoft.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD1661B3871 for <ima@ietfa.amsl.com>; Fri, 24 Apr 2015 12:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 210Bi6F-AHrw for <ima@ietfa.amsl.com>; Fri, 24 Apr 2015 12:22:21 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0751.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:751]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BCBA1B386C for <ima@ietf.org>; Fri, 24 Apr 2015 12:22:20 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) with Microsoft SMTP Server (TLS) id 15.1.148.16; Fri, 24 Apr 2015 19:21:59 +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.0148.008; Fri, 24 Apr 2015 19:21:59 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: IDN in Unicode
Thread-Index: AdB+wzxbuAHnFuVPQUWDnfS4KK0oWw==
Date: Fri, 24 Apr 2015 19:21:58 +0000
Message-ID: <BLUPR03MB1378D012C16E1FD2A700B12D82EC0@BLUPR03MB1378.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-originating-ip: [2001:4898:80e0:ee43::5]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1378;
x-microsoft-antispam-prvs: <BLUPR03MB137885E95F34D91D8513591E82EC0@BLUPR03MB1378.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(2351001)(107886001)(50986999)(33656002)(99286002)(62966003)(77156002)(102836002)(110136001)(2501003)(74316001)(450100001)(92566002)(76576001)(229853001)(122556002)(54356999)(46102003)(86362001)(2656002)(40100003)(87936001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1378; 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)(3002001); SRVR:BLUPR03MB1378; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1378;
x-forefront-prvs: 05568D1FF7
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Apr 2015 19:21:58.9534 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1378
Archived-At: <http://mailarchive.ietf.org/arch/msg/ima/MCGXvndjMFhea7efhGuqVXzsJfQ>
Subject: [EAI] IDN in Unicode
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 19:22:23 -0000
> The basic propose is to find solution for IDN domains and email addresses be present in original scripts. That seems like a completely different discussion than "let's use UTF-32". Many applications handle domain names natively in either UTF-8 or UTF-16, either of which are sufficient to describe the domains in their original scripts. Punycode is kind of a hack to provide a mechanism to resolve domain names using the preexisting infrastructure that is limited to the ASCII space. However many applications, like EAI, prefer UTF-8. Our recommendations provide for IDN to be looked up with Punycode only in the resolution phase. For many apps that is transparent to the app and they can just use Unicode with the system API set. Some apps, however may need to recognize Punycode domains for whatever reason or additional protocol limitations. However in those cases it is still recommended that they prefer Unicode and only use the Punycode when absolutely necessary. -Shawn
- [EAI] IDN in Unicode Shawn Steele
- Re: [EAI] IDN in Unicode John C Klensin