
From Shawn.Steele@microsoft.com  Mon Nov  1 11:23:16 2010
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 CE06628C0ED for <ima@core3.amsl.com>; Mon,  1 Nov 2010 11:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 TjeCs83kOBsX for <ima@core3.amsl.com>; Mon,  1 Nov 2010 11:23:16 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 1C9BC28C0E0 for <ima@ietf.org>; Mon,  1 Nov 2010 11:23:16 -0700 (PDT)
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (157.54.80.67) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 1 Nov 2010 11:23:18 -0700
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.14]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Mon, 1 Nov 2010 11:23:17 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: mailto
Thread-Index: Act58Wx1x4hcrYzuR+Wl50MEke3+tQ==
Date: Mon, 1 Nov 2010 18:23:16 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.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.76]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "jwz@jwz.org" <jwz@jwz.org>, "Larry Masinter \(masinter@adobe.com\)" <masinter@adobe.com>
Subject: [EAI] mailto
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, 01 Nov 2010 18:23:16 -0000

> Second, RFC 6068 (http://tools.ietf.org/html/rfc6068) was just published =
this month. But I'm happy to work on an update if necessary. I have cc'ed m=
y co-authors to check whether they would also be happy to continue as co-au=
thors.

> In terms of I18N, RFC 6068 is a big progress over RFC 2368. It allows non=
-ASCII content in any headers (where the header itself allows that) and in =
the body (via the generic UTF-8-based percent-encoding). This is already wi=
dely supported by many (though not all) MUAs.

> Further changes would be appropriate in the Syntax and Examples sections,=
 to make clear that when using EAI, data can be sent as raw UTF-8, without =
using encoded words.

It seems to me that some updates might be necessary (but it seems reasonabl=
e to wait to know a little bit to better understand what they should be).  =
Particularly I think that users are likely to just use mailto:unicode@unico=
de without bothering with the % escaping, so it seems like some update it g=
oing to be necessary.

-Shawn

From duerst@it.aoyama.ac.jp  Mon Nov  1 22:40:44 2010
Return-Path: <duerst@it.aoyama.ac.jp>
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 925D43A67E4 for <ima@core3.amsl.com>; Mon,  1 Nov 2010 22:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.814
X-Spam-Level: 
X-Spam-Status: No, score=-101.814 tagged_above=-999 required=5 tests=[AWL=-2.024, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 q82fMbZ402BD for <ima@core3.amsl.com>; Mon,  1 Nov 2010 22:39:32 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id E60CF3A67DF for <ima@ietf.org>; Mon,  1 Nov 2010 22:39:20 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oA25d8pW022390 for <ima@ietf.org>; Tue, 2 Nov 2010 14:39:08 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 04e6_875d_830dd5fc_e643_11df_826c_001d096c566a; Tue, 02 Nov 2010 14:39:08 +0900
Received: from [IPv6:::1] ([133.2.210.1]:59684) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S147A797> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 2 Nov 2010 14:39:07 +0900
Message-ID: <4CCFA3F3.9070305@it.aoyama.ac.jp>
Date: Tue, 02 Nov 2010 14:38:59 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Shawn Steele <Shawn.Steele@microsoft.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "jwz@jwz.org" <jwz@jwz.org>, "ima@ietf.org" <ima@ietf.org>, "Larry Masinter \(masinter@adobe.com\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Tue, 02 Nov 2010 05:40:44 -0000

On 2010/11/02 3:23, Shawn Steele wrote:

> Particularly I think that users are likely to just use mailto:unicode@unicode without bothering with the % escaping,

The "without bothering with the %-escaping" part is covered where an IRI 
(instead of only an URI in the strict sense) is accepted.

Regards,    Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From klensin@jck.com  Tue Nov  2 08:36:28 2010
Return-Path: <klensin@jck.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 B0A6C3A69DB for <ima@core3.amsl.com>; Tue,  2 Nov 2010 08:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[AWL=-0.420, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3]
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 B-t-YFwOU4Bj for <ima@core3.amsl.com>; Tue,  2 Nov 2010 08:36:26 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id C11603A68D7 for <ima@ietf.org>; Tue,  2 Nov 2010 08:36:16 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PDIuA-000IqY-BY; Tue, 02 Nov 2010 11:36:10 -0400
Date: Tue, 02 Nov 2010 11:36:09 -0400
From: John C Klensin <klensin@jck.com>
To: =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>, Shawn Steele <Shawn.Steele@microsoft.com>
Message-ID: <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM>
In-Reply-To: <4CCFA3F3.9070305@it.aoyama.ac.jp>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: jwz@jwz.org, ima@ietf.org, "Larry Masinter \\\(masinter@adobe.com\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Tue, 02 Nov 2010 15:36:28 -0000

--On Tuesday, November 02, 2010 14:38 +0900 "\"Martin J.
D=C3=BCrst\"" <duerst@it.aoyama.ac.jp> wrote:

> On 2010/11/02 3:23, Shawn Steele wrote:
>=20
>> Particularly I think that users are likely to just use
>> mailto:unicode@unicode without bothering with the % escaping,
>=20
> The "without bothering with the %-escaping" part is covered
> where an IRI (instead of only an URI in the strict sense) is
> accepted.

Martin,

Yes.  But this is exactly where I find several of the parallel
discussions troubling.

(1) EAI thinks an email address is, in Shawn's notation,
unicode@unicode (or possibly unicode@string-with-A-labels).  It
does not permit %-escapes in the domain name and many mail
systems will interpret %-signs in the local part as something
else entirely, e.g., routing information.

(2) For an IRI, mailto:unicode@unicode is perfectly reasonable.
However, the mapping to a URI, unless it is scheme/protocol
dependent, is likely to produce either
   mailto:%-escapes@%-escapes
or
   mailto:%-escapes@string-with-A-labels

Both of which are really bad news if one tries to get from
mailto:String to an email address by dropping the mailto and
leaving String.

I think that means that any sort of i18n MAILTO processor has to
get from those forms back to the non-escaped Unicode-in-UTF-8
strings that EAI expects before passing an internationalized
address off to a mail-sending or processing operation.   If one
reads the second paragraph of Section 5 of RFC 6068 (and the
warning in the third-to-last paragraph of Section 7), one can
claim that is implied there, but it is difficult (at best) to
parse that exact meaning out from the convoluted language that
was used, presumably to avoid a normative reference to the EAI
specs.

Note that this is a key difference from web and web-like
applications, where the applications can be assumed to be able
to deal with decoding the %-escapes themselves. =20

My own guess is that, even if we discover that the specification
part of 6068 does not need modification for EAI, we are likely
to want to update the document with some very clear and specific
text, and some lurid examples, about what is expected and what
can go wrong.  In a sense, there is a meta-level Security
Consideration in this that is a bit stronger than the last few
paragraphs of Section 7: any level of carelessness in
implementations is likely to result in very bad behavior
including possible misdirection or loss of mail.

best,
   john




From Shawn.Steele@microsoft.com  Tue Nov  2 08:59:39 2010
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 777D228C139 for <ima@core3.amsl.com>; Tue,  2 Nov 2010 08:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.922
X-Spam-Level: 
X-Spam-Status: No, score=-8.922 tagged_above=-999 required=5 tests=[AWL=-1.678, BAYES_00=-2.599, FRT_ADOBE2=2.455, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3, 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 ZdRIKebocws2 for <ima@core3.amsl.com>; Tue,  2 Nov 2010 08:59:37 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id B890E28C135 for <ima@ietf.org>; Tue,  2 Nov 2010 08:59:37 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 2 Nov 2010 08:59:35 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.75]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.01.0255.003; Tue, 2 Nov 2010 08:59:35 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Thread-Topic: [EAI] mailto
Thread-Index: Act58Wx1x4hcrYzuR+Wl50MEke3+tQAmX9SAABTbFoD//48jkQ==
Date: Tue, 2 Nov 2010 15:59:34 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A0AD66@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp>, <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM>
In-Reply-To: <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jwz@jwz.org" <jwz@jwz.org>, "ima@ietf.org" <ima@ietf.org>, "Larry Masinter \\\(masinter@adobe.com\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Tue, 02 Nov 2010 15:59:39 -0000

SSB1c2VkIHVuaWNvZGVAdW5pY29kZSBpbnN0ZWFkIG9mIHV0ZjhAdXRmOCBiZWNhdXNlIHRoZSBl
bmNvZGluZyBvZiBhIGRvY3VtZW50LCBvciB0aGUgaW50ZXJuYWwgcmVwcmVzZW50YXRpb24gb2Yg
dGhlIGFkZHJlc3MsIG1heSBub3QgbmVjZXNzYXJpbHkgYmUgdXRmOC4gIChFZzogSSBkb24ndCB3
YW50IHNvbWVvbmUgdG8gc3RpY2sgdXRmOCBieXRlcyBpbiBhIHV0ZjE2IGRvY3VtZW50IDopKQ0K
DQpJIHRoaW5rIG15IGNvbmNlcm4gaXMgdGhhdCBmb3IgbWFpbHRvOiB0aGUgZGlzdGluY3Rpb24g
YmV0d2VlbiBhbiBJUkkgYW5kIFVSSSBidWNrZXQgaXMgYmx1cnJ5IHRvIHRoZSBhdmVyYWdlIGVu
ZCB1c2VyLiAgU28gSSB0aGluayB0aGF0IHNvbWUgYnVja2V0cyB0aGF0IGFyZSBub21pbmFsbHkg
VVJJJ3Mgd2lsbCBsaWtlbHkgZW5kIHVwIHdpdGggbWFpbHRvOnVuaWNvZGVAdW5pY29kZSBpbiB0
aGVtLiAgSGlzdG9yaWNhbGx5IHNvbWUgYXBwbGljYXRpb25zIGhhdmUgYmVlbiBnZW5lcm91cyBp
biB0aGUgc3RyaW5ncyB0aGV5IGFsbG93LCBzbyBJIGV4cGVjdCBub24tYXNjaWkgbWFpbHRvcyB3
aWxsIHByb2JhYmx5IGNvbnRpbnVlIHRvIHdvcmsuICBJIGRvbid0IGtub3cgaWYgdGhhdCdzIHdv
cnRoIGFja25vd2xlZGdpbmcgaW4gNjA2OC4gIEl0IG1heSBiZSAid29yc2UiIHdoZW4gcGVvcGxl
IGluYWR2ZXJ0ZW50bHkgY3V0ICYgcGFzdCBmcm9tIElSSSB0byBVUkkgb3IgVVJJIHRvIElSSS4N
Cg0KT25lIGFwcHJvYWNoIGFwcHMgY291bGQgdGFrZSBpcyB0byBwcmVzdW1lIFVURi04IChJUkkp
IGlmID4gQVNDSUkgaXMgZW5jb3VudGVyZWQsICYvb3IgcHJlc3VtZSAlIGVuY29kaW5nIChVUkkp
IGlmIHRoYXQncyBlbmNvdW50ZXJlZC4gIFRob3VnaCBKb2huIHBvaW50cyBvdXQgdGhhdCB0ZXN0
aW5nIGZvciAlIGlzbid0IGNvbXBsZXRlbHkgcmVsaWFibGUgaW4gdGhlIGxvY2FsIHBhcnQuDQoN
Ci1TaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg76Oi76Oj76OX76OU76OZDQpodHRwOi8vYmxvZ3MubXNk
bi5jb20vc2hhd25zdGUNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQpGcm9tOiBKb2huIEMgS2xlbnNpbiBba2xlbnNpbkBqY2suY29tXQ0KU2VudDogVHVlc2Rh
eSwgTm92ZW1iZXIgMDIsIDIwMTAgODozNiBBTQ0KVG86ICJNYXJ0aW4gSi4gRMO8cnN0IjsgU2hh
d24gU3RlZWxlDQpDYzogand6QGp3ei5vcmc7IGltYUBpZXRmLm9yZzsgTGFycnkgTWFzaW50ZXIg
XChtYXNpbnRlckBhZG9iZS5jb21cKQ0KU3ViamVjdDogUmU6IFtFQUldIG1haWx0bw0KDQotLU9u
IFR1ZXNkYXksIE5vdmVtYmVyIDAyLCAyMDEwIDE0OjM4ICswOTAwICJcIk1hcnRpbiBKLg0KRMO8
cnN0XCIiIDxkdWVyc3RAaXQuYW95YW1hLmFjLmpwPiB3cm90ZToNCg0KPiBPbiAyMDEwLzExLzAy
IDM6MjMsIFNoYXduIFN0ZWVsZSB3cm90ZToNCj4NCj4+IFBhcnRpY3VsYXJseSBJIHRoaW5rIHRo
YXQgdXNlcnMgYXJlIGxpa2VseSB0byBqdXN0IHVzZQ0KPj4gbWFpbHRvOnVuaWNvZGVAdW5pY29k
ZSB3aXRob3V0IGJvdGhlcmluZyB3aXRoIHRoZSAlIGVzY2FwaW5nLA0KPg0KPiBUaGUgIndpdGhv
dXQgYm90aGVyaW5nIHdpdGggdGhlICUtZXNjYXBpbmciIHBhcnQgaXMgY292ZXJlZA0KPiB3aGVy
ZSBhbiBJUkkgKGluc3RlYWQgb2Ygb25seSBhbiBVUkkgaW4gdGhlIHN0cmljdCBzZW5zZSkgaXMN
Cj4gYWNjZXB0ZWQuDQoNCk1hcnRpbiwNCg0KWWVzLiAgQnV0IHRoaXMgaXMgZXhhY3RseSB3aGVy
ZSBJIGZpbmQgc2V2ZXJhbCBvZiB0aGUgcGFyYWxsZWwNCmRpc2N1c3Npb25zIHRyb3VibGluZy4N
Cg0KKDEpIEVBSSB0aGlua3MgYW4gZW1haWwgYWRkcmVzcyBpcywgaW4gU2hhd24ncyBub3RhdGlv
biwNCnVuaWNvZGVAdW5pY29kZSAob3IgcG9zc2libHkgdW5pY29kZUBzdHJpbmctd2l0aC1BLWxh
YmVscykuICBJdA0KZG9lcyBub3QgcGVybWl0ICUtZXNjYXBlcyBpbiB0aGUgZG9tYWluIG5hbWUg
YW5kIG1hbnkgbWFpbA0Kc3lzdGVtcyB3aWxsIGludGVycHJldCAlLXNpZ25zIGluIHRoZSBsb2Nh
bCBwYXJ0IGFzIHNvbWV0aGluZw0KZWxzZSBlbnRpcmVseSwgZS5nLiwgcm91dGluZyBpbmZvcm1h
dGlvbi4NCg0KKDIpIEZvciBhbiBJUkksIG1haWx0bzp1bmljb2RlQHVuaWNvZGUgaXMgcGVyZmVj
dGx5IHJlYXNvbmFibGUuDQpIb3dldmVyLCB0aGUgbWFwcGluZyB0byBhIFVSSSwgdW5sZXNzIGl0
IGlzIHNjaGVtZS9wcm90b2NvbA0KZGVwZW5kZW50LCBpcyBsaWtlbHkgdG8gcHJvZHVjZSBlaXRo
ZXINCiAgIG1haWx0bzolLWVzY2FwZXNAJS1lc2NhcGVzDQpvcg0KICAgbWFpbHRvOiUtZXNjYXBl
c0BzdHJpbmctd2l0aC1BLWxhYmVscw0KDQpCb3RoIG9mIHdoaWNoIGFyZSByZWFsbHkgYmFkIG5l
d3MgaWYgb25lIHRyaWVzIHRvIGdldCBmcm9tDQptYWlsdG86U3RyaW5nIHRvIGFuIGVtYWlsIGFk
ZHJlc3MgYnkgZHJvcHBpbmcgdGhlIG1haWx0byBhbmQNCmxlYXZpbmcgU3RyaW5nLg0KDQpJIHRo
aW5rIHRoYXQgbWVhbnMgdGhhdCBhbnkgc29ydCBvZiBpMThuIE1BSUxUTyBwcm9jZXNzb3IgaGFz
IHRvDQpnZXQgZnJvbSB0aG9zZSBmb3JtcyBiYWNrIHRvIHRoZSBub24tZXNjYXBlZCBVbmljb2Rl
LWluLVVURi04DQpzdHJpbmdzIHRoYXQgRUFJIGV4cGVjdHMgYmVmb3JlIHBhc3NpbmcgYW4gaW50
ZXJuYXRpb25hbGl6ZWQNCmFkZHJlc3Mgb2ZmIHRvIGEgbWFpbC1zZW5kaW5nIG9yIHByb2Nlc3Np
bmcgb3BlcmF0aW9uLiAgIElmIG9uZQ0KcmVhZHMgdGhlIHNlY29uZCBwYXJhZ3JhcGggb2YgU2Vj
dGlvbiA1IG9mIFJGQyA2MDY4IChhbmQgdGhlDQp3YXJuaW5nIGluIHRoZSB0aGlyZC10by1sYXN0
IHBhcmFncmFwaCBvZiBTZWN0aW9uIDcpLCBvbmUgY2FuDQpjbGFpbSB0aGF0IGlzIGltcGxpZWQg
dGhlcmUsIGJ1dCBpdCBpcyBkaWZmaWN1bHQgKGF0IGJlc3QpIHRvDQpwYXJzZSB0aGF0IGV4YWN0
IG1lYW5pbmcgb3V0IGZyb20gdGhlIGNvbnZvbHV0ZWQgbGFuZ3VhZ2UgdGhhdA0Kd2FzIHVzZWQs
IHByZXN1bWFibHkgdG8gYXZvaWQgYSBub3JtYXRpdmUgcmVmZXJlbmNlIHRvIHRoZSBFQUkNCnNw
ZWNzLg0KDQpOb3RlIHRoYXQgdGhpcyBpcyBhIGtleSBkaWZmZXJlbmNlIGZyb20gd2ViIGFuZCB3
ZWItbGlrZQ0KYXBwbGljYXRpb25zLCB3aGVyZSB0aGUgYXBwbGljYXRpb25zIGNhbiBiZSBhc3N1
bWVkIHRvIGJlIGFibGUNCnRvIGRlYWwgd2l0aCBkZWNvZGluZyB0aGUgJS1lc2NhcGVzIHRoZW1z
ZWx2ZXMuDQoNCk15IG93biBndWVzcyBpcyB0aGF0LCBldmVuIGlmIHdlIGRpc2NvdmVyIHRoYXQg
dGhlIHNwZWNpZmljYXRpb24NCnBhcnQgb2YgNjA2OCBkb2VzIG5vdCBuZWVkIG1vZGlmaWNhdGlv
biBmb3IgRUFJLCB3ZSBhcmUgbGlrZWx5DQp0byB3YW50IHRvIHVwZGF0ZSB0aGUgZG9jdW1lbnQg
d2l0aCBzb21lIHZlcnkgY2xlYXIgYW5kIHNwZWNpZmljDQp0ZXh0LCBhbmQgc29tZSBsdXJpZCBl
eGFtcGxlcywgYWJvdXQgd2hhdCBpcyBleHBlY3RlZCBhbmQgd2hhdA0KY2FuIGdvIHdyb25nLiAg
SW4gYSBzZW5zZSwgdGhlcmUgaXMgYSBtZXRhLWxldmVsIFNlY3VyaXR5DQpDb25zaWRlcmF0aW9u
IGluIHRoaXMgdGhhdCBpcyBhIGJpdCBzdHJvbmdlciB0aGFuIHRoZSBsYXN0IGZldw0KcGFyYWdy
YXBocyBvZiBTZWN0aW9uIDc6IGFueSBsZXZlbCBvZiBjYXJlbGVzc25lc3MgaW4NCmltcGxlbWVu
dGF0aW9ucyBpcyBsaWtlbHkgdG8gcmVzdWx0IGluIHZlcnkgYmFkIGJlaGF2aW9yDQppbmNsdWRp
bmcgcG9zc2libGUgbWlzZGlyZWN0aW9uIG9yIGxvc3Mgb2YgbWFpbC4NCg0KYmVzdCwNCiAgIGpv
aG4=

From klensin@jck.com  Tue Nov  2 09:17:09 2010
Return-Path: <klensin@jck.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 2FA933A6883 for <ima@core3.amsl.com>; Tue,  2 Nov 2010 09:17:09 -0700 (PDT)
X-Quarantine-ID: <xRKe-iwrzJ0K>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace: References: ...mond.corp.microsoft.com>\n  \n <4CCFA3F3.907[...]
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 xRKe-iwrzJ0K for <ima@core3.amsl.com>; Tue,  2 Nov 2010 09:17:08 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 175EC3A68D8 for <ima@ietf.org>; Tue,  2 Nov 2010 09:17:08 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PDJXj-000KPM-Ih; Tue, 02 Nov 2010 12:17:03 -0400
Date: Tue, 02 Nov 2010 12:17:02 -0400
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>
Message-ID: <551A6D579DDE9C42DF83CAF4@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A0AD66@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp> ,<DAB0CCE35AA1AF33C35E209A@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A10A0AD66@TK5EX14MBXC141.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: jwz@jwz.org, ima@ietf.org, Larry Masinter <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Tue, 02 Nov 2010 16:17:09 -0000

--On Tuesday, November 02, 2010 15:59 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> I used unicode@unicode instead of utf8@utf8 because the
> encoding of a document, or the internal representation of the
> address, may not necessarily be utf8.  (Eg: I don't want
> someone to stick utf8 bytes in a utf16 document :))

Understood.  But we've said pretty strongly that we prefer UTF-8
in EAI addresses on the wire and in text on the wire more
generally.  So, even though I know there will be exceptions
(some deliberate, some screw-ups), I hope that utf16 document is
transmitted in utf8 no matter how it is stored.

> I think my concern is that for mailto: the distinction between
> an IRI and URI bucket is blurry to the average end user.

While mailto: may be worse than some hypothetical average case,
I think that distinction will _always_ be blurry to the "average
end user". One could even argue that it is designed to be
blurry: if it were not, we would have at least made some
modification to the structural syntax that would permit a parser
or not-very-bright end user to easily identify which is which.  

This is one of those situations in which the obvious cases,
especially with the HTTP and HTTPS schemes, will work fine but
the edge cases get nasty.  In some ways and because of the
history and necessity of "no one but the delivery server gets to
interpret a local-part" rule, mailto: is sort of a breeder of
edge cases but I'm not sure it is all that special.

That is ultimately one of the two reasons I've considered the
whole IRI approach the wrong way to go since the beginning, but,
since that position has gotten no traction, I think we need to
try to make it work.   That doesn't stop me from thinking that
doing so will be risky and potentially very hard for UIs that
have to force end lusers into making distinctions that may not
make sense to them.
 
>  So I
> think that some buckets that are nominally URI's will likely
> end up with mailto:unicode@unicode in them.

Yes.  Almost certainly, especially for addresses embedded in
text, signature lines, etc.

>  Historically some
> applications have been generous in the strings they allow, so
> I expect non-ascii mailtos will probably continue to work.  I
> don't know if that's worth acknowledging in 6068.  It may be
> "worse" when people inadvertently cut & past from IRI to URI
> or URI to IRI.

I expect so.  And at least cautionary notes in an update to 6068
are what I had in mind in my earlier note.

> One approach apps could take is to presume UTF-8 (IRI) if >
> ASCII is encountered, &/or presume % encoding (URI) if that's
> encountered.  Though John points out that testing for % isn't
> completely reliable in the local part.

In particular, foo%20@example.net and foo%25@example.com are
perfectly valid, 5321- and 5322-conforming, email addresses.
The the first one might be interpreted as a route via "20"
(whatever that meant) and the second as a mailbox name, or vice
versa.  Interpreting either as an IRI or URI containing
%-escapes would be bad news.   Again, I think 6028 actually has
this right, but only for a reader who is exceptionally careful.
For others, the whole situation is a trap for the unwary.

     john


From klensin@jck.com  Thu Nov  4 03:13:10 2010
Return-Path: <klensin@jck.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 5F6B83A69EB for <ima@core3.amsl.com>; Thu,  4 Nov 2010 03:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[AWL=-0.404, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
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 aucOyYEujW7c for <ima@core3.amsl.com>; Thu,  4 Nov 2010 03:13:09 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 51A743A6A00 for <ima@ietf.org>; Thu,  4 Nov 2010 03:12:19 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PDwnx-000NVs-OP; Thu, 04 Nov 2010 06:12:27 -0400
Date: Wed, 03 Nov 2010 21:06:38 -0400
From: John C Klensin <klensin@jck.com>
To: Pete Resnick <presnick@qualcomm.com>, ima@ietf.org
Message-ID: <392E2730FE04A8088C018668@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <4CC85DD5.2060701@qualcomm.com>
References: <4CC85DD5.2060701@qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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: Thu, 04 Nov 2010 10:13:10 -0000

--On Wednesday, 27 October, 2010 12:13 -0500 Pete Resnick
<presnick@qualcomm.com> wrote:

> I sent these comments to Fujiwara-san, but forgot to send them
> to the list. Issues we need to deal with:
>=20
> 1. Now that we are allowing the downgrade of "From:" and
> "Resent-From:" without an alt-address, we must point out that
> RFC 5322 does *not* allow group syntax in "From:" and
> "Resent-From:" and that this document changes that syntax. I
> think that is fine to do that, but this document needs to
> explicitly say that. Perhaps something like this:
>...

Pete, I'm less confident about this.  Remember that the purpose
of any downgrade function is to make the message acceptable to
legacy systems, especially standards-conforming ones.  For
several reasons, I'd assume that there are competent (and
conforming) MUAs out there that would get very annoyed upon
seeing group syntax in those fields.

It may still be the best solution for us but, if it is, we need
more than the syntax change text that you suggest.  We need,
IMO, an explicit analysis and warning about what might occur,
either inline or in Security Considerations.

> 2. MAILBOX downgrading makes group syntax recursive for other
> address fields. This one I'm less confident about. But let's
> say you get a message like this:
>=20
> To: My Friends: <=E5=A7=9A=E5=81=A5=E5=BA=B7@cnnic.cn>, =
<=E6=9D=8E=E6=99=93=E4=B8=9C@cnnic.cn>;
>=20
> According to the rules, you downgrade this to:
>=20
> To: MyFriends: Internationalized Address <<Yao's 2047
> address>> Removed:;, Internationalized Address <<Xiaodong's
> 2047 address>> Removed:;
>=20
> I think this is OK, but it changes the syntax of group to:
>=20
> group =3D display-name ":" [group / group-list] ";" [CFWS]
>=20
> If everyone is OK with this, it should go in the document
> somewhere.

Same comment as above, only more so.  Remember how many MUAs
(including one with which you are very familiar) went for years
without being able to handle group syntax properly and then
contemplate what might happen with this modification, especially
if it is misparsed by a legacy system and the MUA tries to "fix
things up" in the name of robustness.

     john


From klensin@jck.com  Thu Nov  4 03:13:10 2010
Return-Path: <klensin@jck.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 84EDC3A69EC for <ima@core3.amsl.com>; Thu,  4 Nov 2010 03:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[AWL=-0.370,  BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
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 lz4C-uZ4R-wX for <ima@core3.amsl.com>; Thu,  4 Nov 2010 03:13:09 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 874413A69FB for <ima@ietf.org>; Thu,  4 Nov 2010 03:12:26 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PDwo7-000NVs-MQ; Thu, 04 Nov 2010 06:12:36 -0400
Date: Wed, 03 Nov 2010 20:29:20 -0400
From: John C Klensin <klensin@jck.com>
To: Joseph Yee <joseph.yee@gmail.com>, ima@ietf.org
Message-ID: <EF9DA23DF9A3F1A3A0B492F9@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <AANLkTingL=HLAd2T3r_ZNs3Qdc3KBLwJr9xJvnPCFxCZ@mail.gmail.com>
References: <E14011F8737B524BB564B05FF748464A109B76CB@TK5EX14MBXC141.redmond.corp.microsoft.com> <488146827.09914@cnnic.cn> <488190761.22975@cnnic.cn> <AANLkTi=8tc_3JfUGj2hzV1n7CtxX-jv8YowK9vheieCU@mail.gmail.com> <AANLkTingL=HLAd2T3r_ZNs3Qdc3KBLwJr9xJvnPCFxCZ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: Re: [EAI] Fwd:  Minor comments
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: Thu, 04 Nov 2010 10:13:10 -0000

--On Wednesday, 27 October, 2010 11:03 -0400 Joseph Yee
<joseph.yee@gmail.com> wrote:

> Let's stay consistent with previous RFC. =C2=A0RFC5321 uses =
"an"
> instead of "a".

<Co-chair hat on>
Folks, sorry for stepping into this so late, but I want to
strongly reinforce Joseph's comment and carry it a bit further.
Defining and enforcing a consistent style for the RFC Series is
the job of the RFC Editor staff and they are _very_ good at it.
Raising this sort of point and debating it is a distraction for
the WG because whatever decision we make, the RFC Editor will
apply their rules, style manual, and taste. =20

If I were convinced that we had no substantive issues with any
of these documents and that everyone had read them and was happy
about them, the distraction would be trivial or even amusing.
But there is not a lot of evidence that is true.

So, if you have small editorial suggestions like this, please
just drop a note to the author.  If the author feels that it is
worth a debate on the list, let him raise it.  Or, if the author
wants an advisory opinion from the RFC Editor, we can try to get
that.

thanks,
     john


thanks,
   john




From duerst@it.aoyama.ac.jp  Thu Nov  4 04:49:52 2010
Return-Path: <duerst@it.aoyama.ac.jp>
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 5F07128C101 for <ima@core3.amsl.com>; Thu,  4 Nov 2010 04:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.602
X-Spam-Level: 
X-Spam-Status: No, score=-100.602 tagged_above=-999 required=5 tests=[AWL=-1.412, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3, 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 kIM3BAoQmie1 for <ima@core3.amsl.com>; Thu,  4 Nov 2010 04:49:51 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id E14733A6866 for <ima@ietf.org>; Thu,  4 Nov 2010 04:49:50 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oA4BnqZP015164 for <ima@ietf.org>; Thu, 4 Nov 2010 20:49:53 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 69bd_c840_a2d5b41e_e809_11df_8f5a_001d096c5782; Thu, 04 Nov 2010 20:49:52 +0900
Received: from [IPv6:::1] ([133.2.210.1]:41716) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S147C7D2> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 4 Nov 2010 20:49:51 +0900
Message-ID: <4CD29DD3.4070103@it.aoyama.ac.jp>
Date: Thu, 04 Nov 2010 20:49:39 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp> <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM>
In-Reply-To: <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: jwz@jwz.org, Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, "Larry Masinter \\\(masinter@adobe.com\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Thu, 04 Nov 2010 11:49:52 -0000

Hello John,

On 2010/11/03 0:36, John C Klensin wrote:
>
>
> --On Tuesday, November 02, 2010 14:38 +0900 "\"Martin J.
> DÃ¼rst\""<duerst@it.aoyama.ac.jp>  wrote:
>
>> On 2010/11/02 3:23, Shawn Steele wrote:
>>
>>> Particularly I think that users are likely to just use
>>> mailto:unicode@unicode without bothering with the % escaping,
>>
>> The "without bothering with the %-escaping" part is covered
>> where an IRI (instead of only an URI in the strict sense) is
>> accepted.
>
> Martin,
>
> Yes.  But this is exactly where I find several of the parallel
> discussions troubling.
>
> (1) EAI thinks an email address is, in Shawn's notation,
> unicode@unicode (or possibly unicode@string-with-A-labels).  It
> does not permit %-escapes in the domain name and many mail
> systems will interpret %-signs in the local part as something
> else entirely, e.g., routing information.

Yes. Except that it was ascii@ascii, that has been the same since ages.

> (2) For an IRI, mailto:unicode@unicode is perfectly reasonable.
> However, the mapping to a URI, unless it is scheme/protocol
> dependent, is likely to produce either
>     mailto:%-escapes@%-escapes
> or
>     mailto:%-escapes@string-with-A-labels
>
> Both of which are really bad news if one tries to get from
> mailto:String to an email address by dropping the mailto and
> leaving String.

Yes. But please note that it has never been possible to get from 
"mailto:String" to the email address simply by dropping "mailto:". In 
particular, RFC 2368 (which is more than 12 years old and strictly and 
purely about ASCII-only mail addresses only) says, in Section 2:

                                                 Note that all URL
    reserved characters in "to" must be encoded: in particular,
    parentheses, commas, and the percent sign ("%"), which commonly occur
    in the "mailbox" syntax.

So your troubling "parallel discussions" may be mostly due to some 
people having read the specs, and others not. I seriously recommend you 
to read RFC 2368; you may (but should not) be surprised at how much text 
comes directly from there.


> I think that means that any sort of i18n MAILTO processor has to
> get from those forms back to the non-escaped Unicode-in-UTF-8
> strings that EAI expects before passing an internationalized
> address off to a mail-sending or processing operation.

Yes. If it simply implements %-decoding, without looking at the byte 
values, it will easily get the UTF-8 strings (Unicode-in-UTF-8 is a 
pleonasm). So EAI will be happy. What may go wrong is where this UTF-8 
string hits an non-EAI mail agent.

If the mailto processor implements some ASCII-only checking on top of 
%-decoding, then there will be some error. But one should assume that 
this check will be eliminated by whoever implements EAI. In case we are 
dealing with a non-EAI mail agent, raising an error of some kind will of 
course be the right thing to do.


> If one
> reads the second paragraph of Section 5 of RFC 6068 (and the
> warning in the third-to-last paragraph of Section 7),

I would also like to point to the many examples in Section 6, for example:

    To indicate the address "gorby%kremvax@example.com" one would use:

    <mailto:gorby%25kremvax@example.com>

While the example section is written for people who generate mailto: 
URIs from mail addresses, it shouldn't be too difficult to turn these 
examples around, implicitly reading them e.g.:

    The address indicated by the mailto: URI
    <mailto:gorby%25kremvax@example.com> is "gorby%kremvax@example.com".


> one can
> claim that is implied there, but it is difficult (at best) to
> parse that exact meaning out from the convoluted language that
> was used,

If you have any proposals to improve the language and make it easier to 
understand, I'll be happy to integrate them.


> presumably to avoid a normative reference to the EAI
> specs.

This presumption is wrong. Escaping and unescaping the components of 
(mailto:) URIs is something that was done since long ago.

The only part where so "convolution" was used to avoid a reference to 
EAI was in Section two, in the item that starts with:

    5.  Percent-encoding of non-ASCII octets in the <local-part> of an
        <addr-spec> is reserved for the internationalization of the
        <local-part>.


> Note that this is a key difference from web and web-like
> applications, where the applications can be assumed to be able
> to deal with decoding the %-escapes themselves.

No, there is no such key difference. URIs (and IRIs) can contain 
%-escapes, and any software (be that Web-like or not) taking apart an 
URI and using its components has to know how to deal with these. This is 
the same since ages, and RFC 6068 didn't change anything.


> My own guess is that, even if we discover that the specification
> part of 6068 does not need modification for EAI, we are likely
> to want to update the document with some very clear and specific
> text, and some lurid examples, about what is expected and what
> can go wrong.

I don't mind adding more examples and clarifications. Any text appreciated.


> In a sense, there is a meta-level Security
> Consideration in this that is a bit stronger than the last few
> paragraphs of Section 7: any level of carelessness in
> implementations is likely to result in very bad behavior
> including possible misdirection or loss of mail.


Regards,    Martin.

-- 
#-# Martin J. DÃ¼rst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From klensin@jck.com  Thu Nov  4 11:16:16 2010
Return-Path: <klensin@jck.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 A4C6628C0FA for <ima@core3.amsl.com>; Thu,  4 Nov 2010 11:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level: 
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3]
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 lQkmKeUfeJAO for <ima@core3.amsl.com>; Thu,  4 Nov 2010 11:16:15 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 3C00A28C0DB for <ima@ietf.org>; Thu,  4 Nov 2010 11:16:15 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PE4M5-000Bqa-PV; Thu, 04 Nov 2010 14:16:10 -0400
Date: Thu, 04 Nov 2010 14:16:06 -0400
From: John C Klensin <klensin@jck.com>
To: =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>
Message-ID: <2BCA27C2130A1C6CD0691A6F@JcK-eee10>
In-Reply-To: <4CD29DD3.4070103@it.aoyama.ac.jp>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp> <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM> <4CD29DD3.4070103@it.aoyama.ac.jp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: jwz@jwz.org, Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, "Larry Masinter \\\\\(masinter@adobe.com\\\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Thu, 04 Nov 2010 18:16:16 -0000

Hi, Martin,

--On Thursday, 04 November, 2010 20:49 +0900 "\"Martin J.
D=C3=BCrst\"" <duerst@it.aoyama.ac.jp> wrote:

>...
>> (1) EAI thinks an email address is, in Shawn's notation,
>> unicode@unicode (or possibly unicode@string-with-A-labels).
>> It does not permit %-escapes in the domain name and many mail
>> systems will interpret %-signs in the local part as something
>> else entirely, e.g., routing information.
>=20
> Yes. Except that it was ascii@ascii, that has been the same
> since ages.

And there have been email implementations for a decade or two
(even if not "ages") who, in the name of "8-bit-clean" or
interpretations of the robustness principle (with which I'm not
personally sympathetic) have been accepting non-ASCII (and often
non-Unicode) strings and trying to make them work.   And they
have worked in local environments and by prior agreement -- the
discussion in draft-iab-idn-encoding applies here too.

>> (2) For an IRI, mailto:unicode@unicode is perfectly
>> reasonable. However, the mapping to a URI, unless it is
>> scheme/protocol dependent, is likely to produce either
>>     mailto:%-escapes@%-escapes
>> or
>>     mailto:%-escapes@string-with-A-labels
>>=20
>> Both of which are really bad news if one tries to get from
>> mailto:String to an email address by dropping the mailto and
>> leaving String.
>=20
> Yes. But please note that it has never been possible to get
> from "mailto:String" to the email address simply by dropping
> "mailto:".=20

You mean "never valid", not "never possible", don't you?  I
could introduce you to several large financial and "e-business"
operations that do it many times a day. =20

While I'm often an advocate of "let those who violated the
standard deal with their own messes when we do something that
tightens or enforces the rules" and think it applies here, we
need to understand what we are getting ourselves into with this.

> In particular, RFC 2368 (which is more than 12
> years old and strictly and purely about ASCII-only mail
> addresses only) says, in Section 2:
>...
=20
> So your troubling "parallel discussions" may be mostly due to
> some people having read the specs, and others not. I seriously
> recommend you to read RFC 2368; you may (but should not) be
> surprised at how much text comes directly from there.

I have read it and know what it says.  I am not only concerned
about those who have not but about those who deliberately have
ignored its provisions, secure in the belief that we will never
do anything that has bad consequences for them.  See above.=20

>> I think that means that any sort of i18n MAILTO processor has
>> to get from those forms back to the non-escaped
>> Unicode-in-UTF-8 strings that EAI expects before passing an
>> internationalized address off to a mail-sending or processing
>> operation.
>=20
> Yes. If it simply implements %-decoding, without looking at
> the byte values, it will easily get the UTF-8 strings
> (Unicode-in-UTF-8 is a pleonasm).=20

Having run into a file about two weeks ago that had apparently
started life as BIG5 and then had the same transformation that
UTF-8 uses applied to it, and then was shipped with a
content-type of "UTF-8" (according to the guilty party, because
there is no registration for "B5UTF-8" or equivalent) please
forgive me if I sometimes add detail that should not be
necessary.

> So EAI will be happy. What
> may go wrong is where this UTF-8 string hits an non-EAI mail
> agent.

yes

>...
>> If one
>> reads the second paragraph of Section 5 of RFC 6068 (and the
>> warning in the third-to-last paragraph of Section 7),
>=20
> I would also like to point to the many examples in Section 6,
> for example:
>...
> While the example section is written for people who generate
> mailto: URIs from mail addresses, it shouldn't be too
> difficult to turn these examples around, implicitly reading
> them e.g.:
>...

Right.  But the point was that some of the key examples are not
present for EAI purposes and may  create some false sense of
security, not that the existing examples are incorrect in any
way.

>...
> If you have any proposals to improve the language and make it
> easier to understand, I'll be happy to integrate them.

And I'll be happy to look at it _after_ EAI completes all of the
decision-making that might bear on it.

>...
>> Note that this is a key difference from web and web-like
>> applications, where the applications can be assumed to be =
able
>> to deal with decoding the %-escapes themselves.
>=20
> No, there is no such key difference. URIs (and IRIs) can
> contain %-escapes, and any software (be that Web-like or not)
> taking apart an URI and using its components has to know how
> to deal with these. This is the same since ages, and RFC 6068
> didn't change anything.

But that was exactly the point.  Web-like applications take URIs
and use their components natively.   Mail applications generally
don't, so we are dealing with the need for a method-specific
decoding intermediary.  And, if the folks who do those are not
familiar with both the MAILTO spec and the mail ones (or read
the MAILTO spec very carefully and conform exactly even without
knowing what they are doing), or if they are in a hurry and
don't care, bad things can happen that are excluded in the
"application deals with URIs directly" cases.

>...

best,
   john




From Shawn.Steele@microsoft.com  Thu Nov  4 11:24:17 2010
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 4E2793A6A30 for <ima@core3.amsl.com>; Thu,  4 Nov 2010 11:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.61
X-Spam-Level: 
X-Spam-Status: No, score=-9.61 tagged_above=-999 required=5 tests=[AWL=0.689,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 pyt25JSUSGmH for <ima@core3.amsl.com>; Thu,  4 Nov 2010 11:24:16 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 99D9A3A692A for <ima@ietf.org>; Thu,  4 Nov 2010 11:24:16 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 4 Nov 2010 11:24:27 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.75]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.01.0255.003; Thu, 4 Nov 2010 11:24:26 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Thread-Topic: [EAI] mailto
Thread-Index: Act58Wx1x4hcrYzuR+Wl50MEke3+tQAmX9SAABTbFoAAXKwkgAANfyIAAA5zqeA=
Date: Thu, 4 Nov 2010 18:24:26 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A20138@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp> <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM> <4CD29DD3.4070103@it.aoyama.ac.jp> <2BCA27C2130A1C6CD0691A6F@JcK-eee10>
In-Reply-To: <2BCA27C2130A1C6CD0691A6F@JcK-eee10>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jwz@jwz.org" <jwz@jwz.org>, "ima@ietf.org" <ima@ietf.org>, "Larry Masinter \\\\\(masinter@adobe.com\\\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Thu, 04 Nov 2010 18:24:17 -0000

PiBTbyB5b3VyIHRyb3VibGluZyAicGFyYWxsZWwgZGlzY3Vzc2lvbnMiIG1heSBiZSBtb3N0bHkg
ZHVlIHRvIHNvbWUgDQo+IHBlb3BsZSBoYXZpbmcgcmVhZCB0aGUgc3BlY3MsIGFuZCBvdGhlcnMg
bm90LiANCg0KUGFydCBvZiB0aGUgcHJvYmxlbSBpcyB0aGF0IDk5LjklIG9mIHRoZSBwZW9wbGUg
dGhhdCB1c2UgbWFpbHRvOiBoYXZlbid0IHJlYWQgdGhlIHNwZWNzLiAgUGFydGljdWxhcmx5IHdo
ZW4gaXQncyB1c2VkIGluIHBsYWluLXRleHQuICBFZzogYW4gZW1haWwgbWVzc2FnZS4gIEluIHRo
YXQgY2FzZSBpdCBnZXRzIHNlZW4gYnkgYW4gZW5kIHVzZXIuICBJJ2QgZGlzYWdyZWUgd2l0aCBK
b2huIHRoYXQgdGhlIHJpZ2h0IGFwcHJvYWNoIGlzIHRvIGp1c3QgbGV0IHRoZW0gbGl2ZSBpbiB0
aGUgbWVzcyB1bnRpbCB0aGV5IGNvbXBseSB3aXRoIHRoZSBzdGFuZGFyZHMuICBJbnN0ZWFkIGl0
IG1pZ2h0IGJlIHdpc2UgZm9yIHRoZSBzdGFuZGFyZCB0byBhY2tub3dsZWRnZSB0aGF0IGluIDgg
Yml0IGVudmlyb25tZW50cywgdGhlcmUgbWF5IGJlIGluZm9ybWF0aW9uIGluIHRoZSA4dGggYml0
IHRoYXQgcGVvcGxlIGFyZSB1c2luZy4NCg0KLVNoYXduDQoNCg==

From klensin@jck.com  Thu Nov  4 12:03:26 2010
Return-Path: <klensin@jck.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 2AF643A6A39 for <ima@core3.amsl.com>; Thu,  4 Nov 2010 12:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 QXzYWHKv65Ud for <ima@core3.amsl.com>; Thu,  4 Nov 2010 12:03:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 3B7EB3A6935 for <ima@ietf.org>; Thu,  4 Nov 2010 12:03:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PE55r-000Czc-3M; Thu, 04 Nov 2010 15:03:27 -0400
Date: Thu, 04 Nov 2010 15:03:24 -0400
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>
Message-ID: <00B079EFD71F4B6067F97D67@JcK-eee10>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A20138@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A109F3625@TK5EX14MBXC137.redmond.corp.microsoft.com> <4CCFA3F3.9070305@it.aoyama.ac.jp> <DAB0CCE35AA1AF33C35E209A@PST.JCK.COM> <4CD29DD3.4070103@it.aoyama.ac.jp> <2BCA27C2130A1C6CD0691A6F@JcK-eee10> <E14011F8737B524BB564B05FF748464A10A20138@TK5EX14MBXC141.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: jwz@jwz.org, ima@ietf.org, "Larry Masinter \\\\\\\\\(masinter@adobe.com\\\\\\\\\)" <masinter@adobe.com>
Subject: Re: [EAI] mailto
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: Thu, 04 Nov 2010 19:03:26 -0000

--On Thursday, 04 November, 2010 18:24 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>> So your troubling "parallel discussions" may be mostly due to
>> some  people having read the specs, and others not. 
> 
> Part of the problem is that 99.9% of the people that use
> mailto: haven't read the specs.  Particularly when it's used
> in plain-text.  Eg: an email message.  In that case it gets
> seen by an end user.  I'd disagree with John that the right
> approach is to just let them live in the mess until they
> comply with the standards.  Instead it might be wise for the
> standard to acknowledge that in 8 bit environments, there may
> be information in the 8th bit that people are using.

Shawn, no disagreement (and sorry if I wasn't clear).   I think
there are places where it is appropriate to say "let them live
in the mess" and move on.  Probably I think there are more of
those places than you do.  But, in this case, I pretty much
agree with your 99.9% if only because I see things starting with
"mailto:" in signature blocks that are clearly constructed by
people who think they are being clever and elegant and who
assume they know what is in the spec without having a clue where
they would even find it.

I think that is a relevant part of the difference here.  While
there is a formal/systematic definition for mailto: that is
quite well done and that, if read carefully, covers all the
cases, what it defines is a part of user-level syntax.
Expecting end users to understand those subtleties in something
they think they can type is very different from expecting
someone who is implementing SMTP or EAI to have read the spec.
If nothing else, if someone doing those implementations doesn't
read the spec, negative reinforcement will arrive quickly.  For
mailto:, end users and people pretty close to them in skill have
thought they knew what the spec required and permitted, and been
wrong, for, using Martin's term, ages.

    john




From simon.perreault@viagenie.ca  Fri Nov  5 06:55:21 2010
Return-Path: <simon.perreault@viagenie.ca>
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 D6D103A693F; Fri,  5 Nov 2010 06:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 hcf6VpwKkQE9; Fri,  5 Nov 2010 06:55:20 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id C856B3A694A; Fri,  5 Nov 2010 06:55:20 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:b82a:d3a0:34a5:db78]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2C41720CF1; Fri,  5 Nov 2010 09:55:33 -0400 (EDT)
Message-ID: <4CD40CD4.3090503@viagenie.ca>
Date: Fri, 05 Nov 2010 09:55:32 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc14 Thunderbird/3.1.6
MIME-Version: 1.0
To: ima@ietf.org
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: vcarddav@ietf.org
Subject: [EAI] Internationalized email addresses in vCard 4.0
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, 05 Nov 2010 13:55:21 -0000

Hello,

We need some advice from the EAI working group.

vCard 4.0 is a file format for contact information. It's a textual
format and its character set is always UTF-8. One of the information
items it may contain is email addresses. See here:
http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-13#section-6.4.2

Basically to list an email address in a vCard you will have a line
looking like this:

EMAIL:jdoe@example.com

The ABNF for what comes after the colon is "addr-spec", which is defined
in RFC 5322, section 3.4.1.

Now, addr-spec does not allow full Unicode. An internationalized address
would need to be EAI/IDN-encoded, which implies that a vCard app would
need to decode it to display it to a user.

Questions:
- Is this the right way to do it?
- Should we allow full Unicode, which removes the need for decoding from
the vCard app and adds the need for encoding in the MUA?
- Should both forms be possible, should one form be preferred over the
other, or should only one form be allowed?
- What should the ABNF look like for allowing Unicode characters in
email addresses?
- Would it help us in any way if we were to specify a mailto: URL instead?

Thanks,
Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org

From klensin@jck.com  Fri Nov  5 15:41:38 2010
Return-Path: <klensin@jck.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 AD2C43A695A; Fri,  5 Nov 2010 15:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.409
X-Spam-Level: 
X-Spam-Status: No, score=-2.409 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599]
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 jDp+WoA7RvwK; Fri,  5 Nov 2010 15:41:37 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id C490C3A6912; Fri,  5 Nov 2010 15:41:33 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PEUyg-0000v3-E1; Fri, 05 Nov 2010 18:41:46 -0400
Date: Fri, 05 Nov 2010 18:41:44 -0400
From: John C Klensin <klensin@jck.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, ima@ietf.org
Message-ID: <84E442EF93DA69A676651D8E@[10.40.72.147]>
In-Reply-To: <4CD40CD4.3090503@viagenie.ca>
References: <4CD40CD4.3090503@viagenie.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: vcarddav@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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, 05 Nov 2010 22:41:39 -0000

--On Friday, 05 November, 2010 09:55 -0400 Simon Perreault
<simon.perreault@viagenie.ca> wrote:

> Hello,
> 
> We need some advice from the EAI working group.
> 
> vCard 4.0 is a file format for contact information. It's a
> textual format and its character set is always UTF-8. One of
> the information items it may contain is email addresses. See
> here:
> http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-13#sec
> tion-6.4.2
> 
> Basically to list an email address in a vCard you will have a
> line looking like this:
> 
> EMAIL:jdoe@example.com
> 
> The ABNF for what comes after the colon is "addr-spec", which
> is defined in RFC 5322, section 3.4.1.
> 
> Now, addr-spec does not allow full Unicode. An
> internationalized address would need to be EAI/IDN-encoded,
> which implies that a vCard app would need to decode it to
> display it to a user.

Except that you misunderstand what "EAI/IDN encoding". I would
strongly suggest that you have a look at the EAI drafts and that
you deal with this by replacing the 5322 addr-spec with the EAI
equivalent.  Otherwise, you are just going to create trouble for
yourselves and your users.

> Questions:
> - Is this the right way to do it?

Nope.  See above.

> - Should we allow full Unicode, which removes the need for
> decoding from the vCard app and adds the need for encoding in
> the MUA?

No, and you are asking the wrong question.  See above.

> - Should both forms be possible, should one form be
> preferred over the other, or should only one form be allowed?

What "both forms"?

> - What should the ABNF look like for allowing Unicode
> characters in email addresses?

See above.  Your one problem is that you will end up with a
normative reference with a spec that isn't finished yet.  The
good news is that I hope and expect to have it wrapped up well
before the end of the calendar year.

> - Would it help us in any way if we were to specify a mailto:
> URL instead?

Arggh.  Translation: certainly not unless you want to wait for
the EAI WG to finish its review of mailto, which has not really
begun yet.

     john



From Shawn.Steele@microsoft.com  Fri Nov  5 16:08:29 2010
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 E00D13A6965 for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.99
X-Spam-Level: 
X-Spam-Status: No, score=-9.99 tagged_above=-999 required=5 tests=[AWL=0.609,  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 mhRA11vvGHxQ for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:08:28 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 8CF6C3A6960 for <ima@ietf.org>; Fri,  5 Nov 2010 16:08:28 -0700 (PDT)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 5 Nov 2010 16:08:42 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.222]) by TK5EX14HUBC105.redmond.corp.microsoft.com ([157.54.80.48]) with mapi id 14.01.0255.003; Fri, 5 Nov 2010 16:08:42 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Internationalized email addresses in vCard 4.0
Thread-Index: Act9PUcri5AzOC7GQeO9Kqa7u9cjpg==
Date: Fri, 5 Nov 2010 23:08:41 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A3B145@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.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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, 05 Nov 2010 23:08:30 -0000

It should really just allow full UTF-8.  I don't know enough about vCard to=
 know how that impacts compatibility or if you'd want a different field for=
 that, but we really don't want some sort of "encoded" email address floati=
ng around.  EAI is all about UTF-8 mail, including addresses.

Again, not familiar with vCard, but note that users will likely now have 2 =
addresses:  The native script, and some sort of transliterated ASCII.  Eg: =
 Their current ASCII address and a Unicode address.  They'll need the ASCII=
 address for back compat with legacy systems or just because people in othe=
r places aren't literate in their native script.

And it gets "worse" :)  Imagine the Mongolian businessman in Mongolia.  He =
gets a Mongolian email address to chat with his customers locally.  Cool.  =
He ALSO gets a Chinese email address to talk to his suppliers and the gover=
nment.  Then he also gets a third ASCII address to talk to his importers in=
 the US.

I can even imagine a case where someone wants 2 non-ASCII addresses and doe=
sn't really need an ASCII address.

-Shawn

------------------------------

Message: 2
Date: Fri, 05 Nov 2010 09:55:32 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
Subject: [EAI] Internationalized email addresses in vCard 4.0
To: ima@ietf.org
Cc: vcarddav@ietf.org
Message-ID: <4CD40CD4.3090503@viagenie.ca>
Content-Type: text/plain; charset=3DISO-8859-1

Hello,

We need some advice from the EAI working group.

vCard 4.0 is a file format for contact information. It's a textual format a=
nd its character set is always UTF-8. One of the information items it may c=
ontain is email addresses. See here:
http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-13#section-6.4.2

Basically to list an email address in a vCard you will have a line looking =
like this:

EMAIL:jdoe@example.com

The ABNF for what comes after the colon is "addr-spec", which is defined in=
 RFC 5322, section 3.4.1.

Now, addr-spec does not allow full Unicode. An internationalized address wo=
uld need to be EAI/IDN-encoded, which implies that a vCard app would need t=
o decode it to display it to a user.

Questions:
- Is this the right way to do it?
- Should we allow full Unicode, which removes the need for decoding from th=
e vCard app and adds the need for encoding in the MUA?
- Should both forms be possible, should one form be preferred over the othe=
r, or should only one form be allowed?
- What should the ABNF look like for allowing Unicode characters in email a=
ddresses?
- Would it help us in any way if we were to specify a mailto: URL instead?

Thanks,
Simon
--
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org



From klensin@jck.com  Fri Nov  5 16:24:09 2010
Return-Path: <klensin@jck.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 818083A695A for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599]
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 X5ZsAOJ35RvX for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:24:08 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 7C9B23A695C for <ima@ietf.org>; Fri,  5 Nov 2010 16:24:08 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PEVdt-0001ng-2X; Fri, 05 Nov 2010 19:24:21 -0400
Date: Fri, 05 Nov 2010 19:24:18 -0400
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org
Message-ID: <23146A8EE4C4893163605A9F@[10.40.72.147]>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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, 05 Nov 2010 23:24:09 -0000

