IETF Logo Mail Archive

Re: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01

Shawn Steele <Shawn.Steele@microsoft.com> Mon, 12 July 2010 06:08 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 80EEF3A6835 for <ima@core3.amsl.com>; Sun, 11 Jul 2010 23:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.163
X-Spam-Level:
X-Spam-Status: No, score=-9.163 tagged_above=-999 required=5 tests=[AWL=-0.978, BAYES_40=-0.185, 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 MnQPy-aD9LTN for <ima@core3.amsl.com>; Sun, 11 Jul 2010 23:08:22 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id A454D3A67C2 for <ima@ietf.org>; Sun, 11 Jul 2010 23:08:22 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 11 Jul 2010 23:08:30 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.215]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0160.007; Sun, 11 Jul 2010 23:08:29 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Comments on draft-ietf-eai-frmwrk-4952bis-01
Thread-Index: AcsfnGzQlL9X1gg+SIy9oIBnXfjrbQ==
Date: Mon, 12 Jul 2010 06:08:30 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A0DA552C0@TK5EX14MBXC141.redmond.corp.microsoft.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
Subject: Re: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01
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: Mon, 12 Jul 2010 06:08:23 -0000

> The second sentence is not very clear. Is the following what is meant?

>    In this case, the client will not be able to transmit any messages
>    which contain non-ASCII characters in the local-part of any email
>    addresses. If the non-ASCII characters are confined only to the
>    domain portion of the address, such a client will be able to
>    transmit messages if it uses [RFC3490] or [RFC5890] ToAscii() to
>    encode the domain portions of these addresses.

They may have ASCII aliases (eg: transliterations) available, so I think that's a tad too restrictive.

   In this case, the client will not be able to transmit any messages
   which contain non-ASCII characters in the local-part of any email
   addresses. If the client has an ASCII only address available, such
   as an alias, or by applying [RFC3490bis] ToAscii to the domain
   portion of the address, then it may be able to send the mail in
   ASCII as per [RFC2821].

-Shawn

v2.23.0 | Report a Bug | By Email