IETF Logo Mail Archive

Re: [EAI] Rechartering

Shawn Steele <Shawn.Steele@microsoft.com> Fri, 24 July 2009 15:53 UTC

Return-Path: <Shawn.Steele@microsoft.com>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 705E228C15C for <ima@core3.amsl.com>; Fri, 24 Jul 2009 08:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.908
X-Spam-Level:
X-Spam-Status: No, score=-9.908 tagged_above=-999 required=5 tests=[AWL=0.691, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2arfgI4aKQR8 for <ima@core3.amsl.com>; Fri, 24 Jul 2009 08:53:27 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id A8BB23A69F1 for <ima@ietf.org>; Fri, 24 Jul 2009 08:53:27 -0700 (PDT)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Fri, 24 Jul 2009 08:51:05 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.179]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi; Fri, 24 Jul 2009 08:51:04 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, YAO Jiankang <yaojk@cnnic.cn>, Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [EAI] Rechartering
Thread-Index: AQHKBv5CbMAbFBG94EaF4/MwRhfNZ5B6JnbwgAOnXACABQIwX4ABVhyNgAC63ID///2Epg==
Date: Fri, 24 Jul 2009 15:48:51 +0000
Message-ID: <CAD7705D4A93814F97D3EF00790AF0B315FDFC3F@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.13830.1247508102.4936.ima@ietf.org> <CAD7705D4A93814F97D3EF00790AF0B315FA6650@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A5BABF8.4080900@isode.com> <CAD7705D4A93814F97D3EF00790AF0B315FA6AAF@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A60AA0B.4000106@alvestrand.no> <CAD7705D4A93814F97D3EF00790AF0B315FCA179@TK5EX14MBXC104.redmond.corp.microsoft.com> , <EA9664FBEBEB7127550C3D30@[192.168.1.110]> <448158382.31213@cnnic.cn> , <01fe01ca0b6e$dc14f6f0$236ff1da@whatisfuture> <CAD7705D4A93814F97D3EF00790AF0B315FDF9D6@tk5ex14mbxc105.redmond.corp.microsoft.com>, <60D97B429B72BB756E8C14B5@JcK-eee9.example.com>
In-Reply-To: <60D97B429B72BB756E8C14B5@JcK-eee9.example.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] Rechartering
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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 Jul 2009 15:53:28 -0000

> Note that the normalization question is an example here ... NFC
> is almost irrelevant for Chinese characters because there are no
> combining forms, but very important for scripts in which
> combining characters are used and precomposed alternatives are
> common.

Yes, but it's irrelevent on the client side.  Servers "should" be smart, but I wouldn't want to force NFC on a server that thinks its architecture is best served by NFD (for example).  I think it'd be great to strongly recommend that they consider normalization and the best mapping practices for their needs, but I don't think we need to force servers.

Turkish i is a good place where IDN style mappings may not be appropriate for local parts.  As it "only" impacts a particular server's users, and not interoperability, I'd rather not over-specify that part of the standard.

-Shawn

v2.29.0 | Report a Bug | By Email | System Status