--On Friday, 05 November, 2010 23:08 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> It should really just allow full UTF-8.  I don't know enough
> about vCard to know how that impacts compatibility or if you'd
> want a different field for that, but we really don't want some
> sort of "encoded" email address floating around.  EAI is all
> about UTF-8 mail, including addresses.
> 
> Again, not familiar with vCard, but note that users will
> likely now have 2 addresses:  The native script, and some sort
> of transliterated ASCII.  Eg:  Their current ASCII address and
> a Unicode address.  They'll need the ASCII address for back
> compat with legacy systems or just because people in other
> places aren't literate in their native script.
> 
> And it gets "worse" :)  Imagine the Mongolian businessman in
> Mongolia.  He gets a Mongolian email address to chat with his
> customers locally.  Cool.  He ALSO gets a Chinese email
> address to talk to his suppliers and the government.  Then he
> also gets a third ASCII address to talk to his importers in
> the US.

I generally agree, but...

(1) It would be lots better to reference the EAI address
definition (just as they have referenced the 5322 one, and for
the same reasons) than to say "unrestricted Unicode": Even if
they amount to almost the same thing, there are rules about
special-character escaping, etc.

> I can even imagine a case where someone wants 2 non-ASCII
> addresses and doesn't really need an ASCII address.

Let's assume that I'm not in business although I might buy
things from vendors in my country, read and speak only one
language (Lower Slobbovian, for example), have a keyboard with
only that script on it, and want to communicate exclusively with
a few million of my closest friends who are in the same
situation.  I exaggerate a bit, but this is actually the most
important use case for IDNs, IMO.  And I don't need ASCII
addresses because, until I can communicate exclusively in my
language and script, the Internet basically doesn't exist for
me.  There are days on which I don't quite believe this, but it
is certainly the logical and quite obvious corollary to some of
the arguments that have been made for IDN TLDs.

    john




From Shawn.Steele@microsoft.com  Fri Nov  5 16:32:48 2010
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 A3F643A6973 for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.142
X-Spam-Level: 
X-Spam-Status: No, score=-10.142 tagged_above=-999 required=5 tests=[AWL=0.457, 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 vdlKeoU4eMQi for <ima@core3.amsl.com>; Fri,  5 Nov 2010 16:32:47 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id B5F2C3A695C for <ima@ietf.org>; Fri,  5 Nov 2010 16:32:47 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 5 Nov 2010 16:33:01 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.222]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.01.0255.003; Fri, 5 Nov 2010 16:33:01 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, "ima@ietf.org" <ima@ietf.org>
Thread-Topic: [EAI] Internationalized email addresses in vCard 4.0
Thread-Index: Act9PUcri5AzOC7GQeO9Kqa7u9cjpgAPfaIAAA6aAIA=
Date: Fri, 5 Nov 2010 23:33:00 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A3B335@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com> <23146A8EE4C4893163605A9F@[10.40.72.147]>
In-Reply-To: <23146A8EE4C4893163605A9F@[10.40.72.147]>
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] Internationalized email addresses in vCard 4.0
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, 05 Nov 2010 23:32:48 -0000

> (1) It would be lots better to reference the EAI address definition=20

Yes

>> I can even imagine a case where someone wants 2 non-ASCII addresses=20
>> and doesn't really need an ASCII address.

> Let's assume that... want to communicate exclusively with a few million o=
f=20
> my closest friends who are in the same (script).

Clearly, people may only have 1 address, and it may be non-ASCII.  That's p=
robably even desirable in many places. =20

I had been talking about multiple addresses, and wanted to make clear that =
a single user could have multiple non-ASCII addresses.  Eg: if vCard (I don=
't know how it works) said "gee, let's have an ASCII address, and an EAI ad=
dress", that's not sufficient because it makes assumptions that aren't nece=
ssarily true.  I think it's reasonable for users to have 1-n addresses, and=
 that they may all be non-ASCII.

If vCard can extend to "just" use EAI style UTF-8 in existing fields, that =
might be OK.  It'd be nice to have multiple addresses (I sort of hope it al=
ready does :).  The catch is that probably multiples imply different mailbo=
xes?  And with EAI we expect more than one for the same mailbox?

-Shawn




From derhoermi@gmx.net  Fri Nov  5 17:03:04 2010
Return-Path: <derhoermi@gmx.net>
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 178703A69A2 for <ima@core3.amsl.com>; Fri,  5 Nov 2010 17:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.436
X-Spam-Level: 
X-Spam-Status: No, score=-4.436 tagged_above=-999 required=5 tests=[AWL=-1.837, BAYES_00=-2.599]
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 EPrDsIpm5m6Y for <ima@core3.amsl.com>; Fri,  5 Nov 2010 17:03:02 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id DAEF43A6951 for <ima@ietf.org>; Fri,  5 Nov 2010 17:03:01 -0700 (PDT)
Received: (qmail invoked by alias); 06 Nov 2010 00:03:14 -0000
Received: from dslb-094-223-178-207.pools.arcor-ip.net (EHLO xn--bjrn-6qa.xn--hhrmann-90a.de) [94.223.178.207] by mail.gmx.net (mp069) with SMTP; 06 Nov 2010 01:03:14 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+U5gBOiWWU6ghLTbHOIecfLPeZilXAJJg+rDH9Nm endllnDdtdWpUk
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John C Klensin <klensin@jck.com>
Date: Sat, 06 Nov 2010 01:03:10 +0100
Message-ID: <t169d6148robtm8g4e81d5kifnbs3n902q@hive.bjoern.hoehrmann.de>
References: <4CD40CD4.3090503@viagenie.ca> <84E442EF93DA69A676651D8E@[10.40.72.147]>
In-Reply-To: <84E442EF93DA69A676651D8E@[10.40.72.147]>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: ima@ietf.org, vcarddav@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 00:03:04 -0000

* John C Klensin wrote:
>Except that you misunderstand what "EAI/IDN encoding". I would
>strongly suggest that you have a look at the EAI drafts and that
>you deal with this by replacing the 5322 addr-spec with the EAI
>equivalent.  Otherwise, you are just going to create trouble for
>yourselves and your users.

I haven't been paying attention for some time, but trying now, I could
not find that equivalent (I went to the Working Group homepage and
clicked through a couple of drafts, grepped the RFC index for "email"
and "e-mail", particularily scanned for some ABNF in RFC 4952, none of
which turned up anything useful within five minutes. Then I went to
Wikipedia, which only references RFC 5335 on "Internationalized Email
Headers" which didn't seem that relevant, but if you scroll way down
there, there is "utf8-addr-spec"; if that is the definition you mean,
then the definition does not really make sense to me; I would expect
e-mail addresses to be composed of characters, not sequences of bytes.)

I think it would be a good idea to have a Internationalized Email Ad-
dresses RFC that defines the syntax and semantics of addresses, and
does so in terms of characters, not bytes (and naturally does not de-
fine headers, mail protocol extensions, and so on). That specification
might then also address how other protocols are to use said addresses.
For what it is worth.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From yangwooko@gmail.com  Fri Nov  5 17:57:36 2010
Return-Path: <yangwooko@gmail.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 24E473A69AC; Fri,  5 Nov 2010 17:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 CWlyWumfoh82; Fri,  5 Nov 2010 17:57:35 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 5C70B3A69A7; Fri,  5 Nov 2010 17:57:34 -0700 (PDT)
Received: by wwb39 with SMTP id 39so1931508wwb.13 for <multiple recipients>; Fri, 05 Nov 2010 17:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=GdYpoBeVhgf8RRFazxRDRB5k3gQNy1BA6deKzMQ8Ed0=; b=wl14PIkf3TIrySHLitK9aLhwxVdsuuhtmd1yqaQKmXLgdSy+gXx+Ja/k9gC0CiErhq VkJxShZ5sm+d3Gudhh+DDtrvBZZbGWfq0EKzeytFXYGd9j2p8n5HCkH6yS0kHcX+h+bs hg9baduL2rYOJIh7eGkUu6/VcmNReHBOMFsjY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=XHoAc831cKPhc27Mar2W23taiuK68RCKeCL8zm7WgEG/bDEcjumxGud9Zn7rSBU3/H f9T6v7mnAtmKdTnZ7eZJW5BnFH0X0oXuAvBCqvqEPmdHPOnOl+8KI4cQOoOzxT4og6pe KbODM5NGThxJUuWXu6120+5am8XcbkrN7ggtk=
MIME-Version: 1.0
Received: by 10.216.47.19 with SMTP id s19mr1811188web.56.1289005066039; Fri, 05 Nov 2010 17:57:46 -0700 (PDT)
Sender: yangwooko@gmail.com
Received: by 10.216.1.136 with HTTP; Fri, 5 Nov 2010 17:57:45 -0700 (PDT)
In-Reply-To: <t169d6148robtm8g4e81d5kifnbs3n902q@hive.bjoern.hoehrmann.de>
References: <4CD40CD4.3090503@viagenie.ca> <84E442EF93DA69A676651D8E@10.40.72.147> <t169d6148robtm8g4e81d5kifnbs3n902q@hive.bjoern.hoehrmann.de>
Date: Sat, 6 Nov 2010 09:57:45 +0900
X-Google-Sender-Auth: xzVOaWcgNm4U_aCs47dYiB3pKK0
Message-ID: <AANLkTinVjEG+HrGZVHF-iQcmhXr5kJkk+u-A3giVE37q@mail.gmail.com>
From: Yangwoo Ko <newcat@icu.ac.kr>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary=0016367b6cc813338e049457e1b6
Cc: ima@ietf.org, vcarddav@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 00:57:36 -0000

--0016367b6cc813338e049457e1b6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Pleae refer to https://datatracker.ietf.org/doc/draft-ietf-eai-rfc5335bis/

On Sat, Nov 6, 2010 at 9:03 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

>
>
> * John C Klensin wrote:
> >Except that you misunderstand what "EAI/IDN encoding". I would
> >strongly suggest that you have a look at the EAI drafts and that
> >you deal with this by replacing the 5322 addr-spec with the EAI
> >equivalent.  Otherwise, you are just going to create trouble for
> >yourselves and your users.
>
> I haven't been paying attention for some time, but trying now, I could
> not find that equivalent (I went to the Working Group homepage and
> clicked through a couple of drafts, grepped the RFC index for "email"
> and "e-mail", particularily scanned for some ABNF in RFC 4952, none of
> which turned up anything useful within five minutes. Then I went to
> Wikipedia, which only references RFC 5335 on "Internationalized Email
> Headers" which didn't seem that relevant, but if you scroll way down
> there, there is "utf8-addr-spec"; if that is the definition you mean,
> then the definition does not really make sense to me; I would expect
> e-mail addresses to be composed of characters, not sequences of bytes.)
>
> I think it would be a good idea to have a Internationalized Email Ad-
> dresses RFC that defines the syntax and semantics of addresses, and
> does so in terms of characters, not bytes (and naturally does not de-
> fine headers, mail protocol extensions, and so on). That specification
> might then also address how other protocols are to use said addresses.
> For what it is worth.
> --
> Bj=C3=B6rn H=C3=B6hrmann =C2=B7 mailto:bjoern@hoehrmann.de =C2=B7 http://=
bjoern.hoehrmann.de
> Am Badedeich 7 =C2=B7 Telefon: +49(0)160/4415681 =C2=B7 http://www.bjoern=
sworld.de
> 25899 Dageb=C3=BCll =C2=B7 PGP Pub. KeyID: 0xA4357E78 =C2=B7 http://www.w=
ebsitedev.de/
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human / twitter as yangwooko / msn as newcat_kr@yahoo.co.kr / nate as
yangwooko@nate.com

--0016367b6cc813338e049457e1b6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Pleae refer to <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-eai-r=
fc5335bis/">https://datatracker.ietf.org/doc/draft-ietf-eai-rfc5335bis/</a>=
 <br><br><div class=3D"gmail_quote">On Sat, Nov 6, 2010 at 9:03 AM, Bjoern =
