Re: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01 (and -02)

Jason Nelson <jason@exchange.microsoft.com> Mon, 12 July 2010 18:58 UTC

Return-Path: <jason@exchange.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 B360F3A69DC for <ima@core3.amsl.com>; Mon, 12 Jul 2010 11:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 YceQnSnGCv+X for <ima@core3.amsl.com>; Mon, 12 Jul 2010 11:58:23 -0700 (PDT)
Received: from mail.exchange.microsoft.com (mail1.exchange.microsoft.com [131.107.1.17]) by core3.amsl.com (Postfix) with ESMTP id E39C13A68A7 for <ima@ietf.org>; Mon, 12 Jul 2010 11:58:22 -0700 (PDT)
Received: from df-h14-01.exchange.corp.microsoft.com (157.54.78.139) by DF-G14-01.exchange.corp.microsoft.com (157.54.87.87) with Microsoft SMTP Server (TLS) id 14.1.208.0; Mon, 12 Jul 2010 11:58:30 -0700
Received: from DF-M14-05.exchange.corp.microsoft.com ([169.254.2.6]) by DF-H14-01.exchange.corp.microsoft.com ([157.54.78.139]) with mapi id 14.01.0180.003; Mon, 12 Jul 2010 11:58:32 -0700
From: Jason Nelson <jason@exchange.microsoft.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, Joseph Yee <jyee@ca.afilias.info>
Thread-Topic: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01 (and -02)
Thread-Index: AQHLIexgtSHZxK+nj0OrNGA19gBzYpKuGF4A//+LfQA=
Date: Mon, 12 Jul 2010 18:58:29 +0000
Message-ID: <6CE0D5FA2297784CB7A6F5F09865C895307F8353@DF-M14-05.exchange.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A0DA552C0@TK5EX14MBXC141.redmond.corp.microsoft.com> <FCA41AD1F0296F7ADB9AF84B@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A0DA57755@TK5EX14MBXC141.redmond.corp.microsoft.com> <AFF8867C-A6B3-49EC-AFF4-77684461067F@ca.afilias.info> <E14011F8737B524BB564B05FF748464A0DA57978@TK5EX14MBXC141.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A0DA57978@TK5EX14MBXC141.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.110]
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] Comments on draft-ietf-eai-frmwrk-4952bis-01 (and -02)
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 18:58:23 -0000

In the current design, with a message destined to two recipients, A and B, A supports UTF8 and B does not - what should B's P2 content look like?  I get that the RFC specifically deals with addresses in transit, and that we should not be mucking about with messages when not the submission server, but resolving how the mail goes to both the guys in the US and the your business partner in Taiwan with both being able to reply across the board, that's giving me a few headaches.


-----Original Message-----
From: ima-bounces@ietf.org [mailto:ima-bounces@ietf.org] On Behalf Of Shawn Steele
Sent: Monday, July 12, 2010 11:53 AM
To: Joseph Yee
Cc: ima@ietf.org
Subject: Re: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01 (and -02)


Confirmed, yes, I'm happy with it.  (mentioning again as it might get lost in my longer reply I just replied).

-Shawn

-----Original Message-----
From: Joseph Yee [mailto:jyee@ca.afilias.info] 
Sent: Monday, July 12, 2010 11:01 AM
To: Shawn Steele
Cc: John C Klensin; ima@ietf.org
Subject: Re: [EAI] Comments on draft-ietf-eai-frmwrk-4952bis-01 (and -02)

Shawn,

The discussion on encoding domain part with RFC3490 or RFC5890 is focus on what may/can do immediately with ascii-only@utf8-domain address (following the discussion that narrow down the scenario).  Your concern of too restrictive choices was addressed on section 7.1 in Framework-02 of what MUA and user can do.  The text there mentions wide range of approaches.  

I believed that Section 7.1 (in Framework-02) address your concern in Section 3.2 (UTF8SMTPbis).

Best
Joseph
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima