Re: [EAI] #11: Capture the scenario of "SHOULD not use
Shawn Steele <Shawn.Steele@microsoft.com> Mon, 19 September 2011 19:36 UTC
Return-Path: <Shawn.Steele@microsoft.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5046621F8C14 for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 12:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level:
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggbhAvmDNmh3 for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 12:36:27 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 6C61821F8C53 for <ima@ietf.org>; Mon, 19 Sep 2011 12:36:27 -0700 (PDT)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 19 Sep 2011 12:38:51 -0700
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.152]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0339.002; Mon, 19 Sep 2011 12:38:50 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: [EAI] #11: Capture the scenario of "SHOULD not use
Thread-Index: Acx3AzPpcPcpvOtyRFuNxA3PODWcfQ==
Date: Mon, 19 Sep 2011 19:38:50 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A3FAFEFAE@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] #11: Capture the scenario of "SHOULD not use
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 19 Sep 2011 19:36:28 -0000
Dave commented: >On 9/19/2011 7:58 AM, ned+ima@mrochek.com wrote: >>> "Implementers of message-id generation algorithms may prefer to restrain >>> their output to ASCII since that has a few minor advantages, such as when >>> constructing References fields in mailing-list threads where some senders >>> use EAI and others not." > I looked over the draft, and this language made me very uncomfortable. > The reason is that -- once again -- it has this draft trying to juggle a hybrid > (UTF-8/ASCII-only) world, rather than a much simpler UTF-8 only world. IMO this does not harm, and I'd rather not have this topic delay the doc. To me this paragraph might make you think about choosing ids when you do so, yet it is mild and doesn't prohibit UTF-8. That said, I don't mind if it were cut either. -Shawn
- Re: [EAI] #11: Capture the scenario of "SHOULD no… Shawn Steele