Hoehrmann <span dir=3D"ltr">&lt;<a href=3D"mailto:derhoermi@gmx.net">derhoe=
rmi@gmx.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
><br>
<br>
* John C Klensin wrote:<br>
&gt;Except that you misunderstand what &quot;EAI/IDN encoding&quot;. I woul=
d<br>
&gt;strongly suggest that you have a look at the EAI drafts and that<br>
&gt;you deal with this by replacing the 5322 addr-spec with the EAI<br>
&gt;equivalent. =C2=A0Otherwise, you are just going to create trouble for<b=
r>
&gt;yourselves and your users.<br>
<br>
</div>I haven&#39;t been paying attention for some time, but trying now, I =
could<br>
not find that equivalent (I went to the Working Group homepage and<br>
clicked through a couple of drafts, grepped the RFC index for &quot;email&q=
uot;<br>
and &quot;e-mail&quot;, particularily scanned for some ABNF in RFC 4952, no=
ne of<br>
which turned up anything useful within five minutes. Then I went to<br>
Wikipedia, which only references RFC 5335 on &quot;Internationalized Email<=
br>
Headers&quot; which didn&#39;t seem that relevant, but if you scroll way do=
wn<br>
there, there is &quot;utf8-addr-spec&quot;; if that is the definition you m=
ean,<br>
then the definition does not really make sense to me; I would expect<br>
e-mail addresses to be composed of characters, not sequences of bytes.)<br>
<br>
I think it would be a good idea to have a Internationalized Email Ad-<br>
dresses RFC that defines the syntax and semantics of addresses, and<br>
does so in terms of characters, not bytes (and naturally does not de-<br>
fine headers, mail protocol extensions, and so on). That specification<br>
might then also address how other protocols are to use said addresses.<br>
For what it is worth.<br>
<font color=3D"#888888">--<br>
Bj=C3=B6rn H=C3=B6hrmann =C2=B7 mailto:<a href=3D"mailto:bjoern@hoehrmann.d=
e">bjoern@hoehrmann.de</a> =C2=B7 <a href=3D"http://bjoern.hoehrmann.de" ta=
rget=3D"_blank">http://bjoern.hoehrmann.de</a><br>
Am Badedeich 7 =C2=B7 Telefon: +49(0)160/4415681 =C2=B7 <a href=3D"http://w=
ww.bjoernsworld.de" target=3D"_blank">http://www.bjoernsworld.de</a><br>
25899 Dageb=C3=BCll =C2=B7 PGP Pub. KeyID: 0xA4357E78 =C2=B7 <a href=3D"htt=
p://www.websitedev.de/" target=3D"_blank">http://www.websitedev.de/</a><br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
IMA mailing list<br>
<a href=3D"mailto:IMA@ietf.org">IMA@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ima" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/ima</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>a human / t=
witter as yangwooko / msn as <a href=3D"mailto:newcat_kr@yahoo.co.kr" targe=
t=3D"_blank">newcat_kr@yahoo.co.kr</a> / nate as <a href=3D"mailto:yangwook=
o@nate.com" target=3D"_blank">yangwooko@nate.com</a><br>


--0016367b6cc813338e049457e1b6--

From yangwooko@gmail.com  Fri Nov  5 18:05:26 2010
Return-Path: <yangwooko@gmail.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 50D883A69AC for <ima@core3.amsl.com>; Fri,  5 Nov 2010 18:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 n1QhK61RbGxG for <ima@core3.amsl.com>; Fri,  5 Nov 2010 18:05:25 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 530703A69A7 for <ima@ietf.org>; Fri,  5 Nov 2010 18:05:25 -0700 (PDT)
Received: by wwb39 with SMTP id 39so1935146wwb.13 for <ima@ietf.org>; Fri, 05 Nov 2010 18:05:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=jBHr8wdw7Wk/biPqw4UEIRWIBpKF19W0UcuKw1GHNbI=; b=cRqXj4NevTZ/4q8ycBEumrq/2EGluLB8ioR/jcekXqviDvwHUaz+1sso/se4b1AnY7 7qeAf+PERIlzW8SMtBFV8/PJQD3U0Mp8EMLnwAkcagedKl381Ko9K07+Htpg3+0x7dla 88P2oTfxGgysCO3PVuiLaFdX56bEmLaTR5WEs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=kOCSKLBojyZI0cX2IqrFk+l7WQr7bCIyPZOb2Du/FSr204u0x/UgyETu3KTAeD+Z0i WdeNqyYjIWzp/z4LwtQ1NPl+0OV2A8O1zz1/N5Z+zrAdu+dzio/WmDWlXqju67BOBfEY h5/ZMCQhCkRHKII0YwdS7iG4yMXRqEExXwLGc=
MIME-Version: 1.0
Received: by 10.216.172.9 with SMTP id s9mr2782650wel.56.1289005538784; Fri, 05 Nov 2010 18:05:38 -0700 (PDT)
Sender: yangwooko@gmail.com
Received: by 10.216.1.136 with HTTP; Fri, 5 Nov 2010 18:05:38 -0700 (PDT)
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A3B335@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com> <23146A8EE4C4893163605A9F@10.40.72.147> <E14011F8737B524BB564B05FF748464A10A3B335@TK5EX14MBXC141.redmond.corp.microsoft.com>
Date: Sat, 6 Nov 2010 10:05:38 +0900
X-Google-Sender-Auth: 7qDdWKtzxtNxyEDaZWTev4Fjtu4
Message-ID: <AANLkTi=ayW-G+GyU7mq7br6JrwpSPwvFHt=Dcvd6kj65@mail.gmail.com>
From: Yangwoo Ko <newcat@icu.ac.kr>
To: Shawn Steele <Shawn.Steele@microsoft.com>
Content-Type: multipart/alternative; boundary=001636416a7940bb4d049457fdc1
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 01:05:26 -0000

--001636416a7940bb4d049457fdc1
Content-Type: text/plain; charset=UTF-8

Since storing a received email to a specific mailbox depends on
implementations/policies/user-settings of a final SMTP server, any EAI
specification should not imply the binding of an ASCII email address and a
UTF address.

On Sat, Nov 6, 2010 at 8:33 AM, Shawn Steele <Shawn.Steele@microsoft.com>wrote:
(snip)

> If vCard can extend to "just" use EAI style UTF-8 in existing fields, that
> might be OK.  It'd be nice to have multiple addresses (I sort of hope it
> already does :).  The catch is that probably multiples imply different
> mailboxes?  And with EAI we expect more than one for the same mailbox?
> (snip)
>

--001636416a7940bb4d049457fdc1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Since storing a received email to a specific mailbox depends on implementat=
ions/policies/user-settings of a final SMTP server, any EAI specification s=
hould not imply the binding of an ASCII email address and a UTF address. <b=
r>
<br><div class=3D"gmail_quote">On Sat, Nov 6, 2010 at 8:33 AM, Shawn Steele=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:Shawn.Steele@microsoft.com">Shawn.=
Steele@microsoft.com</a>&gt;</span> wrote:<br><div>(snip) <br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left:=
 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class=3D"im">If vCard can extend to &quot;just&quot; use EAI style UTF=
-8 in existing fields, that might be OK. =C2=A0It&#39;d be nice to have mul=
tiple addresses (I sort of hope it already does :). =C2=A0The catch is that=
 probably multiples imply different mailboxes? =C2=A0And with EAI we expect=
 more than one for the same mailbox?<br>
</div>
<font color=3D"#888888">(snip)</font><br></blockquote></div><br clear=3D"al=
l"><br>

--001636416a7940bb4d049457fdc1--

From Shawn.Steele@microsoft.com  Fri Nov  5 23:40:41 2010
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 2346E3A680B for <ima@core3.amsl.com>; Fri,  5 Nov 2010 23:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.233
X-Spam-Level: 
X-Spam-Status: No, score=-10.233 tagged_above=-999 required=5 tests=[AWL=0.365, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 1kue9S5GNXV6 for <ima@core3.amsl.com>; Fri,  5 Nov 2010 23:40:40 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 0CE6B3A6803 for <ima@ietf.org>; Fri,  5 Nov 2010 23:40:39 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 5 Nov 2010 23:40:54 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.222]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi id 14.01.0255.003; Fri, 5 Nov 2010 23:40:54 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Yangwoo Ko <newcat@icu.ac.kr>
Thread-Topic: [EAI] Internationalized email addresses in vCard 4.0
Thread-Index: Act9PUcri5AzOC7GQeO9Kqa7u9cjpgAPfaIAAA6aAID//6d/AP//5+/K
Date: Sat, 6 Nov 2010 06:40:54 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A3F3D0@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com> <23146A8EE4C4893163605A9F@10.40.72.147> <E14011F8737B524BB564B05FF748464A10A3B335@TK5EX14MBXC141.redmond.corp.microsoft.com>, <AANLkTi=ayW-G+GyU7mq7br6JrwpSPwvFHt=Dcvd6kj65@mail.gmail.com>
In-Reply-To: <AANLkTi=ayW-G+GyU7mq7br6JrwpSPwvFHt=Dcvd6kj65@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: multipart/alternative; boundary="_000_E14011F8737B524BB564B05FF748464A10A3F3D0TK5EX14MBXC141r_"
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 06:40:41 -0000

--_000_E14011F8737B524BB564B05FF748464A10A3F3D0TK5EX14MBXC141r_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SG93ZXZlciBpdCB0aGUgZmluYWwgU01UUCBzZXJ2ZXIgKG9yIGl0J3MgYWdlbnQpIHdlcmUgdGhl
IG9uZSBjcmVhdGluZyB0aGUgdkNhcmQsIGl0IHdvdWxkIGtub3cgd2hpY2ggQVNDSUkvVW5pY29k
ZSBhZGRyZXNzZXMgbWF0Y2hlZC4NCg0KDQoNCkkgdGhpbmsgaXQncyBPSyBmb3IgYSB2Q2FyZCB0
byBub3Qga25vdyB0aGF0IFNoYXduLlN0ZWVsZUBtaWNyb3NvZnQuY29tPG1haWx0bzpTaGF3bi5T
dGVlbGVAbWljcm9zb2Z0LmNvbT4gYW5kIHNoYXduc3RlQG1pY3Jvc29mdC5jb208bWFpbHRvOnNo
YXduc3RlQG1pY3Jvc29mdC5jb20+IGdvIHRvIHRoZSBzYW1lIG1haWxib3gsIHRoZSB1c2VyIGNo
b29zaW5nIHRoZSBhZGRyZXNzIGNhbiBmaWd1cmUgb3V0IGlmIGl0J3MgdGhlaXIgd29yayBvciBo
b3RtYWlsIG9yIGhvbWUgYWNjb3VudCBvciB3aGF0ZXZlci4NCg0KDQotU2hhd24NCg0K76Oi76OQ
76On76ObIO+jou+jo++jl++jlO+jmQ0KaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXduc3RlDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiB5YW5nd29va29AZ21haWwu
Y29tIFt5YW5nd29va29AZ21haWwuY29tXSBvbiBiZWhhbGYgb2YgWWFuZ3dvbyBLbyBbbmV3Y2F0
QGljdS5hYy5rcl0NClNlbnQ6IEZyaWRheSwgTm92ZW1iZXIgMDUsIDIwMTAgNjowNSBQTQ0KVG86
IFNoYXduIFN0ZWVsZQ0KQ2M6IEpvaG4gQyBLbGVuc2luOyBpbWFAaWV0Zi5vcmcNClN1YmplY3Q6
IFJlOiBbRUFJXSBJbnRlcm5hdGlvbmFsaXplZCBlbWFpbCBhZGRyZXNzZXMgaW4gdkNhcmQgNC4w
DQoNClNpbmNlIHN0b3JpbmcgYSByZWNlaXZlZCBlbWFpbCB0byBhIHNwZWNpZmljIG1haWxib3gg
ZGVwZW5kcyBvbiBpbXBsZW1lbnRhdGlvbnMvcG9saWNpZXMvdXNlci1zZXR0aW5ncyBvZiBhIGZp
bmFsIFNNVFAgc2VydmVyLCBhbnkgRUFJIHNwZWNpZmljYXRpb24gc2hvdWxkIG5vdCBpbXBseSB0
aGUgYmluZGluZyBvZiBhbiBBU0NJSSBlbWFpbCBhZGRyZXNzIGFuZCBhIFVURiBhZGRyZXNzLg0K
DQpPbiBTYXQsIE5vdiA2LCAyMDEwIGF0IDg6MzMgQU0sIFNoYXduIFN0ZWVsZSA8U2hhd24uU3Rl
ZWxlQG1pY3Jvc29mdC5jb208bWFpbHRvOlNoYXduLlN0ZWVsZUBtaWNyb3NvZnQuY29tPj4gd3Jv
dGU6DQooc25pcCkNCklmIHZDYXJkIGNhbiBleHRlbmQgdG8gImp1c3QiIHVzZSBFQUkgc3R5bGUg
VVRGLTggaW4gZXhpc3RpbmcgZmllbGRzLCB0aGF0IG1pZ2h0IGJlIE9LLiAgSXQnZCBiZSBuaWNl
IHRvIGhhdmUgbXVsdGlwbGUgYWRkcmVzc2VzIChJIHNvcnQgb2YgaG9wZSBpdCBhbHJlYWR5IGRv
ZXMgOikuICBUaGUgY2F0Y2ggaXMgdGhhdCBwcm9iYWJseSBtdWx0aXBsZXMgaW1wbHkgZGlmZmVy
ZW50IG1haWxib3hlcz8gIEFuZCB3aXRoIEVBSSB3ZSBleHBlY3QgbW9yZSB0aGFuIG9uZSBmb3Ig
dGhlIHNhbWUgbWFpbGJveD8NCihzbmlwKQ0KDQoNCg==

--_000_E14011F8737B524BB564B05FF748464A10A3F3D0TK5EX14MBXC141r_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgZGlyPSJsdHIiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUi
IGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8c3R5bGUgaWQ9Im93YVBhcmFT
dHlsZSI+UCB7DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4tQk9UVE9NOiAwcHgNCn0NCjwvc3R5
bGU+DQo8L2hlYWQ+DQo8Ym9keSBmUFN0eWxlPSIxIiBvY3NpPSIwIj4NCjxkaXYgc3R5bGU9ImRp
cmVjdGlvbjogbHRyO2ZvbnQtZmFtaWx5OiBUYWhvbWE7Y29sb3I6ICMwMDAwMDA7Zm9udC1zaXpl
OiAxMHB0OyI+DQo8cD5Ib3dldmVyIGl0IHRoZSBmaW5hbCBTTVRQIHNlcnZlciAob3IgaXQncyBh
Z2VudCkgd2VyZSB0aGUgb25lIGNyZWF0aW5nIHRoZSB2Q2FyZCwgaXQgd291bGQga25vdyB3aGlj
aCBBU0NJSS9Vbmljb2RlIGFkZHJlc3NlcyBtYXRjaGVkLjwvcD4NCjxwPiZuYnNwOzwvcD4NCjxw
PkkgdGhpbmsgaXQncyBPSyBmb3IgYSB2Q2FyZCB0byBub3Qga25vdyB0aGF0IDxhIGhyZWY9Im1h
aWx0bzpTaGF3bi5TdGVlbGVAbWljcm9zb2Z0LmNvbSI+DQpTaGF3bi5TdGVlbGVAbWljcm9zb2Z0
LmNvbTwvYT4gYW5kIDxhIGhyZWY9Im1haWx0bzpzaGF3bnN0ZUBtaWNyb3NvZnQuY29tIj5zaGF3
bnN0ZUBtaWNyb3NvZnQuY29tPC9hPiBnbyB0byB0aGUgc2FtZSBtYWlsYm94LCB0aGUgdXNlciBj
aG9vc2luZyB0aGUgYWRkcmVzcyBjYW4gZmlndXJlIG91dCBpZiBpdCdzIHRoZWlyIHdvcmsgb3Ig
aG90bWFpbCBvciBob21lIGFjY291bnQgb3Igd2hhdGV2ZXIuPC9wPg0KPGRpdj4NCjxwPiZuYnNw
OzwvcD4NCjxkaXYgc3R5bGU9IkZPTlQtRkFNSUxZOiBUYWhvbWE7IEZPTlQtU0laRTogMTNweCI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tU2hhd248L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
bmJzcDs8L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6
IENvZGUyMDAwIj7vo6Lvo5Dvo6fvo5sg76Oi76Oj76OX76OU76OZPC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPmh0dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZTwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJG
T05ULUZBTUlMWTogVGltZXMgTmV3IFJvbWFuOyBDT0xPUjogIzAwMDAwMDsgRk9OVC1TSVpFOiAx
NnB4Ij4NCjxociB0YWJpbmRleD0iLTEiPg0KPGRpdiBzdHlsZT0iRElSRUNUSU9OOiBsdHIiIGlk
PSJkaXZScEY1MDU1NjYiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBzaXplPSIyIiBmYWNlPSJUYWhv
bWEiPjxiPkZyb206PC9iPiB5YW5nd29va29AZ21haWwuY29tIFt5YW5nd29va29AZ21haWwuY29t
XSBvbiBiZWhhbGYgb2YgWWFuZ3dvbyBLbyBbbmV3Y2F0QGljdS5hYy5rcl08YnI+DQo8Yj5TZW50
OjwvYj4gRnJpZGF5LCBOb3ZlbWJlciAwNSwgMjAxMCA2OjA1IFBNPGJyPg0KPGI+VG86PC9iPiBT
aGF3biBTdGVlbGU8YnI+DQo8Yj5DYzo8L2I+IEpvaG4gQyBLbGVuc2luOyBpbWFAaWV0Zi5vcmc8
YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtFQUldIEludGVybmF0aW9uYWxpemVkIGVtYWlsIGFk
ZHJlc3NlcyBpbiB2Q2FyZCA0LjA8YnI+DQo8L2ZvbnQ+PGJyPg0KPC9kaXY+DQo8ZGl2PjwvZGl2
Pg0KPGRpdj5TaW5jZSBzdG9yaW5nIGEgcmVjZWl2ZWQgZW1haWwgdG8gYSBzcGVjaWZpYyBtYWls
Ym94IGRlcGVuZHMgb24gaW1wbGVtZW50YXRpb25zL3BvbGljaWVzL3VzZXItc2V0dGluZ3Mgb2Yg
YSBmaW5hbCBTTVRQIHNlcnZlciwgYW55IEVBSSBzcGVjaWZpY2F0aW9uIHNob3VsZCBub3QgaW1w
bHkgdGhlIGJpbmRpbmcgb2YgYW4gQVNDSUkgZW1haWwgYWRkcmVzcyBhbmQgYSBVVEYgYWRkcmVz
cy4NCjxicj4NCjxicj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBTYXQsIE5vdiA2LCAy
MDEwIGF0IDg6MzMgQU0sIFNoYXduIFN0ZWVsZSA8c3BhbiBkaXI9Imx0ciI+DQombHQ7PGEgaHJl
Zj0ibWFpbHRvOlNoYXduLlN0ZWVsZUBtaWNyb3NvZnQuY29tIiB0YXJnZXQ9Il9ibGFuayI+U2hh
d24uU3RlZWxlQG1pY3Jvc29mdC5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGRpdj4o
c25pcCkgPGJyPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iQk9SREVSLUxFRlQ6IHJnYigy
MDQsMjA0LDIwNCkgMXB4IHNvbGlkOyBNQVJHSU46IDBwdCAwcHQgMHB0IDAuOGV4OyBQQURESU5H
LUxFRlQ6IDFleCIgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxkaXYgY2xhc3M9ImltIj5JZiB2Q2Fy
ZCBjYW4gZXh0ZW5kIHRvICZxdW90O2p1c3QmcXVvdDsgdXNlIEVBSSBzdHlsZSBVVEYtOCBpbiBl
eGlzdGluZyBmaWVsZHMsIHRoYXQgbWlnaHQgYmUgT0suICZuYnNwO0l0J2QgYmUgbmljZSB0byBo
YXZlIG11bHRpcGxlIGFkZHJlc3NlcyAoSSBzb3J0IG9mIGhvcGUgaXQgYWxyZWFkeSBkb2VzIDop
LiAmbmJzcDtUaGUgY2F0Y2ggaXMgdGhhdCBwcm9iYWJseSBtdWx0aXBsZXMgaW1wbHkgZGlmZmVy
ZW50IG1haWxib3hlcz8gJm5ic3A7QW5kIHdpdGggRUFJDQogd2UgZXhwZWN0IG1vcmUgdGhhbiBv
bmUgZm9yIHRoZSBzYW1lIG1haWxib3g/PGJyPg0KPC9kaXY+DQo8Zm9udCBjb2xvcj0iIzg4ODg4
OCI+KHNuaXApPC9mb250Pjxicj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyIGNsZWFyPSJh
bGwiPg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_E14011F8737B524BB564B05FF748464A10A3F3D0TK5EX14MBXC141r_--

From Shawn.Steele@microsoft.com  Sat Nov  6 00:10:34 2010
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 F0E713A6877 for <ima@core3.amsl.com>; Sat,  6 Nov 2010 00:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.294
X-Spam-Level: 
X-Spam-Status: No, score=-10.294 tagged_above=-999 required=5 tests=[AWL=0.305, 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 WeyhwDpsQwSD for <ima@core3.amsl.com>; Sat,  6 Nov 2010 00:10:31 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id CA3C23A6867 for <ima@ietf.org>; Sat,  6 Nov 2010 00:10:30 -0700 (PDT)
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (157.54.80.67) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 6 Nov 2010 00:10:45 -0700
Received: from TK5EX14MBXC141.redmond.corp.microsoft.com ([169.254.9.222]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Sat, 6 Nov 2010 00:10:45 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Internationalized email addresses in vCard 4.0
Thread-Index: AQHLfYEWl1OCtsxs30yzLkVIkcOPlg==
Date: Sat, 6 Nov 2010 07:10:44 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10A3F477@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.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 07:10:34 -0000

>> I would expect
>> e-mail addresses to be composed of characters, not sequences of bytes.)

Certainly we think of the email addresses being composed of Unicode charact=
ers, however UTF-8 is explicity 1-4 bytes per character, and EAI is thinkin=
g primarily about the bytes on the wire, not the characters that those byte=
s represent.  (And the IETF loves to think of those as octets rather than b=
ytes.)

For example, any Windows API would probably take "WCHAR" UTF-16 strings, an=
d then do the right thing so that when it finally shows up "on the wire" it=
'd be in the UTF-8 bytes.=20

There isn't a specific address-only RFC, so you'd have to refer to the appr=
opriate part of the relevent document that contains EAI addresses.  Like 4.=
4 of rfc5335bis.

-Shawn=

From klensin@jck.com  Sat Nov  6 00:50:36 2010
Return-Path: <klensin@jck.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 A45EE3A67FF for <ima@core3.amsl.com>; Sat,  6 Nov 2010 00:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599]
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 4WaxOSBaAVCp for <ima@core3.amsl.com>; Sat,  6 Nov 2010 00:50:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id C19913A6877 for <ima@ietf.org>; Sat,  6 Nov 2010 00:50:35 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PEdXy-000Dy1-H7; Sat, 06 Nov 2010 03:50:46 -0400
Date: Sat, 06 Nov 2010 03:50:44 -0400
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, Yangwoo Ko <newcat@icu.ac.kr>
Message-ID: <9F869AED93B336BDE7CAD163@[10.40.72.147]>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A3F3D0@TK5EX14MBXC141.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com> <23146A8EE4C4893163605A9F@10.40.72.147> <E14011F8737B524BB564B05FF748464A10A3B335@TK5EX14MBXC141.redmond.corp.microsoft.com> ,<AANLkTi=ayW-G+GyU7mq7br6JrwpSPwvFHt=Dcvd6kj65@mail.gmail.com> <E14011F8737B524BB564B05FF748464A10A3F3D0@TK5EX14MBXC141.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ima@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 07:50:36 -0000

--On Saturday, 06 November, 2010 06:40 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> However it the final SMTP server (or it's agent) were the one
> creating the vCard, it would know which ASCII/Unicode
> addresses matched.

So, presumably, would the user.

> I think it's OK for a vCard to not know that
> Shawn.Steele@microsoft.com<mailto:Shawn.Steele@microsoft.com>
> and shawnste@microsoft.com<mailto:shawnste@microsoft.com> go
> to the same mailbox, the user choosing the address can figure
> out if it's their work or hotmail or home account or whatever.

I think there is no possible way that anyone but the user or
delivery SMTP server can know, nor that anyone else should care.
Note that there is no way that you can know whether
klensin@jck.com, john+ietf@jck.com, and john-ietf@jck.com go to
the same mailbox unless I tell you and that I might use
different of them in different vCards (or different RFCs, etc.)

   john




From simon.perreault@viagenie.ca  Sat Nov  6 09:05:10 2010
Return-Path: <simon.perreault@viagenie.ca>
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 5723E3A6821 for <ima@core3.amsl.com>; Sat,  6 Nov 2010 09:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
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 uz6Yr2ghFRCX for <ima@core3.amsl.com>; Sat,  6 Nov 2010 09:05:04 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id B3A643A67B3 for <ima@ietf.org>; Sat,  6 Nov 2010 09:05:04 -0700 (PDT)
Received: from banana.viagenie.ca (unknown [206.172.18.80]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1D3F721BBC for <ima@ietf.org>; Sat,  6 Nov 2010 12:05:20 -0400 (EDT)
Message-ID: <4CD57CBF.6000101@viagenie.ca>
Date: Sat, 06 Nov 2010 12:05:19 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc14 Thunderbird/3.1.6
MIME-Version: 1.0
To: ima@ietf.org
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 16:05:10 -0000

Shawn Steele wrote, on 11/05/2010 07:08 PM:
> Again, not familiar with vCard, but note that users will likely now have 2
> addresses:  The native script, and some sort of transliterated ASCII.  Eg:
> Their current ASCII address and a Unicode address.  They'll need the ASCII
> address for back compat with legacy systems or just because people in other
> places aren't literate in their native script.

Just FYI: any number of email addresses may be specified in a vCard.

> And it gets "worse" :)  Imagine the Mongolian businessman in Mongolia.  He
> gets a Mongolian email address to chat with his customers locally.  Cool.  He
> ALSO gets a Chinese email address to talk to his suppliers and the
> government.  Then he also gets a third ASCII address to talk to his importers
> in the US.

I suppose this would be taken care of by using the LANGUAGE parameter, like this:

EMAIL;LANGUAGE=mn:<address in Mongolian goes here>
EMAIL;LANGUAGE=zh:<address in Chinese goes here>
EMAIL;LANGUAGE=en:<address in English goes here>

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org

From simon.perreault@viagenie.ca  Sat Nov  6 09:11:19 2010
Return-Path: <simon.perreault@viagenie.ca>
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 656E83A682A; Sat,  6 Nov 2010 09:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599]
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 JPXN1fxzymH5; Sat,  6 Nov 2010 09:11:16 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id B7CEE3A67ED; Sat,  6 Nov 2010 09:11:15 -0700 (PDT)
Received: from banana.viagenie.ca (unknown [206.172.18.80]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 517A921BBC; Sat,  6 Nov 2010 12:11:31 -0400 (EDT)
Message-ID: <4CD57E32.1030202@viagenie.ca>
Date: Sat, 06 Nov 2010 12:11:30 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc14 Thunderbird/3.1.6
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <4CD40CD4.3090503@viagenie.ca> <84E442EF93DA69A676651D8E@[10.40.72.147]>
In-Reply-To: <84E442EF93DA69A676651D8E@[10.40.72.147]>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ima@ietf.org, vcarddav@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 16:11:19 -0000

John C Klensin wrote, on 11/05/2010 06:41 PM:
> I would
> strongly suggest that you have a look at the EAI drafts and that
> you deal with this by replacing the 5322 addr-spec with the EAI
> equivalent.  Otherwise, you are just going to create trouble for
> yourselves and your users.

To be clear, does "the EAI equivalent" stand for uAddr-spec, as defined in
<http://tools.ietf.org/html/draft-ietf-eai-rfc5335bis-03#section-4.4>?

> Your one problem is that you will end up with a
> normative reference with a spec that isn't finished yet.  The
> good news is that I hope and expect to have it wrapped up well
> before the end of the calendar year.

Got it, thanks. We'll certainly be discussing this in our WG meeting...

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org

From klensin@jck.com  Sat Nov  6 11:05:26 2010
Return-Path: <klensin@jck.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 2DBF13A6848; Sat,  6 Nov 2010 11:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599]
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 MoLzoN++3nmj; Sat,  6 Nov 2010 11:05:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 276253A67D4; Sat,  6 Nov 2010 11:05:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PEn91-0002Fo-S1; Sat, 06 Nov 2010 14:05:40 -0400
Date: Sat, 06 Nov 2010 14:05:37 -0400
From: John C Klensin <klensin@jck.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Message-ID: <D88CE8302B1A4A8AC6A44549@[10.40.74.78]>
In-Reply-To: <4CD57E32.1030202@viagenie.ca>
References: <4CD40CD4.3090503@viagenie.ca> <84E442EF93DA69A676651D8E@[10.40.72.147]> <4CD57E32.1030202@viagenie.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ima@ietf.org, vcarddav@ietf.org
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 18:05:26 -0000

--On Saturday, 06 November, 2010 12:11 -0400 Simon Perreault
<simon.perreault@viagenie.ca> wrote:

> John C Klensin wrote, on 11/05/2010 06:41 PM:
>> I would
>> strongly suggest that you have a look at the EAI drafts and
>> that you deal with this by replacing the 5322 addr-spec with
>> the EAI equivalent.  Otherwise, you are just going to create
>> trouble for yourselves and your users.
> 
> To be clear, does "the EAI equivalent" stand for uAddr-spec,
> as defined in
> <http://tools.ietf.org/html/draft-ietf-eai-rfc5335bis-03#secti
> on-4.4>?

Yes, with the qualification that, like all WG I-Ds, this is a
moving target and might change before it is approved.  I
wouldn't personally expect that, but you shouldn't take my
belief as a guarantee.

    john




From klensin@jck.com  Sat Nov  6 11:08:54 2010
Return-Path: <klensin@jck.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 086373A68E0 for <ima@core3.amsl.com>; Sat,  6 Nov 2010 11:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599]
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 j2qPagNnMOXb for <ima@core3.amsl.com>; Sat,  6 Nov 2010 11:08:50 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id EA5E03A68BA for <ima@ietf.org>; Sat,  6 Nov 2010 11:08:49 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PEnCL-0002Iq-Jh; Sat, 06 Nov 2010 14:09:06 -0400
Date: Sat, 06 Nov 2010 14:09:02 -0400
From: John C Klensin <klensin@jck.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, ima@ietf.org
Message-ID: <6A7D1E3456990A9B1039765C@[10.40.74.78]>
In-Reply-To: <4CD57CBF.6000101@viagenie.ca>
References: <E14011F8737B524BB564B05FF748464A10A3B145@TK5EX14MBXC141.redmond.corp.microsoft.com> <4CD57CBF.6000101@viagenie.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] Internationalized email addresses in vCard 4.0
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: Sat, 06 Nov 2010 18:08:54 -0000

--On Saturday, 06 November, 2010 12:05 -0400 Simon Perreault
<simon.perreault@viagenie.ca> wrote:

> Shawn Steele wrote, on 11/05/2010 07:08 PM:
>> Again, not familiar with vCard, but note that users will
>> likely now have 2 addresses:  The native script, and some
>...
> Just FYI: any number of email addresses may be specified in a
> vCard.
> 
>> And it gets "worse" :)  Imagine the Mongolian businessman in
>> Mongolia.  He gets a Mongolian email address to chat with his
>> customers locally.  Cool.  He ALSO gets a Chinese email
>> address to talk to his suppliers and the government.  Then he
>> also gets a third ASCII address to talk to his importers in
>> the US.
> 
> I suppose this would be taken care of by using the LANGUAGE
> parameter, like this:
> 
> EMAIL;LANGUAGE=mn:<address in Mongolian goes here>
> EMAIL;LANGUAGE=zh:<address in Chinese goes here>
> EMAIL;LANGUAGE=en:<address in English goes here>

And, of course, one can have any number of EMAIL addresses in
the same or different languages.  So I don't see any problem in
this area.  A program trying to get from a vCard record to a
mailing address might have an interesting heuristic problem if
it wanted to choose just one, but that problem exists for
ASCII-only addresses (i.e., is nothing new) and is not a problem
that either the vCard or EAI WGs need to solve.

   john


From fujiwara@jprs.co.jp  Sun Nov  7 08:27:20 2010
Return-Path: <fujiwara@jprs.co.jp>
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 052BB3A679C for <ima@core3.amsl.com>; Sun,  7 Nov 2010 08:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 o1y6LIiVbxjD for <ima@core3.amsl.com>; Sun,  7 Nov 2010 08:27:19 -0800 (PST)
Received: from send12.jprs.co.jp (send12.jprs.co.jp [IPv6:2001:df0:8:6::72]) by core3.amsl.com (Postfix) with ESMTP id 5D5D83A6403 for <ima@ietf.org>; Sun,  7 Nov 2010 08:27:18 -0800 (PST)
Received: from sendsms12.jprs.co.jp (sendsms12.jprs.co.jp [202.11.17.114]) by send12.jprs.co.jp (8.13.8+Sun/8.13.8) with ESMTP id oA7GRZiE023625;  Mon, 8 Nov 2010 01:27:35 +0900 (JST)
Received: from sendsms12.jprs.co.jp (unknown [127.0.0.1]) by sendsms12.jprs.co.jp (Symantec Mail Security) with ESMTP id 9497D33C6; Mon,  8 Nov 2010 01:27:35 +0900 (JST)
X-AuditID: ca0b1172-0000000600000914-4c-4cd6d37622a4 
Date: Mon, 08 Nov 2010 01:27:34 +0900 (JST)
Message-Id: <20101108.012734.71096091.fujiwara@jprs.co.jp>
To: presnick@qualcomm.com
From: fujiwara@jprs.co.jp
In-Reply-To: <4CC85DD5.2060701@qualcomm.com>
References: <4CC85DD5.2060701@qualcomm.com>
X-Mailer: Mew version 6.3.50 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
X-Brightmail-Tracker: AAAAAA==
Cc: ima@ietf.org
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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: Sun, 07 Nov 2010 16:27:20 -0000

PiBGcm9tOiBQZXRlIFJlc25pY2sgPHByZXNuaWNrQHF1YWxjb21tLmNvbT4NCj4gSSBzZW50IHRo
ZXNlIGNvbW1lbnRzIHRvIEZ1aml3YXJhLXNhbiwgYnV0IGZvcmdvdCB0byBzZW5kIHRoZW0gdG8g
dGhlDQo+IGxpc3QuIElzc3VlcyB3ZSBuZWVkIHRvIGRlYWwgd2l0aDoNCg0KSSByZWNlaXZlZCBi
b3RoIGNvbW1lbnQgZnJvbSBQZXRlIGFuIEpvaG4gYmVmb3JlIHN1Ym1pc3Npb24uIChUaGFua3Mp
DQpUaGVuLCBJIGFkZGVkIHR3byBhdXRob3Igbm90ZXMuDQoNCkZpcnN0Og0KICAgW1sgTm90ZTog
UkZDIDUzMjIgZG9lcyBub3QgYWxsb3cgZ3JvdXAgc3ludGF4IGluICJGcm9tOiIsICJSZXNlbnQt
DQogICBGcm9tOiIsICJTZW5kZXI6IiwgIlJlc2VudC1TZW5kZXI6IiwgYnV0IHByb3Bvc2VkIG1l
dGhvZCB1c2VzIGdyb3VwDQogICBzeW50YXguICBUaGlzIHByb2JsZW0gbmVlZCB0byBiZSBmaXhl
ZC4gXV0NCg0KPiAxLiBOb3cgdGhhdCB3ZSBhcmUgYWxsb3dpbmcgdGhlIGRvd25ncmFkZSBvZiAi
RnJvbToiIGFuZCAiUmVzZW50LUZyb206IiB3aXRob3V0IGFuIGFsdC1hZGRyZXNzLCB3ZSBtdXN0
IHBvaW50IG91dCB0aGF0IFJGQyA1MzIyIGRvZXMgKm5vdCogYWxsb3cgZ3JvdXAgc3ludGF4IGlu
ICJGcm9tOiIgYW5kICJSZXNlbnQtRnJvbToiIGFuZCB0aGF0IHRoaXMgZG9jdW1lbnQgY2hhbmdl
cyB0aGF0IHN5bnRheC4gSSB0aGluayB0aGF0IGlzIGZpbmUgdG8gZG8gdGhhdCwgYnV0IHRoaXMg
ZG9jdW1lbnQgbmVlZHMgdG8gZXhwbGljaXRseSBzYXkgdGhhdC4gUGVyaGFwcyBzb21ldGhpbmcg
bGlrZSB0aGlzOg0KDQpzbmlwDQoNCj4gVGhlIGRlZmluaXRpb24gZm9yIHRoZXNlIGhlYWRlciBm
aWVsZHMgaW4gW1JGQzUzMjJdIG9ubHkgYWxsb3cgPG1haWxib3g+IG9yIDxtYWlsYm94LWxpc3Q+
LCB3aGljaCBtZWFucyB0aGF0IHRoZXkgY2Fubm90IGNvbnRhaW4gdGhlIGdyb3VwIHN5bnRheCBm
b3IgTUFJTEJPWCBkb3duZ3JhZGluZyBkZXNjcmliZWQgaW4gc2VjdGlvbiA0LjEuNy4gVGhlcmVm
b3JlLCB0aGlzIHNwZWNpZmljYXRpb24gY2hhbmdlcyB0aGUgc3ludGF4IG9mIHRoZSBhYm92ZSBm
aWVsZHMgYXMgZm9sbG93cyB0byBhbGxvdyBhIGdyb3VwIHRvIGFwcGVhcjoNCj4gDQo+IGZyb20g
PSAiRnJvbToiIGFkZHJlc3MtbGlzdCBDUkxGDQo+IHNlbmRlciA9ICJTZW5kZXI6IiBhZGRyZXNz
IENSTEYNCj4gcmVzZW50LWZyb20gPSAiUmVzZW50LUZyb206IiBhZGRyZXNzLWxpc3QgQ1JMRg0K
PiByZXNlbnQtc2VuZGVyID0gIlJlc2VudC1TZW5kZXI6IiBhZGRyZXNzIENSTEYNCj4gDQo+IElm
IHRoZSBoZWFkZXIgZmllbGQgY29udGFpbnMgPG1haWxib3g+IGVsZW1lbnRzIHRoYXQgY29udGFp
biBub24tQVNDSUkgYWRkcmVzc2VzLCBwZXJmb3JtIENPTU1FTlQgZG93bmdyYWRpbmcsIERJU1BM
QVktTkFNRSBkb3duZ3JhZGluZywgYW5kIE1BSUxCT1ggZG93bmdyYWRpbmcuDQoNClRoaXMgc3Vn
Z2VzdGlvbiBtYXkgYnJlYWsgUkZDIDUzMjIgY29tcGxpYW50IE1VQS4NCg0KSSBoYXZlIGFub3Ro
ZXIgaWRlYSBhbmQgaXQgaXMgbm90IGJlYXV0aWZ1bC4NCg0KMS4gUmVjb3ZlciBEb3duZ3JhZGVk
LXtGcm9tLFNlbmRlcixSZXNlbnQtRnJvbSxSZXNlbnQtU2VuZGVyfSBoZWFkZXIgZmllbGRzLg0K
Mi4gZm9yIGVhY2gge0Zyb20sU2VuZGVyLFJlc2VudC1Gcm9tLFJlc2VudC1TZW5kZXJ9IGhlYWRl
ciBmaWVsZHMsDQogICAyLjEgaWYgdGhlIGhlYWVyIGZpZWxkIGNvbnRhaW5zIG5vbi1BU0NJSSBh
ZGRyZXNzLA0KICAgICAgICAgZW5jYXBzdWxhdGUgaXQgaW50byBEb3duZ3JhZGVkLSogaGVhZGVy
IGZpZWxkLg0KICAgMi4yIGlmIHRoZSBoZWFkZXIgZmllbGQgaXMgbm90IGEgIkZyb20iIGhlYWRl
ciwgcmVtb3ZlIHRoZSBoZWFkZXIgZmllbGQuDQogICAgICAgKGJlY2F1c2UgaXQgaXMgbm90IG5l
Y2Vzc2FyeSBpbiB0aGUgcG9pbnQgb2YgdGhlIFJGQzUzMjIgY29uZm9ybWFuY2UuKQ0KICAgMi4z
IGlmIHRoZSBoZWFkZXIgZmllbCBpcyBhICJGcm9tIiBoZWFkZXIsIGlmIGl0IGNvbnRhaW5zIG9u
ZSBvciBtb3JlIA0KICAgICAgIEFTQ0lJIG1haWxib3gsIHJlbW92ZSBub24tQVNDSUkgbWFpbGJv
eCBlbGVtZW50Lg0KICAgMi40IGlmIHRoZSBoZWFlciBmaWVsZCBpcyBhICJGcm9tIiBoZWFkZXIg
YW5kIGl0IGRvZXMgbm90IGNvbnRhaW4gQVNDSUkNCiAgICAgICBtYWlsYm94LCByZXdyaXRlIGl0
IGFzIHByZS1jb25maWd1cmVkIHBvcC1zZXJ2ZXIncyBkYWVtb24gRS1tYWlsIGFkZHJlc3MuDQoN
ClRoZW4gZ2VuZXJhdGVkIHBvcC1pbWFwIGRvd25ncmFkZWQgbWVzc2FnZSBjb250YWluczoNCiAg
RnJvbTogPHBvcC1zZXJ2ZXJAcG9wLWRvbT4NCiAgRG93bmdyYWRlZC1Gcm9tOiBFTkNPREVELVdP
UkQoRnJvbSkNCiAgRG93bmdyYWRlZC1TZW5kZXI6IEVOQ09ERUQtV09SRChTZW5kZXIpDQogIERv
d25ncmFkZWQtUmVzZW50LUZyb206IEVOQ09ERUQtV09SRChSZXNlbnQtRnJvbSkNCiAgRG93bmdy
YWRlZC1SZXNlbnQtU2VuZGVyOiBFTkNPREVELVdPUkQoUmVzZW50LVNlbmRlcikNCg0KVGhlIHJl
Y2lwaWVudCBjYW4gcmVhZCBtb3N0IG9mIHRoZSByZWNlaXZlZCBtZXNzYWdlIGV4Y2VwdCBGcm9t
OiBoZWFkZXIgZmllbGQuDQoNCk9yIGVuY29kZSBGcm9tOiBoZWFkZXIgZmllbGQgaW50byBTdWJq
ZWN0IGhlYWRlciB2YWx1ZT8NCg0KICBTdWJqZWN0OiBwb3BpbWFwLWRvd25ncmFkZWQ6IEZyb209
PEZyb20+OiBTdWJqZWN0PTxTdWJqZWN0Pg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KU2Vjb25kOg0K
DQogICBbWyBOb3RlOiBJZiB0aGUgb3JpZ2luYWwgbm9uLUFTQ0lJIGFkZHJlc3MgaXMgYSBwYXJ0
IG9mIGEgZ3JvdXANCiAgIGFkZHJlc3MsIHRoaXMgcmV3cml0aW5nIG1heSBjb25mbGljdCB0aGUg
b3JpZ2luYWwgRElTUExBWS1OQU1FLiAgVGhpcw0KICAgcHJvYmxlbSBuZWVkIHRvIGJlIGZpeGVk
LiBdXQ0KDQoNCj4gMi4gTUFJTEJPWCBkb3duZ3JhZGluZyBtYWtlcyBncm91cCBzeW50YXggcmVj
dXJzaXZlIGZvciBvdGhlciBhZGRyZXNzIGZpZWxkcy4gVGhpcyBvbmUgSSdtIGxlc3MgY29uZmlk
ZW50IGFib3V0LiBCdXQgbGV0J3Mgc2F5IHlvdSBnZXQgYSBtZXNzYWdlIGxpa2UgdGhpczoNCj4g
DQo+IFRvOiBNeSBGcmllbmRzOiA85aea5YGl5bq3QGNubmljLmNuPiwgPOadjuaZk+S4nEBjbm5p
Yy5jbj47DQoNCkluIG1hbnkgY2FzZXMsIGJvdGggPG1haWxib3g+cyBhcmUgcmVtb3ZlZCBiZWZv
cmUgcG9wL2ltYXAgc2VydmVycy4NCkJ1dCBuZWVkIHRvIGNvbnNpZGVyLg0KDQo+IEFjY29yZGlu
ZyB0byB0aGUgcnVsZXMsIHlvdSBkb3duZ3JhZGUgdGhpcyB0bzoNCj4gDQo+IFRvOiBNeUZyaWVu
ZHM6IEludGVybmF0aW9uYWxpemVkIEFkZHJlc3MgPDxZYW8ncyAyMDQ3IGFkZHJlc3M+PiBSZW1v
dmVkOjssIEludGVybmF0aW9uYWxpemVkIEFkZHJlc3MgPDxYaWFvZG9uZydzIDIwNDcgYWRkcmVz
cz4+IFJlbW92ZWQ6Ow0KPiANCj4gSSB0aGluayB0aGlzIGlzIE9LLCBidXQgaXQgY2hhbmdlcyB0
aGUgc3ludGF4IG9mIGdyb3VwIHRvOg0KPiANCj4gZ3JvdXAgPSBkaXNwbGF5LW5hbWUgIjoiIFtn
cm91cCAvIGdyb3VwLWxpc3RdICI7IiBbQ0ZXU10NCj4gDQo+IElmIGV2ZXJ5b25lIGlzIE9LIHdp
dGggdGhpcywgaXQgc2hvdWxkIGdvIGluIHRoZSBkb2N1bWVudCBzb21ld2hlcmUuDQoNCkJ1dCBp
dCBtYXkgYnJlYWsgUkZDIDUzMjIgY29tcGxpYW50IE1VQXMuDQoNClRoZW4sIEkgaGF2ZSBhbiBp
ZGVhLg0KSWYgPGdyb3VwLWxpc3Q+IGNvbnRhaW5zIG5vbi1BU0NJSSA8bWFpbGJveD5zLCBlbmNv
ZGUgd2hvbGUgPGdyb3VwLWxpc3Q+IHRvIA0KIkludGVybmF0aW9uYWxpemUgQWRkcmVzcyIgRU5D
T0RFRC1XT1JEKDxncm91cC1saXN0PikgUmVtb3ZlZDo7Ig0KDQo+IFRvOiBNeSBGcmllbmRzOiA8
5aea5YGl5bq3QGNubmljLmNuPiwgPOadjuaZk+S4nEBjbm5pYy5jbj47DQoNClRoaXMgZXhhbXBs
ZSBtYXkgYmUgZW5jb2RlZCBhczoNCg0KVG86IEludGVybmF0aW9uYWxpemVkIEFkZHJlc3MgPT9V
VEYtOD9RP015RnJpZW5kczpfPDxZYW8ncyAyMDQ3IGFkZHJlc3M+PixfPDxYaWFvZG9uZydzIDIw
NDcgYWRkcmVzcz4+Oz89IFJlbW92ZWQ6Ow0KDQojIEVuY29kZWQgd29yZCBtYXkgYmUgc3BsaXRl
ZCAoZGVmaW5lZCBpbiBSRkMgMjA0NykNCg0KSXMgaXQgYWNjZXB0YWJsZT8NCg0KLS0NCkthenVu
b3JpIEZ1aml3YXJhLCBKUFJTIDxmdWppd2FyYUBqcHJzLmNvLmpwPg0K

From McQuilWP@pobox.com  Sun Nov  7 09:57:07 2010
Return-Path: <McQuilWP@pobox.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 2579F3A6872 for <ima@core3.amsl.com>; Sun,  7 Nov 2010 09:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 yuYd2cI2tzpk for <ima@core3.amsl.com>; Sun,  7 Nov 2010 09:57:06 -0800 (PST)
Received: from sasl.smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by core3.amsl.com (Postfix) with ESMTP id 13FED3A686B for <ima@ietf.org>; Sun,  7 Nov 2010 09:57:04 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id CA29022E1; Sun,  7 Nov 2010 12:57:22 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=PacNqbwze57y 8ozWEeb9y81GxG8=; b=b2e4zR/6YGS3b4eCyA5a1c4lgsh8LFBVz+nXvQseEmuh TkCzkUglfhnAzvOxTuEs9mdL9y+aGCv/8wgr28Whxeoe5rs7NQbAbWKEeBTPxgb3 MK7y4J/iybJkh47fQ9R6e4yokgxfygcBexL+2AecOJS0BTMnhtNznyuiFM0wMPo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=vUz5Dx jF+TTdPMFsre4bET2rR/kec4GyBcZpi1AlVVyufwNf4FS1QxvnTBozLDAwfk//7v GN93A5/S+kH+ZpLDLlO80vz4qAbLP9ZnrZn6bKyaWqEDyUYJ/NkwJ6xVuuImqI1G J0fReG5W2Zu+9xYip2rH9SLzJc/XfmMRjVkQA=
Received: from b-pb-sasl-quonix. (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id B850122E0; Sun,  7 Nov 2010 12:57:21 -0500 (EST)
Received: from [192.168.0.2] (unknown [68.107.61.33]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 385C422DD; Sun,  7 Nov 2010 12:57:20 -0500 (EST)
Date: Sun, 7 Nov 2010 09:57:18 -0800
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <183300747.20101107095718@pobox.com>
To: IMA Discussion <ima@ietf.org>
In-Reply-To: <20101108.012734.71096091.fujiwara@jprs.co.jp>
References: <4CC85DD5.2060701@qualcomm.com> <20101108.012734.71096091.fujiwara@jprs.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 783865DA-EA98-11DF-BDDF-8E8CAFBB27C9-02871704!b-pb-sasl-quonix.pobox.com
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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: Sun, 07 Nov 2010 17:57:07 -0000

On Sun, 2010-11-07, fujiwara@jprs.co.jp wrote:

> I have another idea and it is not beautiful.

> 1. Recover Downgraded-{From,Sender,Resent-From,Resent-Sender} header fields.

Please, if we need something like the Downgraded-* fields, do NOT call them that. The names are very misleading.

Instead, how about Encoded-From, Encoded-To, etc.?

Or even, Incompatible-From, etc.?
 
-- 
Bill McQuillan <McQuilWP@pobox.com>


From daniel@taharlev.com  Mon Nov  8 00:37:34 2010
Return-Path: <daniel@taharlev.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 1B3543A6452 for <ima@core3.amsl.com>; Mon,  8 Nov 2010 00:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 FyLyH100uE5t for <ima@core3.amsl.com>; Mon,  8 Nov 2010 00:37:33 -0800 (PST)
Received: from p3plsmtpa01-02.prod.phx3.secureserver.net (p3plsmtpa01-02.prod.phx3.secureserver.net [72.167.82.82]) by core3.amsl.com (Postfix) with SMTP id 250CA3A67D4 for <ima@ietf.org>; Mon,  8 Nov 2010 00:37:32 -0800 (PST)
Received: (qmail 3456 invoked from network); 8 Nov 2010 08:37:53 -0000
Received: from unknown (94.159.188.124) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 08 Nov 2010 08:37:52 -0000
Message-ID: <001301cb7f20$3b306720$7b01a8c0@dtm1330>
From: "Daniel Taharlev" <daniel@taharlev.com>
To: "Bill McQuillan" <McQuilWP@pobox.com>, "IMA Discussion" <ima@ietf.org>
References: <4CC85DD5.2060701@qualcomm.com><20101108.012734.71096091.fujiwara@jprs.co.jp> <183300747.20101107095718@pobox.com>
Date: Mon, 8 Nov 2010 10:37:48 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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, 08 Nov 2010 08:37:34 -0000

What about "Compatible-From" or "Compliant-From"?
----- Original Message ----- 
From: "Bill McQuillan" <McQuilWP@pobox.com>
To: "IMA Discussion" <ima@ietf.org>
Sent: Sunday, November 07, 2010 7:57 PM
Subject: Re: [EAI] popimap-downgrade-00 - group syntax


>
> On Sun, 2010-11-07, fujiwara@jprs.co.jp wrote:
>
>> I have another idea and it is not beautiful.
>
>> 1. Recover Downgraded-{From,Sender,Resent-From,Resent-Sender} header 
>> fields.
>
> Please, if we need something like the Downgraded-* fields, do NOT call 
> them that. The names are very misleading.
>
> Instead, how about Encoded-From, Encoded-To, etc.?
>
> Or even, Incompatible-From, etc.?
>
> -- 
> Bill McQuillan <McQuilWP@pobox.com>
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
> 


From McQuilWP@pobox.com  Mon Nov  8 01:27:06 2010
Return-Path: <McQuilWP@pobox.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 9C8C93A693C for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ogQx3i2AmKsf for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:27:05 -0800 (PST)
Received: from sasl.smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by core3.amsl.com (Postfix) with ESMTP id 985BC3A6934 for <ima@ietf.org>; Mon,  8 Nov 2010 01:27:05 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id C1391179E; Mon,  8 Nov 2010 04:27:25 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=Tg2KU69YA/++ TZ+ss4+ufeLl9pg=; b=O4SCDangbaQeunUvQ+SBEpfjtsdeCj5Dnj3hbbo2tSin /xBS05hz7g4hPpf5IQ5CgPZSo8gUwsmPZ0oFLTZCoJnbqtPuITt05hxppmJbjLiI 5e6dsYvWfGeAWoKfc06EC++k8GWCeZmfyYFXhgysqUmVHSENsqdrrtc+pvWY/bM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=KeA8ZT ehrny9eTd80zDXlYMhzQtlzmBhvCxIA7G5eZ+WedBj04PFepmcxEbFqpQD8yszMI pjJS0LMx+Gz9JIGTrHDIcYU+9l+UNxpIje35vsagPk9mPthAh46rSgz5OjdK7bKf +cKyhR0vV3HySWz0Z3pHdmaJH4tnbsF2wIF/0=
Received: from b-pb-sasl-quonix. (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id AA8E6179D; Mon,  8 Nov 2010 04:27:24 -0500 (EST)
Received: from [192.168.0.2] (unknown [68.107.61.33]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 36179179C; Mon,  8 Nov 2010 04:27:23 -0500 (EST)
Date: Mon, 8 Nov 2010 01:27:22 -0800
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <507553174.20101108012722@pobox.com>
To: IMA Discussion <ima@ietf.org>
In-Reply-To: <001301cb7f20$3b306720$7b01a8c0@dtm1330>
References: <4CC85DD5.2060701@qualcomm.com><20101108.012734.71096091.fujiwara@jprs.co.jp> <183300747.20101107095718@pobox.com> <001301cb7f20$3b306720$7b01a8c0@dtm1330>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 655D3062-EB1A-11DF-B3EA-8E8CAFBB27C9-02871704!b-pb-sasl-quonix.pobox.com
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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, 08 Nov 2010 09:27:06 -0000

On Mon, 2010-11-08, Daniel Taharlev wrote:
> What about "Compatible-From" or "Compliant-From"?

I would be worried that I'm not sure what the field is supposed to be
compatible with or compliant to.

Consider the consumer of this header field: Someone behind a legacy MTA who
can get his/her (probably legacy) MUA to display unknown header fields.

That consumer would wonder why the From: field didn't seem to correspond
with what might be expected, but the "XXXXXX-From:" field might have its
encoded words decoded into something that he/she recognizes. What would be
an appropriate name for that field?

From-Actually-Was: ?
From-Untranslated: ?
Untranslated-From: ?
Replaced-From: ?

I am more interested that the wordage mean something to the user rather
than the implementers.

-- 
Bill McQuillan <McQuilWP@pobox.com>


From daniel@taharlev.com  Mon Nov  8 01:29:35 2010
Return-Path: <daniel@taharlev.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 D62FA3A693C for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:29:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 pgVoab-MKzBs for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:29:35 -0800 (PST)
Received: from p3plsmtpa01-08.prod.phx3.secureserver.net (p3plsmtpa01-08.prod.phx3.secureserver.net [72.167.82.88]) by core3.amsl.com (Postfix) with SMTP id 034263A6934 for <ima@ietf.org>; Mon,  8 Nov 2010 01:29:34 -0800 (PST)
Received: (qmail 12313 invoked from network); 8 Nov 2010 09:29:55 -0000
Received: from unknown (94.159.188.124) by p3plsmtpa01-08.prod.phx3.secureserver.net (72.167.82.88) with ESMTP; 08 Nov 2010 09:29:54 -0000
Message-ID: <001401cb7f27$7fb854f0$7b01a8c0@dtm1330>
From: "Daniel Taharlev" <daniel@taharlev.com>
To: "Bill McQuillan" <McQuilWP@pobox.com>, "IMA Discussion" <ima@ietf.org>
References: <4CC85DD5.2060701@qualcomm.com><20101108.012734.71096091.fujiwara@jprs.co.jp><183300747.20101107095718@pobox.com><001301cb7f20$3b306720$7b01a8c0@dtm1330> <507553174.20101108012722@pobox.com>
Date: Mon, 8 Nov 2010 11:29:50 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
Subject: Re: [EAI] popimap-downgrade-00 - group syntax
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, 08 Nov 2010 09:29:35 -0000

For the user, a term -- even if not completely accurate -- like 
"Secondary-From" would make the most sense, although it's not really a 
secondary.
----- Original Message ----- 
From: "Bill McQuillan" <McQuilWP@pobox.com>
To: "IMA Discussion" <ima@ietf.org>
Sent: Monday, November 08, 2010 11:27 AM
Subject: Re: [EAI] popimap-downgrade-00 - group syntax


>
> On Mon, 2010-11-08, Daniel Taharlev wrote:
>> What about "Compatible-From" or "Compliant-From"?
>
> I would be worried that I'm not sure what the field is supposed to be
> compatible with or compliant to.
>
> Consider the consumer of this header field: Someone behind a legacy MTA 
> who
> can get his/her (probably legacy) MUA to display unknown header fields.
>
> That consumer would wonder why the From: field didn't seem to correspond
> with what might be expected, but the "XXXXXX-From:" field might have its
> encoded words decoded into something that he/she recognizes. What would be
> an appropriate name for that field?
>
> From-Actually-Was: ?
> From-Untranslated: ?
> Untranslated-From: ?
> Replaced-From: ?
>
> I am more interested that the wordage mean something to the user rather
> than the implementers.
>
> -- 
> Bill McQuillan <McQuilWP@pobox.com>
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
> 


From fujiwara@jprs.co.jp  Mon Nov  8 01:39:35 2010
Return-Path: <fujiwara@jprs.co.jp>
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 3B4D328C0DF for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 vlKsrPHHr4Mw for <ima@core3.amsl.com>; Mon,  8 Nov 2010 01:39:29 -0800 (PST)
Received: from send12.jprs.co.jp (send12.jprs.co.jp [IPv6:2001:df0:8:6::72]) by core3.amsl.com (Postfix) with ESMTP id 01BB03A6966 for <ima@ietf.org>; Mon,  8 Nov 2010 01:39:27 -0800 (PST)
Received: from sendsms12.jprs.co.jp (sendsms12.jprs.co.jp [202.11.17.114]) by send12.jprs.co.jp (8.13.8+Sun/8.13.8) with ESMTP id oA89dimp004596;  Mon, 8 Nov 2010 18:39:44 +0900 (JST)
Received: from sendsms12.jprs.co.jp (unknown [127.0.0.1]) by sendsms12.jprs.co.jp (Symantec Mail Security) with ESMTP id 2251833C6; Mon,  8 Nov 2010 18:39:44 +0900 (JST)
X-AuditID: ca0b1172-0000000600000914-00-4cd7c55f36cd 
Date: Mon, 08 Nov 2010 18:39:43 +0900 (JST)
Message-Id: <20101108.183943.104040737.fujiwara@jprs.co.jp>
To: McQuilWP@pobox.com
From: fujiwara@jprs.co.jp
In-Reply-To: <183300747.20101107095718@pobox.com>
References: <4CC85DD5.2060701@qualcomm.com> <20101108.012734.71096091.fujiwara@jprs.co.jp> <183300747.20101107095718@pobox.com>
X-Mailer: Mew version 6.3.50 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: ima@ietf.org
Subject: [EAI] Preserving header field name issue (Re: popimap-downgrade-00 - group syntax)
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, 08 Nov 2010 09:39:35 -0000

There are multiple proposals for new preserving header fields.
The discussion is OK, but it is another issue.

But "Downgraded-*" header field name was not rejected at the
experimental stage.  Why did you comment it last year ?

I will use "Downgraded-*" header field name until naming discussion will fix.

Regards,

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>

From jason@exchange.microsoft.com  Mon Nov  8 21:57:16 2010
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 A16CE3A6938 for <ima@core3.amsl.com>; Mon,  8 Nov 2010 21:57:16 -0800 (PST)
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 y+OoqFe9vlfr for <ima@core3.amsl.com>; Mon,  8 Nov 2010 21:57:15 -0800 (PST)
Received: from mail.exchange.microsoft.com (mail1.exchange.microsoft.com [131.107.1.17]) by core3.amsl.com (Postfix) with ESMTP id C32E63A693A for <ima@ietf.org>; Mon,  8 Nov 2010 21:57:15 -0800 (PST)
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.218.15; Mon, 8 Nov 2010 21:57:38 -0800
Received: from DF-M14-06.exchange.corp.microsoft.com ([169.254.3.152]) by DF-H14-01.exchange.corp.microsoft.com ([157.54.78.139]) with mapi id 14.01.0255.003; Mon, 8 Nov 2010 21:57:38 -0800
From: Jason Nelson <jason@exchange.microsoft.com>
To: "fujiwara@jprs.co.jp" <fujiwara@jprs.co.jp>, "McQuilWP@pobox.com" <McQuilWP@pobox.com>
Thread-Topic: [EAI] Preserving header field name issue (Re: popimap-downgrade-00 - group syntax)
Thread-Index: AQHLfyjp0NN7Ie/oUECXgpBCZLwM2JNopIMg
Date: Tue, 9 Nov 2010 05:57:37 +0000
Message-ID: <6CE0D5FA2297784CB7A6F5F09865C8954365E295@DF-M14-06.exchange.corp.microsoft.com>
References: <4CC85DD5.2060701@qualcomm.com> <20101108.012734.71096091.fujiwara@jprs.co.jp> <183300747.20101107095718@pobox.com> <20101108.183943.104040737.fujiwara@jprs.co.jp>
In-Reply-To: <20101108.183943.104040737.fujiwara@jprs.co.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
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] Preserving header field name issue (Re: popimap-downgrade-00 - group syntax)
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: Tue, 09 Nov 2010 05:57:16 -0000

The real problem I have with appending anything to the header name when cha=
nging encoding is that it makes header consumption by clients dependent on =
knowledge of the fact that the message has been downgraded. =20

Let us say that we add information in a normal x-header fashion, and it is =
a text header.  The client knows to look for x-fubar and consume it.
Now it needs to know to look for...downgraded-x-fubar?  X-downgraded-fubar?=
  If I'm going to update the clients to consume the downgraded content, I'd=
 just update them to consume utf8 directly.  The downgraded content isn't a=
s compatible as it seems.

Are there any UTF8-isms that don't downgrade to 2047 encoding cleanly outsi=
de of the local part of addresses?

-----Original Message-----
From: ima-bounces@ietf.org [mailto:ima-bounces@ietf.org] On Behalf Of fujiw=
ara@jprs.co.jp
Sent: Monday, November 08, 2010 1:40 AM
To: McQuilWP@pobox.com
Cc: ima@ietf.org
Subject: [EAI] Preserving header field name issue (Re: popimap-downgrade-00=
 - group syntax)

There are multiple proposals for new preserving header fields.
The discussion is OK, but it is another issue.

But "Downgraded-*" header field name was not rejected at the experimental s=
tage.  Why did you comment it last year ?

I will use "Downgraded-*" header field name until naming discussion will fi=
x.

Regards,

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp> _____________________________=
__________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima

From Internet-Drafts@ietf.org  Tue Nov  9 01:00:03 2010
Return-Path: <Internet-Drafts@ietf.org>
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 B4EAF3A6897; Tue,  9 Nov 2010 01:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.069
X-Spam-Level: 
X-Spam-Status: No, score=-102.069 tagged_above=-999 required=5 tests=[AWL=0.530, BAYES_00=-2.599, 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 3XMNNW0PePvQ; Tue,  9 Nov 2010 01:00:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D48823A695E; Tue,  9 Nov 2010 01:00:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
Message-ID: <20101109090001.12875.70325.idtracker@localhost>
Date: Tue, 09 Nov 2010 01:00:01 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-5378bis-00.txt
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: Tue, 09 Nov 2010 09:00:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email Address Internationalization Working Group of the IETF.


	Title           : IMAP Support for UTF-8
	Author(s)       : P. Resnick, et al.
	Filename        : draft-ietf-eai-5378bis-00.txt
	Pages           : 15
	Date            : 2010-11-08

This specification extends the Internet Message Access Protocol
version 4rev1 (IMAP4rev1) to support UTF-8 encoded international
characters in user names, mail addresses and message headers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-5378bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-eai-5378bis-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-09004908.I-D@ietf.org>


--NextPart--

From klensin@jck.com  Wed Nov 24 16:45:58 2010
Return-Path: <klensin@jck.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 B46383A69E1 for <ima@core3.amsl.com>; Wed, 24 Nov 2010 16:45:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 bm4o3AcyxxWr for <ima@core3.amsl.com>; Wed, 24 Nov 2010 16:45:57 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 782C63A69C3 for <ima@ietf.org>; Wed, 24 Nov 2010 16:45:57 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PLPzF-000CUU-OP for ima@ietf.org; Wed, 24 Nov 2010 19:46:57 -0500
Date: Wed, 24 Nov 2010 19:46:57 -0500
From: John C Klensin <klensin@jck.com>
To: EAI WG <ima@ietf.org>
Message-ID: <8C5197623144E221F70F258F@[192.168.1.128]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [EAI] WG last call expires Friday
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: Thu, 25 Nov 2010 00:45:58 -0000

Hi.

Just as a reminder, we agreed in Beijing that WG Last Call on 

SMTP-bis (draft-ietf-eai-rfc5336bis-04) and
Header-bis (draft-ietf-eai-rfc5335bis-03)

would expire this Friday, 26 November and that 

 DSN-bis (draft-ietf-eai-rfc5337bis-dsn)

would be on the same schedule if Tony managed to get issues
resolved among the authors and a draft posted by early last week.

While DSN-bis is not ready, the status of the other two is
unchanged.  I'd appreciate comments, even if they are "looks ok"
from those who agreed to review those documents (and any others
who did review them) posted to this list as soon as possible.
Unless substantive comments are received that indicates that
they should be held up, Joseph and I will hand the off to Alexey
for IESG processing and IETF Last Call at the beginning of next
week.

Note also that 

	POP-bis (draft-ietf-eai-rfc5721bis)   and
	IMAP-bis (draft-ietf-eai-rfc5738bis)

are right behind the three above, with comments expected by
December 3.  Message downgrading
(draft-ietf-eai-popimap-downgrade) should be right behind them,
going into WG Last Call as soon as Pete posts the summary of
discussions in Beijing to the list and a new version, consistent
with the result of those discussions, is published.

We should still be on schedule to get all six of those documents
finished up and in the IESG's hands significantly before the end
of the calendar year.

If any of you have substantive technical objections, this is the
time to speak up.

    john



From yaojk@cnnic.cn  Wed Nov 24 20:03:15 2010
Return-Path: <yaojk@cnnic.cn>
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 AA8043A6A8B for <ima@core3.amsl.com>; Wed, 24 Nov 2010 20:03:15 -0800 (PST)
X-Quarantine-ID: <odhuUTjc6Mbw>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -97.81
X-Spam-Level: 
X-Spam-Status: No, score=-97.81 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 odhuUTjc6Mbw for <ima@core3.amsl.com>; Wed, 24 Nov 2010 20:03:14 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 9D3AE3A69ED for <ima@ietf.org>; Wed, 24 Nov 2010 20:03:11 -0800 (PST)
Received: (eyou send program); Thu, 25 Nov 2010 12:04:11 +0800
Message-ID: <490657851.13158@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 25 Nov 2010 12:04:11 +0800
Message-ID: <9859A398869E4D3D8C702EFBC59E2288@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
Date: Thu, 25 Nov 2010 12:04:11 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0262_01CB8C98.DECBFFE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] 79 ietf  eai minutes
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: Thu, 25 Nov 2010 04:03:15 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0262_01CB8C98.DECBFFE0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0263_01CB8C98.DECBFFE0"


------=_NextPart_001_0263_01CB8C98.DECBFFE0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

DQoNCkRlYXIgYWxsLA0KDQogICB0aGUgZWFpIHdnIG1lZXRpbmcgbWludXRlcyBpbiBpZXRmIDc5
IGhhcyBiZWVuIHB1Ymxpc2hlZC4NCg0KICB0aGUgbWludXRlcyBpcyBhdHRhY2hlZCBvciB5b3Ug
Y2FuIGZvbGxvdyB0aGUgbGluayAgaHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy83OS9t
aW51dGVzL2VhaS50eHQNCg0KICAgaWYgeW91IGhhdmUgYW55IGNvbW1lbnRzLCBwbHMgc2VuZCBp
dCBiZWZvcmUgMSBEZWMuDQoNCg0KcmVtaW5kZXI6DQpBbnlvbmUgd2hvIHJhaXNlZCBoaXMgaGFu
ZCBhbmQgY29tbWl0dGVkIHRvIHJldmlldyBkb2NzDQpzaG91bGQgZG8gc28gYXMgcHJvbWlzZWQu
IA0KDQoNCkppYW5rYW5nIFlhbw==

------=_NextPart_001_0263_01CB8C98.DECBFFE0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBuYW1lPUdFTkVSQVRPUiBjb250
ZW50PSJNU0hUTUwgOC4wMC42MDAxLjE4OTc1Ij4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFEPg0K
PEJPRFkgYmdDb2xvcj0jY2NlOGNmPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPjxCUj48L0RJ
Vj4NCjxESVY+PEZPTlQgc2l6ZT0yPkRlYXIgYWxsLDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQg
c2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNw
OyB0aGUgZWFpIHdnIG1lZXRpbmcgbWludXRlcyBpbiBpZXRmIDc5IGhhcyBiZWVuIA0KcHVibGlz
aGVkLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyB0aGUgbWludXRlcyZuYnNwO2lzIGF0dGFjaGVkIG9y
IHlvdSZuYnNwO2NhbiBmb2xsb3cgdGhlIA0KbGluayZuYnNwOyA8QSANCmhyZWY9Imh0dHA6Ly93
d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvNzkvbWludXRlcy9lYWkudHh0Ij5odHRwOi8vd3d3Lmll
dGYub3JnL3Byb2NlZWRpbmdzLzc5L21pbnV0ZXMvZWFpLnR4dDwvQT48L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4m
bmJzcDsmbmJzcDsgaWYgeW91IGhhdmUgYW55IGNvbW1lbnRzLCBwbHMgc2VuZCBpdCBiZWZvcmUg
MSANCkRlYy48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9E
SVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPnJlbWluZGVy
OjxCUj5BbnlvbmUgd2hvIHJhaXNlZCBoaXMgaGFuZCBhbmQgY29tbWl0dGVkIHRvIHJldmlldyAN
CmRvY3M8QlI+c2hvdWxkIGRvIHNvIGFzIHByb21pc2VkLiA8L0RJVj4NCjxESVY+Jm5ic3A7PC9E
SVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8
L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkppYW5rYW5nIFlhbzwvRk9OVD48L0RJVj48L0JPRFk+
PC9IVE1MPg0K

------=_NextPart_001_0263_01CB8C98.DECBFFE0--

------=_NextPart_000_0262_01CB8C98.DECBFFE0
Content-Type: text/plain;
	name="eai-79.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="eai-79.txt"


-------------------------------------------=20
Meeting=20

Email Address Internationalization (EAI) WG minutes=20

IETF 79, Tuesday, November 9th, 2010=20
0900-1130=20
Garden Ballroom 3=20
Chair: John Klensin =20
   Joseph Yee
Minutes: Jiankang Yao

Blue Sheet, Scribe=20
- scriber: Jiankang Yao


Agenda Bashing=20
- none=20


Documents Discussion=20


SMTP-bis (draft-ietf-eai-rfc5336bis-04):=20
a) no known issues=20
b) WG last call until 26 Nov.=20
c) several volunteers promise to review it=20

Header-bis (draft-ietf-eai-rfc5335bis-03):=20
a) message/global MIME type registrations needs to be updated=20
b) no other known issues=20
c) WG last call until 26 Nov.=20
d) several volunteers promise to review it=20

DSN-bis (draft-ietf-eai-rfc5337bis-dsn-01):=20
a) several issues are identified, and Tony promises to submit the new =
version soon.=20
b) WG last call until 26 Nov.=20
c) several volunteers promise to review it=20

POP-bis (draft-ietf-eai-rfc5721bis-00):=20
a) no known issues=20
b) WG last call until 3 Dec.=20
c) several volunteers promise to review it=20

IMAP-bis (rfc5738bis):=20
a) it has been submitted as the wg draft=20
b) no known issues=20

Post-delivery Message Downgrading for Internationalized Email Messages=20
(draft-ietf-eai-popimap-downgrade-00)=20
a) the group syntax problems are discussed=20
b) group syntax and comment syntax are proposed, group syntax gets =
consensus in meeting=20
c) Pete promises to summarize the discussion result and send it to the =
list=20

Mailinglist-bis:=20
a) It needs more work on it=20
b) Randy will push it with the collaboration of others=20

EAI-mailto:=20
a) It needs more work on it=20
b) Martin will push it with the collaboration of others=20


other documents=20

draft: Advice for non-ASCII & ASCII addresses=20
a) Shawn, and Jiankang etc will do it=20
b) it will be submitted to ietf in Dec.=20

draft: Advice for EAI deployment=20
a) Jiankang, and Shawn etc will do it=20
b) it will be submitted to ietf in Dec.=20


reminder:=20
Anyone who raised his hand and committed to review docs=20
should do so as promised.=20
----------------------------------------
------=_NextPart_000_0262_01CB8C98.DECBFFE0--


From alexey.melnikov@isode.com  Fri Nov 26 11:07:06 2010
Return-Path: <alexey.melnikov@isode.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 E223928C0FA for <ima@core3.amsl.com>; Fri, 26 Nov 2010 11:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, 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 nXQ9o7Prqpd9 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 11:07:05 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id D555728C0F7 for <ima@ietf.org>; Fri, 26 Nov 2010 11:07:02 -0800 (PST)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPAFkQAEeSqa@rufus.isode.com>; Fri, 26 Nov 2010 19:08:04 +0000
Message-ID: <4CF00575.3010400@isode.com>
Date: Fri, 26 Nov 2010 19:07:33 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] Errors in ABNF in draft-ietf-eai-rfc5335bis-03.txt and draft-ietf-eai-rfc5336bis-04.txt
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, 26 Nov 2010 19:07:07 -0000

In draft-ietf-eai-rfc5335bis-03.txt:

>    uAtom          = FWS] 1*uAtext [CFWS]

That is missing an opening "[". In RFC 5336 it was "[CFWS]". So I think 
the correct version is:

   uAtom          = [CFWS] 1*uAtext [CFWS]

>    uDot-Atom      = CFWS] uDot-Atom-text [CFWS]

Also missing an opening "[". So I think it should be:

   uDot-Atom      = [CFWS] uDot-Atom-text [CFWS]

>    angle-addr   =/ [CFWS] "<" uAddr-Spec">" [CFWS] / obs-angle-addr
>                    ; Replace angle-addr in Section 3.4 of RFC 5322

An extra space is needed before ">", otherwise this is not a valid ABNF.


 >   qcontent       =  uQcontent

Should this be =/ ?


 >   mailbox      =  name-addr / addr-spec / uAddr-Spec
 >                   ; Replace mailbox in Section 3.4.1 of RFC 5322

Wrong section reference, should be section 3.4

 >   uLocal-Part  =  uDot-String / uQuoted-String
 >                   ; Replace Local-Part in Section 3.4.1 of RFC 5322

What happened to obs-local-part from "local-part" definition?

 >   item-value      =/      uAddr-Spec

Where "item-value" is originally defined? Why is this extending it?



utext is defined twice in the document:

   utext   =/  UTF8-xtra-char

and then as:

   uText          = %d1-9 /    ; all UTF-8 characters except
                    %d11-12 /  ; US-ASCII NUL, CR, and LF
                    %d14-127 /
                    UTF8-xtra-char

I suggest deleting the first definition.

-----------------------------------
In draft-ietf-eai-rfc5336bis-04.txt:

> 3.3.  Extended Mailbox Address Syntax

 [...]

>             uMailbox = uLocal-part "@" uDomain
>               ; uLocal-part and uDomain defined
>               ; in RFC 5335bis, Section 4.

The problem with referencing definitions in RFC 5335bis is that they 
allow for

   uDomain      =  (sub-udomain 1*("." sub-uDomain)) /
                   dot-atom / domain-literal / obs-domain
                   ; Replace Domain in Section 4.1.2 of  RFC 5321

and definition of dot-atom, domain-literal and obs-domain from RFC 5322 
are going to be problematic in SMTP:

   domain-literal  =   [CFWS] "[" *([FWS] dtext) [FWS] "]" [CFWS]

   obs-domain      =   atom *("." atom)

   atom            =   [CFWS] 1*atext [CFWS]

   dot-atom-text   =   1*atext *("." 1*atext)

   dot-atom        =   [CFWS] dot-atom-text [CFWS]

because of CFWS.

Similar problems with uLocal-Part.

So, RFC5336bis needs to define its own uDomain and uLocal-Part.

> 3.6.3.  Trace Information

 [...]

>       uReturn-path-line = "Return-Path:" FWS uReverse-path <CRLF>
>           ; Replaces Return-path-line in Section 4.4 of RFC 5321
>           ; uReverse-path is defined in Section 4 of RFC5335bis

uReverse-path is not defined in RFC5335bis. So either 
draft-ietf-eai-rfc5335bis needs to be updated to define it, or this 
comment needs to be removed and a definition added, for example:

   uReverse-path   = uPath / "<>"
      ; Replaced Reverse-path in Section 4.2.1 of RFC 5321

>       uTime-stamp-line = "Received:" FWS uStamp <CRLF>
>           ; Replaces Time-stamp-line in Section 4.4 of RFC 5321
>
>       uStamp = From-domain By-domain uOpt-info ";"  FWS date-time
>           ; Replaces Stamp in Section 4.4 of RFC 5321
>
>       uOpt-info = [Via] [With] [ID] [uFor]
>           ; Replaces Opt-info in Section 4.4 of RFC 5321
>           ; The protocol value for With will allow a UTF8SMTPbis value

RFC 5321 defines:
   Opt-info       = [Via] [With] [ID] [For]
                  [Additional-Registered-Clauses]

So it looks like "[Additional-Registered-Clauses]" was lost from the 
uOpt-info.

>       uFor = "FOR" ( FWS (uPath / uMailbox) ) CFWS
>           ; Replaces For in Section 4.4 of RFC 5321
>           ; uMailbox is defined in section 3.3 of this document
>       uPath = "<" [ A-d-l ":" ] uMailbox ">"
>           ; Replace Path in RFC 5321, section 4.1.2
>           ; A-d-l is defined in RFC 5321, section 4.1.2
>           ; uMailbox is defined in section 3.3 of this document


Considering bugs I found, can somebody else sanity check the ABNF in 
these 2 documents?

Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From alexey.melnikov@isode.com  Fri Nov 26 14:10:49 2010
Return-Path: <alexey.melnikov@isode.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 BCBCB28C0F1 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 14:10:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, 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 JAzoXLJl1-dv for <ima@core3.amsl.com>; Fri, 26 Nov 2010 14:10:47 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 6FE7828C10D for <ima@ietf.org>; Fri, 26 Nov 2010 14:10:47 -0800 (PST)
Received: from [172.16.2.129] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPAwowAEeQ-M@rufus.isode.com>; Fri, 26 Nov 2010 22:11:49 +0000
Message-ID: <4CF0307D.9090900@isode.com>
Date: Fri, 26 Nov 2010 22:11:09 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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, 26 Nov 2010 22:10:49 -0000

Hi WG,
Below is my AD review of the document (with some questions to the WG):

(In addition to the ABNF issues I raised in a separate email.)

2.  Overview of Operation

   This specification describes an optional extension to the email
   transport mechanism that permits non-ASCII [ASCII] characters in both
   the envelope and header fields of messages, which are encoded with
   UTF-8 [RFC3629] characters.  The extension is identified with the
   token "UTF8SMTPbis".  In order to provide information that may be
   needed in downgrading, an optional alternate ASCII address may be
   needed if an SMTP client attempts to transfer an internationalized
   message and encounters a server that does not support this extension.

I think the last sentence no longer applies and need to be deleted.

In 3.1:

  9.  The UTF8SMTPbis extension is valid on the submission port
       [RFC4409].

I think this sentence should also say that this extension can be used 
with LMTP.
This will make the reference to RFC 2033 Normative.


In 3.2:

   A UTF8SMTPbis aware MUA/MSA sending to a legacy SMTP server [RFC5321]
   and [RFC5322] MAY convert the ASCII@non-ASCII

Native speakers: should the "the" be replaced with "a" here?

   address into the format
   of ASCII@A-label [RFC5890] if the email address is in the format of
   ASCII@non-ASCII.



3.4.  UTF8 addresses and Response Codes

   An "internationalized message" as defined in the appendix of this
   specification

I think the part that reads "as defined in the appendix of this 
specification"
needs to be removed, because the definition is already in another document
and this document no longer has any appendix.

   MUST NOT be sent to an SMTP server that does not
   support UTF8SMTPbis.  Such a message should be rejected by a server
   if it lacks the support of UTF8SMTPbis.

3.6.2.  Mail eXchangers

   Organizations often authorize multiple servers to accept mail
   addressed to them.  For example, the organization may itself operate
   more than one server, and may also or instead have an agreement with
   other organizations to accept mail as a backup.  Authorized servers
   are generally listed in MX records as described in RFC 5321.  When
   more than one server accepts mail for the domain-part of a mailbox,
   it is strongly advised that either all or none of them support the
   UTF8SMTPbis extension.  Otherwise, surprising downgrades can happen
   during temporary failures, which users might perceive as a serious
   reliability issue.

The last sentence: I think this needs to be reworded or deleted,
as "surprising downgrades" are no longer an issue.


3.6.4.2.  VRFY and EXPN Commands and the UTF8REPLY Parameter

   VERIFY (VRFY) and EXPAND (EXPN) command syntaxes are changed to:

       "VRFY" SP ( uLocal-part / uMailbox ) [ SP "UTF8REPLY" ] CRLF
              ; uLocal-part and uMailbox are defined in
              ; Section 3.3 of this document.

Section 3.3 no longer contains definitions of uLocal-part and uMailbox.
See my separate email message about ABNF errors in rfc5335bis/rfc5336bis.

Also note that RFC 5321 is using:

      vrfy = "VRFY" SP String CRLF

So I suggest using the same format (with "vrfy =") for consistency.


       "EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF8REPLY" ] CRLF
              ; uLocal-part and uMailbox are defined in
              ; Section 3.3 of this document.

As above.
Similarly, I suggest using:

      expn = "EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF8REPLY" ] CRLF


   If the SMTP reply requires UTF-8 strings, but UTF-8 is not allowed in
   the reply, and the server supports enhanced mail system status codes
   [RFC3463], the enhanced response code is either "X.6.8" or "X.6.10"

Can somebody remind me why we have 2 different Enhanced Status Code which
mean the same thing?

   [RFC5248], meaning "A reply containing a UTF-8 string is required to
   show the mailbox name, but that form of response is not permitted by
   the client".


4.  IANA Considerations

   +---------------+-----------------------------+---------------------+
   | WITH protocol | Description                 | Reference           |
   | types         |                             |                     |
   +---------------+-----------------------------+---------------------+
   | UTF8SMTPbis   | UTF8SMTPbis with Service    | [RFCXXXX]           |
   |               | Extensions                  |                     |
   | UTF8SMTPbisA  | UTF8SMTPbis with SMTP AUTH  | [RFC4954] [RFCXXXX] |
   | UTF8SMTPbisS  | UTF8SMTPbis with STARTTLS   | [RFC3207] [RFCXXXX] |
   | UTF8SMTPbisSA | UTF8SMTPbis with both       | [RFC3207] [RFC4954] |
   |               | STARTTLS and SMTP AUTH      | [RFCXXXX]           |
   +---------------+-----------------------------+---------------------+

Do we really need to change the WITH protocol types?


   [RFC2033]  Myers, J., "Local Mail Transfer Protocol", RFC 2033,
              October 1996.

Make this reference Normative as per my earlier comment.

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From yaojk@cnnic.cn  Fri Nov 26 16:39:36 2010
Return-Path: <yaojk@cnnic.cn>
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 B31B828C122 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 16:39:36 -0800 (PST)
X-Quarantine-ID: <0XJ1DgSQKMrr>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -98.864
X-Spam-Level: 
X-Spam-Status: No, score=-98.864 tagged_above=-999 required=5 tests=[AWL=1.179, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 0XJ1DgSQKMrr for <ima@core3.amsl.com>; Fri, 26 Nov 2010 16:39:34 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 4A1043A6A9B for <ima@ietf.org>; Fri, 26 Nov 2010 16:39:31 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 08:40:34 +0800
Message-ID: <490818434.22066@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 08:40:34 +0800
Message-ID: <50D6E533963240B987770FACBF035644@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <490809525.17302@cnnic.cn>
Date: Sat, 27 Nov 2010 08:40:13 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 00:39:37 -0000

dGhhbmtzLA0KDQp3ZSB3aWxsIHVwZGF0ZSB0aGUgZHJhZnQgc29vbi4NCg0KSmlhbmthbmcgWWFv
DQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiQWxleGV5IE1lbG5pa292
IiA8YWxleGV5Lm1lbG5pa292QGlzb2RlLmNvbT4NClRvOiAiRUFJIFdHIiA8aW1hQGlldGYub3Jn
Pg0KU2VudDogU2F0dXJkYXksIE5vdmVtYmVyIDI3LCAyMDEwIDY6MTEgQU0NClN1YmplY3Q6IFtF
QUldIEFEIHJldmlldyBvZiBkcmFmdC1pZXRmLWVhaS1yZmM1MzM2YmlzLTA0LnR4dA0KDQoNCj4g
SGkgV0csDQo+IEJlbG93IGlzIG15IEFEIHJldmlldyBvZiB0aGUgZG9jdW1lbnQgKHdpdGggc29t
ZSBxdWVzdGlvbnMgdG8gdGhlIFdHKToNCj4gDQo+IChJbiBhZGRpdGlvbiB0byB0aGUgQUJORiBp
c3N1ZXMgSSByYWlzZWQgaW4gYSBzZXBhcmF0ZSBlbWFpbC4pDQo+IA0KPiAyLiAgT3ZlcnZpZXcg
b2YgT3BlcmF0aW9uDQo+IA0KPiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBkZXNjcmliZXMgYW4gb3B0
aW9uYWwgZXh0ZW5zaW9uIHRvIHRoZSBlbWFpbA0KPiAgIHRyYW5zcG9ydCBtZWNoYW5pc20gdGhh
dCBwZXJtaXRzIG5vbi1BU0NJSSBbQVNDSUldIGNoYXJhY3RlcnMgaW4gYm90aA0KPiAgIHRoZSBl
bnZlbG9wZSBhbmQgaGVhZGVyIGZpZWxkcyBvZiBtZXNzYWdlcywgd2hpY2ggYXJlIGVuY29kZWQg
d2l0aA0KPiAgIFVURi04IFtSRkMzNjI5XSBjaGFyYWN0ZXJzLiAgVGhlIGV4dGVuc2lvbiBpcyBp
ZGVudGlmaWVkIHdpdGggdGhlDQo+ICAgdG9rZW4gIlVURjhTTVRQYmlzIi4gIEluIG9yZGVyIHRv
IHByb3ZpZGUgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUNCj4gICBuZWVkZWQgaW4gZG93bmdyYWRp
bmcsIGFuIG9wdGlvbmFsIGFsdGVybmF0ZSBBU0NJSSBhZGRyZXNzIG1heSBiZQ0KPiAgIG5lZWRl
ZCBpZiBhbiBTTVRQIGNsaWVudCBhdHRlbXB0cyB0byB0cmFuc2ZlciBhbiBpbnRlcm5hdGlvbmFs
aXplZA0KPiAgIG1lc3NhZ2UgYW5kIGVuY291bnRlcnMgYSBzZXJ2ZXIgdGhhdCBkb2VzIG5vdCBz
dXBwb3J0IHRoaXMgZXh0ZW5zaW9uLg0KPiANCj4gSSB0aGluayB0aGUgbGFzdCBzZW50ZW5jZSBu
byBsb25nZXIgYXBwbGllcyBhbmQgbmVlZCB0byBiZSBkZWxldGVkLg0KPiANCj4gSW4gMy4xOg0K
PiANCj4gIDkuICBUaGUgVVRGOFNNVFBiaXMgZXh0ZW5zaW9uIGlzIHZhbGlkIG9uIHRoZSBzdWJt
aXNzaW9uIHBvcnQNCj4gICAgICAgW1JGQzQ0MDldLg0KPiANCj4gSSB0aGluayB0aGlzIHNlbnRl
bmNlIHNob3VsZCBhbHNvIHNheSB0aGF0IHRoaXMgZXh0ZW5zaW9uIGNhbiBiZSB1c2VkIA0KPiB3
aXRoIExNVFAuDQo+IFRoaXMgd2lsbCBtYWtlIHRoZSByZWZlcmVuY2UgdG8gUkZDIDIwMzMgTm9y
bWF0aXZlLg0KPiANCj4gDQo+IEluIDMuMjoNCj4gDQo+ICAgQSBVVEY4U01UUGJpcyBhd2FyZSBN
VUEvTVNBIHNlbmRpbmcgdG8gYSBsZWdhY3kgU01UUCBzZXJ2ZXIgW1JGQzUzMjFdDQo+ICAgYW5k
IFtSRkM1MzIyXSBNQVkgY29udmVydCB0aGUgQVNDSUlAbm9uLUFTQ0lJDQo+IA0KPiBOYXRpdmUg
c3BlYWtlcnM6IHNob3VsZCB0aGUgInRoZSIgYmUgcmVwbGFjZWQgd2l0aCAiYSIgaGVyZT8NCj4g
DQo+ICAgYWRkcmVzcyBpbnRvIHRoZSBmb3JtYXQNCj4gICBvZiBBU0NJSUBBLWxhYmVsIFtSRkM1
ODkwXSBpZiB0aGUgZW1haWwgYWRkcmVzcyBpcyBpbiB0aGUgZm9ybWF0IG9mDQo+ICAgQVNDSUlA
bm9uLUFTQ0lJLg0KPiANCj4gDQo+IA0KPiAzLjQuICBVVEY4IGFkZHJlc3NlcyBhbmQgUmVzcG9u
c2UgQ29kZXMNCj4gDQo+ICAgQW4gImludGVybmF0aW9uYWxpemVkIG1lc3NhZ2UiIGFzIGRlZmlu
ZWQgaW4gdGhlIGFwcGVuZGl4IG9mIHRoaXMNCj4gICBzcGVjaWZpY2F0aW9uDQo+IA0KPiBJIHRo
aW5rIHRoZSBwYXJ0IHRoYXQgcmVhZHMgImFzIGRlZmluZWQgaW4gdGhlIGFwcGVuZGl4IG9mIHRo
aXMgDQo+IHNwZWNpZmljYXRpb24iDQo+IG5lZWRzIHRvIGJlIHJlbW92ZWQsIGJlY2F1c2UgdGhl
IGRlZmluaXRpb24gaXMgYWxyZWFkeSBpbiBhbm90aGVyIGRvY3VtZW50DQo+IGFuZCB0aGlzIGRv
Y3VtZW50IG5vIGxvbmdlciBoYXMgYW55IGFwcGVuZGl4Lg0KPiANCj4gICBNVVNUIE5PVCBiZSBz
ZW50IHRvIGFuIFNNVFAgc2VydmVyIHRoYXQgZG9lcyBub3QNCj4gICBzdXBwb3J0IFVURjhTTVRQ
YmlzLiAgU3VjaCBhIG1lc3NhZ2Ugc2hvdWxkIGJlIHJlamVjdGVkIGJ5IGEgc2VydmVyDQo+ICAg
aWYgaXQgbGFja3MgdGhlIHN1cHBvcnQgb2YgVVRGOFNNVFBiaXMuDQo+IA0KPiAzLjYuMi4gIE1h
aWwgZVhjaGFuZ2Vycw0KPiANCj4gICBPcmdhbml6YXRpb25zIG9mdGVuIGF1dGhvcml6ZSBtdWx0
aXBsZSBzZXJ2ZXJzIHRvIGFjY2VwdCBtYWlsDQo+ICAgYWRkcmVzc2VkIHRvIHRoZW0uICBGb3Ig
ZXhhbXBsZSwgdGhlIG9yZ2FuaXphdGlvbiBtYXkgaXRzZWxmIG9wZXJhdGUNCj4gICBtb3JlIHRo
YW4gb25lIHNlcnZlciwgYW5kIG1heSBhbHNvIG9yIGluc3RlYWQgaGF2ZSBhbiBhZ3JlZW1lbnQg
d2l0aA0KPiAgIG90aGVyIG9yZ2FuaXphdGlvbnMgdG8gYWNjZXB0IG1haWwgYXMgYSBiYWNrdXAu
ICBBdXRob3JpemVkIHNlcnZlcnMNCj4gICBhcmUgZ2VuZXJhbGx5IGxpc3RlZCBpbiBNWCByZWNv
cmRzIGFzIGRlc2NyaWJlZCBpbiBSRkMgNTMyMS4gIFdoZW4NCj4gICBtb3JlIHRoYW4gb25lIHNl
cnZlciBhY2NlcHRzIG1haWwgZm9yIHRoZSBkb21haW4tcGFydCBvZiBhIG1haWxib3gsDQo+ICAg
aXQgaXMgc3Ryb25nbHkgYWR2aXNlZCB0aGF0IGVpdGhlciBhbGwgb3Igbm9uZSBvZiB0aGVtIHN1
cHBvcnQgdGhlDQo+ICAgVVRGOFNNVFBiaXMgZXh0ZW5zaW9uLiAgT3RoZXJ3aXNlLCBzdXJwcmlz
aW5nIGRvd25ncmFkZXMgY2FuIGhhcHBlbg0KPiAgIGR1cmluZyB0ZW1wb3JhcnkgZmFpbHVyZXMs
IHdoaWNoIHVzZXJzIG1pZ2h0IHBlcmNlaXZlIGFzIGEgc2VyaW91cw0KPiAgIHJlbGlhYmlsaXR5
IGlzc3VlLg0KPiANCj4gVGhlIGxhc3Qgc2VudGVuY2U6IEkgdGhpbmsgdGhpcyBuZWVkcyB0byBi
ZSByZXdvcmRlZCBvciBkZWxldGVkLA0KPiBhcyAic3VycHJpc2luZyBkb3duZ3JhZGVzIiBhcmUg
bm8gbG9uZ2VyIGFuIGlzc3VlLg0KPiANCj4gDQo+IDMuNi40LjIuICBWUkZZIGFuZCBFWFBOIENv
bW1hbmRzIGFuZCB0aGUgVVRGOFJFUExZIFBhcmFtZXRlcg0KPiANCj4gICBWRVJJRlkgKFZSRlkp
IGFuZCBFWFBBTkQgKEVYUE4pIGNvbW1hbmQgc3ludGF4ZXMgYXJlIGNoYW5nZWQgdG86DQo+IA0K
PiAgICAgICAiVlJGWSIgU1AgKCB1TG9jYWwtcGFydCAvIHVNYWlsYm94ICkgWyBTUCAiVVRGOFJF
UExZIiBdIENSTEYNCj4gICAgICAgICAgICAgIDsgdUxvY2FsLXBhcnQgYW5kIHVNYWlsYm94IGFy
ZSBkZWZpbmVkIGluDQo+ICAgICAgICAgICAgICA7IFNlY3Rpb24gMy4zIG9mIHRoaXMgZG9jdW1l
bnQuDQo+IA0KPiBTZWN0aW9uIDMuMyBubyBsb25nZXIgY29udGFpbnMgZGVmaW5pdGlvbnMgb2Yg
dUxvY2FsLXBhcnQgYW5kIHVNYWlsYm94Lg0KPiBTZWUgbXkgc2VwYXJhdGUgZW1haWwgbWVzc2Fn
ZSBhYm91dCBBQk5GIGVycm9ycyBpbiByZmM1MzM1YmlzL3JmYzUzMzZiaXMuDQo+IA0KPiBBbHNv
IG5vdGUgdGhhdCBSRkMgNTMyMSBpcyB1c2luZzoNCj4gDQo+ICAgICAgdnJmeSA9ICJWUkZZIiBT
UCBTdHJpbmcgQ1JMRg0KPiANCj4gU28gSSBzdWdnZXN0IHVzaW5nIHRoZSBzYW1lIGZvcm1hdCAo
d2l0aCAidnJmeSA9IikgZm9yIGNvbnNpc3RlbmN5Lg0KPiANCj4gDQo+ICAgICAgICJFWFBOIiBT
UCAoIHVMb2NhbC1wYXJ0IC8gdU1haWxib3ggKSBbIFNQICJVVEY4UkVQTFkiIF0gQ1JMRg0KPiAg
ICAgICAgICAgICAgOyB1TG9jYWwtcGFydCBhbmQgdU1haWxib3ggYXJlIGRlZmluZWQgaW4NCj4g
ICAgICAgICAgICAgIDsgU2VjdGlvbiAzLjMgb2YgdGhpcyBkb2N1bWVudC4NCj4gDQo+IEFzIGFi
b3ZlLg0KPiBTaW1pbGFybHksIEkgc3VnZ2VzdCB1c2luZzoNCj4gDQo+ICAgICAgZXhwbiA9ICJF
WFBOIiBTUCAoIHVMb2NhbC1wYXJ0IC8gdU1haWxib3ggKSBbIFNQICJVVEY4UkVQTFkiIF0gQ1JM
Rg0KPiANCj4gDQo+ICAgSWYgdGhlIFNNVFAgcmVwbHkgcmVxdWlyZXMgVVRGLTggc3RyaW5ncywg
YnV0IFVURi04IGlzIG5vdCBhbGxvd2VkIGluDQo+ICAgdGhlIHJlcGx5LCBhbmQgdGhlIHNlcnZl
ciBzdXBwb3J0cyBlbmhhbmNlZCBtYWlsIHN5c3RlbSBzdGF0dXMgY29kZXMNCj4gICBbUkZDMzQ2
M10sIHRoZSBlbmhhbmNlZCByZXNwb25zZSBjb2RlIGlzIGVpdGhlciAiWC42LjgiIG9yICJYLjYu
MTAiDQo+IA0KPiBDYW4gc29tZWJvZHkgcmVtaW5kIG1lIHdoeSB3ZSBoYXZlIDIgZGlmZmVyZW50
IEVuaGFuY2VkIFN0YXR1cyBDb2RlIHdoaWNoDQo+IG1lYW4gdGhlIHNhbWUgdGhpbmc/DQo+IA0K
PiAgIFtSRkM1MjQ4XSwgbWVhbmluZyAiQSByZXBseSBjb250YWluaW5nIGEgVVRGLTggc3RyaW5n
IGlzIHJlcXVpcmVkIHRvDQo+ICAgc2hvdyB0aGUgbWFpbGJveCBuYW1lLCBidXQgdGhhdCBmb3Jt
IG9mIHJlc3BvbnNlIGlzIG5vdCBwZXJtaXR0ZWQgYnkNCj4gICB0aGUgY2xpZW50Ii4NCj4gDQo+
IA0KPiA0LiAgSUFOQSBDb25zaWRlcmF0aW9ucw0KPiANCj4gICArLS0tLS0tLS0tLS0tLS0tKy0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCj4gICB8
IFdJVEggcHJvdG9jb2wgfCBEZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgfCBSZWZlcmVuY2Ug
ICAgICAgICAgIHwNCj4gICB8IHR5cGVzICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwNCj4gICArLS0tLS0tLS0tLS0tLS0tKy0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCj4gICB8IFVU
RjhTTVRQYmlzICAgfCBVVEY4U01UUGJpcyB3aXRoIFNlcnZpY2UgICAgfCBbUkZDWFhYWF0gICAg
ICAgICAgIHwNCj4gICB8ICAgICAgICAgICAgICAgfCBFeHRlbnNpb25zICAgICAgICAgICAgICAg
ICAgfCAgICAgICAgICAgICAgICAgICAgIHwNCj4gICB8IFVURjhTTVRQYmlzQSAgfCBVVEY4U01U
UGJpcyB3aXRoIFNNVFAgQVVUSCAgfCBbUkZDNDk1NF0gW1JGQ1hYWFhdIHwNCj4gICB8IFVURjhT
TVRQYmlzUyAgfCBVVEY4U01UUGJpcyB3aXRoIFNUQVJUVExTICAgfCBbUkZDMzIwN10gW1JGQ1hY
WFhdIHwNCj4gICB8IFVURjhTTVRQYmlzU0EgfCBVVEY4U01UUGJpcyB3aXRoIGJvdGggICAgICAg
fCBbUkZDMzIwN10gW1JGQzQ5NTRdIHwNCj4gICB8ICAgICAgICAgICAgICAgfCBTVEFSVFRMUyBh
bmQgU01UUCBBVVRIICAgICAgfCBbUkZDWFhYWF0gICAgICAgICAgIHwNCj4gICArLS0tLS0tLS0t
LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t
LSsNCj4gDQo+IERvIHdlIHJlYWxseSBuZWVkIHRvIGNoYW5nZSB0aGUgV0lUSCBwcm90b2NvbCB0
eXBlcz8NCj4gDQo+IA0KPiAgIFtSRkMyMDMzXSAgTXllcnMsIEouLCAiTG9jYWwgTWFpbCBUcmFu
c2ZlciBQcm90b2NvbCIsIFJGQyAyMDMzLA0KPiAgICAgICAgICAgICAgT2N0b2JlciAxOTk2Lg0K
PiANCj4gTWFrZSB0aGlzIHJlZmVyZW5jZSBOb3JtYXRpdmUgYXMgcGVyIG15IGVhcmxpZXIgY29t
bWVudC4NCj4gDQo+IC0tIA0KPiBJRVRGIEFwcGxpY2F0aW9uIEFyZWEgRGlyZWN0b3IsIDxodHRw
Oi8vd3d3LmlldGYub3JnL2llc2cvbWVtYmVycy5odG1sPg0KPiBJbnRlcm5ldCBNZXNzYWdpbmcg
VGVhbSBMZWFkLCA8aHR0cDovL3d3dy5pc29kZS5jb20+DQo+IEpJRDogc2FtZSBhcyBteSBlbWFp
bCBhZGRyZXNzDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPiBJTUEgbWFpbGluZyBsaXN0DQo+IElNQUBpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ltYQ==


From yaojk@cnnic.cn  Fri Nov 26 17:12:37 2010
Return-Path: <yaojk@cnnic.cn>
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 6D32228C0F9 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 17:12:37 -0800 (PST)
X-Quarantine-ID: <U9qN4kiDWLYg>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -97.952
X-Spam-Level: 
X-Spam-Status: No, score=-97.952 tagged_above=-999 required=5 tests=[AWL=-0.323, BAYES_40=-0.185, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 U9qN4kiDWLYg for <ima@core3.amsl.com>; Fri, 26 Nov 2010 17:12:36 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id D35B73A6A79 for <ima@ietf.org>; Fri, 26 Nov 2010 17:12:33 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 09:13:33 +0800
Message-ID: <490820413.31367@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 09:13:33 +0800
Message-ID: <717365DC5FAB41058E7B1D342352F462@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <490809525.17302@cnnic.cn>
Date: Sat, 27 Nov 2010 09:13:32 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] response code Re: AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 01:12:37 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsZXhleSBNZWxuaWtvdiIg
PGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20+DQpUbzogIkVBSSBXRyIgPGltYUBpZXRmLm9yZz4N
ClNlbnQ6IFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCA2OjExIEFNDQpTdWJqZWN0OiBbRUFJ
XSBBRCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1lYWktcmZjNTMzNmJpcy0wNC50eHQNCg0KDQouLi4u
Lg0KPiANCj4gDQo+ICAgSWYgdGhlIFNNVFAgcmVwbHkgcmVxdWlyZXMgVVRGLTggc3RyaW5ncywg
YnV0IFVURi04IGlzIG5vdCBhbGxvd2VkIGluDQo+ICAgdGhlIHJlcGx5LCBhbmQgdGhlIHNlcnZl
ciBzdXBwb3J0cyBlbmhhbmNlZCBtYWlsIHN5c3RlbSBzdGF0dXMgY29kZXMNCj4gICBbUkZDMzQ2
M10sIHRoZSBlbmhhbmNlZCByZXNwb25zZSBjb2RlIGlzIGVpdGhlciAiWC42LjgiIG9yICJYLjYu
MTAiDQo+IA0KPiBDYW4gc29tZWJvZHkgcmVtaW5kIG1lIHdoeSB3ZSBoYXZlIDIgZGlmZmVyZW50
IEVuaGFuY2VkIFN0YXR1cyBDb2RlIHdoaWNoDQo+IG1lYW4gdGhlIHNhbWUgdGhpbmc/DQo+IA0K
DQpJIHRoaW5rIHRoYXQgaXQgaXMgZHVlIHRvIHRoZSBBc3NvY2lhdGVkIGJhc2ljIHN0YXR1cyBj
b2RlOg0KDQogICAgICBDb2RlOiAgICAgICAgICAgICAgIFguNi44DQogICAgICBTYW1wbGUgVGV4
dDogICAgICAgIFVURi04IHN0cmluZyByZXBseSBpcyByZXF1aXJlZCwNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgYnV0IG5vdCBwZXJtaXR0ZWQgYnkgdGhlIGNsaWVudA0KICAgICAgQXNzb2Np
YXRlZCBiYXNpYyBzdGF0dXMgY29kZTogIDU1MywgNTUwDQoNCg0KICAgICAgQ29kZTogICAgICAg
ICAgICAgICBYLjYuMTANCiAgICAgIFNhbXBsZSBUZXh0OiAgICAgICAgVVRGLTggc3RyaW5nIHJl
cGx5IGlzIHJlcXVpcmVkLA0KICAgICAgICAgICAgICAgICAgICAgICAgICBidXQgbm90IHBlcm1p
dHRlZCBieSB0aGUgY2xpZW50DQogICAgICBBc3NvY2lhdGVkIGJhc2ljIHN0YXR1cyBjb2RlOiAg
MjUyDQoNCg0KSmlhbmthbmcgWWFvDQoNCg0KDQoNCg0KPg0KPiAgIFtSRkM1MjQ4XSwgbWVhbmlu
ZyAiQSByZXBseSBjb250YWluaW5nIGEgVVRGLTggc3RyaW5nIGlzIHJlcXVpcmVkIHRvDQo+ICAg
c2hvdyB0aGUgbWFpbGJveCBuYW1lLCBidXQgdGhhdCBmb3JtIG9mIHJlc3BvbnNlIGlzIG5vdCBw
ZXJtaXR0ZWQgYnkNCj4gICB0aGUgY2xpZW50Ii4NCj4gDQo+IA0K


From klensin@jck.com  Fri Nov 26 19:58:17 2010
Return-Path: <klensin@jck.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 41F9228C136 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 19:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 q0kIybRz+rme for <ima@core3.amsl.com>; Fri, 26 Nov 2010 19:58:16 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 4EEA728C11B for <ima@ietf.org>; Fri, 26 Nov 2010 19:58:16 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMBwQ-000KeC-1X; Fri, 26 Nov 2010 22:59:14 -0500
Date: Fri, 26 Nov 2010 22:59:11 -0500
From: John C Klensin <klensin@jck.com>
To: Jiankang YAO <yaojk@cnnic.cn>, Alexey Melnikov <alexey.melnikov@isode.com>, EAI WG <ima@ietf.org>
Message-ID: <CFD859C14FDD76892CDFE609@[192.168.1.128]>
In-Reply-To: <490818434.22066@cnnic.cn>, <50D6E533963240B987770FACBF035644@LENOVO47E041CF>
References: <490809525.17302@cnnic.cn> <490818434.22066@cnnic.cn>, <50D6E533963240B987770FACBF035644@LENOVO47E041CF>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 03:58:17 -0000

--On Saturday, November 27, 2010 8:40 AM +0800 Jiankang YAO
<yaojk@cnnic.cn> wrote:

> thanks,
> 
> we will update the draft soon.

When you do so, please remove the periods after your personal
name and that of Mao Wei in the top header author lines.

I will do a detailed review over the weekend and get back to
you; you might want to hold off posting a new draft until that
is in your hands.

   john




From yaojk@cnnic.cn  Fri Nov 26 21:26:59 2010
Return-Path: <yaojk@cnnic.cn>
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 EADAF3A69D3 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 21:26:58 -0800 (PST)
X-Quarantine-ID: <6j28tvHn64Gt>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -99.094
X-Spam-Level: 
X-Spam-Status: No, score=-99.094 tagged_above=-999 required=5 tests=[AWL=0.949, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 6j28tvHn64Gt for <ima@core3.amsl.com>; Fri, 26 Nov 2010 21:26:58 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 667C528C136 for <ima@ietf.org>; Fri, 26 Nov 2010 21:26:55 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 13:28:00 +0800
Message-ID: <490835680.07542@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 13:28:00 +0800
Message-ID: <D3C08900A5CB4F78911D4EC662DFBA4B@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <490798500.32210@cnnic.cn>
Date: Sat, 27 Nov 2010 13:28:01 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] udomain Re: Errors in ABNF in draft-ietf-eai-rfc5335bis-03.txt and draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 05:26:59 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsZXhleSBNZWxuaWtvdiIg
PGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20+DQpUbzogIkVBSSBXRyIgPGltYUBpZXRmLm9yZz4N
ClNlbnQ6IFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCAzOjA3IEFNDQpTdWJqZWN0OiBbRUFJ
XSBFcnJvcnMgaW4gQUJORiBpbiBkcmFmdC1pZXRmLWVhaS1yZmM1MzM1YmlzLTAzLnR4dCBhbmQg
ZHJhZnQtaWV0Zi1lYWktcmZjNTMzNmJpcy0wNC50eHQNCg0KDQouLi4uDQo+IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IEluIGRyYWZ0LWlldGYtZWFpLXJmYzUzMzZiaXMt
MDQudHh0Og0KPiANCj4+IDMuMy4gIEV4dGVuZGVkIE1haWxib3ggQWRkcmVzcyBTeW50YXgNCj4g
DQo+IFsuLi5dDQo+IA0KPj4gICAgICAgICAgICAgdU1haWxib3ggPSB1TG9jYWwtcGFydCAiQCIg
dURvbWFpbg0KPj4gICAgICAgICAgICAgICA7IHVMb2NhbC1wYXJ0IGFuZCB1RG9tYWluIGRlZmlu
ZWQNCj4+ICAgICAgICAgICAgICAgOyBpbiBSRkMgNTMzNWJpcywgU2VjdGlvbiA0Lg0KPiANCj4g
VGhlIHByb2JsZW0gd2l0aCByZWZlcmVuY2luZyBkZWZpbml0aW9ucyBpbiBSRkMgNTMzNWJpcyBp
cyB0aGF0IHRoZXkgDQo+IGFsbG93IGZvcg0KPiANCj4gICB1RG9tYWluICAgICAgPSAgKHN1Yi11
ZG9tYWluIDEqKCIuIiBzdWItdURvbWFpbikpIC8NCj4gICAgICAgICAgICAgICAgICAgZG90LWF0
b20gLyBkb21haW4tbGl0ZXJhbCAvIG9icy1kb21haW4NCj4gICAgICAgICAgICAgICAgICAgOyBS
ZXBsYWNlIERvbWFpbiBpbiBTZWN0aW9uIDQuMS4yIG9mICBSRkMgNTMyMQ0KPiANCj4gYW5kIGRl
ZmluaXRpb24gb2YgZG90LWF0b20sIGRvbWFpbi1saXRlcmFsIGFuZCBvYnMtZG9tYWluIGZyb20g
UkZDIDUzMjIgDQo+IGFyZSBnb2luZyB0byBiZSBwcm9ibGVtYXRpYyBpbiBTTVRQOg0KPiANCj4g
ICBkb21haW4tbGl0ZXJhbCAgPSAgIFtDRldTXSAiWyIgKihbRldTXSBkdGV4dCkgW0ZXU10gIl0i
IFtDRldTXQ0KPiANCj4gICBvYnMtZG9tYWluICAgICAgPSAgIGF0b20gKigiLiIgYXRvbSkNCj4g
DQo+ICAgYXRvbSAgICAgICAgICAgID0gICBbQ0ZXU10gMSphdGV4dCBbQ0ZXU10NCj4gDQo+ICAg
ZG90LWF0b20tdGV4dCAgID0gICAxKmF0ZXh0ICooIi4iIDEqYXRleHQpDQo+IA0KPiAgIGRvdC1h
dG9tICAgICAgICA9ICAgW0NGV1NdIGRvdC1hdG9tLXRleHQgW0NGV1NdDQo+IA0KPiBiZWNhdXNl
IG9mIENGV1MuDQo+IA0KPiBTaW1pbGFyIHByb2JsZW1zIHdpdGggdUxvY2FsLVBhcnQuDQo+IA0K
PiBTbywgUkZDNTMzNmJpcyBuZWVkcyB0byBkZWZpbmUgaXRzIG93biB1RG9tYWluIGFuZCB1TG9j
YWwtUGFydC4NCj4gDQoNCnRoYW5rIHlvdSBmb3IgY2F0Y2hpbmcgaXQuDQoNCmluIHRoZSBwcnZl
dmlvdXMgZGlzY3Vzc2lvbiBvbiB0aGUgbWFpbGluZyBsaXN0LCB3ZSB0cnkgdG8gYXZvaWQgdG8g
cmVwZWF0IHRoZSBkZWZpbml0aW9uIHRoYXQgcmVmZXJzIHRvIHRoZSBzYW1lIHRoaW5nIGluIHR3
byBkcmFmdHMuDQoNCml0IHNlZW1zIHRoYXQgdGhlIHVtYWlsYm94IGRlZmluaXRpb24gaGFzIHRv
IGdvIGJhY2sgdG8gdGhlIHByZXZpb3VzIHZlcnNpb24uDQoNCg0KSmlhbmthbmcgWWFvDQoNCg==


From yaojk@cnnic.cn  Fri Nov 26 21:38:27 2010
Return-Path: <yaojk@cnnic.cn>
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 7A10728C136 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 21:38:23 -0800 (PST)
X-Quarantine-ID: <guOqNC0jSDyD>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -98.046
X-Spam-Level: 
X-Spam-Status: No, score=-98.046 tagged_above=-999 required=5 tests=[AWL=-0.416, BAYES_40=-0.185, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 guOqNC0jSDyD for <ima@core3.amsl.com>; Fri, 26 Nov 2010 21:38:19 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id F2C3C28C149 for <ima@ietf.org>; Fri, 26 Nov 2010 21:38:15 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 13:39:19 +0800
Message-ID: <490836359.14086@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 13:39:19 +0800
Message-ID: <AA558B7AB7CC497889959C7C8E440B0D@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "John C Klensin" <klensin@jck.com>, "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <490809525.17302@cnnic.cn> <490818434.22066@cnnic.cn>, <50D6E533963240B987770FACBF035644@LENOVO47E041CF> <490830367.32486@cnnic.cn>
Date: Sat, 27 Nov 2010 13:39:12 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 05:38:30 -0000
X-List-Received-Date: Sat, 27 Nov 2010 05:38:30 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkpvaG4gQyBLbGVuc2luIiA8
a2xlbnNpbkBqY2suY29tPg0KVG86ICJKaWFua2FuZyBZQU8iIDx5YW9qa0Bjbm5pYy5jbj47ICJB
bGV4ZXkgTWVsbmlrb3YiIDxhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29tPjsgIkVBSSBXRyIgPGlt
YUBpZXRmLm9yZz4NClNlbnQ6IFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCAxMTo1OSBBTQ0K
U3ViamVjdDogUmU6IFtFQUldIEFEIHJldmlldyBvZiBkcmFmdC1pZXRmLWVhaS1yZmM1MzM2Ymlz
LTA0LnR4dA0KDQoNCj4gDQo+IA0KPiAtLU9uIFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCA4
OjQwIEFNICswODAwIEppYW5rYW5nIFlBTw0KPiA8eWFvamtAY25uaWMuY24+IHdyb3RlOg0KPiAN
Cj4+IHRoYW5rcywNCj4+IA0KPj4gd2Ugd2lsbCB1cGRhdGUgdGhlIGRyYWZ0IHNvb24uDQo+IA0K
PiBXaGVuIHlvdSBkbyBzbywgcGxlYXNlIHJlbW92ZSB0aGUgcGVyaW9kcyBhZnRlciB5b3VyIHBl
cnNvbmFsDQo+IG5hbWUgYW5kIHRoYXQgb2YgTWFvIFdlaSBpbiB0aGUgdG9wIGhlYWRlciBhdXRo
b3IgbGluZXMuDQo+IA0KPiBJIHdpbGwgZG8gYSBkZXRhaWxlZCByZXZpZXcgb3ZlciB0aGUgd2Vl
a2VuZCBhbmQgZ2V0IGJhY2sgdG8NCj4geW91OyB5b3UgbWlnaHQgd2FudCB0byBob2xkIG9mZiBw
b3N0aW5nIGEgbmV3IGRyYWZ0IHVudGlsIHRoYXQNCj4gaXMgaW4geW91ciBoYW5kcy4NCj4gDQoN
CnRoYW5rcywNCndhaXRpbmcgZm9yIHlvdXIga2luZCBjb21tZW50cy4NCg0KSmlhbmthbmcgWWFv
DQo+ICAgam9obg0KPiANCj4gDQo+


From jyee@ca.afilias.info  Fri Nov 26 23:41:07 2010
Return-Path: <jyee@ca.afilias.info>
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 B6A473A697E for <ima@core3.amsl.com>; Fri, 26 Nov 2010 23:41:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.406
X-Spam-Level: 
X-Spam-Status: No, score=-104.406 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4, 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 e3++Igrz2Nh1 for <ima@core3.amsl.com>; Fri, 26 Nov 2010 23:41:06 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id 6DEAE3A693A for <ima@ietf.org>; Fri, 26 Nov 2010 23:41:06 -0800 (PST)
From: Joseph Yee <jyee@ca.afilias.info>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 27 Nov 2010 02:42:10 -0500
Message-Id: <5A490690-6AB1-49AC-A0BF-CEA2A8BF2B81@ca.afilias.info>
To: EAI WG <ima@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Authenticated: True
Subject: [EAI] RFC5335bis edit
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: Sat, 27 Nov 2010 07:41:07 -0000

Hi, few more edits for RFC5335bis


1.  Editor note in second last paragraph of section 2 can be removed.  =
(Comment regards to RFC5721bis and RFC5738bis)

2. In ABNF of Section 4.4, Let-dig referenced from Section 4.1.2 instead =
of Section 4.1.3 of RFC 5321.

Thanks
Joseph=

From yaojk@cnnic.cn  Sat Nov 27 04:39:43 2010
Return-Path: <yaojk@cnnic.cn>
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 CE3E428C11D for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:39:43 -0800 (PST)
X-Quarantine-ID: <FBNSWjc07vnq>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -99.193
X-Spam-Level: 
X-Spam-Status: No, score=-99.193 tagged_above=-999 required=5 tests=[AWL=0.850, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 FBNSWjc07vnq for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:39:42 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 07E7028B56A for <ima@ietf.org>; Sat, 27 Nov 2010 04:39:39 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 20:40:44 +0800
Message-ID: <490861644.12446@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 20:40:44 +0800
Message-ID: <F87CC27809C94FAC8469EF5551C4A394@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <490809525.17302@cnnic.cn>
Date: Sat, 27 Nov 2010 20:40:33 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] WITH protocol types Re: AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 12:39:44 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsZXhleSBNZWxuaWtvdiIg
PGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20+DQpUbzogIkVBSSBXRyIgPGltYUBpZXRmLm9yZz4N
ClNlbnQ6IFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCA2OjExIEFNDQpTdWJqZWN0OiBbRUFJ
XSBBRCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1lYWktcmZjNTMzNmJpcy0wNC50eHQNCg0KDQouLi4u
DQo+IA0KPiA0LiAgSUFOQSBDb25zaWRlcmF0aW9ucw0KPiANCj4gICArLS0tLS0tLS0tLS0tLS0t
Ky0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCj4g
ICB8IFdJVEggcHJvdG9jb2wgfCBEZXNjcmlwdGlvbiAgICAgICAgICAgICAgICAgfCBSZWZlcmVu
Y2UgICAgICAgICAgIHwNCj4gICB8IHR5cGVzICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwNCj4gICArLS0tLS0tLS0tLS0tLS0tKy0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCj4gICB8
IFVURjhTTVRQYmlzICAgfCBVVEY4U01UUGJpcyB3aXRoIFNlcnZpY2UgICAgfCBbUkZDWFhYWF0g
ICAgICAgICAgIHwNCj4gICB8ICAgICAgICAgICAgICAgfCBFeHRlbnNpb25zICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAgICAgIHwNCj4gICB8IFVURjhTTVRQYmlzQSAgfCBVVEY4
U01UUGJpcyB3aXRoIFNNVFAgQVVUSCAgfCBbUkZDNDk1NF0gW1JGQ1hYWFhdIHwNCj4gICB8IFVU
RjhTTVRQYmlzUyAgfCBVVEY4U01UUGJpcyB3aXRoIFNUQVJUVExTICAgfCBbUkZDMzIwN10gW1JG
Q1hYWFhdIHwNCj4gICB8IFVURjhTTVRQYmlzU0EgfCBVVEY4U01UUGJpcyB3aXRoIGJvdGggICAg
ICAgfCBbUkZDMzIwN10gW1JGQzQ5NTRdIHwNCj4gICB8ICAgICAgICAgICAgICAgfCBTVEFSVFRM
UyBhbmQgU01UUCBBVVRIICAgICAgfCBbUkZDWFhYWF0gICAgICAgICAgIHwNCj4gICArLS0tLS0t
LS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0t
LS0tLSsNCj4gDQo+IERvIHdlIHJlYWxseSBuZWVkIHRvIGNoYW5nZSB0aGUgV0lUSCBwcm90b2Nv
bCB0eXBlcz8NCj4gDQoNClJGQzUzMzYgaGFzIHVwZGF0ZWQgdGhlIFdJVEggcHJvdG9jb2wgdHlw
ZXMuDQpzbyB0aGlzIHRpbWUsIHdlIG1pZ2h0IGhhdmUgdG8gdXBkYXRlIGl0IGFnYWluLg0KDQp0
aGUgdXBkYXRlcyBmb3IgV0lUSCBwcm90b2NvbCB0eXBlcyB3ZXJlIHN1Z2dlc3RlZCBieSBDaHJp
cyBOZXdtYW4gIGluIFJGQzUzMzYuDQoNCkkgdGhpbmsgdGhhdCBDaHJpcyBtYXkgaGF2ZSBhIGJl
dHRlciBhbnN3ZXIgdG8gdGhpcyBxdWVzdGlvbi4NCg0KDQpKaWFua2FuZyBZYW8NCg0KDQo+IA0K
PiAgIFtSRkMyMDMzXSAgTXllcnMsIEouLCAiTG9jYWwgTWFpbCBUcmFuc2ZlciBQcm90b2NvbCIs
IFJGQyAyMDMzLA0KPiAgICAgICAgICAgICAgT2N0b2JlciAxOTk2Lg0KPiANCj4gTWFrZSB0aGlz
IHJlZmVyZW5jZSBOb3JtYXRpdmUgYXMgcGVyIG15IGVhcmxpZXIgY29tbWVudC4NCj4gDQo+IC0t
IA0KPiBJRVRGIEFwcGxpY2F0aW9uIEFyZWEgRGlyZWN0b3IsIDxodHRwOi8vd3d3LmlldGYub3Jn
L2llc2cvbWVtYmVycy5odG1sPg0KPiBJbnRlcm5ldCBNZXNzYWdpbmcgVGVhbSBMZWFkLCA8aHR0
cDovL3d3dy5pc29kZS5jb20+DQo+IEpJRDogc2FtZSBhcyBteSBlbWFpbCBhZGRyZXNzDQo+IA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBJTUEg
bWFpbGluZyBsaXN0DQo+IElNQUBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2ltYQ==


From alexey.melnikov@isode.com  Sat Nov 27 04:51:16 2010
Return-Path: <alexey.melnikov@isode.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 ED63D28C151 for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, 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 VTMeiVzMp8Gt for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:51:15 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id ADBCD28C11D for <ima@ietf.org>; Sat, 27 Nov 2010 04:51:14 -0800 (PST)
Received: from [188.28.56.209] (188.28.56.209.threembb.co.uk [188.28.56.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPD-=gAEeZIl@rufus.isode.com>; Sat, 27 Nov 2010 12:52:18 +0000
Message-ID: <4CF0FED1.50501@isode.com>
Date: Sat, 27 Nov 2010 12:51:29 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Jiankang YAO <yaojk@cnnic.cn>, EAI WG <ima@ietf.org>
References: <490809525.17302@cnnic.cn> <490820413.31367@cnnic.cn>
In-Reply-To: <490820413.31367@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] response code Re: AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 12:51:17 -0000

Hi Jiankang,

Jiankang YAO wrote:

>----- Original Message ----- 
>From: "Alexey Melnikov" <alexey.melnikov@isode.com>
>To: "EAI WG" <ima@ietf.org>
>Sent: Saturday, November 27, 2010 6:11 AM
>Subject: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
>
>.....
>  
>
>>  If the SMTP reply requires UTF-8 strings, but UTF-8 is not allowed in
>>  the reply, and the server supports enhanced mail system status codes
>>  [RFC3463], the enhanced response code is either "X.6.8" or "X.6.10"
>>
>>Can somebody remind me why we have 2 different Enhanced Status Code which
>>mean the same thing?
>>    
>>
>
>I think that it is due to the Associated basic status code:
>
>      Code:               X.6.8
>      Sample Text:        UTF-8 string reply is required,
>                          but not permitted by the client
>      Associated basic status code:  553, 550
>
>
>      Code:               X.6.10
>      Sample Text:        UTF-8 string reply is required,
>                          but not permitted by the client
>      Associated basic status code:  252
>  
>
But the first digit of the basic status code should be included in the 
X.6.8/X.6.10 enhanced status code. I.e. X.6.8 would become either 2.6.8 
or 5.6.8, depending on what the first digit of the basic code is.

John or Tony (or anybody else who knows), do you have an opinion?

>Jiankang Yao
>  
>
>>  [RFC5248], meaning "A reply containing a UTF-8 string is required to
>>  show the mailbox name, but that form of response is not permitted by
>>  the client".
>>    
>>


From alexey.melnikov@isode.com  Sat Nov 27 04:59:27 2010
Return-Path: <alexey.melnikov@isode.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 BA24B28C15E for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, 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 JaR6OGMm6ik7 for <ima@core3.amsl.com>; Sat, 27 Nov 2010 04:59:26 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 49C8728B56A for <ima@ietf.org>; Sat, 27 Nov 2010 04:59:26 -0800 (PST)
Received: from [188.28.56.209] (188.28.56.209.threembb.co.uk [188.28.56.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPEA7QAEebaL@rufus.isode.com>; Sat, 27 Nov 2010 13:00:30 +0000
Message-ID: <4CF100C4.1070903@isode.com>
Date: Sat, 27 Nov 2010 12:59:48 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] AD review of draft-ietf-eai-rfc5335bis-03 .txt
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: Sat, 27 Nov 2010 12:59:27 -0000

Hi,
Below is my review of draft-ietf-eai-rfc5335bis-03.txt. This is in 
addition to the ABNF issues I reported in a separate email. I might have 
a couple of extra issues, but I need to think them over first.

2.  Background and History

   Use of this SMTP extension helps prevent the introduction of such
   messages into message stores that might misinterpret, improperly
   display, or mangle such messages.  It should be noted that using an
   ESMTP extension does not prevent transferring email messages with
   UTF-8 header fields to other systems that use the email format for
   messages and that may not be upgraded, such as unextended POP and
   IMAP servers.  Changes to these protocols to handle UTF-8 header
   fields are addressed in [RFC5721bis] and [RFC5738bis].  [[Note in
   Draft: RFC5721bis and RFC5738bis did not yet posted.]]

Please delete the note, as it is no longer accurate.


4.1.  UTF-8 Syntax and Normalization

   See [RFC5198] for a discussion of normalization; the use of
   normalization form NFC is RECOMMENDED.

I think NFC needs a Normative reference.


4.3.  Syntax Extensions to RFC 5322

   description   = "Content-Description:" unstructured CRLF

   The <utext> syntax is extended above to allow UTF-8 in all
   <unstructured> header fields.

The problem with this is that <unstructured> is not referencing <text>.
RFC 5322 defines:

   unstructured    =   (*([FWS] VCHAR) *WSP) / obs-unstruct

So should this document also extend <unstructured> to allow UTF-8?


   Note, however, this does not remove any constraint on the character
   set of protocol elements; for instance, all the allowed values for
   timezone in the "Date:" headers are still expressed in ASCII.  And
   also, none of this revised syntax changes what is allowed in a
   <message-id>, which will still remain in pure ASCII.

In the last sentence I've noticed that one of the revisions of this draft
changed <msg-id> to <message-id> (as compared to RFC 5335). I believe this
is incorrect, because <msg-id> is an ABNF production used in many other 
places,
such as in In-reply-to and References header fields. So please undo the 
change.

Also, "Date:" headers --> "Date:" header fields.


4.4.  Change on addr-spec Syntax

   Let-dig      =  <See Section 4.1.3 of RFC 5321>

This should be pointing to Section 4.1.2 of RFC 5321.


4.5.  Trace Field Syntax

   The uFor ( described in [I-D.ietf-eai-rfc5336bis] Section 3.6.3 ))
   has been added to allow the use of internationalized addresses in
   "For" fields. by use of the new uFor syntax.

Extra dot before "by".


5.  Security Considerations

   If a user has a non-ASCII mailbox address and an ASCII mailbox
   address, a digital certificate that identifies that user may have
   both addresses in the identity.  Having multiple email addresses as
   identities in a single certificate is already supported in PKIX
   (Public Key Infrastructure for X.509 Certificates) and OpenPGP.

This needs Informative references to PKIX and OpenPGP RFC.

   In this specification, a user could provide an ASCII alternative
   address for a non-ASCII address.  However, it is possible these two
   addresses go to different mailboxes, or even different people.  This
   configuration may be based on a user's personal choice or on
   administration policy.  We recognize that if ASCII and non-ASCII
   email is delivered to two different destinations, based on MTA
   capability, this may violate the principle of least astonishment, but
   this is not a "protocol problem".

I think this paragraph is no longer relevant and needs to be deleted.


6.  IANA Considerations

   IANA has registered the message/global MIME type using the
   registration form contained in Section 4.4.

This should be a bit clearer that IANA needs to update the current 
registration
to point to this document.


 [RFC1652]

This reference doesn't seem to be Normative.


Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From alexey.melnikov@isode.com  Sat Nov 27 05:11:16 2010
Return-Path: <alexey.melnikov@isode.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 2C67128C16C for <ima@core3.amsl.com>; Sat, 27 Nov 2010 05:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, 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 0r+lYtlECvnl for <ima@core3.amsl.com>; Sat, 27 Nov 2010 05:10:48 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 479F628C165 for <ima@ietf.org>; Sat, 27 Nov 2010 05:10:26 -0800 (PST)
Received: from [188.28.56.209] (188.28.56.209.threembb.co.uk [188.28.56.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPEDgQAEecA0@rufus.isode.com>; Sat, 27 Nov 2010 13:11:31 +0000
Message-ID: <4CF10356.20809@isode.com>
Date: Sat, 27 Nov 2010 13:10:46 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
References: <4CF0307D.9090900@isode.com>
In-Reply-To: <4CF0307D.9090900@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 13:11:16 -0000

Alexey Melnikov wrote:

> 4.  IANA Considerations
>
>   +---------------+-----------------------------+---------------------+
>   | WITH protocol | Description                 | Reference           |
>   | types         |                             |                     |
>   +---------------+-----------------------------+---------------------+
>   | UTF8SMTPbis   | UTF8SMTPbis with Service    | [RFCXXXX]           |
>   |               | Extensions                  |                     |
>   | UTF8SMTPbisA  | UTF8SMTPbis with SMTP AUTH  | [RFC4954] [RFCXXXX] |
>   | UTF8SMTPbisS  | UTF8SMTPbis with STARTTLS   | [RFC3207] [RFCXXXX] |
>   | UTF8SMTPbisSA | UTF8SMTPbis with both       | [RFC3207] [RFC4954] |
>   |               | STARTTLS and SMTP AUTH      | [RFCXXXX]           |
>   +---------------+-----------------------------+---------------------+
>
> Do we really need to change the WITH protocol types?

I remembered one more thing: if other LMTP related changes are done, 
this section should also register values for LMTP. E.g. 
UTF8LMTP/UTF8LMTPA/UTF8LMTPS/UTF8LMTPSA.

From alexey.melnikov@isode.com  Sat Nov 27 05:12:17 2010
Return-Path: <alexey.melnikov@isode.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 7C1C528B56A for <ima@core3.amsl.com>; Sat, 27 Nov 2010 05:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, 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 pGXVMm3NqhMR for <ima@core3.amsl.com>; Sat, 27 Nov 2010 05:12:15 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id F1F9B28C166 for <ima@ietf.org>; Sat, 27 Nov 2010 05:12:12 -0800 (PST)
Received: from [188.28.56.209] (188.28.56.209.threembb.co.uk [188.28.56.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPED5QAEeXRD@rufus.isode.com>; Sat, 27 Nov 2010 13:13:10 +0000
Message-ID: <4CF103B8.6030606@isode.com>
Date: Sat, 27 Nov 2010 13:12:24 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
References: <4CF100C4.1070903@isode.com>
In-Reply-To: <4CF100C4.1070903@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] uQuoted-Pair from draft-ietf-eai-rfc5335bis-03 .txt
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: Sat, 27 Nov 2010 13:12:17 -0000

4.3.  Syntax Extensions to RFC 5322

   uQuoted-Pair   = ("\" uText) / obs-qp

I think this is too permissive (although obs-qp allows for control 
characters
already). RFC 5322 says:

 text            =   %d1-9 /            ; Characters excluding CR
                     %d11 /             ;  and LF
                     %d12 /
                     %d14-127

 quoted-pair     =   ("\" (VCHAR / WSP)) / obs-qp

And the ABNF document defines:

 VCHAR          =  %x21-7E
                   ; visible (printing) characters

 WSP            =  SP / HTAB
                   ; white space

So I think something like the following would be more appropriate:

   uQuoted-Pair   = ("\" (VCHAR / WSP / UTF8-xtra-char )) / obs-qp

But that would mean that a single \ can escape a sequence of octets. Is 
that Ok?


From yaojk@cnnic.cn  Sat Nov 27 07:13:29 2010
Return-Path: <yaojk@cnnic.cn>
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 0FA6828C0D0 for <ima@core3.amsl.com>; Sat, 27 Nov 2010 07:13:29 -0800 (PST)
X-Quarantine-ID: <ISHOcw3SRw4K>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -97.999
X-Spam-Level: 
X-Spam-Status: No, score=-97.999 tagged_above=-999 required=5 tests=[AWL=-0.557, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 ISHOcw3SRw4K for <ima@core3.amsl.com>; Sat, 27 Nov 2010 07:13:28 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id E455328B23E for <ima@ietf.org>; Sat, 27 Nov 2010 07:13:24 -0800 (PST)
Received: (eyou send program); Sat, 27 Nov 2010 23:14:30 +0800
Message-ID: <490870870.19386@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sat, 27 Nov 2010 23:14:30 +0800
Message-ID: <C1E07D7276674AED96D4ADC6812DFED7@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
Date: Sat, 27 Nov 2010 23:14:30 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0074_01CB8E88.D874F0B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [EAI] mailbox in rfc5321 and 5322 VS mailbox in rfc5335bis and 5336bis
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: Sat, 27 Nov 2010 15:13:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0074_01CB8E88.D874F0B0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

RGVhciBhbGwsDQoNCnRoZSBtYWlsYm94cyBkZWZpbml0aW9ucyBpbiBSRkM1MzIxIGFuZCA1MzIy
IGFyZSBkZWZpbmVkIGZvciBkaWZmZXJlbnQgcHVycG9zZXMuDQoNCnRoZSBtYWlsYm94cyBkZWZp
bml0aW9ucyBpbiBSRkM1MzIxIGFyZSBmb3IgY29tbWFuZHMgYW5kIGVudmVsb3BlLCBzbyBjYW4g
bm90IGluY2x1ZGUgQ0ZXUzsNCnRoZSBtYWlsYm94cyBkZWZpbml0aW9ucyBpbiBSRkM1MzIyIGFy
ZSBmb3IgbWFpbCBoZWFkZXJzLCBzbyBjYW4gaW5jbHVkZSBDRldTLg0KDQpzaW1pbGFybHksIGl0
IHNlZW1zIHRoYXQgbWFpbGJveCBkZWZpbml0aW9ucyBpbiByZmM1MzM1YmlzIGFuZCA1MzM2Ymlz
IGhhdmUgdG8gYmUgZGVmaW5lZCBkaWZmZXJlbnRseSBpbiBib3RoIGRvY3VtZW50cy4NCg0KSmlh
bmthbmcgWWFvDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkJlbG93IGFyZSBzb21lIHN5bnRheCBk
ZWZpbml0aW9ucyBjb3BpZWQgZnJvbSByZmM1MzIxIGFuZCByZmM1MzIyDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KaW4gcmZjIDUzMjENCg0KTWFpbGJveCAgICAgICAgPSBMb2NhbC1wYXJ0ICJAIiAo
IERvbWFpbiAvIGFkZHJlc3MtbGl0ZXJhbCApDQogYWRkcmVzcy1saXRlcmFsICA9ICJbIiAoIElQ
djQtYWRkcmVzcy1saXRlcmFsIC8NCiAgICAgICAgICAgICAgICAgICAgSVB2Ni1hZGRyZXNzLWxp
dGVyYWwgLw0KICAgICAgICAgICAgICAgICAgICBHZW5lcmFsLWFkZHJlc3MtbGl0ZXJhbCApICJd
Ig0KDQogICBEb21haW4gICAgICAgICA9IHN1Yi1kb21haW4gKigiLiIgc3ViLWRvbWFpbikNCg0K
DQogICBzdWItZG9tYWluICAgICA9IExldC1kaWcgW0xkaC1zdHJdDQoNCiAgIExvY2FsLXBhcnQg
ICAgID0gRG90LXN0cmluZyAvIFF1b3RlZC1zdHJpbmcgICAgICAgICAgICAgICAgICA7IE1BWSBi
ZSBjYXNlLXNlbnNpdGl2ZSAgIERvdC1zdHJpbmcgICAgID0gQXRvbSAqKCIuIiAgQXRvbSkgICBB
dG9tICAgICAgICAgICA9IDEqYXRleHRpbiByZmMgNTMyMm1haWxib3ggICAgICAgICA9ICAgbmFt
ZS1hZGRyIC8gYWRkci1zcGVjDQoNCiAgIG5hbWUtYWRkciAgICAgICA9ICAgW2Rpc3BsYXktbmFt
ZV0gYW5nbGUtYWRkcg0KDQogICBhbmdsZS1hZGRyICAgICAgPSAgIFtDRldTXSAiPCIgYWRkci1z
cGVjICI+IiBbQ0ZXU10gLw0KICAgICAgICAgICAgICAgICAgICAgICBvYnMtYW5nbGUtYWRkcg0K
YWRkci1zcGVjICAgICAgID0gICBsb2NhbC1wYXJ0ICJAIiBkb21haW4NCg0KICAgbG9jYWwtcGFy
dCAgICAgID0gICBkb3QtYXRvbSAvIHF1b3RlZC1zdHJpbmcgLyBvYnMtbG9jYWwtcGFydA0KDQog
ICBkb21haW4gICAgICAgICAgPSAgIGRvdC1hdG9tIC8gZG9tYWluLWxpdGVyYWwgLyBvYnMtZG9t
YWluDQoNCiAgIGRvbWFpbi1saXRlcmFsICA9ICAgW0NGV1NdICJbIiAqKFtGV1NdIGR0ZXh0KSBb
RldTXSAiXSIgW0NGV1NdDQoNCg0KICBhdG9tICAgICAgICAgICAgPSAgIFtDRldTXSAxKmF0ZXh0
IFtDRldTXQ0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ==

------=_NextPart_000_0074_01CB8E88.D874F0B0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBuYW1lPUdFTkVSQVRPUiBjb250
ZW50PSJNU0hUTUwgOC4wMC42MDAxLjE4OTc1Ij4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFEPg0K
PEJPRFkgYmdDb2xvcj0jY2NlOGNmPg0KPERJVj48Rk9OVCBzaXplPTI+RGVhciBhbGwsPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9O
VCBzaXplPTI+dGhlIG1haWxib3hzIGRlZmluaXRpb25zIGluIFJGQzUzMjEgYW5kIDUzMjIgYXJl
IGRlZmluZWQgZm9yIA0KZGlmZmVyZW50IHB1cnBvc2VzLjwvRk9OVD48L0RJVj4NCjxESVY+PEZP
TlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPnRoZSBtYWls
Ym94cyBkZWZpbml0aW9ucyBpbiBSRkM1MzIxIGFyZSBmb3IgY29tbWFuZHMgYW5kIA0KZW52ZWxv
cGUsIHNvIGNhbiBub3QgaW5jbHVkZSBDRldTOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6
ZT0yPg0KPERJVj48Rk9OVCBzaXplPTI+dGhlIG1haWxib3hzIGRlZmluaXRpb25zIGluIFJGQzUz
MjIgYXJlIGZvciBtYWlsIGhlYWRlcnMsIHNvIA0KY2FuIGluY2x1ZGUgQ0ZXUy48L0ZPTlQ+PC9E
SVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5zaW1pbGFybHksIGl0IHNlZW1zIHRoYXQgbWFp
bGJveCBkZWZpbml0aW9ucyZuYnNwO2luIHJmYzUzMzViaXMgYW5kIDUzMzZiaXMgDQpoYXZlIHRv
IGJlIGRlZmluZWQgZGlmZmVyZW50bHkgaW4gYm90aCBkb2N1bWVudHMuPC9ESVY+DQo8RElWPiZu
YnNwOzwvRElWPg0KPERJVj5KaWFua2FuZyBZYW88L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCANCnNpemU9Mj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+QmVsb3cgYXJlIHNvbWUgc3ludGF4IGRlZmluaXRp
b25zIGNvcGllZCBmcm9tIHJmYzUzMjEgYW5kIA0KcmZjNTMyMjwvRk9OVD48L0RJVj4NCjxESVY+
PEZPTlQgDQpzaXplPTI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L0ZPTlQ+PC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj5pbiByZmMgNTMyMTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwv
Rk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+TWFpbGJveCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyA9IExvY2FsLXBhcnQgIkAiICggRG9tYWluIA0KLyBhZGRyZXNzLWxp
dGVyYWwgKTwvRElWPg0KPERJVj4mbmJzcDthZGRyZXNzLWxpdGVyYWwmbmJzcDsgPSAiWyIgKCBJ
UHY0LWFkZHJlc3MtbGl0ZXJhbCANCi88QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KSVB2Ni1hZGRyZXNzLWxpdGVyYWwgDQovPEJS
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyANCkdlbmVyYWwtYWRkcmVzcy1saXRlcmFsICkgIl0iPEJSPjwvRElWPg0KPERJVj4mbmJzcDsm
bmJzcDsgRG9tYWluJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7ID0gDQpzdWItZG9tYWluICooIi4iIHN1Yi1kb21haW4pPEJSPjxCUj48UFJFIGNsYXNzPW5l
d3BhZ2U+ICAgc3ViLWRvbWFpbiAgICAgPSBMZXQtZGlnIFtMZGgtc3RyXQ0KDQo8QlI+PEJSPiZu
YnNwOyZuYnNwOyBMb2NhbC1wYXJ0Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ID0gRG90LXN0cmlu
ZyAvIFF1b3RlZC1zdHJpbmc8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IDsgTUFZIGJlIGNhc2Utc2Vuc2l0aXZlPEJSPjxCUj48QlI+Jm5ic3A7Jm5ic3A7
IERvdC1zdHJpbmcmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPSBBdG9tICooIi4iJm5ic3A7IEF0
b20pPEJSPjxCUj4mbmJzcDsmbmJzcDsgQXRvbSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA9IDEqYXRleHQ8L1BSRT48UFJFIGNsYXNz
PW5ld3BhZ2U+Jm5ic3A7PC9QUkU+PFBSRSBjbGFzcz1uZXdwYWdlPiZuYnNwOzwvUFJFPjxQUkUg
Y2xhc3M9bmV3cGFnZT5pbiByZmMgNTMyMjwvUFJFPjxQUkUgY2xhc3M9bmV3cGFnZT5tYWlsYm94
ICAgICAgICAgPSAgIG5hbWUtYWRkciAvIGFkZHItc3BlYw0KDQogICBuYW1lLWFkZHIgICAgICAg
PSAgIFtkaXNwbGF5LW5hbWVdIGFuZ2xlLWFkZHINCg0KICAgYW5nbGUtYWRkciAgICAgID0gICBb
Q0ZXU10gIiZsdDsiIGFkZHItc3BlYyAiJmd0OyIgW0NGV1NdIC8NCiAgICAgICAgICAgICAgICAg
ICAgICAgb2JzLWFuZ2xlLWFkZHINCmFkZHItc3BlYyAgICAgICA9ICAgbG9jYWwtcGFydCAiQCIg
ZG9tYWluDQoNCiAgIGxvY2FsLXBhcnQgICAgICA9ICAgZG90LWF0b20gLyBxdW90ZWQtc3RyaW5n
IC8gb2JzLWxvY2FsLXBhcnQNCg0KICAgZG9tYWluICAgICAgICAgID0gICBkb3QtYXRvbSAvIGRv
bWFpbi1saXRlcmFsIC8gb2JzLWRvbWFpbg0KDQogICBkb21haW4tbGl0ZXJhbCAgPSAgIFtDRldT
XSAiWyIgKihbRldTXSBkdGV4dCkgW0ZXU10gIl0iIFtDRldTXQ0KDQoNCiAgYXRvbSAgICAgICAg
ICAgID0gICBbQ0ZXU10gMSphdGV4dCBbQ0ZXU10NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L1BS
RT48UFJFIGNsYXNzPW5ld3BhZ2U+Jm5ic3A7PC9QUkU+PFBSRSBjbGFzcz1uZXdwYWdlPjxCUj48
QlI+Jm5ic3A7PC9QUkU+PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0074_01CB8E88.D874F0B0--


From klensin@jck.com  Sat Nov 27 12:22:03 2010
Return-Path: <klensin@jck.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 0AFB228C0DF for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:22:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 dxJ1Z2VS0W6Q for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:22:02 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D657D28C0D7 for <ima@ietf.org>; Sat, 27 Nov 2010 12:22:01 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMRIU-000Lqb-J9; Sat, 27 Nov 2010 15:23:02 -0500
Date: Sat, 27 Nov 2010 15:23:01 -0500
From: John C Klensin <klensin@jck.com>
To: Jiankang YAO <yaojk@cnnic.cn>, Alexey Melnikov <alexey.melnikov@isode.com>, EAI WG <ima@ietf.org>
Message-ID: <DD1963D6B97705E11D21376C@[192.168.1.128]>
In-Reply-To: <490861644.12446@cnnic.cn>, <F87CC27809C94FAC8469EF5551C4A394@LENOVO47E041CF>
References: <490809525.17302@cnnic.cn> <490861644.12446@cnnic.cn>, <F87CC27809C94FAC8469EF5551C4A394@LENOVO47E041CF>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] WITH protocol types Re: AD review of	draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 20:22:03 -0000

--On Saturday, November 27, 2010 8:40 PM +0800 Jiankang YAO
<yaojk@cnnic.cn> wrote:

> 
> ----- Original Message ----- 
> From: "Alexey Melnikov" <alexey.melnikov@isode.com>
> To: "EAI WG" <ima@ietf.org>
> Sent: Saturday, November 27, 2010 6:11 AM
> Subject: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
> 
> 
> ....
>> 
>> 4.  IANA Considerations
>> 
>>   +---------------+-----------------------------+------------
>>   ---------+ | WITH protocol | Description                 |
>>   Reference           | | types         |
>>   |                     |
>>   +---------------+-----------------------------+------------
>>   ---------+ | UTF8SMTPbis   | UTF8SMTPbis with Service    |
>>   [RFCXXXX]           | |               | Extensions
>>   |                     | | UTF8SMTPbisA  | UTF8SMTPbis with
>>   SMTP AUTH  | [RFC4954] [RFCXXXX] | | UTF8SMTPbisS  |
>>   UTF8SMTPbis with STARTTLS   | [RFC3207] [RFCXXXX] | |
>>   UTF8SMTPbisSA | UTF8SMTPbis with both       | [RFC3207]
>>   [RFC4954] | |               | STARTTLS and SMTP AUTH      |
>>   [RFCXXXX]           |
>>   +---------------+-----------------------------+------------
>>   ---------+
>> 
>> Do we really need to change the WITH protocol types?
>> 
> 
> RFC5336 has updated the WITH protocol types.
> so this time, we might have to update it again.
> 
> the updates for WITH protocol types were suggested by Chris
> Newman  in RFC5336.
> 
> I think that Chris may have a better answer to this question.

I'd be happy to hear from Chris but, from the standpoint of the
protocols that affect WITH, I don't see any difference between
5336 and 5336bis and hence no need to change the keyword.  Note
that downgrade considerations cannot apply because the message
is being delivered.   If the first-version experimental
protocols applied, then things would in fact be different.

    john


From klensin@jck.com  Sat Nov 27 12:25:22 2010
Return-Path: <klensin@jck.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 C30D03A6B2A for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 wvMKSM3QAKpO for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:25:20 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 22F4C3A6AE1 for <ima@ietf.org>; Sat, 27 Nov 2010 12:25:19 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMRLj-000LwE-Od; Sat, 27 Nov 2010 15:26:23 -0500
Date: Sat, 27 Nov 2010 15:26:23 -0500
From: John C Klensin <klensin@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Jiankang YAO <yaojk@cnnic.cn>, EAI WG <ima@ietf.org>
Message-ID: <7E1DC20770A03D958BEC7041@[192.168.1.128]>
In-Reply-To: <4CF0FED1.50501@isode.com>
References: <490809525.17302@cnnic.cn> <490820413.31367@cnnic.cn> <4CF0FED1.50501@isode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] response code Re: AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Sat, 27 Nov 2010 20:25:22 -0000

--On Saturday, November 27, 2010 12:51 PM +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

>>>  If the SMTP reply requires UTF-8 strings, but UTF-8 is not
>>>  allowed in the reply, and the server supports enhanced mail
>>>  system status codes [RFC3463], the enhanced response code
>>>  is either "X.6.8" or "X.6.10"
>>> 
>>> Can somebody remind me why we have 2 different Enhanced
>>> Status Code which mean the same thing?
>>>    
>>> 
>> 
>> I think that it is due to the Associated basic status code:
>> 
>>      Code:               X.6.8
>>      Sample Text:        UTF-8 string reply is required,
>>                          but not permitted by the client
>>      Associated basic status code:  553, 550
>> 
>> 
>>      Code:               X.6.10
>>      Sample Text:        UTF-8 string reply is required,
>>                          but not permitted by the client
>>      Associated basic status code:  252
>>  
>> 
> But the first digit of the basic status code should be
> included in the X.6.8/X.6.10 enhanced status code. I.e. X.6.8
> would become either 2.6.8 or 5.6.8, depending on what the
> first digit of the basic code is.
> 
> John or Tony (or anybody else who knows), do you have an
> opinion?

Unless I'm confused, we need either 2.6.8 and 5.6.8 _or_ 2.6.10
and 5.6.10, but not a mixture of x.6.8 and x.6.10.  I.e., I
think I agree with Alexey -- we either need either one basic
enhanced code or more explanation than appears above.

Tony?

    john






From klensin@jck.com  Sat Nov 27 12:33:21 2010
Return-Path: <klensin@jck.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 1EF6B28C0EB for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:33:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 h2KBjvzwe5Z1 for <ima@core3.amsl.com>; Sat, 27 Nov 2010 12:33:18 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1004A3A6AE1 for <ima@ietf.org>; Sat, 27 Nov 2010 12:33:18 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMRTT-000M5H-UP; Sat, 27 Nov 2010 15:34:24 -0500
Date: Sat, 27 Nov 2010 15:34:23 -0500
From: John C Klensin <klensin@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, EAI WG <ima@ietf.org>
Message-ID: <8CB40CB61DF07675C0C60ED2@[192.168.1.128]>
In-Reply-To: <4CF103B8.6030606@isode.com>
References: <4CF100C4.1070903@isode.com> <4CF103B8.6030606@isode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] uQuoted-Pair from draft-ietf-eai-rfc5335bis-03 .txt
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: Sat, 27 Nov 2010 20:33:21 -0000

--On Saturday, November 27, 2010 1:12 PM +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

> 
> 4.3.  Syntax Extensions to RFC 5322
> 
>    uQuoted-Pair   = ("\" uText) / obs-qp
> 
> I think this is too permissive (although obs-qp allows for
> control characters
> already). RFC 5322 says:
> 
>  text            =   %d1-9 /            ; Characters excluding
> CR
>                      %d11 /             ;  and LF
>                      %d12 /
>                      %d14-127
> 
>  quoted-pair     =   ("\" (VCHAR / WSP)) / obs-qp
> 
> And the ABNF document defines:
> 
>  VCHAR          =  %x21-7E
>                    ; visible (printing) characters
> 
>  WSP            =  SP / HTAB
>                    ; white space
> 
> So I think something like the following would be more
> appropriate:
> 
>    uQuoted-Pair   = ("\" (VCHAR / WSP / UTF8-xtra-char )) /
> obs-qp
> 
> But that would mean that a single \ can escape a sequence of
> octets. Is that Ok?

My recollection is that the WG's decisions the first time around
was to drastically reduce the number of permitted "weird"
characters, i.e., if one decides to move into UTF-8 address
land, one gives up the control characters (both C0 and C1) the
embedded spaces in addresses, and most of the need to escape or
quote anything.  What would be prohibited would include anything
the 5321 or 5322 mark as obsolete.   I don't remember any
discussion this time around that would reverse that rule so, if
my recollection is correct, then this ought to be drastically
limited.

Remember that mixing essentially unrestricted Unicode with,
e.g., control characters can cause what is technically known as
"a big mess", so part of the question, IMO, is whether one can
find strong justification for permitting all of those things.

Obviously need the opinions of others about this.

   john


From klensin@jck.com  Sat Nov 27 13:04:30 2010
Return-Path: <klensin@jck.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 8D73E28C0D0 for <ima@core3.amsl.com>; Sat, 27 Nov 2010 13:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599]
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 0a07MtPnLaQe for <ima@core3.amsl.com>; Sat, 27 Nov 2010 13:04:28 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id E31003A6AE1 for <ima@ietf.org>; Sat, 27 Nov 2010 13:04:27 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMRxc-000Mri-DI; Sat, 27 Nov 2010 16:05:32 -0500
Date: Sat, 27 Nov 2010 16:05:31 -0500
From: John C Klensin <klensin@jck.com>
To: Jiankang YAO <yaojk@cnnic.cn>, ima@ietf.org
Message-ID: <8DC51F0046149289B53436CC@[192.168.1.128]>
In-Reply-To: <490870870.19386@cnnic.cn>, <C1E07D7276674AED96D4ADC6812DFED7@LENOVO47E041CF>
References: <490870870.19386@cnnic.cn>, <C1E07D7276674AED96D4ADC6812DFED7@LENOVO47E041CF>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] mailbox in rfc5321 and 5322 VS mailbox in rfc5335bis and	5336bis
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: Sat, 27 Nov 2010 21:04:30 -0000

--On Saturday, November 27, 2010 11:14 PM +0800 Jiankang YAO
<yaojk@cnnic.cn> wrote:

> Dear all,
> 
> the mailboxs definitions in RFC5321 and 5322 are defined for
> different purposes.
> 
> the mailboxs definitions in RFC5321 are for commands and
> envelope, so can not include CFWS; the mailboxs definitions in
> RFC5322 are for mail headers, so can include CFWS.

Unless I'm misunderstanding, the key issue is not the CFWS or
the envelope; it is two related issues:

(1) The way the definitions in 5322 are arranged is not optimal
for this purpose (or for those of 5321 compatibility).   
The <mailbox> of Section 3.4 could rationally be rewritten as 

   mailbox = name-addr | SMTP-addr | addr-spec
   SMTP-addr = "<" addr-spec ">"
   
i.e., either a name-addr (with the optional display-name and
optional brackets, CWFS, etc.) or a narrowly-defined SMTP
address (brackets required) or an addr-spec without the brackets.

If it had been done that way, or something like it, then 5321
could use a definition identical to that of 5322 (Pete, consider
this a not-subtle hint about 5322bis/5321bis should we start
YAMmering again).    One could simplify this even further -- see
(2) below.

>From that point of view, 5336 needs to pick up on the 5335
equivalent of "addr-spec" and not on "mailbox" or "address".

(2) From a slightly different point of view, what has created
the confusion here is that 5321 (correctly, IMO) uses the term
"mailbox" to refer to what 5322 calls an addr-spec (no brackets
or spacing), while 5322 uses "mailbox" to refer to something
that might potentially contain a display-name, CWFS in various
interesting places (including inside the display-name), some
brackets (required if the display name is present), and possibly
a comment (whether the comment is logically part of the
5322-mailbox is part of the reason we circled from group syntax
to comment syntax and back in the discussions in Beijing ...
certainly there is extensive historical/ operational deployment
precedent for treating it as both part and not-part).

As a mental exercise as to what the "mailbox" actually is,
consider whether there are any deployed systems that would treat 

     Joe <xxx@example.com>
     John <xxx@example.com>

as going to different destinations in a mail store.  I can
remember systems that would dispatch differently (think 

     Joe Smith <email-to-internal-post-gateway@example.edu> )
but we got over those, usually in favor of such arrangements as
     Joe Smith
<joe-smith%email-to-internal-post-gateway@example.edu>,  a
_very_ long time ago.

> similarly, it seems that mailbox definitions in rfc5335bis and
> 5336bis have to be defined differently in both documents.

Well, see if 5336 and 5336 can make a common "addr-spec" (or
5321-mailbox) definition work without worrying about
5322-mailbox.

   john


From yaojk@cnnic.cn  Sun Nov 28 06:13:05 2010
Return-Path: <yaojk@cnnic.cn>
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 3FAA63A6BD4 for <ima@core3.amsl.com>; Sun, 28 Nov 2010 06:13:05 -0800 (PST)
X-Quarantine-ID: <aRmzu+oZ-W5Y>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -97.937
X-Spam-Level: 
X-Spam-Status: No, score=-97.937 tagged_above=-999 required=5 tests=[AWL=-0.494, BAYES_50=0.001, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, 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 aRmzu+oZ-W5Y for <ima@core3.amsl.com>; Sun, 28 Nov 2010 06:13:04 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id AA43F3A6BD0 for <ima@ietf.org>; Sun, 28 Nov 2010 06:13:02 -0800 (PST)
Received: (eyou send program); Sun, 28 Nov 2010 22:14:10 +0800
Message-ID: <490953650.02469@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Sun, 28 Nov 2010 22:14:10 +0800
Message-ID: <796763CEE20E4C0BB1E5F900C6337815@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "John C Klensin" <klensin@jck.com>, <ima@ietf.org>
References: <490870870.19386@cnnic.cn>, <C1E07D7276674AED96D4ADC6812DFED7@LENOVO47E041CF> <490891936.09729@cnnic.cn>
Date: Sun, 28 Nov 2010 22:14:15 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: Re: [EAI] mailbox in rfc5321 and 5322 VS mailbox in rfc5335bis and	5336bis
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: Sun, 28 Nov 2010 14:13:05 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkpvaG4gQyBLbGVuc2luIiA8
a2xlbnNpbkBqY2suY29tPg0KVG86ICJKaWFua2FuZyBZQU8iIDx5YW9qa0Bjbm5pYy5jbj47IDxp
bWFAaWV0Zi5vcmc+DQpTZW50OiBTdW5kYXksIE5vdmVtYmVyIDI4LCAyMDEwIDU6MDUgQU0NClN1
YmplY3Q6IFJlOiBbRUFJXSBtYWlsYm94IGluIHJmYzUzMjEgYW5kIDUzMjIgVlMgbWFpbGJveCBp
biByZmM1MzM1YmlzIGFuZCA1MzM2YmlzDQoNCg0KLi4uLg0KPj4gc2ltaWxhcmx5LCBpdCBzZWVt
cyB0aGF0IG1haWxib3ggZGVmaW5pdGlvbnMgaW4gcmZjNTMzNWJpcyBhbmQNCj4+IDUzMzZiaXMg
aGF2ZSB0byBiZSBkZWZpbmVkIGRpZmZlcmVudGx5IGluIGJvdGggZG9jdW1lbnRzLg0KPiANCj4g
V2VsbCwgc2VlIGlmIDUzMzYgYW5kIDUzMzYgY2FuIG1ha2UgYSBjb21tb24gImFkZHItc3BlYyIg
KG9yDQo+IDUzMjEtbWFpbGJveCkgZGVmaW5pdGlvbiB3b3JrIHdpdGhvdXQgd29ycnlpbmcgYWJv
dXQNCj4gNTMyMi1tYWlsYm94Lg0KPiANCg0KYW55IG90aGVyIGNvbW1lbnRzPw0KDQppdCBtYXkg
YmUgbXVjaCBjbGVhcmVyIGlmICB0aGUgbWFpbGJveCBkZWZpbml0aW9uIGluIHJmYzUzMzUgYW5k
IHJmYzUzMzYgc3RpbGwgYXBwbHkgdGhhdCBpbiByZmM1MzM1YmlzIGFuZCByZmM1MzM2YmlzLg0K
DQpKaWFua2FuZyBZYW8NCg0KPiAgIGpvaG4NCj4=


From klensin@jck.com  Sun Nov 28 23:31:21 2010
Return-Path: <klensin@jck.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 8717F3A6B22 for <ima@core3.amsl.com>; Sun, 28 Nov 2010 23:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level: 
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599]
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 z8ZWZbkIjbiG for <ima@core3.amsl.com>; Sun, 28 Nov 2010 23:31:20 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 80A8A3A6806 for <ima@ietf.org>; Sun, 28 Nov 2010 23:31:19 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMyDr-000O46-Fu for ima@ietf.org; Mon, 29 Nov 2010 02:32:28 -0500
Date: Mon, 29 Nov 2010 02:32:25 -0500
From: John C Klensin <klensin@jck.com>
To: EAI WG <ima@ietf.org>
Message-ID: <16205D143513DBD7369EA39F@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [EAI] WG Co-chair review of 5336bis (SMTP extension)
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, 29 Nov 2010 07:31:21 -0000

Hi.

While I'd like to consider this a final review before handoff to
the IESG, the document is in rather poor shape in some areas,
causing me to have some concerns about the quality of reviews
performed by those who promised to review it.   Note that all of
the comments below except (5) below are essentially editorial,
rather than substantive.  But we should fix our own editorial
problems (and authors should have them under control before we
reach this point).  While I believe that many of the sorts of
issues pointed out below can and should be left to the RFC
Editor, the IESG has not agreed in recent years, preferring to
have most or all editorial matters settled before handoff to the
RFC Editor.  If we hand the IESG a document and they start
editorial nit-picking, we waste a lot of time (at best).

I have tried to avoid raising issues pointed out in other notes
to the mailing list, so the list below should be largely new.

(1) Abstract: "syntax", not "syntaxes".

(2) The Introduction is incoherent, consisting of a series of
isolated, choppy statements that bear no obvious relationship to
each other.  Most of those statements may not be necessary if
Framework (4952bis) is really prerequisite for reading/
understanding this document.  I'd recommend discarding most of
the first paragraph of the Introduction and merging the rest
with the present Section 1.1.

(3) In Section 1.1, Framework should be cited (i.e., with
"[RFC4952bis]" when it is first mentioned and probably not again
in the Section 1.   Similarly, a citation to RFC3629 is not
needed each time UTF-8 is mentioned.  

(4) Section 2, third sentence, begins "In order to provide
information that may be needed in downgrading...".  That
sentence is simply false -- there is no alternate address any
more-- and extremely misleading.  This is not the only place
where artifacts of downgrading still appear, see, e.g., the last
sentence of Section 3.6.2 (which might possibly be fixed by
replacing "downgrades" by "rejections").

(5) Section 3.1(3): "Clients MUST ignore any parameters..." was
fine for the experimental protocols.  At this point, we need to
decide what the WG intends about extension models.  "MUST
ignore" implies that any future extension must be optional,
i.e., the system will work in a predictable way if parameters
are supplied and ignored.  "MUST reject" (i.e., behave as if
UTF8SMTPbis had not been supplied at all) means either that
there will be no extensions or that they have to be assumed to
be incompatible.  The latter is _much_ safer -- what does the WG
intend.    Editorially, this bullet item would be much easier to
follow if it made all statements about the server and then all
statements about the client or vice versa: the current form is
server-requirement / client-requirement / server-requirement.

(6) As a specification that will published a year after IDNA2008
was approved, this document should reflect IDNA2008 terminology,
not an odd mix of IDNA2008 terms, IDNA2003 terms, and informal
language.  Specifically (this may not be a complete list), ACE
labels should not be discussed in Section 3.2 especially with a
parenthetical "as specified" note pointing to IDNA Defs on its
first use.  Instead, the term "A-label" should be used with an
appropriate reference.  Unless there is a specific reason for
doing so (in which case it better be explained to the WG), the
text should not talk about domain names in UTF-8 strings but
about U-labels.  It would be desirable to say, once, that any
U-labels are required to be expressed in UTF-8, but that doesn't
make them UTF-8 strings.   The first bullet in 3.3 should refer
to a U-label as well, Section 3.6 should refer to A-labels, and
so on.

(7) I'm not aware of the term "Message User Agent" ever being
used in an Internet mail context: "Mail User Agent (MUA)".

(8) Also in Section 3.2, the next-to-last paragraph ("This
document applies...") is either internally circular or just too
difficult to parse: it is not clear what the clause "which
requires..." points to or why it is useful.

(9) Section 3.4 points to an appendix to the document for a
definition.  There is no such appendix.   I suspect this should
be pointing to Framework.

(10) In the last paragraph of Section 3.4, the term "bounced" is
used.  Given contemporary usage in 5321 and elsewhere,
"rejected" is probably intended.

(11) Section 3.6.1 is hard to follow.  The phrase "any domain
names that appear in this dialogue" would be reasonable if it
were not followed by "or in responses to...".  Please change
this to be clear that the client must send only ASCII (LDH or
A-label) domains in the EHLO command and that, if the server
provides domain names in the EHLO response, they must be
A-labels.  It might be worth noting that this protocol does not
contemplate the server returning any non-ASCII domain names at
all, especially since the UTF8SMTPbis response is forbidden to
have parameters.

(12) In Section 3.6.2, if we are serious about the "Advice for
non-ASCII & ASCII addresses" and/or "Advice for EAI deployment"
documents, a non-normative forward pointer might be appropriate.
Note the "downgrading" comment there and item (4) above.

(13) In Section 3.6.3 and elsewhere, where a requirement is not
new but simply a restatement of an RFC 5321 requirement, it
would probably be useful to make that clear.  For example, the
first sentence of 3.6.3 might be restated as

	"When an SMTP server receives a message for delivery or
	further processing, RFC 5321 requires that it MUST
	insert trace..."

followed by deleting as much of the subsequent text as possible,
i.e., removing all of the discussion that is not directly
relevant to this extension.

(14) Section 3.6.4.1 is titled "MAIL and RCPT Commands" but
discusses only RCPT commands.  Please either discuss MAIL (it is
not clear to me there is anything to say) or edit the title.
It appears to me that the two paragraphs in this section could
be rewritten to be more clear.  As with (5) above, talk about
the client, then the server or vice versa, not a little bit of
one, the other, and then the first again.

(15) In Section 3.6.4.2, I don't recall Alexey's ABNF check
catching this so note that the line

   "User Name < uMailbox>"

is not ABNF.  It is not clear what it is.

(16) Check with Alexey, but I believe that the correct submitter
for the IANA extended code registrations for a standards track
document (if any are needed after the earlier discussion) is
"IETF EAI WG", or can be omitted entirely, and is not the name
of the second author of the I-D.

(17) Several of the References are not used in the text.  Please
run http://fenron.net/~fenner/ietf/xml2rfc-valid/ if your
original is in XML and, in any event,
http://tools.ietf.org/tools/idnits/ in verbose mode.  The latter
will turn up several additional issues, including the use of the
string "RFC" in the Obsoletes and Updates headers, some spacing
problems with citations, as well as a number of non-issues
(e.g., intentional references to obsolete documents, confusion
of section numbers with IP addresses, etc.)

regards,
   john


(14)

From alexey.melnikov@isode.com  Mon Nov 29 01:55:49 2010
Return-Path: <alexey.melnikov@isode.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 41B903A6C09 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 01:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, 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 HzLBdyWtGozW for <ima@core3.amsl.com>; Mon, 29 Nov 2010 01:55:48 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id D11113A6A0C for <ima@ietf.org>; Mon, 29 Nov 2010 01:55:47 -0800 (PST)
Received: from [92.40.217.222] (92.40.217.222.sub.mbb.three.co.uk [92.40.217.222])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPN45QAEeTkr@rufus.isode.com>; Mon, 29 Nov 2010 09:56:55 +0000
Message-ID: <4CF378BC.4050408@isode.com>
Date: Mon, 29 Nov 2010 09:56:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: John C Klensin <klensin@jck.com>
References: <16205D143513DBD7369EA39F@PST.JCK.COM>
In-Reply-To: <16205D143513DBD7369EA39F@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] WG Co-chair review of 5336bis (SMTP extension)
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, 29 Nov 2010 09:55:49 -0000

John C Klensin wrote:

>Hi.
>  
>
Hi John,
A couple of comments on your review.

>While I'd like to consider this a final review before handoff to
>the IESG, the document is in rather poor shape in some areas,
>causing me to have some concerns about the quality of reviews
>performed by those who promised to review it.   Note that all of
>the comments below except (5) below are essentially editorial,
>rather than substantive.  But we should fix our own editorial
>problems (and authors should have them under control before we
>reach this point).  While I believe that many of the sorts of
>issues pointed out below can and should be left to the RFC
>Editor, the IESG has not agreed in recent years, preferring to
>have most or all editorial matters settled before handoff to the
>RFC Editor.
>
I am not going to defend IESG, but speaking in general terms - if you 
can't understand something, you can't verify if it is correct or not. 
This is a valid ground for DISCUSS.

>If we hand the IESG a document and they start
>editorial nit-picking, we waste a lot of time (at best).
>  
>
So true.

>I have tried to avoid raising issues pointed out in other notes
>to the mailing list, so the list below should be largely new.
>
>(1) Abstract: "syntax", not "syntaxes".
>
>(2) The Introduction is incoherent, consisting of a series of
>isolated, choppy statements that bear no obvious relationship to
>each other.
>
I am afraid I have to agree here.

>Most of those statements may not be necessary if
>Framework (4952bis) is really prerequisite for reading/
>understanding this document.  I'd recommend discarding most of
>the first paragraph of the Introduction and merging the rest
>with the present Section 1.1.
>  
>
 [...]

>(5) Section 3.1(3): "Clients MUST ignore any parameters..." was
>fine for the experimental protocols.  At this point, we need to
>decide what the WG intends about extension models.  "MUST
>ignore" implies that any future extension must be optional,
>i.e., the system will work in a predictable way if parameters
>are supplied and ignored.  "MUST reject" (i.e., behave as if
>UTF8SMTPbis had not been supplied at all) means either that
>there will be no extensions or that they have to be assumed to
>be incompatible.  The latter is _much_ safer -- what does the WG
>intend.
>
Can we anticipate any extensions to this extension?

Personally, I don't think that "MUST ignore" is such a bad option. It 
worked reasonably well for SMTP AUTH, albeit SMTP AUTH is a bit special.

>Editorially, this bullet item would be much easier to
>follow if it made all statements about the server and then all
>statements about the client or vice versa: the current form is
>server-requirement / client-requirement / server-requirement.
>  
>
 [...]

>(15) In Section 3.6.4.2, I don't recall Alexey's ABNF check
>catching this so note that the line
>
>   "User Name < uMailbox>"
>
>is not ABNF.  It is not clear what it is.
>  
>
Good catch, I missed that.

>(16) Check with Alexey, but I believe that the correct submitter
>for the IANA extended code registrations for a standards track
>document (if any are needed after the earlier discussion) is
>"IETF EAI WG", or can be omitted entirely, and is not the name
>of the second author of the I-D.
>  
>
Actually that is Ok. The Change Controller field (if present) must be 
"IETF" or a specific IETF WG.

Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From alexey.melnikov@isode.com  Mon Nov 29 09:15:45 2010
Return-Path: <alexey.melnikov@isode.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 7E9A428C0F0 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, 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 NW0U0X78hrmK for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:15:44 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 9AE873A6C19 for <ima@ietf.org>; Mon, 29 Nov 2010 09:15:44 -0800 (PST)
Received: from [172.16.2.127] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPPgBQAEeabG@rufus.isode.com>; Mon, 29 Nov 2010 17:16:53 +0000
Message-ID: <4CF3DFCC.1040707@isode.com>
Date: Mon, 29 Nov 2010 17:15:56 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
References: <16205D143513DBD7369EA39F@PST.JCK.COM> <4CF378BC.4050408@isode.com>
In-Reply-To: <4CF378BC.4050408@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] WG Co-chair review of 5336bis (SMTP extension)
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, 29 Nov 2010 17:15:45 -0000

Comments on my earlier comments below:

Alexey Melnikov wrote:

> John C Klensin wrote:

 [...]

>> (16) Check with Alexey, but I believe that the correct submitter
>> for the IANA extended code registrations for a standards track
>> document (if any are needed after the earlier discussion) is
>> "IETF EAI WG", or can be omitted entirely, and is not the name
>> of the second author of the I-D.
>
> Actually that is Ok. The Change Controller field (if present) must be 
> "IETF" or a specific IETF WG.

On a second thought: this field is supposed to be used to ask more 
questions about a registration. So it is better to specify the WG 
mailing list there. That is what we've done in the Sieve WG for all 
registrations.


From alexey.melnikov@isode.com  Mon Nov 29 09:22:47 2010
Return-Path: <alexey.melnikov@isode.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 8920B28C102 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, 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 2RrHc+zEoVlj for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:22:46 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id D9C4928C0DC for <ima@ietf.org>; Mon, 29 Nov 2010 09:22:45 -0800 (PST)
Received: from [172.16.2.127] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPPhqwAEeQQf@rufus.isode.com>; Mon, 29 Nov 2010 17:23:55 +0000
Message-ID: <4CF3E170.3040700@isode.com>
Date: Mon, 29 Nov 2010 17:22:56 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: EAI WG <ima@ietf.org>
References: <16205D143513DBD7369EA39F@PST.JCK.COM> <4CF378BC.4050408@isode.com>
In-Reply-To: <4CF378BC.4050408@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] WG Co-chair review of 5336bis (SMTP extension)
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, 29 Nov 2010 17:22:47 -0000

Comments on my earlier comments below:

Alexey Melnikov wrote:

> John C Klensin wrote:

 [...]

>> (5) Section 3.1(3): "Clients MUST ignore any parameters..." was
>> fine for the experimental protocols.  At this point, we need to
>> decide what the WG intends about extension models.  "MUST
>> ignore" implies that any future extension must be optional,
>> i.e., the system will work in a predictable way if parameters
>> are supplied and ignored.  "MUST reject" (i.e., behave as if
>> UTF8SMTPbis had not been supplied at all) means either that
>> there will be no extensions or that they have to be assumed to
>> be incompatible.  The latter is _much_ safer -- what does the WG
>> intend.
>
> Can we anticipate any extensions to this extension?
>
> Personally, I don't think that "MUST ignore" is such a bad option. It 
> worked reasonably well for SMTP AUTH, albeit SMTP AUTH is a bit special.

I checked other SMTP documents and none of them specify that extensions 
to an SMTP extension keyword line is allowed. So I am Ok with following 
what John suggested. Any future extension can advertise another keyword, 
if needed.


From jyee@ca.afilias.info  Mon Nov 29 09:33:44 2010
Return-Path: <jyee@ca.afilias.info>
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 463BC28C192 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:33:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.265
X-Spam-Level: 
X-Spam-Status: No, score=-106.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4, 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 2dU95P9IHLF6 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 09:33:39 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id 9F1DF28C18B for <ima@ietf.org>; Mon, 29 Nov 2010 09:33:37 -0800 (PST)
Received: from ms6.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@ca.afilias.info>) id 1PN7ck-0001AY-5p; Mon, 29 Nov 2010 17:34:46 +0000
Received: from tor-gateway.afilias.info ([199.15.87.4] helo=jyee-lt.tor.afilias-int.info) by smtp.afilias.info with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <jyee@ca.afilias.info>) id 1PN7ck-0001Is-8G; Mon, 29 Nov 2010 17:34:46 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Joseph Yee <jyee@ca.afilias.info>
In-Reply-To: <16205D143513DBD7369EA39F@PST.JCK.COM>
Date: Mon, 29 Nov 2010 12:34:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <040AD0C3-789C-497D-8DAF-D8B9503D3816@ca.afilias.info>
References: <16205D143513DBD7369EA39F@PST.JCK.COM>
To: John C Klensin <klensin@jck.com>
X-Mailer: Apple Mail (2.1082)
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] WG Co-chair review of 5336bis (SMTP extension)
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, 29 Nov 2010 17:33:44 -0000

On 2010-11-29, at 2:32 AM, John C Klensin wrote:

[...]

>=20
>=20
>=20
> (5) Section 3.1(3): "Clients MUST ignore any parameters..." was
> fine for the experimental protocols.  At this point, we need to
> decide what the WG intends about extension models.  "MUST
> ignore" implies that any future extension must be optional,
> i.e., the system will work in a predictable way if parameters
> are supplied and ignored.  "MUST reject" (i.e., behave as if
> UTF8SMTPbis had not been supplied at all) means either that
> there will be no extensions or that they have to be assumed to
> be incompatible.  The latter is _much_ safer -- what does the WG
> intend.    Editorially, this bullet item would be much easier to
> follow if it made all statements about the server and then all
> statements about the client or vice versa: the current form is
> server-requirement / client-requirement / server-requirement.

Personal thought (and prediction) on this: extensions or parameters of =
extension usually act like branching of mechanism like AUTH and SORT =
(IMAP).  The only possible extension that I could think of now is =
branching of how headers being managed.  Body has it own extension =
already.  Encoding is restricted to UTF8 only.  If something =
"disruptive" like altering behaviour (like downgrade) or slightly =
incompatible SMTP-like proposed, it may results in a new keyword or a =
brand new protocol.  So personally I think extending UTF8SMTPbis in =
future is less likely.

=46rom client perspective, I think 'MUST ignore' is ok, but 'MUST =
reject' enforce new keyword on extension, which I think is better for =
long term.  Future drafts may always need a matrix table to help =
specifying "A & B & C =3D this; A & !B & C =3D that", which may be the =
case regardless extending on UTF8SMTPbis or not :)

>=20
> (6) As a specification that will published a year after IDNA2008
> was approved, this document should reflect IDNA2008 terminology,
> not an odd mix of IDNA2008 terms, IDNA2003 terms, and informal
> language.  Specifically (this may not be a complete list), ACE
> labels should not be discussed in Section 3.2 especially with a
> parenthetical "as specified" note pointing to IDNA Defs on its
> first use.  Instead, the term "A-label" should be used with an
> appropriate reference.  Unless there is a specific reason for
> doing so (in which case it better be explained to the WG), the
> text should not talk about domain names in UTF-8 strings but
> about U-labels.  It would be desirable to say, once, that any
> U-labels are required to be expressed in UTF-8, but that doesn't
> make them UTF-8 strings.   The first bullet in 3.3 should refer
> to a U-label as well, Section 3.6 should refer to A-labels, and
> so on.

+1
Using A-Label and U-label helps explaining in general.

[...]

Thanks
Joseph

>=20
>=20
>=20
>=20
>=20
>=20
> regards,
>   john
>=20
>=20
> (14)
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima


From klensin@jck.com  Mon Nov 29 16:00:43 2010
Return-Path: <klensin@jck.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 782A428C0DB for <ima@core3.amsl.com>; Mon, 29 Nov 2010 16:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599]
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 Y-k-ZAXVRdZj for <ima@core3.amsl.com>; Mon, 29 Nov 2010 16:00:42 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D4CC73A6C46 for <ima@ietf.org>; Mon, 29 Nov 2010 16:00:41 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PNDfL-0004M0-5R for ima@ietf.org; Mon, 29 Nov 2010 19:01:51 -0500
Date: Mon, 29 Nov 2010 19:01:50 -0500
From: John C Klensin <klensin@jck.com>
To: EAI WG <ima@ietf.org>
Message-ID: <C509C57956CD0D9895F48EAD@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [EAI] WG Co-chair review of 5335bis (headers extension)
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: Tue, 30 Nov 2010 00:00:43 -0000

Hi.

The same preliminary comments that apply to 5336bis apply to
this document as well.  It is in fairly poor shape in some areas
and needs a significant revision --which I hope we can see in
the next few days-- before it will be ready for handoff to the
IESG.  Those who promised to review it for the WG should be
thinking very carefully about why they did not notice these
points.

Like 5336bis, there are artifacts of in-transit downgrading in
this document and some fairly poor and confusing writing...
enough of both to create significant risk of getting bogged down
in IETF Last Call and/or the IESG.

As with the other review, I'm not going to repeat comments made
by others in the last few days except by accident.  I expect the
authors will reflect both those comments and these in a new
version.

(0) To reprise some other comments, the ABNF is "difficult" --
some errors and other things just confusingly structured.
Neither Alexey nor I should have to straighten that sort of
thing out: if the WG doesn't care enough, then we don't care
enough to have these things on the Standards Track.  Except as
the result of other comments, I have not provided additional
comments on the ABNF or references to it -- waiting for a clean
copy.

(1) Abstract.   The first two sentences are either somewhat
redundant or just hard to read.  I think they are ok
technically, but...

(2) Section 1.2 updates RFC 2045 twice, one in the first
paragraph and once in the second.  It cannot update 2045 in the
first paragraph and then "also update[s]" it in the second.

(3) Section 2, first paragraph, should be explicit that "common
names" as used here are the same as "display-names" in 5322.  It
would be even better to use the term display-name throughout and
indicate here that this is usually (but not required to be) the
user's common, ordinary, name.

(4) Section 2, next-to-last paragraph.  It is not clear what
this bit of narrative text is doing here, even though it is
"background".  Please refer to Framework to the extent possible;
if this material belongs in Framework but isn't there, it would
be better to open Framework than to have these apparently-random
comments in this document.  That comment may apply to other
parts of Section 2 as well, this particular paragraph is just
the most problematic.  If the revision of this document does not
remove that basic material, the references need to be checked
and the Note in Draft removed.

(5) Section 3, paragraph 1.  Again more confusing than it needs
to be.  If ASCII strings are UTF-8 strings and ASCII characters
are UTF-8 characters, then some of them cannot be _not_ UTF-8
characters.  And an implicit forward reference from a
terminology section to a piece of ABNF syntax is bad writing at
best.  If you have to invent a special term, do so ("non-ASCII
string" as a string that contains at least one non-ASCII
character is popular in other documents).

(6)  For Section 4.1 and the definition of uText in Section 4.3,
please review my comments about C0 and C1 control characters in
the 5336bis review.   FWIW, I'd personally prefer an informal
definition of UTF-8 and a pointer to 5234 and 3629 rather than
trying to dress this document up with extra ABNF.  Knowing that
UTF-8 can consist of one to four octets per character and how
the octets are structured is really of no use here and hence,
IMO, having those definitions here are not "reasons of
convenience".

(7) In Section 4.1, last paragraph, I think the "no NFKC"
explanation is the exceptional case, i.e., "except" should be
removed from "some names except in unusual...".   I think I
might have written that sentence, but it is still wrong.

(8) Section 4.2, first sentence, "to all subtypes" should be "to
any subtype".  The slash after "message/" should be called to
the attention of the RFC Editor for their preference.

(9) In Section 4.3 note that UTF8-xtra-char includes the C1
controls.  So uAtext excludes the C0 controls but not the C1
controls.  That just makes no sense.   The paragraph starting
"Note" at the end of that section largely repeats the content of
the earlier paragraph in the same section that starts "This
means...".  Please clean this up.

(10) Section 4.4: See my comments in the 5336bis review about
"addr-spec" and "mailbox".  The two documents should be
consistent to the degree possible and _very_ clear.

(11) The examples at the end of Section 4.4 do not conform to
the preferred use of "example" domains.  While we know what
notations like "ASCII@ASCII" mean within the WG, it needs
explanation here, ideally using the expected forms.  Some blank
lines between examples would make this material much more
readable.  And "bounce" should be changed to "rejected" unless
you really mean bounce and bounce exclusively (again, see
comments on 5336bis).

(12) Section 4.5 is hard to follow, especially in the first
paragraph.  If you are just repeating information from 5336bis,
please be explicit about that or, better yet, summarize and
reference.   Don't repeat basic facts about email (e.g.,
material that would be known to anyone who understands 5322)
without indicating that is what you are doing.  Otherwise, you
just confuse people about what is part of this spec (set of
extensions) and what is "normal".

(13) The first bullet under Section 4.6 either has me completely
confused or is just wrong.   If a message contains UTF-8
material in the outermost headers but all body parts use plain
ASCII headers, then it is not a message/global creature at all,
even insofar as message/global is a proper superset of
message/rfc822.  If that message is then embedded,
message/global would be required, but that is not what this
Section says.

(14) The rest of Section 4.6 contains several contradictory
statements.  The parenthetical note in paragraph 2 says "doesn't
recognize... MUST..."  (a MIME requirement not dependent on this
spec) but the "Interoperability considerations" portion of the
template says "will typically".  Under "Encoding considerations"
it says "8-bit or binary... where permitted" but "Restrictions
on usage" says "MUST... unless".   And, fwiw, "MUST unless" is
usually spelled "SHOULD" unless you have a strong reason for
that choice of language.   See earlier notes about contact
information: please use the WG, WG list, etc.

(15) In Section 5, the second and third paragraphs discuss the
same material and appear redundant.  Please merge them.  The
fourth paragraph talks about alternate addresses.  Has No One
reviewed this text in recent weeks?

regards,
    john



From Shawn.Steele@microsoft.com  Mon Nov 29 17:23:55 2010
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 954493A6C58 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 17:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.338
X-Spam-Level: 
X-Spam-Status: No, score=-10.338 tagged_above=-999 required=5 tests=[AWL=0.261, 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 IBOb3DaQT9lg for <ima@core3.amsl.com>; Mon, 29 Nov 2010 17:23:50 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id D04603A6C55 for <ima@ietf.org>; Mon, 29 Nov 2010 17:23:48 -0800 (PST)
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (157.54.80.67) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 29 Nov 2010 17:24:59 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.185]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Mon, 29 Nov 2010 17:24:59 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>, "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Thread-Topic: AD review of draft-ietf-eai-rfc5336bis-04.txt
Thread-Index: AcuQLJjUUKmCuAG8RBy5S3hbqSp5aw==
Date: Tue, 30 Nov 2010 01:24:58 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.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.73]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 01:23:56 -0000

My comments may be late:

> 2.  Overview of Operation

>   token "UTF8SMTPbis".  In order to provide information that may be
>   needed in downgrading, an optional alternate ASCII address may be
>   needed if an SMTP client attempts to transfer an internationalized
>   message and encounters a server that does not support this extension.

> I think the last sentence no longer applies and need to be deleted.

Seems fine to me, but I wonder if the idea is now to allow resending with a=
 different ASCII address using normal SMTP?  Probably not worth mentioning =
there.

>   A UTF8SMTPbis aware MUA/MSA sending to a legacy SMTP server [RFC5321]
>   and [RFC5322] MAY convert the ASCII@non-ASCII
> Native speakers: should the "the" be replaced with "a" here?

Addresse should be address, and "an" would work a bit better maybe than "th=
e".

>  Otherwise, surprising downgrades can happen
>   during temporary failures, which users might perceive as a serious
>   reliability issue.

> The last sentence: I think this needs to be reworded or deleted,
> as "surprising downgrades" are no longer an issue.

I'd be happy with "unexpected failures or disparities".  The core idea that=
 mismatched servers causing confusing behavior is probably worth pointing o=
ut.

- Shawn


From duerst@it.aoyama.ac.jp  Mon Nov 29 17:51:10 2010
Return-Path: <duerst@it.aoyama.ac.jp>
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 BF29B3A6C4F for <ima@core3.amsl.com>; Mon, 29 Nov 2010 17:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.392
X-Spam-Level: 
X-Spam-Status: No, score=-100.392 tagged_above=-999 required=5 tests=[AWL=-0.602, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 kbCLahlXi+Ue for <ima@core3.amsl.com>; Mon, 29 Nov 2010 17:51:10 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id C950D28C111 for <ima@ietf.org>; Mon, 29 Nov 2010 17:51:09 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id oAU1qFg2021709 for <ima@ietf.org>; Tue, 30 Nov 2010 10:52:15 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 1d4a_1fbc_74eff3fa_fc24_11df_85b4_001d096c566a; Tue, 30 Nov 2010 10:52:15 +0900
Received: from [IPv6:::1] ([133.2.210.1]:46964) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1494568> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 30 Nov 2010 10:52:13 +0900
Message-ID: <4CF458C9.4090000@it.aoyama.ac.jp>
Date: Tue, 30 Nov 2010 10:52:09 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <C509C57956CD0D9895F48EAD@PST.JCK.COM>
In-Reply-To: <C509C57956CD0D9895F48EAD@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] WG Co-chair review of 5335bis (headers extension)
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: Tue, 30 Nov 2010 01:51:10 -0000

On 2010/11/30 9:01, John C Klensin wrote:

> (5) Section 3, paragraph 1.  Again more confusing than it needs
> to be.  If ASCII strings are UTF-8 strings and ASCII characters
> are UTF-8 characters, then some of them cannot be _not_ UTF-8
> characters.  And an implicit forward reference from a
> terminology section to a piece of ABNF syntax is bad writing at
> best.  If you have to invent a special term, do so ("non-ASCII
> string" as a string that contains at least one non-ASCII
> character is popular in other documents).

"non-ASCII-only string" or "not-ASCII-only string" is slightly longer, 
but somewhat more precise.

Regards,    Martin.


-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From duerst@it.aoyama.ac.jp  Mon Nov 29 19:29:42 2010
Return-Path: <duerst@it.aoyama.ac.jp>
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 677FA28C126 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 19:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.358
X-Spam-Level: 
X-Spam-Status: No, score=-100.358 tagged_above=-999 required=5 tests=[AWL=-0.568, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 XAcq020fiaA4 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 19:29:41 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id EC83928C125 for <ima@ietf.org>; Mon, 29 Nov 2010 19:29:40 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id oAU3Ui1D030464 for <ima@ietf.org>; Tue, 30 Nov 2010 12:30:45 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 1d4c_9902_37022eba_fc32_11df_85b4_001d096c566a; Tue, 30 Nov 2010 12:30:44 +0900
Received: from [IPv6:::1] ([133.2.210.1]:35312) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S149463A> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 30 Nov 2010 12:30:43 +0900
Message-ID: <4CF46FDE.20909@it.aoyama.ac.jp>
Date: Tue, 30 Nov 2010 12:30:38 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <C509C57956CD0D9895F48EAD@PST.JCK.COM> <4CF458C9.4090000@it.aoyama.ac.jp>
In-Reply-To: <4CF458C9.4090000@it.aoyama.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] WG Co-chair review of 5335bis (headers extension)
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: Tue, 30 Nov 2010 03:29:42 -0000

On 2010/11/30 10:52, "Martin J. Dürst" wrote:
> On 2010/11/30 9:01, John C Klensin wrote:
>
>> (5) Section 3, paragraph 1. Again more confusing than it needs
>> to be. If ASCII strings are UTF-8 strings and ASCII characters
>> are UTF-8 characters, then some of them cannot be _not_ UTF-8
>> characters. And an implicit forward reference from a
>> terminology section to a piece of ABNF syntax is bad writing at
>> best. If you have to invent a special term, do so ("non-ASCII
>> string" as a string that contains at least one non-ASCII
>> character is popular in other documents).
>
> "non-ASCII-only string" or "not-ASCII-only string" is slightly longer,
> but somewhat more precise.

Reconsidering, I think it's important to write these as "non ASCII-only 
string" or "not ASCII-only string". The reverse, "non-ASCII only string" 
or "not-ASCII only string" is not what is meant, and having both hyphens 
is confusing.

Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From klensin@jck.com  Mon Nov 29 20:13:29 2010
Return-Path: <klensin@jck.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 7086228C128 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 20:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599]
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 PxrU6ZtTgAkP for <ima@core3.amsl.com>; Mon, 29 Nov 2010 20:13:28 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 5A85E28C125 for <ima@ietf.org>; Mon, 29 Nov 2010 20:13:27 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PNHbw-000CIb-OX; Mon, 29 Nov 2010 23:14:36 -0500
Date: Mon, 29 Nov 2010 23:14:35 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, "Alexey Melnikov	(alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Message-ID: <970B28762AFDE11B63BD1412@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 04:13:29 -0000

--On Tuesday, November 30, 2010 01:24 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> My comments may be late:
> 
>> 2.  Overview of Operation
> 
>>   token "UTF8SMTPbis".  In order to provide information that
>>   may be needed in downgrading, an optional alternate ASCII
>>   address may be needed if an SMTP client attempts to
>>   transfer an internationalized message and encounters a
>>   server that does not support this extension.
> 
>> I think the last sentence no longer applies and need to be
>> deleted.
> 
> Seems fine to me, but I wonder if the idea is now to allow
> resending with a different ASCII address using normal SMTP?
> Probably not worth mentioning there.

Likely worth mentioning in one of the "advice" documents.
Doesn't belong here, IMO, unless we intend to require it.

>...
>>  Otherwise, surprising downgrades can happen
>>   during temporary failures, which users might perceive as a
>>   serious reliability issue.
> 
>> The last sentence: I think this needs to be reworded or
>> deleted, as "surprising downgrades" are no longer an issue.
> 
> I'd be happy with "unexpected failures or disparities".  The
> core idea that mismatched servers causing confusing behavior
> is probably worth pointing out.

See my earlier comments.   "Unexpected rejections" is closest in
tone to the original, although certainly not the only possible
text.  The real question is how far one wants to go in
explaining the nature of the problem rather than just advising
against getting into the situation where different servers have
different capabilities.  Should you decide that more explanation
is in order, I won't object as long as the explanation is
completely clear, but that is a personal opinion and others in
the WG may disagree.

I would, however, like to see an updated version that reflects
these comments well before the end of this week.

    john



From Shawn.Steele@microsoft.com  Mon Nov 29 23:02:13 2010
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 F18BD3A6C68 for <ima@core3.amsl.com>; Mon, 29 Nov 2010 23:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.37
X-Spam-Level: 
X-Spam-Status: No, score=-10.37 tagged_above=-999 required=5 tests=[AWL=0.229,  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 RmBwf-uxkyIP for <ima@core3.amsl.com>; Mon, 29 Nov 2010 23:02:11 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id A41AE3A6B39 for <ima@ietf.org>; Mon, 29 Nov 2010 23:02:11 -0800 (PST)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 29 Nov 2010 23:03:22 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.185]) by TK5EX14HUBC105.redmond.corp.microsoft.com ([157.54.80.48]) with mapi id 14.01.0255.003; Mon, 29 Nov 2010 23:03:22 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, "ima@ietf.org" <ima@ietf.org>, "Alexey Melnikov	(alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Thread-Topic: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
Thread-Index: AcuQLJjUUKmCuAG8RBy5S3hbqSp5awAW43qA//+nNDE=
Date: Tue, 30 Nov 2010 07:03:21 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10BC9D54@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com>, <970B28762AFDE11B63BD1412@PST.JCK.COM>
In-Reply-To: <970B28762AFDE11B63BD1412@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 07:02:13 -0000

> > Seems fine to me, but I wonder if the idea is now to allow
> > resending with a different ASCII address using normal SMTP?
> > Probably not worth mentioning there.

> Likely worth mentioning in one of the "advice" documents.
> Doesn't belong here, IMO, unless we intend to require it.

Fine by me :)

> > I'd be happy with "unexpected failures or disparities".  The
> > core idea that mismatched servers causing confusing behavior
> > is probably worth pointing out.

> See my earlier comments.   "Unexpected rejections" is closest in
> tone to the original, although certainly not the only possible
> text... I won't object as long as the explanation is
> completely clear, but that is a personal opinion and others in
> the WG may disagree.

Unexpected rejections is fine to me.  I was thinking end-to-end where a use=
r might send to an EAI address, it works, then send to EAI & it fails, then=
 resend to ASCII.  Or the sender may fail to send and their client falls ba=
ck to the sender's ASCII address.  It seems like there are a lot of possibl=
e ways that mismatched capabilities could differ, so I favor vague "this is=
 bad" over "this is bad because of A, B, C, C1,... Z :)"

- Shawn=

From klensin@jck.com  Tue Nov 30 01:45:17 2010
Return-Path: <klensin@jck.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 1078D3A6AEB for <ima@core3.amsl.com>; Tue, 30 Nov 2010 01:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599]
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 5z8QfHjd+2pG for <ima@core3.amsl.com>; Tue, 30 Nov 2010 01:45:16 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 0852D3A6927 for <ima@ietf.org>; Tue, 30 Nov 2010 01:45:16 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PNMn4-000Lwi-Ah; Tue, 30 Nov 2010 04:46:26 -0500
Date: Tue, 30 Nov 2010 04:46:25 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, "Alexey Melnikov	(alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Message-ID: <5C9960FD73D96FB2A025A56B@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10BC9D54@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com> ,<970B28762AFDE11B63BD1412@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A10BC9D54@TK5EX14MBXC137.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 09:45:17 -0000

--On Tuesday, November 30, 2010 07:03 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>...
>> See my earlier comments.   "Unexpected rejections" is closest
>> in tone to the original, although certainly not the only
>> possible text... I won't object as long as the explanation is
>> completely clear, but that is a personal opinion and others in
>> the WG may disagree.
> 
> Unexpected rejections is fine to me.  I was thinking
> end-to-end where a user might send to an EAI address, it
> works, then send to EAI & it fails, then resend to ASCII.  Or
> the sender may fail to send and their client falls back to the
> sender's ASCII address.  It seems like there are a lot of
> possible ways that mismatched capabilities could differ, so I
> favor vague "this is bad" over "this is bad because of A, B,
> C, C1,... Z :)"

Our reasoning about that is very similar, actually.  Hence my
inclination to say "unexpected rejections" rather than something
about downgrade behavior and then move on.

   john


From Shawn.Steele@microsoft.com  Tue Nov 30 07:55:32 2010
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 F17AB28C14B for <ima@core3.amsl.com>; Tue, 30 Nov 2010 07:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.396
X-Spam-Level: 
X-Spam-Status: No, score=-10.396 tagged_above=-999 required=5 tests=[AWL=0.203, 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 dm-w2jAg46CW for <ima@core3.amsl.com>; Tue, 30 Nov 2010 07:55:31 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id C1AEA28C147 for <ima@ietf.org>; Tue, 30 Nov 2010 07:55:31 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 30 Nov 2010 07:56:43 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.185]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0255.003; Tue, 30 Nov 2010 07:56:43 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, "ima@ietf.org" <ima@ietf.org>, "Alexey Melnikov	(alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Thread-Topic: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
Thread-Index: AcuQLJjUUKmCuAG8RBy5S3hbqSp5awAW43qA//+nNDGAALWCgP//4Szg
Date: Tue, 30 Nov 2010 15:56:42 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10BCA816@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com> ,<970B28762AFDE11B63BD1412@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A10BC9D54@TK5EX14MBXC137.redmond.corp.microsoft.com>, <5C9960FD73D96FB2A025A56B@PST.JCK.COM>
In-Reply-To: <5C9960FD73D96FB2A025A56B@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 15:55:33 -0000

SSdkIHRob3VnaHQgbXkgcHJldmlvdXMgc3VnZ2VzdGlvbiBhdm9pZGVkIHRoZSB3b3JkICJkb3du
Z3JhZGUiIDopDQoNCi1TaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg76Oi76Oj76OX76OU76OZDQpodHRw
Oi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGUNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQpGcm9tOiBKb2huIEMgS2xlbnNpbiBba2xlbnNpbkBqY2suY29tXQ0K
U2VudDogVHVlc2RheSwgTm92ZW1iZXIgMzAsIDIwMTAgMTo0NiBBTQ0KVG86IFNoYXduIFN0ZWVs
ZTsgaW1hQGlldGYub3JnOyBBbGV4ZXkgTWVsbmlrb3YgKGFsZXhleS5tZWxuaWtvdkBpc29kZS5j
b20pDQpDYzogWUFPIEppYW5rYW5nDQpTdWJqZWN0OiBSRTogW0VBSV0gQUQgcmV2aWV3IG9mIGRy
YWZ0LWlldGYtZWFpLXJmYzUzMzZiaXMtMDQudHh0DQoNCi0tT24gVHVlc2RheSwgTm92ZW1iZXIg
MzAsIDIwMTAgMDc6MDMgKzAwMDAgU2hhd24gU3RlZWxlDQo8U2hhd24uU3RlZWxlQG1pY3Jvc29m
dC5jb20+IHdyb3RlOg0KDQo+Li4uDQo+PiBTZWUgbXkgZWFybGllciBjb21tZW50cy4gICAiVW5l
eHBlY3RlZCByZWplY3Rpb25zIiBpcyBjbG9zZXN0DQo+PiBpbiB0b25lIHRvIHRoZSBvcmlnaW5h
bCwgYWx0aG91Z2ggY2VydGFpbmx5IG5vdCB0aGUgb25seQ0KPj4gcG9zc2libGUgdGV4dC4uLiBJ
IHdvbid0IG9iamVjdCBhcyBsb25nIGFzIHRoZSBleHBsYW5hdGlvbiBpcw0KPj4gY29tcGxldGVs
eSBjbGVhciwgYnV0IHRoYXQgaXMgYSBwZXJzb25hbCBvcGluaW9uIGFuZCBvdGhlcnMgaW4NCj4+
IHRoZSBXRyBtYXkgZGlzYWdyZWUuDQo+DQo+IFVuZXhwZWN0ZWQgcmVqZWN0aW9ucyBpcyBmaW5l
IHRvIG1lLiAgSSB3YXMgdGhpbmtpbmcNCj4gZW5kLXRvLWVuZCB3aGVyZSBhIHVzZXIgbWlnaHQg
c2VuZCB0byBhbiBFQUkgYWRkcmVzcywgaXQNCj4gd29ya3MsIHRoZW4gc2VuZCB0byBFQUkgJiBp
dCBmYWlscywgdGhlbiByZXNlbmQgdG8gQVNDSUkuICBPcg0KPiB0aGUgc2VuZGVyIG1heSBmYWls
IHRvIHNlbmQgYW5kIHRoZWlyIGNsaWVudCBmYWxscyBiYWNrIHRvIHRoZQ0KPiBzZW5kZXIncyBB
U0NJSSBhZGRyZXNzLiAgSXQgc2VlbXMgbGlrZSB0aGVyZSBhcmUgYSBsb3Qgb2YNCj4gcG9zc2li
bGUgd2F5cyB0aGF0IG1pc21hdGNoZWQgY2FwYWJpbGl0aWVzIGNvdWxkIGRpZmZlciwgc28gSQ0K
PiBmYXZvciB2YWd1ZSAidGhpcyBpcyBiYWQiIG92ZXIgInRoaXMgaXMgYmFkIGJlY2F1c2Ugb2Yg
QSwgQiwNCj4gQywgQzEsLi4uIFogOikiDQoNCk91ciByZWFzb25pbmcgYWJvdXQgdGhhdCBpcyB2
ZXJ5IHNpbWlsYXIsIGFjdHVhbGx5LiAgSGVuY2UgbXkNCmluY2xpbmF0aW9uIHRvIHNheSAidW5l
eHBlY3RlZCByZWplY3Rpb25zIiByYXRoZXIgdGhhbiBzb21ldGhpbmcNCmFib3V0IGRvd25ncmFk
ZSBiZWhhdmlvciBhbmQgdGhlbiBtb3ZlIG9uLg0KDQogICBqb2hu

From klensin@jck.com  Tue Nov 30 13:06:09 2010
Return-Path: <klensin@jck.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 E92CD3A6C16 for <ima@core3.amsl.com>; Tue, 30 Nov 2010 13:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599]
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 l2f3tJfi+XtW for <ima@core3.amsl.com>; Tue, 30 Nov 2010 13:06:09 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D746D3A6BDA for <ima@ietf.org>; Tue, 30 Nov 2010 13:06:08 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PNXQ0-000IHg-8t; Tue, 30 Nov 2010 16:07:20 -0500
Date: Tue, 30 Nov 2010 16:07:19 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, "Alexey Melnikov	(alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>
Message-ID: <3F78C322B22858284DF72700@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10BCA816@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10BC8EE4@TK5EX14MBXC137.redmond.corp.microsoft.com> ,<970B28762AFDE11B63BD1412@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A10BC9D54@TK5EX14MBXC137.redmond.corp.microsoft.com> ,<5C9960FD73D96FB2A025A56B@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A10BCA816@TK5EX14MBXC137.redmond.corp.microsoft.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
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: Tue, 30 Nov 2010 21:06:10 -0000

--On Tuesday, November 30, 2010 15:56 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> I'd thought my previous suggestion avoided the word
> "downgrade" :)

It did.  Mostly just a matter of taste.  At this point, I'm
looking forward to seeing a pair of new drafts.  If those are
not going to be up in the next 24 hours or less, I'd appreciate
updated statements from the various authors about when we can
expect them.

   john

