
From Internet-Drafts@ietf.org  Thu Dec  2 00:30: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 0EE643A68C0; Thu,  2 Dec 2010 00:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.160, 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 jmLFWtOQ9YXz; Thu,  2 Dec 2010 00:30:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C7D23A68A4; Thu,  2 Dec 2010 00:30:02 -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
X-IETF-IDTracker: 3.09
Message-ID: <20101202083002.25979.7144.idtracker@localhost>
Date: Thu, 02 Dec 2010 00:30:02 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5336bis-05.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: Thu, 02 Dec 2010 08:30: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           : SMTP Extension for Internationalized Email Address
	Author(s)       : J. Yao, W. MAO
	Filename        : draft-ietf-eai-rfc5336bis-05.txt
	Pages           : 19
	Date            : 2010-12-02

This document specifies an SMTP extension for transport and delivery
of email messages with internationalized email addresses or header
information.  This document updates some syntax rules defined in RFC
5321 and RFC 5322.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5336bis-05.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-rfc5336bis-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From yaojk@cnnic.cn  Thu Dec  2 00:55:10 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 41A903A6816 for <ima@core3.amsl.com>; Thu,  2 Dec 2010 00:55:10 -0800 (PST)
X-Quarantine-ID: <Uw-INHTJUiOC>
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.188
X-Spam-Level: 
X-Spam-Status: No, score=-99.188 tagged_above=-999 required=5 tests=[AWL=0.855, 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 Uw-INHTJUiOC for <ima@core3.amsl.com>; Thu,  2 Dec 2010 00:55:09 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id AB4DA3A68C6 for <ima@ietf.org>; Thu,  2 Dec 2010 00:55:08 -0800 (PST)
Received: (eyou send program); Thu, 02 Dec 2010 16:56:23 +0800
Message-ID: <491280183.27938@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, 02 Dec 2010 16:56:23 +0800
Message-ID: <C353F082A9C647F785651EA029AAEB73@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <4CF0307D.9090900@isode.com> <490863556.14931@cnnic.cn>
Date: Thu, 2 Dec 2010 16:54:22 +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: Thu, 02 Dec 2010 08:55:10 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsZXhleSBNZWxuaWtvdiIg
PGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20+DQpUbzogIkVBSSBXRyIgPGltYUBpZXRmLm9yZz4N
ClNlbnQ6IFNhdHVyZGF5LCBOb3ZlbWJlciAyNywgMjAxMCA5OjEwIFBNDQpTdWJqZWN0OiBSZTog
W0VBSV0gQUQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtZWFpLXJmYzUzMzZiaXMtMDQudHh0DQoNCg0K
PiBBbGV4ZXkgTWVsbmlrb3Ygd3JvdGU6DQo+IA0KPj4gNC4gIElBTkEgQ29uc2lkZXJhdGlvbnMN
Cj4+DQo+PiAgICstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
LS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KPj4gICB8IFdJVEggcHJvdG9jb2wgfCBEZXNjcmlwdGlv
biAgICAgICAgICAgICAgICAgfCBSZWZlcmVuY2UgICAgICAgICAgIHwNCj4+ICAgfCB0eXBlcyAg
ICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICB8DQo+PiAgICstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
LS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KPj4gICB8IFVURjhTTVRQYmlzICAgfCBVVEY4U01UUGJp
cyB3aXRoIFNlcnZpY2UgICAgfCBbUkZDWFhYWF0gICAgICAgICAgIHwNCj4+ICAgfCAgICAgICAg
ICAgICAgIHwgRXh0ZW5zaW9ucyAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICB8DQo+PiAgIHwgVVRGOFNNVFBiaXNBICB8IFVURjhTTVRQYmlzIHdpdGggU01UUCBBVVRIICB8
IFtSRkM0OTU0XSBbUkZDWFhYWF0gfA0KPj4gICB8IFVURjhTTVRQYmlzUyAgfCBVVEY4U01UUGJp
cyB3aXRoIFNUQVJUVExTICAgfCBbUkZDMzIwN10gW1JGQ1hYWFhdIHwNCj4+ICAgfCBVVEY4U01U
UGJpc1NBIHwgVVRGOFNNVFBiaXMgd2l0aCBib3RoICAgICAgIHwgW1JGQzMyMDddIFtSRkM0OTU0
XSB8DQo+PiAgIHwgICAgICAgICAgICAgICB8IFNUQVJUVExTIGFuZCBTTVRQIEFVVEggICAgICB8
IFtSRkNYWFhYXSAgICAgICAgICAgfA0KPj4gICArLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCj4+DQo+PiBEbyB3ZSBy
ZWFsbHkgbmVlZCB0byBjaGFuZ2UgdGhlIFdJVEggcHJvdG9jb2wgdHlwZXM/DQo+IA0KPiBJIHJl
bWVtYmVyZWQgb25lIG1vcmUgdGhpbmc6IGlmIG90aGVyIExNVFAgcmVsYXRlZCBjaGFuZ2VzIGFy
ZSBkb25lLCANCj4gdGhpcyBzZWN0aW9uIHNob3VsZCBhbHNvIHJlZ2lzdGVyIHZhbHVlcyBmb3Ig
TE1UUC4gRS5nLiANCj4gVVRGOExNVFAvVVRGOExNVFBBL1VURjhMTVRQUy9VVEY4TE1UUFNBLg0K
PiANCg0KSSBzdGlsbCBrZWVwIHRoaXMgcGFydCB1bmNoYW5nZWQuDQoNCmlmIHdlIHJlYWxseSBu
ZWVkIHRvIGNoYW5nZSBpdCB0byBzdXBwb3J0IGxtdHAsIHdlIG1heSB1cGRhZSBpdCBpbiB0aGUg
bmV4dCB2ZXJzaW9uLg0KDQoNCmJlbG93IGlzIG15IHBlcnNvbmFsIGNvbW1lbnRzOiANCg0KDQpp
ZiB3ZSByZWdpc3RlciB0aGUgd2l0aCBwcm90b2NvbCB0eXBlIGZvciBVVEY4TE1UUC9VVEY4TE1U
UEEvVVRGOExNVFBTL1VURjhMTVRQU0EsDQoNCndlIG11c3QgcmVnaXN0ZXIgIFVURjhMTVRQIGZp
cnN0IGFzIHRoZSBlaGxvIGtleXdvcmQsIGJ1dCB3ZSBoYXZlIGFscmVhZHkgc2FpZCB0aGF0IFVU
RjhTTVRQYmlzIGFwcGx5IHRvIExNVFAgdG9vLg0KZm9yIHRoZSBVVEY4TE1UUEEvVVRGOExNVFBT
L1VURjhMTVRQU0EsIEkgaGF2ZSBjaGVja2VkIHRoZSByZWxhdGVkIHJmYywgYnV0IG5vdCBmaW5k
IHRoZSBwcm9wZXIgcmZjIGZvciB0aGVzZSBrZXl3b3Jkcy4NCg0KZG8gdGhlIHNtdHAgcmVsYXRl
ZCByZmMgKCBbUkZDMzIwN10gIFtSRkMzMjA3XSBbUkZDNDk1NF0pIGFwcGx5IHRvIGxtdHAgdG9v
Pw0KDQppZiB0aGF0IGlzIHRydWUsIHdlIG1heSBhZGQgb25lIHNlbnRlbmNlIHN1Y2ggYXMgInRo
ZSAgIldJVEggcHJvdG9jb2wgdHlwZXMiIHJlZ2lzdGVyZWQgIGFyZSAgYXBwbGllZCB0byBMTVRQ
IHRvbyIgaW4gdGhlIGlhbmEgY29uc2lkZXJhdGlvbi4NCg0Kb3IgcmVnaXN0ZXIgbmV3IG9uZSBm
b3IgTE1UUC4NCg0KDQpKaWFua2FuZyBZYW8NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gSU1BIG1haWxpbmcgbGlzdA0KPiBJTUFAaWV0Zi5vcmcN
Cj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbWE=


From alexey.melnikov@isode.com  Thu Dec  2 04:57:11 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 7FEE128C10A for <ima@core3.amsl.com>; Thu,  2 Dec 2010 04:57:11 -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 BqiO4q5TBR67 for <ima@core3.amsl.com>; Thu,  2 Dec 2010 04:57:10 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 3452728C0F5 for <ima@ietf.org>; Thu,  2 Dec 2010 04:57:10 -0800 (PST)
Received: from [172.16.2.200] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPeX7gAbxV-Q@rufus.isode.com>; Thu, 2 Dec 2010 12:58:24 +0000
Message-ID: <4CF797B7.8080207@isode.com>
Date: Thu, 02 Dec 2010 12:57:28 +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>
References: <4CF0307D.9090900@isode.com> <490863556.14931@cnnic.cn> <491280183.27938@cnnic.cn>
In-Reply-To: <491280183.27938@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: EAI WG <ima@ietf.org>
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: Thu, 02 Dec 2010 12:57:11 -0000

Jiankang YAO wrote:

>----- Original Message ----- 
>From: "Alexey Melnikov" <alexey.melnikov@isode.com>
>To: "EAI WG" <ima@ietf.org>
>Sent: Saturday, November 27, 2010 9:10 PM
>Subject: Re: [EAI] AD review of draft-ietf-eai-rfc5336bis-04.txt
>
>
>  
>
>>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.
>>    
>>
>
>I still keep this part unchanged.
>
>
>if we really need to change it to support lmtp, we may updae it in the next version.
>  
>
Yes, we need to add 4 LMTP related entries, as LMTP is a different 
protocol from SMTP.

I think we also agreed to use "UTF8SMTP" instead of "UTF8SMTPbis" above, 
etc.?

>below is my personal comments: 
>
>
>if we register the with protocol type for UTF8LMTP/UTF8LMTPA/UTF8LMTPS/UTF8LMTPSA,
>
>we must register  UTF8LMTP first as the ehlo keyword, but we have already said that UTF8SMTPbis apply to LMTP too.
>for the UTF8LMTPA/UTF8LMTPS/UTF8LMTPSA, I have checked the related rfc, but not find the proper rfc for these keywords.
>
There is no need to register a new SMTP keywords here, as LMTP is not an 
extension to SMTP, it is an independent protocol.

>do the smtp related rfc ( [RFC3207]  [RFC3207] [RFC4954]) apply to lmtp too?
>
Yes, both of them can be used in LMTP.

>if that is true, we may add one sentence such as "the  "WITH protocol types" registered  are  applied to LMTP too" in the iana consideration.
>
>or register new one for LMTP.
>
I think it would be track 5336bis-capable SMTP servers separately from 
5336bis-capable LMTP servers, that is why there are separate WITH 
keywords for them.


From alexey.melnikov@isode.com  Thu Dec  2 05:23:25 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 5EE623A6944 for <ima@core3.amsl.com>; Thu,  2 Dec 2010 05:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 514l5sBx3RKF for <ima@core3.amsl.com>; Thu,  2 Dec 2010 05:23:23 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 84A6D28C0E7 for <ima@ietf.org>; Thu,  2 Dec 2010 05:22:55 -0800 (PST)
Received: from [172.16.2.200] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPed-QAbxaEF@rufus.isode.com>; Thu, 2 Dec 2010 13:24:10 +0000
Message-ID: <4CF79DC6.3080109@isode.com>
Date: Thu, 02 Dec 2010 13:23:18 +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: <4CF0307D.9090900@isode.com> <490863556.14931@cnnic.cn> <491280183.27938@cnnic.cn>
In-Reply-To: <491280183.27938@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] draft-ietf-eai-rfc5336bis-05.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: Thu, 02 Dec 2010 13:23:25 -0000

This version addressed most of my concerns and is a big improvement. 
Thank you. Outstanding changes are:

1) Change "UTF8SMTPbis" WITH keywords to "UTF8SMTP", etc.
2) Add LMTP specific WITH keywords
3) I think we need to collapse X.6.8 and Y.6.8 into 1 IANA registration 
(with all allowed status codes listed in 1 place). I.e.:

      Code:               X.6.8
      Sample Text:        UTF-8 string reply is required,
                          but not permitted by the client
      Associated basic status code:  553, 550, 252
      Description:        This indicates that 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.
 ...

We also need to decide on what to do with X.6.10 - deprecate it in the 
registry?

Best Regards,
Alexey

P.S. I still need to check the updated ABNF, I will do this later.


From Internet-Drafts@ietf.org  Thu Dec  2 11: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 15D5F28C112; Thu,  2 Dec 2010 11:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 EcMaXlxC2l8T; Thu,  2 Dec 2010 11:00:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6936A28C12A; Thu,  2 Dec 2010 11:00:02 -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
X-IETF-IDTracker: 3.09
Message-ID: <20101202190002.20459.22367.idtracker@localhost>
Date: Thu, 02 Dec 2010 11:00:02 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5335bis-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: Thu, 02 Dec 2010 19: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           : Internationalized Email Headers
	Author(s)       :  . Yang, S. Steele
	Filename        : draft-ietf-eai-rfc5335bis-04.txt
	Pages           : 15
	Date            : 2010-12-02

Full internationalization of electronic mail requires not only the
capabilities to transmit non-ASCII content, to encode selected
information in specific header fields, and to use non-ASCII
characters in envelope addresses.  It also requires being able to
express those addresses and the information based on them in mail
header fields.  This document specifies a variant of Internet mail
that permits the use of Unicode encoded in UTF-8, rather than ASCII,
as the base form for Internet email header field.  This form is
permitted in transmission only if authorized by an SMTP extension, as
specified in an associated specification.  This specification updates
Section 6.4 of [RFC2045] to conform with the requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5335bis-04.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-rfc5335bis-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Internet-Drafts@ietf.org  Fri Dec  3 00:15:12 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 492D528C1A5; Fri,  3 Dec 2010 00:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.438
X-Spam-Level: 
X-Spam-Status: No, score=-102.438 tagged_above=-999 required=5 tests=[AWL=0.161, 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 7B159CdvkKLE; Fri,  3 Dec 2010 00:15:06 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72EEC28C191; Fri,  3 Dec 2010 00:15:02 -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
X-IETF-IDTracker: 3.09
Message-ID: <20101203081502.12095.8027.idtracker@localhost>
Date: Fri, 03 Dec 2010 00:15:02 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5336bis-06.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, 03 Dec 2010 08:15:15 -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           : SMTP Extension for Internationalized Email Address
	Author(s)       : J. Yao, W. MAO
	Filename        : draft-ietf-eai-rfc5336bis-06.txt
	Pages           : 19
	Date            : 2010-12-03

This document specifies an SMTP extension for transport and delivery
of email messages with internationalized email addresses or header
information.  This document updates some syntax rules defined in RFC
5321 and RFC 5322.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5336bis-06.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-rfc5336bis-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From yaojk@cnnic.cn  Fri Dec  3 00:16:14 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 0B1E828C107 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 00:16:14 -0800 (PST)
X-Quarantine-ID: <751eziPnQsUB>
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.266
X-Spam-Level: 
X-Spam-Status: No, score=-99.266 tagged_above=-999 required=5 tests=[AWL=0.777, 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 751eziPnQsUB for <ima@core3.amsl.com>; Fri,  3 Dec 2010 00:16:13 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id E4CE228C19B for <ima@ietf.org>; Fri,  3 Dec 2010 00:16:11 -0800 (PST)
Received: (eyou send program); Fri, 03 Dec 2010 16:17:28 +0800
Message-ID: <491364248.30201@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 03 Dec 2010 16:17:28 +0800
Message-ID: <F3C605A2AB7E4C13888EFF901023AE47@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "EAI WG" <ima@ietf.org>
References: <4CF0307D.9090900@isode.com> <490863556.14931@cnnic.cn> <491280183.27938@cnnic.cn> <491296256.28928@cnnic.cn>
Date: Fri, 3 Dec 2010 16:15: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] draft-ietf-eai-rfc5336bis-05.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, 03 Dec 2010 08:16:14 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsZXhleSBNZWxuaWtvdiIg
PGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20+DQpUbzogIkppYW5rYW5nIFlBTyIgPHlhb2prQGNu
bmljLmNuPjsgIkVBSSBXRyIgPGltYUBpZXRmLm9yZz4NClNlbnQ6IFRodXJzZGF5LCBEZWNlbWJl
ciAwMiwgMjAxMCA5OjIzIFBNDQpTdWJqZWN0OiBkcmFmdC1pZXRmLWVhaS1yZmM1MzM2YmlzLTA1
LnR4dA0KDQoNCj4gVGhpcyB2ZXJzaW9uIGFkZHJlc3NlZCBtb3N0IG9mIG15IGNvbmNlcm5zIGFu
ZCBpcyBhIGJpZyBpbXByb3ZlbWVudC4gDQo+IFRoYW5rIHlvdS4gT3V0c3RhbmRpbmcgY2hhbmdl
cyBhcmU6DQo+IA0KPiAxKSBDaGFuZ2UgIlVURjhTTVRQYmlzIiBXSVRIIGtleXdvcmRzIHRvICJV
VEY4U01UUCIsIGV0Yy4NCj4gMikgQWRkIExNVFAgc3BlY2lmaWMgV0lUSCBrZXl3b3Jkcw0KDQoN
CnVwZGF0ZWQuIA0KDQoNCiAgICstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KICAgfCBXSVRIIHByb3RvY29sIHwgRGVz
Y3JpcHRpb24gICAgICAgICAgICAgICAgfCBSZWZlcmVuY2UgICAgICAgICAgICB8DQogICB8IHR5
cGVzICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAg
ICAgICAgIHwNCiAgICstLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KICAgfCBVVEY4U01UUCAgICAgIHwgVVRGOFNNVFAg
d2l0aCBTZXJ2aWNlICAgICAgfCBbUkZDWFhYWF0gICAgICAgICAgICB8DQogICB8ICAgICAgICAg
ICAgICAgfCBFeHRlbnNpb25zICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAg
IHwNCiAgIHwgVVRGOFNNVFBBICAgICB8IFVURjhTTVRQIHdpdGggU01UUCBBVVRIICAgIHwgW1JG
QzQ5NTRdIFtSRkNYWFhYXSAgfA0KICAgfCBVVEY4U01UUFMgICAgIHwgVVRGOFNNVFAgd2l0aCBT
VEFSVFRMUyAgICAgfCBbUkZDMzIwN10gW1JGQ1hYWFhdICB8DQogICB8IFVURjhTTVRQU0EgICAg
fCBVVEY4U01UUCB3aXRoIGJvdGggICAgICAgICB8IFtSRkMzMjA3XSBbUkZDNDk1NF0gIHwNCiAg
IHwgICAgICAgICAgICAgICB8IFNUQVJUVExTIGFuZCBTTVRQIEFVVEggICAgIHwgW1JGQ1hYWFhd
ICAgICAgICAgICAgfA0KICAgfCBVVEY4TE1UUCAgICAgIHwgVVRGOExNVFAgd2l0aCBTZXJ2aWNl
ICAgICAgfCBbUkZDWFhYWF0gICAgICAgICAgICB8DQogICB8ICAgICAgICAgICAgICAgfCBFeHRl
bnNpb25zICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgIHwNCiAgIHwgVVRG
OExNVFBBICAgICB8IFVURjhMTVRQIHdpdGggTE1UUCBBVVRIICAgIHwgW1JGQzQ5NTRdIFtSRkNY
WFhYXSAgfA0KICAgfCBVVEY4TE1UUFMgICAgIHwgVVRGOExNVFAgd2l0aCBTVEFSVFRMUyAgICAg
fCBbUkZDMzIwN10gW1JGQ1hYWFhdICB8DQogICB8IFVURjhMTVRQU0EgICAgfCBVVEY4TE1UUCB3
aXRoIGJvdGggICAgICAgICB8IFtSRkMzMjA3XSBbUkZDNDk1NF0gIHwNCiAgIHwgICAgICAgICAg
ICAgICB8IFNUQVJUVExTIGFuZCBMTVRQIEFVVEggICAgIHwgW1JGQ1hYWFhdICAgICAgICAgICAg
fA0KICAgKy0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0rDQoNCg0KPiAzKSBJIHRoaW5rIHdlIG5lZWQgdG8gY29sbGFwc2Ug
WC42LjggYW5kIFkuNi44IGludG8gMSBJQU5BIHJlZ2lzdHJhdGlvbiANCj4gKHdpdGggYWxsIGFs
bG93ZWQgc3RhdHVzIGNvZGVzIGxpc3RlZCBpbiAxIHBsYWNlKS4gSS5lLjoNCj4gDQo+ICAgICAg
Q29kZTogICAgICAgICAgICAgICBYLjYuOA0KPiAgICAgIFNhbXBsZSBUZXh0OiAgICAgICAgVVRG
LTggc3RyaW5nIHJlcGx5IGlzIHJlcXVpcmVkLA0KPiAgICAgICAgICAgICAgICAgICAgICAgICAg
YnV0IG5vdCBwZXJtaXR0ZWQgYnkgdGhlIGNsaWVudA0KPiAgICAgIEFzc29jaWF0ZWQgYmFzaWMg
c3RhdHVzIGNvZGU6ICA1NTMsIDU1MCwgMjUyDQo+ICAgICAgRGVzY3JpcHRpb246ICAgICAgICBU
aGlzIGluZGljYXRlcyB0aGF0IGEgcmVwbHkgY29udGFpbmluZyBhIFVURi04DQo+ICAgICAgICAg
ICAgICAgICAgICAgICAgICBzdHJpbmcgaXMgcmVxdWlyZWQgdG8gc2hvdyB0aGUgbWFpbGJveCBu
YW1lLA0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgYnV0IHRoYXQgZm9ybSBvZiByZXNwb25z
ZSBpcyBub3QNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIHBlcm1pdHRlZCBieSB0aGUgY2xp
ZW50Lg0KPiAuLi4NCj4gDQoNCnVwZGF0ZWQuDQoNCj4gV2UgYWxzbyBuZWVkIHRvIGRlY2lkZSBv
biB3aGF0IHRvIGRvIHdpdGggWC42LjEwIC0gZGVwcmVjYXRlIGl0IGluIHRoZSANCj4gcmVnaXN0
cnk/DQo+IA0KDQphIG5vdGUgaXMgYWRkZWQgaW4gdGhlIGlhbmEgY29uc2lkZXJhdGlvbi4gDQoN
CmlzIGl0IG9rPyBvciBqdXN0IG5lZ2xlY3QgaXQuDQoNCnRoYW5rcyBhIGxvdC4NCg0KSmlhbmth
bmcgWWFvDQoNCg0KPiBCZXN0IFJlZ2FyZHMsDQo+IEFsZXhleQ0KPiANCj4gUC5TLiBJIHN0aWxs
IG5lZWQgdG8gY2hlY2sgdGhlIHVwZGF0ZWQgQUJORiwgSSB3aWxsIGRvIHRoaXMgbGF0ZXIuDQo+


From alexey.melnikov@isode.com  Fri Dec  3 01:48:28 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 35C433A6AC6 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 01:48:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, 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 bAY+ZpCuleQ5 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 01:48:27 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 178933A6AC5 for <ima@ietf.org>; Fri,  3 Dec 2010 01:48:27 -0800 (PST)
Received: from [188.28.44.118] (188.28.44.118.threembb.co.uk [188.28.44.118])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPi9NAAbxSCj@rufus.isode.com>; Fri, 3 Dec 2010 09:49:41 +0000
Message-ID: <4CF8BD07.7050806@isode.com>
Date: Fri, 03 Dec 2010 09:48:55 +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: ima@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] Comments on the latest ABNF in draft-ietf-eai-rfc5335bis-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, 03 Dec 2010 09:48:28 -0000

4.4.  Change on addr-spec Syntax

   uAddr-Spec      =  uLocal-Part "@" ( uDomain / address-literal )

This should be using RFC 5322, not RFC 5321 syntax. So, it shoul be:

 uAddr-Spec      =  uLocal-Part "@" uDomain



   address-literal =  <See Section 4.1.2 of RFC 5321>

This is not needed.

   uLocal-Part     =  uDot-String / uQuoted-String / obs-Local-Part
                      ; Replace Local-Part in Section 4.1.2 of RFC 5321

This should be using RFC 5322 syntax, not RFC 5321 syntax, so:

   uLocal-Part      =  uDot-Atom / uQuoted-String / obs-local-part


   uDot-string     =  uAtom *("." uAtom)
                      ; Replace Dot-string in RFC 5321, Section 4.1.2

Not needed


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

Should be:
   uDomain          =  uDot-Atom / domain-literal / obs-domain

   domain-literal   = <See Section 3.4.1 of RFC 5322>



   sub-udomain     =  uLet-dig [uLdh-str]
                      ; Replace sub-domain in Section 4.1.2 of RFC 5321

   uLet-dig        =  Let-dig / UTF8-non-ascii
                      ; Replace uLet-dig in Section 4.1.2 of RFC 5321

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

   uLdh-str        =  *( ALPHA / DIGIT / "-" / UTF8-non-ascii) uLet-dig
                      ; Replace Ldh-str Section 4.1.2 of RFC 5321

These 4 productions are not needed.


From Internet-Drafts@ietf.org  Fri Dec  3 08:45:04 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 2E0DB28C134; Fri,  3 Dec 2010 08:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.429
X-Spam-Level: 
X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, 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 33FU2sqsY5PP; Fri,  3 Dec 2010 08:45:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA2F728C113; Fri,  3 Dec 2010 08:45: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
X-IETF-IDTracker: 3.09
Message-ID: <20101203164501.26463.63861.idtracker@localhost>
Date: Fri, 03 Dec 2010 08:45:01 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5335bis-05.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, 03 Dec 2010 16:45:04 -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           : Internationalized Email Headers
	Author(s)       :  . Yang, S. Steele
	Filename        : draft-ietf-eai-rfc5335bis-05.txt
	Pages           : 15
	Date            : 2010-12-03

Full internationalization of electronic mail requires not only the
capabilities to transmit non-ASCII content, to encode selected
information in specific header fields, and to use non-ASCII
characters in envelope addresses.  It also requires being able to
express those addresses and the information based on them in mail
header fields.  This document specifies a variant of Internet mail
that permits the use of Unicode encoded in UTF-8, rather than ASCII,
as the base form for Internet email header field.  This form is
permitted in transmission only if authorized by an SMTP extension, as
specified in an associated specification.  This specification updates
Section 6.4 of [RFC2045] to conform with the requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5335bis-05.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-rfc5335bis-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From alexey.melnikov@isode.com  Fri Dec  3 12:46: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 D712C28C130 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 12:46:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 5jsQKUQhiJuv for <ima@core3.amsl.com>; Fri,  3 Dec 2010 12:46:27 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id BC59C3A68B1 for <ima@ietf.org>; Fri,  3 Dec 2010 12:46:26 -0800 (PST)
Received: from [172.16.2.163] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPlXbwAbxTT1@rufus.isode.com>; Fri, 3 Dec 2010 20:47:43 +0000
Message-ID: <4CF95750.4050107@isode.com>
Date: Fri, 03 Dec 2010 20:47: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: ima@ietf.org
References: <20101203164501.26463.63861.idtracker@localhost>
In-Reply-To: <20101203164501.26463.63861.idtracker@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [EAI] 2 remaining issues with draft-ietf-eai-rfc5335bis-05.txt ABNF
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, 03 Dec 2010 20:46:27 -0000

1) In Section 4.3:

uQuoted-Pair is defined twice:

 uQuoted-Pair   = ("\" (VCHAR / WSP / UTF8-non-ascii )) / obs-qp

and

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

I think the first version is correct, so the second needs to be deleted. 
However, looking at this made me thing: do we really need 
backslash-escaping of UTF-8? Firstly, in email without EAI a single 
character was always escaped, so I don't know how parsers are going to 
behave for multibyte UTF-8 sequences.
Secondly, do we really need escaping for UTF-8? UTF-8 is already allowed 
elsewhere unescaped. So maybe it would be easier just to forget about 
escaping of UTF-8.

If people agree, then the production uQuoted-Pair needs to be removed, 
together with all productions that reference it directly or indirectly.

2). I had the following comment on -04:

  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?


The latest version replaced that with:

  description    = "Content-Description" ":" *uText

First, I think CRLF is missing at the end of the new definition.

But I am also wondering if this document should actually be extending 
<unstructured> anyway, as it is used by many other header field. So:

   unstructured =/ *([FWS] (VCHAR / UTF8-non-ascii) ) *WSP
                           ; extending <unstructured> from RFC 5322, 
Section 3.2.5

?


From Shawn.Steele@microsoft.com  Fri Dec  3 13:03: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 7F4C828C130 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.416
X-Spam-Level: 
X-Spam-Status: No, score=-10.416 tagged_above=-999 required=5 tests=[AWL=0.182, 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 5MR1yX1Ee-Us for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:03:30 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id B35E43A69A9 for <ima@ietf.org>; Fri,  3 Dec 2010 13:03:30 -0800 (PST)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 3 Dec 2010 13:04:48 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.42]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0255.003; Fri, 3 Dec 2010 13:04:48 -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: 5336bis
Thread-Index: AcuTI0YRL2rw12LoQ6qpZFOM+qvSmw==
Date: Fri, 3 Dec 2010 21:04:48 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_E14011F8737B524BB564B05FF748464A10C65AD6TK5EX14MBXC133r_"
MIME-Version: 1.0
Subject: [EAI] 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: Fri, 03 Dec 2010 21:03:32 -0000

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

SSB3YXMgYXNrZWQgdG8gbG9vayBhdCA1MzM2YmlzIGEgYml0IG1vcmU6DQoNClVURjhTTVRQYmlz
IG5lZWRzIGZpeGVkIGV2ZXJ5d2hlcmUgKG9idmlvdXNseSkuICBJTU8gaXQgc2hvdWxkIHN0YXkg
VVRGOFNNVFAuDQoNCjMuMyBFeHRlbmRlZCBtYWlsYm94IGFkZHJlc3Mgc3ludGF4IHNheXM6IOKA
nHRvIHBlcm1pdCBlaXRoZXIgdGhlIGRlZmluaXRpb24gYWJvdmUgb3LigKbigJ0gaW4gdHdvIHBs
YWNlcy4gIEl0IHdvdWxkIGJlIGVhc2llciBmb3IgbWUgaWYgaXQgc2FpZCDigJx0byBwZXJtaXQg
ZWl0aGVyIHRoZSBbUkZDNTMyMV0gZGVmaW5pdGlvbiBhYm92ZSwgb3LigKbigJ0NCg0KQUJORiAm
IEkgZG9u4oCZdCBnZXQgYWxvbmcgd2VsbCwgYnV0IG5vdGhpbmcganVtcHMgb3V0IHRvIG1lIGlu
IHRoYXQgc2VjdGlvbi4NCg0KSW4gMy42LjMgSSBkb27igJl0IGdldCB3aHkgcmVjZWl2ZWQgZmll
bGRzIGhhdmUgdG8gdXNlIEEtbGFiZWxzIGF0IGFsbD8gIEkgYXNzdW1lIEkgbWlzc2VkIGEgZGlz
Y3Vzc2lvbj8gIEl0IHdvdWxkIHNlZW0gdG8gbWUgdGhhdCB0aGUgZW5kLXBvaW50cyBhcmUgYWxs
IEVBSSBhd2FyZSwgc28gaXTigJlzIHVuY2xlYXIgdG8gbWUgd2h5IEEtbGFiZWxzIGFyZSBuZWNl
c3NhcnkgYW55d2hlcmUuDQoNCi0gU2hhd24NCg0K76Oi76OQ76On76ObIO+jou+jo++jl++jlO+j
mQ0KaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXduc3RlDQooU2VsZmhvc3QgNzg5MSkNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb2RlMjAwMDsNCglwYW5v
c2UtMToyIDAgNiAwIDAgMCAwIDAgMCAwO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxA
Q29kZTIwMDAiOw0KCXBhbm9zZS0xOjIgMCA2IDAgMCAwIDAgMCAwIDA7fQ0KLyogU3R5bGUgRGVm
aW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7
bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93
ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFw
aCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdp
bi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFy
Z2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBw
dDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uRW1haWxTdHls
ZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi
c2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0K
CW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21z
by1saXN0LWlkOjc0ODMxMDkzMTsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10
ZW1wbGF0ZS1pZHM6MjEyOTA0MjYwNCAxNjI0MTI2NzEyIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4
Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0
IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OkNhbGli
cmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6
bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFt
aWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsNg0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0
IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9s
O30NCkBsaXN0IGwwOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5
OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0K
dWwNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8
L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0
IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNo
YXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMi
IGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgd2FzIGFza2VkIHRvIGxvb2sgYXQgNTMzNmJpcyBhIGJp
dCBtb3JlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5VVEY4U01UUGJpcyBuZWVkcyBmaXhlZCBl
dmVyeXdoZXJlIChvYnZpb3VzbHkpLiZuYnNwOyBJTU8gaXQgc2hvdWxkIHN0YXkgVVRGOFNNVFAu
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjMuMyBFeHRlbmRlZCBtYWlsYm94IGFkZHJlc3Mgc3lu
dGF4IHNheXM6IOKAnHRvIHBlcm1pdCBlaXRoZXIgdGhlIGRlZmluaXRpb24gYWJvdmUgb3LigKbi
gJ0gaW4gdHdvIHBsYWNlcy4mbmJzcDsgSXQgd291bGQgYmUgZWFzaWVyIGZvciBtZSBpZiBpdCBz
YWlkIOKAnHRvIHBlcm1pdCBlaXRoZXIgdGhlIFtSRkM1MzIxXSBkZWZpbml0aW9uIGFib3ZlLCBv
cuKApuKAnTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BQk5GICZhbXA7IEkgZG9u4oCZdCBnZXQg
YWxvbmcgd2VsbCwgYnV0IG5vdGhpbmcganVtcHMgb3V0IHRvIG1lIGluIHRoYXQgc2VjdGlvbi48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SW4gMy42LjMgSSBkb27igJl0IGdldCB3aHkgcmVjZWl2
ZWQgZmllbGRzIGhhdmUgdG8gdXNlIEEtbGFiZWxzIGF0IGFsbD8mbmJzcDsgSSBhc3N1bWUgSSBt
aXNzZWQgYSBkaXNjdXNzaW9uPyZuYnNwOyBJdCB3b3VsZCBzZWVtIHRvIG1lIHRoYXQgdGhlIGVu
ZC1wb2ludHMgYXJlIGFsbCBFQUkgYXdhcmUsIHNvIGl04oCZcyB1bmNsZWFyIHRvIG1lIHdoeSBB
LWxhYmVscyBhcmUgbmVjZXNzYXJ5IGFueXdoZXJlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4t
IFNoYXduPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkpBIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpDb2RlMjAwMDttc28tZmFyZWFzdC1sYW5ndWFnZTpK
QSI+76Oi76OQ76On76ObIO+jou+jo++jl++jlO+jmTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTpDb2RlMjAwMCI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgaHJlZj0iaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXdu
c3RlIj48c3BhbiBzdHlsZT0iY29sb3I6Ymx1ZSI+aHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXdu
c3RlPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPihTZWxm
aG9zdCA3ODkxKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_E14011F8737B524BB564B05FF748464A10C65AD6TK5EX14MBXC133r_--

From klensin@jck.com  Fri Dec  3 13:27:20 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 8F5543A69AA for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 dgwlIjaSmA5V for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:27:17 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id BB7723A69A9 for <ima@ietf.org>; Fri,  3 Dec 2010 13:27:15 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1POdBB-000KfY-Jg; Fri, 03 Dec 2010 16:28:33 -0500
Date: Fri, 03 Dec 2010 16:28:32 -0500
From: John C Klensin <klensin@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, ima@ietf.org
Message-ID: <A4E0219E0CA472F3354D0B25@PST.JCK.COM>
In-Reply-To: <4CF95750.4050107@isode.com>
References: <20101203164501.26463.63861.idtracker@localhost> <4CF95750.4050107@isode.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] 2 remaining issues with draft-ietf-eai-rfc5335bis-05.txt ABNF
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, 03 Dec 2010 21:27:20 -0000

--On Friday, December 03, 2010 20:47 +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

(Speaking as someone occasionally considered to be an email and
internationalization expert, not as co-chair)

> 1) In Section 4.3:
>=20
> uQuoted-Pair is defined twice:
>=20
>  uQuoted-Pair   =3D ("\" (VCHAR / WSP / UTF8-non-ascii )) /
> obs-qp
>=20
> and
>=20
>  uQuoted-Pair   =3D ("\" uText) / obs-qp
>=20
> I think the first version is correct, so the second needs to
> be deleted. However, looking at this made me thing: do we
> really need backslash-escaping of UTF-8? Firstly, in email
> without EAI a single character was always escaped, so I don't
> know how parsers are going to behave for multibyte UTF-8
> sequences.

Well, the escape mechanism would have to be very carefully
defined to apply to Unicode code points, no matter how
represented in the UTF-8 stream, not subsequent octets.  That
definition is not clear in the existing documents, IMO.  For
most implementation purposes, that definition is equivalent to
"convert to UTF-32 (or to UTF-16 and be _really_ careful about
surrogates), apply escapes, convert back if needed".  That is
actually fairly convenient for BMP/UCS-2 (UTF-16 without
surrogates) or UTF-32 native systems, but isn't going to be easy
to say in the spec.

> Secondly, do we really need escaping for UTF-8? UTF-8 is
> already allowed elsewhere unescaped. So maybe it would be
> easier just to forget about escaping of UTF-8.

Well, I tried to raise a piece of this in my review.   If=20

    "foo\ bar"@example.com
is permitted, then one either has to prohibit embedded spaces
(and, more generally, all C0 and C1 characters plus space) or
one has to permit=20
    "f=C3=BA\ bar"@example.com
I don't see any way to take another position that doesn't lead
to a world of pain.

My preference is to ban spaces, C0, and C1 characters from
local-parts, but I think we can't get rid of escapes without
that ban.=20
=20
>...
> 2). I had the following comment on -04:
>=20
>   description  =3D "Content-Description:" unstructured CRLF
>=20
>   The <utext> syntax is extended above to allow UTF-8 in all
>   <unstructured> header fields.
>=20
> The problem with this is that <unstructured> is not
> referencing <text>.
> RFC 5322 defines:
>=20
>   unstructured    =3D  (*([FWS] VCHAR) *WSP) / obs-unstruct
>=20
> So should this document also extend <unstructured> to allow
> UTF-8?

Depends on whether we think Content-Description is free text or
a protocol element, doesn't it?  I would normally argue for
"protocol element" but the definition of Content-Description
seems pretty clear that it is just a narrative description and
that argues for UTF-8, probably unrestricted (no escapes either)
and terminated only by the line terminator.=20

> The latest version replaced that with:
>=20
>   description    =3D "Content-Description" ":" *uText
>=20
> First, I think CRLF is missing at the end of the new
> definition.

yes.  and that becomes very important as we move toward
permitting embedded non-ASCII characters.   Note too that we
need to be _very_ careful in this area to avoid prohibiting
strings that consist of mixed ASCII and non-ASCII characters
because those strings are essential for most
Latin-character-based writing systems and languages.
=20
> But I am also wondering if this document should actually be
> extending <unstructured> anyway, as it is used by many other
> header field. So:
>=20
>    unstructured =3D/ *([FWS] (VCHAR / UTF8-non-ascii) ) *WSP
>                            ; extending <unstructured> from RFC
> 5322, Section 3.2.5
>=20
> ?

    --john



From Shawn.Steele@microsoft.com  Fri Dec  3 13:33:28 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 24F6128C0FD for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.432
X-Spam-Level: 
X-Spam-Status: No, score=-10.432 tagged_above=-999 required=5 tests=[AWL=0.166, 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 GdiBLKOgbELt for <ima@core3.amsl.com>; Fri,  3 Dec 2010 13:33:27 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id E2D2828C0E2 for <ima@ietf.org>; Fri,  3 Dec 2010 13:33:26 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 3 Dec 2010 13:34:44 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.42]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0255.003; Fri, 3 Dec 2010 13:34:44 -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: 5336bis
Thread-Index: AcuTI0YRL2rw12LoQ6qpZFOM+qvSmwADnWig
Date: Fri, 3 Dec 2010 21:34:43 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C661F3@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_E14011F8737B524BB564B05FF748464A10C661F3TK5EX14MBXC133r_"
MIME-Version: 1.0
Subject: Re: [EAI] 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: Fri, 03 Dec 2010 21:33:28 -0000

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

U3BlY2lmaWNhbGx5LCBJ4oCZbSBoYXBweSBpZiB0aGUgUkZDIHdlcmUgcHVibGlzaGVkIGFzIGl0
IGlzLCBleGNlcHQgb2J2aW91c2x5IHRoZSBVVEY4U01UUGJpcyBNVVNUIGJlIGZpeGVkLg0KDQpJ
IGFzc3VtZSBJ4oCZbSBqdXN0IG1pc3Npbmcgc29tZXRoaW5nIG9idmlvdXMgYWJvdXQgbXkgbGFz
dCBxdWVzdGlvbi4NCg0KLVNoYXduDQoNCkZyb206IFNoYXduIFN0ZWVsZQ0KU2VudDogRnJpZGF5
LCBEZWNlbWJlciAwMywgMjAxMCAxOjA1IFBNDQpUbzogaW1hQGlldGYub3JnOyBBbGV4ZXkgTWVs
bmlrb3YgKGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb20pDQpTdWJqZWN0OiA1MzM2YmlzDQoNCkkg
d2FzIGFza2VkIHRvIGxvb2sgYXQgNTMzNmJpcyBhIGJpdCBtb3JlOg0KDQpVVEY4U01UUGJpcyBu
ZWVkcyBmaXhlZCBldmVyeXdoZXJlIChvYnZpb3VzbHkpLiAgSU1PIGl0IHNob3VsZCBzdGF5IFVU
RjhTTVRQLg0KDQozLjMgRXh0ZW5kZWQgbWFpbGJveCBhZGRyZXNzIHN5bnRheCBzYXlzOiDigJx0
byBwZXJtaXQgZWl0aGVyIHRoZSBkZWZpbml0aW9uIGFib3ZlIG9y4oCm4oCdIGluIHR3byBwbGFj
ZXMuICBJdCB3b3VsZCBiZSBlYXNpZXIgZm9yIG1lIGlmIGl0IHNhaWQg4oCcdG8gcGVybWl0IGVp
dGhlciB0aGUgW1JGQzUzMjFdIGRlZmluaXRpb24gYWJvdmUsIG9y4oCm4oCdDQoNCkFCTkYgJiBJ
IGRvbuKAmXQgZ2V0IGFsb25nIHdlbGwsIGJ1dCBub3RoaW5nIGp1bXBzIG91dCB0byBtZSBpbiB0
aGF0IHNlY3Rpb24uDQoNCkluIDMuNi4zIEkgZG9u4oCZdCBnZXQgd2h5IHJlY2VpdmVkIGZpZWxk
cyBoYXZlIHRvIHVzZSBBLWxhYmVscyBhdCBhbGw/ICBJIGFzc3VtZSBJIG1pc3NlZCBhIGRpc2N1
c3Npb24/ICBJdCB3b3VsZCBzZWVtIHRvIG1lIHRoYXQgdGhlIGVuZC1wb2ludHMgYXJlIGFsbCBF
QUkgYXdhcmUsIHNvIGl04oCZcyB1bmNsZWFyIHRvIG1lIHdoeSBBLWxhYmVscyBhcmUgbmVjZXNz
YXJ5IGFueXdoZXJlLg0KDQotIFNoYXduDQoNCu+jou+jkO+jp++jmyDvo6Lvo6Pvo5fvo5Tvo5kN
Cmh0dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZQ0KKFNlbGZob3N0IDc4OTEpDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvZGUyMDAwOw0KCXBhbm9zZS0xOjIgMCA2IDAgMCAw
IDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBDb2RlMjAwMCI7DQoJcGFu
b3NlLTE6MiAwIDYgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5N
c29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBh
cmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowaW47DQoJbWFy
Z2luLXJpZ2h0OjBpbjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouNWluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxl
LXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29s
b3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWlu
IDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1V
UyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlNwZWNp
ZmljYWxseSwgSeKAmW0gaGFwcHkgaWYgdGhlIFJGQyB3ZXJlIHB1Ymxpc2hlZCBhcyBpdCBpcywg
ZXhjZXB0IG9idmlvdXNseSB0aGUgVVRGOFNNVFBiaXMgTVVTVCBiZSBmaXhlZC48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkkgYXNzdW1lIEnigJltIGp1c3QgbWlzc2luZyBz
b21ldGhpbmcgb2J2aW91cyBhYm91dCBteSBsYXN0IHF1ZXN0aW9uLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+LVNoYXduPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9w
OnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+
PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gU2hhd24gU3RlZWxlDQo8YnI+DQo8Yj5T
ZW50OjwvYj4gRnJpZGF5LCBEZWNlbWJlciAwMywgMjAxMCAxOjA1IFBNPGJyPg0KPGI+VG86PC9i
PiBpbWFAaWV0Zi5vcmc7IEFsZXhleSBNZWxuaWtvdiAoYWxleGV5Lm1lbG5pa292QGlzb2RlLmNv
bSk8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gNTMzNmJpczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgd2FzIGFza2VkIHRvIGxvb2sgYXQgNTMzNmJpcyBhIGJp
dCBtb3JlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5VVEY4U01UUGJpcyBuZWVkcyBmaXhlZCBl
dmVyeXdoZXJlIChvYnZpb3VzbHkpLiZuYnNwOyBJTU8gaXQgc2hvdWxkIHN0YXkgVVRGOFNNVFAu
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjMuMyBFeHRlbmRlZCBtYWlsYm94IGFkZHJlc3Mgc3lu
dGF4IHNheXM6IOKAnHRvIHBlcm1pdCBlaXRoZXIgdGhlIGRlZmluaXRpb24gYWJvdmUgb3LigKbi
gJ0gaW4gdHdvIHBsYWNlcy4mbmJzcDsgSXQgd291bGQgYmUgZWFzaWVyIGZvciBtZSBpZiBpdCBz
YWlkIOKAnHRvIHBlcm1pdCBlaXRoZXIgdGhlIFtSRkM1MzIxXSBkZWZpbml0aW9uIGFib3ZlLCBv
cuKApuKAnTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BQk5GICZhbXA7IEkgZG9u4oCZdCBnZXQg
YWxvbmcgd2VsbCwgYnV0IG5vdGhpbmcganVtcHMgb3V0IHRvIG1lIGluIHRoYXQgc2VjdGlvbi48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SW4gMy42LjMgSSBkb27igJl0IGdldCB3aHkgcmVjZWl2
ZWQgZmllbGRzIGhhdmUgdG8gdXNlIEEtbGFiZWxzIGF0IGFsbD8mbmJzcDsgSSBhc3N1bWUgSSBt
aXNzZWQgYSBkaXNjdXNzaW9uPyZuYnNwOyBJdCB3b3VsZCBzZWVtIHRvIG1lIHRoYXQgdGhlIGVu
ZC1wb2ludHMgYXJlIGFsbCBFQUkgYXdhcmUsIHNvIGl04oCZcyB1bmNsZWFyIHRvIG1lIHdoeSBB
LWxhYmVscyBhcmUgbmVjZXNzYXJ5IGFueXdoZXJlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4t
IFNoYXduPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkpBIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpDb2RlMjAwMDttc28tZmFyZWFzdC1sYW5ndWFnZTpK
QSI+76Oi76OQ76On76ObIO+jou+jo++jl++jlO+jmTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTpDb2RlMjAwMCI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgaHJlZj0iaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXdu
c3RlIj5odHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGU8L2E+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4oU2VsZmhvc3QgNzg5MSk8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_E14011F8737B524BB564B05FF748464A10C661F3TK5EX14MBXC133r_--

From Shawn.Steele@microsoft.com  Fri Dec  3 15:01:23 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 9542C3A67A8 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 15:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.446
X-Spam-Level: 
X-Spam-Status: No, score=-10.446 tagged_above=-999 required=5 tests=[AWL=0.152, 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 Te4o4UHRxzfM for <ima@core3.amsl.com>; Fri,  3 Dec 2010 15:01:21 -0800 (PST)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id B3FA33A6778 for <ima@ietf.org>; Fri,  3 Dec 2010 15:01:21 -0800 (PST)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 3 Dec 2010 15:02:39 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.42]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0255.003; Fri, 3 Dec 2010 15:02:39 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: My happiness with current drafts.
Thread-Index: AcuTPPAwPFLOICTNR4SGgzThEQolnw==
Date: Fri, 3 Dec 2010 23:02:39 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C66C96@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_E14011F8737B524BB564B05FF748464A10C66C96TK5EX14MBXC133r_"
MIME-Version: 1.0
Subject: [EAI] My happiness with current drafts.
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, 03 Dec 2010 23:01:23 -0000

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

SSBqdXN0IHNlbnQgY29tbWVudHMgYWJvdXQgNTMzNmJpcywgSSBhbSBoYXBweSB3aXRoIGl0LCBv
YnZpb3VzbHkgdGhlIGNvbW1lbnQgbmVlZHMgcmVtb3ZlZCBhbmQgVVRGOFNNVFBiaXMgZml4ZWQN
Cg0KSSBhbSBhbHNvIGhhcHB5IHdpdGggNTMzNWJpcywgYnV0IEnigJltIG5vdCBzdXJlIHRoYXQg
Y291bnRzLg0KDQpJIGFtIGFsc28gc3RpbGwgaGFwcHkgd2l0aCA0OTUyYmlzDQoNCkkgYW0gYWxz
byBoYXBweSB3aXRoIDUzMzdiaXMNCg0KLSBTaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg76Oi76Oj76OX
76OU76OZDQpodHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGUNCihTZWxmaG9zdCA3ODkzKQ0K
DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OkNvZGUyMDAwOw0KCXBhbm9zZS0xOjIgMCA2IDAgMCAwIDAgMCAwIDA7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBDb2RlMjAwMCI7DQoJcGFub3NlLTE6MiAwIDYg
MCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxp
Lk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu
cy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlz
aXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERl
ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4w
aW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkkganVzdCBzZW50IGNvbW1lbnRzIGFib3V0IDUzMzZiaXMsIEkg
YW0gaGFwcHkgd2l0aCBpdCwgb2J2aW91c2x5IHRoZSBjb21tZW50IG5lZWRzIHJlbW92ZWQgYW5k
IFVURjhTTVRQYmlzIGZpeGVkPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgYW0gYWxzbyBoYXBw
eSB3aXRoIDUzMzViaXMsIGJ1dCBJ4oCZbSBub3Qgc3VyZSB0aGF0IGNvdW50cy48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+SSBhbSBhbHNvIHN0aWxsIGhhcHB5IHdpdGggNDk1MmJpczxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5JIGFtIGFsc28gaGFwcHkgd2l0aCA1MzM3YmlzPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpKQSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6SkEiPi0gU2hhd248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1mYXJlYXN0LWxhbmd1YWdl
OkpBIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJKQSIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q29kZTIw
MDA7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6SkEiPu+jou+jkO+jp++jmyDvo6Lvo6Pvo5fvo5Tvo5k8
L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6Q29kZTIwMDAi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIGhyZWY9Imh0
dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZSI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsdWUiPmh0
dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZTwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4oU2VsZmhvc3QgNzg5Myk8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_E14011F8737B524BB564B05FF748464A10C66C96TK5EX14MBXC133r_--

From tony@att.com  Fri Dec  3 17:28:08 2010
Return-Path: <tony@att.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 330EF3A69F2 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 17:28:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.481
X-Spam-Level: 
X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, 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 eJqEELeViDzC for <ima@core3.amsl.com>; Fri,  3 Dec 2010 17:28:07 -0800 (PST)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id EC1C33A67B1 for <ima@ietf.org>; Fri,  3 Dec 2010 17:28:06 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-10.tower-129.messagelabs.com!1291426164!58076497!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 28364 invoked from network); 4 Dec 2010 01:29:25 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-10.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Dec 2010 01:29:25 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oB41Thns022842 for <ima@ietf.org>; Fri, 3 Dec 2010 20:29:43 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oB41TaKx022733 for <ima@ietf.org>; Fri, 3 Dec 2010 20:29:36 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oB41TGPL010239 for <ima@ietf.org>; Fri, 3 Dec 2010 20:29:16 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oB41T9p8010178 for <ima@ietf.org>; Fri, 3 Dec 2010 20:29:09 -0500
Received: from [135.70.23.9] (vpn-135-70-23-9.vpn.west.att.com[135.70.23.9]) by maillennium.att.com (mailgw1) with ESMTP id <20101204012908gw1004lkipe> (Authid: tony); Sat, 4 Dec 2010 01:29:09 +0000
X-Originating-IP: [135.70.23.9]
Message-ID: <4CF99963.9070202@att.com>
Date: Fri, 03 Dec 2010 20:29:07 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: EAI WG <ima@ietf.org>
References: <4CF0307D.9090900@isode.com> <490863556.14931@cnnic.cn>	<491280183.27938@cnnic.cn> <491296256.28928@cnnic.cn> <491364248.30201@cnnic.cn>
In-Reply-To: <491364248.30201@cnnic.cn>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [EAI] draft-ietf-eai-rfc5336bis-05.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, 04 Dec 2010 01:28:08 -0000

On 12/3/2010 3:15 AM, Jiankang YAO wrote:
> ----- Original Message -----
> From: "Alexey Melnikov"<alexey.melnikov@isode.com>
> To: "Jiankang YAO"<yaojk@cnnic.cn>; "EAI WG"<ima@ietf.org>
> Sent: Thursday, December 02, 2010 9:23 PM
> Subject: draft-ietf-eai-rfc5336bis-05.txt
>> 3) I think we need to collapse X.6.8 and Y.6.8 into 1 IANA registration
>> (with all allowed status codes listed in 1 place). I.e.:
>>
>>       Code:               X.6.8
>>       Sample Text:        UTF-8 string reply is required,
>>                           but not permitted by the client
>>       Associated basic status code:  553, 550, 252
>>       Description:        This indicates that 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.
>> ...

I think the order should be 252, 550, 553

>> We also need to decide on what to do with X.6.10 - deprecate it in the
>> registry?
> a note is added in the iana consideration.
>
> is it ok? or just neglect it.

Please add text similar to the following to the IANA considerations section:

     IANA is directed to add the following text to the end of the 
Description text of X.6.10:

         This is a duplicate of X.6.8 and deprecated from further use.

Thanks.

     Tony Hansen
     tony@att.com

From yaojk@cnnic.cn  Fri Dec  3 18:13:30 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 56C253A686C for <ima@core3.amsl.com>; Fri,  3 Dec 2010 18:13:30 -0800 (PST)
X-Quarantine-ID: <kpwiuw9TN0Fz>
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: -100.207
X-Spam-Level: 
X-Spam-Status: No, score=-100.207 tagged_above=-999 required=5 tests=[AWL=1.589, BAYES_00=-2.599, 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 kpwiuw9TN0Fz for <ima@core3.amsl.com>; Fri,  3 Dec 2010 18:13:29 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 5AF283A683F for <ima@ietf.org>; Fri,  3 Dec 2010 18:13:27 -0800 (PST)
Received: (eyou send program); Sat, 04 Dec 2010 10:14:46 +0800
Message-ID: <491428886.27178@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, 04 Dec 2010 10:14:46 +0800
Message-ID: <B9337A2F4FAC4D1D8C1335A2EB0F6993@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Shawn Steele" <Shawn.Steele@microsoft.com>
References: <491410301.06656@cnnic.cn>
Date: Sat, 4 Dec 2010 10:12:43 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
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
Cc: ima@ietf.org
Subject: Re: [EAI] 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, 04 Dec 2010 02:13:30 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogU2hhd24gU3RlZWxlIA0KVG86
IGltYUBpZXRmLm9yZyA7IEFsZXhleSBNZWxuaWtvdihhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29t
KSANClNlbnQ6IFNhdHVyZGF5LCBEZWNlbWJlciAwNCwgMjAxMCA1OjA0IEFNDQpTdWJqZWN0OiBb
RUFJXSA1MzM2YmlzDQoNCg0KPkkgd2FzIGFza2VkIHRvIGxvb2sgYXQgNTMzNmJpcyBhIGJpdCBt
b3JlOg0KIA0KPlVURjhTTVRQYmlzIG5lZWRzIGZpeGVkIGV2ZXJ5d2hlcmUgKG9idmlvdXNseSku
ICBJTU8gaXQgc2hvdWxkIHN0YXkgVVRGOFNNVFAuDQo+DQo+DQoNCkkgcmVtZW1iZXIgdGhhdCBp
biB0aGUgNzggaWV0ZiBtZWV0aW5nLCB3ZSBsZWF2ZSBpdCB0byBpZXNnIHRvIGRvIGEgZmluYWwg
ZGVjaXNpb24uDQoNCg0KPg0KDQogDQoNCj4NCj4zLjMgRXh0ZW5kZWQgbWFpbGJveCBhZGRyZXNz
IHN5bnRheCBzYXlzOiDigJx0byBwZXJtaXQgZWl0aGVyIHRoZSBkZWZpbml0aW9uIGFib3ZlIG9y
4oCm4oCdIGluIHR3byBwbGFjZXMuICBJdCB3b3VsZCBiZSBlYXNpZXIgZm9yIG1lIGlmIGl0IHNh
aWQg4oCcdG8gPnBlcm1pdCBlaXRoZXIgdGhlIFtSRkM1MzIxXSBkZWZpbml0aW9uIGFib3ZlLCBv
cuKApuKAnQ0KDQo+DQoNCnVwZGF0ZWQuDQoNCg0KPg0KIA0KDQo+QUJORiAmIEkgZG9u4oCZdCBn
ZXQgYWxvbmcgd2VsbCwgYnV0IG5vdGhpbmcganVtcHMgb3V0IHRvIG1lIGluIHRoYXQgc2VjdGlv
bi4NCiANCj5JbiAzLjYuMyBJIGRvbuKAmXQgZ2V0IHdoeSByZWNlaXZlZCBmaWVsZHMgaGF2ZSB0
byB1c2UgQS1sYWJlbHMgYXQgYWxsPyAgSSBhc3N1bWUgSSBtaXNzZWQgYSBkaXNjdXNzaW9uPyAg
SXQgd291bGQgc2VlbSB0byBtZSB0aGF0IHRoZSBlbmQtcG9pbnRzIGFyZSA+YWxsIEVBSSBhd2Fy
ZSwgc28gaXTigJlzIHVuY2xlYXIgdG8gbWUgd2h5IEEtbGFiZWxzIGFyZSBuZWNlc3NhcnkgYW55
d2hlcmUuDQo+DQoNCklmIEkgcmVtZW1iZXIgY29ycmVjdGx5LCBJIHRoaW5rIHRoYXQgaXQgaXMg
Zm9yIGVhc3kgZGVidWdnaW5nLg0KDQpKaWFua2FuZyBZYW8NCiANCj4tIFNoYXduDQogDQrvo6Lv
o5Dvo6fvo5sg76Oi76Oj76OX76OU76OZDQo=


From yaojk@cnnic.cn  Fri Dec  3 18:14:24 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 CEAC83A69F1 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 18:14:24 -0800 (PST)
X-Quarantine-ID: <wQrjbKeJcbnM>
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.453
X-Spam-Level: 
X-Spam-Status: No, score=-99.453 tagged_above=-999 required=5 tests=[AWL=0.590, 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 wQrjbKeJcbnM for <ima@core3.amsl.com>; Fri,  3 Dec 2010 18:14:23 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 3DAD53A69FB for <ima@ietf.org>; Fri,  3 Dec 2010 18:14:22 -0800 (PST)
Received: (eyou send program); Sat, 04 Dec 2010 10:15:40 +0800
Message-ID: <491428940.28601@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, 04 Dec 2010 10:15:40 +0800
Message-ID: <1E2D5864726E41B6A1193FDF755555DA@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Tony Hansen" <tony@att.com>, "EAI WG" <ima@ietf.org>
References: <4CF0307D.9090900@isode.com><490863556.14931@cnnic.cn>	<491280183.27938@cnnic.cn><491296256.28928@cnnic.cn> <491364248.30201@cnnic.cn> <491426175.27178@cnnic.cn>
Date: Sat, 4 Dec 2010 10:13:27 +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] draft-ietf-eai-rfc5336bis-05.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, 04 Dec 2010 02:14:25 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlRvbnkgSGFuc2VuIiA8dG9u
eUBhdHQuY29tPg0KVG86ICJFQUkgV0ciIDxpbWFAaWV0Zi5vcmc+DQpTZW50OiBTYXR1cmRheSwg
RGVjZW1iZXIgMDQsIDIwMTAgOToyOSBBTQ0KU3ViamVjdDogUmU6IFtFQUldIGRyYWZ0LWlldGYt
ZWFpLXJmYzUzMzZiaXMtMDUudHh0DQoNCg0KPiBPbiAxMi8zLzIwMTAgMzoxNSBBTSwgSmlhbmth
bmcgWUFPIHdyb3RlOg0KPj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4gRnJvbTog
IkFsZXhleSBNZWxuaWtvdiI8YWxleGV5Lm1lbG5pa292QGlzb2RlLmNvbT4NCj4+IFRvOiAiSmlh
bmthbmcgWUFPIjx5YW9qa0Bjbm5pYy5jbj47ICJFQUkgV0ciPGltYUBpZXRmLm9yZz4NCj4+IFNl
bnQ6IFRodXJzZGF5LCBEZWNlbWJlciAwMiwgMjAxMCA5OjIzIFBNDQo+PiBTdWJqZWN0OiBkcmFm
dC1pZXRmLWVhaS1yZmM1MzM2YmlzLTA1LnR4dA0KPj4+IDMpIEkgdGhpbmsgd2UgbmVlZCB0byBj
b2xsYXBzZSBYLjYuOCBhbmQgWS42LjggaW50byAxIElBTkEgcmVnaXN0cmF0aW9uDQo+Pj4gKHdp
dGggYWxsIGFsbG93ZWQgc3RhdHVzIGNvZGVzIGxpc3RlZCBpbiAxIHBsYWNlKS4gSS5lLjoNCj4+
Pg0KPj4+ICAgICAgIENvZGU6ICAgICAgICAgICAgICAgWC42LjgNCj4+PiAgICAgICBTYW1wbGUg
VGV4dDogICAgICAgIFVURi04IHN0cmluZyByZXBseSBpcyByZXF1aXJlZCwNCj4+PiAgICAgICAg
ICAgICAgICAgICAgICAgICAgIGJ1dCBub3QgcGVybWl0dGVkIGJ5IHRoZSBjbGllbnQNCj4+PiAg
ICAgICBBc3NvY2lhdGVkIGJhc2ljIHN0YXR1cyBjb2RlOiAgNTUzLCA1NTAsIDI1Mg0KPj4+ICAg
ICAgIERlc2NyaXB0aW9uOiAgICAgICAgVGhpcyBpbmRpY2F0ZXMgdGhhdCBhIHJlcGx5IGNvbnRh
aW5pbmcgYSBVVEYtOA0KPj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgc3RyaW5nIGlzIHJl
cXVpcmVkIHRvIHNob3cgdGhlIG1haWxib3ggbmFtZSwNCj4+PiAgICAgICAgICAgICAgICAgICAg
ICAgICAgIGJ1dCB0aGF0IGZvcm0gb2YgcmVzcG9uc2UgaXMgbm90DQo+Pj4gICAgICAgICAgICAg
ICAgICAgICAgICAgICBwZXJtaXR0ZWQgYnkgdGhlIGNsaWVudC4NCj4+PiAuLi4NCj4gDQo+IEkg
dGhpbmsgdGhlIG9yZGVyIHNob3VsZCBiZSAyNTIsIDU1MCwgNTUzDQo+IA0KPj4+IFdlIGFsc28g
bmVlZCB0byBkZWNpZGUgb24gd2hhdCB0byBkbyB3aXRoIFguNi4xMCAtIGRlcHJlY2F0ZSBpdCBp
biB0aGUNCj4+PiByZWdpc3RyeT8NCj4+IGEgbm90ZSBpcyBhZGRlZCBpbiB0aGUgaWFuYSBjb25z
aWRlcmF0aW9uLg0KPj4NCj4+IGlzIGl0IG9rPyBvciBqdXN0IG5lZ2xlY3QgaXQuDQo+IA0KPiBQ
bGVhc2UgYWRkIHRleHQgc2ltaWxhciB0byB0aGUgZm9sbG93aW5nIHRvIHRoZSBJQU5BIGNvbnNp
ZGVyYXRpb25zIHNlY3Rpb246DQo+IA0KPiAgICAgSUFOQSBpcyBkaXJlY3RlZCB0byBhZGQgdGhl
IGZvbGxvd2luZyB0ZXh0IHRvIHRoZSBlbmQgb2YgdGhlIA0KPiBEZXNjcmlwdGlvbiB0ZXh0IG9m
IFguNi4xMDoNCj4gDQo+ICAgICAgICAgVGhpcyBpcyBhIGR1cGxpY2F0ZSBvZiBYLjYuOCBhbmQg
ZGVwcmVjYXRlZCBmcm9tIGZ1cnRoZXIgdXNlLg0KPiANCg0KdGhhbmtzLg0KdXBkYXRlZC4NCg0K
SmlhbmthbmcgWWFvDQoNCj4gVGhhbmtzLg0KPiANCj4gICAgIFRvbnkgSGFuc2VuDQo+ICAgICB0
b255QGF0dC5jb20NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gSU1BIG1haWxpbmcgbGlzdA0KPiBJTUFAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbWE=


From Internet-Drafts@ietf.org  Fri Dec  3 18:15: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 47A973A6850; Fri,  3 Dec 2010 18:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.433
X-Spam-Level: 
X-Spam-Status: No, score=-102.433 tagged_above=-999 required=5 tests=[AWL=0.166, 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 6DuFCfIl9fk5; Fri,  3 Dec 2010 18:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D7F03A6403; Fri,  3 Dec 2010 18:15:02 -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
X-IETF-IDTracker: 3.09
Message-ID: <20101204021502.32512.11495.idtracker@localhost>
Date: Fri, 03 Dec 2010 18:15:02 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5336bis-07.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, 04 Dec 2010 02:15: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           : SMTP Extension for Internationalized Email Address
	Author(s)       : J. Yao, W. MAO
	Filename        : draft-ietf-eai-rfc5336bis-07.txt
	Pages           : 19
	Date            : 2010-12-03

This document specifies an SMTP extension for transport and delivery
of email messages with internationalized email addresses or header
information.  This document updates some syntax rules defined in RFC
5321 and RFC 5322.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5336bis-07.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-rfc5336bis-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From klensin@jck.com  Fri Dec  3 20:52: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 40B193A6A24 for <ima@core3.amsl.com>; Fri,  3 Dec 2010 20:52:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 vq+RXTgpS6iq for <ima@core3.amsl.com>; Fri,  3 Dec 2010 20:52:09 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 276233A6A1A for <ima@ietf.org>; Fri,  3 Dec 2010 20:52:09 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1POk7i-00094m-EY; Fri, 03 Dec 2010 23:53:26 -0500
Date: Fri, 03 Dec 2010 23:53:25 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org
Message-ID: <9D7D0F66660154F15D0E8CD4@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10C66C96@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C66C96@TK5EX14MBXC133.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] My happiness with current drafts.
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, 04 Dec 2010 04:52:10 -0000

--On Friday, December 03, 2010 23:02 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> I just sent comments about 5336bis, I am happy with it,
> obviously the comment needs removed and UTF8SMTPbis fixed
> 
> I am also happy with 5335bis, but I'm not sure that counts.
> 
> I am also still happy with 4952bis
> 
> I am also happy with 5337bis

Anticipating a note that will go out early next week, have you
read these drafts for clarity of expression, correct English,
and similar issues on which we are likely to get hung up if they
aren't clear and correct?   Have you checked the ABNF in all
cases, both within documents and for consistency between them?

   john



From yaojk@cnnic.cn  Fri Dec  3 22:17:54 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 C3E8D3A68AF for <ima@core3.amsl.com>; Fri,  3 Dec 2010 22:17:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.796
X-Spam-Level: 
X-Spam-Status: No, score=-101.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 mabps33rgNXi for <ima@core3.amsl.com>; Fri,  3 Dec 2010 22:17:52 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 74C2D3A659A for <ima@ietf.org>; Fri,  3 Dec 2010 22:17:50 -0800 (PST)
Received: (eyou send program); Sat, 04 Dec 2010 14:19:08 +0800
Message-ID: <491443548.18928@cnnic.cn>
Received: from 125.33.1.17 by mail.cnnic.cn with HTTP; Sat, 04 Dec 2010 14:19:08 +0800
X-WebMAIL-MUA: [125.33.1.17]
From: "YAO Jiankang" <yaojk@cnnic.cn>
To: klensin@jck.com, Shawn.Steele@microsoft.com, ima@ietf.org
Date: Sat, 04 Dec 2010 14:19:08 +0800
X-Priority: 3
Content-Type: text/plain
Subject: [EAI] review of rfc5335bis-05.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: YAO Jiankang <yaojk@cnnic.cn>
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, 04 Dec 2010 06:17:55 -0000

the ABNF syntax defined in this document need some improvments.

comments 1:
section 4.3
   FWS     =  <see [RFC5322] Section 3.2.2, folding white space>

   CFWS    =  <see [RFC5322] Section 3.2.2>

suggestions: 
to keep the style same, delete folding white space or add something in CFWS.


comments 2:
in section 4.3
ctext   =/  UTF8-non-ascii

it should be 
uCtext   =%d33-39 /          ; Printable US-ASCII
              %d42-91 /          ;  characters not including
                   %d93-126 /         ;  "(", ")", or "\"
                   obs-ctext  ;
                 UTF8-non-ascii
since ctext has been defined in rfc5322.

comments 3:
in section 4.3
qcontent       =/ uQcontent

it should be deleted since qcontent is not used anywhere in this document.

comments 4:
in section 4.4
uLocal-Part    = uDot-Atom / uQuoted-String / obs-local-part

where uQuoted-String  is not defined anywhere.
BTW, I think that uQuoted-String is not necessary, Quoted-String is ok since there
has a uDot-Atom.

comments 5:
in section 4.4
   uDomain        =  uDot-Atom / domain-literal / obs-domain

   domain-literal = <See Section 3.4.1 of RFC 5322>

where  obs-domain should be also defined or be pointed out where it is from.


comments 6:
in section 4.5

   received-token =/ uAddr-Spec

it should be 
uRreceived-token  =   word / angle-addr / uAddr-spec / domain




comments 7:

6.  IANA Considerations

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


where now it should be Section 4.6 intead of Section 4.4..



comments 8:

8.  Edit history

   This section is used for tracking the update of this document.  Will
   be removed after finalize.

I think that it should use the following format:

[[anchor11: RFC Editor: Please remove this section.]]

so that the rfc editor can easily identify it and remove it.


BTW, it is better that Shawn can double check it.

Jiankang Yao







From alexey.melnikov@isode.com  Sat Dec  4 03:45:54 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 C7BB13A6A42 for <ima@core3.amsl.com>; Sat,  4 Dec 2010 03:45:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 h26G2Cadryjj for <ima@core3.amsl.com>; Sat,  4 Dec 2010 03:45:53 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 6377C3A68BA for <ima@ietf.org>; Sat,  4 Dec 2010 03:45:53 -0800 (PST)
Received: from [92.40.162.159] (92.40.162.159.sub.mbb.three.co.uk [92.40.162.159])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TPoqOwAbxZm7@rufus.isode.com>; Sat, 4 Dec 2010 11:47:10 +0000
Message-ID: <4CFA2A31.3020402@isode.com>
Date: Sat, 04 Dec 2010 11:46:57 +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: YAO Jiankang <yaojk@cnnic.cn>
References: <491443548.18928@cnnic.cn>
In-Reply-To: <491443548.18928@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Shawn.Steele@microsoft.com, ima@ietf.org
Subject: Re: [EAI] review of rfc5335bis-05.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, 04 Dec 2010 11:45:54 -0000

Hi Jiankang,

YAO Jiankang wrote:

>the ABNF syntax defined in this document need some improvments.
>
>comments 1:
>section 4.3
>   FWS     =  <see [RFC5322] Section 3.2.2, folding white space>
>
>   CFWS    =  <see [RFC5322] Section 3.2.2>
>
>suggestions: 
>to keep the style same, delete folding white space or add something in CFWS.
>  
>
Your suggestion is fine, but I would leave this to the discretion of the 
editor.

>comments 2:
>in section 4.3
>ctext   =/  UTF8-non-ascii
>
>it should be 
>uCtext   =%d33-39 /          ; Printable US-ASCII
>              %d42-91 /          ;  characters not including
>                   %d93-126 /         ;  "(", ")", or "\"
>                   obs-ctext  ;
>                 UTF8-non-ascii
>since ctext has been defined in rfc5322.
>  
>
Actually, I wouldn't do this change, because <ctext> is used in many 
other places in RFC 5322. We really want to be extending it, I think.

>comments 3:
>in section 4.3
>qcontent       =/ uQcontent
>
>it should be deleted since qcontent is not used anywhere in this document.
>  
>
It is used indirectly to update <quoted-string> in RFC 5322. So I think 
we need to keep it.

>comments 4:
>in section 4.4
>uLocal-Part    = uDot-Atom / uQuoted-String / obs-local-part
>
>where uQuoted-String  is not defined anywhere.
>  
>
Good point.

>BTW, I think that uQuoted-String is not necessary,
>
It is used in Section 4.3.
We might get away with only defining the updated <qcontent> (or 
<uQcontent>), or <uQuoted-String>, but I am not entirely sure.

>Quoted-String is ok since there has a uDot-Atom.
>
>comments 5:
>in section 4.4
>   uDomain        =  uDot-Atom / domain-literal / obs-domain
>
>   domain-literal = <See Section 3.4.1 of RFC 5322>
>
>where  obs-domain should be also defined or be pointed out where it is from.
>  
>
+1.

>comments 6:
>in section 4.5
>
>   received-token =/ uAddr-Spec
>
>it should be 
>uRreceived-token  =   word / angle-addr / uAddr-spec / domain
>  
>
No. This is extending something defined in RFC 5322.

>comments 7:
>
>6.  IANA Considerations
>
>   IANA has registered the message/global MIME type using the
>   registration form contained in Section 4.4.
>
>
>where now it should be Section 4.6 intead of Section 4.4..
>  
>
Good catch.

>comments 8:
>
>8.  Edit history
>
>   This section is used for tracking the update of this document.  Will
>   be removed after finalize.
>
>I think that it should use the following format:
>
>[[anchor11: RFC Editor: Please remove this section.]]
>
>so that the rfc editor can easily identify it and remove it.
>  
>
Agreed.

>BTW, it is better that Shawn can double check it.
>
>Jiankang Yao
>  
>
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 Shawn.Steele@microsoft.com  Sat Dec  4 11:54:53 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 CC12E28C0CE for <ima@core3.amsl.com>; Sat,  4 Dec 2010 11:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.458
X-Spam-Level: 
X-Spam-Status: No, score=-10.458 tagged_above=-999 required=5 tests=[AWL=0.141, 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 lncXC875YVvj for <ima@core3.amsl.com>; Sat,  4 Dec 2010 11:54:53 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 188B428C0D0 for <ima@ietf.org>; Sat,  4 Dec 2010 11:54:53 -0800 (PST)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 4 Dec 2010 11:54:12 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.42]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.01.0255.003; Sat, 4 Dec 2010 11:54:11 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Jiankang YAO <yaojk@cnnic.cn>
Thread-Topic: [EAI] 5336bis
Thread-Index: AQHLk1kjXnUMDwaS6ECSMa64y4acFpOQs1eb
Date: Sat, 4 Dec 2010 19:54:11 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C68441@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <491410301.06656@cnnic.cn>, <B9337A2F4FAC4D1D8C1335A2EB0F6993@LENOVO47E041CF>
In-Reply-To: <B9337A2F4FAC4D1D8C1335A2EB0F6993@LENOVO47E041CF>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] 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, 04 Dec 2010 19:54:53 -0000

SW1vIHRoYXQgd291bGQgbWFrZSBkZWJ1Z2dpbmcgaGFyZGVyOi0pDQoNClNlbnQgZnJvbSBteSBX
aW5kb3dzIFBob25lIDchIQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSmlh
bmthbmcgWUFPDQpTZW50OiBGcmlkYXksIERlY2VtYmVyIDAzLCAyMDEwIDY6MTUgUE0NClRvOiBT
aGF3biBTdGVlbGUNCkNjOiBpbWFAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbRUFJXSA1MzM2Ymlz
DQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJvbTogU2hhd24gU3RlZWxlDQpU
bzogaW1hQGlldGYub3JnIDsgQWxleGV5IE1lbG5pa292KGFsZXhleS5tZWxuaWtvdkBpc29kZS5j
b20pDQpTZW50OiBTYXR1cmRheSwgRGVjZW1iZXIgMDQsIDIwMTAgNTowNCBBTQ0KU3ViamVjdDog
W0VBSV0gNTMzNmJpcw0KDQoNCj5JIHdhcyBhc2tlZCB0byBsb29rIGF0IDUzMzZiaXMgYSBiaXQg
bW9yZToNCg0KPlVURjhTTVRQYmlzIG5lZWRzIGZpeGVkIGV2ZXJ5d2hlcmUgKG9idmlvdXNseSku
ICBJTU8gaXQgc2hvdWxkIHN0YXkgVVRGOFNNVFAuDQo+DQo+DQoNCkkgcmVtZW1iZXIgdGhhdCBp
biB0aGUgNzggaWV0ZiBtZWV0aW5nLCB3ZSBsZWF2ZSBpdCB0byBpZXNnIHRvIGRvIGEgZmluYWwg
ZGVjaXNpb24uDQoNCg0KPg0KDQoNCg0KPg0KPjMuMyBFeHRlbmRlZCBtYWlsYm94IGFkZHJlc3Mg
c3ludGF4IHNheXM6IOKAnHRvIHBlcm1pdCBlaXRoZXIgdGhlIGRlZmluaXRpb24gYWJvdmUgb3Li
gKbigJ0gaW4gdHdvIHBsYWNlcy4gIEl0IHdvdWxkIGJlIGVhc2llciBmb3IgbWUgaWYgaXQgc2Fp
ZCDigJx0byA+cGVybWl0IGVpdGhlciB0aGUgW1JGQzUzMjFdIGRlZmluaXRpb24gYWJvdmUsIG9y
4oCm4oCdDQoNCj4NCg0KdXBkYXRlZC4NCg0KDQo+DQoNCg0KPkFCTkYgJiBJIGRvbuKAmXQgZ2V0
IGFsb25nIHdlbGwsIGJ1dCBub3RoaW5nIGp1bXBzIG91dCB0byBtZSBpbiB0aGF0IHNlY3Rpb24u
DQoNCj5JbiAzLjYuMyBJIGRvbuKAmXQgZ2V0IHdoeSByZWNlaXZlZCBmaWVsZHMgaGF2ZSB0byB1
c2UgQS1sYWJlbHMgYXQgYWxsPyAgSSBhc3N1bWUgSSBtaXNzZWQgYSBkaXNjdXNzaW9uPyAgSXQg
d291bGQgc2VlbSB0byBtZSB0aGF0IHRoZSBlbmQtcG9pbnRzIGFyZSA+YWxsIEVBSSBhd2FyZSwg
c28gaXTigJlzIHVuY2xlYXIgdG8gbWUgd2h5IEEtbGFiZWxzIGFyZSBuZWNlc3NhcnkgYW55d2hl
cmUuDQo+DQoNCklmIEkgcmVtZW1iZXIgY29ycmVjdGx5LCBJIHRoaW5rIHRoYXQgaXQgaXMgZm9y
IGVhc3kgZGVidWdnaW5nLg0KDQpKaWFua2FuZyBZYW8NCg0KPi0gU2hhd24NCg0K76Oi76OQ76On
76ObIO+jou+jo++jl++jlO+jmQ0K

From Shawn.Steele@microsoft.com  Sat Dec  4 11:59:18 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 C7DA23A6B07 for <ima@core3.amsl.com>; Sat,  4 Dec 2010 11:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.468
X-Spam-Level: 
X-Spam-Status: No, score=-10.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 I83zzTjsmF8I for <ima@core3.amsl.com>; Sat,  4 Dec 2010 11:59:18 -0800 (PST)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 1F8333A6AFB for <ima@ietf.org>; Sat,  4 Dec 2010 11:59:18 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 4 Dec 2010 11:58:22 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.42]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0255.003; Sat, 4 Dec 2010 11:58:22 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <klensin@jck.com>, "ima@ietf.org" <ima@ietf.org>
Thread-Topic: [EAI] My happiness with current drafts.
Thread-Index: AcuTPPAwPFLOICTNR4SGgzThEQolnwAdUz+AAA7XPI8=
Date: Sat, 4 Dec 2010 19:58:21 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C68487@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C66C96@TK5EX14MBXC133.redmond.corp.microsoft.com>, <9D7D0F66660154F15D0E8CD4@PST.JCK.COM>
In-Reply-To: <9D7D0F66660154F15D0E8CD4@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] My happiness with current drafts.
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, 04 Dec 2010 19:59:18 -0000

I didn't see any English errors, but I am not an abnf expert though nothing=
 obvious stood out.

Sent from my Windows Phone 7!!

-----Original Message-----
From: John C Klensin
Sent: Friday, December 03, 2010 8:54 PM
To: Shawn Steele; ima@ietf.org
Subject: Re: [EAI] My happiness with current drafts.


--On Friday, December 03, 2010 23:02 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> I just sent comments about 5336bis, I am happy with it,
> obviously the comment needs removed and UTF8SMTPbis fixed
>
> I am also happy with 5335bis, but I'm not sure that counts.
>
> I am also still happy with 4952bis
>
> I am also happy with 5337bis

Anticipating a note that will go out early next week, have you
read these drafts for clarity of expression, correct English,
and similar issues on which we are likely to get hung up if they
aren't clear and correct?   Have you checked the ABNF in all
cases, both within documents and for consistency between them?

   john




From Internet-Drafts@ietf.org  Sun Dec  5 23:45:02 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 9915C3A6A25; Sun,  5 Dec 2010 23:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.385
X-Spam-Level: 
X-Spam-Status: No, score=-102.385 tagged_above=-999 required=5 tests=[AWL=0.214, 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 JogEKWipUTZR; Sun,  5 Dec 2010 23:45:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFAAF3A69EE; Sun,  5 Dec 2010 23:45: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
X-IETF-IDTracker: 3.09
Message-ID: <20101206074501.26341.96997.idtracker@localhost>
Date: Sun, 05 Dec 2010 23:45:01 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5335bis-06.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: Mon, 06 Dec 2010 07:45:02 -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           : Internationalized Email Headers
	Author(s)       :  . Yang, S. Steele
	Filename        : draft-ietf-eai-rfc5335bis-06.txt
	Pages           : 15
	Date            : 2010-12-05

Full internationalization of electronic mail requires not only the
capabilities to transmit non-ASCII content, to encode selected
information in specific header fields, and to use non-ASCII
characters in envelope addresses.  It also requires being able to
express those addresses and the information based on them in mail
header fields.  This document specifies a variant of Internet mail
that permits the use of Unicode encoded in UTF-8, rather than ASCII,
as the base form for Internet email header field.  This form is
permitted in transmission only if authorized by an SMTP extension, as
specified in an associated specification.  This specification updates
Section 6.4 of [RFC2045] to conform with the requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5335bis-06.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-rfc5335bis-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Shawn.Steele@microsoft.com  Mon Dec  6 10:13:30 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 8F5383A685E for <ima@core3.amsl.com>; Mon,  6 Dec 2010 10:13:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.548
X-Spam-Level: 
X-Spam-Status: No, score=-9.548 tagged_above=-999 required=5 tests=[AWL=-0.808, BAYES_20=-0.74, 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 tjkklDoo8Az0 for <ima@core3.amsl.com>; Mon,  6 Dec 2010 10:13:29 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id D9E943A6822 for <ima@ietf.org>; Mon,  6 Dec 2010 10:13:29 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 6 Dec 2010 10:14:47 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.87]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0255.003; Mon, 6 Dec 2010 10:14:47 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: review of rfc5335bis-05.txt
Thread-Index: AcuVcTuYDNyc+FQsTMChGxLHbt3mTw==
Date: Mon, 6 Dec 2010 18:14:47 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10C7B70A@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.70]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] review of rfc5335bis-05.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: Mon, 06 Dec 2010 18:13:30 -0000

> BTW, it is better that Shawn can double check it.

Is there something specific you want me to focus on?

-Shawn

From yaojk@cnnic.cn  Mon Dec  6 18:07:58 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 F271C3A68E2 for <ima@core3.amsl.com>; Mon,  6 Dec 2010 18:07:57 -0800 (PST)
X-Quarantine-ID: <cvlzfcts0MOB>
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.195
X-Spam-Level: 
X-Spam-Status: No, score=-98.195 tagged_above=-999 required=5 tests=[AWL=-0.752, 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 cvlzfcts0MOB for <ima@core3.amsl.com>; Mon,  6 Dec 2010 18:07:57 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id B5C8A28C0DB for <ima@ietf.org>; Mon,  6 Dec 2010 18:07:54 -0800 (PST)
Received: (eyou send program); Tue, 07 Dec 2010 10:09:18 +0800
Message-ID: <491687758.28310@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 07 Dec 2010 10:09:18 +0800
Message-ID: <80AA5A5713E44B02BC08A9AB43D6E563@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Shawn Steele" <Shawn.Steele@microsoft.com>, <ima@ietf.org>
References: <491659302.31505@cnnic.cn>
Date: Tue, 7 Dec 2010 10:07:23 +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] review of rfc5335bis-05.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, 07 Dec 2010 02:07:58 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlNoYXduIFN0ZWVsZSIgPFNo
YXduLlN0ZWVsZUBtaWNyb3NvZnQuY29tPg0KVG86IDxpbWFAaWV0Zi5vcmc+DQpTZW50OiBUdWVz
ZGF5LCBEZWNlbWJlciAwNywgMjAxMCAyOjE0IEFNDQpTdWJqZWN0OiBSZTogW0VBSV0gcmV2aWV3
IG9mIHJmYzUzMzViaXMtMDUudHh0DQoNCg0KPj4gQlRXLCBpdCBpcyBiZXR0ZXIgdGhhdCBTaGF3
biBjYW4gZG91YmxlIGNoZWNrIGl0Lg0KPiANCj4gSXMgdGhlcmUgc29tZXRoaW5nIHNwZWNpZmlj
IHlvdSB3YW50IG1lIHRvIGZvY3VzIG9uPw0KPiANCg0KQWxleGV5IGhhcyBoZWxwZWQgdG8gY2hl
Y2sgaXQuDQoNCj4gLVNoYXduDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+IElNQSBtYWlsaW5nIGxpc3QNCj4gSU1BQGlldGYub3JnDQo+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaW1h


From jyee@ca.afilias.info  Mon Dec  6 22:02:53 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 D23133A6915 for <ima@core3.amsl.com>; Mon,  6 Dec 2010 22:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.335
X-Spam-Level: 
X-Spam-Status: No, score=-105.335 tagged_above=-999 required=5 tests=[AWL=0.929, 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 VLVFWaIiI7j9 for <ima@core3.amsl.com>; Mon,  6 Dec 2010 22:02:52 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id D0D553A6914 for <ima@ietf.org>; Mon,  6 Dec 2010 22:02:51 -0800 (PST)
From: Joseph Yee <jyee@ca.afilias.info>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 7 Dec 2010 01:04:10 -0500
Message-Id: <469A918B-77EB-4343-90E2-D80EB961ACA1@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] review of rfc5335bis-06
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, 07 Dec 2010 06:02:54 -0000

Read RFC5335bis-06, did some mind parsing of the current ABNF, this =
revision is in good shape.

Just one comment on the ABNF

Section 4.3
	qcontent       =3D/ uQcontent

The extension is not necessary.  "qcontent" used by "quoted-string" (in =
RFC5322),  and "quoted-string" used by "local-part" (RFC5322); however =
RFC5335bis replace "local-part" with "uLocal-Part".  "uLocal-Part" has =
"uQuoted-String" which can do what "quoted-string" does.  =
"quoted-string" used by "local-part" only and no where else in RFC5322.  =
"qcontent" used by "quoted-string" only too.

Since "local-part" is replaced, keeping the "qcontent =3D/ uQcontent" =
cause no harm.

Note: I have no idea how to handle the escape on UTF-8 characters now =
(or how to present it properly in ABNF) on uQuoted-Pair.  John and =
Alexey had the discussion on separate thread. =20

----
Editorial thought on ABNF
Section 4.4 has ABNF comment whenever the new definition replace or =
extend other (including self) definition.  Section 4.3 does the same on =
extension (ctext) but not replacement (comment, word).  I think it would =
be great to add ABNF comments for them, but ok if editors think it's not =
necessary.

------------
Other editorial changes

----
Section 4.2

s/downgraded/down-converted/

----
Section 4.3, 2nd paragraph (the paragraph after the first ABNF, page 6)
The text is hard to read, takes me quite some time to understand the =
impact on whole and special impact on <message-id>.

Suggested text (need more help from wordsmith, welcome all suggestions)
With these extensions defined on top of [RFC5322], the constructs build =
upon these allowed UTF-8 characters in all header values, including =
comments and quoted strings.  However, not all header values allow UTF-8 =
characters, the value of <msg-id> must be ASCII only which bounded by =
the definition of <atext> (see Section 4.5).  To accommodate such =
definitions, <atext> remains its printable-ASCII only definition for =
<msg-id>, new rule <uAtext> added for other header values which permit =
UTF-8 characters.

-----
Section 4.6, the paragraph of "Interoperability considerations" at page =
10

original text
Systems unaware of internationalized
      headers will typically treat a message/global body part as an
      unknown attachment, while they will understand the structure of a
      message/rfc822.

suggestion
All systems understand the structure of message/rfc822, and any systems =
that are unaware of internationalized headers will treat the =
message/global body part as an unknown attachment.

Changing the order makes the flow better with the following sentence.

----
Section 5, 3rd paragraph
Although the word "downgrade" is not in the paragraph, the mechanism =
described in this paragraph is downgrade.  We can reword it to how MUA & =
MSA may change address on sender's behave and yada yada yada, even so =
this is out of scope.  This paragraph does not describe the right =
concern for header-bis anymore, and need to take out on next revision.


Best,
Joseph





From yaojk@cnnic.cn  Tue Dec  7 00:12:45 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 4F9343A68F5 for <ima@core3.amsl.com>; Tue,  7 Dec 2010 00:12:45 -0800 (PST)
X-Quarantine-ID: <2HuCmSvClShn>
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.879
X-Spam-Level: 
X-Spam-Status: No, score=-99.879 tagged_above=-999 required=5 tests=[AWL=1.032, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 2HuCmSvClShn for <ima@core3.amsl.com>; Tue,  7 Dec 2010 00:12:43 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 950243A6926 for <ima@ietf.org>; Tue,  7 Dec 2010 00:12:40 -0800 (PST)
Received: (eyou send program); Tue, 07 Dec 2010 16:14:05 +0800
Message-ID: <491709645.15600@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 07 Dec 2010 16:14:05 +0800
Message-ID: <F5CAE29F190B4BCBA3C085258E66C724@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
Date: Tue, 7 Dec 2010 16:12:11 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0162_01CB9629.81546B50"
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] Fw: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
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, 07 Dec 2010 08:12:45 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0162_01CB9629.81546B50
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogRWxpb3QgTGVhciANClRvOiBk
cmFmdC1pZXRmLWVhaS1yZmM1MzM3YmlzLWRzbkB0b29scy5pZXRmLm9yZyA7IGVhaS1jaGFpcnNA
dG9vbHMuaWV0Zi5vcmcgOyBhcHBzLWRpc2N1c3NAaWV0Zi5vcmcgOyAnSUVTRycgOyBUZWQgSGFy
ZGllIA0KU2VudDogVHVlc2RheSwgRGVjZW1iZXIgMDcsIDIwMTAgMzowNyBQTQ0KU3ViamVjdDog
W2FwcHMtZGlzY3Vzc10gUmV2aWV3IG9mIGRyYWZ0LWlldGYtZWFpLXJmYzUzMzdiaXMtZHNuLTEN
Cg0KDQpJIGhhdmUgYmVlbiBzZWxlY3RlZCBhcyB0aGUgQXBwbGljYXRpb25zIEFyZWEgUmV2aWV3
IFRlYW0gcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQgKGZvciBiYWNrZ3JvdW5kIG9uIGFwcHMtcmV2
aWV3LCBwbGVhc2Ugc2VlIGh0dHA6Ly93d3cuYXBwcy5pZXRmLm9yZy9jb250ZW50L2FwcGxpY2F0
aW9ucy1hcmVhLXJldmlldy10ZWFtKS4NClBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFs
b25nIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cyB5b3UgbWF5IHJlY2VpdmUuIFBs
ZWFzZSB3YWl0IGZvciBkaXJlY3Rpb24gZnJvbSB5b3VyIGRvY3VtZW50IHNoZXBoZXJkIG9yIEFE
IGJlZm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRyYWZ0Lg0KDQpEb2N1bWVudDog
ZHJhZnQtaWV0Zi1lYWktcmZjNTMzN2Jpcy0wMQ0KVGl0bGU6IEludGVybmF0aW9uYWxpemVkIERl
bGl2ZXJ5IFN0YXR1cyBhbmQgRGlzcG9zaXRpb24gTm90aWZpY2F0aW9ucw0KUmV2aWV3ZXI6IEVs
aW90IExlYXINClJldmlldyBEYXRlOiA3IERlYyAyMDEwDQoNClN1bW1hcnk6IA0KDQpUaGlzIGRy
YWZ0IGlzIGFsbW9zdCByZWFkeSBmb3IgcHVibGljYXRpb24gYnV0IGhhcyBhIGZldyBtaW5vciBp
c3N1ZXMgdGhhdCBzaG91bGQgYmUgY29uc2lkZXJlZCBwcmlvciB0byBwdWJsaWNhdGlvbi4gIEdy
ZWF0IGpvYiENCg0KTWFqb3IgSXNzdWVzOiAgbm9uZS4gIENvb2whDQoNCk1pbm9yIElzc3VlczoN
Cg0KVGhlIGRvY3VtZW50IGRvZXMgbm90IHN0YXRlIGNsZWFybHkgd2hhdCB0aGUgZGlmZmVyZW5j
ZXMgYmV0d2VlbiB0aGlzIHNwZWNpZmljYXRpb24gYW5kIFJGQzUzMzcuICBEb2luZyBzbyBjb3Vs
ZCBzcGVlZCBhZG9wdGlvbiBvZiB0aGlzIHNwZWNpZmljYXRpb24uICBBcyBzb21lIG9mIHRoZSBj
aGFuZ2VzIHNlZW0gc3VidGxlLCBzdWNoIGFuIGFkZGl0aW9uIHdvdWxkIGJlIHBhcnRpY3VsYXJs
eSB3ZWxjb21lLg0KDQpBQk5GOiAgQ291cnRlc3kgb2YgQmlsbCBGZW5uZXIncyBBQk5GIGNoZWNr
ZXIsIHRoZXJlIGFyZSBzZXZlcmFsIGNoYW5nZXMgdGhhdCBjb3VsZCBiZSBtYWRlIGZvciBjbGFy
aXR5Og0KDQpVcHBlci1jYXNpZnkgaGV4IChlLmcuLCAyYS0+MkEpIFt0aHJvdWdob3V0XQ0KQ29t
YmluZSAiRGlhZ25vc3RpYy1Db2RlIiAiOiIgLT4gIiJEaWFnbm9zdGljLUNvZGU6Ig0KQ29tYmlu
ZSAiTG9jYWxpemVkLURpYWdub3N0aWMiICI6IiAtPiAiIkxvY2FsaXplZC1EaWFnbm9zdGljOiIN
CkNvbWJpbmUgIkZhaWx1cmUiICI6IiAtPiAiRmFpbHVyZToiDQpDb21iaW5lICJXYXJuaW5nIiAi
OiIgLT4gIldhcm5pbmc6Ig0KDQpNb3JlIGltcG9ydGFudGx5LCB0aGUgc3BlY2lmaWNhdGlvbiBt
YWtlcyB1c2Ugb2YgdGhlID0vIG9wZXJhdG9yICBmcm9tIFJGQyA1MjM0LCBidXQgZm9yIGNvbnN0
cnVjdHMgdGhhdCBpdCBkb2VzIG5vdCBjb250cm9sLiAgSSBkb24ndCBrbm93IGlmIHRoaXMgd2Fz
IHRoZSBvcmlnaW5hbCBpbnRlbnQgb3Igbm90LCBidXQgSSBhbSBhIGxpdHRsZSBjb25jZXJuZWQg
dGhhdCB1c2Ugb2YgPS8gaW4gYSBjb25zdHJ1Y3QgdGhhdCBpcyBub3Qgd2hvbGx5IGNvbnRyb2xs
ZWQgYnkgYSBzaW5nbGUgc3BlY2lmaWNhdGlvbiBpcyBhc2tpbmcgZm9yIGNvbmZ1c2lvbiBsYXRl
ci4gIFRoaXMgaXMgYW4gb3B0aW9uYWwgc3BlY2lmaWNhdGlvbiwgcmlnaHQ/DQoNCkZpbmFsbHks
IGluIHRoZSBiZWdpbm5pbmcgb2YgdGhlIGRvY3VtZW50IHlvdSBkaXNjdXNzIHdoZXRoZXIgb3Ig
bm90IHRvIGNyZWF0ZSBhIG5ldyByZWdpc3RyYXRpb24sIGFuZCBpbmRpY2F0ZSB0aGF0IHRoZSB3
b3JraW5nIGdyb3VwIGNob3NlIG5vdCB0byBjcmVhdGUgYSBuZXcgcmVnaXN0cmF0aW9uLiBJIGNh
biBlYXNpbHkgaW1hZ2luZSBnb29kIHJlYXNvbmluZyBmb3IgdGhpcywgYnV0IHBlcmhhcHMgeW91
IG1pZ2h0IGVsYWJvcmF0ZSBpbiBkZXNjcmlwdGl2ZSBsYW5ndWFnZSB0aGUgbmF0dXJlIG9mIHRo
ZSBjaG9pY2UgYW5kIHdoeSB5b3UgY2hvc2Ugb25lIHdheSByYXRoZXIgdGhhbiB0aGUgb3RoZXIs
IGVzcGVjaWFsbHkgaW4gbGlnaHQgb2Ygd2hhdCBtYXkgc2VlbSBsaWtlIGEgY29udHJhcnkgZGVj
aXNpb24gaW4gNTMzNmJpcy4NCg0KUmVnYXJkcywNCg0KRWxpb3QNCg0KDQoNCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCmFwcHMtZGlzY3VzcyBtYWlsaW5nIGxpc3QNCmFwcHMtZGlzY3Vzc0BpZXRmLm9y
Zw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hcHBzLWRpc2N1c3MNCg==

------=_NextPart_000_0162_01CB9629.81546B50
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0
PVVURi04IiBodHRwLWVxdWl2PWNvbnRlbnQtdHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNv
bnRlbnQ9Ik1TSFRNTCA4LjAwLjYwMDEuMTg5NzUiPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+
DQo8Qk9EWSBiZ0NvbG9yPSNmZmZmZmYgdGV4dD0jMDAwMDAwPg0KPERJVj48Rk9OVCBzaXplPTIg
ZmFjZT3lrovkvZM+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVDogOXB0IOWu
i+S9kyI+LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCjxESVYgc3R5bGU9IkJBQ0tHUk9V
TkQ6ICNlNGU0ZTQ7IGZvbnQtY29sb3I6IGJsYWNrIj48Qj5Gcm9tOjwvQj4gPEEgDQp0aXRsZT1s
ZWFyQGNpc2NvLmNvbSBocmVmPSJtYWlsdG86bGVhckBjaXNjby5jb20iPkVsaW90IExlYXI8L0E+
IDwvRElWPg0KPERJVj48Qj5Ubzo8L0I+IDxBIHRpdGxlPWRyYWZ0LWlldGYtZWFpLXJmYzUzMzdi
aXMtZHNuQHRvb2xzLmlldGYub3JnIA0KaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtZWFpLXJmYzUz
MzdiaXMtZHNuQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWVhaS1yZmM1MzM3YmlzLWRzbkB0
b29scy5pZXRmLm9yZzwvQT4gDQo7IDxBIHRpdGxlPWVhaS1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcg
DQpocmVmPSJtYWlsdG86ZWFpLWNoYWlyc0B0b29scy5pZXRmLm9yZyI+ZWFpLWNoYWlyc0B0b29s
cy5pZXRmLm9yZzwvQT4gOyA8QSANCnRpdGxlPWFwcHMtZGlzY3Vzc0BpZXRmLm9yZyANCmhyZWY9
Im1haWx0bzphcHBzLWRpc2N1c3NAaWV0Zi5vcmciPmFwcHMtZGlzY3Vzc0BpZXRmLm9yZzwvQT4g
OyA8QSANCnRpdGxlPWllc2dAaWV0Zi5vcmcgaHJlZj0ibWFpbHRvOmllc2dAaWV0Zi5vcmciPidJ
RVNHJzwvQT4gOyA8QSANCnRpdGxlPWhhcmRpZUBxdWFsY29tbS5jb20gaHJlZj0ibWFpbHRvOmhh
cmRpZUBxdWFsY29tbS5jb20iPlRlZCBIYXJkaWU8L0E+IA0KPC9ESVY+DQo8RElWPjxCPlNlbnQ6
PC9CPiBUdWVzZGF5LCBEZWNlbWJlciAwNywgMjAxMCAzOjA3IFBNPC9ESVY+DQo8RElWPjxCPlN1
YmplY3Q6PC9CPiBbYXBwcy1kaXNjdXNzXSBSZXZpZXcgb2YgDQpkcmFmdC1pZXRmLWVhaS1yZmM1
MzM3YmlzLWRzbi0xPC9ESVY+PC9ESVY+DQo8RElWPjxCUj48L0RJVj5JIGhhdmUgYmVlbiBzZWxl
Y3RlZCBhcyB0aGUgQXBwbGljYXRpb25zIEFyZWEgUmV2aWV3IFRlYW0gDQpyZXZpZXdlciBmb3Ig
dGhpcyBkcmFmdCAoZm9yIGJhY2tncm91bmQgb24gYXBwcy1yZXZpZXcsIHBsZWFzZSBzZWUgPEEg
DQp0aXRsZT1odHRwOi8vd3d3LmFwcHMuaWV0Zi5vcmcvY29udGVudC9hcHBsaWNhdGlvbnMtYXJl
YS1yZXZpZXctdGVhbSANCmhyZWY9Imh0dHA6Ly93d3cuYXBwcy5pZXRmLm9yZy9jb250ZW50L2Fw
cGxpY2F0aW9ucy1hcmVhLXJldmlldy10ZWFtIj5odHRwOi8vd3d3LmFwcHMuaWV0Zi5vcmcvY29u
dGVudC9hcHBsaWNhdGlvbnMtYXJlYS1yZXZpZXctdGVhbTwvQT4pLjxCUj5QbGVhc2UgDQpyZXNv
bHZlIHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50
cyB5b3UgbWF5IHJlY2VpdmUuIA0KUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIg
ZG9jdW1lbnQgc2hlcGhlcmQgb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgDQp2ZXJzaW9uIG9m
IHRoZSBkcmFmdC48QlI+PEJSPkRvY3VtZW50OiBkcmFmdC1pZXRmLWVhaS1yZmM1MzM3YmlzLTAx
PEJSPlRpdGxlOiANCkludGVybmF0aW9uYWxpemVkIERlbGl2ZXJ5IFN0YXR1cyBhbmQgRGlzcG9z
aXRpb24gTm90aWZpY2F0aW9uczxCUj5SZXZpZXdlcjogDQpFbGlvdCBMZWFyPEJSPlJldmlldyBE
YXRlOiA3IERlYyAyMDEwPEJSPjxCUj5TdW1tYXJ5OiA8QlI+PEJSPlRoaXMgZHJhZnQgaXMgDQph
bG1vc3QgcmVhZHkgZm9yIHB1YmxpY2F0aW9uIGJ1dCBoYXMgYSBmZXcgPEI+bWlub3I8L0I+IGlz
c3VlcyB0aGF0IHNob3VsZCBiZSANCmNvbnNpZGVyZWQgcHJpb3IgdG8gcHVibGljYXRpb24uJm5i
c3A7IEdyZWF0IGpvYiE8QlI+PEJSPk1ham9yIElzc3VlczombmJzcDsgDQpub25lLiZuYnNwOyBD
b29sITxCUj48QlI+TWlub3IgSXNzdWVzOjxCUj48QlI+VGhlIGRvY3VtZW50IGRvZXMgbm90IHN0
YXRlIA0KY2xlYXJseSB3aGF0IHRoZSBkaWZmZXJlbmNlcyBiZXR3ZWVuIHRoaXMgc3BlY2lmaWNh
dGlvbiBhbmQgUkZDNTMzNy4mbmJzcDsgRG9pbmcgDQpzbyBjb3VsZCBzcGVlZCBhZG9wdGlvbiBv
ZiB0aGlzIHNwZWNpZmljYXRpb24uJm5ic3A7IEFzIHNvbWUgb2YgdGhlIGNoYW5nZXMgc2VlbSAN
CnN1YnRsZSwgc3VjaCBhbiBhZGRpdGlvbiB3b3VsZCBiZSBwYXJ0aWN1bGFybHkgd2VsY29tZS48
QlI+PEJSPkFCTkY6Jm5ic3A7IA0KQ291cnRlc3kgb2YgQmlsbCBGZW5uZXIncyBBQk5GIGNoZWNr
ZXIsIHRoZXJlIGFyZSBzZXZlcmFsIGNoYW5nZXMgdGhhdCBjb3VsZCBiZSANCm1hZGUgZm9yIGNs
YXJpdHk6PEJSPjxCUj5VcHBlci1jYXNpZnkgaGV4IChlLmcuLCAyYS0mZ3Q7MkEpIA0KW3Rocm91
Z2hvdXRdPEJSPkNvbWJpbmUgIkRpYWdub3N0aWMtQ29kZSIgIjoiIC0mZ3Q7IA0KIiJEaWFnbm9z
dGljLUNvZGU6IjxCUj5Db21iaW5lICJMb2NhbGl6ZWQtRGlhZ25vc3RpYyIgIjoiIC0mZ3Q7IA0K
IiJMb2NhbGl6ZWQtRGlhZ25vc3RpYzoiPEJSPkNvbWJpbmUgIkZhaWx1cmUiICI6IiAtJmd0OyAi
RmFpbHVyZToiPEJSPkNvbWJpbmUgDQoiV2FybmluZyIgIjoiIC0mZ3Q7ICJXYXJuaW5nOiI8QlI+
PEJSPk1vcmUgaW1wb3J0YW50bHksIHRoZSBzcGVjaWZpY2F0aW9uIG1ha2VzIA0KdXNlIG9mIHRo
ZSA9LyBvcGVyYXRvciZuYnNwOyBmcm9tIFJGQyA1MjM0LCBidXQgZm9yIGNvbnN0cnVjdHMgdGhh
dCBpdCBkb2VzIG5vdCANCmNvbnRyb2wuJm5ic3A7IEkgZG9uJ3Qga25vdyBpZiB0aGlzIHdhcyB0
aGUgb3JpZ2luYWwgaW50ZW50IG9yIG5vdCwgYnV0IEkgYW0gYSANCmxpdHRsZSBjb25jZXJuZWQg
dGhhdCB1c2Ugb2YgPS8gaW4gYSBjb25zdHJ1Y3QgdGhhdCBpcyBub3Qgd2hvbGx5IGNvbnRyb2xs
ZWQgYnkgDQphIHNpbmdsZSBzcGVjaWZpY2F0aW9uIGlzIGFza2luZyBmb3IgY29uZnVzaW9uIGxh
dGVyLiZuYnNwOyBUaGlzIGlzIGFuIG9wdGlvbmFsIA0Kc3BlY2lmaWNhdGlvbiwgcmlnaHQ/PEJS
PjxCUj5GaW5hbGx5LCBpbiB0aGUgYmVnaW5uaW5nIG9mIHRoZSBkb2N1bWVudCB5b3UgDQpkaXNj
dXNzIHdoZXRoZXIgb3Igbm90IHRvIGNyZWF0ZSBhIG5ldyByZWdpc3RyYXRpb24sIGFuZCBpbmRp
Y2F0ZSB0aGF0IHRoZSANCndvcmtpbmcgZ3JvdXAgY2hvc2Ugbm90IHRvIGNyZWF0ZSBhIG5ldyBy
ZWdpc3RyYXRpb24uIEkgY2FuIGVhc2lseSBpbWFnaW5lIGdvb2QgDQpyZWFzb25pbmcgZm9yIHRo
aXMsIGJ1dCBwZXJoYXBzIHlvdSBtaWdodCBlbGFib3JhdGUgaW4gZGVzY3JpcHRpdmUgbGFuZ3Vh
Z2UgdGhlIA0KbmF0dXJlIG9mIHRoZSBjaG9pY2UgYW5kIHdoeSB5b3UgY2hvc2Ugb25lIHdheSBy
YXRoZXIgdGhhbiB0aGUgb3RoZXIsIGVzcGVjaWFsbHkgDQppbiBsaWdodCBvZiB3aGF0IG1heSBz
ZWVtIGxpa2UgYSBjb250cmFyeSBkZWNpc2lvbiBpbiANCjUzMzZiaXMuPEJSPjxCUj5SZWdhcmRz
LDxCUj48QlI+RWxpb3Q8QlI+DQo8UD4NCjxIUj4NCg0KPFA+PC9QPl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPmFwcHMtZGlzY3VzcyBtYWlsaW5nIA0K
bGlzdDxCUj5hcHBzLWRpc2N1c3NAaWV0Zi5vcmc8QlI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9hcHBzLWRpc2N1c3M8QlI+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0162_01CB9629.81546B50--


From Internet-Drafts@ietf.org  Tue Dec  7 10:45: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 3D01F3A696A; Tue,  7 Dec 2010 10:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 eKQsBjj5irLE; Tue,  7 Dec 2010 10:45:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59FA53A686A; Tue,  7 Dec 2010 10:45:02 -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
X-IETF-IDTracker: 3.09
Message-ID: <20101207184502.16456.8738.idtracker@localhost>
Date: Tue, 07 Dec 2010 10:45:02 -0800
Cc: ima@ietf.org
Subject: [EAI] I-D Action:draft-ietf-eai-rfc5335bis-07.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, 07 Dec 2010 18:45: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           : Internationalized Email Headers
	Author(s)       :  . Yang, S. Steele
	Filename        : draft-ietf-eai-rfc5335bis-07.txt
	Pages           : 15
	Date            : 2010-12-07

Full internationalization of electronic mail requires not only the
capabilities to transmit non-ASCII content, to encode selected
information in specific header fields, and to use non-ASCII
characters in envelope addresses.  It also requires being able to
express those addresses and the information based on them in mail
header fields.  This document specifies a variant of Internet mail
that permits the use of Unicode encoded in UTF-8, rather than ASCII,
as the base form for Internet email header field.  This form is
permitted in transmission only if authorized by an SMTP extension, as
specified in an associated specification.  This specification updates
Section 6.4 of [RFC2045] to conform with the requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-rfc5335bis-07.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-rfc5335bis-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From yaojk@cnnic.cn  Sun Dec 12 16:37:09 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 7BC713A6D50 for <ima@core3.amsl.com>; Sun, 12 Dec 2010 16:37:09 -0800 (PST)
X-Quarantine-ID: <pTSIES7QJpq8>
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.166
X-Spam-Level: 
X-Spam-Status: No, score=-98.166 tagged_above=-999 required=5 tests=[AWL=-0.719, BAYES_00=-2.599, HS_FORGED_OE_FW=2.595, 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 pTSIES7QJpq8 for <ima@core3.amsl.com>; Sun, 12 Dec 2010 16:37:08 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 9A8F23A6D16 for <ima@ietf.org>; Sun, 12 Dec 2010 16:37:06 -0800 (PST)
Received: (eyou send program); Mon, 13 Dec 2010 08:38:42 +0800
Message-ID: <492200722.01880@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 13 Dec 2010 08:38:42 +0800
Message-ID: <DEC4A98A41644D448F8E4C912F20BB6F@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
Date: Mon, 13 Dec 2010 08:38:48 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0286_01CB9AA1.29613640"
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] FW:Re: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
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, 13 Dec 2010 00:37:09 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0286_01CB9AA1.29613640
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0287_01CB9AA1.29613640"


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

Znlp

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

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBuYW1lPUdFTkVSQVRPUiBjb250
ZW50PSJNU0hUTUwgOC4wMC42MDAxLjE4OTc1Ij4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFEPg0K
PEJPRFkgYmdDb2xvcj0jY2NlOGNmPg0KPERJVj48Rk9OVCBzaXplPTI+ZnlpPC9GT05UPjwvRElW
PjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_001_0287_01CB9AA1.29613640--

------=_NextPart_000_0286_01CB9AA1.29613640
Content-Type: message/rfc822;
	name="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"

Received: (eyou send program); Mon, 13 Dec 2010 06:14:38 +0800
Message-ID: <492192078.17045@cnnic.cn>
Received: from unknown (HELO ironportc370m.cnnic.cn) (218.241.99.160)
 by 159.226.7.146 with SMTP; Mon, 13 Dec 2010 06:14:38 +0800
X-IronPort-AV: E=Sophos;i="4.59,333,1288540800"; 
   d="scan'208";a="123417"
Received: from mail.ietf.org ([64.170.98.32])
  by ironportc370m.cnnic.cn with ESMTP; 13 Dec 2010 06:14:36 +0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9C1E28B56A;
	Sun, 12 Dec 2010 13:57:50 -0800 (PST)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B28693A6E74
	for <apps-discuss@core3.amsl.com>; Sun, 12 Dec 2010 13:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.072
X-Spam-Level: 
X-Spam-Status: No, score=-110.072 tagged_above=-999 required=5
	tests=[AWL=0.527, 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 fLTviKxItMDI for <apps-discuss@core3.amsl.com>;
	Sun, 12 Dec 2010 13:57:48 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id A583C3A6E62
	for <discuss@apps.ietf.org>; Sun, 12 Dec 2010 13:57:47 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com;
	dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAEADfUBE2Q/khLgWdsb2JhbACDXKAqFQEBFiIppgmKSY9RgSGDNXQEink
X-IronPort-AV: E=Sophos;i="4.59,333,1288569600"; d="scan'208";a="71478366"
Received: from ams-core-2.cisco.com ([144.254.72.75])
	by ams-iport-1.cisco.com with ESMTP; 12 Dec 2010 21:59:23 +0000
Received: from ams3-vpn-dhcp4641.cisco.com (ams3-vpn-dhcp4641.cisco.com
	[10.61.82.32])
	by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id oBCLxN3J014633;
	Sun, 12 Dec 2010 21:59:23 GMT
Message-ID: <4D0545C5.5040608@cisco.com>
Date: Sun, 12 Dec 2010 22:59:33 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
	rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>
References: <252f1508ca393ec830c24fdf94d19cb5@gandalf.orthanc.ca>
In-Reply-To: <252f1508ca393ec830c24fdf94d19cb5@gandalf.orthanc.ca>
X-Enigmail-Version: 1.1.1
Cc: draft-ietf-eai-rfc5337bis-dsn@tools.ietf.org, discuss@apps.ietf.org,
	iesg@ietf.org, apps-review@ietf.org
Subject: Re: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols
	<apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org



On 12/12/10 10:48 PM, Lyndon Nerenberg (VE6BBM/VE7TFX) wrote:
> The base IMAP RFC (3501) made this construct easy and (I think)
> relatively obvious.  YMMV.  If a grammar extension is globally
> applicable to a parent specification, I think the subject document
> reads easier if the extension is called out at the top of the grammar,
> rather than littering each ABNF element with a callout comment.  The
> alternatives can get very noisy, especially if there is multiple
> inheritance involved.

I take your point but then if you are calling out multiple
specifications someone has to go on a fishing expedition to understand
perhaps the single definition they want out of a specification.

Eliot
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss
------=_NextPart_000_0286_01CB9AA1.29613640
Content-Type: message/rfc822;
	name="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"

Received: (eyou send program); Mon, 13 Dec 2010 05:49:00 +0800
Message-ID: <492190540.17013@cnnic.cn>
Received: from unknown (HELO ironportc370m.cnnic.cn) (218.241.99.160)
 by 159.226.7.146 with SMTP; Mon, 13 Dec 2010 05:49:00 +0800
X-IronPort-AV: E=Sophos;i="4.59,333,1288540800"; 
   d="scan'208";a="123332"
Received: from mail.ietf.org ([64.170.98.32])
  by ironportc370m.cnnic.cn with ESMTP; 13 Dec 2010 05:48:59 +0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C30E3A6D38;
	Sun, 12 Dec 2010 13:47:20 -0800 (PST)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 61CF83A6D0C
	for <apps-discuss@core3.amsl.com>; Sun, 12 Dec 2010 13:47:19 -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 0xDB1FWaI1uy for <apps-discuss@core3.amsl.com>;
	Sun, 12 Dec 2010 13:47:18 -0800 (PST)
Received: from orthanc.ca (ve6bbm-1-pt.tunnel.tserv13.ash1.ipv6.he.net
	[IPv6:2001:470:7:139::2])
	by core3.amsl.com (Postfix) with ESMTP id 764C33A6CEE
	for <discuss@apps.ietf.org>; Sun, 12 Dec 2010 13:47:18 -0800 (PST)
Received: from orthanc.ca (localhost [127.0.0.1])
	by orthanc.ca (8.14.4/8.14.4) with ESMTP id oBCLmqAU082703
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 12 Dec 2010 13:48:52 -0800 (PST)
	(envelope-from lyndon@gandalf.orthanc.ca)
Received: (from uucp@localhost)
	by orthanc.ca (8.14.4/8.14.4/Submit) with UUCP id oBCLmq5e082702;
	Sun, 12 Dec 2010 13:48:52 -0800 (PST)
	(envelope-from lyndon@gandalf.orthanc.ca)
Received: from gandalf.orthanc.ca (frodo.orthanc.ca [172.16.0.3])
	by legolas.orthanc.ca (8.14.4/8.14.4) with ESMTP id oBCLmnE4051762;
	Sun, 12 Dec 2010 13:48:49 -0800 (PST)
	(envelope-from lyndon@gandalf.orthanc.ca)
Message-ID: <252f1508ca393ec830c24fdf94d19cb5@gandalf.orthanc.ca>
To: dhc@dcrocker.net, draft-ietf-eai-rfc5337bis-dsn@tools.ietf.org
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca>
Date: Sun, 12 Dec 2010 13:48:48 -0800
In-Reply-To: <4D050373.40406@dcrocker.net>
MIME-Version: 1.0
Cc: discuss@apps.ietf.org, iesg@ietf.org, apps-review@ietf.org
Subject: Re: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols
	<apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org

> So I suggest having a citation for the original version of the rule be included 
> in a comment associated with the new rule.
> 
> For example:
> 
>       generic-address =/ utf-8-enc-addr
>                         ; updates Section 3.2.3 of [RFC3798]

FWIW, this is what I did for IMAP Binary (3516); it doesn't seem to have
caused any confusion:

  7.  Formal Protocol Syntax

   The following syntax specification uses the augmented Backus-Naur
   Form (ABNF) notation as used in [ABNF], and incorporates by reference
   the Core Rules defined in that document.

   This syntax augments the grammar specified in [IMAP4rev1].

   append         =/  "APPEND" SP mailbox [SP flag-list]
                      [SP date-time] SP literal8

   fetch-att      =/  "BINARY" [".PEEK"] section-binary [partial]
                      / "BINARY.SIZE" section-binary

   literal8       =   "~{" number "}" CRLF *OCTET
                      ; <number> represents the number of OCTETs
                      ; in the response string.

   msg-att-static =/  "BINARY" section-binary SP (nstring / literal8)
                      / "BINARY.SIZE" section-binary SP number

   partial        =   "<" number "." nz-number ">"

   resp-text-code =/  "UNKNOWN-CTE"

   section-binary =   "[" [section-part] "]"

The base IMAP RFC (3501) made this construct easy and (I think)
relatively obvious.  YMMV.  If a grammar extension is globally
applicable to a parent specification, I think the subject document
reads easier if the extension is called out at the top of the grammar,
rather than littering each ABNF element with a callout comment.  The
alternatives can get very noisy, especially if there is multiple
inheritance involved.

--lyndon

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss
------=_NextPart_000_0286_01CB9AA1.29613640
Content-Type: message/rfc822;
	name="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"

Received: (eyou send program); Mon, 13 Dec 2010 01:17:41 +0800
Message-ID: <492174261.24001@cnnic.cn>
Received: from unknown (HELO ironportc370m.cnnic.cn) (218.241.99.160)
 by 159.226.7.146 with SMTP; Mon, 13 Dec 2010 01:17:41 +0800
X-IronPort-AV: E=Sophos;i="4.59,333,1288540800"; 
   d="scan'208";a="122206"
Received: from mail.ietf.org ([64.170.98.32])
  by ironportc370m.cnnic.cn with ESMTP; 13 Dec 2010 01:17:40 +0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FAEB3A6DFA;
	Sun, 12 Dec 2010 09:15:10 -0800 (PST)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 431C83A6DEC;
	Sun, 12 Dec 2010 09:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VoAuPyNymyLN; Sun, 12 Dec 2010 09:15:05 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17])
	by core3.amsl.com (Postfix) with ESMTP id EA2653A6DE5;
	Sun, 12 Dec 2010 09:15:04 -0800 (PST)
Received: from [192.168.1.2] (ppp-67-124-89-109.dsl.pltn13.pacbell.net
	[67.124.89.109]) (authenticated bits=0)
	by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBCHGZi5026913
	(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);
	Sun, 12 Dec 2010 09:16:40 -0800
Message-ID: <4D050373.40406@dcrocker.net>
Date: Sun, 12 Dec 2010 09:16:35 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: draft-ietf-eai-rfc5337bis-dsn@tools.ietf.org
References: <4CFDDD2F.2020201@cisco.com> <4D04FB1A.6030804@cisco.com>
In-Reply-To: <4D04FB1A.6030804@cisco.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(sbh17.songbird.com [72.52.113.17]);
	Sun, 12 Dec 2010 09:16:41 -0800 (PST)
Cc: Apps Discuss <discuss@apps.ietf.org>, 'IESG' <iesg@ietf.org>,
	"apps-review@ietf.org" <apps-review@ietf.org>
Subject: Re: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols
	<apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org



On 12/12/2010 8:40 AM, Eliot Lear wrote:
>> More importantly, the specification makes use of the =/ operator  from RFC
>> 5234, but for constructs that it does not control.  I don't know if this was
>> the original intent or not, but I am a little concerned that use of =/ in a
>> construct that is not wholly controlled by a single specification is asking
>> for confusion later.  This is an optional specification, right?
>
> After discussing this a bit with Dave Crocker, perhaps this problem is all in my
> head.  Therefore, I recommend no change to the spec on this point.


While I believe the current specification's use of =/ is not only legal but that 
it is in fact exactly the sort of use that was intended, I also note that it's a 
pretty unusual ABNF construct and that it might invite some confusion. 
Cross-referencing a rule from another specification strikes me as a big deal and 
that it's worth helping the reader as much as possible.

So I suggest having a citation for the original version of the rule be included 
in a comment associated with the new rule.

For example:

      generic-address =/ utf-8-enc-addr
                        ; updates Section 3.2.3 of [RFC3798]

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss
------=_NextPart_000_0286_01CB9AA1.29613640
Content-Type: message/rfc822;
	name="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Re_ [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1.eml"

Received: (eyou send program); Mon, 13 Dec 2010 00:40:56 +0800
Message-ID: <492172056.28336@cnnic.cn>
Received: from unknown (HELO ironportc370m.cnnic.cn) (218.241.99.160)
 by 159.226.7.146 with SMTP; Mon, 13 Dec 2010 00:40:56 +0800
X-IronPort-AV: E=Sophos;i="4.59,332,1288540800"; 
   d="scan'208,217";a="121998"
Received: from mail.ietf.org ([64.170.98.32])
  by ironportc370m.cnnic.cn with ESMTP; 13 Dec 2010 00:40:55 +0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A5DB28C0F3;
	Sun, 12 Dec 2010 08:39:15 -0800 (PST)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12DBF28C0E6
	for <apps-discuss@core3.amsl.com>; Sun, 12 Dec 2010 08:39:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.015
X-Spam-Level: 
X-Spam-Status: No, score=-110.015 tagged_above=-999 required=5
	tests=[AWL=0.583, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	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 fZe0-Cah95PK for <apps-discuss@core3.amsl.com>;
	Sun, 12 Dec 2010 08:39:13 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141])
	by core3.amsl.com (Postfix) with ESMTP id DD05428C0D7
	for <discuss@apps.ietf.org>; Sun, 12 Dec 2010 08:39:12 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com;
	dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.59,332,1288569600"; d="scan'208,217";a="15107511"
Received: from ams-core-2.cisco.com ([144.254.72.75])
	by ams-iport-2.cisco.com with ESMTP; 12 Dec 2010 16:40:48 +0000
Received: from ams3-vpn-dhcp4641.cisco.com (ams3-vpn-dhcp4641.cisco.com
	[10.61.82.32])
	by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id oBCGel7F004241;
	Sun, 12 Dec 2010 16:40:47 GMT
Message-ID: <4D04FB1A.6030804@cisco.com>
Date: Sun, 12 Dec 2010 17:40:58 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
	rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Apps Discuss <discuss@apps.ietf.org>,
	"apps-review@ietf.org" <apps-review@ietf.org>,
	draft-ietf-eai-rfc5337bis-dsn@tools.ietf.org, "'IESG'" <iesg@ietf.org>
References: <4CFDDD2F.2020201@cisco.com>
In-Reply-To: <4CFDDD2F.2020201@cisco.com>
X-Enigmail-Version: 1.1.1
Subject: Re: [apps-discuss] Review of draft-ietf-eai-rfc5337bis-dsn-1
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols
	<apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>,
	<mailto:apps-discuss-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0867400071=="
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0867400071==
Content-Type: multipart/alternative;
 boundary="------------020207080800030402090202"

This is a multi-part message in MIME format.
--------------020207080800030402090202
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I wrote:

On 12/7/10 8:07 AM, Eliot Lear wrote:
> I have been selected as the Applications Area Review Team reviewer for
> this draft (for background on apps-review, please see
> http://www.apps.ietf.org/content/applications-area-review-team).
> Please resolve these comments along with any other Last Call comments
> you may receive. Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-ietf-eai-rfc5337bis-01
> Title: Internationalized Delivery Status and Disposition Notifications
> Reviewer: Eliot Lear
> Review Date: 7 Dec 2010
>

..

> More importantly, the specification makes use of the =/ operator  from
> RFC 5234, but for constructs that it does not control.  I don't know
> if this was the original intent or not, but I am a little concerned
> that use of =/ in a construct that is not wholly controlled by a
> single specification is asking for confusion later.  This is an
> optional specification, right?

After discussing this a bit with Dave Crocker, perhaps this problem is
all in my head.  Therefore, I recommend no change to the spec on this point.

Eliot

--------------020207080800030402090202
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    I wrote:<br>
    <br>
    On 12/7/10 8:07 AM, Eliot Lear wrote:
    <blockquote cite="mid:4CFDDD2F.2020201@cisco.com" type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      I have been selected as the Applications Area Review Team reviewer
      for this draft (for background on apps-review, please see <a
        moz-do-not-send="true"
        href="http://www.apps.ietf.org/content/applications-area-review-team"
title="http://www.apps.ietf.org/content/applications-area-review-team">http://www.apps.ietf.org/content/applications-area-review-team</a>).<br>
      Please resolve these comments along with any other Last Call
      comments you may receive. Please wait for direction from your
      document shepherd or AD before posting a new version of the draft.<br>
      <br>
      Document: draft-ietf-eai-rfc5337bis-01<br>
      Title: Internationalized Delivery Status and Disposition
      Notifications<br>
      Reviewer: Eliot Lear<br>
      Review Date: 7 Dec 2010<br>
      <br>
    </blockquote>
    <br>
    ...<br>
    <br>
    <blockquote cite="mid:4CFDDD2F.2020201@cisco.com" type="cite"> More
      importantly, the specification makes use of the =/ operatorÂ  from
      RFC 5234, but for constructs that it does not control.Â  I don't
      know if this was the original intent or not, but I am a little
      concerned that use of =/ in a construct that is not wholly
      controlled by a single specification is asking for confusion
      later.Â  This is an optional specification, right?<br>
    </blockquote>
    <br>
    After discussing this a bit with Dave Crocker, perhaps this problem
    is all in my head.Â  Therefore, I recommend no change to the spec on
    this point.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------020207080800030402090202--

--===============0867400071==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss

--===============0867400071==--
------=_NextPart_000_0286_01CB9AA1.29613640--


From yaojk@cnnic.cn  Wed Dec 15 16:55:04 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 CE2BC28C12C for <ima@core3.amsl.com>; Wed, 15 Dec 2010 16:55:04 -0800 (PST)
X-Quarantine-ID: <ShYzYxo6n6dV>
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.424
X-Spam-Level: 
X-Spam-Status: No, score=-99.424 tagged_above=-999 required=5 tests=[AWL=0.619, 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 ShYzYxo6n6dV for <ima@core3.amsl.com>; Wed, 15 Dec 2010 16:55:04 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 7424A28C0EC for <ima@ietf.org>; Wed, 15 Dec 2010 16:55:03 -0800 (PST)
Received: (eyou send program); Thu, 16 Dec 2010 08:56:45 +0800
Message-ID: <492461005.02134@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, 16 Dec 2010 08:56:45 +0800
Message-ID: <652CD190BA6C4FAABF95456B7B76B97A@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
Date: Thu, 16 Dec 2010 08:56:57 +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] Fw: [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.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: Thu, 16 Dec 2010 00:55:04 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlRlZCBIYXJkaWUiIDx0ZWQu
aWV0ZkBnbWFpbC5jb20+DQpUbzogPGFwcHMtZGlzY3Vzc0BpZXRmLm9yZz47ICJBbGV4ZXkgTWVs
bmlrb3YiIDxhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29tPjsgIlBldGVyIFNhaW50LUFuZHJlIiA8
c3RwZXRlckBzdHBldGVyLmltPjsgPHRvbnkrZWFpZHNuQG1haWxsZW5uaXVtLmF0dC5jb20+OyA8
Y2hyaXMubmV3bWFuQG9yYWNsZS5jb20+DQpTZW50OiBUaHVyc2RheSwgRGVjZW1iZXIgMTYsIDIw
MTAgNDozMCBBTQ0KU3ViamVjdDogW2FwcHMtZGlzY3Vzc10gZHJhZnQtaWV0Zi1lYWktcmZjNTMz
N2Jpcy1kc24tMDEudHh0DQoNCg0KSSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgYW4gQXBwbGljYXRp
b25zIEFyZWEgUmV2aWV3IFRlYW0gcmV2aWV3ZXIgZm9yDQp0aGlzIGRyYWZ0IChmb3IgYmFja2dy
b3VuZCBvbiBhcHBzLXJldmlldywgcGxlYXNlIHNlZQ0KaHR0cDovL3d3dy5hcHBzLmlldGYub3Jn
L2NvbnRlbnQvYXBwbGljYXRpb25zLWFyZWEtcmV2aWV3LXRlYW0pOyBub3RlDQp0aGF0IEVsaW90
IExlYXIgaXMgYWxzbyByZXZpZXdpbmcgdGhpcyBkcmFmdCBhcyBwYXJ0IG9mIHRoaXMNClRlYW0u
DQoNClBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90aGVyIExh
c3QgQ2FsbCBjb21tZW50cw0KeW91IG1heSByZWNlaXZlLiBQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0
aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBu
ZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLWVhaS1yZmM1
MzM3YmlzLWRzbi0wMS50eHQNClRpdGxlOiBJbnRlcm5hdGlvbmFsaXplZCBEZWxpdmVyeSBTdGF0
dXMgYW5kIERpc3Bvc2l0aW9uIE5vdGlmaWNhdGlvbnMNClJldmlld2VyOiBUZWQgSGFyZGllDQpS
ZXZpZXcgRGF0ZTogRGVjZW1iZXIgMTUsIDIwMTANCg0KDQpTdW1tYXJ5OiBSZXZpZXdlcnMgd2Vy
ZSBhc2tlZCB0byBsb29rIHNwZWNpZmljYWxseSBhdCB0aGUgQUJORjsgaXQNCmFwcGVhcnMgdG8g
bWUgY29ycmVjdCBhbmQgdGhlIG91dHB1dCBmcm9tIGFibmZnZW4gc2VlbWVkIHNlbnNpYmxlLg0K
RWxpb3QgYW5kIERhdmUgQ3JvY2tlciBoYXZlIGFscmVhZHkgZGlzY3Vzc2VkIHRoZSBjaXRhdGlv
biBpc3N1ZS4NClRoZXJlIGFyZSB0d28gb3RoZXIgaXNzdWVzIHdoaWNoIEkgZmVlbCBzaG91bGQg
YmUgcmVzb2x2ZWQuDQoNCk1ham9yIElzc3VlczogVGhlIGRvY3VtZW50IHNheXM6DQoNCk5PVEU6
IFRoZSBvbmx5IGlzc3VlIGZvciB3aGljaCB0aGVyZSBpcyAoYXMgeWV0KSBubyBjb25zZW5zdXMg
eWV0IGlzDQogICB3aGV0aGVyIHRvIGNoYW5nZSB0aGUgbmFtZSBvZiB0aGUgQWRkcmVzcyBUeXBl
IGZyb20gIlVURi04IiB0bw0KICAgc29tZXRoaW5nIGRpZmZlcmVudCwgc3VjaCBhcyAiVVRGOCIs
IHRvIHJlZmxlY3QgdGhlIGZhY3QgdGhhdCB0aGUNCiAgICI8YWRkciA8YWRkcj4+IiBhZGRyZXNz
IHN5bnRheCBpcyBubyBsb25nZXIgcGVybWl0dGVkLg0KDQpSZXZpZXdpbmcgdGhlIG1haWxpbmcg
bGlzdCB0aGVyZSBhcHBlYXJlZCB0byBiZSBvbmUgcGFydGljaXBhbnQgYWR2b2NhdGluZw0KY2hh
bmdlIChTTSkgYW5kIG9uZSAibm90IGFuIGV4Y2l0aW5nIHF1ZXN0aW9uIiAoU2hhd24gU3RlZWxl
KSBhbmQgb25lDQpub3RpbmcgYSBwcm9ibGVtIHdpdGggY2hhbmdpbmcgaXQgKE1hcnRpbiBE/HJz
dCkuICA1MzM1YmlzIGluIHRoZQ0KY3VycmVudCB2ZXJzaW9uDQpzdGlsbCBjYWxscyB0aGlzIFVU
Ri04OyBJIGJlbGlldmUgdGhhdCBzaG91bGQgZ292ZXJuIHRoaXMgc3BlYydzIHVzYWdlIGFuZA0K
dGhpcyBub3RlIHNob3VsZCBiZSByZW1vdmVkLiAgQSBub3RlIHRvIHRoZSBSRkMgRWRpdG9yIHRv
IHVwZGF0ZSB0aGlzIGRvY3VtZW50DQppZiB0aGUgbm9tZW5jbGF0dXJlIGNoYW5nZXMgaW4gdGhl
IG5vcm1hdGl2ZSByZWZlcmVuY2Ugc2hvdWxkIGRvIHRoaXM7DQppZiBub3QsIHRoZW4gSSBiZWxp
ZXZlDQp0aGF0IHRoZSBJRVNHIGNhbiBwZXJtaXQgYSBjaGFuZ2UgYnkgbGF0ZXIgYWRkaW5nIGEg
bmV3IFJGQyBFZGl0b3INCm5vdGUgd2hpbGUgaXQgaXMNCmluIHF1ZXVlLg0KDQpNaW5vciBJc3N1
ZXM6DQoNClRoZSBkb2N1bWVudCBzYXlzOg0KDQogICBUaGUgYWJpbGl0eSB0byBlbmNvZGUgY2hh
cmFjdGVycyB3aXRoIHRoZSBFbWJlZGRlZFVuaWNvZGVDaGFyDQogICBlbmNvZGluZ3Mgc2hvdWxk
IGJlIHZpZXdlZCBhcyBhIHRyYW5zaXRpb25hbCBtZWNoYW5pc20uICBJdCBpcyBob3BlZA0KICAg
dGhhdCBhcyBzeXN0ZW1zIGxhY2tpbmcgc3VwcG9ydCBmb3IgVVRGOFNNVFAgYmVjb21lIGxlc3Mg
Y29tbW9uIG92ZXINCiAgIHRpbWUsIHRoZXNlIGVuY29kaW5ncyBjYW4gZXZlbnR1YWxseSBiZSBw
aGFzZWQgb3V0Lg0KDQpUcmFuc2l0aW9uYWwgbWVjaGFuaXNtcyBnZW5lcmFsbHkgbGl2ZSBhIGxv
bmcsIGxvbmcgdGltZSwgYW5kIHRoaXMgb25lIHNlZW1zDQpsaWtlbHkgdG8gbWUgdG8gbGl2ZSBh
dCBsZWFzdCB0byB0aGUgZW5kIG9mIG15IGNhcmVlci4gIEkgd291bGQNCnBlcnNvbmFsbHkgc3Vn
Z2VzdA0Kc3RyaWtpbmcgdGhpcyB0ZXh0LCBidXQgaXQgZG9lcyBubyBoYXJtIGlmIGxlZnQgaW4u
DQoNCk5pdHM6DQpDaHJpcyBOZXdtYW4ncyBhZGRyZXNzIGluIHRoZSBkcmFmdCBhcHBlYXJzIHRv
IGJlIG9sZC4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQphcHBzLWRpc2N1c3MgbWFpbGluZyBsaXN0DQphcHBzLWRpc2N1c3NAaWV0Zi5vcmcNCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXBwcy1kaXNjdXNz


From Shawn.Steele@microsoft.com  Thu Dec 16 12:47:57 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 47DB73A69C9 for <ima@core3.amsl.com>; Thu, 16 Dec 2010 12:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.427
X-Spam-Level: 
X-Spam-Status: No, score=-10.427 tagged_above=-999 required=5 tests=[AWL=0.172, 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 fcfFhScBhc1r for <ima@core3.amsl.com>; Thu, 16 Dec 2010 12:47:56 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 9A19E3A696C for <ima@ietf.org>; Thu, 16 Dec 2010 12:47:56 -0800 (PST)
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; Thu, 16 Dec 2010 12:49:41 -0800
Received: from TK5EX14MBXC133.redmond.corp.microsoft.com ([169.254.2.87]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Thu, 16 Dec 2010 12:49:41 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.txt
Thread-Index: AcudYpT+IYIuAD13QJKoyvjBmLQzXg==
Date: Thu, 16 Dec 2010 20:49:41 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A10CABF53@TK5EX14MBXC133.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [EAI] [apps-discuss] draft-ietf-eai-rfc5337bis-dsn-01.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: Thu, 16 Dec 2010 20:47:57 -0000

>>   The ability to encode characters with the EmbeddedUnicodeChar
>>   encodings should be viewed as a transitional mechanism.  It is hoped
>>   that as systems lacking support for UTF8SMTP become less common over
>>   time, these encodings can eventually be phased out.

> Transitional mechanisms generally live a long, long time, and this one se=
ems
> likely to me to live at least to the end of my career.

I agree that it could take a long time, however this note seems to me to in=
dicate best practice would be to not use this if not necessary, so I'd leav=
e it in to encourage good behavior moving forward.

-Shawn


From klensin@jck.com  Tue Dec 21 19:57:55 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 2F7713A6958 for <ima@core3.amsl.com>; Tue, 21 Dec 2010 19:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080,  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 aaoo0JxMT4kS for <ima@core3.amsl.com>; Tue, 21 Dec 2010 19:57:54 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id A034F3A692B for <ima@ietf.org>; Tue, 21 Dec 2010 19:57:53 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PVFri-000AF0-5F for ima@ietf.org; Tue, 21 Dec 2010 22:59:50 -0500
Date: Tue, 21 Dec 2010 22:59:49 -0500
From: John C Klensin <klensin@jck.com>
To: IETF EAI WG <ima@ietf.org>
Message-ID: <63BC2DE946B49E7DC3B38AFC@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] Co-chair's comments on state of the documents and the WG
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: Wed, 22 Dec 2010 03:57:55 -0000

(writing as co-chair)

Hi.

Folks, I've been watching progress in this WG between some
weeks before the Beijing IETF and the present.  I think we are
in serious trouble and want to share that opinion with the WG
participants.  

For a WG to function and make a serious claim to represent IETF
technical consensus, there has to be significant participation,
review of documents, etc.  And that has to come from more than
the group of people writing documents.  In practice, we
sometimes relax that requirement a bit.  In particular, there
have been WGs that have been considered successful even though
there have really been only about a half-dozen really active
participants.  But that is just not sensible when the WG is
working on protocols that pose very significant risks to the
installed base if we overlook important cases.  As we have
noticed when we have sorted out the various implications of
extensions on legacy email implementations the EAI effort poses
just exactly that risk.  The extensive syntax discussion in
Beijing is an important example of how careful we need to be
about our decisions.

Our situation is made somewhat more difficult by the
observation that only a relatively small fraction of the
participants in the WG have significant personal experience
with large-scale Internet mail operations or a deep familiarity
with the existing Internet mail protocols.  As we have seen
with the reviews Alexey requested from the Apps Area review
team, when such reviews from the IETF's email expert community
come at all, they tend to come from outside the WG and tend to
find things that the WG did not.  That is disquieting to say
the least.

I note that we got a fairly large number of promises in both
Beijing and Maastricht to carefully review and comment on
documents.  Outside the author group and a few others, either
people did not do those reviews or they lack the skill or
background to find things that have been discovered by Alexey,
myself, or others outside the normal group of WG participants.

Clearly, there is a large community, especially among users of
east Asian languages, who very much want internationalized
email addresses and headers.  There are other communities with
similar needs but the they are not well-represented in the WG
(or have been strangely silent) so, if they have requirements
that are different from those we have seen already, we are at
risk of missing them or getting things wrong.  If the IETF
cannot or will not produce usable specifications, there is
reason to believe that communities will go off in their own
directions, resulting in huge interoperability problem in the
future.

One way of looking at the WG's problem is that there is a
community of people who are deeply interested in email
internationalization but who lack either extensive email
experience or significant experience in writing clear and
precise IETF specifications (whether the problem is with
technical English, ABNF, or the way the existing email specs
are written).  There is also a community who are expert in
Internet email and the writing of the relevant types of
specifications, but few of them have been actively involved in
i18n work and fewer still have time and "day job" support to
devote to this work.  The two communities are largely disjoint,
but both are needed to complete the EAI work with great
confidence about the results being correct and free of
dangerous side-effects.

In discussions with Alexey, it has become clear that we have
hard practical deadlines associated with the end of his term as
AD.  The core documents have to be in his hands and out for
IETF Last Call within the next several weeks or it seems
unlikely that the WG will be able finish its work... ever.

Having read the reviews from the last two weeks or so, I think
it ought to be possible to proceed as follows _if_ WG
participants are really interested enough in finishing this
work to put effort into it:

(1) We get some reviewers from inside the WG but outside the
author group to go through the comments and verify that they
have been properly disposed of, e.g., that appropriate changes
have been made to the documents or we have explained why not to
the satisfaction of the reviewers and/or significant consensus
of WG participants.

(2) We get ths three base documents into Alexey's hands with a
request for IETF Last Call really soon -- certainly before
January 15 and ideally early next week.  That means the
checking described in (1) needs to occur nearly immediately.
Bluntly, silence from those of you have have been silent since
July will have to be taken as indifference on your part to
whether the documents are completed and the WG continues.

(3) We get some serious suggestions from the WG on how we are
going to move forward with the two additional groups of
documents -- (i) POP/ IMAP/ common downgrading protocol
specifications and (ii) all of the "advice" stuff.  If we can
find adequate review for the protocol specs, we can presumably
proceed with them on the same basis that we are using to handle
the base documents.  I am, however, concerned that we may not
be able to find that quality of review unless more people
within the WG start doing serious work.  For the "advice"
documents, unless we can get a lot of review and input from
people who are much more experienced with Internet email than
the WG average --people who could write similar documents for
non-EAI email and have it be credible-- I suggest that we just
drop the documents from the WG agenda and handle them as
individual submissions.  I want to stress that I'm not assuming
there is anything wrong with the drafts -- the issue is only
about getting adequate review to convince ourselves and the
IETF community that those documents really do represent
community consensus.  Put differently, the problem is not
getting the I-Ds written; it is having them reflect sufficient
experience (not just opinions) to be accepted within the
broader Internet email environment.  Doing so requires noting
that the Internet email environment has survived well for
nearly 30 years without such documents.

If people disagree with this rather bleak analysis -- and I
hope they do -- suggesting areas where I am wrong would be a
useful first step in convincing us that the WG really does have
the energy to finish all of the work listed in the charter
(including the optional tasks).

   best regards and best wishes for anything you may be
   celebrating at this time of year,
    john


From duerst@it.aoyama.ac.jp  Wed Dec 22 00:17:21 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 71AE33A69AF for <ima@core3.amsl.com>; Wed, 22 Dec 2010 00:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.216
X-Spam-Level: 
X-Spam-Status: No, score=-100.216 tagged_above=-999 required=5 tests=[AWL=-1.026, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_42=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 4VC48jcwSA6B for <ima@core3.amsl.com>; Wed, 22 Dec 2010 00:17:19 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id 841463A6AD9 for <ima@ietf.org>; Wed, 22 Dec 2010 00:17:18 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oBM8J8R5014478 for <ima@ietf.org>; Wed, 22 Dec 2010 17:19:09 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 6235_3765_25f88bf4_0da4_11e0_b696_001d096c5782; Wed, 22 Dec 2010 17:19:08 +0900
Received: from [IPv6:::1] ([133.2.210.1]:37268) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14A7C33> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 22 Dec 2010 17:19:09 +0900
Message-ID: <4D11B475.5080100@it.aoyama.ac.jp>
Date: Wed, 22 Dec 2010 17:19:01 +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: <63BC2DE946B49E7DC3B38AFC@PST.JCK.COM>
In-Reply-To: <63BC2DE946B49E7DC3B38AFC@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF EAI WG <ima@ietf.org>
Subject: Re: [EAI] Co-chair's comments on state of the documents and the WG
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: Wed, 22 Dec 2010 08:17:21 -0000

Hello John,

I want to make sure that at least somebody replies to your mail.

I don't think at all that I'm qualifying with respect to email 
infrastructure implementation and operation experience; I'm just mostly 
an email user. I can help with internationalization issues, but my 
understanding is that that's not necessarily what's most needed now. I 
may be able to go through some comments and check whether they have been 
applied consistently (essentially a shepherd role?). Getting pointers to 
drafts and mails with comments would help.


On a meta-level, I'm a bit surprised by your comment that we have to 
finish within Alex'es term. I understand that it would be much more 
efficient if Alex could handle our drafts rather than a new AD, and I 
understand that each AD has their preferences for what work they want to 
have happening, and that on occasion very inactive WGs have been shut 
down, but what you wrote below almost sounded like the new AD would just 
shut the WG down without asking anybody, so I hope I'm misunderstanding.

Also, while I think that all your observations were to the point, I 
think a shorter mail, with a subject more like "Wanted: Reviewers for 
XYZ" would have a bigger chance to be read by the relevant people. Also, 
maybe you remember (if only faintly) some of the hands that went up in 
Maastricht or in Beijing, and might be able to contact them directly. On 
average, that gives a better result than anonymous appeals.

Regards,   Martin.


On 2010/12/22 12:59, John C Klensin wrote:
> (writing as co-chair)
>
> Hi.
>
> Folks, I've been watching progress in this WG between some
> weeks before the Beijing IETF and the present.  I think we are
> in serious trouble and want to share that opinion with the WG
> participants.
>
> For a WG to function and make a serious claim to represent IETF
> technical consensus, there has to be significant participation,
> review of documents, etc.  And that has to come from more than
> the group of people writing documents.  In practice, we
> sometimes relax that requirement a bit.  In particular, there
> have been WGs that have been considered successful even though
> there have really been only about a half-dozen really active
> participants.  But that is just not sensible when the WG is
> working on protocols that pose very significant risks to the
> installed base if we overlook important cases.  As we have
> noticed when we have sorted out the various implications of
> extensions on legacy email implementations the EAI effort poses
> just exactly that risk.  The extensive syntax discussion in
> Beijing is an important example of how careful we need to be
> about our decisions.
>
> Our situation is made somewhat more difficult by the
> observation that only a relatively small fraction of the
> participants in the WG have significant personal experience
> with large-scale Internet mail operations or a deep familiarity
> with the existing Internet mail protocols.  As we have seen
> with the reviews Alexey requested from the Apps Area review
> team, when such reviews from the IETF's email expert community
> come at all, they tend to come from outside the WG and tend to
> find things that the WG did not.  That is disquieting to say
> the least.
>
> I note that we got a fairly large number of promises in both
> Beijing and Maastricht to carefully review and comment on
> documents.  Outside the author group and a few others, either
> people did not do those reviews or they lack the skill or
> background to find things that have been discovered by Alexey,
> myself, or others outside the normal group of WG participants.
>
> Clearly, there is a large community, especially among users of
> east Asian languages, who very much want internationalized
> email addresses and headers.  There are other communities with
> similar needs but the they are not well-represented in the WG
> (or have been strangely silent) so, if they have requirements
> that are different from those we have seen already, we are at
> risk of missing them or getting things wrong.  If the IETF
> cannot or will not produce usable specifications, there is
> reason to believe that communities will go off in their own
> directions, resulting in huge interoperability problem in the
> future.
>
> One way of looking at the WG's problem is that there is a
> community of people who are deeply interested in email
> internationalization but who lack either extensive email
> experience or significant experience in writing clear and
> precise IETF specifications (whether the problem is with
> technical English, ABNF, or the way the existing email specs
> are written).  There is also a community who are expert in
> Internet email and the writing of the relevant types of
> specifications, but few of them have been actively involved in
> i18n work and fewer still have time and "day job" support to
> devote to this work.  The two communities are largely disjoint,
> but both are needed to complete the EAI work with great
> confidence about the results being correct and free of
> dangerous side-effects.
>
> In discussions with Alexey, it has become clear that we have
> hard practical deadlines associated with the end of his term as
> AD.  The core documents have to be in his hands and out for
> IETF Last Call within the next several weeks or it seems
> unlikely that the WG will be able finish its work... ever.
>
> Having read the reviews from the last two weeks or so, I think
> it ought to be possible to proceed as follows _if_ WG
> participants are really interested enough in finishing this
> work to put effort into it:
>
> (1) We get some reviewers from inside the WG but outside the
> author group to go through the comments and verify that they
> have been properly disposed of, e.g., that appropriate changes
> have been made to the documents or we have explained why not to
> the satisfaction of the reviewers and/or significant consensus
> of WG participants.
>
> (2) We get ths three base documents into Alexey's hands with a
> request for IETF Last Call really soon -- certainly before
> January 15 and ideally early next week.  That means the
> checking described in (1) needs to occur nearly immediately.
> Bluntly, silence from those of you have have been silent since
> July will have to be taken as indifference on your part to
> whether the documents are completed and the WG continues.
>
> (3) We get some serious suggestions from the WG on how we are
> going to move forward with the two additional groups of
> documents -- (i) POP/ IMAP/ common downgrading protocol
> specifications and (ii) all of the "advice" stuff.  If we can
> find adequate review for the protocol specs, we can presumably
> proceed with them on the same basis that we are using to handle
> the base documents.  I am, however, concerned that we may not
> be able to find that quality of review unless more people
> within the WG start doing serious work.  For the "advice"
> documents, unless we can get a lot of review and input from
> people who are much more experienced with Internet email than
> the WG average --people who could write similar documents for
> non-EAI email and have it be credible-- I suggest that we just
> drop the documents from the WG agenda and handle them as
> individual submissions.  I want to stress that I'm not assuming
> there is anything wrong with the drafts -- the issue is only
> about getting adequate review to convince ourselves and the
> IETF community that those documents really do represent
> community consensus.  Put differently, the problem is not
> getting the I-Ds written; it is having them reflect sufficient
> experience (not just opinions) to be accepted within the
> broader Internet email environment.  Doing so requires noting
> that the Internet email environment has survived well for
> nearly 30 years without such documents.
>
> If people disagree with this rather bleak analysis -- and I
> hope they do -- suggesting areas where I am wrong would be a
> useful first step in convincing us that the WG really does have
> the energy to finish all of the work listed in the charter
> (including the optional tasks).
>
>     best regards and best wishes for anything you may be
>     celebrating at this time of year,
>      john
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>
>

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

From dhc@dcrocker.net  Wed Dec 22 10:03:04 2010
Return-Path: <dhc@dcrocker.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 448D73A6925; Wed, 22 Dec 2010 10:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3n2X7E2rjUvK; Wed, 22 Dec 2010 10:03:00 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 279EC3A6909; Wed, 22 Dec 2010 10:03:00 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBMI4mYh013364 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2010 10:04:53 -0800
Message-ID: <4D123DC0.2050501@dcrocker.net>
Date: Wed, 22 Dec 2010 10:04:48 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Apps Discuss <apps-discuss@ietf.org>, ima@ietf.org, draft-ietf-eai-rfc5336bis@tools.ietf.org, SM <sm+ietf@elandsys.com>, Alexey.Melnikov@isode.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Dec 2010 10:04:55 -0800 (PST)
Subject: [EAI] (private) draft review of: draft-ietf-eai-rfc5336bis-07.txt (v3)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 22 Dec 2010 18:03:04 -0000

IETF Applications Review


I have been selected as an Applications Area Review Team reviewer for this
draft.

For background on apps-review, please see:
<http://www.apps.ietf.org/content/applications-area-review-team>

Please resolve these comments along with any other Last Call comments you
may receive. Please wait for direction from your document shepherd or AD
before posting a new version of the draft.



Document: draft-ietf-eai-rfc5336bis-07.txt
Reviewer: Dave Crocker, Brandenburg InternetWorking
Review Date: 2010-12-22


BACKGROUND:

      The document is a specification for an email transport-time option that is 
described in its Abstract as declaring support for "internationalized email 
addresses or header information" and in the Introduction as being "to support an 
internationalized email address".  The extension specifies changes both in the 
transfer protocol and in the message being transferred, including its Body. 
Legacy Internet Mail only supports classic "network ASCII" for data 
representation and for data transfer encoding.

      The charter for the current work cites previous work that was issued as 
Experimental, and summarizes it as having been "... based on the use of an
SMTP extension to enable the use of UTF-8 in envelope address
local-parts, optionally in address domain-parts, and in mail
headers."  This text appears also to serve as the statement of scope for the 
current working group.

      With respect to the mail header, the scope is specified as covering 
<address> and <encoded-word> constructs.  An <encoded-word> is a means of 
mapping Unicode strings onto classic, network ASCII, although the working group 
focus was on binary, UTF-8 support.


RECOMMENDATIONS:

This work represents an extremely important enhancement to Internet mail. It has 
been clear for twenty years that Internet applications need to be able to 
present data in a form that is natural to the user.

The current work benefits from providing a Framework document and from 
distinguishing changes to the email header from changes to the SMTP protocol.

    0.  The documents do raise distinctions between ASCII and Unicode, versus 
between ASCII and UTF-8. However they do not apply them rigorously in the 
documents.  I suggest that the term "internationalization" be used only during 
introductory discussion and never as part of normative text.  ASCII vs. Unicode 
is a distinction between the underlying range of data being represented.  ASCII 
vs. UTF-8 is a distinction between encoding environments. Text should explicitly 
indicate whether it means data representation versus data encoding and it should 
use Unicode for the former and UTF-8 for the latter.

    1.  The Framework document is normative and needs to be completed along with 
the other two specifications, since they quite reasonably state a normative 
dependence on the Framework document.

    2.  The SMTP extension draft needs to focus on SMTP and the direct support 
of UTF-8 in the message header.  It needs to move all discussion and 
specification of Unicode support in the Header to the Header draft.

    3.  There probably needs to be definition of MIME message/uni-rfc822, 
specifying Unicode support within a message contained in MIME.  I'm less clear 
whether there needs to be a MIME Content-Transfer-Encoding form specific to UTF-8.

    4.  The SMTP extension needs to have the client use an explicit signal when 
it is sending a message encoded in UTF-8. This is easiest as a parameter to the 
MAIL command.  The current specification creates a more complex and almost 
heuristic model for distinguishing ASCII from UTF-8 use.

    5.  The SMTP extension needs to remove all restrictions it imposes on MIME 
content-type.  A major reason that MIME was successful was that it was 
transparent to the transfer infrastructure.  The current SMTP extension 
specification changes this model, which actually increases the barrier to 
adoption of Unicode in email.  It needs to be easy for two MUAs that support 
Unicode in the email header to exchange mail even when the infrastructure does 
not support UTF-8.



SUMMARY COMMENTS:

The document conforms to the conventions for defining SMTP options.

There are a number of significant issues with the specification. These are 
covered in detail, below, and are summarized here:

      *  Framework -- The Framework document[1] is (correctly) referenced as 
required reading.  It supplies essential terminology and architecture for this 
specification.  In fact it is a specification, complete with formally normative 
vocabulary.  This means that it must be a normative reference by rfc5336bis.  It 
therefore also means that the Framework document needs to be completed before 
the current specification can be standardized.

      *  Scope -- the specification appears to go significantly beyond the scope 
of the working group's charter, including revisions to basic SMTP that have no 
obvious requirement for support of Unicode during transport. In fact, at least 
one change is likely to /restrict/ system-wide adoption, rather than encourage 
it!  In particular, the specification restricts the conditions under which some 
MIME content is allowed to be sent. (See next bullet.)

      *  Infrastructure Requirement -- Unless this option is in force, carrying 
internationalized email in a MIME part is prohibited.  This is out of scope for 
the working group and it is a counter-productive rule.  Imagine if the same type 
of rule had been specified when MIME was created, saying that MIME could only be 
sent when an "attachments-supported" option were in force. This would have 
prevented the early adoption of MIME use by individual MUAs until the entire 
infrastructure supported MIME.   (As an example of the very high barrier this 
raises, note the difference in real-world support and use of MDN versus DSN.) 
While it is reasonable for the working group to define a new MIME content-type 
that modifies message/rfc822 to support internationalized addresses, it is not 
appropriate for the working group to modify the SMTP transfer model to constrain 
what types of message content can be sent.

      *  Beyond <encoded-word> -- The work, here, appears to have two goals. One 
is to add support for Unicode in a <local-part>; that is, support for 
internationalized addresses.  However note that <encoded-word> and <A-label> 
already accomplish this in a way that is transparent to the existing email 
infrastructure; only the end-systems need to understand it.  The second goal is 
to support Unicode in the more "native" form of UTF-8. (The quotation marks are 
because UTF-8 is not native Unicode, either; it is a highly encoded form of 
Unicode...)  This creates some confusion in the specification.  Given that the 
option for SMTP is "UTF8SMTPbis", then the binary encoding goal seems to 
dominate the work. This is a certainly a reasonable goal, but it will help the 
clarity of the specification to make these two different goals more clear within 
the document and to apply them more carefully.

      *  Terminology confusion -- The Framework document carefully distinguishes 
between "ASCII addresses and non-ASCII addresses.  It equates 
"internationalized" first with "non-ASCII", but then with "UTF8SMTPbis". A core 
problem is that ASCII is part of the actual internationalized set of Unicode 
characters. So, to say that "international" characters are non-ASCII is exclude 
part of Unicode from the term "international".  In addition, equating the term 
"internationalization" with UTF-8 encourages confusion between underlying or 
"native" data -- that is, Unicode -- with the way it is represented over the 
wire.  UTF-8 is merely one means of over-the-wire representation.  So, for 
example, <A-label> and <encoded-word> are two other means of encoding.  It's 
clear that this core distinction really is understood by the authors of this and 
the Framework documents.  However the vocabulary choices and their usage create 
a problem in the details of the specification.  "Internationalization" should 
mean Unicode, not a particular binary representation of it within 8-bit chunks. 
  The problem, here, is in using the term "internationalization" to refer to a 
subset of Unicode, that is, the subset that is not ASCII.  I strongly suggest 
saying "Unicode" when intending to refer to the richer set of characters that 
are the goal of this work, and "UTF-8" when referring to the particular binary 
encoding of Unicode that is the focus of the SMTP extension work.

      *  Non-UTF-8 Unicode support -- Can a message support Unicode without 
UTF-8?  The existence of <encoded-word> and <A-label> constructs makes clear 
that the answer is yes.  Hence, it should be possible to support Unicode 
messages, without this SMTP extension.  Perhaps this is out of scope for this 
SMTP extension and perhaps it is handled by the Email Header draft, but I think 
it worth having this document cite this alternative mode, if only to a) make 
clear that the alternative exists, and b) make more clear what the specific and 
strong benefit of this extension is.

      *  Partial enforcement --  Since ASCII is a subset of Unicode, having this 
extension be in force means that /everything/ is Unicode AND, apparently, is 
encoded in UTF-8.  If the environment created by this extension supports UTF-8, 
then it supports UTF-8, meaning both ASCII and non-ASCII.  Defining rules that 
depend on having this extension be in force but then still distinguish between 
ASCII and non-ASCII does not seem to make sense.

      *  Complexity and Heuristics -- In a number of places, the specification 
defines highly contingent action, where one side can use UTF-8 only if the other 
side has done so. This makes the enhancement much more complicated than 
necessary or appropriate. The enhancement needs to work with an all-or-nothing 
model in which UTF-8 is in force or it is not.  And, yes, this appears to be a 
major change in the model of this specification.  My understanding is that these 
issues were discussed in the working group, but I do not understand why  and 
nearly-heuristic approach was preferred.  Instead I recommend the client to 
signal explicitly when UTF8-encoded addresses are present, such as a 
<Mail-parameters> option (<esmtp-param>) to the MAIL command.

      *  5321 vs. 5322 -- The specification seems to confuse -- or at least to 
mix -- some rules from RFC 5321 versus some from RFC 5322.  <mailbox> is the 
major example.

      *  Since an RFC 5322 message can and often does exist outside of the SMTP 
environment, any changes to the RFC 5322 specification should be in a document 
that is separate from this extension specification.  This specification can then 
cite it.  I suggest moving all RFC 5322 changes to the Header document[2]  and 
merely citing it here.

      *  UTF8SMTPbis -- The draft uses the string "UTF8SMTPbis" when referencing 
the SMTP option.  The Framework document explains the choice, but IANA 
Considerations in this document needs to provide explicit handling instructions 
for it, since this is certain NOT to be the actual string that is used.

      *  Redundant Specification - in a number of places, normative language 
from other specifications is repeated.  This invites divergent specification and 
is generally out of scope for the current work. To the extent that the current 
specification needs to refer to normative parts of other specifications, it 
should do only that:  cite it; do not repeat it.  For example to highlight an 
important normative item from another specification, the current specification 
might describe the "topic" the external language covers, without saying what it 
says.  In other cases, the key point is that the current specification is not 
changing requirements from another specification; that is what should be said, 
rather than repeating what that requirement is. In general, these references to 
external, normative behaviors should be reviewed for relevance to the current 
work.  How is internationalized addresses relevant to the normative detail?

      *  Rule Meta-Naming -- The 'u' preface for revised rules is a reasonable 
idea, but appears to be problematic.  These rules replace existing rules in 
other specifications. There needs to be an explicit and decision about the 
handling of this, and it needs to be applied consistently, either directly 
replacing the rules or else re-naming them consistently, in a fashion that can 
be parsed (similar to the naming template that was done with RFC5322 obs-* 
rules.)  If an initial string is to be used, I suggest UTF-8-* rather than u*, 
in order to make it possible to parse this meta-label more reliably.





DETAILED COMMENTS:

{ I have included text from the draft that provides context, but have skipped 
sequences of text from the draft that do not. }


> 1.  Introduction
>
> The Simple Mail Transfer Protocol [RFC5321] provides a negotiation mechanism
> about service extension with which clients can discover

      with which ->  by which { or } through which

{ Either of these would be my stylistic preference. }


> server capabilities and make decisions for further processing.  This
> document use this mechanism to support an internationalized email

      use -> uses


> address.  An extended overview of the extension model for

{ The option enables use of UTF-8 in the email header, beyond just addresses,
therefore: }

      to support...address
      ->
      to support internationalized email addresses and internationalized
characters for the email header.


> internationalized addresses and headers appears in [RFC4952bis],

      headers -> the email header


> referred to as "the framework document" or just as "framework" elsewhere in
> this specification.  This document specifies an SMTP extension to permit
> internationalized email addresses in envelopes,

      envelopes -> the SMTP envelope

{ 1.  Although 'envelope' is almost certainly unambiguous, its use over the
years has been confusing, so it is worth being particularly clear in a
specification.

   2.  The use of plurals in a specification can be confusing.  I suggest using
the singular form wherever it can work, so that remaining use of plurals becomes
more precise. Also note the particular confusion with the word "headers" in 
email.  Since a single email has only a single header, the use of plural means 
each header from a set of messages... }


> and UNICODE characters (encoded in UTF-8) [RFC3629] in headers.

      headers -> the header


> 1.1.  Role of This Specification
>
> The framework document specifies the requirements for, and describes
> components of, full internationalization of the electronic mail.  A thorough
> understanding of the information in that document and in the base Internet
> email specifications [RFC5321] [RFC5322] is necessary to understand and
> implement this specification.

{ This means that the Framework document is normative; it needs to be cited as 
such.  Since understanding it is a pre-condition of reading the specification, 
it also requires that the Framework document be completed before this document. }


> This document specifies an element of the email internationalization work,
> specifically the definition of an SMTP extension for internationalized email
> address transport delivery.

{ Since it also declares support for internationalization in the message header,
it covers more than delivery.  In effect, it is a transport-time flag for
declaring internationalization of the entire email "environment".  I'm not quite
sure what exact language change to suggest, however.

I also note that it does more than declare support for internationalized 
addresses:  It declares support for encoding them into UTF-8. This is a 
significant, additional requirement and should be stated explicitly. }


> 1.2.  Terminology
...
> This specification defines only those Augmented BNF (ABNF) [RFC5234] syntax
> rules that are different from those of the base email specifications and,
> where the earlier rules are upgraded or extended, gives them new names.
> When the new rule is a small modification to

{ The wording in the first part of this paragraph seems awkward.  I think the
following is clearer: }

      This specification uses Augmented BNF (ABNF) rules [RFC5234], with some
modifications.  The modified rules are defined here and the rest are simply 
imported from [RFC5234].  New names are used, for rules that are upgraded
or enhanced.  When the ...


> the older one, it is typically given a name starting with "u".  Rules

{ The use of "typically" makes the description of this convention problematic. 
It needs to be always true or else not mentioned.  Or perhaps alternative 
phrasing:  }

      When a new...with "u".
      ->
      When a new rule has a name starting with "u", it is a small modification to
an older rule.

{ This asserts what is true and ignores what is not true, such as rules that 
qualify for the "u" but did not get it...

However I now believe that it is important to have a consistent meta-rule for 
naming the revised rules and that it be applied consistently to all rules that 
qualify for it.  Further, the naming convention should be easily parseable, and 
therefore more like what is used in RFC5322, to cover "obsolete" rules.  I 
suggest that new rules, here, be named UTF-8-*.  To repeat:  I believe that 
/all/ rules that resolve to UTF-8 must be renamed, so that implementers know 
what they need to change. }


> that are undefined here may be found in the base email specifications

{ The specifications should be cited here, explicitly, even though they have 
been cited elsewhere.  It is important to leave no ambiguity for the reader. }

      here may be -> here can be

{"may" is a reserved word for normative specification. Normative meaning is not 
based on the use of capitalization. }


> 3.2.  The UTF8SMTPbis Extension

> An SMTP server that announces this extension MUST be prepared to
>    accept a UTF-8 string [RFC3629] in any position in which RFC 5321
>    specifies that a mailbox can appear.  That string MUST be parsed only
>    as specified in [RFC5321], i.e., by separating the mailbox into

{ The 'i.e.' clause is an example of repeating normative text from another 
specification.

The current document is not empowered to give directives about basic SMTP 
parsing, nor is there any internationalization requirement that it do so.  At 
most, it should say that the changes specified in this document do not change 
any other aspect of SMTP processing. }


>         Once isolated by this parsing process, the local part MUST be
>    treated as opaque unless the SMTP server is the final delivery Mail
>    Transfer Agent (MTA).

{ The statement about handling of <local-part> is redundant with the base RFC 
5321 specification.  The statement, here, should be that the handling of 
<local-part> is unchanged from the base specification.  Again, it should not 
repeat the normative language, unless it is changing it.  If it is changing it, 
the change needs to be essential for support of internationalized addresses. }


>                        Any domain names that are to be
>    compared to local strings SHOULD be checked for validity and then
>    MUST be compared as specified in section 3 of [RFC5891].

{ Dictating use of RFC5891 is within scope.  Dictating validation seems not to 
be.  So...}

    -> Any domain name that is to be compared to a local string MUST use Section 
3 of [RFC5891] as the basis for comparison.


> An SMTP client that receives the UTF8SMTPbis extension keyword in response
> to the EHLO command MAY transmit mailbox names within SMTP commands as
> internationalized strings in UTF-8 form.  It MAY send a UTF-8 header
> [RFC5335bis] (which may also include mailbox names in UTF-8).  It MAY
> transmit the domain parts of mailbox names within SMTP commands or the
> message header as A-labels or U-labels

{ I believe that the use of "MAY" is not correct. This would mean that the 
receiver needs a means of distinguishing whether the data are UTF-8 or not. This 
would border on requiring support of a heuristic, but it certainly adds a 
significant processing overhead and additional software complexity.

The only alternative is to specify use of a MAIL command <Mail-parameters> 
option that declares that the message supports internationalized addresses. 
Given the approach in this specification, I believe the intent is also to have 
it mean that UTF-8 encoding is supported.

The core issue here is specifying an option which declares a message to have an 
EAI context for all of the message.  So the processing context is fully 
EAI/UTF-8 or it is legacy net-ASCII.  This is considerably simpler to specify 
and to process, than would be requiring parsing the incoming string and looking 
for non-ASCII UTF-8.

Hence: }

      An SMTP client...U-labels
      ->
      An SMTP client that receives the UTF8SMTPbis extension keyword, in response to
the EHLO command, will transmit <local-part> within SMTP commands as
internationalized strings in UTF-8 form.  It will send the email header in UTF-8
[RFC5335bis] (which can also include <mailbox> names in UTF-8.)  It also will
transmit the domain parts of mailbox names within SMTP commands or the message
header as A-labels or U-labels

{ Note - the term "mailbox names" is not defined here or in RFC 5321.  In RFC 
5321 it appears to be used to mean local-part; however becasue its precise 
meaning is unclear, I strongly urge NOT using it here at all. Instead I suggest 
using whatever ABNF rulename is appropriate.  This guarantees clarity.

   Note:  I changed 'may' to 'can'. Also, when an ABNF rule is being cited within
prose text, such as for <mailbox>, it should be distinguished so that the reader
knows it is a formal term.  I have used <> to bracket the term mailbox. }


> All labels in domain parts of mailbox names which are IDN
>    forms of A-labels or U-labels MUST be valid.

{ This is strange.  Either it is repeating a normative requirement from SMTP or 
it is expanding SMTP to require special validation for IDN forms of domain names 
that is not present for ASCII forms.  Neither interpretation seems like the 
right thing to be doing here. Such a modification to SMTP seems out of scope.

Also, the term <mailbox> has different semantic definitions in RFC 5321 and RFC 
5322.  A strict reading of the differences could be a problem.  A loose reading 
would note that both definitions reduce to include <local-part> and <domain> 
components that are common to both specifications.  I encourage you to review 
this issue carefully and put a note at the beginning of the document stating 
explicitly how you have chosen to handle it.

My best recommendation is that this document should only refer to RFC 5321 ABNF 
and that it should move /all/ RFC 5322 modifications or enhancements to the EAI 
Header document (draft-ietf-eai-rfc5335bis). }


>                    When a Mail User
>    Agent(MUA) submits a message to a Message Submission Server
>    ("MSA")[RFC4409], it is the responsibility of the MSA to ensure that
>    all domain labels are valid.

{ Given that this specification creates broad systemic effects and given that it 
needs to refer to components other than an SMTP client or server, it should cite 
RFC 5598, to give the reader an integrated view of the email service. I'll note 
that citing 5598 has become common for email specifications; so this is not a 
controversial suggestion. }


>The presence of the UTF8SMTPbis
>    extension does not change the requirement of RFC 5321 that servers
>    relaying mail MUST NOT attempt to parse, evaluate, or transform the
>    local part in any way.

{ This sentence replicates normative language from a different specification. 
This is a very bad thing to do, in case the original specification changes its 
language.  I suggest: }

      The presence of...in any way
      ->
      The presence of the UTF8SMTPbis extension does not change RFC 5321 server
relaying behaviors.

{ this retains some text as a flag to the reader, but does not provide the
specific semantics, which might change in the original specification. }


> If the UTF8SMTPbis SMTP extension is not offered by the server, the SMTP
> client MUST NOT transmit an internationalized address and MUST NOT transmit

{ This appears to prohibit the sending of internationalized addresses that are 
encoded in ASCII, rather than in UTF-8.  The purpose of ASCII encoding is to 
eliminate the need for infrastructure support for Unicode characters.  However 
the language here appears to be imposing the barrier of infrastructure support. 
  If the concern is sending UTF-8, then that's the language that needs to be 
used.  Messages with ASCII-encoding of internationalized addresses need to be 
permitted to be sent, without first requiring infrastructure support. }


> a mail message containing internationalized mail headers as described in
> [RFC5335bis] at any level within its MIME structure [RFC2045] and [RFC2047].

{ The prohibition of internationalized mail headers within a MIME structure -- 
"at any level within its MIME structure"  -- is out of scope for the working 
group and is a /major/ change to SMTP.  It is also a really terrible rule!  In 
terms of protocol modeling, it would have been like saying that no one could use 
MIME until the infrastructure supported it!

It is one thing to give the reader a reminder that UTF-8 is illegal in the email 
header of a message and quite another to attempt to prohibit it in attachments. 
  Attachments already carry all sorts of data.  UTF-8 is merely one more type. I 
believe that there currently no SMTP constraints on the carriage of MIME; I also 
believe it essential that there not be, since such constraints impede adoption. 
  (That is why MDN support is good and DNS support is poor.)

Also note that MIME objects exist outside of email transport and that directives 
about legal or illegal MIME ought to be separated from SMTP...

Also, perhaps mail with UTF-8 in the header needs a different
MIME type, such as text/UTF-8-message?... }


> 2.  It may either reject the message during the SMTP transaction or accept

      may -> MAY

{ However, I note that this concerns a SMTP client, not a server.

> 3.3.  Extended Mailbox Address Syntax
>
> RFC 5321, Section 4.1.2, defines the syntax of a mailbox entirely in terms
> of ASCII characters, using the production for a mailbox and those productions

      mailbox ->  <mailbox>


> on which it depends.
>
> The key changes made by this specification are, informally, to

{ I don't understand what it means to change RFC 5321 "informally".  I think it 
is intended to mean that the list is not guaranteed to be complete.  If so, I 
suggest wording such as: }

    -> The key changes made by this specification include:


> o  Change the definition of "Domain" to permit either the RFC 5321 definition
> above or a UTF-8 string representing a DNS label that is conformant with
> IDNA definitions [RFC5890].

{ "either"???  That sounds completely ambiguous.  }


> o  Change the definition of "Local-part" to permit either the definition
> above or a UTF-8 string.  That string MUST NOT contain any of the ASCII
> characters (either graphics or controls) that are not permitted in "atext";
> it is otherwise unrestricted.

{ same concern as above.  }


> According to the description above, the syntax of an internationalized email
> mailbox name (address) is defined in ABNF [RFC5234] as follows.
>
> uMailbox = uLocal-part "@" ( uDomain / address-literal ) ; Replace Mailbox
> in RFC 5321, Section 4.1.2

{  This implies that the option applies only to RFC5321 and not to RFC5322, but 
the later rules make clear that 5322 is also supposed to be covered.

To repeat:  I recommend that all RFC 5322 enhancements and ABNF should be moved 
to the EAI Header draft and that the SMTP extension should merely cite that draft.

Note that RFC5322 is for an object that can and does exist outside of SMTP. 
Enhancements to RFC5322 well might need to apply when there is no SMTP, or at 
least long after it is relevant.  }


> UTF-8-non-ASCII = UTF-8-2 / UTF-8-3 / UTF-8-4
>
> UTF-8-2 =  <See Section 4 of RFC 3629>
>
> UTF-8-3 =  <See Section 4 of RFC 3629>
>
> UTF-8-4 =  <See Section 4 of RFC 3629>

{ These rules are also defined in RFC5335 and draft-ietf-eai-rfc5335bis.  Citing 
RFC 3629 is therefore confusing, and possibly can create specification 
divergence. I suspect that RFC 3629 is not the correct reference, here, since it 
would imply that RFC5335bis' definitions should be ignored... If RFC 3629 /is/ 
the correct reference, then I cannot guess why and I cannot guess why it will 
not create problems with divergent specification. }


> The value of "uDomain" SHOULD be verified by IDNA definitions [RFC5890].  If

{  I do not understand what "SHOULD be verified by IDNA definitions" means.

If it means that the uDomain "SHOULDbe verified" then it is out of scope for 
this specification. There is no reason that SMTP rules concerning verification 
of Unicode-based domains needs to be different from ASCII-based domains.  In 
particular, verification of a Domain name is specified elsewhere.

If it means that the uDomain "should be IDNA complaint" then I do not understand 
having the exceptions that a "should" allows.  For this EAI work, I would think 
that when UTF8SMTPbis is in force, then IDNA compliance needs to be a MUST.  }


> that verification fails, the email address with that uDomain MUST NOT be
> regarded as a valid email address.

    MUST NOT be regarded as a valid
    ->
    MUST BE regarded as an invalid

{ Stating this as an affirmative is stronger.  }


> 3.4.  UTF-8 addresses and Response Codes
>
> An internationalized message 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.

{ The first sentence is restating a normative rule already existing in other 
specifications.  The second sentence is simply confusing.  If the first sentence 
is applied, then the server does not support UTF8SMTPbis.  I suspect what is 
actually meant in the second sentence is something like: }

    If a server receives email encoded in UTF-8, when UTF8SMTPbis is not in 
force, then the server SHOULD reject the message.

{ However, this means that the current specification is trying to dictate 
behavior in the legacy environment, and it cannot do that.

I believe the rule that is actually intended is: }

      An SMTP client MUST only send a message containing UTF-8 to a server that 
supports UTF8SMTPbis.  If the server does not support this option, then the 
client MUST  terminate the delivery attempt with a permanent error, or else find 
another path.


> The three-digit reply codes used in this section are consistent with their
> meanings as defined in RFC 5321.

{ "consistent with"?  I hope you actually mean that they are "the same"! Either 
they are the same as in 5321 or they are changed. }


> When messages are rejected because the RCPT command requires an ASCII
> address, the response code 553 is used with the meaning "mailbox name not

    used -> returned,


> allowed".  When messages are rejected for other reasons, such as the MAIL
> command requiring an ASCII address, the response code 550 is used with the

{  RFC 5321 uses the terms "completion code", "reply code" and "response code" 
interchangeably.  That probably makes the use of "response code" here legal. 
However the formal ABNF in RFC 5321 defines the rules:

      <reply-line>

      <reply-code>

For clarity and precision, I strongly recommend using only those terms when 
referring to replies/responses/completion.  Since the current document is 
cross-referencing a formal construct from another document, it will help the 
reader to resolve the reference by using only the most formal term.}


> meaning "mailbox unavailable".  When the server supports enhanced mail

{ "unavailable" sounds like a temporary error.  More generally, the text here 
says that this set of rejections is "for other reasons".  However it does not 
really mean all other rejections.  Since there are many, different "other 
reasons" and some of them are temporary errors, this text needs to be revised. 
It needs to make clear the difference in handling temporary versus permanent 
errors and in particular it needs to define both types in terms that are 
specific to this enhancement, in order to distinguish them from all other SMTP 
reply-codes.}


> system status codes [RFC3463], response code "X.6.7" [RFC5248] is used,
> meaning that "UTF-8 addresses not permitted for that sender/recipient".
>
> If the response code is issued after the final "." of the DATA command, the
> response code "554" is used with the meaning "Transaction failed".  When the
> server supports enhanced mail system status codes [RFC3463], response code
> "X.6.9" [RFC5248] is used, meaning that "UTF-8 header message can not be
> transferred to one or more recipient so the message must be rejected".
>
> 3.5.  Body Parts and SMTP Extensions
>
> There is no ESMTP parameter to assert that a message is an internationalized
> message.  An SMTP server that requires accurate knowledge of whether a
> message is internationalized is required to parse all message header fields
> and MIME header fields [RFC2045] and [RFC2047] in the message body.

{ This is confusing.  There is a rule against sending an internationalized 
message, unless UTF8SMTPbis is in force, but there is no requirement that the 
server be told explicitly when a message is internationalized???

As noted above, the simple and appropriate action to take is, instead, to have 
the MAIL command contain an <esmtp-param> that declares that the message 
supports internationalized addresses.

My understanding is that this was discussed by the working group.  Why was this 
not the choice of the working group? }


> While this specification requires that servers support the 8BITMIME
> extension [RFC1652] to ensure that servers have adequate handling capability
> for 8-bit data and to avoid a number of complex encoding problems, the use
> of internationalized addresses obviously does not require non-ASCII body
> parts in the MIME message [RFC2045] and [RFC2047].  The UTF8SMTPbis extension
> MAY be used with the BODY=8BITMIME parameter if that is appropriate given
> the body content or, with the BODY=BINARYMIME parameter, if the server
> advertises BINARYMIME [RFC3030] and that is appropriate.

{ This last sentence is either saying too much or too little.  In general, this 
option does not specify MIME or Body details.  Nor does there appear to be any 
reason that it should.  As a consequence, I believe that any text about MIME or 
the Body needs to be non-normative.  It's fine to provide a small amount of 
pedagogy about the carriage of MIME, but including normative language about it 
here merely invites confusion and possibly even divergent specifications.

Also note that the reference to "BODY=" values does not explicitly cite RFC 
1652.  So the references require the reader to already know what is being 
referred to.  This should be fixed.}


> Assuming that the server advertises UTF8SMTPbis and 8BITMIME, and
> receives at least one non-ASCII address, the precise interpretation of
> "BODY=8BITMIME", and "BODY=BINARYMIME" in the MAIL command is: 1.  If a

{  My reading of the current specification is that it does not change the 
handling of email Body or MIME mechanisms.  Hence, DO NOT REPEAT NORMATIVE 
LANGUAGE FROM OTHER SPECIFICATIONS.  It invites divergent specification.  If the 
current specification is actually re-defining the semantics or syntax of RFC 
1652, then it needs to say so. However my reading of the current specification 
is that it is quite independent of email Body issues. }


> BODY=8BITMIME parameter is present, the header contains UTF-8 characters,
> and some or all of the body parts contain 8-bit line-oriented data. 2.  If a
> BODY=BINARYMIME parameter is present, the header contains UTF-8 characters,
> and some or all body parts contain binary data without restriction as to
> line lengths or delimiters.

{ Also note that the items numbered 1 and 2 are not complete sentences.  They 
only contain the conditional clause.  "If...." is missing the "then".  Hence, no 
actual "interpretation" is provided, contrary to the promise that is given.}


> 3.6.  Additional ESMTP Changes and Clarifications
>
> The information carried in the mail transport process involves addresses
> ("mailboxes") and domain names in various contexts in addition to the MAIL
> and RCPT commands and extended alternatives to them.  In general, the rule
> is that, when RFC 5321 specifies a mailbox, this specification expects UTF-8

    this specification -> this SMTP extension

{ "this specification could be misread as meaning RFC 5321, since it is the most 
recent specification references...}


> to be used for the entire string; when RFC 5321 specifies a domain name, the
> name SHOULD be in the form of A-label if its raw form is non-ASCII.

{ the more serious problem is the continuing confusion about ASCII vs. non-ASCII 
and UTF-8 vs non-UTF-8.  Again, I believe that having this extension be in force 
means that this data are /always/ UTF-8.  Hence, it is not a matter of 
"expects".  It is a matter of "requires".}


> The following subsections list and discuss all of the relevant cases.
>
> 3.6.1.  The Initial SMTP Exchange
>
> When an SMTP connection is opened, the server normally sends a "greeting"
> response consisting of the 220 response code and some information.  The

{ "normally"?  what are the exceptions?}


> client then sends the EHLO command.  Since the client cannot know whether
> the server supports UTF8SMTPbis until after it receives the response from
> EHLO, the client must send only ASCII (LDH label [RFC5890] or A-label)
> domains in the EHLO command and that, if the server provides domain names in
> the EHLO response, they must be in the form of LDH labels or A-labels.
>
> 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

      may -> might

or

      may -> can

{ normative vocabulary can only be used for normative statements.  please do a 
global search and replace, where normative vocabulary are used in non-normative 
sentences.}


> 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.

{ This last sentence sounds normative and I believe it should be. So... }

      it is strongly advised that either all or none of them support
      ->
      all or none of them SHOULD support


> Otherwise, surprising rejections
> can happen during temporary failures, which users might perceive as a serious

{ Probably not just temporary failures.  Having services that are meant to be 
redundant with each other actually provide different semantic behavior is just 
plain dangerous. It is essentially guaranteed that they will cause problems.}


> 3.6.3.  Trace Information
>
>    When an SMTP server receives a message for delivery or further
>    processing, RFC 5321 requires that it MUST insert trace ("time stamp"
>    or "Received") information at the beginning of the message content.
>    For the trace information, this memo updates the time stamp line and
>    the return path line [RFC5321] formally defined as follows:

{ Again, don't repeat normative language.  I suggest simply deleting the first 
sentence. }


> [RFC5321] formally defined as follows:
>
> uReturn-path-line = "Return-Path:" FWS uReverse-path <CRLF> ; Replaces
> Return-path-line in Section 4.4 of RFC 5321

{ On reflection, I think the "u" rule-naming convention is problematic.  If the 
current specification is replacing a rule previously defined elsewhere, it needs 
to use the same rulename.  This is simpler and clearer.  Otherwise, all future 
references to the rule need to use the new name.

Rather, where the draft is replacing a rule from another specification, the rule 
definition includes a comment that cites where the original rule is from; that 
should be sufficient. }


> uReverse-path = uPath / "<>" ; Replace Reverse-path in RFC 5321, section
> 4.1.2
>
> uPath = "<" [ A-d-l ":" ] uMailbox ">" ; Replace Path in RFC 5321, section
> 4.1.2 ; uMailbox is defined in section 3.3 of this document
>
> A-d-l = <See section 4.1.2 of RFC 5321>

{ Small improvement:  Where a rule is defined elsewhere, I suggest having the 
descriptive text in the rule say <Defined in...> rather than <See...>. }


> 3.6.4.  UTF-8 Strings in Replies
>
> 3.6.4.1.  RCPT Commands
>
> If an SMTP client follows this specification and sends any RCPT commands
> containing non-ASCII addresses, the SMTP server is permitted to use UTF-8
> characters in the email address associated with 251 and 551 response codes,
> and the client MUST be able to accept and process them.

{ I assume that "follows this specification" means that the UTF8SMTPbis option 
is in force.  If so, then say that, because it is simpler and more precise. But, 
then, it does require declaring /use/ of the option...

However the meaning of the text here is odd.  It implies that the server is not 
permitted to use UTF-8 unless it has already received UTF-8, even though the 
option is in force.  I suspect that that is not the specification that is 
intended.  Or, at least, I hope it is not.

If it actually /is/ what is intended, it means that the enhanced environment is 
going to have all sorts of /additional/ conditional code, to check on whether a 
specific context in the state machine is allowed to act in one way or another.

The simple and more reasonable model is that when the extension is in force, 
UTF-8 is allowed.  Period.  So... }

      If an SMTP session is using this extension, then the server is permitted 
to use UTF-8 characters in the email address associated with 251 and 551 
reply-codes, and the client MUST be able to accept and process them.

{ I chose "SMTP session" to avoid the more complex discussion of the 
client/server 'negotiation' about using the extension.  So, here it is either in 
force or it isn't and if it is in force, it is for client AND server. }


>      If a given RCPT
> command does not include a non-ASCII envelope address, the server MUST NOT
> return a 251 or 551 response containing a non-ASCII mailbox.  Instead, it
> MUST transform such responses into 250 or 550 responses that do not contain
> non-ASCII addresses.

{  See above.  I very strongly disagree with having the complexity this kind of 
conditional requirement creates.  Or else there is a basic issue involved here 
that the document does not discuss but needs to, to justify the complexity. }


> 3.6.4.2.  VRFY and EXPN Commands and the UTF-8REPLY Parameter
>
> If the VRFY and EXPN commands are transmitted with the optional parameter
> "UTF-8REPLY", it indicates the client can accept UTF-8 strings in replies to
> those commands.  This allows the server to use UTF-8 strings in mailbox

{ Is this extension trying to to say that a client might support UTF8SMTPbis but 
not be able to access UTF-8 replies???  Under what circumstance is this 
reasonable? }


> names and full names that occur in replies without concern that the client
> might be confused by them.  An SMTP client that conforms to this

{ What does it mean to be "confused" by them?  Because the extension is in 
force, we know that the client supports UTF-8. }


> specification MUST accept and correctly process replies from the VRFY and
> EXPN commands that contain UTF-8 strings.  However, the SMTP server MUST NOT
> use UTF-8 strings in replies if the SMTP client does not specifically allow
> such replies by transmitting this parameter.  Most replies do not require

{ Why is this constraint required? }


> that a mailbox name be included in the returned text, and therefore UTF-8 is
> not needed in them. Some replies, notably those resulting from successful
> execution of the VRFY and EXPN commands, do include the mailbox, making the
> provisions of this section important.
>
> VERIFY (VRFY) and EXPAND (EXPN) command syntaxes are changed to:
>
> vrfy = "VRFY" SP ( uLocal-part / uMailbox ) [ SP "UTF-8REPLY" ] CRLF ;
> uLocal-part and uMailbox are defined in ; Section 3.3 of this document.
>
> expn = "EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF-8REPLY" ] CRLF ;
> uLocal-part and uMailbox are defined in ; Section 3.3 of this document.

{ Note that these rules only specify UTF-8 support, without any contingency on 
use.  That is, they do not cover the variability that is described in the prose, 
and that disparity from the prose specification is an example of the complexity 
created by having the use of UTF-8 in replies be so contingent on the actual 
data sent by the client. }


> If a normal success response (i.e., 250) is returned, the response MAY
> include the full name of the user and MUST include the mailbox of the user.
> It MUST be in either of the following forms:
>
> User Name <uMailbox> ; uMailbox is defined in Section 3.3 of this document.
> ; User Name can contain non-ASCII characters.
>
> uMailbox ; uMailbox is defined in Section 3.3 of this document.

{ "User Name" needs to be specified as an abnf rule.  It isn't.

This appears to be intended to invoke the RFC 5322 definition of <mailbox> 
rather than the RFC 5321 definition.  In any event, it is creating a semantic 
change to the response, from RFC 5321, beyond merely allowing UTF-8 characters. }


> 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 "X.6.8" [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".

{ "the mailbox name"?  which string is that? }


> If the SMTP client does not support the UTF8SMTPbisbis extension, but receives
> a UTF-8 string in a reply, it may not be able to properly report the reply

If a UTF-8 string is sent in a reply, when this extension is not in force, then 
it is a protocol violation.  Period.


> [RFC4952bis] Klensin, J. and Y. Ko, "Overview and Framework for
> Internationalized Email", RFC 4952, July 2010.

      RFC4951
      ->
      draft-ietf-eai-frmwrk-4952bis

{ It is not now, and never will be, RFC 4952;  And RFC4952bis is currently dated 
September 2010. When it is an RFC, it will have a new number.

Also, Internet Drafts, including -bis documents, usually follow a different 
citation labeling convention, such as I-D.rfc4952bis, to make clear that they 
are an I-D and not an RFC. }




[1]  draft-ietf-eai-frmwrk-4952bis-10

[2]  draft-ietf-eai-rfc5335bis-03


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc@dcrocker.net  Wed Dec 22 10:11:47 2010
Return-Path: <dhc@dcrocker.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 889C93A6A58; Wed, 22 Dec 2010 10:11:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 snNxGobXMIJz; Wed, 22 Dec 2010 10:11:46 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 99F6A3A6909; Wed, 22 Dec 2010 10:11:46 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBMIDa0K013617 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2010 10:13:42 -0800
Message-ID: <4D123FD1.2080906@dcrocker.net>
Date: Wed, 22 Dec 2010 10:13:37 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ima@ietf.org
References: <4D123DC0.2050501@dcrocker.net>
In-Reply-To: <4D123DC0.2050501@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Dec 2010 10:13:42 -0800 (PST)
Cc: Alexey.Melnikov@isode.com, draft-ietf-eai-rfc5336bis@tools.ietf.org, Apps Discuss <apps-discuss@ietf.org>, SM <sm+ietf@elandsys.com>
Subject: Re: [EAI] [apps-discuss] (private) draft review of:	draft-ietf-eai-rfc5336bis-07.txt (v3)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 22 Dec 2010 18:11:47 -0000

Folks -- Apologies for the pre-posting detritus on the subject line.  Obviously 
it was (no longer) a private message.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc@dcrocker.net  Wed Dec 22 13:37:35 2010
Return-Path: <dhc@dcrocker.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 73E2D3A6B06; Wed, 22 Dec 2010 13:37:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 lnRAJh-6AxzH; Wed, 22 Dec 2010 13:37:31 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 622FC3A68F7; Wed, 22 Dec 2010 13:37:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFX+EU2HCzI1/2dsb2JhbACkIXOqMQKZHYMMDIIxBIRmiTsGFA
X-IronPort-AV: E=Sophos;i="4.60,215,1291611600"; d="scan'208";a="224496323"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Dec 2010 16:39:27 -0500
X-IronPort-AV: E=Sophos;i="4.60,215,1291611600"; d="scan'208";a="561933639"
Received: from unknown (HELO 307622ANEX1.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Dec 2010 16:39:24 -0500
Received: from mail pickup service by 307622ANEX1.global.avaya.com with Microsoft SMTPSVC; Wed, 22 Dec 2010 22:38:46 +0100
Received: from 307622ANEX4.global.avaya.com ([135.64.140.11]) by 307622ANEX1.global.avaya.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 Dec 2010 19:06:00 +0100
Received: from co300216-co-erhwest.avaya.com ([198.152.7.5]) by 307622ANEX4.global.avaya.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 Dec 2010 19:05:20 +0100
X-IronPort-AV: E=Sophos;i="4.60,214,1291611600"; d="scan'208";a="559820276"
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]) by co300216-co-erhwest.avaya.com with ESMTP; 22 Dec 2010 13:05:18 -0500
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMAACTMEU1AqmIgimdsb2JhbACkFxUBAQEKCQwHDwcfqlACmSqDDAyCMQSEZok7
X-IronPort-AV: E=Sophos;i="4.60,214,1291611600"; d="scan'208";a="256306575"
Received: from mail.ietf.org ([64.170.98.32]) by co300216-co-ierwest.avaya.com with ESMTP; 22 Dec 2010 13:05:14 -0500
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48BAB3A6A88; Wed, 22 Dec 2010 10:03:06 -0800 (PST)
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 448D73A6925; Wed, 22 Dec 2010 10:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 3n2X7E2rjUvK; Wed, 22 Dec 2010 10:03:00 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 279EC3A6909; Wed, 22 Dec 2010 10:03:00 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBMI4mYh013364 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2010 10:04:53 -0800
Message-ID: <4D123DC0.2050501@dcrocker.net>
Date: Wed, 22 Dec 2010 10:04:48 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Apps Discuss <apps-discuss@ietf.org>, ima@ietf.org, draft-ietf-eai-rfc5336bis@tools.ietf.org, SM <sm+ietf@elandsys.com>, Alexey.Melnikov@isode.com
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Dec 2010 10:04:55 -0800 (PST)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: apps-discuss-bounces@ietf.org
Errors-To: apps-discuss-bounces@ietf.org
X-OriginalArrivalTime: 22 Dec 2010 18:05:20.0285 (UTC) FILETIME=[CBCA2CD0:01CBA202]
Subject: [EAI] [apps-discuss] (private) draft review of:	draft-ietf-eai-rfc5336bis-07.txt (v3)
X-BeenThere: ima@ietf.org
Reply-To: dcrocker@bbiw.net
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: Wed, 22 Dec 2010 21:37:35 -0000

IETF Applications Review


I have been selected as an Applications Area Review Team reviewer for this
draft.

For background on apps-review, please see:
<http://www.apps.ietf.org/content/applications-area-review-team>

Please resolve these comments along with any other Last Call comments you
may receive. Please wait for direction from your document shepherd or AD
before posting a new version of the draft.



Document: draft-ietf-eai-rfc5336bis-07.txt
Reviewer: Dave Crocker, Brandenburg InternetWorking
Review Date: 2010-12-22


BACKGROUND:

      The document is a specification for an email transport-time option that is 
described in its Abstract as declaring support for "internationalized email 
addresses or header information" and in the Introduction as being "to support an 
internationalized email address".  The extension specifies changes both in the 
transfer protocol and in the message being transferred, including its Body. 
Legacy Internet Mail only supports classic "network ASCII" for data 
representation and for data transfer encoding.

      The charter for the current work cites previous work that was issued as 
Experimental, and summarizes it as having been "... based on the use of an
SMTP extension to enable the use of UTF-8 in envelope address
local-parts, optionally in address domain-parts, and in mail
headers."  This text appears also to serve as the statement of scope for the 
current working group.

      With respect to the mail header, the scope is specified as covering 
<address> and <encoded-word> constructs.  An <encoded-word> is a means of 
mapping Unicode strings onto classic, network ASCII, although the working group 
focus was on binary, UTF-8 support.


RECOMMENDATIONS:

This work represents an extremely important enhancement to Internet mail. It has 
been clear for twenty years that Internet applications need to be able to 
present data in a form that is natural to the user.

The current work benefits from providing a Framework document and from 
distinguishing changes to the email header from changes to the SMTP protocol.

    0.  The documents do raise distinctions between ASCII and Unicode, versus 
between ASCII and UTF-8. However they do not apply them rigorously in the 
documents.  I suggest that the term "internationalization" be used only during 
introductory discussion and never as part of normative text.  ASCII vs. Unicode 
is a distinction between the underlying range of data being represented.  ASCII 
vs. UTF-8 is a distinction between encoding environments. Text should explicitly 
indicate whether it means data representation versus data encoding and it should 
use Unicode for the former and UTF-8 for the latter.

    1.  The Framework document is normative and needs to be completed along with 
the other two specifications, since they quite reasonably state a normative 
dependence on the Framework document.

    2.  The SMTP extension draft needs to focus on SMTP and the direct support 
of UTF-8 in the message header.  It needs to move all discussion and 
specification of Unicode support in the Header to the Header draft.

    3.  There probably needs to be definition of MIME message/uni-rfc822, 
specifying Unicode support within a message contained in MIME.  I'm less clear 
whether there needs to be a MIME Content-Transfer-Encoding form specific to UTF-8.

    4.  The SMTP extension needs to have the client use an explicit signal when 
it is sending a message encoded in UTF-8. This is easiest as a parameter to the 
MAIL command.  The current specification creates a more complex and almost 
heuristic model for distinguishing ASCII from UTF-8 use.

    5.  The SMTP extension needs to remove all restrictions it imposes on MIME 
content-type.  A major reason that MIME was successful was that it was 
transparent to the transfer infrastructure.  The current SMTP extension 
specification changes this model, which actually increases the barrier to 
adoption of Unicode in email.  It needs to be easy for two MUAs that support 
Unicode in the email header to exchange mail even when the infrastructure does 
not support UTF-8.



SUMMARY COMMENTS:

The document conforms to the conventions for defining SMTP options.

There are a number of significant issues with the specification. These are 
covered in detail, below, and are summarized here:

      *  Framework -- The Framework document[1] is (correctly) referenced as 
required reading.  It supplies essential terminology and architecture for this 
specification.  In fact it is a specification, complete with formally normative 
vocabulary.  This means that it must be a normative reference by rfc5336bis.  It 
therefore also means that the Framework document needs to be completed before 
the current specification can be standardized.

      *  Scope -- the specification appears to go significantly beyond the scope 
of the working group's charter, including revisions to basic SMTP that have no 
obvious requirement for support of Unicode during transport. In fact, at least 
one change is likely to /restrict/ system-wide adoption, rather than encourage 
it!  In particular, the specification restricts the conditions under which some 
MIME content is allowed to be sent. (See next bullet.)

      *  Infrastructure Requirement -- Unless this option is in force, carrying 
internationalized email in a MIME part is prohibited.  This is out of scope for 
the working group and it is a counter-productive rule.  Imagine if the same type 
of rule had been specified when MIME was created, saying that MIME could only be 
sent when an "attachments-supported" option were in force. This would have 
prevented the early adoption of MIME use by individual MUAs until the entire 
infrastructure supported MIME.   (As an example of the very high barrier this 
raises, note the difference in real-world support and use of MDN versus DSN.) 
While it is reasonable for the working group to define a new MIME content-type 
that modifies message/rfc822 to support internationalized addresses, it is not 
appropriate for the working group to modify the SMTP transfer model to constrain 
what types of message content can be sent.

      *  Beyond <encoded-word> -- The work, here, appears to have two goals. One 
is to add support for Unicode in a <local-part>; that is, support for 
internationalized addresses.  However note that <encoded-word> and <A-label> 
already accomplish this in a way that is transparent to the existing email 
infrastructure; only the end-systems need to understand it.  The second goal is 
to support Unicode in the more "native" form of UTF-8. (The quotation marks are 
because UTF-8 is not native Unicode, either; it is a highly encoded form of 
Unicode...)  This creates some confusion in the specification.  Given that the 
option for SMTP is "UTF8SMTPbis", then the binary encoding goal seems to 
dominate the work. This is a certainly a reasonable goal, but it will help the 
clarity of the specification to make these two different goals more clear within 
the document and to apply them more carefully.

      *  Terminology confusion -- The Framework document carefully distinguishes 
between "ASCII addresses and non-ASCII addresses.  It equates 
"internationalized" first with "non-ASCII", but then with "UTF8SMTPbis". A core 
problem is that ASCII is part of the actual internationalized set of Unicode 
characters. So, to say that "international" characters are non-ASCII is exclude 
part of Unicode from the term "international".  In addition, equating the term 
"internationalization" with UTF-8 encourages confusion between underlying or 
"native" data -- that is, Unicode -- with the way it is represented over the 
wire.  UTF-8 is merely one means of over-the-wire representation.  So, for 
example, <A-label> and <encoded-word> are two other means of encoding.  It's 
clear that this core distinction really is understood by the authors of this and 
the Framework documents.  However the vocabulary choices and their usage create 
a problem in the details of the specification.  "Internationalization" should 
mean Unicode, not a particular binary representation of it within 8-bit chunks. 
  The problem, here, is in using the term "internationalization" to refer to a 
subset of Unicode, that is, the subset that is not ASCII.  I strongly suggest 
saying "Unicode" when intending to refer to the richer set of characters that 
are the goal of this work, and "UTF-8" when referring to the particular binary 
encoding of Unicode that is the focus of the SMTP extension work.

      *  Non-UTF-8 Unicode support -- Can a message support Unicode without 
UTF-8?  The existence of <encoded-word> and <A-label> constructs makes clear 
that the answer is yes.  Hence, it should be possible to support Unicode 
messages, without this SMTP extension.  Perhaps this is out of scope for this 
SMTP extension and perhaps it is handled by the Email Header draft, but I think 
it worth having this document cite this alternative mode, if only to a) make 
clear that the alternative exists, and b) make more clear what the specific and 
strong benefit of this extension is.

      *  Partial enforcement --  Since ASCII is a subset of Unicode, having this 
extension be in force means that /everything/ is Unicode AND, apparently, is 
encoded in UTF-8.  If the environment created by this extension supports UTF-8, 
then it supports UTF-8, meaning both ASCII and non-ASCII.  Defining rules that 
depend on having this extension be in force but then still distinguish between 
ASCII and non-ASCII does not seem to make sense.

      *  Complexity and Heuristics -- In a number of places, the specification 
defines highly contingent action, where one side can use UTF-8 only if the other 
side has done so. This makes the enhancement much more complicated than 
necessary or appropriate. The enhancement needs to work with an all-or-nothing 
model in which UTF-8 is in force or it is not.  And, yes, this appears to be a 
major change in the model of this specification.  My understanding is that these 
issues were discussed in the working group, but I do not understand why  and 
nearly-heuristic approach was preferred.  Instead I recommend the client to 
signal explicitly when UTF8-encoded addresses are present, such as a 
<Mail-parameters> option (<esmtp-param>) to the MAIL command.

      *  5321 vs. 5322 -- The specification seems to confuse -- or at least to 
mix -- some rules from RFC 5321 versus some from RFC 5322.  <mailbox> is the 
major example.

      *  Since an RFC 5322 message can and often does exist outside of the SMTP 
environment, any changes to the RFC 5322 specification should be in a document 
that is separate from this extension specification.  This specification can then 
cite it.  I suggest moving all RFC 5322 changes to the Header document[2]  and 
merely citing it here.

      *  UTF8SMTPbis -- The draft uses the string "UTF8SMTPbis" when referencing 
the SMTP option.  The Framework document explains the choice, but IANA 
Considerations in this document needs to provide explicit handling instructions 
for it, since this is certain NOT to be the actual string that is used.

      *  Redundant Specification - in a number of places, normative language 
from other specifications is repeated.  This invites divergent specification and 
is generally out of scope for the current work. To the extent that the current 
specification needs to refer to normative parts of other specifications, it 
should do only that:  cite it; do not repeat it.  For example to highlight an 
important normative item from another specification, the current specification 
might describe the "topic" the external language covers, without saying what it 
says.  In other cases, the key point is that the current specification is not 
changing requirements from another specification; that is what should be said, 
rather than repeating what that requirement is. In general, these references to 
external, normative behaviors should be reviewed for relevance to the current 
work.  How is internationalized addresses relevant to the normative detail?

      *  Rule Meta-Naming -- The 'u' preface for revised rules is a reasonable 
idea, but appears to be problematic.  These rules replace existing rules in 
other specifications. There needs to be an explicit and decision about the 
handling of this, and it needs to be applied consistently, either directly 
replacing the rules or else re-naming them consistently, in a fashion that can 
be parsed (similar to the naming template that was done with RFC5322 obs-* 
rules.)  If an initial string is to be used, I suggest UTF-8-* rather than u*, 
in order to make it possible to parse this meta-label more reliably.





DETAILED COMMENTS:

{ I have included text from the draft that provides context, but have skipped 
sequences of text from the draft that do not. }


> 1.  Introduction
>
> The Simple Mail Transfer Protocol [RFC5321] provides a negotiation mechanism
> about service extension with which clients can discover

      with which ->  by which { or } through which

{ Either of these would be my stylistic preference. }


> server capabilities and make decisions for further processing.  This
> document use this mechanism to support an internationalized email

      use -> uses


> address.  An extended overview of the extension model for

{ The option enables use of UTF-8 in the email header, beyond just addresses,
therefore: }

      to support...address
      ->
      to support internationalized email addresses and internationalized
characters for the email header.


> internationalized addresses and headers appears in [RFC4952bis],

      headers -> the email header


> referred to as "the framework document" or just as "framework" elsewhere in
> this specification.  This document specifies an SMTP extension to permit
> internationalized email addresses in envelopes,

      envelopes -> the SMTP envelope

{ 1.  Although 'envelope' is almost certainly unambiguous, its use over the
years has been confusing, so it is worth being particularly clear in a
specification.

   2.  The use of plurals in a specification can be confusing.  I suggest using
the singular form wherever it can work, so that remaining use of plurals becomes
more precise. Also note the particular confusion with the word "headers" in 
email.  Since a single email has only a single header, the use of plural means 
each header from a set of messages... }


> and UNICODE characters (encoded in UTF-8) [RFC3629] in headers.

      headers -> the header


> 1.1.  Role of This Specification
>
> The framework document specifies the requirements for, and describes
> components of, full internationalization of the electronic mail.  A thorough
> understanding of the information in that document and in the base Internet
> email specifications [RFC5321] [RFC5322] is necessary to understand and
> implement this specification.

{ This means that the Framework document is normative; it needs to be cited as 
such.  Since understanding it is a pre-condition of reading the specification, 
it also requires that the Framework document be completed before this document. }


> This document specifies an element of the email internationalization work,
> specifically the definition of an SMTP extension for internationalized email
> address transport delivery.

{ Since it also declares support for internationalization in the message header,
it covers more than delivery.  In effect, it is a transport-time flag for
declaring internationalization of the entire email "environment".  I'm not quite
sure what exact language change to suggest, however.

I also note that it does more than declare support for internationalized 
addresses:  It declares support for encoding them into UTF-8. This is a 
significant, additional requirement and should be stated explicitly. }


> 1.2.  Terminology
..
> This specification defines only those Augmented BNF (ABNF) [RFC5234] syntax
> rules that are different from those of the base email specifications and,
> where the earlier rules are upgraded or extended, gives them new names.
> When the new rule is a small modification to

{ The wording in the first part of this paragraph seems awkward.  I think the
following is clearer: }

      This specification uses Augmented BNF (ABNF) rules [RFC5234], with some
modifications.  The modified rules are defined here and the rest are simply 
imported from [RFC5234].  New names are used, for rules that are upgraded
or enhanced.  When the ...


> the older one, it is typically given a name starting with "u".  Rules

{ The use of "typically" makes the description of this convention problematic. 
It needs to be always true or else not mentioned.  Or perhaps alternative 
phrasing:  }

      When a new...with "u".
      ->
      When a new rule has a name starting with "u", it is a small modification to
an older rule.

{ This asserts what is true and ignores what is not true, such as rules that 
qualify for the "u" but did not get it...

However I now believe that it is important to have a consistent meta-rule for 
naming the revised rules and that it be applied consistently to all rules that 
qualify for it.  Further, the naming convention should be easily parseable, and 
therefore more like what is used in RFC5322, to cover "obsolete" rules.  I 
suggest that new rules, here, be named UTF-8-*.  To repeat:  I believe that 
/all/ rules that resolve to UTF-8 must be renamed, so that implementers know 
what they need to change. }


> that are undefined here may be found in the base email specifications

{ The specifications should be cited here, explicitly, even though they have 
been cited elsewhere.  It is important to leave no ambiguity for the reader. }

      here may be -> here can be

{"may" is a reserved word for normative specification. Normative meaning is not 
based on the use of capitalization. }


> 3.2.  The UTF8SMTPbis Extension

> An SMTP server that announces this extension MUST be prepared to
>    accept a UTF-8 string [RFC3629] in any position in which RFC 5321
>    specifies that a mailbox can appear.  That string MUST be parsed only
>    as specified in [RFC5321], i.e., by separating the mailbox into

{ The 'i.e.' clause is an example of repeating normative text from another 
specification.

The current document is not empowered to give directives about basic SMTP 
parsing, nor is there any internationalization requirement that it do so.  At 
most, it should say that the changes specified in this document do not change 
any other aspect of SMTP processing. }


>         Once isolated by this parsing process, the local part MUST be
>    treated as opaque unless the SMTP server is the final delivery Mail
>    Transfer Agent (MTA).

{ The statement about handling of <local-part> is redundant with the base RFC 
5321 specification.  The statement, here, should be that the handling of 
<local-part> is unchanged from the base specification.  Again, it should not 
repeat the normative language, unless it is changing it.  If it is changing it, 
the change needs to be essential for support of internationalized addresses. }


>                        Any domain names that are to be
>    compared to local strings SHOULD be checked for validity and then
>    MUST be compared as specified in section 3 of [RFC5891].

{ Dictating use of RFC5891 is within scope.  Dictating validation seems not to 
be.  So...}

    -> Any domain name that is to be compared to a local string MUST use Section 
3 of [RFC5891] as the basis for comparison.


> An SMTP client that receives the UTF8SMTPbis extension keyword in response
> to the EHLO command MAY transmit mailbox names within SMTP commands as
> internationalized strings in UTF-8 form.  It MAY send a UTF-8 header
> [RFC5335bis] (which may also include mailbox names in UTF-8).  It MAY
> transmit the domain parts of mailbox names within SMTP commands or the
> message header as A-labels or U-labels

{ I believe that the use of "MAY" is not correct. This would mean that the 
receiver needs a means of distinguishing whether the data are UTF-8 or not. This 
would border on requiring support of a heuristic, but it certainly adds a 
significant processing overhead and additional software complexity.

The only alternative is to specify use of a MAIL command <Mail-parameters> 
option that declares that the message supports internationalized addresses. 
Given the approach in this specification, I believe the intent is also to have 
it mean that UTF-8 encoding is supported.

The core issue here is specifying an option which declares a message to have an 
EAI context for all of the message.  So the processing context is fully 
EAI/UTF-8 or it is legacy net-ASCII.  This is considerably simpler to specify 
and to process, than would be requiring parsing the incoming string and looking 
for non-ASCII UTF-8.

Hence: }

      An SMTP client...U-labels
      ->
      An SMTP client that receives the UTF8SMTPbis extension keyword, in response to
the EHLO command, will transmit <local-part> within SMTP commands as
internationalized strings in UTF-8 form.  It will send the email header in UTF-8
[RFC5335bis] (which can also include <mailbox> names in UTF-8.)  It also will
transmit the domain parts of mailbox names within SMTP commands or the message
header as A-labels or U-labels

{ Note - the term "mailbox names" is not defined here or in RFC 5321.  In RFC 
5321 it appears to be used to mean local-part; however becasue its precise 
meaning is unclear, I strongly urge NOT using it here at all. Instead I suggest 
using whatever ABNF rulename is appropriate.  This guarantees clarity.

   Note:  I changed 'may' to 'can'. Also, when an ABNF rule is being cited within
prose text, such as for <mailbox>, it should be distinguished so that the reader
knows it is a formal term.  I have used <> to bracket the term mailbox. }


> All labels in domain parts of mailbox names which are IDN
>    forms of A-labels or U-labels MUST be valid.

{ This is strange.  Either it is repeating a normative requirement from SMTP or 
it is expanding SMTP to require special validation for IDN forms of domain names 
that is not present for ASCII forms.  Neither interpretation seems like the 
right thing to be doing here. Such a modification to SMTP seems out of scope.

Also, the term <mailbox> has different semantic definitions in RFC 5321 and RFC 
5322.  A strict reading of the differences could be a problem.  A loose reading 
would note that both definitions reduce to include <local-part> and <domain> 
components that are common to both specifications.  I encourage you to review 
this issue carefully and put a note at the beginning of the document stating 
explicitly how you have chosen to handle it.

My best recommendation is that this document should only refer to RFC 5321 ABNF 
and that it should move /all/ RFC 5322 modifications or enhancements to the EAI 
Header document (draft-ietf-eai-rfc5335bis). }


>                    When a Mail User
>    Agent(MUA) submits a message to a Message Submission Server
>    ("MSA")[RFC4409], it is the responsibility of the MSA to ensure that
>    all domain labels are valid.

{ Given that this specification creates broad systemic effects and given that it 
needs to refer to components other than an SMTP client or server, it should cite 
RFC 5598, to give the reader an integrated view of the email service. I'll note 
that citing 5598 has become common for email specifications; so this is not a 
controversial suggestion. }


>The presence of the UTF8SMTPbis
>    extension does not change the requirement of RFC 5321 that servers
>    relaying mail MUST NOT attempt to parse, evaluate, or transform the
>    local part in any way.

{ This sentence replicates normative language from a different specification. 
This is a very bad thing to do, in case the original specification changes its 
language.  I suggest: }

      The presence of...in any way
      ->
      The presence of the UTF8SMTPbis extension does not change RFC 5321 server
relaying behaviors.

{ this retains some text as a flag to the reader, but does not provide the
specific semantics, which might change in the original specification. }


> If the UTF8SMTPbis SMTP extension is not offered by the server, the SMTP
> client MUST NOT transmit an internationalized address and MUST NOT transmit

{ This appears to prohibit the sending of internationalized addresses that are 
encoded in ASCII, rather than in UTF-8.  The purpose of ASCII encoding is to 
eliminate the need for infrastructure support for Unicode characters.  However 
the language here appears to be imposing the barrier of infrastructure support. 
  If the concern is sending UTF-8, then that's the language that needs to be 
used.  Messages with ASCII-encoding of internationalized addresses need to be 
permitted to be sent, without first requiring infrastructure support. }


> a mail message containing internationalized mail headers as described in
> [RFC5335bis] at any level within its MIME structure [RFC2045] and [RFC2047].

{ The prohibition of internationalized mail headers within a MIME structure -- 
"at any level within its MIME structure"  -- is out of scope for the working 
group and is a /major/ change to SMTP.  It is also a really terrible rule!  In 
terms of protocol modeling, it would have been like saying that no one could use 
MIME until the infrastructure supported it!

It is one thing to give the reader a reminder that UTF-8 is illegal in the email 
header of a message and quite another to attempt to prohibit it in attachments. 
  Attachments already carry all sorts of data.  UTF-8 is merely one more type. I 
believe that there currently no SMTP constraints on the carriage of MIME; I also 
believe it essential that there not be, since such constraints impede adoption. 
  (That is why MDN support is good and DNS support is poor.)

Also note that MIME objects exist outside of email transport and that directives 
about legal or illegal MIME ought to be separated from SMTP...

Also, perhaps mail with UTF-8 in the header needs a different
MIME type, such as text/UTF-8-message?... }


> 2.  It may either reject the message during the SMTP transaction or accept

      may -> MAY

{ However, I note that this concerns a SMTP client, not a server.

> 3.3.  Extended Mailbox Address Syntax
>
> RFC 5321, Section 4.1.2, defines the syntax of a mailbox entirely in terms
> of ASCII characters, using the production for a mailbox and those productions

      mailbox ->  <mailbox>


> on which it depends.
>
> The key changes made by this specification are, informally, to

{ I don't understand what it means to change RFC 5321 "informally".  I think it 
is intended to mean that the list is not guaranteed to be complete.  If so, I 
suggest wording such as: }

    -> The key changes made by this specification include:


> o  Change the definition of "Domain" to permit either the RFC 5321 definition
> above or a UTF-8 string representing a DNS label that is conformant with
> IDNA definitions [RFC5890].

{ "either"???  That sounds completely ambiguous.  }


> o  Change the definition of "Local-part" to permit either the definition
> above or a UTF-8 string.  That string MUST NOT contain any of the ASCII
> characters (either graphics or controls) that are not permitted in "atext";
> it is otherwise unrestricted.

{ same concern as above.  }


> According to the description above, the syntax of an internationalized email
> mailbox name (address) is defined in ABNF [RFC5234] as follows.
>
> uMailbox = uLocal-part "@" ( uDomain / address-literal ) ; Replace Mailbox
> in RFC 5321, Section 4.1.2

{  This implies that the option applies only to RFC5321 and not to RFC5322, but 
the later rules make clear that 5322 is also supposed to be covered.

To repeat:  I recommend that all RFC 5322 enhancements and ABNF should be moved 
to the EAI Header draft and that the SMTP extension should merely cite that draft.

Note that RFC5322 is for an object that can and does exist outside of SMTP. 
Enhancements to RFC5322 well might need to apply when there is no SMTP, or at 
least long after it is relevant.  }


> UTF-8-non-ASCII = UTF-8-2 / UTF-8-3 / UTF-8-4
>
> UTF-8-2 =  <See Section 4 of RFC 3629>
>
> UTF-8-3 =  <See Section 4 of RFC 3629>
>
> UTF-8-4 =  <See Section 4 of RFC 3629>

{ These rules are also defined in RFC5335 and draft-ietf-eai-rfc5335bis.  Citing 
RFC 3629 is therefore confusing, and possibly can create specification 
divergence. I suspect that RFC 3629 is not the correct reference, here, since it 
would imply that RFC5335bis' definitions should be ignored... If RFC 3629 /is/ 
the correct reference, then I cannot guess why and I cannot guess why it will 
not create problems with divergent specification. }


> The value of "uDomain" SHOULD be verified by IDNA definitions [RFC5890].  If

{  I do not understand what "SHOULD be verified by IDNA definitions" means.

If it means that the uDomain "SHOULDbe verified" then it is out of scope for 
this specification. There is no reason that SMTP rules concerning verification 
of Unicode-based domains needs to be different from ASCII-based domains.  In 
particular, verification of a Domain name is specified elsewhere.

If it means that the uDomain "should be IDNA complaint" then I do not understand 
having the exceptions that a "should" allows.  For this EAI work, I would think 
that when UTF8SMTPbis is in force, then IDNA compliance needs to be a MUST.  }


> that verification fails, the email address with that uDomain MUST NOT be
> regarded as a valid email address.

    MUST NOT be regarded as a valid
    ->
    MUST BE regarded as an invalid

{ Stating this as an affirmative is stronger.  }


> 3.4.  UTF-8 addresses and Response Codes
>
> An internationalized message 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.

{ The first sentence is restating a normative rule already existing in other 
specifications.  The second sentence is simply confusing.  If the first sentence 
is applied, then the server does not support UTF8SMTPbis.  I suspect what is 
actually meant in the second sentence is something like: }

    If a server receives email encoded in UTF-8, when UTF8SMTPbis is not in 
force, then the server SHOULD reject the message.

{ However, this means that the current specification is trying to dictate 
behavior in the legacy environment, and it cannot do that.

I believe the rule that is actually intended is: }

      An SMTP client MUST only send a message containing UTF-8 to a server that 
supports UTF8SMTPbis.  If the server does not support this option, then the 
client MUST  terminate the delivery attempt with a permanent error, or else find 
another path.


> The three-digit reply codes used in this section are consistent with their
> meanings as defined in RFC 5321.

{ "consistent with"?  I hope you actually mean that they are "the same"! Either 
they are the same as in 5321 or they are changed. }


> When messages are rejected because the RCPT command requires an ASCII
> address, the response code 553 is used with the meaning "mailbox name not

    used -> returned,


> allowed".  When messages are rejected for other reasons, such as the MAIL
> command requiring an ASCII address, the response code 550 is used with the

{  RFC 5321 uses the terms "completion code", "reply code" and "response code" 
interchangeably.  That probably makes the use of "response code" here legal. 
However the formal ABNF in RFC 5321 defines the rules:

      <reply-line>

      <reply-code>

For clarity and precision, I strongly recommend using only those terms when 
referring to replies/responses/completion.  Since the current document is 
cross-referencing a formal construct from another document, it will help the 
reader to resolve the reference by using only the most formal term.}


> meaning "mailbox unavailable".  When the server supports enhanced mail

{ "unavailable" sounds like a temporary error.  More generally, the text here 
says that this set of rejections is "for other reasons".  However it does not 
really mean all other rejections.  Since there are many, different "other 
reasons" and some of them are temporary errors, this text needs to be revised. 
It needs to make clear the difference in handling temporary versus permanent 
errors and in particular it needs to define both types in terms that are 
specific to this enhancement, in order to distinguish them from all other SMTP 
reply-codes.}


> system status codes [RFC3463], response code "X.6.7" [RFC5248] is used,
> meaning that "UTF-8 addresses not permitted for that sender/recipient".
>
> If the response code is issued after the final "." of the DATA command, the
> response code "554" is used with the meaning "Transaction failed".  When the
> server supports enhanced mail system status codes [RFC3463], response code
> "X.6.9" [RFC5248] is used, meaning that "UTF-8 header message can not be
> transferred to one or more recipient so the message must be rejected".
>
> 3.5.  Body Parts and SMTP Extensions
>
> There is no ESMTP parameter to assert that a message is an internationalized
> message.  An SMTP server that requires accurate knowledge of whether a
> message is internationalized is required to parse all message header fields
> and MIME header fields [RFC2045] and [RFC2047] in the message body.

{ This is confusing.  There is a rule against sending an internationalized 
message, unless UTF8SMTPbis is in force, but there is no requirement that the 
server be told explicitly when a message is internationalized???

As noted above, the simple and appropriate action to take is, instead, to have 
the MAIL command contain an <esmtp-param> that declares that the message 
supports internationalized addresses.

My understanding is that this was discussed by the working group.  Why was this 
not the choice of the working group? }


> While this specification requires that servers support the 8BITMIME
> extension [RFC1652] to ensure that servers have adequate handling capability
> for 8-bit data and to avoid a number of complex encoding problems, the use
> of internationalized addresses obviously does not require non-ASCII body
> parts in the MIME message [RFC2045] and [RFC2047].  The UTF8SMTPbis extension
> MAY be used with the BODY=8BITMIME parameter if that is appropriate given
> the body content or, with the BODY=BINARYMIME parameter, if the server
> advertises BINARYMIME [RFC3030] and that is appropriate.

{ This last sentence is either saying too much or too little.  In general, this 
option does not specify MIME or Body details.  Nor does there appear to be any 
reason that it should.  As a consequence, I believe that any text about MIME or 
the Body needs to be non-normative.  It's fine to provide a small amount of 
pedagogy about the carriage of MIME, but including normative language about it 
here merely invites confusion and possibly even divergent specifications.

Also note that the reference to "BODY=" values does not explicitly cite RFC 
1652.  So the references require the reader to already know what is being 
referred to.  This should be fixed.}


> Assuming that the server advertises UTF8SMTPbis and 8BITMIME, and
> receives at least one non-ASCII address, the precise interpretation of
> "BODY=8BITMIME", and "BODY=BINARYMIME" in the MAIL command is: 1.  If a

{  My reading of the current specification is that it does not change the 
handling of email Body or MIME mechanisms.  Hence, DO NOT REPEAT NORMATIVE 
LANGUAGE FROM OTHER SPECIFICATIONS.  It invites divergent specification.  If the 
current specification is actually re-defining the semantics or syntax of RFC 
1652, then it needs to say so. However my reading of the current specification 
is that it is quite independent of email Body issues. }


> BODY=8BITMIME parameter is present, the header contains UTF-8 characters,
> and some or all of the body parts contain 8-bit line-oriented data. 2.  If a
> BODY=BINARYMIME parameter is present, the header contains UTF-8 characters,
> and some or all body parts contain binary data without restriction as to
> line lengths or delimiters.

{ Also note that the items numbered 1 and 2 are not complete sentences.  They 
only contain the conditional clause.  "If...." is missing the "then".  Hence, no 
actual "interpretation" is provided, contrary to the promise that is given.}


> 3.6.  Additional ESMTP Changes and Clarifications
>
> The information carried in the mail transport process involves addresses
> ("mailboxes") and domain names in various contexts in addition to the MAIL
> and RCPT commands and extended alternatives to them.  In general, the rule
> is that, when RFC 5321 specifies a mailbox, this specification expects UTF-8

    this specification -> this SMTP extension

{ "this specification could be misread as meaning RFC 5321, since it is the most 
recent specification references...}


> to be used for the entire string; when RFC 5321 specifies a domain name, the
> name SHOULD be in the form of A-label if its raw form is non-ASCII.

{ the more serious problem is the continuing confusion about ASCII vs. non-ASCII 
and UTF-8 vs non-UTF-8.  Again, I believe that having this extension be in force 
means that this data are /always/ UTF-8.  Hence, it is not a matter of 
"expects".  It is a matter of "requires".}


> The following subsections list and discuss all of the relevant cases.
>
> 3.6.1.  The Initial SMTP Exchange
>
> When an SMTP connection is opened, the server normally sends a "greeting"
> response consisting of the 220 response code and some information.  The

{ "normally"?  what are the exceptions?}


> client then sends the EHLO command.  Since the client cannot know whether
> the server supports UTF8SMTPbis until after it receives the response from
> EHLO, the client must send only ASCII (LDH label [RFC5890] or A-label)
> domains in the EHLO command and that, if the server provides domain names in
> the EHLO response, they must be in the form of LDH labels or A-labels.
>
> 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

      may -> might

or

      may -> can

{ normative vocabulary can only be used for normative statements.  please do a 
global search and replace, where normative vocabulary are used in non-normative 
sentences.}


> 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.

{ This last sentence sounds normative and I believe it should be. So... }

      it is strongly advised that either all or none of them support
      ->
      all or none of them SHOULD support


> Otherwise, surprising rejections
> can happen during temporary failures, which users might perceive as a serious

{ Probably not just temporary failures.  Having services that are meant to be 
redundant with each other actually provide different semantic behavior is just 
plain dangerous. It is essentially guaranteed that they will cause problems.}


> 3.6.3.  Trace Information
>
>    When an SMTP server receives a message for delivery or further
>    processing, RFC 5321 requires that it MUST insert trace ("time stamp"
>    or "Received") information at the beginning of the message content.
>    For the trace information, this memo updates the time stamp line and
>    the return path line [RFC5321] formally defined as follows:

{ Again, don't repeat normative language.  I suggest simply deleting the first 
sentence. }


> [RFC5321] formally defined as follows:
>
> uReturn-path-line = "Return-Path:" FWS uReverse-path <CRLF> ; Replaces
> Return-path-line in Section 4.4 of RFC 5321

{ On reflection, I think the "u" rule-naming convention is problematic.  If the 
current specification is replacing a rule previously defined elsewhere, it needs 
to use the same rulename.  This is simpler and clearer.  Otherwise, all future 
references to the rule need to use the new name.

Rather, where the draft is replacing a rule from another specification, the rule 
definition includes a comment that cites where the original rule is from; that 
should be sufficient. }


> uReverse-path = uPath / "<>" ; Replace Reverse-path in RFC 5321, section
> 4.1.2
>
> uPath = "<" [ A-d-l ":" ] uMailbox ">" ; Replace Path in RFC 5321, section
> 4.1.2 ; uMailbox is defined in section 3.3 of this document
>
> A-d-l = <See section 4.1.2 of RFC 5321>

{ Small improvement:  Where a rule is defined elsewhere, I suggest having the 
descriptive text in the rule say <Defined in...> rather than <See...>. }


> 3.6.4.  UTF-8 Strings in Replies
>
> 3.6.4.1.  RCPT Commands
>
> If an SMTP client follows this specification and sends any RCPT commands
> containing non-ASCII addresses, the SMTP server is permitted to use UTF-8
> characters in the email address associated with 251 and 551 response codes,
> and the client MUST be able to accept and process them.

{ I assume that "follows this specification" means that the UTF8SMTPbis option 
is in force.  If so, then say that, because it is simpler and more precise. But, 
then, it does require declaring /use/ of the option...

However the meaning of the text here is odd.  It implies that the server is not 
permitted to use UTF-8 unless it has already received UTF-8, even though the 
option is in force.  I suspect that that is not the specification that is 
intended.  Or, at least, I hope it is not.

If it actually /is/ what is intended, it means that the enhanced environment is 
going to have all sorts of /additional/ conditional code, to check on whether a 
specific context in the state machine is allowed to act in one way or another.

The simple and more reasonable model is that when the extension is in force, 
UTF-8 is allowed.  Period.  So... }

      If an SMTP session is using this extension, then the server is permitted 
to use UTF-8 characters in the email address associated with 251 and 551 
reply-codes, and the client MUST be able to accept and process them.

{ I chose "SMTP session" to avoid the more complex discussion of the 
client/server 'negotiation' about using the extension.  So, here it is either in 
force or it isn't and if it is in force, it is for client AND server. }


>      If a given RCPT
> command does not include a non-ASCII envelope address, the server MUST NOT
> return a 251 or 551 response containing a non-ASCII mailbox.  Instead, it
> MUST transform such responses into 250 or 550 responses that do not contain
> non-ASCII addresses.

{  See above.  I very strongly disagree with having the complexity this kind of 
conditional requirement creates.  Or else there is a basic issue involved here 
that the document does not discuss but needs to, to justify the complexity. }


> 3.6.4.2.  VRFY and EXPN Commands and the UTF-8REPLY Parameter
>
> If the VRFY and EXPN commands are transmitted with the optional parameter
> "UTF-8REPLY", it indicates the client can accept UTF-8 strings in replies to
> those commands.  This allows the server to use UTF-8 strings in mailbox

{ Is this extension trying to to say that a client might support UTF8SMTPbis but 
not be able to access UTF-8 replies???  Under what circumstance is this 
reasonable? }


> names and full names that occur in replies without concern that the client
> might be confused by them.  An SMTP client that conforms to this

{ What does it mean to be "confused" by them?  Because the extension is in 
force, we know that the client supports UTF-8. }


> specification MUST accept and correctly process replies from the VRFY and
> EXPN commands that contain UTF-8 strings.  However, the SMTP server MUST NOT
> use UTF-8 strings in replies if the SMTP client does not specifically allow
> such replies by transmitting this parameter.  Most replies do not require

{ Why is this constraint required? }


> that a mailbox name be included in the returned text, and therefore UTF-8 is
> not needed in them. Some replies, notably those resulting from successful
> execution of the VRFY and EXPN commands, do include the mailbox, making the
> provisions of this section important.
>
> VERIFY (VRFY) and EXPAND (EXPN) command syntaxes are changed to:
>
> vrfy = "VRFY" SP ( uLocal-part / uMailbox ) [ SP "UTF-8REPLY" ] CRLF ;
> uLocal-part and uMailbox are defined in ; Section 3.3 of this document.
>
> expn = "EXPN" SP ( uLocal-part / uMailbox ) [ SP "UTF-8REPLY" ] CRLF ;
> uLocal-part and uMailbox are defined in ; Section 3.3 of this document.

{ Note that these rules only specify UTF-8 support, without any contingency on 
use.  That is, they do not cover the variability that is described in the prose, 
and that disparity from the prose specification is an example of the complexity 
created by having the use of UTF-8 in replies be so contingent on the actual 
data sent by the client. }


> If a normal success response (i.e., 250) is returned, the response MAY
> include the full name of the user and MUST include the mailbox of the user.
> It MUST be in either of the following forms:
>
> User Name <uMailbox> ; uMailbox is defined in Section 3.3 of this document.
> ; User Name can contain non-ASCII characters.
>
> uMailbox ; uMailbox is defined in Section 3.3 of this document.

{ "User Name" needs to be specified as an abnf rule.  It isn't.

This appears to be intended to invoke the RFC 5322 definition of <mailbox> 
rather than the RFC 5321 definition.  In any event, it is creating a semantic 
change to the response, from RFC 5321, beyond merely allowing UTF-8 characters. }


> 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 "X.6.8" [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".

{ "the mailbox name"?  which string is that? }


> If the SMTP client does not support the UTF8SMTPbisbis extension, but receives
> a UTF-8 string in a reply, it may not be able to properly report the reply

If a UTF-8 string is sent in a reply, when this extension is not in force, then 
it is a protocol violation.  Period.


> [RFC4952bis] Klensin, J. and Y. Ko, "Overview and Framework for
> Internationalized Email", RFC 4952, July 2010.

      RFC4951
      ->
      draft-ietf-eai-frmwrk-4952bis

{ It is not now, and never will be, RFC 4952;  And RFC4952bis is currently dated 
September 2010. When it is an RFC, it will have a new number.

Also, Internet Drafts, including -bis documents, usually follow a different 
citation labeling convention, such as I-D.rfc4952bis, to make clear that they 
are an I-D and not an RFC. }




[1]  draft-ietf-eai-frmwrk-4952bis-10

[2]  draft-ietf-eai-rfc5335bis-03


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss

From Shawn.Steele@microsoft.com  Wed Dec 22 13:41:38 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 AEA9F3A68BE for <ima@core3.amsl.com>; Wed, 22 Dec 2010 13:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.801
X-Spam-Level: 
X-Spam-Status: No, score=-9.801 tagged_above=-999 required=5 tests=[AWL=-0.474, BAYES_00=-2.599, FRT_BEFORE=1.272, 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 MOoB3F4E2c5a for <ima@core3.amsl.com>; Wed, 22 Dec 2010 13:41:36 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 10B853A6888 for <ima@ietf.org>; Wed, 22 Dec 2010 13:41:36 -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; Wed, 22 Dec 2010 13:43:35 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0255.003; Wed, 22 Dec 2010 13:43:34 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>, "dhc@dcrocker.net" <dhc@dcrocker.net>
Thread-Topic: draft review of: draft-ietf-eai-rfc5336bis-07.txt
Thread-Index: AcuiGRTYB9OLItJ0TAi53YY1xoI7vQ==
Date: Wed, 22 Dec 2010 21:43:34 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B3E917@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.70]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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: Wed, 22 Dec 2010 21:41:38 -0000

Some comments:

> Date: Wed, 22 Dec 2010 10:04:48 -0800
> From: Dave CROCKER <dhc@dcrocker.net>

>     5.  The SMTP extension needs to remove all restrictions it imposes on=
 MIME=20
> content-type.  A major reason that MIME was successful was that it was=20
> transparent to the transfer infrastructure.  The current SMTP extension=20
> specification changes this model, which actually increases the barrier to=
=20
> adoption of Unicode in email.  It needs to be easy for two MUAs that supp=
ort=20
> Unicode in the email header to exchange mail even when the infrastructure=
 does=20
> not support UTF-8.

I disagree:)  If a mail agent/client/whatever can handle UTF-8 in the heade=
r, then those should certainly be able to handle UTF-8 in the body of the m=
ail.  Yes, MIME has worked because it tunnels other encodings through mecha=
nisms that don't understand those encodings, however any EAI aware client/s=
erver/whatever would necessarily be able to understand UTF-8, reducing the =
need for other content.

In fact, MIME isn't entirely successful.  It works a large part of the time=
, but there are differences in encoding behaviors between vendors that crea=
te very troublesome edge cases and variations that can be difficult to work=
 around.  I've often encountered customers with encoding related problems. =
 A strong preference for UTF-8 would resolve a large number of interoperabi=
lity issues.

> However note that <encoded-word> and <A-label>=20
> already accomplish this in a way that is transparent to the existing emai=
l=20
> infrastructure; only the end-systems need to understand it.

Actually a-labels are causing serious pains for infrastructure and applicat=
ions.  IDN aware applications must be aware of both forms of their name, an=
d a-labels are "leaking" into all sorts of unexpected places.  Even at a si=
mple form, merely encoding Unicode in an a-label to query a server is insuf=
ficient for basic web content.  In addition, the http request has to be enc=
oded with a punycode form, and the server needs to be made aware of it's pu=
nycode name.  And then there's the mixing of IRIs and URIs, so applications=
 in many layers need to recognize both the punycode and unicode forms.  Thi=
s is amazingly painful across the entire ecosystem. =20

> The second goal is to support Unicode in the more "native" form of UTF-8.=
=20
> (The quotation marks are because UTF-8 is not native Unicode, either; it =
is
> a highly encoded form of Unicode...)

That is serious quibbling.  By that definition, there is no native form of =
Unicode.  The Unicode Standard clearly provides for UTF-8, UTF-16, and UTF-=
32 variations, and makes no preference for which representation is preferre=
d.  UTF-8 is obviously far more compatible with SMTP than either UTF-16 or =
UTF-32.

> I strongly suggest=20
> saying "Unicode" when intending to refer to the richer set of characters =
that=20
> are the goal of this work, and "UTF-8" when referring to the particular b=
inary=20
> encoding of Unicode that is the focus of the SMTP extension work.

That makes sense.

> Non-UTF-8 Unicode support -- Can a message support Unicode without=20
> UTF-8?  The existence of <encoded-word> and <A-label> constructs makes cl=
ear=20
> that the answer is yes.  Hence, it should be possible to support Unicode=
=20
> messages, without this SMTP extension. =20

This was debated to great extent, primarily as a "fallback" option.  The WG=
 overwhelmingly thinks that <a-labels> are a terrible way to work around th=
ese problems:
  * Encoded forms are inherintly non-user friendly
  * Encoded forms "leak".
  * It is impossible to create an EAI aware mail client or server without u=
pdating that client or server, even if that update were "merely" to handle =
the new use of these encodings.  Obviously if an update is required, then U=
TF-8 could be that update.
  * Implementing IDN has shown how very complicated and annoying leaking en=
coded forms can be.  The biggest problem is that the encoded form "leaks" i=
nto unicode-aware contexts, and suddenly software that wasn't broken by the=
 new standard is broken by needing to decode these things.
  * Clearly the encoded-words were interesting when trying to shove stuff t=
hrough 7 bit pipes and Unicode was in it's infancy, but that is no longer t=
he case.  Most of the infrastructure supports 8 bit mail, so there is very =
little benefit to making the standard this complex.

> Instead I recommend the client to=20
> signal explicitly when UTF8-encoded addresses are present, such as a=20
> <Mail-parameters> option (<esmtp-param>) to the MAIL command.

In my opinion that is more complex.  Currently my client/server have to use=
 an encoding, like ASCII (though some use other encodings).  The UTF8SMTP h=
andshaking clearly indicates that we're talking in UTF-8.  No further hands=
haking is therefore required.

The only cases where the standard requires anything more than the initial h=
andshaking is when that handshaking failed.

>>         Once isolated by this parsing process, the local part MUST be
>>    treated as opaque unless the SMTP server is the final delivery Mail
>>    Transfer Agent (MTA).

> { The statement about handling of <local-part> is redundant with the base=
 RFC=20
> 5321 specification.  The statement, here, should be that the handling of=
=20
> <local-part> is unchanged from the base specification.  Again, it should =
not=20
> repeat the normative language, unless it is changing it.  If it is changi=
ng it,=20
> the change needs to be essential for support of internationalized address=
es. }

The intent here was because some people wanted to explicitly forbid encodin=
g or decoding (specifically punycoding) the local part.  I'm happy if all o=
f the stuff because of that is omitted, defaulting as you say, to the base =
RFC 5321 specification.

(Full disclosure: I am one of those who wouldn't mind allowing punycode fal=
lback, as a very worst case last resort.  IMO that should only be fore tunn=
eling through non-EAI aware systems though and certainly not a first class =
way of "solving" EAI.).

>> It MAY send a UTF-8 header
>> [RFC5335bis] (which may also include mailbox names in UTF-8).  It MAY
>> transmit the domain parts of mailbox names within SMTP commands or the
>> message header as A-labels or U-labels

> { I believe that the use of "MAY" is not correct. This would mean that th=
e=20
> receiver needs a means of distinguishing whether the data are UTF-8 or no=
t.}

I believe this is trying to say that an ASCII-only message would also work.=
  Since ASCII is a subset of UTF-8, the encoding doesn't really have to be =
detected.  In other words:  Just because we exchanged "UTF8SMTP" that doesn=
't mean that you are required to include characters >=3D U+0080.  IMO this =
could probably be change to be MUST?

The intent is very much not to allow switching to non-UTF-8 modes, the hand=
shaking already said that this session is in UTF-8.  (Note that in practice=
 a non-UTF8SMTP session isn't necessarily ASCII.  Existing implementations =
often use whatever the system code page is.  UTF8SMTP allows a session to a=
ctually declare a specific UTF-8 code page, whereas existing implementation=
s just have to get lucky, unless they use MIME).

>> All labels in domain parts of mailbox names which are IDN
>>    forms of A-labels or U-labels MUST be valid.

> { This is strange.  Either it is repeating a normative requirement from S=
MTP or=20
> it is expanding SMTP to require special validation for IDN forms of domai=
n names=20
> that is not present for ASCII forms.  Neither interpretation seems like t=
he=20
> right thing to be doing here. Such a modification to SMTP seems out of sc=
ope.

Seems redundant to me too.  I think this probably comes from the problem th=
at a-labels and u-labels in IDN "leak".  So we can't be sure which one they=
 are.  This clarifies that EAI has to be aware of IDN and make sure it does=
 the right thing?

>>The presence of the UTF8SMTPbis
>>    extension does not change the requirement of RFC 5321 that servers
>>    relaying mail MUST NOT attempt to parse, evaluate, or transform the
>>    local part in any way.

> { This sentence replicates normative language from a different specificat=
ion.=20
> This is a very bad thing to do, in case the original specification change=
s its=20
> language.  I suggest: }

Again, this is a co-chair not wanting me to encode local parts as a-labels =
to tunnel through non-UTF8SMTP connections, even in a very-worst-case-last-=
resort sort of way :)

>> If the UTF8SMTPbis SMTP extension is not offered by the server, the SMTP
>> client MUST NOT transmit an internationalized address and MUST NOT trans=
mit

>{ This appears to prohibit the sending of internationalized addresses that=
 are=20
>encoded in ASCII, rather than in UTF-8.=20

There are no "internationalized addresses that are in ASCII".  There "are" =
some that use ACE encoding, (but I wouldn't call that strictly ASCII).  Als=
o current practice can send addresses in nearly any code pages, which I've =
seen in CJK locales. This would require those servers conform to UTF-8, sin=
ce the current practice just causes a mess when it escapes the local system=
.

>  If the concern is sending UTF-8, then that's the language that needs to =
be=20
> used.

I believe the main thing is that if I try to connect, and the server doesn'=
t offer UTF8SMTP, then I shouldn't blindly go ahead and send my UTF-8 heade=
r anyway.

>  Messages with ASCII-encoding of internationalized addresses need to be=20
> permitted to be sent, without first requiring infrastructure support. }

There is no standard for ascii-encoded internationalized addresses.  (Other=
 than domains).

>> There is no ESMTP parameter to assert that a message is an international=
ized
>> message.  An SMTP server that requires accurate knowledge of whether a
>> message is internationalized is required to parse all message header fie=
lds
>> and MIME header fields [RFC2045] and [RFC2047] in the message body.

> { This is confusing.  There is a rule against sending an internationalize=
d=20
> message, unless UTF8SMTPbis is in force, but there is no requirement that=
 the=20
> server be told explicitly when a message is internationalized???

It's unnecessary, since the other option would be ASCII, which is, in effec=
t, UTF-8, so the additional handshaking isn't required.  I'm confused what =
this would gain us.  A "normal" message is, effectively, intenrationalized,=
 because it would still work with (or without) UTF8SMTP.

>> If an SMTP client follows this specification and sends any RCPT commands
>> containing non-ASCII addresses, the SMTP server is permitted to use UTF-=
8
>> characters in the email address associated with 251 and 551 response cod=
es,
>> and the client MUST be able to accept and process them.

> { I assume that "follows this specification" means that the UTF8SMTPbis o=
ption=20
> is in force.  If so, then say that, because it is simpler and more precis=
e. But,=20
> then, it does require declaring /use/ of the option...

There are two cases:  Either it's UTF8SMTP from the handshaking, so then it=
s this specification, or there was no UTF8SMTP handshaking, so then this RF=
C doesn't apply.  So if UTF8SMTP was offered, then it is being used. =20

Since UTF8SMTP is offered by the server, you can tell if the client is usin=
g it because it sent characters > U+007F.  Since the client might not recog=
nize UTF8SMTP, then whether the client supports UTF8 might not be clear, ho=
wever this section says that if the client sent UTF-8, then the server may =
respond similarly.

>> 3.6.4.2.  VRFY and EXPN Commands and the UTF-8REPLY Parameter
>>
>> If the VRFY and EXPN commands are transmitted with the optional paramete=
r
>> "UTF-8REPLY", it indicates the client can accept UTF-8 strings in replie=
s to
>> those commands.  This allows the server to use UTF-8 strings in mailbox

> { Is this extension trying to to say that a client might support UTF8SMTP=
bis but=20
> not be able to access UTF-8 replies???  Under what circumstance is this=20
> reasonable? }

The server normally has no clue if the client supports UTF-8 until it gets =
a UTF-8 address from the client.  However these commands could cause UTF-8 =
replies to an ASCII query.  The option explicitly states that the client is=
 prepared to receive that UTF-8 reply.

- Shawn

Senior Software Design Engineer
Windows Globalization
Microsoft


From Shawn.Steele@microsoft.com  Wed Dec 22 13:49:31 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 38AB23A68BE for <ima@core3.amsl.com>; Wed, 22 Dec 2010 13:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.66
X-Spam-Level: 
X-Spam-Status: No, score=-9.66 tagged_above=-999 required=5 tests=[AWL=-0.561,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_42=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 pcKOF5BXvVZX for <ima@core3.amsl.com>; Wed, 22 Dec 2010 13:49:29 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id A2B0E3A6888 for <ima@ietf.org>; Wed, 22 Dec 2010 13:49:29 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 22 Dec 2010 13:51:28 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0255.003; Wed, 22 Dec 2010 13:51:28 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>, "John C Klensin (klensin@jck.com)" <klensin@jck.com>, =?iso-8859-1?B?Ik1hcnRpbiBKLiBE/HJzdCIgKGR1ZXJzdEBpdC5hb3lhbWEuYWMuanAp?= <duerst@it.aoyama.ac.jp>
Thread-Topic: [EAI] Co-chair's comments on state of the documents and the WG
Thread-Index: AcuiGL8xWq6z3v6TQfiB0uSJbI5yxg==
Date: Wed, 22 Dec 2010 21:51:28 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B3E9E6@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.70]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] Co-chair's comments on state of the documents and the WG
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: Wed, 22 Dec 2010 21:49:31 -0000

I concede to not being as well-versed about some of the details of email, h=
owever I've made sure that Exchange, Office, and other interested people ha=
ve reviewed the documents.  We have no substantiative problems with the doc=
uments, and most of the comments (until Dave's) seem centered around editin=
g and fixing errors in the behaviors, not changing the actual standard.

So: it's unclear what more I can do to speed up the process or get the requ=
ired review.  Exchange & Office certainly know a lot about mail.  Do we nee=
d someone from Google or Yahoo or ??? to chime in?

-Shawn

------------------------------
Date: Wed, 22 Dec 2010 17:19:01 +0900
From: "Martin J. D?rst" <duerst@it.aoyama.ac.jp>
Subject: Re: [EAI] Co-chair's comments on state of the documents and
	the WG
To: John C Klensin <klensin@jck.com>
Cc: IETF EAI WG <ima@ietf.org>
Message-ID: <4D11B475.5080100@it.aoyama.ac.jp>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Hello John,

I want to make sure that at least somebody replies to your mail.

I don't think at all that I'm qualifying with respect to email=20
infrastructure implementation and operation experience; I'm just mostly=20
an email user. I can help with internationalization issues, but my=20
understanding is that that's not necessarily what's most needed now. I=20
may be able to go through some comments and check whether they have been=20
applied consistently (essentially a shepherd role?). Getting pointers to=20
drafts and mails with comments would help.


On a meta-level, I'm a bit surprised by your comment that we have to=20
finish within Alex'es term. I understand that it would be much more=20
efficient if Alex could handle our drafts rather than a new AD, and I=20
understand that each AD has their preferences for what work they want to=20
have happening, and that on occasion very inactive WGs have been shut=20
down, but what you wrote below almost sounded like the new AD would just=20
shut the WG down without asking anybody, so I hope I'm misunderstanding.

Also, while I think that all your observations were to the point, I=20
think a shorter mail, with a subject more like "Wanted: Reviewers for=20
XYZ" would have a bigger chance to be read by the relevant people. Also,=20
maybe you remember (if only faintly) some of the hands that went up in=20
Maastricht or in Beijing, and might be able to contact them directly. On=20
average, that gives a better result than anonymous appeals.

Regards,   Martin.


On 2010/12/22 12:59, John C Klensin wrote:
> (writing as co-chair)
>
> Hi.
>
> Folks, I've been watching progress in this WG between some
> weeks before the Beijing IETF and the present.  I think we are
> in serious trouble and want to share that opinion with the WG
> participants.
>
> For a WG to function and make a serious claim to represent IETF
> technical consensus, there has to be significant participation,
> review of documents, etc.  And that has to come from more than
> the group of people writing documents.  In practice, we
> sometimes relax that requirement a bit.  In particular, there
> have been WGs that have been considered successful even though
> there have really been only about a half-dozen really active
> participants.  But that is just not sensible when the WG is
> working on protocols that pose very significant risks to the
> installed base if we overlook important cases.  As we have
> noticed when we have sorted out the various implications of
> extensions on legacy email implementations the EAI effort poses
> just exactly that risk.  The extensive syntax discussion in
> Beijing is an important example of how careful we need to be
> about our decisions.
>
> Our situation is made somewhat more difficult by the
> observation that only a relatively small fraction of the
> participants in the WG have significant personal experience
> with large-scale Internet mail operations or a deep familiarity
> with the existing Internet mail protocols.  As we have seen
> with the reviews Alexey requested from the Apps Area review
> team, when such reviews from the IETF's email expert community
> come at all, they tend to come from outside the WG and tend to
> find things that the WG did not.  That is disquieting to say
> the least.
>
> I note that we got a fairly large number of promises in both
> Beijing and Maastricht to carefully review and comment on
> documents.  Outside the author group and a few others, either
> people did not do those reviews or they lack the skill or
> background to find things that have been discovered by Alexey,
> myself, or others outside the normal group of WG participants.
>
> Clearly, there is a large community, especially among users of
> east Asian languages, who very much want internationalized
> email addresses and headers.  There are other communities with
> similar needs but the they are not well-represented in the WG
> (or have been strangely silent) so, if they have requirements
> that are different from those we have seen already, we are at
> risk of missing them or getting things wrong.  If the IETF
> cannot or will not produce usable specifications, there is
> reason to believe that communities will go off in their own
> directions, resulting in huge interoperability problem in the
> future.
>
> One way of looking at the WG's problem is that there is a
> community of people who are deeply interested in email
> internationalization but who lack either extensive email
> experience or significant experience in writing clear and
> precise IETF specifications (whether the problem is with
> technical English, ABNF, or the way the existing email specs
> are written).  There is also a community who are expert in
> Internet email and the writing of the relevant types of
> specifications, but few of them have been actively involved in
> i18n work and fewer still have time and "day job" support to
> devote to this work.  The two communities are largely disjoint,
> but both are needed to complete the EAI work with great
> confidence about the results being correct and free of
> dangerous side-effects.
>
> In discussions with Alexey, it has become clear that we have
> hard practical deadlines associated with the end of his term as
> AD.  The core documents have to be in his hands and out for
> IETF Last Call within the next several weeks or it seems
> unlikely that the WG will be able finish its work... ever.
>
> Having read the reviews from the last two weeks or so, I think
> it ought to be possible to proceed as follows _if_ WG
> participants are really interested enough in finishing this
> work to put effort into it:
>
> (1) We get some reviewers from inside the WG but outside the
> author group to go through the comments and verify that they
> have been properly disposed of, e.g., that appropriate changes
> have been made to the documents or we have explained why not to
> the satisfaction of the reviewers and/or significant consensus
> of WG participants.
>
> (2) We get ths three base documents into Alexey's hands with a
> request for IETF Last Call really soon -- certainly before
> January 15 and ideally early next week.  That means the
> checking described in (1) needs to occur nearly immediately.
> Bluntly, silence from those of you have have been silent since
> July will have to be taken as indifference on your part to
> whether the documents are completed and the WG continues.
>
> (3) We get some serious suggestions from the WG on how we are
> going to move forward with the two additional groups of
> documents -- (i) POP/ IMAP/ common downgrading protocol
> specifications and (ii) all of the "advice" stuff.  If we can
> find adequate review for the protocol specs, we can presumably
> proceed with them on the same basis that we are using to handle
> the base documents.  I am, however, concerned that we may not
> be able to find that quality of review unless more people
> within the WG start doing serious work.  For the "advice"
> documents, unless we can get a lot of review and input from
> people who are much more experienced with Internet email than
> the WG average --people who could write similar documents for
> non-EAI email and have it be credible-- I suggest that we just
> drop the documents from the WG agenda and handle them as
> individual submissions.  I want to stress that I'm not assuming
> there is anything wrong with the drafts -- the issue is only
> about getting adequate review to convince ourselves and the
> IETF community that those documents really do represent
> community consensus.  Put differently, the problem is not
> getting the I-Ds written; it is having them reflect sufficient
> experience (not just opinions) to be accepted within the
> broader Internet email environment.  Doing so requires noting
> that the Internet email environment has survived well for
> nearly 30 years without such documents.
>
> If people disagree with this rather bleak analysis -- and I
> hope they do -- suggesting areas where I am wrong would be a
> useful first step in convincing us that the WG really does have
> the energy to finish all of the work listed in the charter
> (including the optional tasks).
>
>     best regards and best wishes for anything you may be
>     celebrating at this time of year,
>      john
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>
>

--=20
#-# 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  Wed Dec 22 15:34: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 85A183A6943 for <ima@core3.amsl.com>; Wed, 22 Dec 2010 15:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.07
X-Spam-Level: 
X-Spam-Status: No, score=-2.07 tagged_above=-999 required=5 tests=[AWL=-0.371,  BAYES_00=-2.599, J_CHICKENPOX_42=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 rYYhMUTCVkAM for <ima@core3.amsl.com>; Wed, 22 Dec 2010 15:34:16 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 2A0BA3A6A6F for <ima@ietf.org>; Wed, 22 Dec 2010 15:34:16 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PVYEA-000Fcl-3p; Wed, 22 Dec 2010 18:36:14 -0500
Date: Wed, 22 Dec 2010 18:36:13 -0500
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: <29EABD21FDAD754C86AA2628@PST.JCK.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
Cc: IETF EAI WG <ima@ietf.org>
Subject: Re: [EAI] Co-chair's comments on state of the documents and the WG
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: Wed, 22 Dec 2010 23:34:17 -0000

--On Wednesday, December 22, 2010 17:19 +0900 "\"Martin J.
D=C3=BCrst\"" <duerst@it.aoyama.ac.jp> wrote:

> Hello John,
>=20
> I want to make sure that at least somebody replies to your
> mail.

Thanks.

> I don't think at all that I'm qualifying with respect to email
> infrastructure implementation and operation experience; I'm
> just mostly an email user. I can help with
> internationalization issues, but my understanding is that
> that's not necessarily what's most needed now. I may be able
> to go through some comments and check whether they have been
> applied consistently (essentially a shepherd role?). Getting
> pointers to drafts and mails with comments would help.

In addition to checks for consistency and compatibility with the
base email specs and email operations, one of the things I
personally think we most need is careful reading for clarity and
comprehensibility of the text.  I found a lot of problems in
that area in my pre-Beijing reviews, but it will take additional
sets of eyes to verify  that those issues have been adequately
addressed and that I found everything (which I am quite
confident that I did not).

> On a meta-level, I'm a bit surprised by your comment that we
> have to finish within Alex'es term. I understand that it would
> be much more efficient if Alex could handle our drafts rather
> than a new AD, and I understand that each AD has their
> preferences for what work they want to have happening, and
> that on occasion very inactive WGs have been shut down, but
> what you wrote below almost sounded like the new AD would just
> shut the WG down without asking anybody, so I hope I'm
> misunderstanding.

As you have suspected, it is a little more complicated than
"Alexey's term".  The [re-]chartering of the WG, my agreement
(and presumably Joseph's) to take over the co-chair, possibly
commitments from some of the authors/editors, and the charter
itself were based, IMO, on three assumptions:

	(i) That we had basic agreement on the technology, with
	a solid footing in the experimental documents and
	implementations that had already been completed and
	tested.
	
	(ii) That there was significant agreement, and some
	specific product drivers, that made "get it done quickly
	and on a very aggressive schedule" a critical goal that
	was important enough to drive WG work and decisions.
	
	(iii) That there was sufficient engagement within the
	WG, and specifically signup for document authoring,
	review, editing, to make (ii) realistic.

Now, from that point of view, slippages to the schedule defined
in the charter benchmarks constitute a much more serious
situation than would be the case if the WG were operating with
more leisure.  We are now three months behind schedule on
headers (5335bis), SMTP (5336bis), and DSN (5337bis).
Realistically, it will be January before those actually go to
the IESG, so make that "four months behind".  We are now a month
behind on submission of IMAP/POP (5378bis, 5721bis, and
draft-ietf-eai-popimap-downgrade) and, since there has been
substantially no WG discussion of any of them other than among
authors and at the Beijing meeting, I assume a more realistic
estimate is 2-3 months behind even if we abruptly see a lot of
comments and participation.

We haven't even started talking about submission servers and a
decision is due this month.  And the various "advice" documents
are even further behind.  There might be time between now and
April for  the mailing list work and anything we might do about
Mailto to catch up, but not unless there is serious WG
engagement... and soon.

While there is no direct link between that situation and
Alexey's stepping down, the situation brings us closer to the
possible point at which someone goes to him and says "this isn't
working: find new editors and leadership and/or considering
rechartering with a different model or closing the WG entirely".
That someone could even be me.   And, if we are going to have
that discussion, I want to have it with Alexey before he steps
down, not someone we have to read in as part of the process.

> Also, while I think that all your observations were to the
> point, I think a shorter mail, with a subject more like
> "Wanted: Reviewers for XYZ" would have a bigger chance to be
> read by the relevant people. Also, maybe you remember (if only
> faintly) some of the hands that went up in Maastricht or in
> Beijing, and might be able to contact them directly. On
> average, that gives a better result than anonymous appeals.

I remember.  For the Maastricht meeting, we even have pictures
(in the minutes) of those who raised their hands.  More
important, if the purpose had been to get more specific reviews,
I hope I would have had the sense to write that note.  But it
wasn't.  The intent of this note was to outline the general
status of things to WG participants and to try to make it clear
that, unless there is a lot more engagement --in reviews, but
also in discussions and sorting out specific issues, and across
the WG's task list now just in specific subtopics in which
individuals are interested-- the WG is in serious trouble and
probably on course for shutting down without a lot of the
current tasks being completed.

best,
    john




From dhc2@dcrocker.net  Wed Dec 22 16:40:11 2010
Return-Path: <dhc2@dcrocker.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 2D3363A691A for <ima@core3.amsl.com>; Wed, 22 Dec 2010 16:40:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5UMTIxi2y2pp for <ima@core3.amsl.com>; Wed, 22 Dec 2010 16:40:10 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 014E43A6B00 for <ima@ietf.org>; Wed, 22 Dec 2010 16:40:09 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBN0g3T3022492 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2010 16:42:09 -0800
Message-ID: <4D129ADC.7070105@dcrocker.net>
Date: Wed, 22 Dec 2010 16:42:04 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Shawn Steele <Shawn.Steele@microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B3E917@TK5EX14MBXC137.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B3E917@TK5EX14MBXC137.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Dec 2010 16:42:09 -0800 (PST)
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 23 Dec 2010 00:40:11 -0000

On 12/22/2010 1:43 PM, Shawn Steele wrote:
> The UTF8SMTP handshaking clearly indicates that we're talking in UTF-8.  No
> further handshaking is therefore required.


Please provide some clarification:

      Where does the text define an explicit protocol handshake, so that both 
sides know that the session is now using UTF-8?

I could not find it (except for VRFY and EXPN...)

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From Claudio.Allocchio@garr.it  Wed Dec 22 09:22:33 2010
Return-Path: <Claudio.Allocchio@garr.it>
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 314063A6B93; Wed, 22 Dec 2010 09:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  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 qDWh19coFosJ; Wed, 22 Dec 2010 09:22:30 -0800 (PST)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id C03B53A6B91; Wed, 22 Dec 2010 09:22:29 -0800 (PST)
Received: from mac-allocchio3.elettra.trieste.it (mac-allocchio3.elettra.trieste.it [140.105.2.18]) (authenticated bits=0) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id oBMHOHLc001829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2010 18:24:17 +0100 (CET)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 cyrus.dir.garr.it oBMHOHLc001829
DomainKey-Signature: a=rsa-sha1; s=mail; d=garr.it; c=simple; q=dns; b=roKPdmhQpHF81dShcG6jug9nCIiG1uJHA4qDeE/yLidzpQvZRcsXZLAuj83J1P/iE /xobSXJXNu1TnpF1LTnhB8U6GD6anCxXBZWa6h6+c9D0CgtHFkb6KOWd5DptoQ87NTy xL1MSfD127NKaQOdDrjmhfNaYeWd436MxOvJ04w=
Date: Wed, 22 Dec 2010 18:24:11 +0100 (CET)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.elettra.trieste.it
To: apps-discuss@ietf.org, ima@ietf.org, draft-ietf-eai-rfc5336bis@tools.ietf.org
Message-ID: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Wed, 22 Dec 2010 16:51:37 -0800
Cc: Alexey.Melnikov@isode.com, SM <sm+ietf@elandsys.com>
Subject: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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: Wed, 22 Dec 2010 17:22:33 -0000

I have been selected as the Applications Area Review Team reviewer for this
draft (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).

Please resolve these comments along with any other Last Call comments you
may receive. Please wait for direction from your document shepherd or AD
before posting a new version of the draft.

Document: draft-ietf-eai-rfc5336bis
Reviewer: Claudio Allocchio (GARR, Italian Research and Academic Network)
Review Date: 2010-12-22
IETF Last Call Date:  N/A
IESG Telechat Date:  N/A

Summary:

The document specifies how to apply internationalization to some SMTP
elements, and to some Header elements which depends from the SMTP elements.
However there seem to be a discrepancy from what the abstract states, and
what is elaborated into the document details: the document also deals with
quite a number of elements which involve bodyparts, and affect the whole
email legacy system, and beyond, such as logs, traces, and wherever email
addresses are used (certificates, etc.). This seems thus to go beyond what
the summary states, even this fact is not explicitly discussed. It is
unclear thus if this "update" of RFC5321 and RFC5322 is only limited in
scope or not. My reading of the document say it goes beyond, and implicitly
affects also what is being transported into the email system. This is thus a
serious issue to be solved before the document can go to the Standard Track.
Another big issue is about blending the boundaries of servers in the
transport system (MTAs), clients (UAs) and their roles, when the document
specify that servers shall use guessing techniques from looking into
bodyparts to understand if what they're transporting is internationalized
according to this specification or not. This is IMHO a basic violation of
the role distiction in the legacy email system, and affects the MIME model
al well.

The document quite often repeats rules from other specifications, AND
re-describes these rules. This is dangerous (it makes very difficult to keep
aligned documents, and will lead to different interpretations) and not
needed.

The full specification probably needs a serious "english language" revision,
because the language issues which I specified in "Minor Issues" seems to be
a non neglegible number. I'll try to identify as many as possible and
suggest changes.

Major Issues:

This specification updates a number of SMTP and Headers fields from RFC5321
and RFC5322. However these fields are also used in Gatewaying to other email
systems, which are still existing. Section 3.7 in RFC5321 describes specific
cases. However this memo provides no clue on possible effect that
internationalized fields can have in case gatewaying occurs. Gatewaying
functions strongly rely on these values, and the introduction of these
modification should describe this scenario, too. I suggest to include a
specific section about these issues, and suggest at least a number of
possible actions which Gateways can take to survive this change.

The EAI WG charter states that in handling email message we shall be
"consistent with the long-term view that email with invalid addresses or
syntax should be rejected, rather than fixed up in transit between
submission servers and delivery servers.". However a number of sections in
the specification seem to contradict this, where they suggest actions, by
exammining message elements (in the SMTP and in the Headers and in the
Bodyparts) in order to try to deliver anyhow. This is a subtle line between
maximising the service chance to deliver, and "fixing" things during the
transaction, and it can encourage implementors to do many of these acions,
instead of stiching to the idea "not supported --> non delivery".

Major Issues by sections.

Abstract:

" This document specifies an SMTP extension for transport and delivery
    of email messages with internationalized email addresses or header
    information."

"internationalized" is not defined here in details. Sections 1 and 1.2 try 
to do this, but the language is not crystal clear: "to permit 
internationalized email addresses in envelopes, and UNICODE characters 
(encoded in UTF-8) [RFC3629] in headers." Are addresses in envelopes (SMTP 
envelopes!) also via UNICODE characters encoded in UTF-8? The reference to 
"the framework document" seem to come too late in the text to ensure the 
reader fully understand the relationship.

  3.2 The UTF8SMTPbis Extension

"An SMTP server that announces this extension MUST be prepared to
accept a UTF-8 string [RFC3629] in any position in which RFC 5321
specifies that a mailbox can appear."

s/mailbox/<mailbox>/  (it's a definition!).

The specification does NOT suggest a preferred order among the 3 possible
options when the SMTP server state it does not support UTF8SMTPbis. Having 3
"MAY" options at the same level can create a very uncertain email service
behaviour, and a very bad user's experience! This is consistent with what
happens in other cases for other "options" in the email system (like DSNs
and MDNs), but there should be at least an informative document describing
the various scenarios, and giving some guidance to implementors in order to
avoid totally incosistent behaviours.

If we do not specify a consistent procedure to try the 3 options, in many
cases we will just in practice break the concept of universal email common
service, creating islands which do not talk to each other. The 3.6.2 section
gives some suggestions about this, but this is limited to MX listed servers
for a single domain. My concern is more general. In 3.6.2 anyhow the
language should be more precise. It states "orgnisations", which something
totally undefined from a protocol point of view. MX records refer to
"domains", not to "organisations".


   3.3.  Extended Mailbox Address Syntax

The definition of

              uAtom = 1*ucharacter
                ; Replace Atom in RFC 5321, Section 4.1.2

              ucharacter = atext / UTF8-non-ascii

              atext = <See Section 3.2.3 of RFC 5322>

permits that uAtom is either an atext OR an UTF8-non-ascii... which in the
end allows a uMailbox to be a mixed contruction where some uAtom is in
atext, while some other uAtom is in UTF8-non-ascii AT THE SAME TIME, e.g. a
construct like

      some-ascii.some-UTF8-non-ascii@some-UTF8-non-ascii.some-ascii.tld

is allowed. However the distinction here seems to be unneeded, as ASCII is a
subset of UTF8.

Section 3.6 tries to clarify that this is not allowed; owever there is
normative language there apart on SHOULD for the domain name. I think this
shold be fixed with a clearer normative specfication.

This of course applies also to all other tokens where uAtom is used.

3.5 Body Parts and SMTP Extensions

I have problems in understanding why an SMTP server should peek extensively
into the message geing transfered to understand that it is handling an
interationalzed message. "There is no ESMTP parameter to assert that a
message is an internationalized message." in my opinion should be fixed in
another way, by ADDING an appropriate ESMTP parameter to state this! This
will solve already in the SMTP dialogue many isses which in this
specification are handeled by guessing techinques.

3.6.1 "the server normally sends..." --> "the server sends" (sorry... we do
not like ABnormal servers!) :-)

   Minor Issues:

1. Introduction

The sentence "This document use this mechanism to support an
internationalized email address." defintly needs a better form; if you do
not know already know what we are talking about, it can be misleading.

"This document uses this mechanism to allow internationalized email
addresses support in SMTP elements."

3.1 Framework for the Internationalization Extension

- bullet point 3. I do not see any need to state that clients MUST reject...
and MUST be fully compliant... etc. This is implicit in any specification.
If there is a specific need to add this detailed behaviour (to prevent wrong
implementions? why?) either we shall ensure the text is clear and
unambiguous, or we shall add an Implementers Note, as it was done in some
other RFCs.

3.2 The UTF8SMTPbis Extension

same general comment as per 3.1: in general the section states behaviours
which do not need to be specified again, because they're alredy described
seomewhere else. This might also become a Major issue if the specification
of such behaviours are changed elsewhere. Just poit to extrnal references.
(it seems editors are worried of implmentors which do not fully undesrtand
or know the other email specifications... )

3.3.  Extended Mailbox Address Syntax

What does the sentence "..., using the production for a mailbox and those
productions on which it depends." mean? I assume you meant <mailbox>, is
this correct?

5.  Security Considerations

there is one more issue: as internationalized items will also result into
logs and traces, their presence may affects trouble ticket systems used by
security operations teams (CERTs/CSIRTs). And they also can affect quick
handling of incidents, has it may require more time to correctly read and
understand logs and traces if they are not in current ascii form. This might
even be a Major Issue. I propose adding this text in the section, besides
pointing to the exteral reference:

---------------------- start of added text
Beyond the use inside the email global system (in SMTP envelopes and message
headers), internationalized email addresses will also show up inside other
scenarios, in particular:

  - the logging systems of SMTP transactions and other logs to monitor
    the email systems;

  - the trouble ticket systems used by Security Teams to manage security
    incidents, when an email address is involved

This will likely require extending support for full UTF8 also into these
systems, in order to avoid problems, which could cause also important loss
of data, or require to provide an adequate mechanism to map non ASCII
strings into them.

Another Security aspect to consider is related to the ability by Security
Team members to quickly understand/read and identify email addresses from
the logs, when they are tracking an incident. Mechanims to automatically and
quickly provide the origin or ownership of an internationalized email
address shall implemented for use also by log readers which cannot read
easily non-ASCII information.
--------------------------- end of added text

Also, in Security Consideration, there is no mention of the fact that we are
changing VRFY/EXPN commands to include internationalized addresses.
VRFY/EXPN commands can exist ALSO in an SMTP transaction which is not
supoused to transfer an email messages between MTAs. And their use has also
do to with Security. Here is an additional text for this:

---------------------- start of added text
The SMTP commands VRFY and EXPN are sometimes used in SMTP transactions
where there is no message to transfer (by tools used to take automated
actions in case potential spam messages are identified). RFC5321 section 3.5
and 7.3 give some detailed description of use and possible behaviours.
Implementation of internationalized addrsses can affect also logs and
actions by these tools.
--------------------------- end of added text

   Nits:

see
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-eai-rfc5336bis-07.txt

Best Regards!

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From ned.freed@mrochek.com  Wed Dec 22 18:00:19 2010
Return-Path: <ned.freed@mrochek.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 0EE9D3A6B73; Wed, 22 Dec 2010 18:00:19 -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 o94ZlK-EsVdQ; Wed, 22 Dec 2010 18:00:17 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 747FF3A6957; Wed, 22 Dec 2010 18:00:15 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVQAP22BVK00D8M6@mauve.mrochek.com>; Wed, 22 Dec 2010 18:02:13 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVQAMJ9A8W007CHU@mauve.mrochek.com>; Wed, 22 Dec 2010 18:02:10 -0800 (PST)
Message-id: <01NVQAP0UQRU007CHU@mauve.mrochek.com>
Date: Wed, 22 Dec 2010 18:01:15 -0800 (PST)
From: Ned Freed <NED+eai@mauve.mrochek.com>
In-reply-to: "Your message dated Wed, 22 Dec 2010 18:24:11 +0100 (CET)" <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
Sender: Ned Freed <ned.freed@mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
To: apps-discuss@ietf.org, ima@ietf.org, draft-ietf-eai-rfc5336bis@tools.ietf.org, Alexey.Melnikov@isode.com, SM <sm+ietf@elandsys.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293066799; bh=Feemn/cXE+aVE7HLK0R4oHPQIAS3TSAWB9Mo5Lr55is=; h=Message-id:Date:From:Subject:In-reply-to:Sender:MIME-version: Content-type:References:To; b=jD8FPwA5C5AtLZlBdWz1kTY25Av4FQAqPbvUdY7U5+l7SQfRAa1HivY4eon38U4p2 oJ7zlpFucd4qwNXyiQeQbjDossE5uHwcY4tMbgj4AYaov0FMFe9O5nYHI27yHrrP5q lwGRGvyhw35vkV6VJ9hDj5uTfuWOO1b+HQ7YkdH0=
X-Mailman-Approved-At: Wed, 22 Dec 2010 18:04:01 -0800
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 23 Dec 2010 02:00:19 -0000

I was asked to review draft-ietf-eai-rfc5336bis-07.txt. I was also provided
with a preliminary copy of the review Dave did, so these notes should be viewed
as an addendum to Dave's review, not as a standalone critique. In particular,
any failure to reiterate Dave's various points here should not be taken as
disagreement with him; on the contrary, I am in agreement with almost all of
his comments.

Now for the specifics:

(0) I cannot emphasize strongly enough how important it is to have a
    UTF8SMTP sort of parameter on the MAIL FROM to indicate that a message
    employing this extension is being submitted/relayed/delivered. This is
    especially important in the relay case - we do not want to require
    that relays grub through every message they receive looking for possible
    utf-8 so they can carry the negotiation of this extension forward, but
    that's exactly what the present proposal forces them to do.

(1) 3.1 item 4 and 3.6.4.2 add an optional UTF8REPLY parameter to VRFY and
    EXPN. They do this by redefining the syntax to be:

    vrfy = "VRFY" SP ( uLocal-part / uMailbox )
                     [ SP "UTF8REPLY" ] CRLF

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

    The original syntax for VRFY and EXPN given in RFC 5321 is:

    vrfy = "VRFY" SP String CRLF
    expn = "EXPN" SP String CRLF
    String = Atom / Quoted-string
    Atom = 1*atext

    It's not immediately obvious, but the new syntax is in fact a superset of
    the old. (uLocal-part subsumes local-part, which in turn allows atoms
    and quoted strings.) However, this change does much more than hang a
    parameter on the command; for the first time an entire address is
    permitted as an EXPN/VRFY argument. But no semantics are given for
    this significant syntax expansion, nor does this expansion appear to be
    within scope for EAI.

    A more reasonable syntax would be:

    vrfy = "VRFY" SP uString [ SP "UTF8REPLY" ] CRLF

    expn = "EXPN" SP uString [ SP "UTF8REPLY" ] CRLF

    uString = uAtom / uQuoted-string

    But this now fails along a different dimension: When adding a parameter
    capability to a command, it should be done in a general way, so that any
    future extensions can build on a cleanly specified foundation. Like so:

    vrfy = "VRFY" SP uString [ SP vrfy-parameters ] CRLF
    vrfy-parameters = esmtp-param *(SP esmtp-param)

    expn = "EXPN" SP uString [ SP expn-parameters ] CRLF
    expn-parameters = esmtp-param *(SP esmtp-param)

    uString = uAtom / uQuoted-string

    Of course this will add 555 as a possible response to VRFY/EXPN, and that
    needs to be noted.

(2) In response to Dave's critique/query about why the parameter on VRFY and
    EXPN is needed, it's because these commands can appear outside of a
    transaction and thus there's not necessarily an indication that the client
    is prepared to accept UTF-8 responses. However, this brings up another
    issue, which is that a server that supports this extension needs a way
    to tell a client that doesn't that it cannot return a proper response
    to VRFY/EXPN without that parameter being specified. A new SMTP error
    status is needed, but the document only defines an extended status
    for this purpose; it doesn't specify a regular status code to use.

(3) Section 3.2 says:

   1.  If and only if the SMTP client (sender) is a Message Submission
       Server ("MSA") [RFC4409], it MAY, consistent with the general
       provisions for changes by such servers, rewrite the envelope,
       headers, or message material to make them entirely ASCII and
       consistent with the provisions of RFC 5321 [RFC5321] and RFC 5322
       [RFC5322].

    This is a bad idea no matter how you slice it. Such transformations
    depend on the availability of address mapping (from a UTF-8 address to
    an equivalent ASCII address) information; an agent being an MSA is neither
    necessary nor sufficient reason to have this information.

    But the bigger problem by far is defining what transformations are
    permissible. The present framework document is basically silent on
    what's allowed, so I for one have no idea what it means to be
    "consistent with the general provisions for changes by such servers"
    actually means. And unless you're willing to spell this out, I see this
    as practically guarnteeing a slew of interop problems.

(4) Also from 3.2:

  3.  It may find an alternate route to the destination that permits
       UTF8SMTPbis.  That route may be discovered by trying alternate
       Mail eXchanger (MX) hosts (using preference rules as specified in
       RFC 5321) or using other means available to the SMTP-sender.

    So you can use alternate MXes, but not alternate A records? I actually
    agree with this - an alternate A is presumably another address for
    the same host, so no point in trying it. But this needs to be spelled
    out.

    At an absolute minimum this needs to be accompanied by some
    security considerations text. The issue, I hope, is obvious: There
    are sites aplenty with large numbers of MX records and which won't
    support this extension any time soon. And all too often those MXes
    are *slow* to respond. So sending a message that causes them all to
    be tried is ... you get the idea.

    In fact I'm tempted to go one further and say that if an MX at a given
    priority is found not to support this extension, you SHOULD assume that
    MXes at lower priority don't either.

(5) Consider this text from 3.5:

   Assuming that the server advertises UTF8SMTPbis and 8BITMIME, and
   receives at least one non-ASCII address, the precise interpretation
   of "BODY=8BITMIME", and "BODY=BINARYMIME" in the MAIL command is:

   Since when are the addresses in the envelope a predictor of the addresses
   that appear in the outermost header, let alone any enclosed message/rfc822
   headers? Really, this could not be more fundamental: There's no requirement
   that envelope addresses appear in the outermost header or vice versa, and
   circumstances abound where the addresses in the header and envelope end up
   being partly or entirely disjoint. As such, while the use of UTF-8 in the
   envelope can be taken as an indication that this is an EAI message, the
   absence tells you nothing.

   Addrressing item (0) above and having a parameter on MAIL FROM addresses the
   technical side of this one, but the entire notion of coupling and
   confusion between envelope and header needs to be stamped out in this
   specification.

(6) A bunch of the references are to bis-versions, but the actual cite is to
    the current RFC.

One final comment. Several of the issues that have been raised are so
fundamental that once they are addressed (point (0) especially), this document
is almost certainly going to require another full review cycle.

				Ned

From ned.freed@mrochek.com  Wed Dec 22 18:07:36 2010
Return-Path: <ned.freed@mrochek.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 2F5AA3A6AA6; Wed, 22 Dec 2010 18:07:36 -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 gBiGcP0j3C8I; Wed, 22 Dec 2010 18:07:34 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 93D233A6957; Wed, 22 Dec 2010 18:07:19 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVQAXTWAPC00FC49@mauve.mrochek.com>; Wed, 22 Dec 2010 18:09:17 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVQAMJ9A8W007CHU@mauve.mrochek.com>; Wed, 22 Dec 2010 18:09:15 -0800 (PST)
Message-id: <01NVQAXSNK5E007CHU@mauve.mrochek.com>
Date: Wed, 22 Dec 2010 18:03:33 -0800 (PST)
From: Ned Freed <NED+eai@mauve.mrochek.com>
In-reply-to: "Your message dated Wed, 22 Dec 2010 18:24:11 +0100 (CET)" <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
Sender: Ned Freed <ned.freed@mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
To: Claudio Allocchio <Claudio.Allocchio@garr.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293067223; bh=hH6DXkCbJV6lEwbPJ3TFQPifXS5OfU0z3aN4i63hBUE=; h=Cc:Message-id:Date:From:Subject:In-reply-to:Sender:MIME-version: Content-type:References:To; b=e+BeQBALaRxEya6wlyokbn81pduiNeZPBuyLkoBgJpUQfUzYRnGPCDmZpZJT0HWMB xv+VfJPbASocH9RrHxVKObN+O9olfT668W27FPqEMuTQkudfgoufLxOqUdzgFPS+IS wECkM7fetEs4L1UH3JI4x6hJ8IrNwWB7/qM/Flt8=
Cc: Alexey.Melnikov@isode.com, draft-ietf-eai-rfc5336bis@tools.ietf.org, ima@ietf.org, apps-discuss@ietf.org, SM <sm+ietf@elandsys.com>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 23 Dec 2010 02:07:36 -0000

+1 to all of Claudio's points raised here.

				Ned

> I have been selected as the Applications Area Review Team reviewer for this
> draft (for background on apps-review, please see
> http://www.apps.ietf.org/content/applications-area-review-team).

> Please resolve these comments along with any other Last Call comments you
> may receive. Please wait for direction from your document shepherd or AD
> before posting a new version of the draft.

> Document: draft-ietf-eai-rfc5336bis
> Reviewer: Claudio Allocchio (GARR, Italian Research and Academic Network)
> Review Date: 2010-12-22
> IETF Last Call Date:  N/A
> IESG Telechat Date:  N/A

> Summary:

> The document specifies how to apply internationalization to some SMTP
> elements, and to some Header elements which depends from the SMTP elements.
> However there seem to be a discrepancy from what the abstract states, and
> what is elaborated into the document details: the document also deals with
> quite a number of elements which involve bodyparts, and affect the whole
> email legacy system, and beyond, such as logs, traces, and wherever email
> addresses are used (certificates, etc.). This seems thus to go beyond what
> the summary states, even this fact is not explicitly discussed. It is
> unclear thus if this "update" of RFC5321 and RFC5322 is only limited in
> scope or not. My reading of the document say it goes beyond, and implicitly
> affects also what is being transported into the email system. This is thus a
> serious issue to be solved before the document can go to the Standard Track.
> Another big issue is about blending the boundaries of servers in the
> transport system (MTAs), clients (UAs) and their roles, when the document
> specify that servers shall use guessing techniques from looking into
> bodyparts to understand if what they're transporting is internationalized
> according to this specification or not. This is IMHO a basic violation of
> the role distiction in the legacy email system, and affects the MIME model
> al well.

> The document quite often repeats rules from other specifications, AND
> re-describes these rules. This is dangerous (it makes very difficult to keep
> aligned documents, and will lead to different interpretations) and not
> needed.

> The full specification probably needs a serious "english language" revision,
> because the language issues which I specified in "Minor Issues" seems to be
> a non neglegible number. I'll try to identify as many as possible and
> suggest changes.

> Major Issues:

> This specification updates a number of SMTP and Headers fields from RFC5321
> and RFC5322. However these fields are also used in Gatewaying to other email
> systems, which are still existing. Section 3.7 in RFC5321 describes specific
> cases. However this memo provides no clue on possible effect that
> internationalized fields can have in case gatewaying occurs. Gatewaying
> functions strongly rely on these values, and the introduction of these
> modification should describe this scenario, too. I suggest to include a
> specific section about these issues, and suggest at least a number of
> possible actions which Gateways can take to survive this change.

> The EAI WG charter states that in handling email message we shall be
> "consistent with the long-term view that email with invalid addresses or
> syntax should be rejected, rather than fixed up in transit between
> submission servers and delivery servers.". However a number of sections in
> the specification seem to contradict this, where they suggest actions, by
> exammining message elements (in the SMTP and in the Headers and in the
> Bodyparts) in order to try to deliver anyhow. This is a subtle line between
> maximising the service chance to deliver, and "fixing" things during the
> transaction, and it can encourage implementors to do many of these acions,
> instead of stiching to the idea "not supported --> non delivery".

> Major Issues by sections.

> Abstract:

> " This document specifies an SMTP extension for transport and delivery
>     of email messages with internationalized email addresses or header
>     information."

> "internationalized" is not defined here in details. Sections 1 and 1.2 try
> to do this, but the language is not crystal clear: "to permit
> internationalized email addresses in envelopes, and UNICODE characters
> (encoded in UTF-8) [RFC3629] in headers." Are addresses in envelopes (SMTP
> envelopes!) also via UNICODE characters encoded in UTF-8? The reference to
> "the framework document" seem to come too late in the text to ensure the
> reader fully understand the relationship.

>   3.2 The UTF8SMTPbis Extension

> "An SMTP server that announces this extension MUST be prepared to
> accept a UTF-8 string [RFC3629] in any position in which RFC 5321
> specifies that a mailbox can appear."

> s/mailbox/<mailbox>/  (it's a definition!).

> The specification does NOT suggest a preferred order among the 3 possible
> options when the SMTP server state it does not support UTF8SMTPbis. Having 3
> "MAY" options at the same level can create a very uncertain email service
> behaviour, and a very bad user's experience! This is consistent with what
> happens in other cases for other "options" in the email system (like DSNs
> and MDNs), but there should be at least an informative document describing
> the various scenarios, and giving some guidance to implementors in order to
> avoid totally incosistent behaviours.

> If we do not specify a consistent procedure to try the 3 options, in many
> cases we will just in practice break the concept of universal email common
> service, creating islands which do not talk to each other. The 3.6.2 section
> gives some suggestions about this, but this is limited to MX listed servers
> for a single domain. My concern is more general. In 3.6.2 anyhow the
> language should be more precise. It states "orgnisations", which something
> totally undefined from a protocol point of view. MX records refer to
> "domains", not to "organisations".


>    3.3.  Extended Mailbox Address Syntax

> The definition of

>               uAtom = 1*ucharacter
>                 ; Replace Atom in RFC 5321, Section 4.1.2

>               ucharacter = atext / UTF8-non-ascii

>               atext = <See Section 3.2.3 of RFC 5322>

> permits that uAtom is either an atext OR an UTF8-non-ascii... which in the
> end allows a uMailbox to be a mixed contruction where some uAtom is in
> atext, while some other uAtom is in UTF8-non-ascii AT THE SAME TIME, e.g. a
> construct like

>       some-ascii.some-UTF8-non-ascii@some-UTF8-non-ascii.some-ascii.tld

> is allowed. However the distinction here seems to be unneeded, as ASCII is a
> subset of UTF8.

> Section 3.6 tries to clarify that this is not allowed; owever there is
> normative language there apart on SHOULD for the domain name. I think this
> shold be fixed with a clearer normative specfication.

> This of course applies also to all other tokens where uAtom is used.

> 3.5 Body Parts and SMTP Extensions

> I have problems in understanding why an SMTP server should peek extensively
> into the message geing transfered to understand that it is handling an
> interationalzed message. "There is no ESMTP parameter to assert that a
> message is an internationalized message." in my opinion should be fixed in
> another way, by ADDING an appropriate ESMTP parameter to state this! This
> will solve already in the SMTP dialogue many isses which in this
> specification are handeled by guessing techinques.

> 3.6.1 "the server normally sends..." --> "the server sends" (sorry... we do
> not like ABnormal servers!) :-)

>    Minor Issues:

> 1. Introduction

> The sentence "This document use this mechanism to support an
> internationalized email address." defintly needs a better form; if you do
> not know already know what we are talking about, it can be misleading.

> "This document uses this mechanism to allow internationalized email
> addresses support in SMTP elements."

> 3.1 Framework for the Internationalization Extension

> - bullet point 3. I do not see any need to state that clients MUST reject...
> and MUST be fully compliant... etc. This is implicit in any specification.
> If there is a specific need to add this detailed behaviour (to prevent wrong
> implementions? why?) either we shall ensure the text is clear and
> unambiguous, or we shall add an Implementers Note, as it was done in some
> other RFCs.

> 3.2 The UTF8SMTPbis Extension

> same general comment as per 3.1: in general the section states behaviours
> which do not need to be specified again, because they're alredy described
> seomewhere else. This might also become a Major issue if the specification
> of such behaviours are changed elsewhere. Just poit to extrnal references.
> (it seems editors are worried of implmentors which do not fully undesrtand
> or know the other email specifications... )

> 3.3.  Extended Mailbox Address Syntax

> What does the sentence "..., using the production for a mailbox and those
> productions on which it depends." mean? I assume you meant <mailbox>, is
> this correct?

> 5.  Security Considerations

> there is one more issue: as internationalized items will also result into
> logs and traces, their presence may affects trouble ticket systems used by
> security operations teams (CERTs/CSIRTs). And they also can affect quick
> handling of incidents, has it may require more time to correctly read and
> understand logs and traces if they are not in current ascii form. This might
> even be a Major Issue. I propose adding this text in the section, besides
> pointing to the exteral reference:

> ---------------------- start of added text
> Beyond the use inside the email global system (in SMTP envelopes and message
> headers), internationalized email addresses will also show up inside other
> scenarios, in particular:

>   - the logging systems of SMTP transactions and other logs to monitor
>     the email systems;

>   - the trouble ticket systems used by Security Teams to manage security
>     incidents, when an email address is involved

> This will likely require extending support for full UTF8 also into these
> systems, in order to avoid problems, which could cause also important loss
> of data, or require to provide an adequate mechanism to map non ASCII
> strings into them.

> Another Security aspect to consider is related to the ability by Security
> Team members to quickly understand/read and identify email addresses from
> the logs, when they are tracking an incident. Mechanims to automatically and
> quickly provide the origin or ownership of an internationalized email
> address shall implemented for use also by log readers which cannot read
> easily non-ASCII information.
> --------------------------- end of added text

> Also, in Security Consideration, there is no mention of the fact that we are
> changing VRFY/EXPN commands to include internationalized addresses.
> VRFY/EXPN commands can exist ALSO in an SMTP transaction which is not
> supoused to transfer an email messages between MTAs. And their use has also
> do to with Security. Here is an additional text for this:

> ---------------------- start of added text
> The SMTP commands VRFY and EXPN are sometimes used in SMTP transactions
> where there is no message to transfer (by tools used to take automated
> actions in case potential spam messages are identified). RFC5321 section 3.5
> and 7.3 give some detailed description of use and possible behaviours.
> Implementation of internationalized addrsses can affect also logs and
> actions by these tools.
> --------------------------- end of added text

>    Nits:

> see
> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-eai-rfc5336bis-07.txt

> Best Regards!

> ------------------------------------------------------------------------------
> Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
>                          Senior Technical Officer
> tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
> fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

>             PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima

From chl@clerew.man.ac.uk  Thu Dec 23 09:49:12 2010
Return-Path: <chl@clerew.man.ac.uk>
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 24CF33A6846 for <ima@core3.amsl.com>; Thu, 23 Dec 2010 09:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.621
X-Spam-Level: 
X-Spam-Status: No, score=-4.621 tagged_above=-999 required=5 tests=[AWL=-1.022, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 XgqcB69RO9br for <ima@core3.amsl.com>; Thu, 23 Dec 2010 09:49:10 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id B5EC43A683D for <ima@ietf.org>; Thu, 23 Dec 2010 09:49:10 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 0049B2229E for <ima@ietf.org>; Thu, 23 Dec 2010 17:51:09 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Thu, 23 Dec 2010 17:51:09 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBNHp7wi024681 for <ima@ietf.org>; Thu, 23 Dec 2010 17:51:09 GMT
Date: Thu, 23 Dec 2010 17:51:07 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vn6g7hky6hl8nm@clerew.man.ac.uk>
In-Reply-To: <01NVQAP0UQRU007CHU@mauve.mrochek.com>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d138c0d.1725c-7d6b-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 23 Dec 2010 17:49:12 -0000

On Thu, 23 Dec 2010 02:01:15 -0000, Ned Freed <NED+eai@mauve.mrochek.com>  
wrote:

> Now for the specifics:
>
> (0) I cannot emphasize strongly enough how important it is to have a
>     UTF8SMTP sort of parameter on the MAIL FROM to indicate that a  
> message
>     employing this extension is being submitted/relayed/delivered. This  
> is
>     especially important in the relay case - we do not want to require
>     that relays grub through every message they receive looking for  
> possible
>     utf-8 so they can carry the negotiation of this extension forward,  
> but
>     that's exactly what the present proposal forces them to do.

Well there was a header for that purpose in the early days of the WG but,  
IIRC, it was omitted because it could not be relied upon as regards  
leakage, and also because we concluded that, although the MTA would have  
to make a complete pass through the body in order to detect the presence  
on non-ascii, most MTAs already had to make that pass anyway as part of  
the 8BITMIME checks, and the extra code now required was neither here not  
there.

But it is some years since we had that discussion. Perhaps someone else  
could recall the exact arguments.

But, having said that, I would not be averse to reinventing that header -   
but be warned that it might turn out not to be as reliable an indication  
as might first appear.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From Shawn.Steele@microsoft.com  Thu Dec 23 10:06: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 122743A6853 for <ima@core3.amsl.com>; Thu, 23 Dec 2010 10:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.381
X-Spam-Level: 
X-Spam-Status: No, score=-10.381 tagged_above=-999 required=5 tests=[AWL=0.218, 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 Gnbda7BPX6YH for <ima@core3.amsl.com>; Thu, 23 Dec 2010 10:06:31 -0800 (PST)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 06D863A6850 for <ima@ietf.org>; Thu, 23 Dec 2010 10:06:30 -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; Thu, 23 Dec 2010 10:08:31 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Thu, 23 Dec 2010 10:08:31 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>, "dhc2@dcrocker.net" <dhc2@dcrocker.net>
Thread-Topic: draft review of: draft-ietf-eai-rfc5336bis-07.txt
Thread-Index: AQHLosxnZKE8WbHRRkm0/0RbbNQAJQ==
Date: Thu, 23 Dec 2010 18:08:31 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B3FD33@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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: Thu, 23 Dec 2010 18:06:32 -0000

U29ycnkgdGhpcyB3YXMgYmVmb3JlIEkgZmluaXNoZWQgcmVhZGluZyB0aGUgcmVzdCBvZiBpdCwg
b3IgSSBjb3VsZCd2ZSBiZWVuIGNsZWFyZXIuDQoNClVURjhTTVRQIHNheXMgdGhlIHNlcnZlcidz
IHdpbGxpbmcgdG8gYWNjZXB0IFVURjguICBDaGFyYWN0ZXJzID4gMHg3ZiBhcmUgaWxsZWdhbCBp
biBhZGRyZXNzZXMuIFNvIGlmIHRoZSBjbGllbnQgc2VuZHMgbWFpbCB3aXRoIGNoYXJhY3RlcnMg
PiAweDdmIGluIHRoZSBoZWFkZXIsIHRoYXQnZCBiZSB0aGUgMm5kIGhhbGYgb2YgdGhlIGhhbmRz
aGFraW5nLiAgRG9lc24ndCB3b3JrIGZvciBWUkZZIC8gRVhQTiwgc28gdGhhdCdzIHdoeSB0aGV5
IGhhdmUgdGhlaXIgb3duIHRoaW5nLg0KDQotU2hhd24NCg0K76Oi76OQ76On76ObIO+jou+jo++j
l++jlO+jmQ0KaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXduc3RlDQoNCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpEYXRlOiBXZWQs
IDIyIERlYyAyMDEwIDE2OjQyOjA0IC0wODAwDQpGcm9tOiBEYXZlIENST0NLRVIgPGRoYzJAZGNy
b2NrZXIubmV0Pg0KU3ViamVjdDogUmU6IFtFQUldIGRyYWZ0IHJldmlldyBvZjogZHJhZnQtaWV0
Zi1lYWktcmZjNTMzNmJpcy0wNy50eHQNClRvOiBTaGF3biBTdGVlbGUgPFNoYXduLlN0ZWVsZUBt
aWNyb3NvZnQuY29tPg0KQ2M6ICJpbWFAaWV0Zi5vcmciIDxpbWFAaWV0Zi5vcmc+DQpNZXNzYWdl
LUlEOiA8NEQxMjlBREMuNzA3MDEwNUBkY3JvY2tlci5uZXQ+DQpDb250ZW50LVR5cGU6IHRleHQv
cGxhaW47IGNoYXJzZXQ9SVNPLTg4NTktMTsgZm9ybWF0PWZsb3dlZA0KDQoNCg0KT24gMTIvMjIv
MjAxMCAxOjQzIFBNLCBTaGF3biBTdGVlbGUgd3JvdGU6DQo+IFRoZSBVVEY4U01UUCBoYW5kc2hh
a2luZyBjbGVhcmx5IGluZGljYXRlcyB0aGF0IHdlJ3JlIHRhbGtpbmcgaW4gVVRGLTguICBObw0K
PiBmdXJ0aGVyIGhhbmRzaGFraW5nIGlzIHRoZXJlZm9yZSByZXF1aXJlZC4NCg0KDQpQbGVhc2Ug
cHJvdmlkZSBzb21lIGNsYXJpZmljYXRpb246DQoNCiAgICAgIFdoZXJlIGRvZXMgdGhlIHRleHQg
ZGVmaW5lIGFuIGV4cGxpY2l0IHByb3RvY29sIGhhbmRzaGFrZSwgc28gdGhhdCBib3RoDQpzaWRl
cyBrbm93IHRoYXQgdGhlIHNlc3Npb24gaXMgbm93IHVzaW5nIFVURi04Pw0KDQpJIGNvdWxkIG5v
dCBmaW5kIGl0IChleGNlcHQgZm9yIFZSRlkgYW5kIEVYUE4uLi4pDQoNCmQvDQoNCg0KLS0NCg0K
ICAgRGF2ZSBDcm9ja2VyDQogICBCcmFuZGVuYnVyZyBJbnRlcm5ldFdvcmtpbmcNCiAgIGJiaXcu
bmV0

From dhc2@dcrocker.net  Thu Dec 23 10:26:37 2010
Return-Path: <dhc2@dcrocker.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 513673A6860 for <ima@core3.amsl.com>; Thu, 23 Dec 2010 10:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aX0POOftGvsX for <ima@core3.amsl.com>; Thu, 23 Dec 2010 10:26:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 546753A685E for <ima@ietf.org>; Thu, 23 Dec 2010 10:26:35 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBNISUdH018187 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 23 Dec 2010 10:28:35 -0800
Message-ID: <4D1394CD.5060509@dcrocker.net>
Date: Thu, 23 Dec 2010 10:28:29 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Shawn Steele <Shawn.Steele@microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 23 Dec 2010 10:28:36 -0800 (PST)
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 23 Dec 2010 18:26:37 -0000

On 12/23/2010 10:08 AM, Shawn Steele wrote:
> Sorry this was before I finished reading the rest of it, or I could've been clearer.
>
> UTF8SMTP says the server's willing to accept UTF8.  Characters>  0x7f are illegal in addresses. So if the client sends mail with characters>  0x7f in the header, that'd be the 2nd half of the handshaking.  Doesn't work for VRFY / EXPN, so that's why they have their own thing.
...
> Date: Wed, 22 Dec 2010 16:42:04 -0800
> From: Dave CROCKER<dhc2@dcrocker.net>
...

>        Where does the text define an explicit protocol handshake, so that both
> sides know that the session is now using UTF-8?


Sean,

Thanks for the follow-up.  Unfortunately, what you have described -- and it 
matches my understanding of the specification -- is only the first part of a 
handshake.  The remaining part is absent.  In other words, it is not a handshake.

Common examples of handshake mechanisms include:

    <http://www.inetdaemon.com/tutorials/internet/tcp/3-way_handshake.shtml>
    <http://en.wikipedia.org/wiki/Challenge-handshake_authentication_protocol>
    <http://en.wikipedia.org/wiki/Transmission_Control_Protocol>

That is, a "handshake" is a synchronization process for changing a condition. 
In this case, it moves an SMTP session from the condition of supporting network 
ASCII, for basic data representation, into the condition of supporting UTF-8.

Synchronization of such a change requires a /mutual/ exchange of coordination 
information, so that each participant can agree to the change.  This requires a 
minimum of one notification in /each direction/.  (More than one is primarily 
useful to cover certain types of failure conditions that occur in networks; 
hence TCP uses a three-way handshake.)

The EAI SMTP extension only has an announcement of UTF-8 capability by the 
server.  It has no corresponding agreement announced by the SMTP client that it 
will participate in support of UTF-8.

Adding a parameter to VRFY and EXPN is a good example of what is needed for the 
MAIL command, in that it is an explicit declaration by the client.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ned.freed@mrochek.com  Thu Dec 23 16:40:27 2010
Return-Path: <ned.freed@mrochek.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 D29F13A68C4 for <ima@core3.amsl.com>; Thu, 23 Dec 2010 16:40:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[AWL=0.268,  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 NWdlT4w+f6la for <ima@core3.amsl.com>; Thu, 23 Dec 2010 16:40:26 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 3FC7A3A687A for <ima@ietf.org>; Thu, 23 Dec 2010 16:40:22 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVRM7CJNE8003BCK@mauve.mrochek.com> for ima@ietf.org; Thu, 23 Dec 2010 16:42:19 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVR6GYPGPS007CHU@mauve.mrochek.com>; Thu, 23 Dec 2010 16:42:17 -0800 (PST)
Message-id: <01NVRM7BIKTM007CHU@mauve.mrochek.com>
Date: Thu, 23 Dec 2010 16:33:32 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 23 Dec 2010 17:51:07 +0000" <op.vn6g7hky6hl8nm@clerew.man.ac.uk>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1; Format=flowed; DelSp=yes
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk>
To: Charles Lindsey <chl@clerew.man.ac.uk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293148394; bh=qu+vDQ2ZO8aXfPg16Vnpjb0TKBke7BlB+kwkjBb3T2Y=; h=Cc:Message-id:Date:From:Subject:In-reply-to:MIME-version: Content-type:References:To; b=l25bI4ohgigYt8a9e9HmnyvVw9h/X4dqRrDuUYHIgGquDZTXbcBziaCu88Ww5Hs2U SMyxiLObfZ9G4KE0uQTlySuyWFypd1zBIjGvYUr9LKaCylufwow0Q9lESYBmV1fsIn +TByAUtUDQOroSUrPgYOQjiuQUPm1IFPoN5OxrqE=
X-Mailman-Approved-At: Thu, 23 Dec 2010 16:48:39 -0800
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 00:40:28 -0000

> On Thu, 23 Dec 2010 02:01:15 -0000, Ned Freed <NED+eai@mauve.mrochek.com>
> wrote:

> > Now for the specifics:
> >
> > (0) I cannot emphasize strongly enough how important it is to have a
> >     UTF8SMTP sort of parameter on the MAIL FROM to indicate that a
> > message
> >     employing this extension is being submitted/relayed/delivered. This
> > is
> >     especially important in the relay case - we do not want to require
> >     that relays grub through every message they receive looking for
> > possible
> >     utf-8 so they can carry the negotiation of this extension forward,
> > but
> >     that's exactly what the present proposal forces them to do.

> Well there was a header for that purpose in the early days of the WG but,

A header doesn't work for this purpose. It needs to be announced in the
envelope. Just as one example, this allows messages sent to an address
that is known not to be able to support utf-8 addresses to be rejected
immediately.

> IIRC, it was omitted because it could not be relied upon as regards
> leakage, and also because we concluded that, although the MTA would have
> to make a complete pass through the body in order to detect the presence
> on non-ascii, most MTAs already had to make that pass anyway as part of
> the 8BITMIME checks, and the extra code now required was neither here not
> there.

That's completely nonsensical on several fronts. First, 8bitMIME is announced
in the envelope so there is no need to scan the message looking for it unless
you want to be especially careful. Second, a check to see if the message
contains 8bit characters is fairly cheap, but a scan to see if the 8bit appears
specifically in addresses is much more expensive - now you're talking about a
full MIME parse. Maybe this doesn't matter when you're running an MTA that
processes a handful of messages a day, but things are a little different when
you're processing several hundred messages a second, which for some MTA is a
*conservative* estimate.

> But it is some years since we had that discussion. Perhaps someone else
> could recall the exact arguments.

> But, having said that, I would not be averse to reinventing that header -
> but be warned that it might turn out not to be as reliable an indication
> as might first appear.

Again, headers don't have the proper semantics. A MAIL FROM parameter, OTOH,
does.

				Ned

From dhc2@dcrocker.net  Thu Dec 23 19:21:17 2010
Return-Path: <dhc2@dcrocker.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 299DE3A68E2 for <ima@core3.amsl.com>; Thu, 23 Dec 2010 19:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wqMZ3kDKNhsq for <ima@core3.amsl.com>; Thu, 23 Dec 2010 19:21:16 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 221003A68E0 for <ima@ietf.org>; Thu, 23 Dec 2010 19:21:16 -0800 (PST)
Received: from [192.168.1.43] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBO3N7BM029085 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 23 Dec 2010 19:23:13 -0800
Message-ID: <4D14121B.1090103@dcrocker.net>
Date: Thu, 23 Dec 2010 19:23:07 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Charles Lindsey <chl@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>	<01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk>
In-Reply-To: <op.vn6g7hky6hl8nm@clerew.man.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 23 Dec 2010 19:23:13 -0800 (PST)
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 03:21:17 -0000

On 12/23/2010 9:51 AM, Charles Lindsey wrote:
> On Thu, 23 Dec 2010 02:01:15 -0000, Ned Freed <NED+eai@mauve.mrochek.com> wrote:
>> (0) I cannot emphasize strongly enough how important it is to have a
>> UTF8SMTP sort of parameter on the MAIL FROM to indicate that a message
>> employing this extension is being submitted/relayed/delivered.
...
> Well there was a header for that purpose in the early days of the WG but, IIRC,


The difference between attaching information to a header field WITHIN an object, 
versus attaching it to meta-data OUTSIDE OF the object is fundamental.

By the time you are processing the header field that is within the object, you 
have already established the processing context for that object.

If you want to switch the basic set of characters that apply to the header of a 
message, you must declare the new set BEFORE you start processing the header.

THAT is why UTF-8 must be declared in the SMTP protocol and not later.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc2@dcrocker.net  Fri Dec 24 09:28:18 2010
Return-Path: <dhc2@dcrocker.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 F33B23A6830 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 09:28:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 VNaXSvZs59yp for <ima@core3.amsl.com>; Fri, 24 Dec 2010 09:28:16 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id AFF1E3A680B for <ima@ietf.org>; Fri, 24 Dec 2010 09:28:16 -0800 (PST)
Received: from [192.168.1.63] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBOHUDpN014627 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 24 Dec 2010 09:30:19 -0800
Message-ID: <4D14D8A3.1080107@dcrocker.net>
Date: Fri, 24 Dec 2010 09:30:11 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Abel Yang <abelyang@twnic.net.tw>, Shawn Steele <Shawn.Steele@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 24 Dec 2010 09:30:19 -0800 (PST)
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: [EAI] UTF-8 in a Subject header field?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 17:28:18 -0000

Hi.

I am reading through draft-ietf-eai-rfc5335bis-07.txt and can see modifications 
to support Unicode in addresses and Received header fields.  However I do not 
see support for UTF-8 or Unicode in the Subject header field or any other header 
fields.

Since my understanding of the goal of the draft is to provide native UTF-8 
support for the email header, I assume it is meant for all user-visible data.

So I thought I should ask how the working group expects UTF-8 Subject data and 
data in other free-form header-fields to be handled.

Thanks.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From johnl@iecc.com  Fri Dec 24 10:45:07 2010
Return-Path: <johnl@iecc.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 9AB553A6833 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 10:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.063
X-Spam-Level: 
X-Spam-Status: No, score=-111.063 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_ENC_UTF8=0.152, 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 4WWVwMwrarz1 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 10:45:05 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 736203A6830 for <ima@ietf.org>; Fri, 24 Dec 2010 10:45:05 -0800 (PST)
Received: (qmail 19579 invoked from network); 24 Dec 2010 18:47:08 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 24 Dec 2010 18:47:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=120b3.4d14eaac.k1012; i=johnl@user.iecc.com; bh=YkjeJZr/V7HVE8qwumVrj3KG/beKpAYqe2QU/R95g4w=; b=fMUtV2Gnz7n4DYPoJ0jvQvWPhx6zTpNHDN9dnjHHCLNSOxg57sVgfT3af338ctPT9NHNOlxDgLTIe/7zuSXOpXCv2YYZoRjA2tEkanyo3qcxBRCT5yBlXxWHYLYzpMRwg+12B51CGlL9YFlsr+56As07j23l+FY3xQT8tAWhxWo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=120b3.4d14eaac.k1012; olt=johnl@user.iecc.com; bh=YkjeJZr/V7HVE8qwumVrj3KG/beKpAYqe2QU/R95g4w=; b=Ido1LhUmGMHQ9S7m4GiVSNmEdeZVhBahVCcAE3p8dzKRERvuYEDJtAbhQRTKyp8Iv29gk6WXDDJqj3bN7Vt/XS4BeVxr90tbcJWXmOSzrLJx33qpSG/j2uxkFxzO1mypiLA3UbBRkePrGcLY8r11Dr6X9dxMHAuC8PezNotvwhE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 24 Dec 2010 18:47:08 -0000
Message-ID: <20101224184708.73906.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ima@ietf.org
In-Reply-To: <4D14D8A3.1080107@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
Subject: Re: [EAI] UTF-8 in a Subject header field?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 18:45:07 -0000

>So I thought I should ask how the working group expects UTF-8 Subject
>data and data in other free-form header-fields to be handled.

Isn't that covered by RFC 2047 ?

  Subject: =?UTF-8?Q?Joyeux=20No=C3=ABl?=

I realize that if we're going to allow bare UTF-8 in addresses, it
might seem reasonable to allow it everywhere, but it's better to avoid
multiple ways to do the same thing.

R's,
John



From klensin@jck.com  Fri Dec 24 11:19: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 F33743A67F1 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 11:19:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 9hajwBf8XkYo for <ima@core3.amsl.com>; Fri, 24 Dec 2010 11:19:15 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id AD25A3A6843 for <ima@ietf.org>; Fri, 24 Dec 2010 11:19:14 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWDCD-0009if-3R; Fri, 24 Dec 2010 14:20:57 -0500
Date: Fri, 24 Dec 2010 14:20:56 -0500
From: John C Klensin <klensin@jck.com>
To: dcrocker@bbiw.net, Abel Yang <abelyang@twnic.net.tw>, Shawn Steele <Shawn.Steele@microsoft.com>
Message-ID: <75C474FB3427ECA25A669CFF@PST.JCK.COM>
In-Reply-To: <4D14D8A3.1080107@dcrocker.net>
References: <4D14D8A3.1080107@dcrocker.net>
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, Claudio Allocchio <Claudio.Allocchio@garr.it>
Subject: Re: [EAI] UTF-8 in a Subject header field?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 19:19:16 -0000

Dave,

First of all, thanks for your careful and comprehensive review
(and, to others, for theirs).  I'm trying to consolidate most of
the more substantive review comments and at least my personal
(as participant and sometime author, but not as WG Chair)
responses to them.  It has turned out to be a larger task than I
had originally estimated, so let me respond to this one note
separately...

--On Friday, December 24, 2010 09:30 -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

> Hi.
> 
> I am reading through draft-ietf-eai-rfc5335bis-07.txt and can
> see modifications to support Unicode in addresses and Received
> header fields.  However I do not see support for UTF-8 or
> Unicode in the Subject header field or any other header fields.
> 
> Since my understanding of the goal of the draft is to provide
> native UTF-8 support for the email header, I assume it is
> meant for all user-visible data.

The WG's intent, as you have deduced, is that one should be able
to simply use UTF-8 in all unstructured header fields,
especially those in which encoded words are permitted by RFC
2047 and its successors.  That intent should be clear from the
second paragraph of Section 2 ("The traditional format...").
Trace fields and fields containing address information are
singled out for special treatment only because of their
interaction with the envelope specifications in rfc5336bis.

The specific problem in this case is that, while the document
specifies many header fields as being UTF-8-capable by virtue of
the changes in Section 4.3, particularly to <ctext>, the RFC
5322 definition of <subject>, <comments>, and <optional-field>s
(and some obsolete equivalents) rely on <unstructured>, which,
in turn, relies on the RFC 5234 definition of VCHAR.  And the
5234 definition of VCHAR is definitely ASCII-only.

So, Section 4.3 needs an updated production for <unstructured>
as well.

The document would, IMO, benefit from a tad more tutorial/
overview text that better explains what header fields are and
are not extended, but that should not be strictly necessary.

This situation raises an aspect of one or two more general
problems that we should probably move to the apps-discuss list:

When working on the previous (experimental) set of documents,
the WG discovered that the IETF has no standardized model or
agreed-upon practices for how to handle the ABNF if an extension
to one document modifies its syntax rules.  The WG struggled, at
length, with the question of how to do that in a way that would
minimize confusion and concluded that the approach it took (old
production names with new definitions) was probably the least
bad.  That may not have been the right choice, and it does lend
itself to errors like this one, but I'd encourage anyone who
wants to complain about the approach taken to think through, and
suggest, alternatives.  Note that one possible alternative would
be to simply replicate the entire RFC 5322 production set, as
extended, in this document, possibly with new names for
everything, but the size of that grammar and the likelihood of
become unsynchronized if the 5322 syntax ever changes, probably
does not recommend that approach.

The other, possibly-separate, problem is that none of the
authors/editors of the EAI core documents had significant prior
experience producing RFC-ready IETF specs, much less specs with
sensitive ABNF.   That is a problem that we need to deal with,
possibly with more educational efforts or metalanguage tutorials
as well as with patience during the review process, unless we
want to doom the IETF to a situation in which only metalanguage
experts and the same old group of people (in my case and maybe
yours, with both meanings of "old") can write new or updated
documents.

best wishes to all for whatever you are celebrating at this time
of year.
   john



> 
> So I thought I should ask how the working group expects UTF-8
> Subject data and data in other free-form header-fields to be
> handled.





From klensin@jck.com  Fri Dec 24 11:39:31 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 D8E7D3A684F for <ima@core3.amsl.com>; Fri, 24 Dec 2010 11:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 7U0Q1ZUuyb5P for <ima@core3.amsl.com>; Fri, 24 Dec 2010 11:39:30 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1A5333A683C for <ima@ietf.org>; Fri, 24 Dec 2010 11:39:29 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWDW7-000ANY-Vr; Fri, 24 Dec 2010 14:41:32 -0500
Date: Fri, 24 Dec 2010 14:41:31 -0500
From: John C Klensin <klensin@jck.com>
To: John Levine <johnl@taugh.com>, ima@ietf.org
Message-ID: <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM>
In-Reply-To: <20101224184708.73906.qmail@joyce.lan>
References: <20101224184708.73906.qmail@joyce.lan>
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: dcrocker@bbiw.net
Subject: Re: [EAI] UTF-8 in a Subject header field?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 19:39:32 -0000

--On Friday, December 24, 2010 18:47 +0000 John Levine
<johnl@taugh.com> wrote:

>> So I thought I should ask how the working group expects UTF-8
>> Subject data and data in other free-form header-fields to be
>> handled.
> 
> Isn't that covered by RFC 2047 ?
> 
>   Subject: =?UTF-8?Q?Joyeux=20No=C3=ABl?=
> 
> I realize that if we're going to allow bare UTF-8 in
> addresses, it might seem reasonable to allow it everywhere,
> but it's better to avoid multiple ways to do the same thing.

Actually, one of the EAI goals has been to gradually retire
"multiple ways to do the same thing" by having encoded words
become gradually obsolete (see Section 7.2 of
draft-ietf-eai-frmwrk-4952bis).

FWIW, at some level, one could "avoid multiple ways to do the
same thing" --and have a much more robust mail environment in
the short and medium term-- by declaring address (and other
envelope-related) information as ASCII forever and confining
internationalization efforts to display names and other textual
subfields that could be expressed as encoded words.   For better
or worse, that option is  clearly not acceptable to large, and
growing, groups of Internet users -- the choices were between
having the IETF standardize an internationalization model that
would eventually work (and interoperate) worldwide and having a
lot of certainly-leaky local protocol extensions that would
divide the Internet mail environment back up into islands
connected by gateways.  

Stated more aggressively, much of the design of the EAI work has
been to move toward a target in which Internet email is as fully
internationalized as possible, with a minimum of kludges left
over from either legacy ASCII or the transition process.
Encoded words were, IMO, an ingenious solution given the
constraints of the time.  But, if we are going to move toward
internationalized email, rather than treating all address and
header elements as ASCII-forever protocol elements, then the
assumption under which EAI was chartered, and the conclusion of
the WG, has been that we needed to figure out how to actually do
that, rather than carrying old i18n-supporting kludges around
forever.

best,
     john





From johnl@taugh.com  Fri Dec 24 12:55:17 2010
Return-Path: <johnl@taugh.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 4BC153A6870 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 12:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.062
X-Spam-Level: 
X-Spam-Status: No, score=-11.062 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_ENC_UTF8=0.152]
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 C9-itO1okP6d for <ima@core3.amsl.com>; Fri, 24 Dec 2010 12:55:15 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 9FCB33A686B for <ima@ietf.org>; Fri, 24 Dec 2010 12:55:15 -0800 (PST)
Received: (qmail 48495 invoked from network); 24 Dec 2010 20:57:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=bd6e.4d15092d.k1012; i=johnl@submit.iecc.com; bh=5Q8iz1xBGK6ibpidQpD+IMh5WyXMsiMFeOoRolpMPsM=; b=MtYyikAYJsgm3M+Ep52msgxn2tIlbFORdVEoYEfdkbgaNd6CgsqWrKCLR1zdO8eW8wWWIL51rtnqZGeTyinrUkU3ICS2n8GvxHXRjc9hJO1uMXmFulA2wTvDEt3EqF9hHY4LNhKW3kE8lg4OKIRJa8JtAOoAaNaBWepwKX5DAKU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=bd6e.4d15092d.k1012; olt=johnl@submit.iecc.com; bh=5Q8iz1xBGK6ibpidQpD+IMh5WyXMsiMFeOoRolpMPsM=; b=kXVhjopqpnH19xb58T7IQCuyL4yhemFux/VBXQ69QqJ0spl4vzfPQ/J7Voys5YvRbqtUlN7UOlMcmPT8LC1sxjdTGP8ZkgKkjN8dTKGiR8d3S97f4+iCyZmlQrLs9/GNd9Mlwxr8frLUo9R65Cd+z0tSUcQvPgDkTbWbouNLX9o=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 Dec 2010 20:56:55 -0000
Date: 24 Dec 2010 15:57:17 -0500
Message-ID: <alpine.BSF.2.00.1012241545410.94715@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <klensin@jck.com>
In-Reply-To: <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM>
References: <20101224184708.73906.qmail@joyce.lan> <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ima@ietf.org, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: [EAI] UTF-8 in a Subject header field?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 20:55:17 -0000

> Actually, one of the EAI goals has been to gradually retire
> "multiple ways to do the same thing" by having encoded words
> become gradually obsolete (see Section 7.2 of
> draft-ietf-eai-frmwrk-4952bis).

Hmmn.  Now that I look at all the documents, I see that.

With that in mind, I'd suggest that the EAI documents would benefit by 
being shorter and more brutal: anywhere you can use arbitrary ASCII you 
can now use arbitrary UTF-8.  All other encodings are deprecated, no 
charsets other than UTF8 in top-level MIME parts, A-labels in addresses 
will cause a razzberry to come out of your speaker.  If you want to send 
mail to somebody who doesn't grok EAI, it's your MUA's job to try to 
create a mail-classic version.

It also suggests that STARTEAI to confirm that we are now in the world of 
EAI would be better than trying to flag every command that might have an 
argument or response.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From Claudio.Allocchio@garr.it  Fri Dec 24 13:39:25 2010
Return-Path: <Claudio.Allocchio@garr.it>
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 917563A687D for <ima@core3.amsl.com>; Fri, 24 Dec 2010 13:39:25 -0800 (PST)
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.060,  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 srtS-LSZHdmz for <ima@core3.amsl.com>; Fri, 24 Dec 2010 13:39:24 -0800 (PST)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id 2BD4C3A6870 for <ima@ietf.org>; Fri, 24 Dec 2010 13:39:23 -0800 (PST)
Received: from mac-allocchio3.garrtest.units.it (mac-allocchio3.garrtest.units.it [140.105.201.3]) (authenticated bits=0) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id oBOLfBQE000816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Dec 2010 22:41:12 +0100 (CET)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 cyrus.dir.garr.it oBOLfBQE000816
DomainKey-Signature: a=rsa-sha1; s=mail; d=garr.it; c=simple; q=dns; b=h6etb09DCn0dNl/gcOlv0yk1LulBKnpzhBUNihTQVCDKWZiLKuWsHJp+0WVG+wHMG otASckAR/KS7z4wWgT+cGbXerMX+i44qGzBCbzgP7TsRplN1VXY3nL4/XiBkB12BJn0 cfyC0H63CmhZvDU9s23vQQ84EgZ1NayiX7M011Y=
Date: Fri, 24 Dec 2010 22:41:10 +0100 (CET)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.garrtest.units.it
To: John C Klensin <klensin@jck.com>
In-Reply-To: <75C474FB3427ECA25A669CFF@PST.JCK.COM>
Message-ID: <Pine.OSX.4.64.1012242238560.46539@mac-allocchio3.garrtest.units.it>
References: <4D14D8A3.1080107@dcrocker.net> <75C474FB3427ECA25A669CFF@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Claudio Allocchio <Claudio.Allocchio@garr.it>, ima@ietf.org, Shawn Steele <Shawn.Steele@microsoft.com>, dcrocker@bbiw.net
Subject: [EAI] Seasons' Greetings!
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 21:39:25 -0000

On Fri, 24 Dec 2010, John C Klensin wrote:

> best wishes to all for whatever you are celebrating at this time
> of year.

Thank you, and let me add my best wishes, too!


------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From SRS0=5/TOXx=TX=taharlev.com=daniel@srs.bis3.ap.blackberry.com  Fri Dec 24 13:46:11 2010
Return-Path: <SRS0=5/TOXx=TX=taharlev.com=daniel@srs.bis3.ap.blackberry.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 98A5A3A688D; Fri, 24 Dec 2010 13:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.723
X-Spam-Level: 
X-Spam-Status: No, score=-5.723 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
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 t1r-k1m45ESb; Fri, 24 Dec 2010 13:46:10 -0800 (PST)
Received: from smtp01.bis.ap.blackberry.com (smtp01.bis.ap.blackberry.com [216.9.247.48]) by core3.amsl.com (Postfix) with ESMTP id 995593A688C; Fri, 24 Dec 2010 13:46:09 -0800 (PST)
Received: from b27.c1.bise3.blackberry ([192.168.0.127]) by srs.bis3.ap.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id oBOLOaCh012511; Fri, 24 Dec 2010 21:48:11 GMT
X-rim-org-msg-ref-id: 342892338
Message-ID: <342892338-1293227291-cardhu_decombobulator_blackberry.rim.net-50040754-@b27.c1.bise3.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <4D14D8A3.1080107@dcrocker.net><75C474FB3427ECA25A669CFF@PST.JCK.COM><Pine.OSX.4.64.1012242238560.46539@mac-allocchio3.garrtest.units.it>
In-Reply-To: <Pine.OSX.4.64.1012242238560.46539@mac-allocchio3.garrtest.units.it>
Sensitivity: Normal
Importance: Normal
To: "Claudio Allocchio" <Claudio.Allocchio@garr.it>, ima-bounces@ietf.org, "John C Klensin" <klensin@jck.com>
From: "Daniel Taharlev" <daniel@taharlev.com>
Date: Fri, 24 Dec 2010 21:48:07 +0000
Content-Type: text/plain
MIME-Version: 1.0
Cc: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, dcrocker@bbiw.net
Subject: Re: [EAI] Seasons' Greetings!
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: daniel@taharlev.com
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Dec 2010 21:49:49 -0000

KzENCg0KDQoNCkRhbmllbCBUYWhhcmxldg0KZGFuaWVsQHRhaGFybGV2LmNvbQ0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQ2xhdWRpbyBBbGxvY2NoaW8gPENsYXVkaW8uQWxs
b2NjaGlvQGdhcnIuaXQ+DQpTZW5kZXI6IGltYS1ib3VuY2VzQGlldGYub3JnDQpEYXRlOiBGcmks
IDI0IERlYyAyMDEwIDIyOjQxOjEwIA0KVG86IEpvaG4gQyBLbGVuc2luPGtsZW5zaW5AamNrLmNv
bT4NCkNjOiBDbGF1ZGlvIEFsbG9jY2hpbzxDbGF1ZGlvLkFsbG9jY2hpb0BnYXJyLml0PjsgPGlt
YUBpZXRmLm9yZz47IFNoYXduIFN0ZWVsZTxTaGF3bi5TdGVlbGVAbWljcm9zb2Z0LmNvbT47IDxk
Y3JvY2tlckBiYml3Lm5ldD4NClN1YmplY3Q6IFtFQUldIFNlYXNvbnMnIEdyZWV0aW5ncyENCg0K
DQpPbiBGcmksIDI0IERlYyAyMDEwLCBKb2huIEMgS2xlbnNpbiB3cm90ZToNCg0KPiBiZXN0IHdp
c2hlcyB0byBhbGwgZm9yIHdoYXRldmVyIHlvdSBhcmUgY2VsZWJyYXRpbmcgYXQgdGhpcyB0aW1l
DQo+IG9mIHllYXIuDQoNClRoYW5rIHlvdSwgYW5kIGxldCBtZSBhZGQgbXkgYmVzdCB3aXNoZXMs
IHRvbyENCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNsYXVkaW8gQWxsb2NjaGlvICAgICAg
ICAgICAgIEcgICBBICAgUiAgIFIgICAgICAgICAgQ2xhdWRpby5BbGxvY2NoaW9AZ2Fyci5pdA0K
ICAgICAgICAgICAgICAgICAgICAgICAgIFNlbmlvciBUZWNobmljYWwgT2ZmaWNlcg0KdGVsOiAr
MzkgMDQwIDM3NTg1MjMgICAgICBJdGFsaWFuIEFjYWRlbWljIGFuZCAgICAgICBHPUNsYXVkaW87
IFM9QWxsb2NjaGlvOw0KZmF4OiArMzkgMDQwIDM3NTg1NjUgICAgICAgIFJlc2VhcmNoIE5ldHdv
cmsgICAgICAgICBQPWdhcnI7IEE9Z2FycjsgQz1pdDsNCg0KICAgICAgICAgICAgUEdQIEtleTog
aHR0cDovL3d3dy5jZXJ0LmdhcnIuaXQvUEdQL2tleXMucGhwMyNjYQ0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklNQSBtYWlsaW5nIGxpc3QNCklNQUBp
ZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbWENCg0K

From klensin@jck.com  Fri Dec 24 16:41:14 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 CCD223A68C1 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 16:41:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 GteIYuMiDvzn for <ima@core3.amsl.com>; Fri, 24 Dec 2010 16:41:14 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id CE4203A68BD for <ima@ietf.org>; Fri, 24 Dec 2010 16:41:13 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWIE7-000Hjp-Fm; Fri, 24 Dec 2010 19:43:15 -0500
Date: Fri, 24 Dec 2010 19:43:14 -0500
From: John C Klensin <klensin@jck.com>
To: John R Levine <johnl@taugh.com>
Message-ID: <E5F66B04416DC1DA0EED6F75@PST.JCK.COM>
In-Reply-To: <alpine.BSF.2.00.1012241545410.94715@joyce.lan>
References: <20101224184708.73906.qmail@joyce.lan> <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM> <alpine.BSF.2.00.1012241545410.94715@joyce.lan>
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, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: [EAI] UTF-8 in a Subject header field?
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, 25 Dec 2010 00:41:15 -0000

--On Friday, December 24, 2010 15:57 -0500 John R Levine
<johnl@taugh.com> wrote:

>> Actually, one of the EAI goals has been to gradually retire
>> "multiple ways to do the same thing" by having encoded words
>> become gradually obsolete (see Section 7.2 of
>> draft-ietf-eai-frmwrk-4952bis).
> 
> Hmmn.  Now that I look at all the documents, I see that.
> 
> With that in mind, I'd suggest that the EAI documents would
> benefit by being shorter and more brutal: anywhere you can use
> arbitrary ASCII you can now use arbitrary UTF-8.  All other
> encodings are deprecated, no charsets other than UTF8 in
> top-level MIME parts, A-labels in addresses will cause a
> razzberry to come out of your speaker.  If you want to send
> mail to somebody who doesn't grok EAI, it's your MUA's job to
> try to create a mail-classic version.

Some variations on this theme were considered at length by the
WG, probably circa 2006.  The problem is that it creates a
nasty, probably fatal, transition problem at a level that would
make "new mail protocol on new port and just try one, then the
other" attractive.   The WG decided that was a bad idea; the
current model has now effectively been through IETF Last Call
and consensus three times: approval of what became RFC 4942
(March 2007), approval of what became RFC 5335, 5336, and 5337
(July 2008), and approval of draft-ietf-eai-frmwrk-4952bis (last
September).  Those are not merely WG decisions but decisions
that the IETF has had multiple chances to review over a nearly 3
1/2 year period, with published Experimental protocols and
implementations in the middle.   

At some point, it has to be too late to redesign the basic
model, at least absent empirical demonstration of showstoppers.

> It also suggests that STARTEAI to confirm that we are now in
> the world of EAI would be better than trying to flag every
> command that might have an argument or response.

There is not, as far as I can tell, an "every command"
situation.  The commands that might plausibly be flagged are:

	-- MAIL (as proposed by multiple reviewers but not yet
	accepted by the WG -- see subsequent notes)
	
	-- VRFY and EXPN. 

That combination comes right out of the "mail transaction" model
of RFC 821 that was made more explicit in 2821.  It is not
exactly an EAI invention, nor is it "every command".  One could
do a STARTEAI instead but it would require extra turnarounds in
the non-pipeline case (and, without doing much analysis, I think
even in the pipeline one).

    best,
     john


     


From johnl@taugh.com  Fri Dec 24 19:03:59 2010
Return-Path: <johnl@taugh.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 CAB773A69B4 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 19:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.061
X-Spam-Level: 
X-Spam-Status: No, score=-11.061 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_ENC_UTF8=0.152]
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 BB2jq8U-jYCN for <ima@core3.amsl.com>; Fri, 24 Dec 2010 19:03:58 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 9EFA63A6899 for <ima@ietf.org>; Fri, 24 Dec 2010 19:03:55 -0800 (PST)
Received: (qmail 11050 invoked from network); 25 Dec 2010 03:05:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=2b28.4d155f95.k1012; i=johnl@submit.iecc.com; bh=orVYg5a9kmPD1RmWvqS4O1+2SDcOe2o5LW1h233XIH0=; b=gJVPbw5HpK4GPlPR43esVn5H/NkSOVIHfN2kdq5cERCkHT4xDIBV19USCRuYDTuphAeWH/bUMbVEiyqBt5jWPJGWQWRCrw4oNFSWwt5neltMxxXv1OtYCodz4HTiTX4myNIhaxOfHoPh2wVNB0NaS8J+i0FORkXx3C7HP+rJV4c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=2b28.4d155f95.k1012; olt=johnl@submit.iecc.com; bh=orVYg5a9kmPD1RmWvqS4O1+2SDcOe2o5LW1h233XIH0=; b=HljUYrH1xOYPiNXXv2v6zFyXZBUk3FISL/I5LaSAhQVyL2BZL5hY3cNVQXbo0AU1s8fvu9BV4jXFvGDyaRqcPMmkuihEq5V52f3rMJiPR+vEZMJQ26ARbzOiaE3cncOSTQbPICt0nnehzxMwD6PZ23o4+C808SYP7vDduCE+eh0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 25 Dec 2010 03:05:35 -0000
Date: 24 Dec 2010 22:05:56 -0500
Message-ID: <alpine.BSF.2.00.1012242201240.97546@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <klensin@jck.com>
In-Reply-To: <E5F66B04416DC1DA0EED6F75@PST.JCK.COM>
References: <20101224184708.73906.qmail@joyce.lan> <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM> <alpine.BSF.2.00.1012241545410.94715@joyce.lan> <E5F66B04416DC1DA0EED6F75@PST.JCK.COM>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ima@ietf.org
Subject: Re: [EAI] UTF-8 in a Subject header field?
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, 25 Dec 2010 03:03:59 -0000

>> With that in mind, I'd suggest that the EAI documents would
>> benefit by being shorter and more brutal: anywhere you can use
>> arbitrary ASCII you can now use arbitrary UTF-8.  All other
>> encodings are deprecated, no charsets other than UTF8 in
>> top-level MIME parts, A-labels in addresses will cause a
>> razzberry to come out of your speaker.  If you want to send
>> mail to somebody who doesn't grok EAI, it's your MUA's job to
>> try to create a mail-classic version.
>
> Some variations on this theme were considered at length by the
> WG, probably circa 2006. ...

But I don't see much difference from what the docs say now.  If you're 
sending EAI, you can put UTF-8 in the envelope and pretty much anywhere in 
the headers.  If you're not, you can't, give or take RFC2045 encoded 
strings and A-labels.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From klensin@jck.com  Fri Dec 24 20:19:12 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 A8C773A69B5 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 20:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 2Mdmzksbr30T for <ima@core3.amsl.com>; Fri, 24 Dec 2010 20:19:11 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 952DD3A68DF for <ima@ietf.org>; Fri, 24 Dec 2010 20:19:10 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWLcy-000MhW-Bw; Fri, 24 Dec 2010 23:21:08 -0500
Date: Fri, 24 Dec 2010 23:21:07 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5B92D222E006F894AE0307EC@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.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] 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, 25 Dec 2010 04:19:12 -0000

Shawn,

It isn't clear to me that anyone ever responded to this comment.
If they have, I apologize for the duplication.  If not...

--On Friday, December 03, 2010 21:04 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>...
> In 3.6.3 I don't get why received fields have to use
> A-labels at all?  I assume I missed a discussion?  It would
> seem to me that the end-points are all EAI aware, so it's
> unclear to me why A-labels are necessary anywhere.
>...

Claudio pointed out in his review of 5336bis that there there
are whole array of databases and tools surrounding the email
environment.  His particular concerns were to warn about logs
and the like, but the issue is more general: neither tools nor
people should ever actually need to look at a Trace ("Received")
field unless something has gone wrong or is suspected of having
gone wrong.  Those tools (or people) may not be EAI-aware, may
not have fonts appropriate to display of arbitrary Unicode
strings, may not be able to read such strings (even to iterate
the characters) even if they can display them, etc.    There is
very little advantage in internationalizing those fields and, if
we were to require it, the net effect would either be less
stable operation or delays in deploying EAI as more
infrastructure and training are required to be put in place.

The A-label requirement does require that a MTA that uses a
universal "name resolution" API (the problem discussed in
draft-iab-idn-encoding) perform a U-label to A-label conversion,
but the main issue in draft-iab-idn-encoding really doesn't
apply here: think of the requirement as applying to 

   Received: from ... with smtp ...

or with any of the other "with" keywords specified in 5336bis or
the IANA registry.  "with smtp" is pretty much defined in 5321
as running over TCP.  If one had

   Received: from ... with Proprietary-Email-Transport-XYZ ...

then one would be far enough outside of the combination of 5321
and 5336bis that, if a name (domain or otherwise) is expressed
in UTF-8 (or UTF-16 for that matter), the implementation would
not be significantly more outside the specs.

best,
     john





From Shawn.Steele@microsoft.com  Fri Dec 24 20:36:59 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 87DC13A6899 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 20:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.559
X-Spam-Level: 
X-Spam-Status: No, score=-9.559 tagged_above=-999 required=5 tests=[AWL=-0.626, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_FWDLOOK=1.666]
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 SWr4QY3AvTjr for <ima@core3.amsl.com>; Fri, 24 Dec 2010 20:36:58 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 4719C3A6879 for <ima@ietf.org>; Fri, 24 Dec 2010 20:36:58 -0800 (PST)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 24 Dec 2010 20:39:02 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.01.0255.003; Fri, 24 Dec 2010 20:39:01 -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>
Thread-Topic: [EAI] 5336bis
Thread-Index: AQHLo+szLpydMbQZU02+vAPbytL9FJOwkoHO
Date: Sat, 25 Dec 2010 04:39:01 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B40E87@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com>, <5B92D222E006F894AE0307EC@PST.JCK.COM>
In-Reply-To: <5B92D222E006F894AE0307EC@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] 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, 25 Dec 2010 04:36:59 -0000

VGhhbmtzLCBJIGhhZG4ndCBzZWVuIGEgcmVwbHkgeWV0LiAgSSB1bmRlcnN0YW5kLCBidXQgdGhp
cyBpcyB0aGUga2luZCBvZiAibGVha2luZyIgdGhhdCBtYWtlcyBJRE4gaG9ycmlibGUgdG8gaW50
ZXJvcGVyYXRlIHdpdGguICBTdXJlLCB0aGUgdG9vbHMgbWF5IG5vdCBiZSBVbmljb2RlIGF3YXJl
LCBidXQgdGhleSBhbHNvIG1heSBub3QgYmUgUHVueWNvZGUgYXdhcmUsIG1lYW5pbmcgdGhhdCBz
b21lb25lIGhhcyB0byBmaWd1cmUgb3V0IGhvdyB0byB0cmFuc2xhdGUgaXQuDQoNCklNTyB0aGUg
aGVhZGVycyBhcmUgRUFJLCBzbyB0aGVzZSBzaG91bGQgb25seSBoYXBwZW4gb24gYW4gRUFJIGF3
YXJlIHN5c3RlbSwgaW4gd2hpY2ggY2FzZSB0aGUgdG9vbHMgc2hvdWxkIGJlIHVwZGF0ZWQgOikg
IEVnOiBzb21ldGhpbmcgY291bGQgYmUgYnJva2VuIG5vIG1hdHRlciB3aGF0LCBzbyBJJ2QgcHJl
ZmVyIGl0IHdhcyBicm9rZW4gaW4gYSBmb3J3YXJkLWxvb2tpbmcgd2F5LCB0aGVuIGF0IGxlYXN0
IHdoZW4gdGhlIHRvb2xzIGdvdCBmaXhlZCB0aGV5IHdvdWxkbid0IGFsd2F5cyBoYXZlIHRvIGhh
dmUgdGhlIHB1bnljb2RlIGhhY2suDQoNCkFuZCB0aGlzIGRvZXNuJ3QgaGVscCBtdWNoIGZvciBv
dGhlciBkYXRhIGluIHRoZSBoZWFkZXIsIG9yIGxvY2FsIHBhcnRzLg0KDQotU2hhd24NCg0K76Oi
76OQ76On76ObIO+jou+jo++jl++jlO+jmQ0KaHR0cDovL2Jsb2dzLm1zZG4uY29tL3NoYXduc3Rl
DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogSm9o
biBDIEtsZW5zaW4gW2tsZW5zaW5AamNrLmNvbV0NClNlbnQ6IEZyaWRheSwgRGVjZW1iZXIgMjQs
IDIwMTAgODoyMSBQTQ0KVG86IFNoYXduIFN0ZWVsZTsgaW1hQGlldGYub3JnOyBBbGV4ZXkgTWVs
bmlrb3YNClN1YmplY3Q6IFJlOiBbRUFJXSA1MzM2YmlzDQoNClNoYXduLA0KDQpJdCBpc24ndCBj
bGVhciB0byBtZSB0aGF0IGFueW9uZSBldmVyIHJlc3BvbmRlZCB0byB0aGlzIGNvbW1lbnQuDQpJ
ZiB0aGV5IGhhdmUsIEkgYXBvbG9naXplIGZvciB0aGUgZHVwbGljYXRpb24uICBJZiBub3QuLi4N
Cg0KLS1PbiBGcmlkYXksIERlY2VtYmVyIDAzLCAyMDEwIDIxOjA0ICswMDAwIFNoYXduIFN0ZWVs
ZQ0KPFNoYXduLlN0ZWVsZUBtaWNyb3NvZnQuY29tPiB3cm90ZToNCg0KPi4uLg0KPiBJbiAzLjYu
MyBJIGRvbid0IGdldCB3aHkgcmVjZWl2ZWQgZmllbGRzIGhhdmUgdG8gdXNlDQo+IEEtbGFiZWxz
IGF0IGFsbD8gIEkgYXNzdW1lIEkgbWlzc2VkIGEgZGlzY3Vzc2lvbj8gIEl0IHdvdWxkDQo+IHNl
ZW0gdG8gbWUgdGhhdCB0aGUgZW5kLXBvaW50cyBhcmUgYWxsIEVBSSBhd2FyZSwgc28gaXQncw0K
PiB1bmNsZWFyIHRvIG1lIHdoeSBBLWxhYmVscyBhcmUgbmVjZXNzYXJ5IGFueXdoZXJlLg0KPi4u
Lg0KDQpDbGF1ZGlvIHBvaW50ZWQgb3V0IGluIGhpcyByZXZpZXcgb2YgNTMzNmJpcyB0aGF0IHRo
ZXJlIHRoZXJlDQphcmUgd2hvbGUgYXJyYXkgb2YgZGF0YWJhc2VzIGFuZCB0b29scyBzdXJyb3Vu
ZGluZyB0aGUgZW1haWwNCmVudmlyb25tZW50LiAgSGlzIHBhcnRpY3VsYXIgY29uY2VybnMgd2Vy
ZSB0byB3YXJuIGFib3V0IGxvZ3MNCmFuZCB0aGUgbGlrZSwgYnV0IHRoZSBpc3N1ZSBpcyBtb3Jl
IGdlbmVyYWw6IG5laXRoZXIgdG9vbHMgbm9yDQpwZW9wbGUgc2hvdWxkIGV2ZXIgYWN0dWFsbHkg
bmVlZCB0byBsb29rIGF0IGEgVHJhY2UgKCJSZWNlaXZlZCIpDQpmaWVsZCB1bmxlc3Mgc29tZXRo
aW5nIGhhcyBnb25lIHdyb25nIG9yIGlzIHN1c3BlY3RlZCBvZiBoYXZpbmcNCmdvbmUgd3Jvbmcu
ICBUaG9zZSB0b29scyAob3IgcGVvcGxlKSBtYXkgbm90IGJlIEVBSS1hd2FyZSwgbWF5DQpub3Qg
aGF2ZSBmb250cyBhcHByb3ByaWF0ZSB0byBkaXNwbGF5IG9mIGFyYml0cmFyeSBVbmljb2RlDQpz
dHJpbmdzLCBtYXkgbm90IGJlIGFibGUgdG8gcmVhZCBzdWNoIHN0cmluZ3MgKGV2ZW4gdG8gaXRl
cmF0ZQ0KdGhlIGNoYXJhY3RlcnMpIGV2ZW4gaWYgdGhleSBjYW4gZGlzcGxheSB0aGVtLCBldGMu
ICAgIFRoZXJlIGlzDQp2ZXJ5IGxpdHRsZSBhZHZhbnRhZ2UgaW4gaW50ZXJuYXRpb25hbGl6aW5n
IHRob3NlIGZpZWxkcyBhbmQsIGlmDQp3ZSB3ZXJlIHRvIHJlcXVpcmUgaXQsIHRoZSBuZXQgZWZm
ZWN0IHdvdWxkIGVpdGhlciBiZSBsZXNzDQpzdGFibGUgb3BlcmF0aW9uIG9yIGRlbGF5cyBpbiBk
ZXBsb3lpbmcgRUFJIGFzIG1vcmUNCmluZnJhc3RydWN0dXJlIGFuZCB0cmFpbmluZyBhcmUgcmVx
dWlyZWQgdG8gYmUgcHV0IGluIHBsYWNlLg0KDQpUaGUgQS1sYWJlbCByZXF1aXJlbWVudCBkb2Vz
IHJlcXVpcmUgdGhhdCBhIE1UQSB0aGF0IHVzZXMgYQ0KdW5pdmVyc2FsICJuYW1lIHJlc29sdXRp
b24iIEFQSSAodGhlIHByb2JsZW0gZGlzY3Vzc2VkIGluDQpkcmFmdC1pYWItaWRuLWVuY29kaW5n
KSBwZXJmb3JtIGEgVS1sYWJlbCB0byBBLWxhYmVsIGNvbnZlcnNpb24sDQpidXQgdGhlIG1haW4g
aXNzdWUgaW4gZHJhZnQtaWFiLWlkbi1lbmNvZGluZyByZWFsbHkgZG9lc24ndA0KYXBwbHkgaGVy
ZTogdGhpbmsgb2YgdGhlIHJlcXVpcmVtZW50IGFzIGFwcGx5aW5nIHRvDQoNCiAgIFJlY2VpdmVk
OiBmcm9tIC4uLiB3aXRoIHNtdHAgLi4uDQoNCm9yIHdpdGggYW55IG9mIHRoZSBvdGhlciAid2l0
aCIga2V5d29yZHMgc3BlY2lmaWVkIGluIDUzMzZiaXMgb3INCnRoZSBJQU5BIHJlZ2lzdHJ5LiAg
IndpdGggc210cCIgaXMgcHJldHR5IG11Y2ggZGVmaW5lZCBpbiA1MzIxDQphcyBydW5uaW5nIG92
ZXIgVENQLiAgSWYgb25lIGhhZA0KDQogICBSZWNlaXZlZDogZnJvbSAuLi4gd2l0aCBQcm9wcmll
dGFyeS1FbWFpbC1UcmFuc3BvcnQtWFlaIC4uLg0KDQp0aGVuIG9uZSB3b3VsZCBiZSBmYXIgZW5v
dWdoIG91dHNpZGUgb2YgdGhlIGNvbWJpbmF0aW9uIG9mIDUzMjENCmFuZCA1MzM2YmlzIHRoYXQs
IGlmIGEgbmFtZSAoZG9tYWluIG9yIG90aGVyd2lzZSkgaXMgZXhwcmVzc2VkDQppbiBVVEYtOCAo
b3IgVVRGLTE2IGZvciB0aGF0IG1hdHRlciksIHRoZSBpbXBsZW1lbnRhdGlvbiB3b3VsZA0Kbm90
IGJlIHNpZ25pZmljYW50bHkgbW9yZSBvdXRzaWRlIHRoZSBzcGVjcy4NCg0KYmVzdCwNCiAgICAg
am9obg==

From klensin@jck.com  Fri Dec 24 21:51: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 0F8103A68E0 for <ima@core3.amsl.com>; Fri, 24 Dec 2010 21:51:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level: 
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[AWL=-0.752, BAYES_00=-2.599, SARE_FWDLOOK=1.666]
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 pjbZ-IKp6ceo for <ima@core3.amsl.com>; Fri, 24 Dec 2010 21:51:07 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 733053A69A9 for <ima@ietf.org>; Fri, 24 Dec 2010 21:51:07 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWN42-000OZK-Ev; Sat, 25 Dec 2010 00:53:10 -0500
Date: Sat, 25 Dec 2010 00:53:09 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <9CA8154030BEF063FF6F6D9C@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B40E87@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A10C65AD6@TK5EX14MBXC133.redmond.corp.microsoft.com> ,<5B92D222E006F894AE0307EC@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A11B40E87@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] 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, 25 Dec 2010 05:51:09 -0000

--On Saturday, December 25, 2010 04:39 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> Thanks, I hadn't seen a reply yet.  I understand, but this is
> the kind of "leaking" that makes IDN horrible to interoperate
> with.  Sure, the tools may not be Unicode aware, but they also
> may not be Punycode aware, meaning that someone has to figure
> out how to translate it.
> 
> IMO the headers are EAI, so these should only happen on an EAI
> aware system, in which case the tools should be updated :)
> Eg: something could be broken no matter what, so I'd prefer it
> was broken in a forward-looking way, then at least when the
> tools got fixed they wouldn't always have to have the punycode
> hack.
> 
> And this doesn't help much for other data in the header, or
> local parts.

Yes.  Added to my notes, we now have a pretty good summary of
the tradeoffs.  In fairness, I should also note that we made
that decision at a time when in-transit downgrade was still in
the system and avoiding having to downgrade Received headers was
another important consideration.

While I still think the decision we made was the right one, this
is one of many decisions that makes me wish we could declare and
enforce a flag day and just stop trying to game out the
implications of different transition strategies.  While I'm
wishing for the impossible, I'd suggest that Jan 1 2011 would be
a good candidate :-(

     john






From klensin@jck.com  Sat Dec 25 12:18:12 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 DEA0D3A696B; Sat, 25 Dec 2010 12:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.213
X-Spam-Level: 
X-Spam-Status: No, score=-2.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 icONbDRawxMl; Sat, 25 Dec 2010 12:18:11 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 549B13A6863; Sat, 25 Dec 2010 12:18:10 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWab2-000FG7-9B; Sat, 25 Dec 2010 15:20:08 -0500
Date: Sat, 25 Dec 2010 15:20:07 -0500
From: John C Klensin <klensin@jck.com>
To: Ned Freed <NED+eai@mauve.mrochek.com>
Message-ID: <227C2506194609988B81BE4F@PST.JCK.COM>
In-Reply-To: <01NVQAP0UQRU007CHU@mauve.mrochek.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.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: Alexey.Melnikov@isode.com, draft-ietf-eai-rfc5336bis@tools.ietf.org, ima@ietf.org, apps-discuss@ietf.org
Subject: [EAI] RFC5336 and VRFY/EXPN (was: Re: apps-team review of draft-ietf-eai-rfc5336bis)
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, 25 Dec 2010 20:18:13 -0000

(writing as a personal opinion, not speaking for the WG.  Shawn
and others have already addressed parts of this, but, for
completeness...)

--On Wednesday, December 22, 2010 18:01 -0800 Ned Freed
<NED+eai@mauve.mrochek.com> wrote:

>...
> (1) 3.1 item 4 and 3.6.4.2 add an optional UTF8REPLY parameter
> to VRFY and     EXPN. They do this by redefining the syntax to
> be:
> 
>     vrfy = "VRFY" SP ( uLocal-part / uMailbox )
>                      [ SP "UTF8REPLY" ] CRLF
> 
>     expn = "EXPN" SP ( uLocal-part / uMailbox )
>                      [ SP "UTF8REPLY" ] CRLF
> 
>     The original syntax for VRFY and EXPN given in RFC 5321 is:
> 
>     vrfy = "VRFY" SP String CRLF
>     expn = "EXPN" SP String CRLF
>     String = Atom / Quoted-string
>     Atom = 1*atext
> 
>     It's not immediately obvious, but the new syntax is in
> fact a superset of     the old. (uLocal-part subsumes
> local-part, which in turn allows atoms     and quoted
> strings.) However, this change does much more than hang a
> parameter on the command; for the first time an entire address
> is     permitted as an EXPN/VRFY argument. But no semantics
> are given for     this significant syntax expansion, nor does
> this expansion appear to be     within scope for EAI.
> 
>     A more reasonable syntax would be:
> 
>     vrfy = "VRFY" SP uString [ SP "UTF8REPLY" ] CRLF
> 
>     expn = "EXPN" SP uString [ SP "UTF8REPLY" ] CRLF
> 
>     uString = uAtom / uQuoted-string

Yes.  I don't think the above mess was intentional.   In
fairness to the authors, the ABNF has been changed too many
times by too many people and I think the situation above is a
side-effect.   As you point out, the syntax changes may not be
adequate (see below).

>     But this now fails along a different dimension: When
> adding a parameter     capability to a command, it should be
> done in a general way, so that any     future extensions can
> build on a cleanly specified foundation. Like so:
> 
>     vrfy = "VRFY" SP uString [ SP vrfy-parameters ] CRLF
>     vrfy-parameters = esmtp-param *(SP esmtp-param)
> 
>     expn = "EXPN" SP uString [ SP expn-parameters ] CRLF
>     expn-parameters = esmtp-param *(SP esmtp-param)
> 
>     uString = uAtom / uQuoted-string
> 
>     Of course this will add 555 as a possible response to
> VRFY/EXPN, and that needs to be noted.

Right. See below.

In addition, one must have a session for which mail transactions
are permitted (i.e., EHLO must have been sent) in order to use
any parameters at all.  RFC 5321, Section 4.1.4, explicitly
permits sending VRFY or EXPN without first having EHLO in the
session.  So there is another implicit requirement in all of
this that should almost certainly be made explicit.   (I think
this is the topic about handshaking that Dave and Shawn have
been circling around, but I'm not sure).

 
> (2) In response to Dave's critique/query about why the
> parameter on VRFY and     EXPN is needed, it's because these
> commands can appear outside of a     transaction and thus
> there's not necessarily an indication that the client     is
> prepared to accept UTF-8 responses. 

Yes, exactly.

> However, this brings up
> another     issue, which is that a server that supports this
> extension needs a way     to tell a client that doesn't that
> it cannot return a proper response     to VRFY/EXPN without
> that parameter being specified. A new SMTP error     status is
> needed, but the document only defines an extended status
> for this purpose; it doesn't specify a regular status code to
> use.

If we go down this path, the WG clearly needs to reexamine
whether such a code is necessary.  I think you have made a
persuasive case, but I can't speak for the WG.

Indeed, this has all gotten sufficiently complex that I think
perhaps the WG should reexamine its decision to handle the "VRFY
and EXPN with possible non-ASCII responses" situation by
parameterizing those commands rather than introducing new
commands, say VRF8 and EXP8.  IIR, the WG did consider that
alternative (long ago) and conclude that adding a parameter was
the more straightforward option.  But, perhaps, given the
various complexities that have emerged, that was not the right
decision.  With other commands, such as MAIL and RCPT, we've
already got a history of parameters and the base (821/5321)
syntax is very clearly delimited.  By contrast, I certainly
remember seeing VRFY followed by unquoted strings with blanks in
them in the wild (e.g., arrangements like 
    VRFY Ned Freed
) and some servers tolerating them in the name of robustness or
in memory of 821, which had
    VRFY <SP> <string> <CRLF>
    <string> ::= <char> | <char> <string>
    <char> ::= <c> | "\" <x>
    <c> ::= any one of the 128 ASCII characters, 
        but not any <special> or <SP>
    <x> ::= any one of the 128 ASCII characters
       (no exceptions)
which makes
    VRFY Dave\ Crocker
perfectly valid.    I don't know if similar examples still occur
and with what frequency, but...

In addition, if we handle EAI-extended VRFY and EXPN with
parameters, we end up in the odd situation in which the
no-parameter versions can be issued without mail session
initialization (the EHLO command) but the extended,
parameterized ones require a previously-initialized session.
The MAIL and RCPT commands dn't have an issue because they
require session initialization anyway.  That restriction on
extended VRFY and EXPN certainly works technically, but isn't
going to be the easiest thing to explain and might cause some
"interesting" behavior if implementations screw it up or
clients, having not sent EHLO, assume that they are talking with
legacy 821 servers.   By contrast, a rule that requires session
initialization prior to using a new command is a no-brainer to
specify and implement cleanly, with no excuses about, e.g.,
ancient legacy environments.

I would welcome your thoughts on this tradeoff between adding
new commands (whose syntax would be identical to 5321 VRFY/EXPN
but expanded to UTF-8 input and/or output) and the current
proposal for a parameterized multiple-case situation, presumably
fixed up more or less as you have suggested.

    john



From klensin@jck.com  Sun Dec 26 10:34:35 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 75A673A67B6 for <ima@core3.amsl.com>; Sun, 26 Dec 2010 10:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 Wq1XEBzRZOxr for <ima@core3.amsl.com>; Sun, 26 Dec 2010 10:34:34 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 707E83A67A3 for <ima@ietf.org>; Sun, 26 Dec 2010 10:34:33 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PWvSP-0007IG-F1; Sun, 26 Dec 2010 13:36:37 -0500
X-Vipre-Scanned: 004F62E0001DEB004F642D-TDI
Date: Sun, 26 Dec 2010 13:36:36 -0500
From: John C Klensin <klensin@jck.com>
To: John R Levine <johnl@taugh.com>
Message-ID: <111F71B3BA3F6522BDBF00C0@[192.168.1.128]>
In-Reply-To: <alpine.BSF.2.00.1012242201240.97546@joyce.lan>
References: <20101224184708.73906.qmail@joyce.lan> <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM> <alpine.BSF.2.00.1012241545410.94715@joyce.lan> <E5F66B04416DC1DA0EED6F75@PST.JCK.COM> <alpine.BSF.2.00.1012242201240.97546@joyce.lan>
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] UTF-8 in a Subject header field?
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, 26 Dec 2010 18:34:35 -0000

--On Friday, December 24, 2010 10:05 PM -0500 John R Levine
<johnl@taugh.com> wrote:

>>> With that in mind, I'd suggest that the EAI documents would
>>> benefit by being shorter and more brutal: anywhere you can
>>> use arbitrary ASCII you can now use arbitrary UTF-8.  All
>>> other encodings are deprecated, no charsets other than UTF8
>>> in top-level MIME parts, A-labels in addresses will cause a
>>> razzberry to come out of your speaker.  If you want to send
>>> mail to somebody who doesn't grok EAI, it's your MUA's job to
>>> try to create a mail-classic version.
>> 
>> Some variations on this theme were considered at length by the
>> WG, probably circa 2006. ...
> 
> But I don't see much difference from what the docs say now.
> If you're sending EAI, you can put UTF-8 in the envelope and
> pretty much anywhere in the headers.  If you're not, you
> can't, give or take RFC2045 encoded strings and A-labels.

No razzberries for A-labels, no deprecation of content-type
charsets other than UTF-8 (probably a good idea at some point,
but out of scope).  But certainly, if you want to send something
with explicit non-ASCII (i.e., UTF-8 with codepoints about
U+007F) in the headers, or with explicit non-ASCII in the
envelope, without the extension being offered in the next hop,
then the sender has to cope.  And "cope" is limited to:

	(1) For the MUA, do whatever it is that MUAs might do,
	taking advantage of using whatever out-of-band
	information (such as alternate ASCII addresses or
	transliteration rather than encodings)might be available
	(and, I trust obviously, not using or depending on any
	out-of-band information that isn't available).
	
	(2) For the MSA, act on behalf of the MUA as needed and
	previously negotiated between the two or with the sender
	(that negotiation can be completely out of band, rather
	than a matter of protocols), again utilizing whatever
	out-of-band information is available and whose use is
	authorized by the sender.
	
	(3) For a gateway, do whatever it is that gateways might
	do.
	
	(4) For anything else, reject or bounce the message as
	undeliverable.

I assume the WG would appreciate advice as to whether things
really need to be spelled out in that much detail -- certainly
some of it is a rephrasing of rules that already exist in RFC
5321 about who can change what -- and, if so, where it should go.

      john





From johnl@taugh.com  Sun Dec 26 18:06:34 2010
Return-Path: <johnl@taugh.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 EEBF43A6832 for <ima@core3.amsl.com>; Sun, 26 Dec 2010 18:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.061
X-Spam-Level: 
X-Spam-Status: No, score=-11.061 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_ENC_UTF8=0.152]
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 xPMc9igRIl8d for <ima@core3.amsl.com>; Sun, 26 Dec 2010 18:06:33 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 877E53A67D8 for <ima@ietf.org>; Sun, 26 Dec 2010 18:06:32 -0800 (PST)
Received: (qmail 39835 invoked from network); 27 Dec 2010 02:08:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=9b9a.4d17f524.k1012; i=johnl@submit.iecc.com; bh=o+SkTvJNx7Rwa+uB1HxSvwPzNtVSoCJS6yp7QYHATjA=; b=oGGEHhTCrjAKPJlx8peOEz179MbexeNulE3E1r42+KV/J9ekhk/swQrOxUpHT+AXaHThgjGJJfqShYnEqYdssY6SfyuhrKYJ/eU9K/MyyD2aDYxqyeF85FT/woHUVSmW7UhEHq+ZZm5GbVJr/uMnB7SibbNCY9F3QVToYSGIYTE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=9b9a.4d17f524.k1012; olt=johnl@submit.iecc.com; bh=o+SkTvJNx7Rwa+uB1HxSvwPzNtVSoCJS6yp7QYHATjA=; b=J43f+AuxPGn+zDQal7MPDUEKqs7k7b1xlvBF9NEbzov3lpDosM0wRlEspSYELiLOwkTByff0nULlq2mSbs+MNimcOSZY8ARhYO2YR1CqXaI/Vag1da000Q9+kPNdPUQcV5FiM6C0Rpv7gP+ZWlIGVknKOiSVmJamYjR1mNEfR2s=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Dec 2010 02:08:14 -0000
Date: 26 Dec 2010 21:08:37 -0500
Message-ID: <alpine.BSF.2.00.1012262104500.12454@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <klensin@jck.com>
In-Reply-To: <111F71B3BA3F6522BDBF00C0@[192.168.1.128]>
References: <20101224184708.73906.qmail@joyce.lan> <3E294E95ECB4BB6C80AE5E26@PST.JCK.COM> <alpine.BSF.2.00.1012241545410.94715@joyce.lan> <E5F66B04416DC1DA0EED6F75@PST.JCK.COM> <alpine.BSF.2.00.1012242201240.97546@joyce.lan> <111F71B3BA3F6522BDBF00C0@[192.168.1.128]>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ima@ietf.org
Subject: Re: [EAI] UTF-8 in a Subject header field?
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, 27 Dec 2010 02:06:35 -0000

>> But I don't see much difference from what the docs say now. ...

> No razzberries for A-labels, no deprecation of content-type
> charsets other than UTF-8 (probably a good idea at some point,
> but out of scope).

True.

> without the extension being offered in the next hop,
> then the sender has to cope.  And "cope" is limited to:

Here's where brutality could be helpful.  Rather than calling out possible 
ways to sneak an EAI message through other than EAI channels, just say 
bounce unless you happen to have a non-standard way to get the message to 
the recipient.  And perhaps leave out the last part of the sentence, since 
you can always do whatever non-standard extensions you want.

Are there actually MSAs that downgrade EAI messages?  I have no idea, 
never having had to address this particular problem.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From al@akc.com  Sun Dec 26 20:58:37 2010
Return-Path: <al@akc.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 F32773A6848; Sun, 26 Dec 2010 20:58:36 -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 zwFKJzrJ4FkN; Sun, 26 Dec 2010 20:58:35 -0800 (PST)
Received: from imail.akc.com (mail.akc.com [192.188.192.3]) by core3.amsl.com (Postfix) with ESMTP id 35BC93A6832; Sun, 26 Dec 2010 20:58:34 -0800 (PST)
Received: from upstairs (upstairs.akc.com [64.253.39.242]) by imail.akc.com with SMTP; Mon, 27 Dec 2010 00:00:13 -0500
Message-ID: <3F5293BF906846C89013734B3D6262D9@upstairs>
From: "Al Costanzo" <al@akc.com>
To: "Ned Freed" <ned.freed@mrochek.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it><01NVQAP0UQRU007CHU@mauve.mrochek.com><227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com>
Date: Mon, 27 Dec 2010 00:00:09 -0500
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.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-Mailman-Approved-At: Sun, 26 Dec 2010 23:49:52 -0800
Cc: ima@ietf.org, apps-discuss@ietf.org
Subject: Re: [EAI] [apps-discuss] RFC5336 and VRFY/EXPN (was: Re: apps-team review of draft-ietf-eai-rfc5336bis)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Al Costanzo <al@akc.com>
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, 27 Dec 2010 04:58:37 -0000

> OTOH, a lot of servers back in the days prior to RFC 2821 didn't support 
> the
> 821 thing of allowing literal spances with a \ and no enclosing quotes. So 
> this
> never could be said to have interoperated. And I think the time has come 
> to
> abandon it (although I note that if you really want to continue supporting 
> it,
> the added parameter doesn't prevent you from doing so).
>

Ned,

If my memory servers me, (and it may not),

There were good reasons why VRFY supported this.  I dont know if any are 
valid anymore but one idea was that you could send the persons name, not the 
email address, to find out if that person had an email address on that 
system.

Was this not the reason Ned to allow blanks (whitespace) and unquoted 
strings?  If you remove this from the spec, this functionality would be 
lost, I don't really see a reason to lose something that works.

>> RFC 5321, Section 4.1.4, explicitly
>> permits sending VRFY or EXPN without first having EHLO in the
>> session.  So there is another implicit requirement in all of
>> this that should almost certainly be made explicit.

I do not remember VRFY command requiring the EHELO, there are a number of 
mailing list verifiers that do not send the EHELO first. Verifiers, since 
they do not actually send email, usually dont send the EHELO first. (our 
application does) and I think requiring the EHELO first as part of a 
handshake it the proper way to do this.

Only my humble opinon.

-Al Costanzo





----- Original Message ----- 
From: "Ned Freed" <ned.freed@mrochek.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <Alexey.Melnikov@isode.com>; <apps-discuss@ietf.org>; "Ned Freed" 
<NED+eai@mauve.mrochek.com>; <ima@ietf.org>; 
<draft-ietf-eai-rfc5336bis@tools.ietf.org>
Sent: Sunday, December 26, 2010 5:53 PM
Subject: Re: [apps-discuss] [EAI] RFC5336 and VRFY/EXPN (was: Re: apps-team 
review of draft-ietf-eai-rfc5336bis)


>> In addition, one must have a session for which mail transactions
>> are permitted (i.e., EHLO must have been sent) in order to use
>> any parameters at all.
>
> You certainly need to send an EHLO and process the result to find out what
> extensions are allowed - guessing what combination of extensions will work 
> most
> certainly is not a sound operational policy. And implementations are 
> certainly
> free to only offer the extensions that have been returned in an EHLO 
> repsonse.
>
> That said, I don't see an actual requirement in section 2.2 stating that 
> EHLO
> must be issued before any parameters can be used. (Maybe it's somewhere 
> else,
> but a cursory search didn't find it.) Our MTA certainly doesn't enforce 
> this
> and AFAIK neither does sendmail, PostFix, Apache James, or qmail. (Exim, 
> OTOH,
> appears to.)
>
>> RFC 5321, Section 4.1.4, explicitly
>> permits sending VRFY or EXPN without first having EHLO in the
>> session.  So there is another implicit requirement in all of
>> this that should almost certainly be made explicit.
>
> There certainly should be a note saying that you need to issue an EHLO
> and check the response before attaching any parameters to VRFY/EXPN. I 
> don't
> think a requirement that parameters not be accepted before an EHLO
> has been issued is needed.
>
>> (I think
>> this is the topic about handshaking that Dave and Shawn have
>> been circling around, but I'm not sure).
>
> It's part of it, I think.
>
>> > However, this brings up
>> > another     issue, which is that a server that supports this
>> > extension needs a way     to tell a client that doesn't that
>> > it cannot return a proper response     to VRFY/EXPN without
>> > that parameter being specified. A new SMTP error     status is
>> > needed, but the document only defines an extended status
>> > for this purpose; it doesn't specify a regular status code to
>> > use.
>
>> If we go down this path, the WG clearly needs to reexamine
>> whether such a code is necessary.  I think you have made a
>> persuasive case, but I can't speak for the WG.
>
> It doesn't have to be a new code. OTOH, it needs to be a code that 
> EXPN/VRFY
> don't return for other purposes, and I think if you look at the list of
> available codes a new code is needed.
>
>> Indeed, this has all gotten sufficiently complex that I think
>> perhaps the WG should reexamine its decision to handle the "VRFY
>> and EXPN with possible non-ASCII responses" situation by
>> parameterizing those commands rather than introducing new
>> commands, say VRF8 and EXP8.  IIR, the WG did consider that
>> alternative (long ago) and conclude that adding a parameter was
>> the more straightforward option. But, perhaps, given the
>> various complexities that have emerged, that was not the right
>> decision.
>
> I considered suggesting new commands, but given the need to specify
> syntax for the new commands I don't see this as any simplier
> specification-wise. In terms of implementation, a new command is actually
> a somewhat more complex - the code changes are less localized, and I 
> suspect
> other implementations will be comparable in this regard.
>
> But the minute you need some other variant on EXPN and VRFY, the alternate
> command appraoch becomes the far more complex way to do it. Now, we 
> haven't had
> a specification come along that needed additional EXPN/VRFY parameters 
> before
> this one, but these things have a way of showing up once you open the door 
> and
> get people thinking about them. So I'm strongly inclined to stick with the
> parameter approach.
>
>> With other commands, such as MAIL and RCPT, we've
>> already got a history of parameters and the base (821/5321)
>> syntax is very clearly delimited.  By contrast, I certainly
>> remember seeing VRFY followed by unquoted strings with blanks in
>> them in the wild (e.g., arrangements like
>>     VRFY Ned Freed
>> ) and some servers tolerating them in the name of robustness or
>> in memory of 821, which had
>>     VRFY <SP> <string> <CRLF>
>>     <string> ::= <char> | <char> <string>
>>     <char> ::= <c> | "\" <x>
>>     <c> ::= any one of the 128 ASCII characters,
>>         but not any <special> or <SP>
>>     <x> ::= any one of the 128 ASCII characters
>>        (no exceptions)
>> which makes
>>     VRFY Dave\ Crocker
>> perfectly valid.    I don't know if similar examples still occur
>> and with what frequency, but...
>
> OTOH, a lot of servers back in the days prior to RFC 2821 didn't support 
> the
> 821 thing of allowing literal spances with a \ and no enclosing quotes. So 
> this
> never could be said to have interoperated. And I think the time has come 
> to
> abandon it (although I note that if you really want to continue supporting 
> it,
> the added parameter doesn't prevent you from doing so).
>
> Ned
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
> 



From chl@clerew.man.ac.uk  Mon Dec 27 04:22:46 2010
Return-Path: <chl@clerew.man.ac.uk>
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 A1BA13A688B for <ima@core3.amsl.com>; Mon, 27 Dec 2010 04:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.45
X-Spam-Level: 
X-Spam-Status: No, score=-4.45 tagged_above=-999 required=5 tests=[AWL=-0.851,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 yk2cAFw3dBmK for <ima@core3.amsl.com>; Mon, 27 Dec 2010 04:22:45 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id C59423A672F for <ima@ietf.org>; Mon, 27 Dec 2010 04:22:43 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id EDA0D21F0D for <ima@ietf.org>; Mon, 27 Dec 2010 12:24:46 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 27 Dec 2010 12:24:46 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBRCOjmm019428 for <ima@ietf.org>; Mon, 27 Dec 2010 12:24:46 GMT
Date: Mon, 27 Dec 2010 12:24:45 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
In-Reply-To: <01NVRM7BIKTM007CHU@mauve.mrochek.com>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d18858e.14db7-623-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 27 Dec 2010 12:22:46 -0000

On Fri, 24 Dec 2010 00:33:32 -0000, Ned Freed <ned.freed@mrochek.com>  
wrote:

>> On Thu, 23 Dec 2010 02:01:15 -0000, Ned Freed  
>> <NED+eai@mauve.mrochek.com>
>> wrote:
>
>> > Now for the specifics:
>> >
>> > (0) I cannot emphasize strongly enough how important it is to have a
>> >     UTF8SMTP sort of parameter on the MAIL FROM to indicate that a
>> > message
>> >     employing this extension is being submitted/relayed/delivered.  
>> This
>> > is
>> >     especially important in the relay case - we do not want to require
>> >     that relays grub through every message they receive looking for
>> > possible
>> >     utf-8 so they can carry the negotiation of this extension forward,
>> > but
>> >     that's exactly what the present proposal forces them to do.
>
>> Well there was a header for that purpose in the early days of the WG  
>> but,
>
> A header doesn't work for this purpose. It needs to be announced in the
> envelope. Just as one example, this allows messages sent to an address
> that is known not to be able to support utf-8 addresses to be rejected
> immediately.

Ah! the WG considered a header for this purpose, but not a specific  
announcement in the envelope. So we ought to look at that now.

However, I do not quite see the necessity for it. If some MTA announces  
the capability UTF8SMTP, then it is declaring its willingness to accept  
messages destined for utf-8 addresses and to do the "right thing" with any  
problems that might arise (such as generating a bounce if some MTA further  
down the chain finds a problem). Essentially the same as current MTAs do  
with ASCII messages that turn out to be undeliverable.

If some client tries to send such a message without first checking that  
the UTF8SMTP capability has been advertised, then it is in breach of our  
proposal, and is just like people who try to "just send 8-bits" at the  
moment - if they strike lucky it might work, but there is no guarantee.

So I think the only situation where a "this message uses UTF-8 in headers"  
parameter in the MAIL FROM would confer any actual benefit is when some  
particular message within some environment where UTF-8 is the  norm just  
happens to be in pure ASCII (I am on a visit to China, but I am just  
sending an ASCII-only message home). In that case, the _absence_ of that  
parameter in the MAIL FROM would indicate to the MTA that it could happliy  
forward the message to other MTAs that did not advertise UTF8SMTP.

So it would be up to originating MUA (or maybe to submission servers) to  
ensure that the said parameter was provided, or not, according to the  
content of the particular message, and for all subsequent agents to  
propagate that parameter as received when forwarding it on.

But note that introducing this parameter now whould create problems for  
those who have already implemented the experimental proposal without such  
a parameter. That should not be a show stopper, but that transition needs  
some thought.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From chl@clerew.man.ac.uk  Mon Dec 27 04:34:47 2010
Return-Path: <chl@clerew.man.ac.uk>
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 34D1C3A67F0 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 04:34:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.329
X-Spam-Level: 
X-Spam-Status: No, score=-4.329 tagged_above=-999 required=5 tests=[AWL=-0.730, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 LMeMuSPX565Y for <ima@core3.amsl.com>; Mon, 27 Dec 2010 04:34:46 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id AB09A3A672F for <ima@ietf.org>; Mon, 27 Dec 2010 04:34:26 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 2A74D21ECE for <ima@ietf.org>; Mon, 27 Dec 2010 12:36:30 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 27 Dec 2010 12:36:30 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBRCaT4w020134 for <ima@ietf.org>; Mon, 27 Dec 2010 12:36:30 GMT
Date: Mon, 27 Dec 2010 12:36:29 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1394CD.5060509@dcrocker.net>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vodha3k56hl8nm@clerew.man.ac.uk>
In-Reply-To: <4D1394CD.5060509@dcrocker.net>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d18884e.3773-7cec-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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: Mon, 27 Dec 2010 12:34:47 -0000

On Thu, 23 Dec 2010 18:28:29 -0000, Dave CROCKER <dhc2@dcrocker.net> wrote:

> That is, a "handshake" is a synchronization process for changing a  
> condition. In this case, it moves an SMTP session from the condition of  
> supporting network ASCII, for basic data representation, into the  
> condition of supporting UTF-8.
>
> Synchronization of such a change requires a /mutual/ exchange of  
> coordination information, so that each participant can agree to the  
> change.  This requires a minimum of one notification in /each  
> direction/.  (More than one is primarily useful to cover certain types  
> of failure conditions that occur in networks; hence TCP uses a three-way  
> handshake.)
>
> The EAI SMTP extension only has an announcement of UTF-8 capability by  
> the server.  It has no corresponding agreement announced by the SMTP  
> client that it will participate in support of UTF-8.

But I don't think that should be necessary. A client that is capable of  
handling these new UTF-8 messages is presumably aware of its own  
capability. So if it sees that the server advertises UTF8SMTP, it should  
be able to just start sending UTF-8 without further ado. There is no need  
to inform the server that it is willing to receive responses appropriate  
to that method of operation - the server can assume that any client  
sending such messages is uft-8 enabled (ignoring the case of broken  
clients that "just send 8 bits"). So a full handshake in the usual sense  
is not necessary.

In fact, as I have just written in my reply to Ned, the interesting case  
is when the client might wish to say "this message does NOT use UTF-8 so  
you can send it on to any destination".

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From klensin@jck.com  Mon Dec 27 08:20: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 1B4943A689F for <ima@core3.amsl.com>; Mon, 27 Dec 2010 08:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 L4eh3pM6uGpr for <ima@core3.amsl.com>; Mon, 27 Dec 2010 08:20:55 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 42E9F3A68A2 for <ima@ietf.org>; Mon, 27 Dec 2010 08:20:54 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXFqT-000M0Y-Pd; Mon, 27 Dec 2010 11:22:50 -0500
X-Vipre-Scanned: 04FB4397001DEB04FB44E4-TDI
Date: Mon, 27 Dec 2010 11:22:48 -0500
From: John C Klensin <klensin@jck.com>
To: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Message-ID: <F5827C761F7675FB24E889B1@[192.168.1.128]>
In-Reply-To: <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
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: Ned Freed <ned.freed@mrochek.com>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 27 Dec 2010 16:20:58 -0000

--On Monday, December 27, 2010 12:24 PM +0000 Charles Lindsey
<chl@clerew.man.ac.uk> wrote:

>> A header doesn't work for this purpose. It needs to be
>> announced in the envelope. Just as one example, this allows
>> messages sent to an address that is known not to be able to
>> support utf-8 addresses to be rejected immediately.
>=20
> Ah! the WG considered a header for this purpose, but not a
> specific announcement in the envelope. So we ought to look at
> that now.

Actually, the WG did consider an envelope announcement at one
point.  But that is not particularly relevant at this stage.
Several of the reviewers have made a strong argument for an
envelope parameter, so we need to consider whether, in the light
of those arguments, we want to change our collective minds and
add such a parameter.

> However, I do not quite see the necessity for it. If some MTA
> announces the capability UTF8SMTP, then it is declaring its
> willingness to accept messages destined for utf-8 addresses
> and to do the "right thing" with any problems that might arise
> (such as generating a bounce if some MTA further down the
> chain finds a problem). Essentially the same as current MTAs
> do with ASCII messages that turn out to be undeliverable.
>=20
> If some client tries to send such a message without first
> checking that the UTF8SMTP capability has been advertised,
> then it is in breach of our proposal, and is just like people
> who try to "just send 8-bits" at the moment - if they strike
> lucky it might work, but there is no guarantee.

If I recall, that was more or less the WG's position wrt both
the header and envelope suggestions.

> So I think the only situation where a "this message uses UTF-8
> in headers" parameter in the MAIL FROM would confer any actual
> benefit is when some particular message within some
> environment where UTF-8 is the  norm just happens to be in
> pure ASCII (I am on a visit to China, but I am just sending an
> ASCII-only message home). In that case, the _absence_ of that
> parameter in the MAIL FROM would indicate to the MTA that it
> could happliy forward the message to other MTAs that did not
> advertise UTF8SMTP.
>=20
> So it would be up to originating MUA (or maybe to submission
> servers) to ensure that the said parameter was provided, or
> not, according to the content of the particular message, and
> for all subsequent agents to propagate that parameter as
> received when forwarding it on.
>=20
> But note that introducing this parameter now whould create
> problems for those who have already implemented the
> experimental proposal without such a parameter. That should
> not be a show stopper, but that transition needs some thought.

I think this last is a non-issue: precisely the reason we agreed
to change the ESMTP announcement keyword was to protect new,
standards-conforming, implementations (and to delay assigning
that keyword until after we were sure the standards-track specs
were stable) from different behavior in experimental
implementations. =20

Advertise new EHLO keyword; get new behavior (or no EAI).
Advertise old/experimental EHLO keyword and one is on one's own.
Oddly, another argument for adding the MAIL command client
announcement is that it would tell a server who had chosen to
advertise both keywords what was expected.  I would hope that,
instead, we would see no such servers (as far as I know, none of
the experimental implementations have been released into the
wild) but, if folks decided to do that to support some sort of
transition requirement, a MAIL from keyword that would imply,
among other things, "don't try to apply RFC 5504 downgrading",
might be beneficial.

     john

>=20
> =
--Charles=C2=A0H.=C2=A0Lindsey=C2=A0---------At=C2=A0Home,=C2=A0d=
oing=C2=A0my=C2=A0own=C2=A0th
> ing------------------------
> Tel:=C2=A0+44=C2=A0161=C2=A0436=C2=A06131=C2=A0
> =C2=A0=C2=A0=C2=A0Web:=C2=A0http://www.cs.man.ac.uk/~chl
> =
Email:=C2=A0chl@clerew.man.ac.uk=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0Snail:=C2=A05=C2=A0Clerewood=C2=A0
> Ave,=C2=A0CHEADLE,=C2=A0SK8=C2=A03JU,=C2=A0U.K.
> =
PGP:=C2=A02C15F1A9=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Fingerprint=
:=C2=A073=C2=A06D=C2=A0C2=C2=A051=C2=A093=C2=A0A0
> =
=C2=A001=C2=A0E7=C2=A065=C2=A0E8=C2=A064=C2=A07E=C2=A014=C2=A0A4=C2=
=A0AB=C2=A0A5
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima





From klensin@jck.com  Mon Dec 27 09:04:23 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 D0FB43A68BA for <ima@core3.amsl.com>; Mon, 27 Dec 2010 09:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 Uzj1wr3K6DSQ for <ima@core3.amsl.com>; Mon, 27 Dec 2010 09:04:23 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id CEC483A68B3 for <ima@ietf.org>; Mon, 27 Dec 2010 09:04:22 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXGWg-000MaI-Nf; Mon, 27 Dec 2010 12:06:26 -0500
X-Vipre-Scanned: 0523321F001DEB0523336C-TDI
Date: Mon, 27 Dec 2010 12:06:24 -0500
From: John C Klensin <klensin@jck.com>
To: Charles Lindsey <chl@clerew.man.ac.uk>
Message-ID: <78A98936A90EDFAE0C8EC560@[192.168.1.128]>
In-Reply-To: <op.vodha3k56hl8nm@clerew.man.ac.uk>
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1394CD.5060509@dcrocker.net> <op.vodha3k56hl8nm@clerew.man.ac.uk>
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 <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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: Mon, 27 Dec 2010 17:04:23 -0000

Charles,

I know that you (or your mail software) are inclined to strip
secondary addresses when you reply to mailing list posting.
Often that is useful.  But, for you and others with similar
habits/ systems please keep in mind that most of the reviewers
in this round are not on the IAM list -- I don't remember if Ned
is, Dave certainly is not unless he subscribed in the last week
or two.  If you have any doubt, please be sure you include the
address of whomever you are responding to in your reply.
Otherwise, the person to whom you are responding may not see
your response or, almost as bad, if you send him or her the
response separately, the WG may not see any discussion that
follows.

    thanks,
      john


--On Monday, December 27, 2010 12:36 PM +0000 Charles Lindsey
<chl@clerew.man.ac.uk> wrote:

> On Thu, 23 Dec 2010 18:28:29 -0000, Dave CROCKER
> <dhc2@dcrocker.net> wrote:
> 
>> That is, a "handshake" is a synchronization process for
>> changing a   condition. In this case, it moves an SMTP
>> session from the condition of   supporting network ASCII, for
>> basic data representation, into the   condition of supporting
>> UTF-8.
>> 
>> Synchronization of such a change requires a /mutual/ exchange
>> of   coordination information, so that each participant can
>> agree to the   change.  This requires a minimum of one
>> notification in /each   direction/.  (More than one is
>> primarily useful to cover certain types   of failure
>> conditions that occur in networks; hence TCP uses a three-way
>>  handshake.)
>> 
>> The EAI SMTP extension only has an announcement of UTF-8
>> capability by   the server.  It has no corresponding
>> agreement announced by the SMTP   client that it will
>> participate in support of UTF-8.
> 
> But I don't think that should be necessary. A client that is
> capable of handling these new UTF-8 messages is presumably
> aware of its own capability. So if it sees that the server
> advertises UTF8SMTP, it should be able to just start sending
> UTF-8 without further ado. There is no need to inform the
> server that it is willing to receive responses appropriate to
> that method of 





From klensin@jck.com  Mon Dec 27 10:47:08 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 10A2B3A67B4; Mon, 27 Dec 2010 10:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 LFz-GYd4n9EG; Mon, 27 Dec 2010 10:47:07 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 8EF5E3A67A7; Mon, 27 Dec 2010 10:47:06 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXI83-000Njv-Hx; Mon, 27 Dec 2010 13:49:07 -0500
X-Vipre-Scanned: 058133FB001DEB05813548-TDI
Date: Mon, 27 Dec 2010 13:49:06 -0500
From: John C Klensin <klensin@jck.com>
To: Al Costanzo <al@akc.com>, Ned Freed <ned.freed@mrochek.com>
Message-ID: <7C0660F7DFFE9C1990252217@[192.168.1.128]>
In-Reply-To: <3F5293BF906846C89013734B3D6262D9@upstairs>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com> <3F5293BF906846C89013734B3D6262D9@upstairs>
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, apps-discuss@ietf.org
Subject: Re: [EAI] [apps-discuss] RFC5336 and VRFY/EXPN (was: Re: apps-team	review of draft-ietf-eai-rfc5336bis)
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, 27 Dec 2010 18:47:08 -0000

--On Monday, December 27, 2010 12:00 AM -0500 Al Costanzo
<al@akc.com> wrote:

>...
> Ned,
> 
> If my memory servers me, (and it may not),
> 
> There were good reasons why VRFY supported this.  I dont know
> if any are valid anymore but one idea was that you could send
> the persons name, not the email address, to find out if that
> person had an email address on that system.

and what that address was, of course.

This was heavily used for a while with both VRFY and, separately
with finger, to get from name to email address.  The advantage
of the VRFY approach was that it would permit a user to enter an
address that might look like "John Klensin@example.com" at which
point the MUA would send 
   VRFY John Klensin
to the mail server at example.com, get back an address, and then
open a mail session.

Of course, Ned's observations about lousy support (with which I
agree) notwithstanding, the variation of 
   VRFY "John\ Klensin"
would have been fully 821-compliant.  I vaguely remember one MUA
that would send the first (escape-less) version and then send
the second if the reply from the first was "no 'John; here" or
"syntax error" rather than "no 'John Klensin' here".  The
heuristic is pretty trivial.

That use of VRFY became less popular as MUAs became more
separate from first-hop full service MTA (aka submission
servers) because that sort of use of VRFY pretty much requires
at least some SMTP capability (including domain name lookups,
coping with MXs, etc.) in the MUAs, ability to use port 25
connections from just about anywhere, etc.   I don't know
whether the usage is gone entirely, but it is certainly a lot
less common than it appeared to be many years ago.

> Was this not the reason Ned to allow blanks (whitespace) and
> unquoted strings?  If you remove this from the spec, this
> functionality would be lost, I don't really see a reason to
> lose something that works.

Especially if the clock could be turned back, one could allow
only the single form

  VRFY "John Klensin"

just getting rid of the bare, unquoted, backslash escape that
was permitted by 821 but that 5321 already excludes.

>>> RFC 5321, Section 4.1.4, explicitly
>>> permits sending VRFY or EXPN without first having EHLO in the
>>> session.  So there is another implicit requirement in all of
>>> this that should almost certainly be made explicit.
 
> I do not remember VRFY command requiring the EHELO, there are
> a number of mailing list verifiers that do not send the EHELO
> first.

It never has been a requirement although sending EHLO (or HELO)
first has always been harmless.  Either 5321 or 2821 simply made
it very clear that there was no such requirement.

> Verifiers, since they do not actually send email,
> usually dont send the EHELO first. (our application does) and
> I think requiring the EHELO first as part of a handshake it
> the proper way to do this.

That is one issue on the side of "new command".  If one now
decides to require EHLO first, then all existing uses of VRFY
without it (which conform perfectly well to 5321 and all of its
predecessors) become invalid,  That is pretty uncomfortable to
me.  By contrast, if one creates the new command, then, if the
response to EHLO includes some sort of EXTENDED-VRFY capability
(see below),  one could have:

	-- VRFY without EHLO as requesting the 5321 behavior
	(with or without non-conforming extensions or
	flexibility and with responses limited to ASCII).
	
	-- EHLO, then VRFY as requesting the 5321 behavior,
	identical to that above.  
	
	-- EHLO, then New-VRFY as requiring a strict Atom or
	Quoted-string optionally followed by a parameter list.

Note that, if the non-conforming client behavior we know is out
there is used, then 
    VRFY Costanzo 8BITREPLIES-OK
or equivalent could be interpreted by the server as either of
    VRFY "Constanzo\ 8BITREPLIES-OK"
or as coming with a parameter, or as a syntax error, in either
VRFY case.   Not really a good idea, IMO, and at least one
reason we have not permitted the use of extended parameters with
older SMTP commands with EHLO and capability permission.

Note too that the last paragraph of RFC 5321 Section 3.5.1 is,
in part and while not explicit, a caution against treating the
standard syntax too literally or narrowly. 

We could, in principle, do a completely new command without
involving the extension mechanism at all, thereby allowing
sending it before or without EHLO, but that strikes me as a
really scary idea.

> Only my humble opinon.

Only mine also -- I really don't have my mind made up about this
and am just trying to get the various arguments in front of the
WG.

     john

p.s. I agree with what I take to be at least a corollary to
Ned's remarks: having EAI create special-purpose commands that
are not very narrowly tied to i18n issues would be a bad idea.
If there is any perceived need for a new command, we ought to
define in a separate I-D, as (impossible keyword is deliberate
to clarify that this is not a proposal)
   NewVRFY String *(SP esmtp-param)
with String given only the 5321 interpretation, not the 821 one,
and then process that command through the SMTP list, etc.

If that appeals to anyone, I might generate a strawman just to
facilitate the discussion.



From dhc2@dcrocker.net  Mon Dec 27 11:00:59 2010
Return-Path: <dhc2@dcrocker.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 174D73A68CC for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.586
X-Spam-Level: 
X-Spam-Status: No, score=-6.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uMP2GE-ccU1C for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:00:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 230773A67B5 for <ima@ietf.org>; Mon, 27 Dec 2010 11:00:58 -0800 (PST)
Received: from [192.168.1.75] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBRJ2sLM000970 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2010 11:03:00 -0800
Message-ID: <4D18E2DC.9040903@dcrocker.net>
Date: Mon, 27 Dec 2010 11:02:52 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com>	<4D1394CD.5060509@dcrocker.net>	<op.vodha3k56hl8nm@clerew.man.ac.uk> <78A98936A90EDFAE0C8EC560@[192.168.1.128]>
In-Reply-To: <78A98936A90EDFAE0C8EC560@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 27 Dec 2010 11:03:00 -0800 (PST)
Cc: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 27 Dec 2010 19:00:59 -0000

On 12/27/2010 9:06 AM, John C Klensin wrote:
>  most of the reviewers
> in this round are not on the IAM list -- I don't remember if Ned
> is, Dave certainly is not


i am subscribed.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From klensin@jck.com  Mon Dec 27 11:15: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 135EB3A68BF for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 WnrzUPxRD6FV for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:15:42 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 2D82F3A67B5 for <ima@ietf.org>; Mon, 27 Dec 2010 11:15:42 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXIZk-000O4Q-1n; Mon, 27 Dec 2010 14:17:44 -0500
X-Vipre-Scanned: 059B650F001DEB059B665C-TDI
Date: Mon, 27 Dec 2010 14:17:43 -0500
From: John C Klensin <klensin@jck.com>
To: dcrocker@bbiw.net
Message-ID: <35137CA789085358D5369377@[192.168.1.128]>
In-Reply-To: <4D18E2DC.9040903@dcrocker.net>
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1394CD.5060509@dcrocker.net> <op.vodha3k56hl8nm@clerew.man.ac.uk> <78A98936A90EDFAE0C8EC560@[192.168.1.128]> <4D18E2DC.9040903@dcrocker.net>
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: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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: Mon, 27 Dec 2010 19:15:43 -0000

--On Monday, December 27, 2010 11:02 AM -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

> On 12/27/2010 9:06 AM, John C Klensin wrote:
>>  most of the reviewers
>> in this round are not on the IAM list -- I don't remember if
>> Ned is, Dave certainly is not
> 
> 
> i am subscribed.

Sorry for the duplicate then.  And thanks.

    john



From klensin@jck.com  Mon Dec 27 11:37:39 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 600A93A67BD for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 qvfjV9jKPzfO for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:37:35 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 2E82528B797 for <ima@ietf.org>; Mon, 27 Dec 2010 11:37:33 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXIut-000OMN-8S for ima@ietf.org; Mon, 27 Dec 2010 14:39:37 -0500
X-Vipre-Scanned: 05AF6702001DEB05AF684F-TDI
Date: Mon, 27 Dec 2010 14:39:31 -0500
From: John C Klensin <klensin@jck.com>
To: ima@ietf.org
Message-ID: <68655A9F86D4BE7ED933F8A6@[192.168.1.128]>
In-Reply-To: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>
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] Analysis of comments on 5336bis (was: Re: apps-team review of draft-ietf-eai-rfc5336bis)
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, 27 Dec 2010 19:37:39 -0000

Hi.

Long, careful, and thoughtful reviews deserve long --and I hope
careful and thoughtful-- responses.  This note attempts to
identify the main substantive points in the reviews and react
to them.  Some may consider it a special case of no good deed
going unpunished; if so, I'm sorry.

I'm sending the note separately to the EAI WG mailing list
(ima@ietf.org) and the Apps Discuss one.  I hope that we can
move discussion to the WG list.  Put differently, please do not
respond to this note on the apps-discuss list -- if anyone has
additional comments, please take them to the WG list.  My
apologies to those who will get it twice -- there seemed no
better way to avoid, or at least reduce, multiple threads of
discussions that were not visible to WG participants.

Writing only as a participant in the WG and co-author of the
"EAI framework" document, I have several comments on the
various Applications Area Review Team comments (my co-chair
helped a bit with part of this note but I'll take the blame
as needed).  To be certain we all start with the same
background assumptions, please remember that the original form
of the "EAI Framework" supported the Experimental version of
these protocols document was published in July 2007 as RFC
4952.  Its replacement, draft-ietf-eai-frmwrk-4952bis-10, is
more to the point today.  That draft is intended to be aligned
with the documents that are now under consideration (or to have
them aligned with it), has completed IETF Last Call, was
approved for publication by the IESG in late September, and has
been in the RFC Editor queue awaiting normative references to
the current set of documents and resolution of a naming issue
that the WG decided to leave until after the approval process
completed (more on that below).

Speaking very personally because I don't know whether the WG
participants will agree, I think these specifications are
important enough that I'd rather have them right than stand on
any sort of procedural argument.  However, I think the
community also needs to consider when, newly-discovered
showstoppers aside, it becomes too late to raise fundamental
design issues that were reviewed extensively by the WG prior to
forwarding the first-round documents to the IESG, went through
IETF Last Call in 2007 and 2008, have been implemented and
tested experimentally, and where the basic framework and
changes from the 2007-2008 specs were reviewed by the WG,
passed through IETF Last Call, and were approved by the IESG in
September of this year.

There are places in the comments below where I've tried to
summarize what I believe is WG opinion or WG consensus, but
even those remarks should be taken as personal opinion rather
than the formal opinion of the WG.  The WG has deliberately not
been given a preview of these notes and is seeing them for the
first time at the same time as reviewers and others.  I do hope
that some of the notes will act as a basis for discussion.

For convenience, I'm going to try to consider the review
comments by topic (there is some overlap among reviews) rather
than responding to each review comment separately.  When it
seems useful to identify particular comments, I've used the
first name of the author of the comments and the date of the
posting.  To avoid a hugely long note, this one is strictly
about 5336bis (the SMTP extensions); a separate note will be
posted about each of the other relevant documents.  Note that,
again speaking personally, I agree with some of the comments
even though WG consensus, as reflected in the current drafts,
does not.  

I have not commented on, or even listed, specific issues whose
consequences appear to be entirely editorial, even if the
editorial issues are quite broad.  I'll leave those comments to
the authors/editors (subject, as usual, to WG approval).  I
have also omitted most issues that seem to have been more than
adequately covered in mailing list discussions.

The balance of this note is about the reviews and on-list
comments about draft-ietf-eai-rfc5336bis.  It does not include
comments that appeared to be redundant unless listing different
versions seemed to add perspective or other information.  While
I've commented briefly on the VRFY and EXPN issues below, those
are being much better covered in the discussions between Dave
and Shawn, Ned's analysis, and the subsequent than I could do
or have attempted here.  Separate notes about the other reviews
will follow.


(1) Overview, scope, and summary:

Claudio Allocchio 2010-12-22 wrote: 

> The document specifies how to apply internationalization to
> some SMTP elements, and to some Header elements which
> depends from the SMTP elements.  However there seem to be a
> discrepancy from what the abstract states, and what is
> elaborated into the document details: the document also
> deals with quite a number of elements which involve
> bodyparts, and affect the whole email legacy system, and
> beyond, such as logs, traces, and wherever email addresses
> are used (certificates, etc.). This seems thus to go beyond
> what the summary states, even this fact is not explicitly
> discussed. It is unclear thus if this "update" of RFC5321
> and RFC5322 is only limited in scope or not. My reading of
> the document say it goes beyond, and implicitly affects also
> what is being transported into the email system.  This is
> thus a serious issue to be solved before the document can go
> to the Standard Track.

With the understanding that the abstract, and several other
editorial issues with the text, could certainly be improved,
please note that specifications for header fields that contain
trace-related information (and that are inserted by MTAs) have
appeared in all of RFCs 821/ 2821/ 5321.  The trend over time,
starting with some explicit DRUMS decisions, has been to move
more of that information into the x21 member of the pair rather
than having it split between x21 and x22.  So the choice with
this document is between updating information that appears in
5321 and creating a split between envelope and header
information that is different than the base email documents.
The WG concluded that tracking the organization and information
content of 5321 would be less confusing than trying to create a
new model.

By contrast, the information about certificates, etc., was
introduced into the predecessor of this document at the
insistence of the community and the IESG during Last Call on
RFC 5336.  We could take it out of here, possibly by reopening
the Framework document and inserting additional "other
consequences for email and the Internet" sections there.  FWIW,
my personal opinion is that doing so would not add
significantly to either document comprehensibility or protocol
quality, but that is a matter for WG and community consensus.


Dave Crocker 2010-12-22 wrote:

> * Beyond <encoded-word> -- The work, here, appears to have
> two goals. One is to add support for Unicode in a
> <local-part>; that is, support for internationalized
> addresses.  However note that <encoded-word> and <A-label>
> already accomplish this in a way that is transparent to the
> existing email infrastructure; only the end-systems need to
> understand it. 

When the discussions that led to the establishment of the EAI
WG started, the goal was seen as expanding the syntax of
<local-part>, as you suggest.  It turns out that doing that is
not really feasible, at least without leading to horrible
kludges, so the WG was chartered (now four or five years ago)
to extend header fields as well.  As mentioned elsewhere, the
IETF has had repeated opportunities to review those decisions
and has formally approved them.  Even mapping back and forth
between A-labels and U-labels is, in the real world, not as
transparent as one would like (or obtain if one knew that
everything that looks like a domain name is a domain name in
the public DNS -- see draft-iab-idn-encoding or review the
slides from the Hiroshima technical plenary for more details on
that issue).  

Curiously, if the WG had not been constrained by very old (and
necessary) rules about how the email environment works, its job
might have been much more simple and more in line with at least
one extrapolation from the comment above: if we had
standardized local-part formats sufficiently to avoid having to
prohibit interpreting or tampering with those fields enroute,
the WG could, in principle, have written extremely short
specifications allowing encoded-words (possibly restricted to
encoded UTF-8) in local-parts and essentially been done.  While
I doubt that solution would have been acceptable to many
implementers and user constituencies (in part because "only the
end-systems need to understand it" has never worked as well as
we often hope it does), it would have been much easier in terms
of specification simplicity.

In case it is useful for understanding the WG's choices in this
area, the WG in principle had a choice between adopting a
minimal change --relying as much as possible on trick encodings
and dependencies on endpoint handling as possible -- and moving
in the direction of relatively comprehensive use of
natively-encoded (see below) Unicode in email with some
transition provisions that would gradually atrophy.  In
practice, there was no choice at all: internal discussions made
it clear that a standard based on the former approach would
simply be ignored and localized or proprietary solutions
adopted and only one based on the latter had an reasonable
chance of implementation and global deployment.  Extrapolation
from the independent-of-EAI work reflected in
draft-iab-idn-encoding -- work that originated in the concerns
of a couple of operating systems that dominate the network
today-- also suggests that more dependency on exotic,
IETF-specific encodings is not a direction we should be going
in unless it is absolutely necessary.

> The second goal is to support Unicode in the
> more "native" form of UTF-8. (The quotation marks are
> because UTF-8 is not native Unicode, either; it is a highly
> encoded form of Unicode...)

As others have commented on the mailing list, the above and
some of the comments that followed in the review demonstrate a
fairly profound misunderstanding of Unicode and Unicode
terminology.  The only encoding form more "native" than UTF-8
(or UTF-16 or UTF-32) is a set of abstract integers that have
no intrinsic computer encoding form.  The IETF has established
a number of "non-native" encoding forms, including UTF-7 and
the Punycode-derived ACE form, but they are avoided where
possible in these specifications.

See the comments under #7 below for an additional aspect of the
ASCII-versus-Unicode distinctions.



(2) Explicitness versus discovery in MIME and related topics,
including a possible parameter on the MAIL command.

Claudio Allocchio 2010-12-22 wrote: 

> Another big issue is about blending the boundaries of
> servers in the transport system (MTAs), clients (UAs) and
> their roles, when the document specify that servers shall
> use guessing techniques from looking into bodyparts to
> understand if what they're transporting is internationalized
> according to this specification or not.  This is IMHO a
> basic violation of the role distiction in the legacy email
> system, and affects the MIME model al well.   

Yes, except that this "blending" already occurs with MIME and
other SMTP extensions.  Over the years, we have made some
decisions to be very explicit about parameters and
pre-identification of content and other decisions to force
systems to inspect or parse content because we did not believe
that such parameters could be trusted (or that any sensible
implementer would trust them).  I hope we have gotten most of
those historical decisions right although I have some doubts,
at least in retrospect, about some of them.

Given that history, I don't think it is appropriate to assume
that the EAI effort is leading us into a role distinction sin
or not because we are already there.  The question is what the
right choice is for this particular situation.  The WG
considered that choice at great length (albeit in the 2006-2008
period rather than more recently, but that part of the
specification has not changed) and came to the conclusion
that forcing inspection was the better plan.  Testing with the
Experimental versions of the protocols did not expose serious
problems with that choice. 

I am sure that the WG would be happy to reconsider this topic
is appropriate, but some solid evidence that there is a problem
and that the current decision is wrong would be far more
helpful in that regard than assertions based on a philosophy of
email that IETF protocols have already violated.  That
assertion, and some evidence, have been made for a MAIL command
parameter:

Claudio Allocchio 2010-12-22 wrote: 

> 3.5 Body Parts and SMTP Extensions

> I have problems in understanding why an SMTP server should
> peek extensively into the message geing transferred to
> understand that it is handling an interationalzed message.
> "There is no ESMTP parameter to assert that a message is an
> internationalized message." in my opinion should be fixed in
> another way, by ADDING an appropriate ESMTP parameter to
>...

Dave Crocker 2010-12-22 wrote:

> 4.  The SMTP extension needs to have the client use an
> explicit signal when it is sending a message encoded in
> UTF-8. This is easiest as a parameter to the MAIL command.
> The current specification creates a more complex and almost
> heuristic model for distinguishing ASCII from UTF-8 use.

Ned Freed 2010-12-22 wrote:

> (0) I cannot emphasize strongly enough how important it is
> to have a UTF8SMTP sort of parameter on the MAIL FROM to
> indicate that a message employing this extension is being
> submitted/relayed/delivered.  
>...

Ned Freed 2010-12-23 wrote (small excerpt):

> Again, headers don't have the proper semantics. A MAIL FROM
> parameter, OTOH, does.

The working group did consider the tradeoffs between (i)
forcing a server (really relay) to do a complete MIME parse if
it received an extended message and had to decide what to do if
the next hop did not support the extensions and (ii) putting in
a parameter whose presence or absence might not be trustworthy
given a history of, e.g., text/plain body parts being sent with
distinctly non-ASCII content but without charset parameters,
misuse of "name extensions" in lieu of adherence to
Content-Type, etc.  The decision of the WG was reflected in RFC
5336 (after IETF Last Call, etc.) and I note that none of the
known implementers of the RFC 5336 spec are objecting to that
decision now.  The consensus of the reviewers now seems to be
that the WG got it wrong.  The WG needs to review this again;
the change is certainly easy to make should it be appropriate.



(3) Fundamentals of handling syntax changes from other
specifications (especially 5321/5322):

Claudio Allocchio 2010-12-22 wrote: 

> The document quite often repeats rules from other
> specifications, AND re-describes these rules. This is
> dangerous (it makes very difficult to keep aligned
> documents, and will lead to different interpretations) and
> not needed.

The tradeoff, I hope obviously, is with the reader having to
flip back and forth repeatedly between documents to have any
hope of understanding the specification accurately.  I'm
personally sympathetic to your concern, but many WG
participants disagree. 

Specific suggestions that could be used as a model would be
helpful to the WG and the editors.


Claudio Allocchio 2010-12-22 wrote: 

> 3.6.1 "the server normally sends..." --"the server sends"
> (sorry... we do not like ABnormal servers!) :-)

This is another example of a narrative/ informative comment.
We know about exceptions.   Perhaps the sentence would be
better stated as "an RFC 5321-conforming server sends...".



(4) Gateways and related boundary systems

Claudio Allocchio 2010-12-22 wrote: 
 
> This specification updates a number of SMTP and Headers
> fields from RFC5321 and RFC5322. However these fields are
> also used in Gatewaying to other email systems, which are
> still existing. Section 3.7 in RFC5321 describes specific
> cases. However this memo provides no clue on possible effect
> that internationalized fields can have in case gatewaying
> occurs.  Gatewaying functions strongly rely on these values,
> and the introduction of these modification should describe
> this scenario, too. I suggest to include a specific section
> about these issues, and suggest at least a number of
> possible actions which Gateways can take to survive this
> change.

I'm not sure I understand why Gateways are different from
anything else.  If a gateway doesn't advertise the extension,
then it should never see a message that contains either
non-ASCII envelope addresses or non-ASCII content in the
headers (other than as encoded-words, of course).   The WG does
have some placeholder benchmarks for advice of various sorts;
IMO it would be quite useful to supply some of that advice for
gateways once sufficient operational experience had
accumulated.

But the only really hard gateway problem I see is if a given
gateway MTA interfaces to two back-end systems, one of which is
ASCII-only and one of which is broadly UTF-8 capable.  It will
either need to be reconfigured into two virtual gateways, one
of which advertises the extensions and one of which does not,
or it will simply have to reject mail with UTF-8 header fields
that is addressed to a system that can't handle it.  I note,
however, that such a gateway already has a problem that it
presumably has some mechanism to deal with: if it receives mail
with UTF-8 (or other non-ASCII) headers from one of its
i18n-capable systems with an Internet destination, it already
has to reject the message or perform some sort of conversions
that are, necessarily, not described in IETF specifications.


(5) The legacy of the Experimental protocols

Claudio Allocchio 2010-12-22 wrote: 

> The EAI WG charter states that in handling email message we
> shall be "consistent with the long-term view that email with
> invalid addresses or syntax should be rejected, rather than
> fixed up in transit between submission servers and delivery
> servers.". However a number of sections in the specification
> seem to contradict this, where they suggest actions, by
> exammining message elements (in the SMTP and in the Headers
> and in the Bodyparts) in order to try to deliver anyhow.
> This is a subtle line between maximising the service chance
> to deliver, and "fixing" things during the transaction, and
> it can encourage implementors to do many of these acions,
> instead of stiching to the idea "not supported --non
> delivery".

The experimental protocols described in RFC 5336 and elsewhere
included a rather complex mechanism for in-transit downgrading.
I'd encourage you to go look it up if you are interested, but
the general design was based on the 8BITMIME model -- a sender
discovering that the next-hop server wouldn't accept the option
could either reject the message or engage in a downgrading
process that was distinctly not lightweight.  The conclusion
from implementations and experiments was that it was too
heavyweight, too hard to get right, and that the number of
cases in which the downgrade procedure could not be applied
would be very confusing to users.  All vestiges of that
machinery should have been removed from the current versions of
the documents.  But I found some in an earlier review and it
may well be that some of the other review comments have
identified others.  If so, they clearly need to come out; the
editors may need help in identifying specific examples.


(6) Server actions when UTF8SMTP[bis] is not supported (and
Section 3.6.2).

Claudio Allocchio 2010-12-22 wrote: 

> The specification does NOT suggest a preferred order among
> the 3 possible options when the SMTP server state it does
> not support UTF8SMTPbis. Having 3 "MAY" options at the same
> level can create a very uncertain email service behaviour,
> and a very bad user's experience! This is consistent with
> what happens in other cases for other "options" in the email
> system (like DSNs and MDNs), but there should be at least an
> informative document describing the various scenarios, and
> giving some guidance to implementors in order to avoid
> totally incosistent behaviours.

Small bit of calibration about this: remember that the EAI
specs cannot do anything to dictate the behavior of an SMTP
server that does not support the EAI extensions and may have
never heard of them.  There is also a general design
assumptions, shared with other [E]SMTP assumption, that the
specification should not make any changes to general email
behavior that are not necessary consequences of what the
extension is trying to accomplish.

On rereading the document after going through these comments,
it is clear to me that the document would be improved by being
much more clear about what text is a change with EAI and
normative, what is a necessary consequence of provisions in RFC
5321 or other applicable standards, and what is just
informative narrative.  I don't know whether the WG shares that
point of view, nor whether it is desirable to try to rewrite
the document along those lines at this stage (in general, these
are not "known technical defects" so, if we could be assured
that Draft Standard versions of the documents would appear on a
timely basis, it might make sense to let them go for the
present).

These three options are simple extrapolations of rules that
already exist in RFC 5321: SMTP-senders must not send invalid
messages into the public Internet and must reject or bounce
such messages if they cannot be fixed up; only Submission
servers (and gateways) are permitted to make significant
changes to fix things up; and, implicitly, if mail is not
deliverable along the normal path and one knows a legitimate
path that would work, one is permitted to use it.  

Note that the first (MSA) option is useful for non-ASCII
address local-parts iff the MSA has an external source of
information that permits substituting ASCII-only addresses for
non-ASCII ones.  For address domain-parts and miscellaneous
header fields, there are typically encoded-word (or A-label)
options available.  Perhaps the document should be more
explicit about that.

If that flexibility "just in practice break[s] the concept of
universal email common service, creating islands which do not
talk to each other", then we would already have seen that
problem.  For example, the specification of 8BITMIME can lead
to the same situation without EAI: if a relay receives a
message with C-T-E 8bit or binary, and the first-preference
reachable MX doesn't support that option, it can downgrade the
message, reject it, or, IIR, try other servers at the same
preference level to see if one of them will provide support for
the extension.

Ned Freed 20101222 wrote:

>> 1.  If and only if the SMTP client (sender) is a Message
>> Submission Server ("MSA") [RFC4409], it MAY, consistent
>> with the general provisions for changes by such servers,
>> rewrite the envelope, headers, or message material to
>> make them entirely ASCII and consistent with the
>> provisions of RFC 5321 [RFC5321] and RFC 5322 [RFC5322].

> This is a bad idea no matter how you slice it. Such
> transformations depend on the availability of address
> mapping (from a UTF-8 address to an equivalent ASCII
> address) information; an agent being an MSA is neither
> necessary nor sufficient reason to have this information.

However, RFC 5321 already requires that an MSA not inject a
message into the public Internet until/unless it is valid.  And
it (and RFC 4409) effectively give the MSA permission to do
anything an MUA can do in order to accomplish that.  There is
no (intentional at least) assertion in 5336bis that the MSA (or
the MUA, for that matter) must have access to address mapping
information, just no requirement that it not use that
information if it has access to it.  If it doesn't have the
needed information, then there are clearly a lot of things it
cannot do; the quoted statement above is then just a
reiteration of the 5321 prohibition on passing trash into the
network (whether it is worth reiterating is a separate matter).

Of course, if a message is transferred from an MUA to the MSA
that contains non-ASCII header information in UTF-8 form but no
non-ASCII addresses, the above provisions don't imply the MSA
doing anything more than mapping that header information into
encoded words.  Again, there is no requirement that the MSA do
that mapping; the statement simply reiterates, in an i18n
context, the general permission for the MSA to take something
that works in a user->MUA->MSA environment and fix it to
conform to public Internet specifications.

It is worth noting that, during WG discussions, several strong
claims were made about intentions to implement both UTF-8 to
encoded word mappings and tables to support precisely the type
of address mapping suggested above in selected MSAs.  Assuming
people were telling the truth (and I certainly assume they
were), the conditions specified above, including address
mapping, are going to be exercised.

> But the bigger problem by far is defining what
> transformations are permissible. The present framework
> document is basically silent on what's allowed, so I for one
> have no idea what it means to be "consistent with the
> general provisions for changes by such servers" actually
> means. And unless you're willing to spell this out, I see
> this as practically guarnteeing a slew of interop problems.

With the understanding that my comments above go much further
than the existing text, that the WG hasn't agreed to any
expansion, and that Dave seems to be arguing for less text that
is just repetition of existing rules in 5321/5322, how much
further would you suggest going in spelling things out?


(7) Suboptimal use of ABNF and ABNF constructions

Dave Crocker 2010-12-22 wrote:

> * Rule Meta-Naming -- The 'u' preface for revised rules is a
> reasonable idea, but appears to be problematic.  These rules
> replace existing rules in other specifications. There needs
> to be an explicit and decision about the handling of this,
> and it needs to be applied consistently, either directly
> replacing the rules or else re-naming them consistently,
>...
> { On reflection, I think the "u" rule-naming convention is
> problematic.  If the current specification is replacing a
> rule previously defined elsewhere, it needs to use the same
> rulename.  This is simpler and clearer.

(and several comments by others, noting that Dave's second
recommendation appears to contradict Claudio's)

As I commented at more length in a note to Dave, Claudio, and the
EAI list on 2010-12-24 14:20 -0500, we've had a lot of trouble
getting ABNF for these documents right, much less optimal.  A
significant part of the optimality problem is that that there
seems to be no established good way to update one specification
by extending its syntax -- a problem that the IETF community
will almost certainly have to deal with again as we
internationalize more protocols.

In the particular case of ASCII and UTF-8 constructions, even
though ASCII is a compatible proper subset of UTF-8, there
is often a need to distinguish the two because plain-ASCII
works in legacy protocols (and does not require special
normalization or comparison rules that might, themselves, be
controversial) while UTF-8 does not work in the legacy cases
and raises more complex normalization, comparison, and
collation issues.   FWIW, we had the same problem in the
IDNA2008 specs because it was necessary to distinguish between
a traditional DNS "preferred syntax" name (aka "LDH") that did
not start with an ACE prefix and one that did use that prefixed
form, in spite of the fact that the latter, by design, would be
treated as a traditional "LDH" name by any application that was
not aware of the special IDNA constructions.

For the particular case of EAI, the WG decided to go with the
"u" prefix on new rules that superseded 5321 or 5322 rules.
The WG tried to be consistent with that prefix on new rules,
and preserve most of the original rules.  All rules were
extended rather than overwritten.  The WG had discussed,
somewhat earlier, the possibility of simply coping the entire
ABNF collection from RFC5321/5322 and then extending or
modifying rules as needed.  That would have eliminated the need
to reference back to those documents for ABNF but the idea was
rejected, largely to avoid exactly the problem with updating
that several reviewers commented on.

Again, this is a general problem: if the community has a clear
preference as to how it should be dealt with, I'm nearly sure
that the EAI WG will conform.  In the absence of a general
solution, my personal guess is that the "u" convention (applied
accurately and consistently) may turn out to be the best we can
do.


(8) MIME restrictions and nested encodings

Dave Crocker 2010-12-22 wrote:

> 5.  The SMTP extension needs to remove all restrictions it
> imposes on MIME content-type.  A major reason that MIME was
> successful was that it was transparent to the transfer
> infrastructure.  The current SMTP extension specification
> changes this model, which actually increases the barrier to
> adoption of Unicode in email.  It needs to be easy for two
> MUAs that support Unicode in the email header to exchange
> mail even when the infrastructure does not support UTF-8.

Right.  Unfortunately, there is already a restriction in MIME
that links Content-Type to Content-Transfer-Encoding, the "no
nested encodings" rule.  That rule is imposed primarily as a
restriction on message/ subtypes.  And it works because MIME
assumed that all header information was going to be ASCII and
hence able to be transmitted in C-T-E: 7bit.

So now we have a little problem: MIME is designed to permit
forwarding messages in encapsulated form using message/rfc822.
But message/rfc822 uses ASCII headers only and has to obey the
"no nested encodings" rule.  One would like to be able to
encapsulate an EAI-conformant message and even forward it into
a legacy environment.  There are actually a number of options
for doing that, including deciding that a message with
non-ASCII headers cannot be forwarded into a 5321/5322
environment (pretty obviously a bad idea to prohibit that),
creating a new top-level MIME type with different rules (the
transition issues and implications for legacy MUAs are pretty
astonishing), or creating a new "message/" subtype with
different rules and what may be seen as an additional
Content-Type/ Content-Transfer-Encoding entanglement.  After
considerable discussion, the WG selected the latter (see #13
below) and got IETF signoff in RFC 5336.


(9) Strong conformance language

Claudio Allocchio 2010-12-22 wrote: 

> 3.1 Framework for the Internationalization Extension

> - bullet point 3. I do not see any need to state that
> clients MUST reject...  and MUST be fully compliant... etc.
> This is implicit in any specification.  If there is a
> specific need to add this detailed behaviour (to prevent
>...

Our general practice with email specifications has been to
specify conforming behavior and simply leave non-conforming
behavior "outside the scope of the specification".  That
doesn't work in this case because, according to the WG's
analysis, a partial implementation --whether outside the spec
or otherwise-- would be bad news for interoperability.  So it
seemed necessary to be very clear about what clients were
expected to do and what servers could reasonably expect.
Whether that was better done with this text, with an
"Implementer's Note" (which has no normative status), or with
an extended explanation of the problems and a threat or two
would seem to me to be largely matters of editorial taste,
especially for a Proposed Standard.


(10) Security-related issues

Claudio Allocchio 2010-12-22 wrote: 

> 5.  Security Considerations

> there is one more issue: as internationalized items will
> also result into logs and traces, their presence may affects
> trouble ticket systems used by security operations teams
> (CERTs/CSIRTs). And they also can affect quick handling of
> incidents, has it may require more time to correctly read
>....

Agreed.   I assume the editors will consider your proposed text.


(11) Editorial issues with significant substantive
implications.

Dave Crocker 2010-12-22 wrote:

> { Note - the term "mailbox names" is not defined here or in
> RFC 5321.  In RFC 5321 it appears to be used to mean
> local-part; however because its precise meaning is unclear,
> I strongly urge NOT using it here at all. Instead I suggest
> using whatever ABNF rulename is appropriate.  This
> guarantees clarity.

Well, while getting rid of "mailbox name" or defining it very
precisely, would probably be an improvement, there is no ANBF
rulename that would really be appropriate, at least without
additional decoration.  As you and others have pointed out
recently, rules for <mailbox> appear in both 5321 (where it
refers to the mailbox name (sic) itself, e.g.,
local-part@domain-part) and in 5322 (where it refers to
something that might include a display name and assorted
spacing).   I have no doubt that this document should be as
clear and precise as possible, but its authors should not be
blamed for trying to work around the errors of the authors of
5321, 5322, and their predecessors. 

Dave Crocker 2010-12-22 wrote:

>> The value of "uDomain" SHOULD be verified by IDNA
>> definitions [RFC5890].  If

> { I do not understand what "SHOULD be verified by IDNA
> definitions" means.

> If it means that the uDomain "SHOULDbe verified" then it is
> out of scope for this specification. There is no reason that
> SMTP rules concerning verification of Unicode-based domains
> needs to be different from ASCII-based domains.  In
> particular, verification of a Domain name is specified
> elsewhere.
>...

Editorial issues aside, 5321 contains some very
carefully-written language whose intent is to require that
domain-parts be validated lexically but to avoid requiring
that they be looked up in the DNS until/unless that is
necessary for some other reason.  The "lookup" side of
IDNA2008 (in RFC 5392) makes more or less the same circle
around this issue but with the understanding that lexical
validation of U-labels is a somewhat more complex process than
checking against a short list of characters, positions, and
lengths.   I believe that is what the author was trying to
capture.  Certainly it could have been expressed differently.

Dave Crocker 2010-12-22 wrote:

>> Otherwise, surprising rejections
>> can happen during temporary failures, which users might
>> perceive as a serious 

> { Probably not just temporary failures.  Having services
> that are meant to be redundant with each other actually
> provide different semantic behavior is just plain dangerous.
> It is essentially guaranteed that they will cause problems.}

Sure.  But you argued extensively elsewhere for not duplicating
text that appears elsewhere and, IMO, more important, for not
making statements that go beyond a rather narrow reading of the
requirements for internationalized email.  

Ned Freed 20101222 wrote:

> So you can use alternate MXes, but not alternate A records?
> I actually agree with this - an alternate A is presumably
> another address for the same host, so no point in trying it.
> But this needs to be spelled out.
 
> At an absolute minimum this needs to be accompanied by some
> security considerations text. The issue, I hope, is obvious:
> There are sites aplenty with large numbers of MX records and
> which won't support this extension any time soon. And all
> too often those MXes are *slow* to respond. So sending a
> message that causes them all to be tried is ... you get the
> idea.
 
> In fact I'm tempted to go one further and say that if an MX
> at a given priority is found not to support this extension,
> you SHOULD assume that MXes at lower priority don't either.

And this is where we descend into a situation that extends far
beyond EAI.  The problem, as Ned's note almost suggests, is
actually quite general.  For example, if we had

   foo.example.com. MX 0  foomail0.example.com.
   foo.example.com. MX 10 foomail1.example.com.
   foo.example.com. MX 10 foomail2.example.com.

and "foomail1" supported 8BITMIME with downgrading and
"foomail2" did not, a system sending a message containing
C-T-E: 8bit that reached foomail1 would have the message go
through with downgrading if needed but would get a rejection or
option not supported condition if it happened to get to
foomail2.  Or it might get lucky and hit foomail0 and find out
what it actually supported.  Similar situations could apply
--at least wrt rejection versus bounces-- if foomail1 supported
a different set of antispam provisions than foomail2, or, for
that matter, if both deferred antispam processing to foomail0.

As far as I can tell after a very brief scan, there is no
current normative IETF specification that discusses this
situation and gives guidance about it.  In retrospect, we
probably should have at least described the issues with
non-identity of services in RFC 1425, but we didn't do that,
much less make specific recommendations.  

I agree with Ned that it would make a lot of sense to
explicitly say "no alternate A records because, if they don't
represent the same host, you should be using MXs" and "if the
first MX you try doesn't support the extension, assume the
others don't either and stop".  But, because of the generality
of the problem, this document doesn't seem to me to be the
right place to say that.  5321bis probably would be a
reasonable if we think it is a clarification, but especially
with YAM in a coma and no mention of this topic in the
pre-approval document, the odds of my getting to 5321bis before
this EAI work is closed out are in the "low to none" range.
Worse, while someone could quickly cons up an I-D to specify
this behavior and try to push it through as a Proposed Standard
that 5336bis could reference, processing of such a document
would essentially constitute a claim that the spec is new and
not a clarification to 5321, precluding folding it into 5321bis
later, at least without marching that document along the
standards track to Draft Standard first.  Suggestions about how
to get out of that mess are welcome, but I don't think it is an
EAI problem (even though 5336bis might plausibly be modified
--or the Framework document reopened and modified -- to explain
just how ambiguous the whole situation is).

For RFC 5336, it was important to call the issue out because
the "downgrade or not" behavior is even more complicated than
the potential behavior variations with 8BITMIME (remembering
that one can offer the option but, if the next hop doesn't
support 8bit transport, one can either downgrade or reject) and
other extensions..  Whether it is necessary to say anything at
all in 5336bis, given how little we have said in places that
perhaps establish precedents, is debatable.  But please let's
not suggest expanding on this case in this document to cover
other email environments, especially in the context of urging
the the spec keep its scope and assertions narrow.


Dave Crocker 2010-12-22 wrote:

>> 3.6.4.2.  VRFY and EXPN Commands and the UTF-8REPLY
>>Parameter 

>> If the VRFY and EXPN commands are transmitted with the
>> optional parameter "UTF-8REPLY", it indicates the client
>> can accept UTF-8 strings in replies to those commands.
>> This allows the server to use UTF-8 strings in mailbox

> { Is this extension trying to to say that a client might
> support UTF8SMTPbis but not be able to access UTF-8
> replies???  Under what circumstance is this reasonable? }
>...

Not what it is intending to say (could have been expressed
better).  Consider the following scenario: Client sends EHLO,
server offers UTF8SMTPbis.  Client sends VRFY as its next
command, using an ASCII-only argument and no parameter.  The
server has no clue as to whether or not the client is
EAI-compliant or otherwise has any idea what to with a
reply containing a non-ASCII address.  For the server to return
a non-ASCII string under those circumstances would be in
violation of 5321.



(12) The keyword denoted as "UTF8SMTPbis" in the drafts.

While the changes between the Experimental protocols and the
present draft are not large, they are also not trivial.  After
fairly extensive discussion, the WG concluded that these new
specifications should be denoted by a different SMTP Extension
keyword than the "UTF8SMTP" that was used by the Experimental
version (RFC 5336).  In large part because of concerns that
some implementation would be deployed in advance of the
specification becoming final, the WG concluded that the new/
final keyword should be assigned only as part of the IESG
approval process.  "UTF8SMTPbis" is only a placeholder and will
not be that final keyword.  It may be worth noting that, if the
protocol is changed to require a MAIL command parameter, that
WG decision will have turned out to be quite important.

Anyone who strongly believes that some variation on the
"UTF8SMTP" theme misrepresents what is actually happening in
these specifications is welcome to suggest other keywords to
the IESG.


(13) New content types for embedded messages.

Dave Crocker 2010-12-22 wrote:

> 3.  There probably needs to be definition of MIME
> message/uni-rfc822, specifying Unicode support within a
> message contained in MIME.  I'm less clear whether there
> needs to be a MIME Content-Transfer-Encoding form specific
> to UTF-8.

See message/global in draft-ietf-eai-rfc5335bis.  This is an
area where the WG's decisions about what material belonged in
which document followed the advice to keep header and body part
discussions in 5335bis rather than 5336bis.


(14) Procedural and quasi-procedural issues

Dave Crocker 2010-12-22 wrote:

> 1.  The Framework document is normative and needs to be
> completed along with the other two specifications, since
> they quite reasonably state a normative dependence on the
> Framework document.
>...
> * Framework -- The Framework document[1] is (correctly)
> referenced as required reading.  It supplies essential
> terminology and architecture for this specification.  In
> fact it is a specification, complete with formally normative
> vocabulary.  This means that it must be a normative
> reference by rfc5336bis.  It therefore also means that the
> Framework document needs to be completed before the current
> specification can be standardized.

Note that the Framework document went through IETF Last Call
and was approved by the IESG last September for publication as
Informational.  The WG was agnostic on whether it should be
Informational or Standards Track.   Since it is still in the
RFC Editor queue awaiting references to the documents now under
review, I assume that, if there were sufficient consensus that
it is normative and should be on the Standards Track, the IESG
could be persuaded to revisit that decision.  In addition,
while I don't believe that anything in these reviews requires
doing so, the document could, in principle, be recalled by the
IESG and material changed or altered.

Dave Crocker 2010-12-22 wrote:

> * Infrastructure Requirement -- Unless this option is in
> force, carrying internationalized email in a MIME part is
> prohibited.  This is out of scope for the working group and
> it is a counter-productive rule.  Imagine if the same type
>...

There may well be an editorial problem with how this is written
up or even with how "internationalized mail" is defined.  But I
see nothing that supports the apparent hyperbole in the
comments above.  Remember that 5322 and the base MIME specs
prohibit non-ASCII headers, so messages containing such headers
(as the message header or MIME headers) are prohibited by those
specs without some new extension(s).   There is no
(intentional) prohibition in these documents against carrying
non-ASCII text in mail messages.  And, if one wanted to
pseudo-encapsulate a message and its headers by treating it as,
e.g., text/plain with charset=utf8, rather than as
message/rfc822 (or message/global), these specifications don't
prohibit that either (might not be a good idea because of the
loss of recognition and handling of boundary markers and internal
Content-Types and Content-Transfer-Encoddings, but that is not
a problem for this specification).

So, unless the comment above is just the result of confusion
brought on by an editorial problem, I don't see where you are
going with it.


(15) Future of rfc5336bis.

Ned Freed, 20101222 wrote: 

> One final comment. Several of the issues that have been raised
> are so fundamental that once they are addressed (point (0)
> especially), this document is almost certainly going to
> require another full review cycle.

Sadly, I agree.  I even believe that, were none of these
fundamental issues present, the number of editorial corrections
(including ABNF matters) that are required will be sufficiently
extensive that the risk of introducing new problems would
require such a review cycle.

     john



From klensin@jck.com  Mon Dec 27 11:45:19 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 AF2D33A68CD for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 BWk9nBSZoa4p for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:45:19 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id BF7053A67BD for <ima@ietf.org>; Mon, 27 Dec 2010 11:45:18 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXJ2R-000OPZ-Eo for ima@ietf.org; Mon, 27 Dec 2010 14:47:23 -0500
X-Vipre-Scanned: 05B68BED001DEB05B68D3A-TDI
Date: Mon, 27 Dec 2010 14:47:22 -0500
From: John C Klensin <klensin@jck.com>
To: ima@ietf.org
Message-ID: <8A939B5EBFD403D55927BB10@[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 status, next steps, and the long "review" note
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, 27 Dec 2010 19:45:20 -0000

Hi.

As most of you will have noticed, or will notice soon, I just
sent out a huge note that tries to summarize the issues raised
in the review of 5336bis.   Another one (not nearly as long)
will follow about 5337bis.   I haven't seen any formal review
comments about 5335bis, but we should not assume from silence
that it is in much better shape.

If the WG is going to stay even nearly on schedule (see my
previous very lengthy note), note only are the various authors
and editors going to need to go back to work, but the WG needs
to be ready to be engaged in discussing any and all of the
various issues that have been raised (except for those that are
clearly editorial and trivial).  If that level of participation
isn't available, I believe we will have a very hard time getting
through Last Call.

In that context, I would encourage people to read, or at least
skim, my long response and the original comments (at least one
of which is even longer).  But you need to pay special attention
to the notes on the WG list that address specific issues.
Joseph is trying to get the issues summarized in a tracker, but
there is no need to wait: the discussion that is now going on
about the details of handling VRFY and EXPN might as well be the
first topic.

   regards and best holiday wishes to all,
     john


From dhc2@dcrocker.net  Mon Dec 27 11:56:13 2010
Return-Path: <dhc2@dcrocker.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 7E9453A68D9 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.588
X-Spam-Level: 
X-Spam-Status: No, score=-6.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 7zAhoBaBFfg0 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 11:56:11 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 34E203A67BD for <ima@ietf.org>; Mon, 27 Dec 2010 11:56:11 -0800 (PST)
Received: from [192.168.1.75] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBRJw7QM002456 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2010 11:58:12 -0800
Message-ID: <4D18EFCD.6000309@dcrocker.net>
Date: Mon, 27 Dec 2010 11:58:05 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Charles Lindsey <chl@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>	<01NVQAP0UQRU007CHU@mauve.mrochek.com>	<op.vn6g7hky6hl8nm@clerew.man.ac.uk>	<01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
In-Reply-To: <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 27 Dec 2010 11:58:12 -0800 (PST)
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 27 Dec 2010 19:56:13 -0000

On 12/27/2010 4:24 AM, Charles Lindsey wrote:
> On Fri, 24 Dec 2010 00:33:32 -0000, Ned Freed <ned.freed@mrochek.com> wrote:
>> A header doesn't work for this purpose. It needs to be announced in the
>> envelope.
...
> However, I do not quite see the necessity for it. If some MTA announces the
> capability UTF8SMTP, then it is declaring its willingness to accept messages
> destined for utf-8 addresses and to do the "right thing" with any problems that
> might arise


Any protocol model that requires a participant to do deep inspection of the data 
or to do some form of guessing is likely to be problematic. It can invite errors 
and/or higher handling overhead.

The current specification actually suffers both of these.  It requires deep 
inspection by the server, AND it requires the server to guess whether an 
ASCII-only message is meant to be part of the legacy processing environment or 
whether it might really be subject to Unicode processing, in spite of having 
only UTF-8 characters below x07f.  (The latter is part of the fun of having 
Unicode be a superset of ASCII.)

While it might be safe to treat an ASCII-only message as being part of the 
legacy system, it might not.  For example, the set of recipients that support 
legacy vs. Unicode might be different and this can change the nature of a 
conversational exchange.  Finding out about the limitation with the first 
posting is better than with a later posting.

That is, the fact that an SMTP option is involved means that the goal is to move 
the entire email infrastructure over to Unicode support.  Both sides of the SMTP 
exchange need to know whether that move has taken place, without having to guess 
or do deep inspection.

It also happens that an option to the MAIL command is cheap, so why not do it?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From Shawn.Steele@microsoft.com  Mon Dec 27 12:03:28 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 847E33A68DD for <ima@core3.amsl.com>; Mon, 27 Dec 2010 12:03:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.286
X-Spam-Level: 
X-Spam-Status: No, score=-10.286 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152]
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 nnLTReVCK9Cq for <ima@core3.amsl.com>; Mon, 27 Dec 2010 12:03:27 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 76B233A68D9 for <ima@ietf.org>; Mon, 27 Dec 2010 12:03:27 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 27 Dec 2010 12:05:32 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0255.003; Mon, 27 Dec 2010 12:05:32 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: UTF-8 in a Subject header field?
Thread-Index: AQHLpftKpipPiA0HGUy2RkHNFb/bxw==
Date: Mon, 27 Dec 2010 20:05:31 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B4314B@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] UTF-8 in a Subject header field?
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, 27 Dec 2010 20:03:28 -0000

Pj4gU28gSSB0aG91Z2h0IEkgc2hvdWxkIGFzayBob3cgdGhlIHdvcmtpbmcgZ3JvdXAgZXhwZWN0
cyBVVEYtOA0KPj4gU3ViamVjdCBkYXRhIGFuZCBkYXRhIGluIG90aGVyIGZyZWUtZm9ybSBoZWFk
ZXItZmllbGRzIHRvIGJlDQo+PiBoYW5kbGVkLg0KPg0KPiBJc24ndCB0aGF0IGNvdmVyZWQgYnkg
UkZDIDIwNDcgPw0KPg0KPiAgIFN1YmplY3Q6ID0/VVRGLTg/UT9Kb3lldXg9MjBObz1DMz1BQmw/
PQ0KPg0KPiBJIHJlYWxpemUgdGhhdCBpZiB3ZSdyZSBnb2luZyB0byBhbGxvdyBiYXJlIFVURi04
IGluDQo+IGFkZHJlc3NlcywgaXQgbWlnaHQgc2VlbSByZWFzb25hYmxlIHRvIGFsbG93IGl0IGV2
ZXJ5d2hlcmUsDQo+IGJ1dCBpdCdzIGJldHRlciB0byBhdm9pZCBtdWx0aXBsZSB3YXlzIHRvIGRv
IHRoZSBzYW1lIHRoaW5nLg0KDQo+IFdpdGggdGhhdCBpbiBtaW5kLCBJJ2Qgc3VnZ2VzdCB0aGF0
IHRoZSBFQUkgZG9jdW1lbnRzIHdvdWxkIGJlbmVmaXQgYnkgDQo+IGJlaW5nIHNob3J0ZXIgYW5k
IG1vcmUgYnJ1dGFsOiBhbnl3aGVyZSB5b3UgY2FuIHVzZSBhcmJpdHJhcnkgQVNDSUkgeW91IA0K
PiBjYW4gbm93IHVzZSBhcmJpdHJhcnkgVVRGLTguICBBbGwgb3RoZXIgZW5jb2RpbmdzIGFyZSBk
ZXByZWNhdGVkLCBubyANCj4gY2hhcnNldHMgb3RoZXIgdGhhbiBVVEY4IGluIHRvcC1sZXZlbCBN
SU1FIHBhcnRzLCBBLWxhYmVscyBpbiBhZGRyZXNzZXMgDQo+IHdpbGwgY2F1c2UgYSByYXp6YmVy
cnkgdG8gY29tZSBvdXQgb2YgeW91ciBzcGVha2VyLiAgSWYgeW91IHdhbnQgdG8gc2VuZCANCj4g
bWFpbCB0byBzb21lYm9keSB3aG8gZG9lc24ndCBncm9rIEVBSSwgaXQncyB5b3VyIE1VQSdzIGpv
YiB0byB0cnkgdG8gDQo+IGNyZWF0ZSBhIG1haWwtY2xhc3NpYyB2ZXJzaW9uLg0KDQpJbiBteSBv
cGluaW9uIFVURi04IGluc3RlYWQgb2YgQVNDSUkgd291bGQgYmUgdGhlIGJlc3QgZm9yIEVBSSwg
cGFydGljdWxhcmx5IHNpbmNlIHdlJ3JlIG5vdCBib3RoZXJpbmcgd2l0aCBkb3duZ3JhZGUuICBU
aGVyZSBtaWdodCBiZSBzb21lIHBsYWNlcyAoY2VsbCBwaG9uZSBnYXRld2F5cz8pIHRoYXQnZCBi
ZW5lZml0IGZyb20gYmVpbmcgYWJsZSB0byBoYXZlIG90aGVyIGVuY29kZWQgTUlNRSBwYXJ0cywg
dGhvdWdodCBJIGRvbid0IG1pbmQgaWYgdGhleSBnZXQgcmF6emJlcnJpZXMuDQoNCiJUb2RheSIg
c29tZXRpbWVzIDgtYml0IG5vbi1hc2NpaSBzdHVmZiAiZ2V0cyB0aHJvdWdoIiwgYnV0IHRoZXJl
J3Mgbm8gZGVmaW5lZCBiZWhhdmlvciBmb3IgdGhhdCBwcmFjdGljZS4gIFNheWluZyB0aGF0ICI4
LWJpdCBzdHVmZiBpcyBVVEYtOCIgKHVubGVzcyBpdCdzIGluIHNvbWUgb3RoZXIgbWltZSBwYXJ0
KSB3b3VsZCBjbGFyaWZ5IHRoYXQgYmVoYXZpb3IuDQoNCi1TaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg
76Oi76Oj76OX76OU76OZDQpodHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGU=

From barryleiba.mailing.lists@gmail.com  Mon Dec 27 12:56:41 2010
Return-Path: <barryleiba.mailing.lists@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 04AF53A68E4 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 12:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.636
X-Spam-Level: 
X-Spam-Status: No, score=-102.636 tagged_above=-999 required=5 tests=[AWL=0.341, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 2T5YJ8P3pHPS for <ima@core3.amsl.com>; Mon, 27 Dec 2010 12:56:39 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 959573A68E3 for <ima@ietf.org>; Mon, 27 Dec 2010 12:56:39 -0800 (PST)
Received: by iwn40 with SMTP id 40so9469582iwn.31 for <ima@ietf.org>; Mon, 27 Dec 2010 12:58:44 -0800 (PST)
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=DCCD5fSREMESwu/SPYKy+xjj9oLkhCCGPPTaHcic1X0=; b=t8NRlo30IRMLMFwVml7I0js6jrkPPlJZ+yUPs3ykgvw3uEFVG7/d3NxM0yB5oj4UMS y0SB7/3wlSqGo3Na0HfMaVB+cH0pqFrElx1rU278lNB6FwjdrmXsV6FiZ7nzJXhbjRaX o5v6idUTAnUNUtzY9LMZEPpoO0Bq4D3iHrOt0=
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=T1IDq5DxrlVlGHwBgILahlaxdYy/EmgO8D/y5djnUrQv1tfe7p1u5oVuCU8awI4NzJ hXwthifyvN5lCZXEDjP9nTWJk3gX0kU+ZDOy+qyPeqBxJLvcE8p6EoYnCpjEg40sha9R hhDo6UP5zW/JQXf5vzqAF5W7zQSOjGatmUnNE=
MIME-Version: 1.0
Received: by 10.42.167.67 with SMTP id r3mr12928479icy.13.1293483524235; Mon, 27 Dec 2010 12:58:44 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.240.2 with HTTP; Mon, 27 Dec 2010 12:58:44 -0800 (PST)
In-Reply-To: <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk>
Date: Mon, 27 Dec 2010 15:58:44 -0500
X-Google-Sender-Auth: YqeoLpYqooY3S3u4YZfEvNTV9IQ
Message-ID: <AANLkTinQyjbQDC8GS5q=TJrtb9O60m94Lwzwt2Q2UuQU@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Charles Lindsey <chl@clerew.man.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 27 Dec 2010 20:56:41 -0000

> However, I do not quite see the necessity for it. If some MTA announces the
> capability UTF8SMTP, then it is declaring its willingness to accept messages
> destined for utf-8 addresses and to do the "right thing" with any problems
> that might arise (such as generating a bounce if some MTA further down the
> chain finds a problem). Essentially the same as current MTAs do with ASCII
> messages that turn out to be undeliverable.
>
> If some client tries to send such a message without first checking that the
> UTF8SMTP capability has been advertised, then it is in breach of our
> proposal, and is just like people who try to "just send 8-bits" at the
> moment - if they strike lucky it might work, but there is no guarantee.

That isn't quite enough.  If a message goes through a couple of MTAs
OK, and then there comes an MTA that doesn't do UTF8SMTP, how is this
MTA to know that the message has UTF8 and the situation needs to be
dealt with? The submitting client knew, but we're well past that, and
the only way to tell now, lacking some clue in the protocol, is by
inspection of the message.

As Dave says, the parameter is cheap; let's do it.

Barry

From klensin@jck.com  Mon Dec 27 16:10: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 9C22B28C0CF for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 JHh20yvXN8hc for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:10:34 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id B225128B56A for <ima@ietf.org>; Mon, 27 Dec 2010 16:10:31 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXNB6-00018r-Dy for ima@ietf.org; Mon, 27 Dec 2010 19:12:36 -0500
X-Vipre-Scanned: 06A95C63001DEB06A95DB0-TDI
Date: Mon, 27 Dec 2010 19:12:34 -0500
From: John C Klensin <klensin@jck.com>
To: ima@ietf.org
Message-ID: <02EB1F03BAF0ED410F97CDC6@[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] EAI review topic: Parameter on MAIL command
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, 28 Dec 2010 00:10:36 -0000

(writing as co-chair)

Hi.

Joseph and/or I will be sending out a series of (short) notes to
the WG mailing list identifying substantive issues that the WG
needs to review and make decisions about.  They are going to be
short in the hope that people will read them and read them soon,
but there are relevant previous discussions on the mailing list,
in the reviews, and in the long set of notes I posted earlier
that people should try to understand before responding to the
questions.  However, remember that the WG is supposed to be
working quickly: these issues are in the critical path for
anything to more forward.

Question: Should we define, and require, an announcement
parameter on the MAIL command if the sender intends to transmit
either non-ASCII addresses or UTF-8 in headers (other than as
encoded words)?

Discussion references: My long note, especially item (2), which
I hope summarizes the review comments) and a number of comments
on-list about what is required if this header is not present.

    john


From klensin@jck.com  Mon Dec 27 16:19:35 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 80B813A682B for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 dw7Lc9Y8ODjW for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:19:34 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 8A2B23A6810 for <ima@ietf.org>; Mon, 27 Dec 2010 16:19:34 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXNJq-0001In-2F for ima@ietf.org; Mon, 27 Dec 2010 19:21:39 -0500
X-Vipre-Scanned: 06B1A02B001DEB06B1A178-TDI
Date: Mon, 27 Dec 2010 19:21:35 -0500
From: John C Klensin <klensin@jck.com>
To: ima@ietf.org
Message-ID: <2B9258A1B04B6596D4F07D20@[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] EAI review topic: VRFY/EXPN
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, 28 Dec 2010 00:19:35 -0000

(writing as co-chair and incorporating the introduction to the
note I sent a few minutes ago by reference)

Topic: The description of VRFY and EXPN handling in 5336bis is
not adequate.  Whatever is done, we will have to change/fix it.
In the questions below, I've mentioned VRFY but I assume that
EXPN would get exactly the same treatment.

Questions: 

(1) Should VRFY be retained as is, with the parameter, but with
a restriction that the parameter MUST NOT be used without EHLO
appearing first.

(2) Should VRFY be retained as is, with the parameter and
without the "ok to use VRFY without a session, i.e., without
EHLO first".  Note that this would be the first time an SMTP
extension has been permitted without explicit server permission
via EHLO and that it involves a small risk of non-EAI-aware
servers parsing the parameter as part of a name sent by a client.

(3) Should we move toward a new command, replacing VRFY, but
with more specific syntax that explicitly provides for
parameters and, presumably, a mail session?   Note that, if the
answer to this is "yes", someone would need to generate a
proposal that could be processed separately from the EAI effort.
While generating the proposal is no problem, the specification
of the new command would create a normative dependency from
5336bis and that might slow things down in terms of publication
of 5336bis/ 5335bis/ 5337bis.

Discussion references: Many notes on the mailing list in the
last several days.

    john


From dhc2@dcrocker.net  Mon Dec 27 16:29:56 2010
Return-Path: <dhc2@dcrocker.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 0CE293A6831 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 RsYveWlF4ido for <ima@core3.amsl.com>; Mon, 27 Dec 2010 16:29:53 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id E291B3A6810 for <ima@ietf.org>; Mon, 27 Dec 2010 16:29:53 -0800 (PST)
Received: from [192.168.1.75] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBS0VrFN008104 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ima@ietf.org>; Mon, 27 Dec 2010 16:31:58 -0800
Message-ID: <4D192FF8.1030706@dcrocker.net>
Date: Mon, 27 Dec 2010 16:31:52 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ima@ietf.org
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]>
In-Reply-To: <68655A9F86D4BE7ED933F8A6@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 27 Dec 2010 16:31:59 -0800 (PST)
Subject: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 28 Dec 2010 00:29:56 -0000

Folks,

I'm sending this under separate Subject line "cover" because I think there is a 
basic issue that needs some careful attention:


On 12/27/2010 11:39 AM, John C Klensin wrote:
>> The second goal is to support Unicode in the
>> >  more "native" form of UTF-8. (The quotation marks are
>> >  because UTF-8 is not native Unicode, either; it is a highly
>> >  encoded form of Unicode...)
> As others have commented on the mailing list, the above and
> some of the comments that followed in the review demonstrate a
> fairly profound misunderstanding of Unicode and Unicode
> terminology.  The only encoding form more "native" than UTF-8
> (or UTF-16 or UTF-32) is a set of abstract integers that have
> no intrinsic computer encoding form.  The IETF has established
> a number of "non-native" encoding forms, including UTF-7 and
> the Punycode-derived ACE form, but they are avoided where
> possible in these specifications.

and

On 12/27/2010 11:39 AM, John C Klensin wrote:
 > In the particular case of ASCII and UTF-8 constructions, even
 > though ASCII is a compatible proper subset of UTF-8, there
 > is often a need to distinguish the two because plain-ASCII
 > works in legacy protocols (and does not require special
 > normalization or comparison rules that might, themselves, be
 > controversial) while UTF-8 does not work in the legacy cases
 > and raises more complex normalization, comparison, and
 > collation issues.


One of the most difficult aspects of integrating work from outside the IETF into 
protocols done inside the IETF is the multicultural "diversity" between the 
outside and inside communities. The two communities have different terminology 
and different technical perspectives, yet the result must be something viable to 
both worlds.

In this case, a key point to realize is that this is not merely work within the 
Unicode community.  It has to make sense for Internet/IETF protocol reviewers, 
implementers and users.

That challenge is exacerbated by the fact that the current work is being grafted 
onto a long-running system with its own peculiar realities involving underlying 
data "representation" versus superficial data "encoding".

And then there are the further opportunities for confusion by the fact that the 
older environment is based on a data form that is a subset of the newer form and 
the fact that some encodings can sit ON TOP OF some other encodings!

All of this should make everyone extremely cautious about terminology that gets 
used:  It needs to be very precise and very accurate, and it needs to work for 
readers who are not experts in one culture or the other.  Consequently the 
observation that a reader might be relatively naive about one of the cultures 
ought to serve as a challenge to the writer, not a means of dismissing comments 
from the reader.

In fact, at least some of us reading the current specifications found things 
confused between ASCII vs. Unicode -- that is between the range of text 
characters being supported -- and between ASCII vs. UTF-8 -- that is between a 
7-bit encoding and an 8-bit encoding.  The former is semantic while the latter 
is syntactic.[1]

The fact that the Unicode world is used to saying UTF-8 to mean both semantics 
and syntax is not enough for the current work, in my view.  It needs to do the 
additional work of making sure that the reader has no legitimate opportunity to 
be confused between the two.

This is why I think the specifications should use Unicode when they mean the 
rich set of text characters, and UTF-8 when talking about the most popular 
encoding of those characters into an 8-bit form.  (As noted, there really are a 
variety of other encodings, including some that are idiosynchratic.)


d/

[1] For what it's worth, I'll note that before I sent my previous note, I did do 
some review of Unicode and UTF-8 terminology and could readily see that 
representation vs. encoding are not maintained as strict distinctions and that 
UTF-8 is used to mean both.  Rather than taking this a reducing the validity of 
my concern, it strengthened my feeling that the specifications need additional 
effort at clarity about the distinction.
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From klensin@jck.com  Mon Dec 27 18:36:15 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 81A613A6908 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 18:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 J0X-EawtgT4R for <ima@core3.amsl.com>; Mon, 27 Dec 2010 18:36:14 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id ADFE83A6800 for <ima@ietf.org>; Mon, 27 Dec 2010 18:36:14 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXPS7-0002kP-1q; Mon, 27 Dec 2010 21:38:19 -0500
X-Vipre-Scanned: 072EC3A2001DEB072EC4EF-TDI
Date: Mon, 27 Dec 2010 21:38:17 -0500
From: John C Klensin <klensin@jck.com>
To: dcrocker@bbiw.net, ima@ietf.org
Message-ID: <9B48F59821946F2EA2DCDEA0@[192.168.1.128]>
In-Reply-To: <4D192FF8.1030706@dcrocker.net>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]> <4D192FF8.1030706@dcrocker.net>
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] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 02:36:15 -0000

--On Monday, December 27, 2010 4:31 PM -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

>...
> This is why I think the specifications should use Unicode when
> they mean the rich set of text characters, and UTF-8 when
> talking about the most popular encoding of those characters
> into an 8-bit form.  (As noted, there really are a variety of
> other encodings, including some that are idiosynchratic.)

Dave,

In case it wasn't clear, I agree that the above would be a good
idea.  The more difficult problem is how to discuss "ASCII
versus Unicode" since the collection of characters that make up
ASCII is a proper subset of the collection that makes up
Unicode, just as the set of ASCII single-octet code points as
described, e.g., in RFC 20, is a subset of Unicode expressed in
UTF-8 (where the ASCII subset of Unicode is the only set of code
points expressed in exactly one octet.

So, to be more specific, while I agree with you that Unicode
should be used for the abstract set of character and UTF-8 only
when that particular encoding is intended, "ASCII versus
Unicode" and "ASCII versus Unicode are ultimately equally
incorrect.

   john




From dhc2@dcrocker.net  Mon Dec 27 20:04:27 2010
Return-Path: <dhc2@dcrocker.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 297E03A6908 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level: 
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 vArr9qHtXW3p for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:04:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 492903A683F for <ima@ietf.org>; Mon, 27 Dec 2010 20:04:26 -0800 (PST)
Received: from [192.168.1.75] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBS46OTr011663 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2010 20:06:30 -0800
Message-ID: <4D19623F.3040804@dcrocker.net>
Date: Mon, 27 Dec 2010 20:06:23 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>	<68655A9F86D4BE7ED933F8A6@[192.168.1.128]>	<4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@[192.168.1.128]>
In-Reply-To: <9B48F59821946F2EA2DCDEA0@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 27 Dec 2010 20:06:31 -0800 (PST)
Cc: ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 28 Dec 2010 04:04:27 -0000

On 12/27/2010 6:38 PM, John C Klensin wrote:
>     The more difficult problem is how to discuss "ASCII
> versus Unicode" since the collection of characters that make up
> ASCII is a proper subset of the collection that makes up
> Unicode,

That's why I cited that fact in my review and my recent note.

Nonetheless, "ASCII" refers both to a semantic and a syntax for text characters, 
which indeed invites confusion.

Still, ASCII versus Unicode refers to the semantic distinction between legacy 
email versus the enhanced version that is the goal of the working group.


> So, to be more specific, while I agree with you that Unicode
> should be used for the abstract set of character and UTF-8 only
> when that particular encoding is intended,

ok.


>  "ASCII versus
> Unicode" and "ASCII versus Unicode are ultimately equally
> incorrect.

Well, it is essential to make the distinction between legacy and new semantics, 
since it is the essence of the current work.

The choice of terms is a separate issue.  If you have alternative labeling, that 
would be great to consider.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From klensin@jck.com  Mon Dec 27 20:15: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 37ABF3A6915 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 qDYZg8MzKJ1s for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:15:29 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 3E1963A683F for <ima@ietf.org>; Mon, 27 Dec 2010 20:15:29 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXR0A-0003n9-0Q; Mon, 27 Dec 2010 23:17:34 -0500
X-Vipre-Scanned: 0789A179001DEB0789A2C6-TDI
Date: Mon, 27 Dec 2010 23:17:32 -0500
From: John C Klensin <klensin@jck.com>
To: dcrocker@bbiw.net
Message-ID: <61939C011F6BB4A93749804C@[192.168.1.128]>
In-Reply-To: <4D19623F.3040804@dcrocker.net>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@[192.168.1.128]> <4D19623F.3040804@dcrocker.net>
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] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 04:15:30 -0000

--On Monday, December 27, 2010 8:06 PM -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

>>  "ASCII versus
>> Unicode" and "ASCII versus Unicode are ultimately equally
>> incorrect.
> 
> Well, it is essential to make the distinction between legacy
> and new semantics, since it is the essence of the current work.

yes.  That was what people were trying to do with "ASCII versus
UTF-8".  As you point out, that doesn't work well.  "ASCII
versus Unicode" really doesn't work any better.

> The choice of terms is a separate issue.

Indeed.

>  If you have
> alternative labeling, that would be great to consider.

I hope someone in the WG will have a good suggestion.   If not,
we may be back to "ASCII" versus "non-ASCII" as the disjoint
pair, "Unicode"  to describe the international CCS (inclusive of
ASCII), and "UTF-8" to describe the particular encoding that is
used for this protocol and recommended by RFC 2277 (a
recommendation that is reinforced by draft-iab-idn-encoding and
other more recent work).

    john




From Shawn.Steele@microsoft.com  Mon Dec 27 20:52:07 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 2E5563A6908 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:52:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.369
X-Spam-Level: 
X-Spam-Status: No, score=-10.369 tagged_above=-999 required=5 tests=[AWL=0.230, 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 rhiyNqH10-jT for <ima@core3.amsl.com>; Mon, 27 Dec 2010 20:52:05 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id D3CDE3A683F for <ima@ietf.org>; Mon, 27 Dec 2010 20:52:05 -0800 (PST)
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (157.54.80.67) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 27 Dec 2010 20:54:09 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.01.0255.003; Mon, 27 Dec 2010 20:54:09 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: EAI review topic: VRFY/EXPN 
Thread-Index: AQHLpktDRww7oS2QxkiKoXqfkSEOrg==
Date: Tue, 28 Dec 2010 04:54:09 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B43C3F@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 28 Dec 2010 04:52:07 -0000

SSdtIGEgYml0IGNvbmZ1c2VkIGFib3V0IFZSRlkvRVhQTi4gIFRoZXkgYXJlIGJvdGggcG90ZW50
aWFsIHZlY3RvcnMgZm9yIGJydXRlIGZvcmNlIGRldGVybWluYXRpb24gdGhhdCBhY2NvdW50cyBl
eGlzdC4gIEknbSBub3Qgc3VyZSB3aGF0IHRoZSB2YWx1ZSBpcyBmb3IgYWRkaW5nIHRoYXQgc3Bh
bW1lciBzdXBwb3J0IHRvIEVBST8gIFNpbmNlIHdlJ3JlIGRpc2N1c3NpbmcgaXQgYW55d2F5LCBJ
J2QgYmUgaGFwcHkganVzdCBkcm9wcGluZyB0aG9zZS4NCg0KLVNoYXduDQoNCu+jou+jkO+jp++j
myDvo6Lvo6Pvo5fvo5Tvo5kNCmh0dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZQ==

From Shawn.Steele@microsoft.com  Mon Dec 27 21:00: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 EA7533A683E for <ima@core3.amsl.com>; Mon, 27 Dec 2010 21:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.303
X-Spam-Level: 
X-Spam-Status: No, score=-10.303 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152]
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 sByB6f1q5s+2 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 21:00:16 -0800 (PST)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 86F063A683F for <ima@ietf.org>; Mon, 27 Dec 2010 21:00:16 -0800 (PST)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 27 Dec 2010 21:02:21 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.01.0255.003; Mon, 27 Dec 2010 21:02:21 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Unicode vs. UTF-8 / Encoding vs. Representation
Thread-Index: AQHLpkwbTmdHQcqhfE29Tc0GMPzL0A==
Date: Tue, 28 Dec 2010 05:02:20 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B43C5F@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 05:00:18 -0000

RldJVzogSSdtIGhhcHB5IGNsYXJpZnlpbmcgVVRGLTggZW5jb2RpbmcgdnMgVW5pY29kZSBjaGFy
YWN0ZXIgcmVwZXJ0b2lyZS4gIEkgbWlzc2VkIHdoYXRldmVyIHRoZSBwcm9ibGVtIGlzIHdpdGgg
IkFTQ0lJIHZzIFVURi04Ij8gIEkgZG9uJ3QgbGlrZSAiQVNDSUkgdnMgbm9uLUFTQ0lJIiBhcyBp
dCB3b3VsZCBpbXBseSBvdGhlciBlbmNvZGluZ3MgbWlnaHQgYmUgdmFsaWQsIGFuZCBhIGJpZyBn
b2FsIG9mIHRoZSBXRyBpcyB0byBkZXByZWNhdGUgb3RoZXIgZW5jb2RpbmdzIGZvciBFQUkgdG8g
YWxsZXZpYXRlIHRoZSBjb25mdXNpb24vcHJvYmxlbXMgYXJvdW5kIGVuY29kaW5ncy4NCg0KSW4g
dGhlIGRpc2N1c3Npb24gdGhlcmUgd2FzIHNvbWUgZ2VuZXJhbCBjb21tZW50cyBhcm91bmQgdGhl
ICJvbGRlciIgZXhpc3RpbmcgZW52aXJvbm1lbnQuICBJTU8gRUFJIHJlcXVpcmVzIHVwZGF0ZXMg
dG8gdW5kZXJzdGFuZCB0aGUgYWRkcmVzc2VzLCBzbyBJJ20gbm90IHRlcnJpYmx5IHdvcnJpZWQg
YWJvdXQgcHJvdmlkaW5nIHN1cHBvcnQgZm9yIHRoaW5ncyB0aGF0IGNhbiBiZSBoYW5kbGVkIGJ5
IHJlcXVpcmluZyB0aGUgdXNlIG9mIFVURi04IHRocm91Z2hvdXQuICBFQUkgc2VuZGVycyBhbmQg
cmVjZWl2ZXJzIHdvdWxkIGhhdmUgdG8gdW5kZXJzdGFuZCB0aGF0IHN0dWZmIGFueXdheS4NCg0K
LVNoYXduDQoNCu+jou+jkO+jp++jmyDvo6Lvo6Pvo5fvo5Tvo5kNCmh0dHA6Ly9ibG9ncy5tc2Ru
LmNvbS9zaGF3bnN0ZQ==

From yangwooko@gmail.com  Mon Dec 27 22:21:59 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 622713A6924 for <ima@core3.amsl.com>; Mon, 27 Dec 2010 22:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.825
X-Spam-Level: 
X-Spam-Status: No, score=-2.825 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 Yg9wBcloSrCi for <ima@core3.amsl.com>; Mon, 27 Dec 2010 22:21:57 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 2212F3A6923 for <ima@ietf.org>; Mon, 27 Dec 2010 22:21:57 -0800 (PST)
Received: by qyj19 with SMTP id 19so9610717qyj.10 for <ima@ietf.org>; Mon, 27 Dec 2010 22:24:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=S1FmXebQXfxL31tVhaggQUf4+yMq2PUjG3SbfwvVbOc=; b=SXnFiRvsiXN1NVmoCGsnbVkCvbzqlZKF/9M4IYEz17RTaWcys8NNoTxdOfWCU7jWJk TAUcm5/sBb+n/CPdvnbtWU375s3ocO76npGWGp4kyL8bdVsNPWPMgp3A3elQcrdLJgoo z0I44OE8/PmKw5LAT4nRzAzsQH591IHu75HZ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=BcQsv1wCGXqfUA0Yk2ucK0U3tRnyDke/r2VDftf0SaMf7uQES5k2oi5kLwkyMAOZsa ek/542rw2iYpHfIOlguaxlb6t3J//CDTWu7ymVQJ4LyajNnLCqOaFHES2Re9A65V+a5F Y+4LLei/gNu7EdzrpZx616iWTsWKn8JiYEzGg=
Received: by 10.224.67.12 with SMTP id p12mr12741826qai.57.1293517441932; Mon, 27 Dec 2010 22:24:01 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Mon, 27 Dec 2010 22:23:41 -0800 (PST)
In-Reply-To: <61939C011F6BB4A93749804C@192.168.1.128>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Tue, 28 Dec 2010 15:23:41 +0900
X-Google-Sender-Auth: hR7kukci2yN834Q0CcvBZ2ZnaWk
Message-ID: <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com>
To: John C Klensin <klensin@jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: dcrocker@bbiw.net, ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 06:21:59 -0000

On Tue, Dec 28, 2010 at 1:17 PM, John C Klensin <klensin@jck.com> wrote:
>> =C2=A0If you have
>> alternative labeling, that would be great to consider.
>
> I hope someone in the WG will have a good suggestion. =C2=A0 If not,
> we may be back to "ASCII" versus "non-ASCII" as the disjoint
> pair, "Unicode" =C2=A0to describe the international CCS (inclusive of
> ASCII), and "UTF-8" to describe the particular encoding that is
> used for this protocol and recommended by RFC 2277 (a
> recommendation that is reinforced by draft-iab-idn-encoding and
> other more recent work).

I hope so too. But I don't expect that we are going to have a nice
answer to this soon enough. If it still significantly matters, will it
be useful to list up the cases of possible confusions when current
terminogies are used? With the list, we may be able to add some notes
to one of our documents (possibly framework doc)  to address the known
possible confusions.

--=20
a human known as yangwooko@gmail.com @ gtalk

From chl@clerew.man.ac.uk  Tue Dec 28 04:17:59 2010
Return-Path: <chl@clerew.man.ac.uk>
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 ED0733A695A for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:17:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.238
X-Spam-Level: 
X-Spam-Status: No, score=-4.238 tagged_above=-999 required=5 tests=[AWL=-0.639, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 kyimpXkc4t3b for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:17:58 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id 1C8E63A6959 for <ima@ietf.org>; Tue, 28 Dec 2010 04:17:24 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 6DF2E21F1E; Tue, 28 Dec 2010 12:11:58 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Tue, 28 Dec 2010 12:11:58 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBSCBuDr025126; Tue, 28 Dec 2010 12:11:58 GMT
Date: Tue, 28 Dec 2010 12:11:56 -0000
To: "John C Klensin" <klensin@jck.com>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <E14011F8737B524BB564B05FF748464A11B3FD33@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1394CD.5060509@dcrocker.net> <op.vodha3k56hl8nm@clerew.man.ac.uk> <78A98936A90EDFAE0C8EC560@[192.168.1.128]>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vofat61x6hl8nm@clerew.man.ac.uk>
In-Reply-To: <78A98936A90EDFAE0C8EC560@[192.168.1.128]>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d19d40e.a96b-1464-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] draft review of: draft-ietf-eai-rfc5336bis-07.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, 28 Dec 2010 12:18:00 -0000

On Mon, 27 Dec 2010 17:06:24 -0000, John C Klensin <klensin@jck.com> wrote:

> Charles,
>
> I know that you (or your mail software) are inclined to strip
> secondary addresses when you reply to mailing list posting.
> Often that is useful.

Indeed. Some people (myself included) prefer NOT to receive personal  
copies of messages that are also sent to a mailing list. Other people take  
exactly the opposite view. You can't please everybody _;( .

> ...  But, for you and others with similar
> habits/ systems please keep in mind that most of the reviewers
> in this round are not on the IAM list -- I don't remember if Ned
> is, Dave certainly is not unless he subscribed in the last week
> or two.

OK, point taken, and I am happy to use "reply to all" when I know that  
some particular person in an occasional visitor not actually subscribed to  
the list. But in the case of Dave and Ned, Dave has confirmed he is now  
subscribed and Ned submitted a response to a message I had sent to the  
list only, so I presume he is now subscribed also. But I shall watch out  
for future problems of this nature.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From chl@clerew.man.ac.uk  Tue Dec 28 04:19:58 2010
Return-Path: <chl@clerew.man.ac.uk>
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 13E363A6959 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:19:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.167
X-Spam-Level: 
X-Spam-Status: No, score=-4.167 tagged_above=-999 required=5 tests=[AWL=-0.568, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 wRZi0C56n3Oa for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:19:57 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id DAC213A6879 for <ima@ietf.org>; Tue, 28 Dec 2010 04:19:36 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 5884922104 for <ima@ietf.org>; Tue, 28 Dec 2010 12:21:41 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Tue, 28 Dec 2010 12:21:41 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBSCLeHD026066 for <ima@ietf.org>; Tue, 28 Dec 2010 12:21:41 GMT
Date: Tue, 28 Dec 2010 12:21:40 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk> <4D18EFCD.6000309@dcrocker.net>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vofbaeb86hl8nm@clerew.man.ac.uk>
In-Reply-To: <4D18EFCD.6000309@dcrocker.net>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d19d655.7da5-102b-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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, 28 Dec 2010 12:19:58 -0000

On Mon, 27 Dec 2010 19:58:05 -0000, Dave CROCKER <dhc2@dcrocker.net> wrote:

> That is, the fact that an SMTP option is involved means that the goal is  
> to move the entire email infrastructure over to Unicode support.  Both  
> sides of the SMTP exchange need to know whether that move has taken  
> place, without having to guess or do deep inspection.

Clearly the client needs to know what the server will accept, but I am  
still not clear why the server needs to know what the client supports  
(i.e. why a full two-way handshake is needed. Perhaps you could provide an  
example.
>
> It also happens that an option to the MAIL command is cheap, so why not  
> do it?

Yes, I have no great aversion to a MAIL option as suggested, and the way  
this discussion is going it seems likely that the WG is going to change  
its mind on that. My aim in this thread is to establish exactly what will  
be gained by so doing, since in most situations it is not needed.

I mentioned one case where it _would_ help in my reply to Ned, and I see  
Barry has now identified another.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From ajs@crankycanuck.ca  Tue Dec 28 04:21:26 2010
Return-Path: <ajs@crankycanuck.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 B37EB3A6959 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 fmfhjxenGfJc for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:21:26 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id E30A03A6879 for <ima@ietf.org>; Tue, 28 Dec 2010 04:21:25 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 799E31ECB41D for <ima@ietf.org>; Tue, 28 Dec 2010 12:23:30 +0000 (UTC)
Date: Tue, 28 Dec 2010 07:23:25 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: ima@ietf.org
Message-ID: <20101228122325.GA81417@shinkuro.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@[192.168.1.128]> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <61939C011F6BB4A93749804C@[192.168.1.128]>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 12:21:26 -0000

On Mon, Dec 27, 2010 at 11:17:32PM -0500, John C Klensin wrote:

> I hope someone in the WG will have a good suggestion.   If not,
> we may be back to "ASCII" versus "non-ASCII" as the disjoint
> pair, "Unicode"  to describe the international CCS (inclusive of
> ASCII), and "UTF-8" to describe the particular encoding that is
> used for this protocol and recommended by RFC 2277 (a
> recommendation that is reinforced by draft-iab-idn-encoding and
> other more recent work).

It seems to me that one could take a cue from the IDNA work, which
differentiated A-label, U-label, LDH-label, and so on.

I haven't thought about this too carefully, have barely had time to
follow the discussion, and won't have time to think about it much more
for the next 3 weeks, but perhaps something like "A-set" for the
ASCII-only characters, "U-set" for all Unicode characters, and (ugly)
"X-set" for the set of characters that are in Unicode eXcluding the
ASCII subset?  I know that introducing and rigorously defining new
terms is hard (to return to the IDNA analogy, it took a _lot_ of time
to work out those precise definitions), but it seems that confusion
may continue otherwise.

Feel free to point and laugh.  This might just be a bad idea.

A

-- 
Andrew Sullivan
ajs@crankycanuck.ca

From chl@clerew.man.ac.uk  Tue Dec 28 04:35:49 2010
Return-Path: <chl@clerew.man.ac.uk>
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 2C1E73A6959 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[AWL=-0.511,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 RjBB5fHCwlFv for <ima@core3.amsl.com>; Tue, 28 Dec 2010 04:35:48 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id 97EA93A6879 for <ima@ietf.org>; Tue, 28 Dec 2010 04:35:35 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 11EE2220C9 for <ima@ietf.org>; Tue, 28 Dec 2010 12:37:40 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Tue, 28 Dec 2010 12:37:40 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBSCbd3a027027 for <ima@ietf.org>; Tue, 28 Dec 2010 12:37:40 GMT
Date: Tue, 28 Dec 2010 12:37:39 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com> <3F5293BF906846C89013734B3D6262D9@upstairs> <7C0660F7DFFE9C1990252217@[192.168.1.128]>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vofb01pj6hl8nm@clerew.man.ac.uk>
In-Reply-To: <7C0660F7DFFE9C1990252217@[192.168.1.128]>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d19da14.171c-1373-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] [apps-discuss] RFC5336 and VRFY/EXPN (was: Re: apps-team	review of draft-ietf-eai-rfc5336bis)
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, 28 Dec 2010 12:35:49 -0000

On Mon, 27 Dec 2010 18:49:06 -0000, John C Klensin <klensin@jck.com> wrote:

> That is one issue on the side of "new command".  If one now
> decides to require EHLO first, then all existing uses of VRFY
> without it (which conform perfectly well to 5321 and all of its
> predecessors) become invalid,  That is pretty uncomfortable to
> me.  By contrast, if one creates the new command, then, if the
> response to EHLO includes some sort of EXTENDED-VRFY capability
> (see below),  one could have:
>
> 	-- VRFY without EHLO as requesting the 5321 behavior
> 	(with or without non-conforming extensions or
> 	flexibility and with responses limited to ASCII).
> 	
> 	-- EHLO, then VRFY as requesting the 5321 behavior,
> 	identical to that above.
> 	
> 	-- EHLO, then New-VRFY as requiring a strict Atom or
> 	Quoted-string optionally followed by a parameter list.

I am still not clear what the precise difficulty is that we are  
addressing. Writing
     VRFY John Klensin
and finding it doesn't work is a problem with the present legacy setup and  
it is not our job to fix it (though fixing it as a byproduct of some other  
fix would be OK).

What we _are_ concerned with is

     VRFY rené@example.com

for which we _do_ need some extension. But why cannot we just say that if  
you want to send that VRFY then you MUST do an EHLO first to ensure that  
UTF8SMTPbis is available, in which case you know that the extension  
permitting "rené" is available. This leaves the legacy behaviour (not  
sending EHLO first and hence not being allowed to say "rené") untouched.  
And no need for any New-VRFY.

Or is what I am suggesting what you intended to convey by your second  
option above?

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From dcrocker@bbiw.net  Tue Dec 28 09:04:10 2010
Return-Path: <dcrocker@bbiw.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 146A63A681B for <ima@core3.amsl.com>; Tue, 28 Dec 2010 09:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 9MR6wioB3bKv for <ima@core3.amsl.com>; Tue, 28 Dec 2010 09:04:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 95E733A6890 for <ima@ietf.org>; Tue, 28 Dec 2010 09:04:08 -0800 (PST)
Received: from [192.168.1.75] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBSH677U031122 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2010 09:06:13 -0800
Message-ID: <4D1A18FB.3020604@bbiw.net>
Date: Tue, 28 Dec 2010 09:06:03 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dcrocker@bbiw.net, ima@ietf.org
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>	<68655A9F86D4BE7ED933F8A6@[192.168.1.128]>	<4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@[192.168.1.128]> <4D19623F.3040804@dcrocker.net>
In-Reply-To: <4D19623F.3040804@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 28 Dec 2010 09:06:13 -0800 (PST)
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 17:04:10 -0000

Folks,

It occurs to me that we could make do with existing terms.  The challenge is to 
use them carefully:


               | Representation |  Encoding  |
               +----------------+------------+
               |                |            |
        Legacy |     ASCII      |   7-bit    |
               |                |            |
               +----------------+------------+
               |                |            |
International |    Unicode     |   UTF-8    |
               |                |            |
               +----------------+------------+



The change in our reference is to stop using ASCII to refer to an encoding.  For 
Internet ASCII, the formal definition usually is "7-bit ASCII in an 8-bit field, 
with the high bit off", but "7-bit" should suffice...

Thoughts?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From klensin@jck.com  Tue Dec 28 10:23:42 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 21AEC3A68AB for <ima@core3.amsl.com>; Tue, 28 Dec 2010 10:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 LbznHlKRJpT1 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 10:23:41 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id BE38E3A68A6 for <ima@ietf.org>; Tue, 28 Dec 2010 10:23:40 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXeEq-000D4D-FV; Tue, 28 Dec 2010 13:25:36 -0500
X-Vipre-Scanned: 0A920AF2001DEB0A920C3F-TDI
Date: Tue, 28 Dec 2010 13:25:35 -0500
From: John C Klensin <klensin@jck.com>
To: Yangwoo Ko <newcat@icu.ac.kr>
Message-ID: <0D625A27294258D00E95152A@[192.168.1.128]>
In-Reply-To: <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@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
Cc: Andrew Sullivan <ajs@shinkuro.com>, dcrocker@bbiw.net, ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 28 Dec 2010 18:23:42 -0000

--On Tuesday, December 28, 2010 3:23 PM +0900 Yangwoo Ko
<newcat@icu.ac.kr> wrote:

> On Tue, Dec 28, 2010 at 1:17 PM, John C Klensin
> <klensin@jck.com> wrote:
>>> =C2=A0If you have
>>> alternative labeling, that would be great to consider.
>>=20
>> I hope someone in the WG will have a good suggestion. =C2=A0 =
If
>> not, we may be back to "ASCII" versus "non-ASCII" as the
>> disjoint pair, "Unicode" =C2=A0to describe the international =
CCS
>> (inclusive of ASCII), and "UTF-8" to describe the particular
>> encoding that is used for this protocol and recommended by
>> RFC 2277 (a recommendation that is reinforced by
>> draft-iab-idn-encoding and other more recent work).
>=20
> I hope so too. But I don't expect that we are going to have a
> nice answer to this soon enough. If it still significantly
> matters, will it be useful to list up the cases of possible
> confusions when current terminogies are used? With the list,
> we may be able to add some notes to one of our documents
> (possibly framework doc)  to address the known possible
> confusions.

If we try to push this definitional issue very far, it is far
more complicated than has been suggested so far.  For the work
of the EAI WG, I suggest that there are two practical
possibilities:

	(1) The current terminology is not precisely correct
	given other, Standard, usage but, with small
	adjustments, can be used in the documents with some
	explicit local definitions.
	
	(2) In the tradition of John Tukey and others, we invent
	entirely new language that is precisely-defined locally.
	As Andrew points out, that is precisely what IDNA2008
	ended up having to do after struggling with a variation
	on this problem in the DNS space.

Despite Andrew's misgivings, the definitional problem here is
not nearly as hard as that for IDNA.  I think either of the
above would be possible without significantly delaying the WG.
However, the first would be a lot safer in terms of the risk of
introducing new errors as terminology is redefined and then
applied (a problem we certainly got into with IDNA).

Dave suggested in a later note...

>...
> The change in our reference is to stop using ASCII to refer to
> an encoding.  For Internet ASCII, the formal definition
> usually is "7-bit ASCII in an 8-bit field, with the high bit
> off", but "7-bit" should suffice...

Unfortunately, this doesn't work either if one aspires to the
kind of precision for which you seem to be asking.  First of
all, the ANSI definition of ASCII contains both a character
repertoire and an encoding and is, if I recall, fairly explicit
about that.   ANSI also didn't define anything about ASCII in
longer data fields than 7 bits, so the encoding itself is
two-levels: (i) the ASCII repertoire specified as a seven-bit
encoding and (ii) the embedding of [intrinsically 7-bit] ASCII
into an 8-bit field.

While there has never been such a thing as "8-bit ASCII" from a
standards point of view, that term, or "ASCII-8", have often
been used both to describe embedding of ASCII into octets _and_
as the name of an extended, ASCII-based, character repertoire
and encoding that is essentially Latin-1 or ISO 8859-1.   While
the ASCII repertoire is a proper subset of the Unicode
repertoire and (i) the ASCII code points have the same integer
values as the corresponding Unicode code points if the left
octet is stripped from the latter and (ii) when Unicode is
encoded in UTF-8, the octets corresponding to the ASCII
repertoire have the same values as the ASCII code points
embedded in octets with a leading zero bit, there are other CCSs
for which ASCII (both the repertoire and the leading-zero
imbedding) are proper subsets --including the entire ISO 8859
family.   All of the character repertoires of the 8859 standards
are subsets of the Unicode repertoires, but only 8859-1 bears an
obvious relationship to the Unicode code point assignments (and,
in UTF-8, the top half of the 8859-1 repertoire turns into two
octets and the relationship to the original encodings disappears
entirely.

We have usually used "ASCII [embedded] in an 8-bit field, with
the high bit off" on the Internet (indeed, that is part of the
problem that RFC 20 tried to solve), but we have had ASCII
floating around in 7-bit form (not stored in octets) and there
is have been two other octet embeddings that puts the spare bit
somewhere in the middle (one of them as a zero and one as a
parity bit).  There are also 7-bit encodings of other things
floating around, including the encoding described in RFC 2152
(and its predecessor 1642) and the 1642 modification described
in IMAP4rev1 [RFC 2060], a modification not incorporated in the
1642->2152 update.

So, no, "7-bit" doesn't do it either.

Dave's note suggest that a general terminology solution is
needed, a view with which I agree.  But, just as the EAI WG has
been urged to avoid doing work that extends beyond the narrow
scope of what is specifically needed to email address and header
internationalization, an effort to sort out character set
repertoire, definition, encoding, and embedding issues in a
general and appropriate way should not be imposed on the EAI WG.
It might be appropriate to do so by reopening and revising RFC
3536 (which I note uses some terminology that is now considered
obsolete enough to have caused loud protests when used in other
documents) or by initiating a separate effort, but it would be,
IMO, unreasonable and unfair to delay EAI progress for that work
to be initiated and completed.  As Andrew said (and the above
explanation should reinforce), "introducing and rigorously
defining new terms is hard".

    john


From klensin@jck.com  Tue Dec 28 11:42:46 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 08AA13A68BE for <ima@core3.amsl.com>; Tue, 28 Dec 2010 11:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 v0cj2-aBMytp for <ima@core3.amsl.com>; Tue, 28 Dec 2010 11:42:44 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 2324B3A68B7 for <ima@ietf.org>; Tue, 28 Dec 2010 11:42:44 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXfTP-000E01-1D; Tue, 28 Dec 2010 14:44:43 -0500
X-Vipre-Scanned: 0ADA7844001DEB0ADA7991-TDI
Date: Tue, 28 Dec 2010 14:44:41 -0500
From: John C Klensin <klensin@jck.com>
To: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Message-ID: <B2DA8473E8F67A3F495A9D67@[192.168.1.128]>
In-Reply-To: <op.vofb01pj6hl8nm@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com> <3F5293BF906846C89013734B3D6262D9@upstairs> <7C0660F7DFFE9C1990252217@[192.168.1.128]> <op.vofb01pj6hl8nm@clerew.man.ac.uk>
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] [apps-discuss] RFC5336 and VRFY/EXPN (was: Re:	apps-team	review of draft-ietf-eai-rfc5336bis)
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, 28 Dec 2010 19:42:46 -0000

--On Tuesday, December 28, 2010 12:37 PM +0000 Charles Lindsey
<chl@clerew.man.ac.uk> wrote:

> On Mon, 27 Dec 2010 18:49:06 -0000, John C Klensin
> <klensin@jck.com> wrote:
>=20
>> That is one issue on the side of "new command".  If one now
>> decides to require EHLO first, then all existing uses of VRFY
>> without it (which conform perfectly well to 5321 and all of
>> its predecessors) become invalid,  That is pretty
>> uncomfortable to me.  By contrast, if one creates the new
>> command, then, if the response to EHLO includes some sort of
>> EXTENDED-VRFY capability (see below),  one could have:
>>=20
>> 	-- VRFY without EHLO as requesting the 5321 behavior
>> 	(with or without non-conforming extensions or
>> 	flexibility and with responses limited to ASCII).
>> 	
>> 	-- EHLO, then VRFY as requesting the 5321 behavior,
>> 	identical to that above.
>> 	
>> 	-- EHLO, then New-VRFY as requiring a strict Atom or
>> 	Quoted-string optionally followed by a parameter list.
>=20
> I am still not clear what the precise difficulty is that we
> are addressing. Writing
>      VRFY John Klensin
> and finding it doesn't work is a problem with the present
> legacy setup and it is not our job to fix it (though fixing it
> as a byproduct of some other fix would be OK).

Right.

> What we _are_ concerned with is
>=20
>      VRFY ren=C3=A9@example.com

We are actually concerned with two cases (if one considers the
above to be the same case if "@example.com" is left off).  The
other one is=20
       VRFY Rene
(note no accent), with the understanding that, e.g., either
       rene@mailhost1.example.com
or
       rene@mailhost2.example.com
could come back.

> for which we _do_ need some extension. But why cannot we just
> say that if you want to send that VRFY then you MUST do an
> EHLO first to ensure that UTF8SMTPbis is available, in which
> case you know that the extension permitting "ren=C3=A9" is
> available.=20

The problem is (mostly) not what the client sends but what the
server can return.   Suppose the server advertises UTF8SMTPbis
and the client sends "VRFY rene" (all-ASCII).  Now the server
doesn't know whether it is plausible to return an address
containing non-ASCII characters or not: the client has to
somehow give it permission to do that.

Modulo however one feels about heuristics, one would be ok with
UTF8SMTP in the EHLO response to _send_ "VRFY ren=C3=A9" (the =
client
knows that the server supports the EAI extensions) and the
server could deduce that, if the client is sending non-ASCII, it
can accept a non-ASCII response.

But, if the client sense all-ASCII, the server can't figure out
what it can accept in a response unless the client also sends
along some sort of "I can accept a non-ASCII response if you
would like to give me one".  Hence the need for a parameter.

Even in the "ren=C3=A9" case, the argument about whether or not =
the
parameter is desirable comes down to a situation much like the
discussion of parameters on the MAIL command.  The difference is
that they heuristics are easy for "ren=C3=A9" and don't work at =
all
for "rene"; for the MAIL case, they are very easy if either the
MAIL command or the first RCPT command contains a non-ASCII
address and are possible, but very hard, if the message has
non-ASCII in the headers but no clue in the envelope.

The problem with=20
   VRFY John Klensin
is that it often does "work" in the legacy setup.  As a leftover
from 821 and massive confusion about the "\" escape, some will
treat it as equivalent to
   VRFY "John\ Klensin"
while others will treat it as a syntax error.  The first is a
little more liberal application of the robustness principle than
I would recommend, but it "works".  The second works too -- it
is a syntax error.

But, if the server advertises UTF8SMTPbis, it could certainly be
telling the client that it expects an 5321 interpretation of the
VRFY command, for which the syntax is unambigious.   For a
client who actually understands EAI, that gives
   VRFY John
an unambiguous interpretation (don't return non-ASCII in the
address)
   VRFY John UTF8SMTPbis
is unambiguous too -- the server is being asked to verify "John"
but can return non-ASCII in the address if needed.=20
   VRFY John Klensin
also has an unambiguous interpretation as a syntax error and
   VRFY ren=C3=A9 UTF8SMTPbis
is just fine too.

But suppose the client doesn't know anything about i18n and just
ignores the UTF8SMTPbis announcement (as it is obligated to
ignore any extension announcement it doesn't recognize).   Now,
when it sends=20
    VRFY John UTF8SMTPbis
the server really doesn't know --because it doesn't know whether
the client is EAI-aware or not-- whether this was intended to be
the EAI form, with a parameter enabling a non-ASCII reply, as
above or whether it is a broken (but common) way to express a
request for information about "John" with a rather odd-looking
second name.

If you are still confused about that much, the next part will
not make sense, but let me try anyway.

There is a problem here that we just didn't have when we added
parameters to MAIL and RCPT (and, for that matter, to DATA).  In
the first two cases, 821 and its successors defined the base
syntax is containing only an address in brackets.  All of the
weird backslash-escape stuff could appear there too, but it was
rare and one still had the brackets, so anything past the right
bracket was guaranteed to be a parameter (or so severely broken
that it could be discounted). =20

Some folks were stupid and/or careless enough to omit the
brackets in their implementations, but I have never seen an
instance in the wild of "no brackets but embedded space in the
address"; when SMTP server implementations decided to accept
unbracketed strings, they would generally give up if they then
encountered spaces.   (I do remember writing a test case once
for the equivalent of=20
   MAIL FROM: foo bar@example.com
my recollection is that I didn't learn anything interesting,
i.e., that most server implementations rejected it as a syntax
error although there might have been one that resolved it into=20
   MAIL FROM:<foo\ bar@example.com>=20
)

But VRFY isn't like that.  We don't have a clear,
widely-respected, "if there is anything past this point in the
string it is clearly a syntax error or EMSMTP-enabled
parameter", so there is always a possibility of the parameter
being misinterpreted as part of the string to be verified
because the client sends something odd (and non-conforming but
common) no matter what the server says.  If you want to
guarantee that whatever the client sends can be interpreted
unambiguously, then one needs an unambiguous client announcement
prior to the VRFY command and separate from whatever shows up in
it, e.g., a MAIL parameter (requiring that VRFY be sent, not
only after EHLO but after MAIL) or a separate
"I'm-an-EAI-conforming-client" command.   Or one eliminates the
ambiguity completely with a separate command that cannot be sent
unless some relevant extension is specified that comes with a
rigid syntax and provision for parameters.

On the other hand, something bizarre-looking like "UTF8SMTP" is
going to be safe enough in practice because it will always (or
almost always) yield an error message if interpreted as part of
the name to be verified.   If the WG concludes on that basis
that=20
   VRFY Potentially-Quoted-String UTFSMTP
is good enough that it can safely be used after the server has
announced EAI support, I'm not going to lose a lot of sleep over
the risk and edge cases.

> This leaves the legacy behaviour (not sending EHLO
> first and hence not being allowed to say "ren=C3=A9") =
untouched.
> And no need for any New-VRFY.

Again, the problem is not having the client send "ren=C3=A9".  =
It is
having the server send it when the client sent pure ASCII.

    john



From alexey.melnikov@isode.com  Tue Dec 28 14:20:07 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 A98ED3A695B; Tue, 28 Dec 2010 14:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 KbkoR3uOz-G1; Tue, 28 Dec 2010 14:20:06 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id ECE4F3A68E8; Tue, 28 Dec 2010 14:20:05 -0800 (PST)
Received: from [188.28.189.65] (188.28.189.65.threembb.co.uk [188.28.189.65])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TRpjAQB0Kyt8@rufus.isode.com>; Tue, 28 Dec 2010 22:22:06 +0000
Message-ID: <4D1A4414.5060103@isode.com>
Date: Tue, 28 Dec 2010 20:09: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: Ned Freed <ned.freed@mrochek.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com>
In-Reply-To: <01NVVQNSWU7U007CHU@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ned Freed <NED+eai@mauve.mrochek.com>, apps-discuss@ietf.org, ima@ietf.org, draft-ietf-eai-rfc5336bis@tools.ietf.org
Subject: Re: [EAI] RFC5336 and VRFY/EXPN
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, 28 Dec 2010 22:20:07 -0000

[With my MTA server developer hat on, not speaking as an AD]

Ned Freed wrote:

>>In addition, one must have a session for which mail transactions
>>are permitted (i.e., EHLO must have been sent) in order to use
>>any parameters at all.
>>    
>>
>
>You certainly need to send an EHLO and process the result to find out what
>extensions are allowed - guessing what combination of extensions will work most
>certainly is not a sound operational policy. And implementations are certainly
>free to only offer the extensions that have been returned in an EHLO repsonse.
>
>That said, I don't see an actual requirement in section 2.2 stating that EHLO
>must be issued before any parameters can be used. (Maybe it's somewhere else,
>but a cursory search didn't find it.) Our MTA certainly doesn't enforce this
>and AFAIK neither does sendmail, PostFix, Apache James, or qmail.
>
Isode M-Switch doesn't enforce this either.

>(Exim, OTOH, appears to.)
>  
>
>>RFC 5321, Section 4.1.4, explicitly
>>permits sending VRFY or EXPN without first having EHLO in the
>>session.  So there is another implicit requirement in all of
>>this that should almost certainly be made explicit.
>>    
>>
>There certainly should be a note saying that you need to issue an EHLO
>and check the response before attaching any parameters to VRFY/EXPN. I don't
>think a requirement that parameters not be accepted before an EHLO
>has been issued is needed.
>  
>
+1. Maybe the client has cached EHLO response from a previous connection.

>>(I think
>>this is the topic about handshaking that Dave and Shawn have
>>been circling around, but I'm not sure).
>>    
>>
>It's part of it, I think.
>  
>
>>>However, this brings up
>>>another     issue, which is that a server that supports this
>>>extension needs a way     to tell a client that doesn't that
>>>it cannot return a proper response     to VRFY/EXPN without
>>>that parameter being specified. A new SMTP error     status is
>>>needed, but the document only defines an extended status
>>>for this purpose; it doesn't specify a regular status code to
>>>use.
>>>      
>>>
>>If we go down this path, the WG clearly needs to reexamine
>>whether such a code is necessary.  I think you have made a
>>persuasive case, but I can't speak for the WG.
>>    
>>
>*It doesn't have to be a new code. OTOH, it needs to be a code that EXPN/VRFY
>don't return for other purposes, and I think if you look at the list of
>available codes a new code is needed.
>*
>
>>Indeed, this has all gotten sufficiently complex that I think
>>perhaps the WG should reexamine its decision to handle the "VRFY
>>and EXPN with possible non-ASCII responses" situation by
>>parameterizing those commands rather than introducing new
>>commands, say VRF8 and EXP8.  IIR, the WG did consider that
>>alternative (long ago) and conclude that adding a parameter was
>>the more straightforward option. But, perhaps, given the
>>various complexities that have emerged, that was not the right
>>decision.
>>    
>>
>I considered suggesting new commands, but given the need to specify
>syntax for the new commands I don't see this as any simplier
>specification-wise. In terms of implementation, a new command is actually
>a somewhat more complex - the code changes are less localized, and I suspect
>other implementations will be comparable in this regard.
>  
>
+1.

>But the minute you need some other variant on EXPN and VRFY, the alternate
>command appraoch becomes the far more complex way to do it. Now, we haven't had
>a specification come along that needed additional EXPN/VRFY parameters before
>this one, but these things have a way of showing up once you open the door and
>get people thinking about them. So I'm strongly inclined to stick with the
>parameter approach.
>  
>
+1.



From alexey.melnikov@isode.com  Tue Dec 28 14:21:03 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 6F13F3A68E8 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 14:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 yI2kVy9Llzrc for <ima@core3.amsl.com>; Tue, 28 Dec 2010 14:21:02 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 63D0F3A68E7 for <ima@ietf.org>; Tue, 28 Dec 2010 14:21:02 -0800 (PST)
Received: from [188.28.189.65] (188.28.189.65.threembb.co.uk [188.28.189.65])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TRpjQgB0K3mE@rufus.isode.com>; Tue, 28 Dec 2010 22:22:59 +0000
Message-ID: <4D1A499C.1000505@isode.com>
Date: Tue, 28 Dec 2010 20:33:32 +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: <02EB1F03BAF0ED410F97CDC6@[192.168.1.128]>
In-Reply-To: <02EB1F03BAF0ED410F97CDC6@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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, 28 Dec 2010 22:21:03 -0000

John C Klensin wrote:

>(writing as co-chair)
>  
>
[Speaking as an individual contributor. As an AD I will be Ok with 
whatever there is rough consensus for.]

>Hi.
>
>Joseph and/or I will be sending out a series of (short) notes to
>the WG mailing list identifying substantive issues that the WG
>needs to review and make decisions about.  They are going to be
>short in the hope that people will read them and read them soon,
>but there are relevant previous discussions on the mailing list,
>in the reviews, and in the long set of notes I posted earlier
>that people should try to understand before responding to the
>questions.  However, remember that the WG is supposed to be
>working quickly: these issues are in the critical path for
>anything to more forward.
>
>Question: Should we define, and require, an announcement
>parameter on the MAIL command if the sender intends to transmit
>either non-ASCII addresses or UTF-8 in headers (other than as
>encoded words)?
>  
>
Yes.

(Note I think this is just one more drop in favor of having a new SMTP 
capability for the 5336bis SMTP extension).

>Discussion references: My long note, especially item (2), which
>I hope summarizes the review comments) and a number of comments
>on-list about what is required if this header is not present.
>  
>



From alexey.melnikov@isode.com  Tue Dec 28 14:21: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 78FCA3A6965 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 14:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 8HWMSKW91jdt for <ima@core3.amsl.com>; Tue, 28 Dec 2010 14:21:05 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 7EA633A6962 for <ima@ietf.org>; Tue, 28 Dec 2010 14:21:05 -0800 (PST)
Received: from [188.28.189.65] (188.28.189.65.threembb.co.uk [188.28.189.65])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TRpjTAB0K7mG@rufus.isode.com>; Tue, 28 Dec 2010 22:23:09 +0000
Message-ID: <4D1A4A00.4080202@isode.com>
Date: Tue, 28 Dec 2010 20:35: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: Shawn Steele <Shawn.Steele@microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B43C3F@TK5EX14MBXC137.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B43C3F@TK5EX14MBXC137.redmond.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 28 Dec 2010 22:21:06 -0000

Shawn Steele wrote:

>I'm a bit confused about VRFY/EXPN.  They are both potential vectors for brute force determination that accounts exist.
>
Some implementations require use of SMTP AUTH before these commands can 
be used. Our MTA (Isode M-Switch) has a configuration option for that.

>  I'm not sure what the value is for adding that spammer support to EAI?  Since we're discussing it anyway, I'd be happy just dropping those.
>  
>



From Shawn.Steele@microsoft.com  Tue Dec 28 15:02:47 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 070BD3A68DD for <ima@core3.amsl.com>; Tue, 28 Dec 2010 15:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.385
X-Spam-Level: 
X-Spam-Status: No, score=-10.385 tagged_above=-999 required=5 tests=[AWL=0.214, 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 rN1XmYedzLqT for <ima@core3.amsl.com>; Tue, 28 Dec 2010 15:02:45 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id DCFEE3A67F7 for <ima@ietf.org>; Tue, 28 Dec 2010 15:02:44 -0800 (PST)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 28 Dec 2010 15:04:50 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0255.003; Tue, 28 Dec 2010 15:04:49 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Thread-Topic: [EAI] EAI review topic: VRFY/EXPN
Thread-Index: AQHLpt3V7wPgbgDwxka9wkRly5X7apO2eYXH
Date: Tue, 28 Dec 2010 23:04:49 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B4614A@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B43C3F@TK5EX14MBXC137.redmond.corp.microsoft.com>, <4D1A4A00.4080202@isode.com>
In-Reply-To: <4D1A4A00.4080202@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 28 Dec 2010 23:02:47 -0000

Forgive my ignorance, but us this  useful?  Like if you trust me, aren't th=
ere better was for me to get addresses?  Like from a directory or something=
?

- Shawn

Sent from my Windows Phone 7

-----Original Message-----
From: Alexey Melnikov
Sent: Tuesday, December 28, 2010 2:23 PM
To: Shawn Steele
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN


Shawn Steele wrote:

>I'm a bit confused about VRFY/EXPN.  They are both potential vectors for b=
rute force determination that accounts exist.
>
Some implementations require use of SMTP AUTH before these commands can
be used. Our MTA (Isode M-Switch) has a configuration option for that.

>  I'm not sure what the value is for adding that spammer support to EAI?  =
Since we're discussing it anyway, I'd be happy just dropping those.
>
>




From ned+ima@mrochek.com  Tue Dec 28 15:55:21 2010
Return-Path: <ned+ima@mrochek.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 302D53A68F7 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 15:55:21 -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 qgGOvr8VDbjY for <ima@core3.amsl.com>; Tue, 28 Dec 2010 15:55:19 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 93F353A68F3 for <ima@ietf.org>; Tue, 28 Dec 2010 15:55:19 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVYK3AHRDS00EDEN@mauve.mrochek.com> for ima@ietf.org; Tue, 28 Dec 2010 15:57:21 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVYGXLX10W007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Tue, 28 Dec 2010 15:57:18 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NVYK39E5FO007CHU@mauve.mrochek.com>
Date: Tue, 28 Dec 2010 15:35:25 -0800 (PST)
In-reply-to: "Your message dated Tue, 28 Dec 2010 23:04:49 +0000" <E14011F8737B524BB564B05FF748464A11B4614A@TK5EX14MBXC137.redmond.corp.microsoft.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <E14011F8737B524BB564B05FF748464A11B43C3F@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1A4A00.4080202@isode.com> <E14011F8737B524BB564B05FF748464A11B4614A@TK5EX14MBXC137.redmond.corp.microsoft.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293577676; bh=BAiz9OQhKBnrItV/DX4y4Mwy0D4vIxValqYEcMfxKG4=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=XwHVSmMydzpcKGC2zva5ceiPU4cuYjynwEnqX5x5RtJqLswVLLbt0e5av7dRqFm1v hVitETyGjNhctiCETjxQBR9MShp7BflyfNAVqSFw4txFIgXsF6gngXL6GoxYT7G2gt mLOCWIEZZEhZ2gra/+s3OgjLbznTwElCtZJCAHYY=
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 28 Dec 2010 23:55:21 -0000

> Forgive my ignorance, but us this  useful?

It's useful for infrastructure probes and checks, to the point where I've seen
several sites impose a requirement that all MTAs have VRFY/EXPN enabled.

> Like if you trust me, aren't there better was for me to get addresses?  Like
> from a directory or something?

What matters is how things are actually handled by the software routing
messages around. Peering directly into the underlying data sources
necessarily ignores the multitude of semantics implemented and applied by the
MTAs themselves.

If you really need to know how something is going to be routed, you're much
better off asking the router what it would do than trying to second guess it by
looking at a few of the data sources it uses. In our MTA, for example, the
functional specification of just the semantics that are applied to LDAP entries
during alias expansion is around 50 pages long. Do you seriously think you're
better off going at LDAP directly and having to implement all of that yourself
when you can just send a command and get the information back?

Oh, and your point about how VRFY can be used to guess addresses is mostly
specious. Given the need to reject messages as soon as possible so as to avoid
expensive and unnecessary antispam processing, address guessing can be done
using RCPT TO. I've never been entirely clear on how VRFY earned such a bad
rep, but it's mostly undeserved.

				Ned

P.S. We also support requiring authentication prior to being able to use these
commands, but I'm not sure I've ever seen anyone actually use such a setup. The
closest I've seen was access control based on the IP of the client, which we
also support.

From ned+ima@mrochek.com  Tue Dec 28 16:23:12 2010
Return-Path: <ned+ima@mrochek.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 4EF2A3A680D for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:23:12 -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 pFzv+Sc57nTT for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:23:11 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 0E0203A67F1 for <ima@ietf.org>; Tue, 28 Dec 2010 16:23:10 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVYL1VN88W00FH3B@mauve.mrochek.com> for ima@ietf.org; Tue, 28 Dec 2010 16:25:14 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVY85NSB40007FL5@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Tue, 28 Dec 2010 16:25:11 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NVYL1UIU1G007FL5@mauve.mrochek.com>
Date: Tue, 28 Dec 2010 14:21:11 -0800 (PST)
In-reply-to: "Your message dated Mon, 27 Dec 2010 15:58:44 -0500" <AANLkTinQyjbQDC8GS5q=TJrtb9O60m94Lwzwt2Q2UuQU@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk> <AANLkTinQyjbQDC8GS5q=TJrtb9O60m94Lwzwt2Q2UuQU@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293579349; bh=KFDYF26gUpW0d/Xa5HteuwuOG0Ig+h9bRxBfOThF5rY=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=Cq+pqcSsp1gV1KH+jD/fDVljyE12FVL7PRHgJGu5jN/7jeyWLH9WDV9OYA//UvbT5 rptc3jNJA6fGw5cuSf/U2SyMV6nJ9LqyRVvrhf6NOYKkOgD9swroLRw9TPLKj6veIC dGRnu47yMCE0Teq7GCjFOoHFS+MHTG1YDyaux8e0=
Cc: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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: Wed, 29 Dec 2010 00:23:12 -0000

> > However, I do not quite see the necessity for it. If some MTA announces the
> > capability UTF8SMTP, then it is declaring its willingness to accept messages
> > destined for utf-8 addresses and to do the "right thing" with any problems
> > that might arise (such as generating a bounce if some MTA further down the
> > chain finds a problem). Essentially the same as current MTAs do with ASCII
> > messages that turn out to be undeliverable.
> >
> > If some client tries to send such a message without first checking that the
> > UTF8SMTP capability has been advertised, then it is in breach of our
> > proposal, and is just like people who try to "just send 8-bits" at the
> > moment - if they strike lucky it might work, but there is no guarantee.

> That isn't quite enough.  If a message goes through a couple of MTAs
> OK, and then there comes an MTA that doesn't do UTF8SMTP, how is this
> MTA to know that the message has UTF8 and the situation needs to be
> dealt with? The submitting client knew, but we're well past that, and
> the only way to tell now, lacking some clue in the protocol, is by
> inspection of the message.

This is indeed the main value of having such a parameter. But it provides
other benefits as well - for example, an MTA may know that the forward
path for certain recipients doesn't support this extension. Such recipients
can be rejected at RCPT TO time. And the earlier the rejection happens, the
better, because the further into the infrastructure you travel, the more likely
problems are to arise on getting the notification back.

More generally, this group seems to be having difficulty on at least two
fronts. First, the current specifications still show some attachment to the
previous model, where messages were supposed to contain the information
necessary to downgrade them. The new model, where bouncing is going to be the
only option most of the time, has very different operational characteristics.
For one thing, stuff that's merely nice to have in a scenario where downgrading
is possible becomes a lot more important when downgrading is no longer an
option.

Second, there's a big difference between designing an experimental protocol and
specifying protocols for a production service. In the former case, it may be OK
to do stuff that has implementors scratching their heads and wondering how to
put it all together. But in the latter case, the shoe is really on the other
foot: The service has to sell itself on a benefits versus costs basis. So,
while there's certainly no rule in the IETF about avoiding deep inspection,
requiring it may result in serious deployment problems. And deployment of
new services is tough enough even for very simple, straightforward things,
which this set of specifications most certainly is NOT.

				Ned

From Shawn.Steele@microsoft.com  Tue Dec 28 16:24:11 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 7655B3A680D for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.394
X-Spam-Level: 
X-Spam-Status: No, score=-10.394 tagged_above=-999 required=5 tests=[AWL=0.205, 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 fIARbSdrN29D for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:24:10 -0800 (PST)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 9A83C3A67F1 for <ima@ietf.org>; Tue, 28 Dec 2010 16:24:10 -0800 (PST)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 28 Dec 2010 16:26:15 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0255.003; Tue, 28 Dec 2010 16:26:15 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Ned Freed <ned.freed@mrochek.com>
Thread-Topic: [EAI] EAI review topic: VRFY/EXPN
Thread-Index: AQHLpt3V7wPgbgDwxka9wkRly5X7apO2eYXHgAAO3CeAAAfbQA==
Date: Wed, 29 Dec 2010 00:26:14 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B47396@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B43C3F@TK5EX14MBXC137.redmond.corp.microsoft.com> <4D1A4A00.4080202@isode.com> <E14011F8737B524BB564B05FF748464A11B4614A@TK5EX14MBXC137.redmond.corp.microsoft.com> <01NVYK39E5FO007CHU@mauve.mrochek.com>
In-Reply-To: <01NVYK39E5FO007CHU@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 00:24:11 -0000

R29vZCBlbm91Z2ggZm9yIG1lLCB0aGFua3MgOikNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IE5lZCBGcmVlZCBbbWFpbHRvOm5lZC5mcmVlZEBtcm9jaGVrLmNvbV0gDQpTZW50
OiBQxY3KuywgS2VrZW1hcGEgMjgsIDIwMTAgMzozNSBQTQ0KVG86IFNoYXduIFN0ZWVsZQ0KQ2M6
IEFsZXhleSBNZWxuaWtvdjsgaW1hQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0VBSV0gRUFJIHJl
dmlldyB0b3BpYzogVlJGWS9FWFBODQoNCj4gRm9yZ2l2ZSBteSBpZ25vcmFuY2UsIGJ1dCB1cyB0
aGlzICB1c2VmdWw/DQoNCkl0J3MgdXNlZnVsIGZvciBpbmZyYXN0cnVjdHVyZSBwcm9iZXMgYW5k
IGNoZWNrcywgdG8gdGhlIHBvaW50IHdoZXJlIEkndmUgc2VlbiBzZXZlcmFsIHNpdGVzIGltcG9z
ZSBhIHJlcXVpcmVtZW50IHRoYXQgYWxsIE1UQXMgaGF2ZSBWUkZZL0VYUE4gZW5hYmxlZC4NCg0K
PiBMaWtlIGlmIHlvdSB0cnVzdCBtZSwgYXJlbid0IHRoZXJlIGJldHRlciB3YXMgZm9yIG1lIHRv
IGdldCBhZGRyZXNzZXM/ICANCj4gTGlrZSBmcm9tIGEgZGlyZWN0b3J5IG9yIHNvbWV0aGluZz8N
Cg0KV2hhdCBtYXR0ZXJzIGlzIGhvdyB0aGluZ3MgYXJlIGFjdHVhbGx5IGhhbmRsZWQgYnkgdGhl
IHNvZnR3YXJlIHJvdXRpbmcgbWVzc2FnZXMgYXJvdW5kLiBQZWVyaW5nIGRpcmVjdGx5IGludG8g
dGhlIHVuZGVybHlpbmcgZGF0YSBzb3VyY2VzIG5lY2Vzc2FyaWx5IGlnbm9yZXMgdGhlIG11bHRp
dHVkZSBvZiBzZW1hbnRpY3MgaW1wbGVtZW50ZWQgYW5kIGFwcGxpZWQgYnkgdGhlIE1UQXMgdGhl
bXNlbHZlcy4NCg0KSWYgeW91IHJlYWxseSBuZWVkIHRvIGtub3cgaG93IHNvbWV0aGluZyBpcyBn
b2luZyB0byBiZSByb3V0ZWQsIHlvdSdyZSBtdWNoIGJldHRlciBvZmYgYXNraW5nIHRoZSByb3V0
ZXIgd2hhdCBpdCB3b3VsZCBkbyB0aGFuIHRyeWluZyB0byBzZWNvbmQgZ3Vlc3MgaXQgYnkgbG9v
a2luZyBhdCBhIGZldyBvZiB0aGUgZGF0YSBzb3VyY2VzIGl0IHVzZXMuIEluIG91ciBNVEEsIGZv
ciBleGFtcGxlLCB0aGUgZnVuY3Rpb25hbCBzcGVjaWZpY2F0aW9uIG9mIGp1c3QgdGhlIHNlbWFu
dGljcyB0aGF0IGFyZSBhcHBsaWVkIHRvIExEQVAgZW50cmllcyBkdXJpbmcgYWxpYXMgZXhwYW5z
aW9uIGlzIGFyb3VuZCA1MCBwYWdlcyBsb25nLiBEbyB5b3Ugc2VyaW91c2x5IHRoaW5rIHlvdSdy
ZSBiZXR0ZXIgb2ZmIGdvaW5nIGF0IExEQVAgZGlyZWN0bHkgYW5kIGhhdmluZyB0byBpbXBsZW1l
bnQgYWxsIG9mIHRoYXQgeW91cnNlbGYgd2hlbiB5b3UgY2FuIGp1c3Qgc2VuZCBhIGNvbW1hbmQg
YW5kIGdldCB0aGUgaW5mb3JtYXRpb24gYmFjaz8NCg0KT2gsIGFuZCB5b3VyIHBvaW50IGFib3V0
IGhvdyBWUkZZIGNhbiBiZSB1c2VkIHRvIGd1ZXNzIGFkZHJlc3NlcyBpcyBtb3N0bHkgc3BlY2lv
dXMuIEdpdmVuIHRoZSBuZWVkIHRvIHJlamVjdCBtZXNzYWdlcyBhcyBzb29uIGFzIHBvc3NpYmxl
IHNvIGFzIHRvIGF2b2lkIGV4cGVuc2l2ZSBhbmQgdW5uZWNlc3NhcnkgYW50aXNwYW0gcHJvY2Vz
c2luZywgYWRkcmVzcyBndWVzc2luZyBjYW4gYmUgZG9uZSB1c2luZyBSQ1BUIFRPLiBJJ3ZlIG5l
dmVyIGJlZW4gZW50aXJlbHkgY2xlYXIgb24gaG93IFZSRlkgZWFybmVkIHN1Y2ggYSBiYWQgcmVw
LCBidXQgaXQncyBtb3N0bHkgdW5kZXNlcnZlZC4NCg0KCQkJCU5lZA0KDQpQLlMuIFdlIGFsc28g
c3VwcG9ydCByZXF1aXJpbmcgYXV0aGVudGljYXRpb24gcHJpb3IgdG8gYmVpbmcgYWJsZSB0byB1
c2UgdGhlc2UgY29tbWFuZHMsIGJ1dCBJJ20gbm90IHN1cmUgSSd2ZSBldmVyIHNlZW4gYW55b25l
IGFjdHVhbGx5IHVzZSBzdWNoIGEgc2V0dXAuIFRoZSBjbG9zZXN0IEkndmUgc2VlbiB3YXMgYWNj
ZXNzIGNvbnRyb2wgYmFzZWQgb24gdGhlIElQIG9mIHRoZSBjbGllbnQsIHdoaWNoIHdlIGFsc28g
c3VwcG9ydC4NCg0K

From barryleiba@gmail.com  Tue Dec 28 16:52:32 2010
Return-Path: <barryleiba@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 7D80C3A68F7 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.64
X-Spam-Level: 
X-Spam-Status: No, score=-102.64 tagged_above=-999 required=5 tests=[AWL=0.337, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 V2scH79G50n4 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 16:52:31 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 955BE3A68F6 for <ima@ietf.org>; Tue, 28 Dec 2010 16:52:31 -0800 (PST)
Received: by iwn40 with SMTP id 40so10407848iwn.31 for <ima@ietf.org>; Tue, 28 Dec 2010 16:54:36 -0800 (PST)
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=IkC2y8wtHq/btyuMpPG3CvwIGsHBs1q7DD4dOpNa+i4=; b=gjaqk5+n5Zw/l2jTHHxzSh1Ca6XfAxNtoa1KpVbSNfT5dgS0yhgxF5U1ZDFbgkBt7T 6z+wzpwPOYhQc0/9qT+4qiviXF4QhUfvBH4ubB54CRW+vGPwhfEIDvOPbpB4+9LO0gll BU1W8VTnkSp+3jdymfeCTUkNLiopfgJ8pvB1E=
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=tG3qdF6JtWl6XcaXTLMNDe1Rq6rY3sHWpFvA29wEvO72df7RYpynAxv/OtSJwPI5pa 0mDnBTXuGRVEgAlOb7Nym5X8xpcoUXozzSvkhEuOntG5yKByQ7RMYDHDzxtgnvMbGxii kGAKsTXNQ/fhgKHWI3r8o7Xg+Lj9Oo0JHWv2Y=
MIME-Version: 1.0
Received: by 10.231.173.12 with SMTP id n12mr3536736ibz.159.1293584076591; Tue, 28 Dec 2010 16:54:36 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.231.208.12 with HTTP; Tue, 28 Dec 2010 16:54:36 -0800 (PST)
In-Reply-To: <01NVYL1UIU1G007FL5@mauve.mrochek.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <op.vn6g7hky6hl8nm@clerew.man.ac.uk> <01NVRM7BIKTM007CHU@mauve.mrochek.com> <op.vodgrjbm6hl8nm@clerew.man.ac.uk> <AANLkTinQyjbQDC8GS5q=TJrtb9O60m94Lwzwt2Q2UuQU@mail.gmail.com> <01NVYL1UIU1G007FL5@mauve.mrochek.com>
Date: Tue, 28 Dec 2010 19:54:36 -0500
X-Google-Sender-Auth: yaoyPknAFreSR6a1-vr4bpkSiAk
Message-ID: <AANLkTi=HTfSujNLj2uQW-Z88rFU9UOSKeqS1YpFNJP_S@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] apps-team review of draft-ietf-eai-rfc5336bis
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: Wed, 29 Dec 2010 00:52:32 -0000

I agree with both things that Ned says, below.  I think we do have to
think of this not as revising the experiment, but as using the results
of the experiment to start over and re-design.  I'm sorry that those
of us who were following this from the start have not been following
it closely enough to get this right.

Barry

> More generally, this group seems to be having difficulty on at least two
> fronts. First, the current specifications still show some attachment to the
> previous model, where messages were supposed to contain the information
> necessary to downgrade them. The new model, where bouncing is going to be the
> only option most of the time, has very different operational characteristics.
> For one thing, stuff that's merely nice to have in a scenario where downgrading
> is possible becomes a lot more important when downgrading is no longer an
> option.
>
> Second, there's a big difference between designing an experimental protocol and
> specifying protocols for a production service. In the former case, it may be OK
> to do stuff that has implementors scratching their heads and wondering how to
> put it all together. But in the latter case, the shoe is really on the other
> foot: The service has to sell itself on a benefits versus costs basis. So,
> while there's certainly no rule in the IETF about avoiding deep inspection,
> requiring it may result in serious deployment problems. And deployment of
> new services is tough enough even for very simple, straightforward things,
> which this set of specifications most certainly is NOT.

From klensin@jck.com  Tue Dec 28 19:38:48 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 4255B3A63D2 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 19:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 yE2Y1YLgc-Cf for <ima@core3.amsl.com>; Tue, 28 Dec 2010 19:38:47 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 2F7E13A63C9 for <ima@ietf.org>; Tue, 28 Dec 2010 19:38:46 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXmu5-000Hwi-7W; Tue, 28 Dec 2010 22:40:45 -0500
X-Vipre-Scanned: 0C8E4C69001DEB0C8E4DB6-TDI
Date: Tue, 28 Dec 2010 22:40:43 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org
Message-ID: <4BA621B76107C8760218F529@[192.168.1.128]>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B43C5F@TK5EX14MBXC137.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A11B43C5F@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
Cc: dcrocker@bbiw.net
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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: Wed, 29 Dec 2010 03:38:48 -0000

--On Tuesday, December 28, 2010 5:02 AM +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> FWIW: I'm happy clarifying UTF-8 encoding vs Unicode character
> repertoire.  I missed whatever the problem is with "ASCII vs
> UTF-8"?  I don't like "ASCII vs non-ASCII" as it would imply
> other encodings might be valid, and a big goal of the WG is to
> deprecate other encodings for EAI to alleviate the
> confusion/problems around encodings.

Yes, that is exactly the problem with "non-ASCII".  To be
strictly correct, we would need to say something like "the ASCII
subset of UTF-8" (or "Unicode", as appropriate from context) and
"the non-ASCII subset of UTF-8" (ditto), but that is getting
quite cumbersome.

> In the discussion there was some general comments around the
> "older" existing environment.  IMO EAI requires updates to
> understand the addresses, so I'm not terribly worried about
> providing support for things that can be handled by requiring
> the use of UTF-8 throughout.  EAI senders and receivers would
> have to understand that stuff anyway.

Yes, as long as the server can tell it is really [Unicode
encoded in] UTF-8 (and able to return [Unicode encoded in]
UTF-8, rather than actually dealing with a legacy client.  That
is where the VRFY/EXPN discussion and the MAIL parameter one
become important.

    john


From dhc2@dcrocker.net  Tue Dec 28 22:10:28 2010
Return-Path: <dhc2@dcrocker.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 C4A7C3A68AC for <ima@core3.amsl.com>; Tue, 28 Dec 2010 22:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=-0.053,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 XKLI0Ys9WgVG for <ima@core3.amsl.com>; Tue, 28 Dec 2010 22:10:27 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id C5BA93A68A8 for <ima@ietf.org>; Tue, 28 Dec 2010 22:10:27 -0800 (PST)
Received: from [192.168.1.90] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBT6CQDf012834 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2010 22:12:32 -0800
Message-ID: <4D1AD148.7070000@dcrocker.net>
Date: Tue, 28 Dec 2010 22:12:24 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it>	<68655A9F86D4BE7ED933F8A6@192.168.1.128>	<4D192FF8.1030706@dcrocker.net>	<9B48F59821946F2EA2DCDEA0@192.168.1.128>	<4D19623F.3040804@dcrocker.net>	<61939C011F6BB4A93749804C@192.168.1.128>	<AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@[192.168.1.128]>
In-Reply-To: <0D625A27294258D00E95152A@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 28 Dec 2010 22:12:33 -0800 (PST)
Cc: ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 29 Dec 2010 06:10:28 -0000

On 12/28/2010 10:25 AM, John C Klensin wrote:
> Dave suggested in a later note...
>> The change in our reference is to stop using ASCII to refer to
>> an encoding.  For Internet ASCII, the formal definition
>> usually is "7-bit ASCII in an 8-bit field, with the high bit
>> off", but "7-bit" should suffice...
>
> Unfortunately, this doesn't work either if one aspires to the
> kind of precision for which you seem to be asking.

1.  A 2x2 matrix isn't all that precise.

2.  Retaining ambiguous terms doesn't work very well, either.

3.  The terms I suggested all have established use.

4.  RFC 20 (October, 1969) which has a version of the same language I used for 
citing ASCII as an encoding form, as you also cite:

        "7-bit ASCII embedded in an 8 bit byte whose high order bit is always 0"

In other words, "7-bit" is a long-established term for an encoding of ASCII.

So, in spite of the length of your note, I could not discern what you consider 
to be deficient in the terminoloy matrix I suggest, nor what alternative(s) you 
suggest.


>  an effort to sort out character set
> repertoire, definition, encoding, and embedding issues in a
> general and appropriate way should not be imposed on the EAI WG.

That does indeed sound quite ambitious.  So it's probably good that that is not 
the task being suggested.  There is only the need to have the working group 
invoke existing terms or define new ones, for its own usage to ensure clarity 
and accuracy.

Once again:  A 2x2 matrix is not much of all that ambitious, especially when 3 
of the 4 terms appears to be already acceptable...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From yaojk@cnnic.cn  Tue Dec 28 23:21: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 128E63A68A7 for <ima@core3.amsl.com>; Tue, 28 Dec 2010 23:21:15 -0800 (PST)
X-Quarantine-ID: <gTYl2RzvBkyy>
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.457
X-Spam-Level: 
X-Spam-Status: No, score=-99.457 tagged_above=-999 required=5 tests=[AWL=0.586, 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 gTYl2RzvBkyy for <ima@core3.amsl.com>; Tue, 28 Dec 2010 23:21:14 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id BF2483A685B for <ima@ietf.org>; Tue, 28 Dec 2010 23:21:12 -0800 (PST)
Received: (eyou send program); Wed, 29 Dec 2010 15:23:14 +0800
Message-ID: <493607394.16329@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 29 Dec 2010 15:23:14 +0800
Message-ID: <5E1CE608FF5A4F0F8CE6F47C238CFF24@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: <ima@ietf.org>
References: <02EB1F03BAF0ED410F97CDC6@[192.168.1.128]> <493574993.17079@cnnic.cn>
Date: Wed, 29 Dec 2010 15:23:18 +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] EAI review topic: Parameter on MAIL command
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: Wed, 29 Dec 2010 07:21:15 -0000

DQouLi4uDQo+DQo+DQo+PlF1ZXN0aW9uOiBTaG91bGQgd2UgZGVmaW5lLCBhbmQgcmVxdWlyZSwg
YW4gYW5ub3VuY2VtZW50DQo+PnBhcmFtZXRlciBvbiB0aGUgTUFJTCBjb21tYW5kIGlmIHRoZSBz
ZW5kZXIgaW50ZW5kcyB0byB0cmFuc21pdA0KPj5laXRoZXIgbm9uLUFTQ0lJIGFkZHJlc3NlcyBv
ciBVVEYtOCBpbiBoZWFkZXJzIChvdGhlciB0aGFuIGFzDQo+PmVuY29kZWQgd29yZHMpPw0KPj4g
IA0KDQpJdCBzZWVtcyB0aGF0IG1hbnkgY29sbGVhZ3VlcyBpbiB0aGlzIGxpc3QgaGF2ZSBhZ3Jl
ZWQgdG8gYWRkIGEgcGFyYW1ldGVyICBvbiB0aGUgTUFJTCBjb21tYW5kIHRvIGluZGljYXRlIHRo
YXQNCndoZXRoZXIgdGhlIG1lc3NhZ2UgdHJhbnNmZXJyZWQgaXMgIGluIHRoZSBmb3JtYXQgb2Yg
VVRGLTggaW4gaGVhZGVycy4NCklmIHRoZSBXRyBoYXMgYSBjb25zZW5zdXMgb24gaXQsIEkgd2ls
bCB1cGRhdGUgaXQgaW4gdGhlIG5leHQgdmVyc2lvbi4NCg0KSSBwcm9wb3NlIHRoZSBmb2xsb3cg
dGV4dCBhYm91dCB0aGlzIHBhcmFtZXRlcjoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KT25lIG9wdGlvbmFsIHBhcmFtZXRlciBpcyBhZGRlZCB0byB0aGUgU01U
UCBNQUlMIGNvbW1hbmQuDQogVGhpcyBwYXJhbWV0ZXIgaXMgbmFtZWQgYXMgVVRGOEhFQURFUlMu
IFRoZSAiVVRGOEhFQURFUlMiIHBhcmFtZXRlcg0KaGFzIG9uZSBvZiB0d28gdmFsdWVzOiB5IG9y
IG4uIFRoZSBwYXJhbWV0ZXIgIlVURjhIRUFERVJTIiBpcw0KZGVzaWduZWQgdG8gYXNzZXJ0IHdo
ZXRoZXIgdGhlIG1lc3NhZ2UgdHJhbnNmZXJyZWQgaXMgIGluIHRoZSBmb3JtYXQgb2YgVVRGLTgg
aW4gaGVhZGVycywgd2hpY2ggbWVhbnMNCnRoYXQgdGhlIG1lc3NhZ2UgaW4gdGhlIGhlYWRlcnMg
aXMgaW4gdGhlIGZvcm1hdCBvZiBVVEYtOFtSRkM1MzM2YmlzXSBpZiB0aGUgdmFsdWUgaXMgJ3kn
IG9yIG5vdCBpZiB0aGUgdmFsdWUgaXMNCiduJy4NCklmIHRoZSBzZXJ2ZXIgaXMgbm90IEVBSS1h
d2FyZSwgDQp0aGUgICJVVEY4SEVBREVSUyIgcGFyYW1ldGVyIE1VU1Qgbm90IGJlIHVzZWQgaW4g
dGhlIE1BSUwgY29tbWFuZCBieSB0aGUgY2xpZW50Lg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KDQphbnkgY29tbWVudHMgYXJlIHdlbGNvbWUuDQoNClRoYW5rcy4N
Cg0KSmlhbmthbmcgWWFvDQo=


From yangwooko@gmail.com  Tue Dec 28 23:58:47 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 6BBAA3A68AF for <ima@core3.amsl.com>; Tue, 28 Dec 2010 23:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level: 
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 KHAnhLQdkNHx for <ima@core3.amsl.com>; Tue, 28 Dec 2010 23:58:46 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 60E493A685C for <ima@ietf.org>; Tue, 28 Dec 2010 23:58:46 -0800 (PST)
Received: by qyk34 with SMTP id 34so11413776qyk.10 for <ima@ietf.org>; Wed, 29 Dec 2010 00:00:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=oJNxuNIA+gZgbGiZt1jCRfMoALvxhOq5IV/HtVMC+eA=; b=KtqVBphlFJH0eiEAmPgnRr29JkIepg0t1IcS2N2LiRrN+SaaGUHAPl/+Ds9I7q2Xl2 whz4ZjUuUQsqcN+48N40a7KdgUN+5C7Vy+fYeR4F7HDEgwb4usvCzAMHWFtWKkvxeWuh xB8ovkAWQ2y7ZgUcia0LPAFjRMdInHK4Fsen0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=sDOWuXOJxbOvkVVURFs5IZhZeBqv59JOhu1pmRHP9fZSIHf5XHTag5H4rrU5BH6JHP +udJJUoo7lGf7Zsn6af+Xop1hTRo91lUgjOehEZ9Y1M/F6SqbeN1AUz6kgCW1xGIYknr ybJFop+H9G1B5Pz//sQcV9F7G/mGj69AnbtVU=
Received: by 10.229.233.196 with SMTP id jz4mr13024881qcb.135.1293609650117; Wed, 29 Dec 2010 00:00:50 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Wed, 29 Dec 2010 00:00:30 -0800 (PST)
In-Reply-To: <02EB1F03BAF0ED410F97CDC6@192.168.1.128>
References: <02EB1F03BAF0ED410F97CDC6@192.168.1.128>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Wed, 29 Dec 2010 17:00:30 +0900
X-Google-Sender-Auth: hYUAqZor04fNabrLP2R_uPpYRmo
Message-ID: <AANLkTikZ61i3vhOLvkNGjDCVGS2pdZ3JB3wJM00BSpmz@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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: Wed, 29 Dec 2010 07:58:47 -0000

I prefer an option that looks simplest in a situation where all
servers are upgraded to be compliant to these new specifications. In
that sense, I am negative to adding a parameter to MAIL command to
handle (hopefully very rare) situations of encoutering an un-upgraded
server. Since most of recent comments received by this WG recommend
adding the option, I am not strongly against the idea because the
modification will not significantly affect the current document.

On Tue, Dec 28, 2010 at 9:12 AM, John C Klensin <klensin@jck.com> wrote:
>
>
> (writing as co-chair)
>
> Hi.
>
> Joseph and/or I will be sending out a series of (short) notes to
> the WG mailing list identifying substantive issues that the WG
> needs to review and make decisions about. =C2=A0They are going to be
> short in the hope that people will read them and read them soon,
> but there are relevant previous discussions on the mailing list,
> in the reviews, and in the long set of notes I posted earlier
> that people should try to understand before responding to the
> questions. =C2=A0However, remember that the WG is supposed to be
> working quickly: these issues are in the critical path for
> anything to more forward.
>
> Question: Should we define, and require, an announcement
> parameter on the MAIL command if the sender intends to transmit
> either non-ASCII addresses or UTF-8 in headers (other than as
> encoded words)?
>
> Discussion references: My long note, especially item (2), which
> I hope summarizes the review comments) and a number of comments
> on-list about what is required if this header is not present.
>
> =C2=A0 =C2=A0john
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human known as yangwooko@gmail.com @ gtalk

From duerst@it.aoyama.ac.jp  Wed Dec 29 00:03:16 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 B12FC3A68E8 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.431
X-Spam-Level: 
X-Spam-Status: No, score=-100.431 tagged_above=-999 required=5 tests=[AWL=-0.641, 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 F419i2M2jRfg for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:03:15 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id 6F3413A685C for <ima@ietf.org>; Wed, 29 Dec 2010 00:03:15 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oBT85Fih008000 for <ima@ietf.org>; Wed, 29 Dec 2010 17:05:15 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 6231_9393_5e2239d4_1322_11e0_a91a_001d096c5782; Wed, 29 Dec 2010 17:05:15 +0900
Received: from [IPv6:::1] ([133.2.210.1]:39254) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14ABCA9> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 29 Dec 2010 17:05:15 +0900
Message-ID: <4D1AEBB6.9030402@it.aoyama.ac.jp>
Date: Wed, 29 Dec 2010 17:05:10 +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: <2B9258A1B04B6596D4F07D20@[192.168.1.128]>
In-Reply-To: <2B9258A1B04B6596D4F07D20@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 08:03:16 -0000

In the hope to move the debate forward, and after the clarifications by 
Alex and Ned, but not an email infrastructure insider, my preferences below.

On 2010/12/28 9:21, John C Klensin wrote:
> (writing as co-chair and incorporating the introduction to the
> note I sent a few minutes ago by reference)
>
> Topic: The description of VRFY and EXPN handling in 5336bis is
> not adequate.  Whatever is done, we will have to change/fix it.
> In the questions below, I've mentioned VRFY but I assume that
> EXPN would get exactly the same treatment.
>
> Questions:
>
> (1) Should VRFY be retained as is, with the parameter, but with
> a restriction that the parameter MUST NOT be used without EHLO
> appearing first.

That seems like an easy fix.

> (2) Should VRFY be retained as is, with the parameter and
> without the "ok to use VRFY without a session, i.e., without
> EHLO first".  Note that this would be the first time an SMTP
> extension has been permitted without explicit server permission
> via EHLO and that it involves a small risk of non-EAI-aware
> servers parsing the parameter as part of a name sent by a client.

It seems that this is what the reviewers have advised against, so I 
guess we should give up on it.

> (3) Should we move toward a new command, replacing VRFY, but
> with more specific syntax that explicitly provides for
> parameters and, presumably, a mail session?   Note that, if the
> answer to this is "yes", someone would need to generate a
> proposal that could be processed separately from the EAI effort.
> While generating the proposal is no problem, the specification
> of the new command would create a normative dependency from
> 5336bis and that might slow things down in terms of publication
> of 5336bis/ 5335bis/ 5337bis.

I'm not sure why this would need to be separate from EAI. It's obviously 
for EAI. Of course, we have to come up with new command names, but that 
should be easy (some already circulated on the list). Apart from that, 
take the current syntax, and change text from "new syntax on old 
command" to "new command", which I'd guess is mostly a clerical 
exercise. Or did I get something wrong?

Anyway, my order of preference would be (1), (3), (2).

Regards,   Martin.


> Discussion references: Many notes on the mailing list in the
> last several days.
>
>      john
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>
>

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

From yangwooko@gmail.com  Wed Dec 29 00:26:23 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 012FC3A68E8 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.863
X-Spam-Level: 
X-Spam-Status: No, score=-2.863 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 z8g6JtYN+yDf for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:26:21 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id AC70A3A685C for <ima@ietf.org>; Wed, 29 Dec 2010 00:26:21 -0800 (PST)
Received: by vws7 with SMTP id 7so3946655vws.31 for <ima@ietf.org>; Wed, 29 Dec 2010 00:28:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=+hCLH8TaWRZjx4/BBNkuiCq+MvBU2Ix5O+yfsKbTLC4=; b=X95zMa3mHm4n5jRdeDrpgRKAX3fsilams7fUmntafHVGPoLBSrg3zdTHT66DIoCL8M RZgCypVUo6gxkVBiQy/igifsZyA/eRIKRT/7B+o0V3f1ZsyEA7/KcEAS9ovUdimeZ1fD YJVpmYF9AOAcnWp7b4xKyMFR1VftLWPwcEtFQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=RU1WvvAF27Pi/XB9OzieXJks/SdlJAgFxhw3uOt53IGsTO8jhVgRVCQZZuD0UN1rb8 m6U72nQDV4f/Og+0BFTTfsoNHE/2lDeRISXQTpgTmid6UoTH6l151NtVaoZe+2zRogJb ZhVemJ4TYnAlizN8/3e0fK8eEkcqIF1pH70zc=
Received: by 10.220.93.81 with SMTP id u17mr4026748vcm.121.1293611304876; Wed, 29 Dec 2010 00:28:24 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Wed, 29 Dec 2010 00:28:04 -0800 (PST)
In-Reply-To: <4D1AD148.7070000@dcrocker.net>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Wed, 29 Dec 2010 17:28:04 +0900
X-Google-Sender-Auth: 9rDyX4sTEPWW4cldMmmoYQYFAiw
Message-ID: <AANLkTi=r-TJWQ85Y_e_17SCfK1SHpOUrBQb-FSDGxm04@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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: Wed, 29 Dec 2010 08:26:23 -0000

Let me think about the other extreme.

What about explicitly saying that "in this document, we use the terms,
ASCII and UTF-8, to mean either encoding or representation and they
should be interpreted according to the context they are used" ?

Then what specific parts of the document will confuse readers?

On Wed, Dec 29, 2010 at 3:12 PM, Dave CROCKER <dhc2@dcrocker.net> wrote:
>
>
>
>
> On 12/28/2010 10:25 AM, John C Klensin wrote:
>>
>> Dave suggested in a later note...
>>>
>>> The change in our reference is to stop using ASCII to refer to
>>> an encoding. =C2=A0For Internet ASCII, the formal definition
>>> usually is "7-bit ASCII in an 8-bit field, with the high bit
>>> off", but "7-bit" should suffice...
>>
>> Unfortunately, this doesn't work either if one aspires to the
>> kind of precision for which you seem to be asking.
>
> 1. =C2=A0A 2x2 matrix isn't all that precise.
>
> 2. =C2=A0Retaining ambiguous terms doesn't work very well, either.
>
> 3. =C2=A0The terms I suggested all have established use.
>
> 4. =C2=A0RFC 20 (October, 1969) which has a version of the same language =
I used
> for citing ASCII as an encoding form, as you also cite:
>
> =C2=A0 =C2=A0 =C2=A0 "7-bit ASCII embedded in an 8 bit byte whose high or=
der bit is always
> 0"
>
> In other words, "7-bit" is a long-established term for an encoding of ASC=
II.
>
> So, in spite of the length of your note, I could not discern what you
> consider to be deficient in the terminoloy matrix I suggest, nor what
> alternative(s) you suggest.
>
>
>> =C2=A0an effort to sort out character set
>> repertoire, definition, encoding, and embedding issues in a
>> general and appropriate way should not be imposed on the EAI WG.
>
> That does indeed sound quite ambitious. =C2=A0So it's probably good that =
that is
> not the task being suggested. =C2=A0There is only the need to have the wo=
rking
> group invoke existing terms or define new ones, for its own usage to ensu=
re
> clarity and accuracy.
>
> Once again: =C2=A0A 2x2 matrix is not much of all that ambitious, especia=
lly when
> 3 of the 4 terms appears to be already acceptable...
>
> d/
> --
>
> =C2=A0Dave Crocker
> =C2=A0Brandenburg InternetWorking
> =C2=A0bbiw.net
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human known as yangwooko@gmail.com @ gtalk

From yangwooko@gmail.com  Wed Dec 29 00:33:39 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 13FDA3A68E8 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level: 
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.051,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 iZMxdRSR2bpp for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:33:38 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id E68523A685C for <ima@ietf.org>; Wed, 29 Dec 2010 00:33:37 -0800 (PST)
Received: by qwg5 with SMTP id 5so10403582qwg.31 for <ima@ietf.org>; Wed, 29 Dec 2010 00:35:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=yEHyopXfgfc5a+5mJ9hTZOahEOyL3cP2kEVb1aHirnU=; b=CSpGo7Ud7HRnQTPnwUg9hEBiEvWrN1tvr7EvefRbHAfiq1Bqy/TSYbNk5IAqy0MUB9 lOgT7MKmW8BWiDQ4FITenhunuwY3SBRCr8ME87lBaK7l8GnCbSTjLJEzILGGC5rC61Mx 7iV7IGjVxMe9S5v3PmtiVGQSJsIiXgwEBD6Eo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=CzSLCziWDNhvcIqraEQn8vNiXR6sRgUOlCZlI48MKZaDP7xNqkZNPzxu2y1aQVEDHH llUavhQTfGEmKAAIErSjjFjbx8atQkWqasg5LbCAGP7IjOclB2LlVAXsdz+LnGkSOne1 5nYfEZ9b/kPUrkqBvOdrbSc53iV2lYcwCeQPo=
Received: by 10.224.80.200 with SMTP id u8mr14091509qak.7.1293611741496; Wed, 29 Dec 2010 00:35:41 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Wed, 29 Dec 2010 00:35:21 -0800 (PST)
In-Reply-To: <2B9258A1B04B6596D4F07D20@192.168.1.128>
References: <2B9258A1B04B6596D4F07D20@192.168.1.128>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Wed, 29 Dec 2010 17:35:21 +0900
X-Google-Sender-Auth: LdOyBI0AtIt8hihJqL4PYUS8IE4
Message-ID: <AANLkTincOwV1-scb7gAgh0oO6_T6rDwhn6LT8ErAqeFy@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 08:33:39 -0000

+1 to option (1)

On Tue, Dec 28, 2010 at 9:21 AM, John C Klensin <klensin@jck.com> wrote:
>
>
> (writing as co-chair and incorporating the introduction to the
> note I sent a few minutes ago by reference)
>
> Topic: The description of VRFY and EXPN handling in 5336bis is
> not adequate. =C2=A0Whatever is done, we will have to change/fix it.
> In the questions below, I've mentioned VRFY but I assume that
> EXPN would get exactly the same treatment.
>
> Questions:
>
> (1) Should VRFY be retained as is, with the parameter, but with
> a restriction that the parameter MUST NOT be used without EHLO
> appearing first.
>
> (2) Should VRFY be retained as is, with the parameter and
> without the "ok to use VRFY without a session, i.e., without
> EHLO first". =C2=A0Note that this would be the first time an SMTP
> extension has been permitted without explicit server permission
> via EHLO and that it involves a small risk of non-EAI-aware
> servers parsing the parameter as part of a name sent by a client.
>
> (3) Should we move toward a new command, replacing VRFY, but
> with more specific syntax that explicitly provides for
> parameters and, presumably, a mail session? =C2=A0 Note that, if the
> answer to this is "yes", someone would need to generate a
> proposal that could be processed separately from the EAI effort.
> While generating the proposal is no problem, the specification
> of the new command would create a normative dependency from
> 5336bis and that might slow things down in terms of publication
> of 5336bis/ 5335bis/ 5337bis.
>
> Discussion references: Many notes on the mailing list in the
> last several days.
>
> =C2=A0 =C2=A0john
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human known as yangwooko@gmail.com @ gtalk

From yaojk@cnnic.cn  Wed Dec 29 00:59:32 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 3EAFC28C0DD for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:59:32 -0800 (PST)
X-Quarantine-ID: <zGcLOOLHfDSw>
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.41
X-Spam-Level: 
X-Spam-Status: No, score=-99.41 tagged_above=-999 required=5 tests=[AWL=0.481,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803,  SARE_SUB_ENC_UTF8=0.152, 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 zGcLOOLHfDSw for <ima@core3.amsl.com>; Wed, 29 Dec 2010 00:59:31 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id AC48D3A68F8 for <ima@ietf.org>; Wed, 29 Dec 2010 00:59:30 -0800 (PST)
Received: (eyou send program); Wed, 29 Dec 2010 17:01:35 +0800
Message-ID: <493613295.04708@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 29 Dec 2010 17:01:35 +0800
Message-ID: <7DD5A11B442D4851959F61B1E237015A@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Andrew Sullivan" <ajs@crankycanuck.ca>, <ima@ietf.org>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it><68655A9F86D4BE7ED933F8A6@[192.168.1.128]><4D192FF8.1030706@dcrocker.net><9B48F59821946F2EA2DCDEA0@[192.168.1.128]><4D19623F.3040804@dcrocker.net><61939C011F6BB4A93749804C@[192.168.1.128]> <493539018.05274@cnnic.cn>
Date: Wed, 29 Dec 2010 17:01:40 +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] new terms Re: Unicode vs. UTF-8 / Encoding vs. Representation
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: Wed, 29 Dec 2010 08:59:32 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFuZHJldyBTdWxsaXZhbiIg
PGFqc0BjcmFua3ljYW51Y2suY2E+DQpUbzogPGltYUBpZXRmLm9yZz4NClNlbnQ6IFR1ZXNkYXks
IERlY2VtYmVyIDI4LCAyMDEwIDg6MjMgUE0NClN1YmplY3Q6IFJlOiBbRUFJXSBVbmljb2RlIHZz
LiBVVEYtOCAvIEVuY29kaW5nIHZzLiBSZXByZXNlbnRhdGlvbg0KDQoNCj4gT24gTW9uLCBEZWMg
MjcsIDIwMTAgYXQgMTE6MTc6MzJQTSAtMDUwMCwgSm9obiBDIEtsZW5zaW4gd3JvdGU6DQo+IA0K
Pj4gSSBob3BlIHNvbWVvbmUgaW4gdGhlIFdHIHdpbGwgaGF2ZSBhIGdvb2Qgc3VnZ2VzdGlvbi4g
ICBJZiBub3QsDQo+PiB3ZSBtYXkgYmUgYmFjayB0byAiQVNDSUkiIHZlcnN1cyAibm9uLUFTQ0lJ
IiBhcyB0aGUgZGlzam9pbnQNCj4+IHBhaXIsICJVbmljb2RlIiAgdG8gZGVzY3JpYmUgdGhlIGlu
dGVybmF0aW9uYWwgQ0NTIChpbmNsdXNpdmUgb2YNCj4+IEFTQ0lJKSwgYW5kICJVVEYtOCIgdG8g
ZGVzY3JpYmUgdGhlIHBhcnRpY3VsYXIgZW5jb2RpbmcgdGhhdCBpcw0KPj4gdXNlZCBmb3IgdGhp
cyBwcm90b2NvbCBhbmQgcmVjb21tZW5kZWQgYnkgUkZDIDIyNzcgKGENCj4+IHJlY29tbWVuZGF0
aW9uIHRoYXQgaXMgcmVpbmZvcmNlZCBieSBkcmFmdC1pYWItaWRuLWVuY29kaW5nIGFuZA0KPj4g
b3RoZXIgbW9yZSByZWNlbnQgd29yaykuDQo+IA0KPiBJdCBzZWVtcyB0byBtZSB0aGF0IG9uZSBj
b3VsZCB0YWtlIGEgY3VlIGZyb20gdGhlIElETkEgd29yaywgd2hpY2gNCj4gZGlmZmVyZW50aWF0
ZWQgQS1sYWJlbCwgVS1sYWJlbCwgTERILWxhYmVsLCBhbmQgc28gb24uDQo+IA0KDQp5ZXMsIEkg
dGhpbmsgdGhhdCB3ZSBtYXkgYm9ycm93IHRoZSBpZGVhcyBmcm9tIFJGQzU4OTAuDQoNCiBBICJV
LWxhYmVsIiBpcyBhbiBJRE5BLXZhbGlkIHN0cmluZyBvZiBVbmljb2RlIGNoYXJhY3RlcnMsIGlu
DQogICAgICBOb3JtYWxpemF0aW9uIEZvcm0gQyAoTkZDKSBhbmQgaW5jbHVkaW5nIGF0IGxlYXN0
IG9uZSBub24tQVNDSUkNCiAgICAgIGNoYXJhY3RlciwgZXhwcmVzc2VkIGluIGEgc3RhbmRhcmQg
VW5pY29kZSBFbmNvZGluZyBGb3JtIChzdWNoIGFzDQogICAgICBVVEYtOCkuIA0KDQoNCkkgc3Vn
Z2VzdCB0byBkZWZpbmUgdGhlIGZvbGxvd2luZyB0ZXJtczoNCg0KVS1jaGFyYWN0ZXI6DQogQSAi
VS1jaGFyYWN0ZXIiIGlzIGEgbm9uLUFTQ0lJIFVuaWNvZGUgY2hhcmFjdGVyLCBpbg0KICAgICAg
Tm9ybWFsaXphdGlvbiBGb3JtIEMgKE5GQykgYW5kIGV4cHJlc3NlZCBpbiBhIHN0YW5kYXJkIFVu
aWNvZGUgRW5jb2RpbmcgRm9ybSBvZiBVVEYtOC4gDQoNCiANClUtc3RyaW5nOg0KIEEgIlUtc3Ry
aW5nIiBpcyBhIHN0cmluZyBvZiBVbmljb2RlIGNoYXJhY3RlcnMsIGluDQogICAgICBOb3JtYWxp
emF0aW9uIEZvcm0gQyAoTkZDKSBhbmQgaW5jbHVkaW5nIGF0IGxlYXN0IG9uZSBub24tQVNDSUkN
CiAgICAgIGNoYXJhY3RlciwgZXhwcmVzc2VkIGluIGEgc3RhbmRhcmQgVW5pY29kZSBFbmNvZGlu
ZyBGb3JtIG9mIFVURi04LiANCg0KQS1jaGFyYWN0ZXI6DQogIEFuICAiQS1jaGFyYWN0ZXIiIGlz
IGFuIEFTQ0lJIFVuaWNvZGUgY2hhcmFjdGVyLCBleHByZXNzZWQgaW4gYSBzdGFuZGFyZCBVbmlj
b2RlIEVuY29kaW5nIEZvcm0gb2YgVVRGLTguIA0KDQpBLXN0cmluZzoNCiBBbiAgIkEtc3RyaW5n
IiBpcyAgYSBzdHJpbmcgb2YgVW5pY29kZSBjaGFyYWN0ZXJzLCAgaW5jbHVkaW5nIEFTQ0lJDQog
ICAgICBjaGFyYWN0ZXJzIG9ubHksIGV4cHJlc3NlZCBpbiBhIHN0YW5kYXJkIFVuaWNvZGUgRW5j
b2RpbmcgRm9ybSBvZiBVVEYtOC4gDQoNCg0KYXJlICB0aGUgZGVmaW5pdGlvbnMgYWJvdmUgY2xl
YXI/DQoNCg0KYW5vdGhlciBxdWVzdGlvbiBpcyB0aGF0IHdlIGRlZmluZSB0aGVzZSBuZXcgdGVy
bXMgaW4gcmZjNTMzNmJpcyBvciBpbiByZmM0OTUyYmlzPw0KDQoNCnRoYW5rcy4NCg0KSmlhbmth
bmcgWWFvDQoNCg==


From klensin@jck.com  Wed Dec 29 01:36: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 5C26D28C0EB for <ima@core3.amsl.com>; Wed, 29 Dec 2010 01:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 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 APaLSzRF5CQX for <ima@core3.amsl.com>; Wed, 29 Dec 2010 01:36:27 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 6835628C0E9 for <ima@ietf.org>; Wed, 29 Dec 2010 01:36:26 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PXsUI-000L69-47; Wed, 29 Dec 2010 04:38:30 -0500
X-Vipre-Scanned: 0DD5D47F001DEB0DD5D5CC-TDI
Date: Wed, 29 Dec 2010 04:38:29 -0500
From: John C Klensin <klensin@jck.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Message-ID: <D273138577C60C0101AC1487@[192.168.1.128]>
In-Reply-To: <4D1AEBB6.9030402@it.aoyama.ac.jp>
References: <2B9258A1B04B6596D4F07D20@[192.168.1.128]> <4D1AEBB6.9030402@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: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 09:36:30 -0000

--On Wednesday, December 29, 2010 5:05 PM +0900 "\"Martin J.
D=C3=BCrst\"" <duerst@it.aoyama.ac.jp> wrote:

>...
>> (3) Should we move toward a new command, replacing VRFY, but
>> with more specific syntax that explicitly provides for
>> parameters and, presumably, a mail session?   Note that, if
>> the answer to this is "yes", someone would need to generate a
>> proposal that could be processed separately from the EAI
>> effort. While generating the proposal is no problem, the
>> specification of the new command would create a normative
>> dependency from 5336bis and that might slow things down in
>> terms of publication of 5336bis/ 5335bis/ 5337bis.

> I'm not sure why this would need to be separate from EAI. It's
> obviously for EAI. Of course, we have to come up with new
> command names, but that should be easy (some already
> circulated on the list). Apart from that, take the current
> syntax, and change text from "new syntax on old command" to
> "new command", which I'd guess is mostly a clerical exercise.
> Or did I get something wrong?

For the record, my mentioning "new command" was to be sure the
WG considered all options and because a discussion, I hope
brief, of what a new command would do for us may help to
illuminate this issues and risks of the other choices.  I did
not mention it to advocate going down that path: the essence of
the argument against it is that it involves fairly high cost to
avoid a problem that is unlikely to ever occur in practice.

That said, the reason for "separate from EAI" is that there is
specific syntax in RFC 5321 for parameters for MAIL and RCPT
(Section 4.2).  It does not do so for DATA and, even though the
base command does not accept arguments, making the syntax is
mind-numbingly obvious, we invented a new command (BDAT) for a
parameterized version in RFC 3030.  In theory, and following the
same path now being suggested for VRFY/EXPN, we could have
simply added more parameters to DATA rather than making up BDAT.
If I recall, the big concern was that such parameters would
simply be ignored as noise or comments on the DATA command -- a
slightly different situation than with VRFY.

But, while the "extra stuff gets ignored" concern probably does
not apply to VRFY (or EXPN) any more than they would to MAIL or
RCPT, VRFY and EXPN do accept arguments and have been
misunderstood and misused in ways that make it impossible to
distinguish between the last part of the argument String and a
parameter with 100% confidence.  If we need to specify a syntax
for parameters with VRFY (technically speaking, whether with a
new command name or not), we don't have an established model for
adding parameters to VRFY and EXPN.  Establishing a syntax for
VRFY-with-optional-parameters (or
NewCommand-with-optional-parameters) is an RFC 5321 update
issue, but not an EAI issue.  =20

At least that is how I understand the situation and the concern.

best,
    john





From eai@troystarr.net  Wed Dec 29 02:59:25 2010
Return-Path: <eai@troystarr.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 598D028C0DE for <ima@core3.amsl.com>; Wed, 29 Dec 2010 02:59:25 -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 YTi7aHj2SFv2 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 02:59:24 -0800 (PST)
Received: from mho-01-ewr.mailhop.org (mho-01-ewr.mailhop.org [204.13.248.71]) by core3.amsl.com (Postfix) with ESMTP id 28C9728B56A for <ima@ietf.org>; Wed, 29 Dec 2010 02:59:24 -0800 (PST)
Received: from user-0c2i81f.cable.earthlink.net ([24.41.32.47] helo=remote.troystarr.net) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <eai@troystarr.net>) id 1PXtma-000GrI-NQ; Wed, 29 Dec 2010 11:01:29 +0000
Received: from FORGE.foundry.home ([fe80::ad0e:5a01:9a0:c9a8]) by FORGE.foundry.home ([fe80::ad0e:5a01:9a0:c9a8%10]) with mapi; Wed, 29 Dec 2010 03:01:26 -0800
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.41.32.47
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19s1R1owyeQ0948Z+NX9L6k
From: Troy Starr <eai@troystarr.net>
To: 'Jiankang YAO' <yaojk@cnnic.cn>, "'ima@ietf.org'" <ima@ietf.org>
Date: Wed, 29 Dec 2010 03:01:25 -0800
Thread-Topic: Re: [EAI] EAI review topic: Parameter on MAIL command
Thread-Index: AcunPaiA7ne085X4RkuKHuP9vdfDWA==
Message-ID: <C32A1A5CB0814846B91BFAB307442A2B34285EE68F@FORGE.foundry.home>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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: Wed, 29 Dec 2010 11:01:27 -0000

Hi Jiankang -

First, apologies for not replying directly to your message and breaking you=
r message thread.  I've been following the discussion of the mailing list a=
rchive on the web without actually subscribing to it, but wanted to respond=
 to your proposal.  I've just subscribed to the mailing list now, but I don=
't have your actual e-mail message to reply to.  I've copied your original =
message below for context.

I agree that having an explicit MAIL parameter would be valuable for the re=
asons already discussed.  I'd like to propose a different parameter name an=
d set of values, though.  My concern with the UTF8HEADERS parameter name is=
 that it is very closely tied to this RFC, which could make future extensio=
ns more difficult than necessary.  I don't know what those future extension=
s might be, but I think it would be worthwhile to avoid potential difficult=
y if it's relatively easy to do so.

The closest analogy I could think of was the 8BITMIME SMTP extension (RFC 1=
652).  That WG also decided to create a MAIL parameter to indicate that the=
 message was taking advantage of that SMTP extension.  However, instead of =
creating a parameter called 8BITMIMEBODY with a binary value, they gave the=
 parameter a more generic name (BODY) and set the value to the specific typ=
e (7BIT for legacy and 8BITMIME for the new functionality).  That decision =
worked well for the future BINARYMIME SMTP extension (RFC 3030), since it a=
llowed them to reuse the existing BODY parameter and simply add an addition=
al value to it (BINARYMIME).

Making the parameter more generic may be of similar value to future working=
 groups.  Therefore, I propose the following text instead:

----------
An optional parameter using the keyword HEADER is added to the MAIL FROM co=
mmand.  The value associated with this parameter is a keyword indicating wh=
ether the message contains only ASCII characters in the envelope and header=
 fields, or whether the message contains non-ASCII characters in the envelo=
pe and header fields and MUST follow the guidelines of this RFC.  The synta=
x of the value is as follows, using ABNF notation:

	header-value ::=3D "ASCII" / "UNICODE"

The maximum length of a MAIL FROM command line is increased by 15 character=
s by the possible addition of the HEADER keyword and value.
----------

I see that there's an active discussion about ASCII/Unicode/UTF-8 terminolo=
gy within the mailing list, so the values used here should conform to whate=
ver consensus is reached.  And of course, some may disagree and feel that t=
he UTF8HEADERS proposal is more than sufficient.  I welcome any feedback.

- Troy Starr
Full disclosure: I work for Microsoft, but am not speaking on their behalf =
or in any official capacity.

-----Original Message-----
From: Jiankang YAO [mailto: yaojk@cnnic.cn]
Sent: Tuesday, December 28, 2010 11:23 PM
To: ima@ietf.org
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command

....
>
>
>>Question: Should we define, and require, an announcement
>>parameter on the MAIL command if the sender intends to transmit
>>either non-ASCII addresses or UTF-8 in headers (other than as
>>encoded words)?
>> =20

It seems that many colleagues in this list have agreed to add a parameter  =
on the MAIL command to indicate that
whether the message transferred is  in the format of UTF-8 in headers.
If the WG has a consensus on it, I will update it in the next version.

I propose the follow text about this parameter:
---------------------------------------------------------------------------=
------------------------
One optional parameter is added to the SMTP MAIL command.
 This parameter is named as UTF8HEADERS. The "UTF8HEADERS" parameter
has one of two values: y or n. The parameter "UTF8HEADERS" is
designed to assert whether the message transferred is  in the format of UTF=
-8 in headers, which means
that the message in the headers is in the format of UTF-8[RFC5336bis] if th=
e value is 'y' or not if the value is
'n'.
If the server is not EAI-aware,=20
the  "UTF8HEADERS" parameter MUST not be used in the MAIL command by the cl=
ient.
---------------------------------------------------------------------------=
----------------------

any comments are welcome.

Thanks.

Jiankang Yao

From chl@clerew.man.ac.uk  Wed Dec 29 03:19:49 2010
Return-Path: <chl@clerew.man.ac.uk>
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 8229928C0EA for <ima@core3.amsl.com>; Wed, 29 Dec 2010 03:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.063
X-Spam-Level: 
X-Spam-Status: No, score=-4.063 tagged_above=-999 required=5 tests=[AWL=-0.464, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1pz-VSm47B0M for <ima@core3.amsl.com>; Wed, 29 Dec 2010 03:19:48 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id A6F5828C0DE for <ima@ietf.org>; Wed, 29 Dec 2010 03:19:37 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 9219322196 for <ima@ietf.org>; Wed, 29 Dec 2010 11:21:42 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Wed, 29 Dec 2010 11:21:42 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBTBLf7q029162 for <ima@ietf.org>; Wed, 29 Dec 2010 11:21:42 GMT
Date: Wed, 29 Dec 2010 11:21:40 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com> <3F5293BF906846C89013734B3D6262D9@upstairs> <7C0660F7DFFE9C1990252217@[192.168.1.128]> <op.vofb01pj6hl8nm@clerew.man.ac.uk> <B2DA8473E8F67A3F495A9D67@[192.168.1.128]>
Content-Transfer-Encoding: 8bit
Message-ID: <op.vog26e2l6hl8nm@clerew.man.ac.uk>
In-Reply-To: <B2DA8473E8F67A3F495A9D67@[192.168.1.128]>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d1b19c6.e355-702-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] [apps-discuss] RFC5336 and VRFY/EXPN (was: Re:	apps-team	review of draft-ietf-eai-rfc5336bis)
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: Wed, 29 Dec 2010 11:19:49 -0000

On Tue, 28 Dec 2010 19:44:41 -0000, John C Klensin <klensin@jck.com> wrote:

>> What we _are_ concerned with is
>>
>>      VRFY rené@example.com
>
> We are actually concerned with two cases (if one considers the
> above to be the same case if "@example.com" is left off).  The
> other one is
>        VRFY Rene
> (note no accent), with the understanding that, e.g., either
>        rene@mailhost1.example.com
> or
>        rene@mailhost2.example.com
> could come back.
>
>> for which we _do_ need some extension. But why cannot we just
>> say that if you want to send that VRFY then you MUST do an
>> EHLO first to ensure that UTF8SMTPbis is available, in which
>> case you know that the extension permitting "rené" is
>> available.
>
> The problem is (mostly) not what the client sends but what the
> server can return.   Suppose the server advertises UTF8SMTPbis
> and the client sends "VRFY rene" (all-ASCII).  Now the server
> doesn't know whether it is plausible to return an address
> containing non-ASCII characters or not: the client has to
> somehow give it permission to do that.

I think I would take the view that if the client behaves as a pure legacy  
client, then the server should respond like a pure legacy server. So if we  
want a server to offer rené@example.com in response to a request for (pure  
ASCII) 'rene', then we need some extended syntax (either a parameter or a  
new command). But I am not sure we need that facility anyway (and I  
suspect René himself would be most offended to be addressed as Rene).
>
> Modulo however one feels about heuristics, one would be ok with
> UTF8SMTP in the EHLO response to _send_ "VRFY rené" (the client
> knows that the server supports the EAI extensions) and the
> server could deduce that, if the client is sending non-ASCII, it
> can accept a non-ASCII response.

Indeed, but I think you missed the real point of my message, which was  
suggesting that a client MUST do an EHLO (and check for UTF8SMTPbis)  
_before_
issuing "VRFY rené", and that any VRFY issued _without_ a prior EHLO would  
be constrained to pure ASCII only. That would remove any need for any  
'new-VRFY' command AFAICS.
>
> But, if the client sense all-ASCII, the server can't figure out
> what it can accept in a response unless the client also sends
> along some sort of "I can accept a non-ASCII response if you
> would like to give me one".  Hence the need for a parameter.
>
> Even in the "rené" case, the argument about whether or not the
> parameter is desirable comes down to a situation much like the
> discussion of parameters on the MAIL command.  The difference is
> that they heuristics are easy for "rené" and don't work at all
> for "rene"; for the MAIL case, they are very easy if either the
> MAIL command or the first RCPT command contains a non-ASCII
> address and are possible, but very hard, if the message has
> non-ASCII in the headers but no clue in the envelope.
>
> The problem with
>    VRFY John Klensin
> is that it often does "work" in the legacy setup.  As a leftover
> from 821 and massive confusion about the "\" escape, some will
> treat it as equivalent to
>    VRFY "John\ Klensin"
> while others will treat it as a syntax error.  The first is a
> little more liberal application of the robustness principle than
> I would recommend, but it "works".  The second works too -- it
> is a syntax error.
>
> But, if the server advertises UTF8SMTPbis, it could certainly be
> telling the client that it expects an 5321 interpretation of the
> VRFY command, for which the syntax is unambigious. ...

No, it would not tell a legacy client that. It has to assume a legacy  
client unless it receives explicit information (parameter or new command)  
to the contrary.


>    VRFY John UTF8SMTPbis
> is unambiguous too -- the server is being asked to verify "John"
> but can return non-ASCII in the address if needed.
>    VRFY John Klensin
> also has an unambiguous interpretation as a syntax error and
>    VRFY rené UTF8SMTPbis
> is just fine too.

Use of such a parameter would be my preferred solution. It is consistent  
with the existing syntax of 5321, and hence confirms (to my view) the  
position that
    VRFY John Klensin
is a syntactic error, and should remain so.
>
> But suppose the client doesn't know anything about i18n and just
> ignores the UTF8SMTPbis announcement (as it is obligated to
> ignore any extension announcement it doesn't recognize).   Now,
> when it sends
>     VRFY John UTF8SMTPbis
> the server really doesn't know -....

Then to a legacy server it is a syntactic error. If the server chooses to  
guess some intended meaning, then that is not our problem (it would most  
likely return some 553, which is fine by me). An I18N server would  
interpret the UTF8SMTPbis as a parameter and
     VRFY "René Déscartes" UTF8SMTPbis
would work just fine (assuming the client had checked that EHLO allowed  
UTF8SMTPbis).

If we go ahead with some UTF8SMTPbis parameter, as Ned is asking, then it  
may as well be allowed for all commands (VRFY EXPN MAIl RCPT DATA).

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From johnl@iecc.com  Wed Dec 29 07:57:19 2010
Return-Path: <johnl@iecc.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 2CFF228C108 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 07:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.136
X-Spam-Level: 
X-Spam-Status: No, score=-111.136 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.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 OcZoac00mzu6 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 07:57:17 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 93E5A28C10F for <ima@ietf.org>; Wed, 29 Dec 2010 07:57:17 -0800 (PST)
Received: (qmail 74764 invoked from network); 29 Dec 2010 15:59:22 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 29 Dec 2010 15:59:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=15637.4d1b5adb.k1012; i=johnl@user.iecc.com; bh=eB4yzjcKO0Pz5G9COZjL9ui6u2yRaHA4MwxbK7ft9pI=; b=w17ur4a7jXEpzPw4XUW3/YCLFMd/dpYqF2YpXmr3qbQMQbAyYJKxxleWurt8n/3XwqkvkeTruVtGsPunv0YntLM/TdMKCDztVYv2cxOZvozEfyi0/EIiR06jv4LClGwFXIO05l27brjrII5822kNeCGVji15MZ5axi1CGwLH6xM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=15637.4d1b5adb.k1012; olt=johnl@user.iecc.com; bh=eB4yzjcKO0Pz5G9COZjL9ui6u2yRaHA4MwxbK7ft9pI=; b=eREjdv6dUD5zFMoCJA6v5Z+K+kasxIIhle0DuC3S3p4PkCEg9MUv91NMGFJZcm0hychQSHFatsw8/1p6DEKLWtzsbF+94T+CN5+Rt5X5WQXCHbSKdwq/lX+6sW2Sxf4g1p1j/dtznDWd2U5tE5P5xI47jw80rYrvXReBHwJNivg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 29 Dec 2010 15:59:23 -0000
Message-ID: <20101229155923.87606.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ima@ietf.org
In-Reply-To: <01NVYK39E5FO007CHU@mauve.mrochek.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 15:57:19 -0000

Just as a reality check, does anyone have any idea how many mail
servers still support EXPN or VRFY on the public Internet?  I tried a
bunch of large familiar mail systems, and got mostly 502 responses,
with a smattering of 500 and 252.  It is my impression that online
directory lookups happen with LDAP if they happen at all, and this
tempest is in a very small teapot.

If we do think that it's worth EAI-zing them, I reiterate my
suggestion of a STARTEAI command, rather than adding syntactically
tricky parameters to MAIL, VRFY, and/or EXPN.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From ned+ima@mrochek.com  Wed Dec 29 09:46:12 2010
Return-Path: <ned+ima@mrochek.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 DAA173A6863 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 09:46:12 -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 9xuUvHgiuswI for <ima@core3.amsl.com>; Wed, 29 Dec 2010 09:46:11 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 774D83A685B for <ima@ietf.org>; Wed, 29 Dec 2010 09:46:11 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVZLGX4KGW009GE9@mauve.mrochek.com> for ima@ietf.org; Wed, 29 Dec 2010 09:48:10 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVYGXLX10W007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Wed, 29 Dec 2010 09:48:00 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NVZLGRF9E4007CHU@mauve.mrochek.com>
Date: Wed, 29 Dec 2010 09:32:14 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 15:59:23 +0000" <20101229155923.87606.qmail@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293641922; bh=x0vhQa2QAEOUvOLuJEOcvvF72AUauzyiWRUKcmExlFQ=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=drHaN5aPKFdxa9aORUqJZ+DEeDZmdL7v3vfdwxVvxIf8GjThBvvhFzTy88A3oyRPQ oX+ClqmUzD14eyD/XVAv4JT7bdo58n+zXg9mpQ8l0SxT2J4wNQ5GeNj4BvgYjp+wL5 RD7r+hQvIx3+dnZKf3y+H319pPA0oky5RC0eje/o=
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 17:46:13 -0000

> Just as a reality check, does anyone have any idea how many mail
> servers still support EXPN or VRFY on the public Internet?

Which, given how VRFY/EXPN are actually used in practice, is a completely
meaningless number and a check of absolutely nothing close to reality. Just
because an option isn't offered to random schmoes like you who happen by
doesn't mean it's of no use. You might as well argue that because you tested a
bunch of MTAs and found that they weren't willing to relay mail for you, we
shouldn't concern ourselves with relay operations in our standards.

> I tried a
> bunch of large familiar mail systems, and got mostly 502 responses,
> with a smattering of 500 and 252.  It is my impression that online
> directory lookups happen with LDAP if they happen at all, and this
> tempest is in a very small teapot.

Well, all I can say is that you are quite simply wrong. And I have already
explained why in previous notes.

> If we do think that it's worth EAI-zing them, I reiterate my
> suggestion of a STARTEAI command, rather than adding syntactically
> tricky parameters to MAIL, VRFY, and/or EXPN.

First of all, there's nothing problematic about parameters to MAIL - we have
already defined a bunch of them, and aside from a couple of glitches having to
do with encoding disagreements - which had nothing to do with the overall
parsing of the line - I know of no interoperability issues they've caused.

Second, the notion of using a general announcer is a truly terrible idea. The
reason it's a terrible idea is that only some subset of the messages a given
MTA handles will be EAI messages. So when you process an EAI message followed
by a non-EAI message, you most certainly do not want the non-EAI message to be
flagged as EAI. So you need a way to turn that indicator off. There are two
ways to do that: Disconnect/reconnect or provide an off-switch. But now you
have what amounts to a global state bit that you have to keep track of. And
this is a sure-fire recipe for implementation issues and interoperability
problems.

				Ned

From klensin@jck.com  Wed Dec 29 10:11:35 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 8D1903A680E for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level: 
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 VB0DM+g-Fjns for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:11:34 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 7E44F3A67F1 for <ima@ietf.org>; Wed, 29 Dec 2010 10:11:32 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PY0Wk-000PWj-Tx; Wed, 29 Dec 2010 13:13:35 -0500
X-Vipre-Scanned: 0FAD6775001DEB0FAD68C2-TDI
Date: Wed, 29 Dec 2010 13:13:34 -0500
From: John C Klensin <klensin@jck.com>
To: ned+ima@mrochek.com, John Levine <johnl@taugh.com>
Message-ID: <3593064B56C9F619AD72997C@[192.168.1.128]>
In-Reply-To: <01NVZLGRF9E4007CHU@mauve.mrochek.com>
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan> <01NVZLGRF9E4007CHU@mauve.mrochek.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] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 18:11:35 -0000

--On Wednesday, December 29, 2010 9:32 AM -0800
ned+ima@mrochek.com wrote:

>...
> Second, the notion of using a general announcer is a truly
> terrible idea. The reason it's a terrible idea is that only
> some subset of the messages a given MTA handles will be EAI
> messages. So when you process an EAI message followed by a
> non-EAI message, you most certainly do not want the non-EAI
> message to be flagged as EAI. So you need a way to turn that
> indicator off. There are two ways to do that:
> Disconnect/reconnect or provide an off-switch. But now you
> have what amounts to a global state bit that you have to keep
> track of. And this is a sure-fire recipe for implementation
> issues and interoperability problems.

Well, one could also organize things so that RSET would do
provide the "off" function, rather that requiring (bleech)
STOPEAI or "STARTEAI STOP".  But that is just a way to
manipulate the global state and does not make it a less terrible
idea.

     john




From johnl@taugh.com  Wed Dec 29 10:25:23 2010
Return-Path: <johnl@taugh.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 BBD863A6869 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.141
X-Spam-Level: 
X-Spam-Status: No, score=-11.141 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.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 kUacMWxpzUQL for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:25:22 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 73E593A683E for <ima@ietf.org>; Wed, 29 Dec 2010 10:25:22 -0800 (PST)
Received: (qmail 9022 invoked from network); 29 Dec 2010 18:27:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=233d.4d1b7d8e.k1012; i=johnl@submit.iecc.com; bh=bEW+gkddoDsWZwUHz4VtuwZ5d+QChAIxqWHCW5m4KkU=; b=qdzt/KogF/NNGm3EXFXg96WDlsjMPCn/g6k1NwfRXvFzGcMkRT3p5fTmUSQ9i9a0unq9E+EdaapagwZYxDWRtvGGcqUVKUG+WX7mwSgRBsvg5WGuxCapJB0HDnTDLFsO7djHMtqKN04ptUxHCol1uTjkX8VDLRul+ttbZus3gPM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=233d.4d1b7d8e.k1012; olt=johnl@submit.iecc.com; bh=bEW+gkddoDsWZwUHz4VtuwZ5d+QChAIxqWHCW5m4KkU=; b=Gfcp9RSpeap9bWHWJUv7j5CQ4OyIa9n2aLpM6m6xJvV5mzCowwjmDlPC8H+uvzx00YuPRFoyb7zcsSAL0luyCp3tFLBJmtcICJLZr+6yu0Z0hT89J+px3TgXzfY8NtE13iQsWN08Gwu5GMo4bSnISnr2umpyEom9NgsHTNuyzLE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Dec 2010 18:27:04 -0000
Date: 29 Dec 2010 13:27:26 -0500
Message-ID: <alpine.BSF.2.00.1012291306180.97686@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ned Freed" <ned.freed@mrochek.com>
In-Reply-To: <01NVZLGRF9E4007CHU@mauve.mrochek.com>
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan> <01NVZLGRF9E4007CHU@mauve.mrochek.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 18:25:23 -0000

>> Just as a reality check, does anyone have any idea how many mail
>> servers still support EXPN or VRFY on the public Internet? ...

> Well, all I can say is that you are quite simply wrong. And I have already
> explained why in previous notes.

I saw that you said that some places use them internally, perhaps after 
AUTH.  That's fine, but that seems like private network stuff, which 
hasn't generally been a priority to standardize.

> First of all, there's nothing problematic about parameters to MAIL - we have
> already defined a bunch of them, ...

> Second, the notion of using a general announcer is a truly terrible 
> idea. ...

If you have a flag on MAIL, the MAIL command turns on a global state bit, 
the flag has to be remembered through the session through RCPT and DATA. 
If there are other random commands in between such as NOOP or EXPN or 
VRFY, it has to be remembered past them, too.  The bit gets turned off 
sometime between the dot at end of data and the next MAIL command.

If you have a flag command, STARTEAI turns the bit on and RSET or EHLO 
turns it off.  I'm having trouble seeing why the first bit is good and the 
second bit is bad.

There's nothing wrong with a MAIL flag, but flagging EXPN and VRFY seems 
to be a problem due to the loose syntax of those commands that, as far as 
I can tell, would have to retroactively make whatever the flag is into a 
reserved word in those commands.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From Shawn.Steele@microsoft.com  Wed Dec 29 10:50:47 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 0F3AB3A6855 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.402
X-Spam-Level: 
X-Spam-Status: No, score=-10.402 tagged_above=-999 required=5 tests=[AWL=0.197, 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 V2isFV9TSUWe for <ima@core3.amsl.com>; Wed, 29 Dec 2010 10:50:45 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 904233A67D6 for <ima@ietf.org>; Wed, 29 Dec 2010 10:50:45 -0800 (PST)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 29 Dec 2010 10:52:44 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0255.003; Wed, 29 Dec 2010 10:52:41 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: ascii nomenclature
Thread-Index: AQHLp4mSo7ikDWyGRk6giVJBiYGK7A==
Date: Wed, 29 Dec 2010 18:52:41 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B48E95@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] ascii nomenclature
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: Wed, 29 Dec 2010 18:50:47 -0000

VGhlc2UgIHdvdWxkIHdvcmsgZm9yIG1lLi4uDQoNCi1TaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg76Oi
76Oj76OX76OU76OZDQpodHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGUNCg0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KDQogQSAiVS1sYWJlbCIgaXMgYW4gSUROQS12YWxpZCBzdHJpbmcgb2Yg
VW5pY29kZSBjaGFyYWN0ZXJzLCBpbg0KICAgICAgTm9ybWFsaXphdGlvbiBGb3JtIEMgKE5GQykg
YW5kIGluY2x1ZGluZyBhdCBsZWFzdCBvbmUgbm9uLUFTQ0lJDQogICAgICBjaGFyYWN0ZXIsIGV4
cHJlc3NlZCBpbiBhIHN0YW5kYXJkIFVuaWNvZGUgRW5jb2RpbmcgRm9ybSAoc3VjaCBhcw0KICAg
ICAgVVRGLTgpLg0KDQoNCkkgc3VnZ2VzdCB0byBkZWZpbmUgdGhlIGZvbGxvd2luZyB0ZXJtczoN
Cg0KVS1jaGFyYWN0ZXI6DQogQSAiVS1jaGFyYWN0ZXIiIGlzIGEgbm9uLUFTQ0lJIFVuaWNvZGUg
Y2hhcmFjdGVyLCBpbg0KICAgICAgTm9ybWFsaXphdGlvbiBGb3JtIEMgKE5GQykgYW5kIGV4cHJl
c3NlZCBpbiBhIHN0YW5kYXJkIFVuaWNvZGUgRW5jb2RpbmcgRm9ybSBvZiBVVEYtOC4NCg0KDQpV
LXN0cmluZzoNCiBBICJVLXN0cmluZyIgaXMgYSBzdHJpbmcgb2YgVW5pY29kZSBjaGFyYWN0ZXJz
LCBpbg0KICAgICAgTm9ybWFsaXphdGlvbiBGb3JtIEMgKE5GQykgYW5kIGluY2x1ZGluZyBhdCBs
ZWFzdCBvbmUgbm9uLUFTQ0lJDQogICAgICBjaGFyYWN0ZXIsIGV4cHJlc3NlZCBpbiBhIHN0YW5k
YXJkIFVuaWNvZGUgRW5jb2RpbmcgRm9ybSBvZiBVVEYtOC4NCg0KQS1jaGFyYWN0ZXI6DQogIEFu
ICAiQS1jaGFyYWN0ZXIiIGlzIGFuIEFTQ0lJIFVuaWNvZGUgY2hhcmFjdGVyLCBleHByZXNzZWQg
aW4gYSBzdGFuZGFyZCBVbmljb2RlIEVuY29kaW5nIEZvcm0gb2YgVVRGLTguDQoNCkEtc3RyaW5n
Og0KIEFuICAiQS1zdHJpbmciIGlzICBhIHN0cmluZyBvZiBVbmljb2RlIGNoYXJhY3RlcnMsICBp
bmNsdWRpbmcgQVNDSUkNCiAgICAgIGNoYXJhY3RlcnMgb25seSwgZXhwcmVzc2VkIGluIGEgc3Rh
bmRhcmQgVW5pY29kZSBFbmNvZGluZyBGb3JtIG9mIFVURi04Lg0KDQoNCmFyZSAgdGhlIGRlZmlu
aXRpb25zIGFib3ZlIGNsZWFyPw0KDQoNCmFub3RoZXIgcXVlc3Rpb24gaXMgdGhhdCB3ZSBkZWZp
bmUgdGhlc2UgbmV3IHRlcm1zIGluIHJmYzUzMzZiaXMgb3IgaW4gcmZjNDk1MmJpcz8NCg0KDQp0
aGFua3MuDQoNCkppYW5rYW5nIFlhbw==

From ned+ima@mrochek.com  Wed Dec 29 11:05:02 2010
Return-Path: <ned+ima@mrochek.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 53DD93A687A for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, 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 RvbRDyNtqQRA for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:05:01 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id A1A693A6878 for <ima@ietf.org>; Wed, 29 Dec 2010 11:04:59 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVZO8LB4N400FIME@mauve.mrochek.com> for ima@ietf.org; Wed, 29 Dec 2010 11:06:57 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NVYGXLX10W007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Wed, 29 Dec 2010 11:06:50 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NVZO8H0IVS007CHU@mauve.mrochek.com>
Date: Wed, 29 Dec 2010 10:46:28 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 17:05:10 +0900" <4D1AEBB6.9030402@it.aoyama.ac.jp>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1; Format=flowed
References: <2B9258A1B04B6596D4F07D20@[192.168.1.128]> <4D1AEBB6.9030402@it.aoyama.ac.jp>
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293646650; bh=vNZreF8q/oc3b1N6WkzxkoykDFnmWep6hnJwP/+tyLY=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=f7R28vV5ihBWuGxpezOuAgoQRsaOxCj5yys1WNHdCcCU20drk1DJ+X2zfxniTIgpJ JT5n42yKJX5/jyLDLqfOioQFYj1SD+rRPPTsNPdWRtc6bZvaUSL0Ex/xOKlydE5yJJ 8YTBNI72ZFJREnYeuhaMp2u1VgjxmYuLrgIyhhP8=
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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: Wed, 29 Dec 2010 19:05:02 -0000

> In the hope to move the debate forward, and after the clarifications by
> Alex and Ned, but not an email infrastructure insider, my preferences below.

> On 2010/12/28 9:21, John C Klensin wrote:
> > (writing as co-chair and incorporating the introduction to the
> > note I sent a few minutes ago by reference)
> >
> > Topic: The description of VRFY and EXPN handling in 5336bis is
> > not adequate.  Whatever is done, we will have to change/fix it.
> > In the questions below, I've mentioned VRFY but I assume that
> > EXPN would get exactly the same treatment.
> >
> > Questions:
> >
> > (1) Should VRFY be retained as is, with the parameter, but with
> > a restriction that the parameter MUST NOT be used without EHLO
> > appearing first.

> That seems like an easy fix.

Agreed, as long as there's no requirement that servers MUST enforce this
restriction.

> > (2) Should VRFY be retained as is, with the parameter and
> > without the "ok to use VRFY without a session, i.e., without
> > EHLO first".  Note that this would be the first time an SMTP
> > extension has been permitted without explicit server permission
> > via EHLO and that it involves a small risk of non-EAI-aware
> > servers parsing the parameter as part of a name sent by a client.

> It seems that this is what the reviewers have advised against, so I
> guess we should give up on it.

I'm less worried about this than others are, but it's a legitimate concern.

> > (3) Should we move toward a new command, replacing VRFY, but
> > with more specific syntax that explicitly provides for
> > parameters and, presumably, a mail session?   Note that, if the
> > answer to this is "yes", someone would need to generate a
> > proposal that could be processed separately from the EAI effort.

I would hope that any refinement of VRFY would, in addition to allowing actual
addresses to be specified (and defining the semantics for what such a query
means), also provide for structured return value. In short, if we're going to
go down the new command path, we should look at what additional needs could be
met by such a mechanism. But all this is far outside of EAI's scope.

> > While generating the proposal is no problem, the specification
> > of the new command would create a normative dependency from
> > 5336bis and that might slow things down in terms of publication
> > of 5336bis/ 5335bis/ 5337bis.

> I'm not sure why this would need to be separate from EAI.

The main reason, aside from the obvious process issues, is that this isn't
quite the right group to design and review such a proposal.

> It's obviously for EAI.

Well, that depends on how far the proposal goes. If all we're doing is defining
VFY8/EXP8 and changing nothing else, then sure, this could be part of EAI, just
as adding a parameter to the existing commands can be. (I've already explained
why I strongly prefer a parameter to additional single-purpose commands.)

But once you sit down and define a proper replacement, at an absolute minimum
you're going to want to make it able to accept addresses. And as I noted, this
isn't the right group for that.

> Of course, we have to come up with new command names, but that
> should be easy (some already circulated on the list). Apart from that,
> take the current syntax, and change text from "new syntax on old
> command" to "new command", which I'd guess is mostly a clerical
> exercise. Or did I get something wrong?

> Anyway, my order of preference would be (1), (3), (2).

That's mine as well.

				Ned

From Shawn.Steele@microsoft.com  Wed Dec 29 11:09:22 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 3E3DB3A6867 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.409
X-Spam-Level: 
X-Spam-Status: No, score=-10.409 tagged_above=-999 required=5 tests=[AWL=0.190, 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 TQuCaMZa3YoR for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:09:16 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id C2FB03A6855 for <ima@ietf.org>; Wed, 29 Dec 2010 11:09:16 -0800 (PST)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 29 Dec 2010 11:11:20 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0255.003; Wed, 29 Dec 2010 11:11:20 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Parameter on MAIL command
Thread-Index: AQHLp4ws3lxwGwKnrECyMArG/cBprg==
Date: Wed, 29 Dec 2010 19:11:19 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B48F2B@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.123.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [EAI] Parameter on MAIL command
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: Wed, 29 Dec 2010 19:09:22 -0000

SSB0aGluayBhIHBhcmFtZXRlciBvbiBNQUlMIGlzIGFjY2VwdGFibGUsIGJ1dCBJJ2QgcHJlZmVy
IGlmIGl0IHdlcmUgYm9vbGVhbiAocHJlc2VudCBvciBub3QsIGxpa2Ugd2UgaGF2ZSBmb3IgVlJG
WS9FWFBOKSwgYW5kIHdlIG1heSBhcyB3ZWxsIHVzZSB0aGUgc2FtZSBwYXJhbWV0ZXIgZm9yIGFs
bCAzLiAgIlVURjhTTVRQIiBvciAiVVRGOCIgd291bGQgYmUgc3VmZmljaWVudC4NCg0KSSdtIG5v
dCBzdXJlIHdoYXQgcHVycG9zZSB0aGUgcGFyYW1ldGVyIHdvdWxkIHNlcnZlIG9uIFJDUFQgb3Ig
REFUQS4gIFNlZW1zIGxpa2UgdGhlcmUnZCBiZSBjb25mdXNpbmcgY2FzZXMgaWYgdGhlIG1haWwg
InN0YXJ0ZWQiIHdpdGggYSBVVEY4IGZsYWcgKE1BSUwpLCBhbmQgZGlkbid0IGhhdmUgdGhhdCBw
cmVzZW50IGluIFJDUFQgb3IgREFUQS4gIFRoYXQgY29tcGxleGl0eSB3b3VsZCBtZWFuIGRlY2lk
aW5nIHdoYXQgdG8gZG8gaW4gdGhvc2UgY2FzZXMsIHRoZW4gY29kZSBwYXRocy90ZXN0cyB0byBt
YWtlIHN1cmUgdGhhdCBiZWhhdmVkLiAgSSdkIHJhdGhlciBoYXZlIGl0ICJvbiIgb3IgIm9mZiIg
Zm9yIGEgc2luZ2xlIG1lc3NhZ2UuDQoNCi1TaGF3bg0KDQrvo6Lvo5Dvo6fvo5sg76Oi76Oj76OX
76OU76OZDQpodHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGU=

From klensin@jck.com  Wed Dec 29 11:28:32 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 0559C3A6879 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 3YpJ+d077O1k for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:28:30 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 8C7673A686D for <ima@ietf.org>; Wed, 29 Dec 2010 11:28:30 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PY1jH-00005N-OC; Wed, 29 Dec 2010 14:30:36 -0500
X-Vipre-Scanned: 0FF3E972001DEB0FF3EABF-TDI
Date: Wed, 29 Dec 2010 14:30:34 -0500
From: John C Klensin <klensin@jck.com>
To: dcrocker@bbiw.net
Message-ID: <E5F8CCE3E3046EA5F0D8D34C@[192.168.1.128]>
In-Reply-To: <4D1AD148.7070000@dcrocker.net>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@[192.168.1.128]> <4D1AD148.7070000@dcrocker.net>
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] Unicode vs. UTF-8 / Encoding vs. Representation
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: Wed, 29 Dec 2010 19:28:32 -0000

--On Tuesday, December 28, 2010 10:12 PM -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

>...
>> Unfortunately, this doesn't work either if one aspires to the
>> kind of precision for which you seem to be asking.
> 
> 1.  A 2x2 matrix isn't all that precise.

I'm not objecting to the matrix, only to the terms, even though
I think we need to be sure that we don't confuse encoding with
embedding (ASCII in an eight bit field isn't the only problem;
technically UTF-32 is an embedding of the Unicode code point
integer space (0 ... 0x10FFFF) in a 32-bit field.  Worse, both
UTF-16 and UTF-32 have big-endian and little-endian variations.
 
> 2.  Retaining ambiguous terms doesn't work very well, either.
> 
> 3.  The terms I suggested all have established use.

And, by the parameters of this conversation, established
somewhat ambiguous use.

> 4.  RFC 20 (October, 1969) which has a version of the same
> language I used for citing ASCII as an encoding form, as you
> also cite:
> 
>         "7-bit ASCII embedded in an 8 bit byte whose high
> order bit is always 0"
> 
> In other words, "7-bit" is a long-established term for an
> encoding of ASCII.

I can't get from that longer statement to your conclusion.  The
reality is that we have been sloppy about these differences for
years and have gotten away with it because everyone knew how to
extrapolate from ASCII-the-repertoire to ASCII-the-encoding to
ASCII-the-embedding, especially since TENEX/TOPS-20 (ASCII
stored in 7 bit fields) and Multics (ASCII stored in 9 bit
fields with two leading zeros) stopped being important forces in
the network.  I didn't have enough contact with the relevant
systems to know whether IBM OS/360 ASCII (parity bit in the
middle, if I recall) was ever actually used in ARPANET/Internet
contexts, but, if it was, it should be added to that "no longer
an important force" list.

> So, in spite of the length of your note, I could not discern
> what you consider to be deficient in the terminoloy matrix I
> suggest, nor what alternative(s) you suggest.

See above.

Suggested alternative #1:

	Define new, precise, terms on an IETF-wide basis rather
	than trying to make patches that eliminate some of the
	imprecision and reusing terms that are in use elsewhere
	with other meanings.  If we are going to do that, I
	think Andrew's terms would be a reasonable starting
	point.  But it is clear to me that definitional work is
	not an appropriate task for the EAI WG to take on.

Suggested alternative #2: 

	We localize the definitions, using YangWoo's suggestion
	as a starting point and ignoring any cells of your
	matrix (or my slightly larger one) that we don't need.
	
>...

     john




From klensin@jck.com  Wed Dec 29 11:38:48 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 3FE213A67AA for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  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 iUZs1x2fv1sT for <ima@core3.amsl.com>; Wed, 29 Dec 2010 11:38:29 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 0EFA33A67D6 for <ima@ietf.org>; Wed, 29 Dec 2010 11:38:29 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PY1sv-0000Bu-V1; Wed, 29 Dec 2010 14:40:34 -0500
X-Vipre-Scanned: 0FFD0A3C001DEB0FFD0B89-TDI
Date: Wed, 29 Dec 2010 14:40:33 -0500
From: John C Klensin <klensin@jck.com>
To: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
Message-ID: <0141500E06782DD298E3708D@[192.168.1.128]>
In-Reply-To: <op.vog26e2l6hl8nm@clerew.man.ac.uk>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <01NVQAP0UQRU007CHU@mauve.mrochek.com> <227C2506194609988B81BE4F@PST.JCK.COM> <01NVVQNSWU7U007CHU@mauve.mrochek.com> <3F5293BF906846C89013734B3D6262D9@upstairs> <7C0660F7DFFE9C1990252217@[192.168.1.128]> <op.vofb01pj6hl8nm@clerew.man.ac.uk> <B2DA8473E8F67A3F495A9D67@[192.168.1.128]> <op.vog26e2l6hl8nm@clerew.man.ac.uk>
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] [apps-discuss] RFC5336 and VRFY/EXPN (was:	Re:	apps-team	review of draft-ietf-eai-rfc5336bis)
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: Wed, 29 Dec 2010 19:38:48 -0000

--On Wednesday, December 29, 2010 11:21 AM +0000 Charles Lindsey
<chl@clerew.man.ac.uk> wrote:

>> The problem is (mostly) not what the client sends but what =
the
>> server can return.   Suppose the server advertises =
UTF8SMTPbis
>> and the client sends "VRFY rene" (all-ASCII).  Now the server
>> doesn't know whether it is plausible to return an address
>> containing non-ASCII characters or not: the client has to
>> somehow give it permission to do that.
>=20
> I think I would take the view that if the client behaves as a
> pure legacy client, then the server should respond like a pure
> legacy server. So if we want a server to offer
> ren=C3=A9@example.com in response to a request for (pure =
ASCII)
> 'rene', then we need some extended syntax (either a parameter
> or a new command).

yes

> But I am not sure we need that facility
> anyway (and I suspect Ren=C3=A9 himself would be most offended =
to
> be addressed as Rene).

For a better example, suppose one had
   VRFY mueller
and the response should have been
   m=C3=BCller@example.com
Then, while Muller might not like it, or even be offended, she
(and almost everyone else) would certainly anticipate the
linkage between that query and that result.   But we agree that
a parameter is needed in that case, so perhaps it is a =
non-issue.
=20
> Indeed, but I think you missed the real point of my message,
> which was suggesting that a client MUST do an EHLO (and check
> for UTF8SMTPbis) _before_
> issuing "VRFY ren=C3=A9", and that any VRFY issued _without_ a
> prior EHLO would be constrained to pure ASCII only. That would
> remove any need for any 'new-VRFY' command AFAICS.

Again, the reason for either the new command (presumably with a
parameter) and a parameter on VRFY has to do with possible
responses, not what appears as a command argument.    That is
where John Levine's argument comes in: only a command that
explicitly starts an EAI session from the client side and is
then followed by VRFY can eliminate the need for the parameter.

>> But, if the server advertises UTF8SMTPbis, it could certainly
>> be telling the client that it expects an 5321 interpretation
>> of the VRFY command, for which the syntax is unambigious. ...
>=20
> No, it would not tell a legacy client that. It has to assume a
> legacy client unless it receives explicit information
> (parameter or new command) to the contrary.

Ok. We agree.

I've covered your other comments in other notes, I think.

   john


From jyee@ca.afilias.info  Wed Dec 29 14:31:23 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 6CAF028C11E for <ima@core3.amsl.com>; Wed, 29 Dec 2010 14:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.724
X-Spam-Level: 
X-Spam-Status: No, score=-105.724 tagged_above=-999 required=5 tests=[AWL=0.389, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152, 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 MzujXPdgmTOL for <ima@core3.amsl.com>; Wed, 29 Dec 2010 14:31:21 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id CED3E28B797 for <ima@ietf.org>; Wed, 29 Dec 2010 14:31:20 -0800 (PST)
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: <E5F8CCE3E3046EA5F0D8D34C@[192.168.1.128]>
Date: Wed, 29 Dec 2010 17:33:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@[192.168.1.128]> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@[192.168.1.128]>
To: John C Klensin <klensin@jck.com>
X-Mailer: Apple Mail (2.1082)
X-Authenticated: True
Cc: dcrocker@bbiw.net, ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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: Wed, 29 Dec 2010 22:31:23 -0000

On 2010-12-29, at 2:30 PM, John C Klensin wrote:

>=20
>=20
> --On Tuesday, December 28, 2010 10:12 PM -0800 Dave CROCKER
> <dhc2@dcrocker.net> wrote:
>=20
>> ...
>>> Unfortunately, this doesn't work either if one aspires to the
>>> kind of precision for which you seem to be asking.
>>=20
>> 1.  A 2x2 matrix isn't all that precise.
>=20
> I'm not objecting to the matrix, only to the terms, even though
> I think we need to be sure that we don't confuse encoding with
> embedding (ASCII in an eight bit field isn't the only problem;
> technically UTF-32 is an embedding of the Unicode code point
> integer space (0 ... 0x10FFFF) in a 32-bit field.  Worse, both
> UTF-16 and UTF-32 have big-endian and little-endian variations.
>=20
>> 2.  Retaining ambiguous terms doesn't work very well, either.
>>=20
>> 3.  The terms I suggested all have established use.
>=20
> And, by the parameters of this conversation, established
> somewhat ambiguous use.
>=20
>> 4.  RFC 20 (October, 1969) which has a version of the same
>> language I used for citing ASCII as an encoding form, as you
>> also cite:
>>=20
>>        "7-bit ASCII embedded in an 8 bit byte whose high
>> order bit is always 0"
>>=20
>> In other words, "7-bit" is a long-established term for an
>> encoding of ASCII.
>=20
> I can't get from that longer statement to your conclusion.  The
> reality is that we have been sloppy about these differences for
> years and have gotten away with it because everyone knew how to
> extrapolate from ASCII-the-repertoire to ASCII-the-encoding to
> ASCII-the-embedding, especially since TENEX/TOPS-20 (ASCII
> stored in 7 bit fields) and Multics (ASCII stored in 9 bit
> fields with two leading zeros) stopped being important forces in
> the network.  I didn't have enough contact with the relevant
> systems to know whether IBM OS/360 ASCII (parity bit in the
> middle, if I recall) was ever actually used in ARPANET/Internet
> contexts, but, if it was, it should be added to that "no longer
> an important force" list.

Echo to John's comment, using "7-bit" as the word for encoding is in the =
category of "you know what I mean" in writing.


>=20
>> So, in spite of the length of your note, I could not discern
>> what you consider to be deficient in the terminoloy matrix I
>> suggest, nor what alternative(s) you suggest.
>=20
> See above.
>=20
> Suggested alternative #1:
>=20
> 	Define new, precise, terms on an IETF-wide basis rather
> 	than trying to make patches that eliminate some of the
> 	imprecision and reusing terms that are in use elsewhere
> 	with other meanings.  If we are going to do that, I
> 	think Andrew's terms would be a reasonable starting
> 	point.  But it is clear to me that definitional work is
> 	not an appropriate task for the EAI WG to take on.
>=20
> Suggested alternative #2:=20
>=20
> 	We localize the definitions, using YangWoo's suggestion
> 	as a starting point and ignoring any cells of your
> 	matrix (or my slightly larger one) that we don't need.

I agreed that Unicode and UTF-8 are great terms to start with.  Maybe =
something like "ASCII" on representation (I just wish we could use =
'English' instead) and "ASCII Encoding" or "ASCII-Encoding" to make the =
distinction from representation.

And we still don't know how to represent the set of "Unicode excluding =
ASCII".

And expanding from Andrew's idea, maybe using "mailbox" instead of =
"set"?
So it's "A-mailbox", "U-mailbox" and "X-mailbox"?

(hoping few more iterations would generate good idea/result)

best
Joseph

> =09
>> ...
>=20
>     john
>=20
>=20
>=20
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima


From yangwooko@gmail.com  Wed Dec 29 18:21:46 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 3919A28C134 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 18:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.939
X-Spam-Level: 
X-Spam-Status: No, score=-2.939 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 84ruPW46y1pT for <ima@core3.amsl.com>; Wed, 29 Dec 2010 18:21:44 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 9C31F28C133 for <ima@ietf.org>; Wed, 29 Dec 2010 18:21:44 -0800 (PST)
Received: by vws7 with SMTP id 7so4199052vws.31 for <ima@ietf.org>; Wed, 29 Dec 2010 18:23:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=3/YRPrxZoxqXYUjpW2bKl627vBOIXtL/JIT9TTVVXG4=; b=EoTU6BC1PWtxsyARLnNU9gPAI/tmq3/hBILia0KAFeS5RUxpC4rzky+0gQa1RexU+d vRmK4Uodjp1ob+NTc5XBfOlegkXJGHAYKH8fd4VnmYtdTMBA9TIzwPq4Mk/5AiPxDRBE RPU7zrxYQrF76VtNWA38tPbGG6PRJj6KWOtQk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=FY31ptaV0mKe4bnDHkwFgWETFK8yFoxw5q5oj9DUeuTk3JbQgtyG4Xs3kLzGDLJ7Fr /9yXZuO833TO+JbIuJb+6AWlBuGrWfRU44FWmiMam4TqKtev7pgQKYuIU/cqYVl35qFF 3QcFM5L8vXnxxPudw/H0qjO2f0EKYen1fOnZg=
Received: by 10.220.158.211 with SMTP id g19mr759180vcx.86.1293675828356; Wed, 29 Dec 2010 18:23:48 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Wed, 29 Dec 2010 18:23:28 -0800 (PST)
In-Reply-To: <C32A1A5CB0814846B91BFAB307442A2B34285EE68F@FORGE.foundry.home>
References: <C32A1A5CB0814846B91BFAB307442A2B34285EE68F@FORGE.foundry.home>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Thu, 30 Dec 2010 11:23:28 +0900
X-Google-Sender-Auth: AIPHLsNpe4XEtLUHhn3ZDNoD1XU
Message-ID: <AANLkTim+1yZjc-TBj7PfUzG-vyYNqe5tPvCQoWZcyjYW@mail.gmail.com>
To: "ima@ietf.org" <ima@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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, 30 Dec 2010 02:21:46 -0000

I think the name "HEADER" is broader than what it intends to specify.
Better (not in terms of asthetics but in terms of scoping) name is
"HEADER ENCODING".

In addition to this, ASCII/UTF8 sounds more appropriate in this
context than ASCII/UNICODE.

On Wed, Dec 29, 2010 at 8:01 PM, Troy Starr <eai@troystarr.net> wrote:
>
>
> Hi Jiankang -
>
> First, apologies for not replying directly to your message and breaking y=
our message thread. =C2=A0I've been following the discussion of the mailing=
 list archive on the web without actually subscribing to it, but wanted to =
respond to your proposal. =C2=A0I've just subscribed to the mailing list no=
w, but I don't have your actual e-mail message to reply to. =C2=A0I've copi=
ed your original message below for context.
>
> I agree that having an explicit MAIL parameter would be valuable for the =
reasons already discussed. =C2=A0I'd like to propose a different parameter =
name and set of values, though. =C2=A0My concern with the UTF8HEADERS param=
eter name is that it is very closely tied to this RFC, which could make fut=
ure extensions more difficult than necessary. =C2=A0I don't know what those=
 future extensions might be, but I think it would be worthwhile to avoid po=
tential difficulty if it's relatively easy to do so.
>
> The closest analogy I could think of was the 8BITMIME SMTP extension (RFC=
 1652). =C2=A0That WG also decided to create a MAIL parameter to indicate t=
hat the message was taking advantage of that SMTP extension. =C2=A0However,=
 instead of creating a parameter called 8BITMIMEBODY with a binary value, t=
hey gave the parameter a more generic name (BODY) and set the value to the =
specific type (7BIT for legacy and 8BITMIME for the new functionality). =C2=
=A0That decision worked well for the future BINARYMIME SMTP extension (RFC =
3030), since it allowed them to reuse the existing BODY parameter and simpl=
y add an additional value to it (BINARYMIME).
>
> Making the parameter more generic may be of similar value to future worki=
ng groups. =C2=A0Therefore, I propose the following text instead:
>
> ----------
> An optional parameter using the keyword HEADER is added to the MAIL FROM =
command. =C2=A0The value associated with this parameter is a keyword indica=
ting whether the message contains only ASCII characters in the envelope and=
 header fields, or whether the message contains non-ASCII characters in the=
 envelope and header fields and MUST follow the guidelines of this RFC. =C2=
=A0The syntax of the value is as follows, using ABNF notation:
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0header-value ::=3D "ASCII" / "UNICODE"
>
> The maximum length of a MAIL FROM command line is increased by 15 charact=
ers by the possible addition of the HEADER keyword and value.
> ----------
>
> I see that there's an active discussion about ASCII/Unicode/UTF-8 termino=
logy within the mailing list, so the values used here should conform to wha=
tever consensus is reached. =C2=A0And of course, some may disagree and feel=
 that the UTF8HEADERS proposal is more than sufficient. =C2=A0I welcome any=
 feedback.
>
> - Troy Starr
> Full disclosure: I work for Microsoft, but am not speaking on their behal=
f or in any official capacity.
>
> -----Original Message-----
> From: Jiankang YAO [mailto: yaojk@cnnic.cn]
> Sent: Tuesday, December 28, 2010 11:23 PM
> To: ima@ietf.org
> Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
>
> ....
>>
>>
>>>Question: Should we define, and require, an announcement
>>>parameter on the MAIL command if the sender intends to transmit
>>>either non-ASCII addresses or UTF-8 in headers (other than as
>>>encoded words)?
>>>
>
> It seems that many colleagues in this list have agreed to add a parameter=
 =C2=A0on the MAIL command to indicate that
> whether the message transferred is =C2=A0in the format of UTF-8 in header=
s.
> If the WG has a consensus on it, I will update it in the next version.
>
> I propose the follow text about this parameter:
> -------------------------------------------------------------------------=
--------------------------
> One optional parameter is added to the SMTP MAIL command.
> =C2=A0This parameter is named as UTF8HEADERS. The "UTF8HEADERS" parameter
> has one of two values: y or n. The parameter "UTF8HEADERS" is
> designed to assert whether the message transferred is =C2=A0in the format=
 of UTF-8 in headers, which means
> that the message in the headers is in the format of UTF-8[RFC5336bis] if =
the value is 'y' or not if the value is
> 'n'.
> If the server is not EAI-aware,
> the =C2=A0"UTF8HEADERS" parameter MUST not be used in the MAIL command by=
 the client.
> -------------------------------------------------------------------------=
------------------------
>
> any comments are welcome.
>
> Thanks.
>
> Jiankang Yao
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human known as yangwooko@gmail.com @ gtalk

From yangwooko@gmail.com  Wed Dec 29 18:51:44 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 E6B1128C133 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 18:51:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.871
X-Spam-Level: 
X-Spam-Status: No, score=-2.871 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 gT+8M9VaVTQw for <ima@core3.amsl.com>; Wed, 29 Dec 2010 18:51:44 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 08D0F28B23E for <ima@ietf.org>; Wed, 29 Dec 2010 18:51:43 -0800 (PST)
Received: by qwg5 with SMTP id 5so11203836qwg.31 for <ima@ietf.org>; Wed, 29 Dec 2010 18:53:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=Zgk1RDyS8VIEb/UOSL/VJAi9cD2c8vBUcpF4br2arxc=; b=hvn5lQ+oXbT5ZKJjtEJfldOYDiBLTfb4TMfzKIkLFkIhHZoFibUF0ZqWuu/UAFuFv+ bdpxPuRTIcmSs/bt4VB9YAlBoEQSMk7H8jGVpxkUEug1U4W6BdGJguHCTTGRxwaaHOOe 1UpDUiY9h7NyStjurR0RzrJFFR3vHodB3G8eM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=ZlEpOCjmk0tYoaAAJwJMWRE66VSo/OidZc4sokSWS9gOJJ9ybJTeHHASbqFdAbIMeq 8NIKF0spMHqPo9ZQ/Nvgw8HhElx/8IKlKmJLztr4JPZ0K8Qzx2jKeTDjOYXqJsMIbBiy Wj3MW03iF2I1d9iArPlvXD62DYc2YK3QhzOyU=
Received: by 10.229.233.74 with SMTP id jx10mr13990528qcb.97.1293677629435; Wed, 29 Dec 2010 18:53:49 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Wed, 29 Dec 2010 18:53:29 -0800 (PST)
In-Reply-To: <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@192.168.1.128> <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Thu, 30 Dec 2010 11:53:29 +0900
X-Google-Sender-Auth: MHx1uk5JNU9nIrlSFC7NS-eq-Xg
Message-ID: <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com>
To: Joseph Yee <jyee@ca.afilias.info>
Content-Type: text/plain; charset=UTF-8
Cc: dcrocker@bbiw.net, ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 30 Dec 2010 02:51:45 -0000

On Thu, Dec 30, 2010 at 7:33 AM, Joseph Yee <jyee@ca.afilias.info> wrote:
> And we still don't know how to represent the set of "Unicode excluding ASCII".

What is this set for?

-- 
a human known as yangwooko@gmail.com @ gtalk

From ned+ima@mrochek.com  Wed Dec 29 19:59:09 2010
Return-Path: <ned+ima@mrochek.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 7C19C3A6904 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 19:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  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 2uCbpjM+L2hY for <ima@core3.amsl.com>; Wed, 29 Dec 2010 19:59:07 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 6CE263A63D3 for <ima@ietf.org>; Wed, 29 Dec 2010 19:59:07 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW06VWTDSW00E4V8@mauve.mrochek.com> for ima@ietf.org; Wed, 29 Dec 2010 20:01:09 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW014MBSMO007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Wed, 29 Dec 2010 20:01:05 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NW06VVF1P4007CHU@mauve.mrochek.com>
Date: Wed, 29 Dec 2010 19:59:59 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 03:01:25 -0800" <C32A1A5CB0814846B91BFAB307442A2B34285EE68F@FORGE.foundry.home>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <C32A1A5CB0814846B91BFAB307442A2B34285EE68F@FORGE.foundry.home>
To: Troy Starr <eai@troystarr.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293678700; bh=gaNMkiFRn9xJq3pYdp2inYEz8KIeqQMErGs0U+0UoUc=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=PwkaLn/c2n7KS04IO+AiAVt4ltrAsYdYX6lNFskNc//lzCW5OLKR9RT6a+lXnoejx Fy/3edAsU9lKNw2XY3IuT5fZOBILpGdIoLHAg1UM8E9S5ziadpv22rm7obIynm+0uM pwGnRyTOZZFWyBKnQCsmTCGybUZUHVw4s9xcRI+Y=
Cc: "'ima@ietf.org'" <ima@ietf.org>
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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, 30 Dec 2010 03:59:09 -0000

> ----------

> An optional parameter using the keyword HEADER is added to the MAIL FROM
> command.  The value associated with this parameter is a keyword indicating
> whether the message contains only ASCII characters in the envelope and header
> fields, or whether the message contains non-ASCII characters in the envelope
> and header fields and MUST follow the guidelines of this RFC.  The syntax of
> the value is as follows, using ABNF notation:

> 	header-value ::= "ASCII" / "UNICODE"

> The maximum length of a MAIL FROM command line is increased by 15 characters
> by the possible addition of the HEADER keyword and value.

> ----------

I think this is an excellent suggestion.

> I see that there's an active discussion about ASCII/Unicode/UTF-8 terminology
> within the mailing list, so the values used here should conform to whatever
> consensus is reached.

Agreed as well.

				Ned

From ned+ima@mrochek.com  Wed Dec 29 21:53:30 2010
Return-Path: <ned+ima@mrochek.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 721683A6910 for <ima@core3.amsl.com>; Wed, 29 Dec 2010 21:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 Z4ONaNqEEZiw for <ima@core3.amsl.com>; Wed, 29 Dec 2010 21:53:28 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 6B0DD3A688F for <ima@ietf.org>; Wed, 29 Dec 2010 21:53:26 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW0AVLX9JK00GAPU@mauve.mrochek.com> for ima@ietf.org; Wed, 29 Dec 2010 21:55:26 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW014MBSMO007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Wed, 29 Dec 2010 21:55:22 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NW0AVK5L3W007CHU@mauve.mrochek.com>
Date: Wed, 29 Dec 2010 20:39:12 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 13:27:26 -0500" <alpine.BSF.2.00.1012291306180.97686@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan> <01NVZLGRF9E4007CHU@mauve.mrochek.com> <alpine.BSF.2.00.1012291306180.97686@joyce.lan>
To: John R Levine <johnl@taugh.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293685558; bh=4q5Yn9gpHiYbrpjhYVdfEfR5YjWDhclWw5WdL7L4PPA=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=kx0p4ZPyIVCCd+2Ik1SKpISEMn8iqmn31xuPRN66S4zPcr5UcB+1tPn2lJ+2t2Hqy H3th1Y7+VUp1wxzR0gfXr34w70l/LMyld7h4desLU4awzmvEqWDbIc3dnMCr3nyybe +R0bR65Al+m9Um85D0Ckmv0IQigb/9phGy4ui1vM=
Cc: Ned Freed <ned.freed@mrochek.com>, ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 30 Dec 2010 05:53:30 -0000

> >> Just as a reality check, does anyone have any idea how many mail
> >> servers still support EXPN or VRFY on the public Internet? ...

> > Well, all I can say is that you are quite simply wrong. And I have already
> > explained why in previous notes.

> I saw that you said that some places use them internally, perhaps after
> AUTH.  That's fine, but that seems like private network stuff, which
> hasn't generally been a priority to standardize.

First of all, nowhere did I say that this is "private network stuff", and in
fact it isn't. It is fairly common to outsource various sorts of network
auditing and management operations, including these sorts of checks, with all
that such outsourcing implies.

But let's suppose for a moment that this really is just "private network
stuff". So what? The IETF routinely works on protocols that are relevant on the
LAN but have essentially no presence on the wider Internet like DHCP or
mDNS/Bonjour. Even LDAP, while it was intended for Whites Pages services, is in
practice "private network stuff".

And all this is exactly as it should be: While it is vitally important that the
protocols actually operating across the Internet be properly specified and
standardized, it is equally important that the operations and management
aspects of the network also be standardized so that products from different
vendors can interoperate, even if said protocols operate entirely within the
confines of private networks.

And insofar as the email community is concerned the "private network stuff
isn't the IETF's business" has a somewhat unpleasant history: This is the main
argument that was used to block standardization work on POP and IMAP for a
considerable period. In hindsight, this argument should have been rejected as
bogus a lot sooner, and had that been done a number of issues might have been
avoided.

> > First of all, there's nothing problematic about parameters to MAIL - we have
> > already defined a bunch of them, ...

> > Second, the notion of using a general announcer is a truly terrible
> > idea. ...

> If you have a flag on MAIL, the MAIL command turns on a global state bit,

Nope. It turns on a transaction-specific information bit, a bit the MTA has to
maintain as part of the message metadata order to fulfill it's obligations
should the message require further relaying. There is no state bit involved and
no need for one.

> the flag has to be remembered through the session through RCPT and DATA.
> If there are other random commands in between such as NOOP or EXPN or
> VRFY, it has to be remembered past them, too.  The bit gets turned off
> sometime between the dot at end of data and the next MAIL command.

Nope. But even even if this were the case, you're focusing on the server and
ignoring the client. It's the client, not the server, where the complexity of
using a global state bit really manifests - in order to implement your approach
the client has to keep track of the state it has put the server in. This is
mostly because servers can be, and often are, written as bunch of state
variables and a simple command loop. Clients, OTOH, tend to manifest as a bunch
of branching code paths that work very differently depending on what extensions
are present and needed. And sure enough, history has shown that client state
maintenance is one of the most common, if not the most common, places where
implementors make mistakes - they miss some client code path and things
desynchonize.

> If you have a flag command, STARTEAI turns the bit on and RSET or EHLO
> turns it off.  I'm having trouble seeing why the first bit is good and the
> second bit is bad.

Wow. I didn't think there was an even worse idea than a STARTEAI/STOPEAI
command set, but you managed to come with it. Your proposal now is to have
commands that can be - and often are - issued at various times during a session
result in a change of state that's totally unrelated to the purpose the command
is typically being issued for. In our client code, for example, there are at
least four places that issue EHLO and well over a dozen that send out a RSET.
All of those would have to be modified to track the EAI state changes.

> There's nothing wrong with a MAIL flag, but flagging EXPN and VRFY seems
> to be a problem due to the loose syntax of those commands that, as far as
> I can tell, would have to retroactively make whatever the flag is into a
> reserved word in those commands.

Then you need to reread my proposed ABNF for adding a parameter. You're
imagining issues that don't exist.

				Ned

From chl@clerew.man.ac.uk  Thu Dec 30 02:33:07 2010
Return-Path: <chl@clerew.man.ac.uk>
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 E591A28C14F for <ima@core3.amsl.com>; Thu, 30 Dec 2010 02:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.725
X-Spam-Level: 
X-Spam-Status: No, score=-3.725 tagged_above=-999 required=5 tests=[AWL=-0.726, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_LOW=-1]
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 UA8+jk11WHTg for <ima@core3.amsl.com>; Thu, 30 Dec 2010 02:33:06 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id 58DA028C0E5 for <ima@ietf.org>; Thu, 30 Dec 2010 02:32:46 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 4D1C0222DC for <ima@ietf.org>; Thu, 30 Dec 2010 10:34:51 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Thu, 30 Dec 2010 10:34:51 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBUAYnZH027223 for <ima@ietf.org>; Thu, 30 Dec 2010 10:34:51 GMT
Date: Thu, 30 Dec 2010 10:34:49 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <2B9258A1B04B6596D4F07D20@[192.168.1.128]> <4D1AEBB6.9030402@it.aoyama.ac.jp>
Content-Transfer-Encoding: 8bit
Message-ID: <op.voivob1v6hl8nm@clerew.man.ac.uk>
In-Reply-To: <4D1AEBB6.9030402@it.aoyama.ac.jp>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d1c604b.b44-311-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 30 Dec 2010 10:33:08 -0000

On Wed, 29 Dec 2010 08:05:10 -0000, Martin J. Dürst  
<duerst@it.aoyama.ac.jp> wrote:

> In the hope to move the debate forward, and after the clarifications by  
> Alex and Ned, but not an email infrastructure insider, my preferences  
> below.

>> Topic: The description of VRFY and EXPN handling in 5336bis is
>> not adequate.  Whatever is done, we will have to change/fix it.
>> In the questions below, I've mentioned VRFY but I assume that
>> EXPN would get exactly the same treatment.

> Anyway, my order of preference would be (1), (3), (2).

+1 (with especial emp[hasis on (1)).

If you add John Levine's STARTEAI command as (4), then my preference would  
be
(1), (3), (4), (2).

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From chl@clerew.man.ac.uk  Thu Dec 30 02:38:54 2010
Return-Path: <chl@clerew.man.ac.uk>
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 7448228C14B for <ima@core3.amsl.com>; Thu, 30 Dec 2010 02:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.893
X-Spam-Level: 
X-Spam-Status: No, score=-3.893 tagged_above=-999 required=5 tests=[AWL=-0.446, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 isarr31UVmmx for <ima@core3.amsl.com>; Thu, 30 Dec 2010 02:38:53 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id 187B528C0E5 for <ima@ietf.org>; Thu, 30 Dec 2010 02:38:40 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 11B51222DF for <ima@ietf.org>; Thu, 30 Dec 2010 10:40:45 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Thu, 30 Dec 2010 10:40:45 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBUAeiag027581 for <ima@ietf.org>; Thu, 30 Dec 2010 10:40:45 GMT
Date: Thu, 30 Dec 2010 10:40:44 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@[192.168.1.128]> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@[192.168.1.128]>
Content-Transfer-Encoding: 8bit
Message-ID: <op.voivx6nm6hl8nm@clerew.man.ac.uk>
In-Reply-To: <E5F8CCE3E3046EA5F0D8D34C@[192.168.1.128]>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d1c61ad.e7f-561-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 30 Dec 2010 10:38:54 -0000

On Wed, 29 Dec 2010 19:30:34 -0000, John C Klensin <klensin@jck.com> wrote:


>> 1.  A 2x2 matrix isn't all that precise.
>
> I'm not objecting to the matrix, only to the terms, even though
> I think we need to be sure that we don't confuse encoding with
> embedding (ASCII in an eight bit field isn't the only problem;
> technically UTF-32 is an embedding of the Unicode code point
> integer space (0 ... 0x10FFFF) in a 32-bit field.  Worse, both
> UTF-16 and UTF-32 have big-endian and little-endian variations.

If you are looking for a term to describe some UTF-8 text that is not also  
an ASCII text, then normal mathematical usage is to use the word "proper".

E.g., a is A is a "proper subset" of B, then A is not identical to B.

So something like "proper-utf8" would follow that concention. You might  
even use "PROPER_UTF8" as that parameter of the MAIL command.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From johnl@taugh.com  Thu Dec 30 05:58:07 2010
Return-Path: <johnl@taugh.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 469163A680C for <ima@core3.amsl.com>; Thu, 30 Dec 2010 05:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.143
X-Spam-Level: 
X-Spam-Status: No, score=-11.143 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.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 tKKdZdQP0Uu2 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 05:58:06 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id CEE003A680E for <ima@ietf.org>; Thu, 30 Dec 2010 05:58:05 -0800 (PST)
Received: (qmail 35494 invoked from network); 30 Dec 2010 14:00:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8aa5.4d1c9067.k1012; i=johnl@submit.iecc.com; bh=0ieqsbbs4hdyKBI2cD+S3nWZ0dy36pFqlwyC6Iud+Iw=; b=INveW3YV88bB73FTLdpRSkKs9/XjtRxhFlvGKPieQQdPqvYHRVhcdrwf0sQhtF+fCa6cfSQDRyYA3N3gMaMsDJdqo/bjZVsR8IiHw8TbzaRF2f1nJRutbO2vWwkbU0p7HTwmOhjU88m+uIKCYzBV/WIf+W6iWznP13pxjye1nnM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8aa5.4d1c9067.k1012; olt=johnl@submit.iecc.com; bh=0ieqsbbs4hdyKBI2cD+S3nWZ0dy36pFqlwyC6Iud+Iw=; b=s9D62rLu0vznGXddeIB0dXcIdkKtlNQ5RMcmxo9N/PmPDc9WNt5f6Cz6xiPb9LPj9h/cfufxMbDcjOXXMOkd5+BTynd12s6Dm3iCxeIl52ZMZhnc/41BdwfVuLIYzpAuOxjESTZcHkT+k15d+xeZXVDjPtIpZQ5L3tiaq5f4uRE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Dec 2010 13:59:45 -0000
Date: 30 Dec 2010 09:00:06 -0500
Message-ID: <alpine.BSF.2.00.1012300859340.1762@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ned Freed" <ned.freed@mrochek.com>
In-Reply-To: <01NW0AVK5L3W007CHU@mauve.mrochek.com>
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan> <01NVZLGRF9E4007CHU@mauve.mrochek.com> <alpine.BSF.2.00.1012291306180.97686@joyce.lan> <01NW0AVK5L3W007CHU@mauve.mrochek.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 30 Dec 2010 13:58:07 -0000

> is typically being issued for. In our client code, for example, there are at
> least four places that issue EHLO and well over a dozen that send out a RSET.
> All of those would have to be modified to track the EAI state changes.

OK, you win.  I hadn't realized your code was so bad.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From dhc2@dcrocker.net  Thu Dec 30 06:25:52 2010
Return-Path: <dhc2@dcrocker.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 3DD3F3A6812 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 06:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 S0nZi-IHdBhs for <ima@core3.amsl.com>; Thu, 30 Dec 2010 06:25:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 04FD53A680E for <ima@ietf.org>; Thu, 30 Dec 2010 06:25:51 -0800 (PST)
Received: from [192.168.1.117] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBUERo7N021947 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ima@ietf.org>; Thu, 30 Dec 2010 06:27:55 -0800
Message-ID: <4D1C96E0.4060607@dcrocker.net>
Date: Thu, 30 Dec 2010 06:27:44 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ima@ietf.org
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]>
In-Reply-To: <68655A9F86D4BE7ED933F8A6@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 30 Dec 2010 06:27:56 -0800 (PST)
Subject: [EAI] Repeating normative text from other specifications
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 30 Dec 2010 14:25:52 -0000

On 12/27/2010 11:39 AM, John C Klensin wrote:
> Claudio Allocchio 2010-12-22 wrote:
>
>> >  The document quite often repeats rules from other
>> >  specifications, AND re-describes these rules. This is
>> >  dangerous (it makes very difficult to keep aligned
>> >  documents, and will lead to different interpretations) and
>> >  not needed.
> The tradeoff, I hope obviously, is with the reader having to
> flip back and forth repeatedly between documents to have any
> hope of understanding the specification accurately.  I'm
> personally sympathetic to your concern, but many WG
> participants disagree.


Folks,

This issue is worth exploring specifically, since it is a touchstone to very 
different approaches in specification style.  It is an issue that occurs 
frequently in discussions about specification writing.  In my experience, 
repeating normative text is a mistake, and sometimes a very bad one.

The simplistic response, to the concern about having to switch back and forth 
between specifications, is that a serious implementer is going to have to do 
that anyhow, unless the new extension specification incorporates ALL of the base 
specification.

It is also likely that having to switch back and forth frequently, between 
specification, could mean that there is a  need for cleaner specification of the 
extension.  Good modularization has clean interfaces.  Clean interfaces do not 
requiring constantly checking back and forth from one side of the interface to 
the other.

That is, the general practice, in writing Internet specifications, is 
modularity.  Think of it as a form of layering violation, when one specification 
repeats normative text from another.

There are a number of dangers in repeating text.  One is that it invites 
divergence.  If the controlling specification is changed, the document repeating 
the text could diverge from the primary standard.  In addition, the 
specification repeating the normative text might misrepresent the original 
specification.

At the least repeated text is taken out of context.  Repeating part of a 
specification invites the reader to be unaware of the context in which that part 
takes place.

The third issue is sloppiness.  Good specification writing is an exercise in 
organization and discipline.  Having to repeat text from another specification 
could indicate a general issue with organization of the new specification.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jyee@ca.afilias.info  Thu Dec 30 07:38:01 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 2087E3A685D for <ima@core3.amsl.com>; Thu, 30 Dec 2010 07:38:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.854
X-Spam-Level: 
X-Spam-Status: No, score=-105.854 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152, 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 YnagLFaPkwYA for <ima@core3.amsl.com>; Thu, 30 Dec 2010 07:38:00 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id 4C0623A6844 for <ima@ietf.org>; Thu, 30 Dec 2010 07:38:00 -0800 (PST)
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: <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com>
Date: Thu, 30 Dec 2010 10:39:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <82115E5B-A387-486C-A46D-70CCA176C4A8@ca.afilias.info>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@192.168.1.128> <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info> <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com>
To: Yangwoo Ko <newcat@icu.ac.kr>
X-Mailer: Apple Mail (2.1082)
X-Authenticated: True
Cc: dcrocker@bbiw.net, ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 30 Dec 2010 15:38:01 -0000

I try to mean non-ascii, and I write an incorrect term.  Sorry for the =
noise.


Joseph

On 2010-12-29, at 9:53 PM, Yangwoo Ko wrote:

> On Thu, Dec 30, 2010 at 7:33 AM, Joseph Yee <jyee@ca.afilias.info> =
wrote:
>> And we still don't know how to represent the set of "Unicode =
excluding ASCII".
>=20
> What is this set for?
>=20
> --=20
> a human known as yangwooko@gmail.com @ gtalk


From ned+ima@mrochek.com  Thu Dec 30 10:19:23 2010
Return-Path: <ned+ima@mrochek.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 67A413A6825 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 10:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 avMnIggdv6JO for <ima@core3.amsl.com>; Thu, 30 Dec 2010 10:19:22 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 864103A67D3 for <ima@ietf.org>; Thu, 30 Dec 2010 10:19:20 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW10XGD32O00GZ16@mauve.mrochek.com> for ima@ietf.org; Thu, 30 Dec 2010 10:21:23 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW1039TZ4000FQHJ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Thu, 30 Dec 2010 10:21:20 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NW10XEJE4200FQHJ@mauve.mrochek.com>
Date: Thu, 30 Dec 2010 10:18:42 -0800 (PST)
In-reply-to: "Your message dated Thu, 30 Dec 2010 06:27:44 -0800" <4D1C96E0.4060607@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@[192.168.1.128]> <4D1C96E0.4060607@dcrocker.net>
To: Dave CROCKER <dhc2@dcrocker.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293730312; bh=FjrrBEeCPuHT6QilVU96lD80NlfqDqF7mhU6VHQW398=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=MGRgHvQvhrd/nz7EQ63rKKDtQ9+9XTemwL9S0T3AG8uAwkYes9HjvAZTs3GgKC/QY yXgS51b9UuypzGSbAG77R9ebvs7zwGf5gRQ7TMZxbYplK9iFJyYiYFxPh/lLQ/Injn aGK9AKthPGMRz2Wcc5ta21YRCOV6g6DZ/VRB886c=
Cc: ima@ietf.org
Subject: Re: [EAI] Repeating normative text from other specifications
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, 30 Dec 2010 18:19:23 -0000

+1 on all points.


				Ned
> Folks,

> This issue is worth exploring specifically, since it is a touchstone to very
> different approaches in specification style.  It is an issue that occurs
> frequently in discussions about specification writing.  In my experience,
> repeating normative text is a mistake, and sometimes a very bad one.

> The simplistic response, to the concern about having to switch back and forth
> between specifications, is that a serious implementer is going to have to do
> that anyhow, unless the new extension specification incorporates ALL of the base
> specification.

> It is also likely that having to switch back and forth frequently, between
> specification, could mean that there is a  need for cleaner specification of the
> extension.  Good modularization has clean interfaces.  Clean interfaces do not
> requiring constantly checking back and forth from one side of the interface to
> the other.

> That is, the general practice, in writing Internet specifications, is
> modularity.  Think of it as a form of layering violation, when one specification
> repeats normative text from another.

> There are a number of dangers in repeating text.  One is that it invites
> divergence.  If the controlling specification is changed, the document repeating
> the text could diverge from the primary standard.  In addition, the
> specification repeating the normative text might misrepresent the original
> specification.

> At the least repeated text is taken out of context.  Repeating part of a
> specification invites the reader to be unaware of the context in which that part
> takes place.

> The third issue is sloppiness.  Good specification writing is an exercise in
> organization and discipline.  Having to repeat text from another specification
> could indicate a general issue with organization of the new specification.

> d/


> --

>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima

From ned+ima@mrochek.com  Thu Dec 30 10:40:43 2010
Return-Path: <ned+ima@mrochek.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 9FF2E3A6800 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 10:40:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  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 i85T6g9F6khB for <ima@core3.amsl.com>; Thu, 30 Dec 2010 10:40:42 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 6965E3A67D3 for <ima@ietf.org>; Thu, 30 Dec 2010 10:40:42 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW11NZLDUO009M4H@mauve.mrochek.com> for ima@ietf.org; Thu, 30 Dec 2010 10:42:46 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW1039TZ4000FQHJ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Thu, 30 Dec 2010 10:42:43 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NW11NY81JE00FQHJ@mauve.mrochek.com>
Date: Thu, 30 Dec 2010 10:22:45 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 17:00:30 +0900" <AANLkTikZ61i3vhOLvkNGjDCVGS2pdZ3JB3wJM00BSpmz@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=utf-8
References: <02EB1F03BAF0ED410F97CDC6@192.168.1.128> <AANLkTikZ61i3vhOLvkNGjDCVGS2pdZ3JB3wJM00BSpmz@mail.gmail.com>
To: Yangwoo Ko <newcat@icu.ac.kr>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293731596; bh=M18m/jSWNCuLqAUP4CpqmAFlN54zGTsRhAdUPaXySEw=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=H5u4kzfD6oGS992HDi7dKg0Zgkfpo9dT+r/7XNHQlJmNBY4fCtUcLJO6UQJlUpE7C qpeMQhQN4+l/80CmrPPLvgisjmFYAF0RgJQ7V+MMLw+h1I2kSZLx18syRPdie10d21 7r0RqDeDtYimqcX0rXYTJ6vzKip0LrPyzw13vx2o=
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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, 30 Dec 2010 18:40:43 -0000

> I prefer an option that looks simplest in a situation where all
> servers are upgraded to be compliant to these new specifications.

Unfortunately, past experience has shown us that considering the end point
without also considering the path to get there is often a prelude to a failure
to deploy.

Believe me, I wish it were otherwise - it would have made MIME cleaner and
simpler, for one thing.

> In that sense, I am negative to adding a parameter to MAIL command to
> handle (hopefully very rare) situations of encoutering an un-upgraded
> server.

This point won't be reached any time soon. In fact given how many email
implementataions are now baked into various infrastructure pieces, it's more
likely we won't get to this point for a very, very, very long time. And that
makes it very important to have a viable transition and coexistence strategy.

> Since most of recent comments received by this WG recommend
> adding the option, I am not strongly against the idea because the
> modification will not significantly affect the current document.

Speaking as an implementor, the presence of this parameter should let us avoid
avoid having to perform deep inspection of messages in almost all cases. And
while we already support deep inspection capabilities for a number of other
reasons, it's sufficiently expensive that we ship with any options depending on
it disabled by default. That would mean that without this parameter anyone
wanting to use EAI will have to explicitly enable it, which definitely isn't
going to help get this deployed.

				Ned

From ned+ima@mrochek.com  Thu Dec 30 11:44:10 2010
Return-Path: <ned+ima@mrochek.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 4EFAB3A6833 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 11:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 Y91Id6oN7BGl for <ima@core3.amsl.com>; Thu, 30 Dec 2010 11:44:09 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 7FBBC3A6830 for <ima@ietf.org>; Thu, 30 Dec 2010 11:44:08 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW13VKGT4G00EXSI@mauve.mrochek.com> for ima@ietf.org; Thu, 30 Dec 2010 11:46:09 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NW1039TZ4000FQHJ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ima@ietf.org; Thu, 30 Dec 2010 11:46:05 -0800 (PST)
From: ned+ima@mrochek.com
Message-id: <01NW13VIQMD800FQHJ@mauve.mrochek.com>
Date: Thu, 30 Dec 2010 10:43:18 -0800 (PST)
In-reply-to: "Your message dated Wed, 29 Dec 2010 13:13:34 -0500" <3593064B56C9F619AD72997C@[192.168.1.128]>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <01NVYK39E5FO007CHU@mauve.mrochek.com> <20101229155923.87606.qmail@joyce.lan> <01NVZLGRF9E4007CHU@mauve.mrochek.com> <3593064B56C9F619AD72997C@[192.168.1.128]>
To: John C Klensin <klensin@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1293735398; bh=qlt4DoGMmSBbpt0X+IopuN/VBQlLPK1uoWwajUt4hYk=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=RLVCpQgcuhcCRCt4h8NJAtzvSgQ5HQTAVKYtrN7n2PuiCK23Ez3nPYh3e3WBerb67 6N8IXzw83kfVAmwBbQAGofzGeXxjNSTwHxhwpVfyOkIj2LPPBhW1BdTGiNpuLwvnTr mpzLpEv17xvPY3uMODDOjDue1YtzMu0klbxcZfmw=
Cc: ima@ietf.org
Subject: Re: [EAI] EAI review topic: VRFY/EXPN
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, 30 Dec 2010 19:44:10 -0000

> --On Wednesday, December 29, 2010 9:32 AM -0800
> ned+ima@mrochek.com wrote:

> >...
> > Second, the notion of using a general announcer is a truly
> > terrible idea. The reason it's a terrible idea is that only
> > some subset of the messages a given MTA handles will be EAI
> > messages. So when you process an EAI message followed by a
> > non-EAI message, you most certainly do not want the non-EAI
> > message to be flagged as EAI. So you need a way to turn that
> > indicator off. There are two ways to do that:
> > Disconnect/reconnect or provide an off-switch. But now you
> > have what amounts to a global state bit that you have to keep
> > track of. And this is a sure-fire recipe for implementation
> > issues and interoperability problems.

> Well, one could also organize things so that RSET would do
> provide the "off" function, rather that requiring (bleech)
> STOPEAI or "STARTEAI STOP".  But that is just a way to
> manipulate the global state and does not make it a less terrible
> idea.

The nice thing about the way RSET works presently is unless your client needs
some fairly wierd command ordering that gets into the odd historical coupling
between RSET and HELO, a RSET maps directly and exclusively to a reset of the
transaction state. So when an implementation wants to reset the transaction
state, it just needs to call its "send command, check status" routine with
"RSET" as the parameter, done - no need for additional state checks or an
additional layer of processing to track any other state variables.

But when you add additional glboal state, you either need to add code to track
that everywhere or introduce an indirection layer. (I"d probably opt for the
latter since it results in cleaner code overall, but it's more work.)

Currently the trickiest aspect of SMTP implementations is client error
handling. I'd like to keep it that way, especially since for the most part
client error handling is a sunk cost.

				Ned

From dcrocker@bbiw.net  Thu Dec 30 16:32:16 2010
Return-Path: <dcrocker@bbiw.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 95B2228C0D0 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 16:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 Xy4OXdhUWmQZ for <ima@core3.amsl.com>; Thu, 30 Dec 2010 16:32:15 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 2A35028B56A for <ima@ietf.org>; Thu, 30 Dec 2010 16:32:15 -0800 (PST)
Received: from [192.168.42.82] (m352736d0.tmodns.net [208.54.39.53]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id oBV0XnCk001807 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 30 Dec 2010 16:33:59 -0800
Message-ID: <4D1D24E8.8020005@bbiw.net>
Date: Thu, 30 Dec 2010 16:33:44 -0800
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joseph Yee <jyee@ca.afilias.info>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@192.168.1.128> <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info> <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com> <82115E5B-A387-486C-A46D-70CCA176C4A8@ca.afilias.info>
In-Reply-To: <82115E5B-A387-486C-A46D-70CCA176C4A8@ca.afilias.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 30 Dec 2010 16:34:00 -0800 (PST)
Cc: ima@ietf.org
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 31 Dec 2010 00:32:17 -0000

On 12/30/2010 7:39 AM, Joseph Yee wrote:
> I try to mean non-ascii, and I write an incorrect term.  Sorry for the noise.


That's ok.  The question remains:  Why is "non-ascii" important?

There is some benefit in separating ASCII from the rest of Unicode, for some of 
the BNF, in order to facilitate adding Unicode on top of the existing ASCII 
definitions.  But beyond that, Unicode is Unicode.  ASCII is part of Unicode and 
the fact that a collection of Unicode happens to also be all ASCII does not make 
it "not" Unicode.

If a message is in legacy form, then it is ASCII (or, rather, ASCII-only).  If 
it is in Unicode form, then it is in Unicode, even if all the characters are 
x07F or below...

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From yangwooko@gmail.com  Thu Dec 30 17:07:04 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 0956E3A68AC for <ima@core3.amsl.com>; Thu, 30 Dec 2010 17:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.863
X-Spam-Level: 
X-Spam-Status: No, score=-2.863 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 Fe190HFkf5n1 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 17:07:02 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id C43193A68AB for <ima@ietf.org>; Thu, 30 Dec 2010 17:07:02 -0800 (PST)
Received: by vws7 with SMTP id 7so4496911vws.31 for <ima@ietf.org>; Thu, 30 Dec 2010 17:09:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=nH4C9rR540QV35vamVkqfQ11iJ3UbS73Ulv+in59k1o=; b=Mzw6HL9HGksm0aMh3MrRN/ODDH7j1koEvsdJumycsyV/X6mgsELC+1ZO3mLTNAFpLR dY7hLMyE3/Az2hhDzGFjUWQmWU6DH5hJEKgtJAQqvt/uXgyrqY6EtwH67bONtQxqExvz th284eV+CbxNXvu+IxDb7as49tNa0r8wPW2WA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=cWJOGNTCOh1zcwp6dSnYvJKZAEvr47EHqqej5sIOJeca07PqPj6eNAn1I7AGcQrQZV o+BY+L2sqW8c/Q0ZgLH+soGhVAHsxVpd+Rk1gzq3LQEvMwjCceG6AVneNUppiyzASH6a cYRDzAET+8E+8CtlyL9JE+XLOFShgI9sgfL8I=
Received: by 10.220.93.81 with SMTP id u17mr4570724vcm.121.1293757747413; Thu, 30 Dec 2010 17:09:07 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Thu, 30 Dec 2010 17:08:47 -0800 (PST)
In-Reply-To: <4D1D24E8.8020005@bbiw.net>
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@192.168.1.128> <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info> <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com> <82115E5B-A387-486C-A46D-70CCA176C4A8@ca.afilias.info> <4D1D24E8.8020005@bbiw.net>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Fri, 31 Dec 2010 10:08:47 +0900
X-Google-Sender-Auth: gYYsn1vVusXP_FombWt7ofSpT88
Message-ID: <AANLkTinnDa4NBYBtr_iWLxNV6F0pt9p4Yfx75GYQnZt=@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 31 Dec 2010 01:07:04 -0000

Thanks Dave. That is exactly what I tried to convey. And that is the
reason why I do not understand the necessity of defining a term for
non-ASCII Unicode characters. There need to be only two kinds, legacy
and more than legacy.

On Fri, Dec 31, 2010 at 9:33 AM, Dave CROCKER <dcrocker@bbiw.net> wrote:
>
>
>
>
> On 12/30/2010 7:39 AM, Joseph Yee wrote:
>>
>> I try to mean non-ascii, and I write an incorrect term. =C2=A0Sorry for =
the
>> noise.
>
>
> That's ok. =C2=A0The question remains: =C2=A0Why is "non-ascii" important=
?
>
> There is some benefit in separating ASCII from the rest of Unicode, for s=
ome
> of the BNF, in order to facilitate adding Unicode on top of the existing
> ASCII definitions. =C2=A0But beyond that, Unicode is Unicode. =C2=A0ASCII=
 is part of
> Unicode and the fact that a collection of Unicode happens to also be all
> ASCII does not make it "not" Unicode.
>
> If a message is in legacy form, then it is ASCII (or, rather, ASCII-only)=
.
> =C2=A0If it is in Unicode form, then it is in Unicode, even if all the ch=
aracters
> are x07F or below...
>
> d/
>
> --
>
> =C2=A0Dave Crocker
> =C2=A0Brandenburg InternetWorking
> =C2=A0bbiw.net
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>



--=20
a human known as yangwooko@gmail.com @ gtalk

From yangwooko@gmail.com  Thu Dec 30 17:16:09 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 CEE1D3A68B0 for <ima@core3.amsl.com>; Thu, 30 Dec 2010 17:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.934
X-Spam-Level: 
X-Spam-Status: No, score=-2.934 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 JUd2xU47gcVO for <ima@core3.amsl.com>; Thu, 30 Dec 2010 17:16:09 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 0A9E43A68AB for <ima@ietf.org>; Thu, 30 Dec 2010 17:16:08 -0800 (PST)
Received: by vws7 with SMTP id 7so4500087vws.31 for <ima@ietf.org>; Thu, 30 Dec 2010 17:18:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=Qr5FTt9ktxweVSFoVWkv4VyRCjpAd4P/Xt67q2Aqkc0=; b=jBho2JQ9iSvQNGioSaLWrtgKMY+GHbjtEeCcsc5lbQ9VwUxko6ip3RcYnQhBbN4ZXk ABVnwWFYxPPs/Z/EyZ6n/vCy5xR2qjOaKrd+9GeZrDRh5mrwxCQJes4+0KKWqAGS14QX cAJlqYPjo4aNGGuwN6OJK8LAAHlDL8qU6Yljg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=dJhsWbN7cxigEhTZMq3kCPLAPqzJwD/T+xrbzDr0bdIlqhvuXBBrE/JRUu+SKN8m5M WP1Uoniy8tTK7hFImw+kJpWHypqmEEmQsB9q7+dqW4/rfEvr26V740LK+YiEYE+J6/VH tugVX4bYUlg7k/bM0ermsmGrTVp30ypTxkfvE=
Received: by 10.220.158.211 with SMTP id g19mr1067807vcx.86.1293758294454; Thu, 30 Dec 2010 17:18:14 -0800 (PST)
MIME-Version: 1.0
Sender: yangwooko@gmail.com
Received: by 10.220.202.134 with HTTP; Thu, 30 Dec 2010 17:17:53 -0800 (PST)
In-Reply-To: <01NW11NY81JE00FQHJ@mauve.mrochek.com>
References: <02EB1F03BAF0ED410F97CDC6@192.168.1.128> <AANLkTikZ61i3vhOLvkNGjDCVGS2pdZ3JB3wJM00BSpmz@mail.gmail.com> <01NW11NY81JE00FQHJ@mauve.mrochek.com>
From: Yangwoo Ko <newcat@icu.ac.kr>
Date: Fri, 31 Dec 2010 10:17:53 +0900
X-Google-Sender-Auth: grSlXOKZWAjXY5k4Ql5zlHip9Gw
Message-ID: <AANLkTimdX1JDCgQyh5wGSx3gbrzK+vbXEvjEVnxrmp22@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [EAI] EAI review topic: Parameter on MAIL command
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, 31 Dec 2010 01:16:09 -0000

On Fri, Dec 31, 2010 at 3:22 AM, Ned Freed <ned.freed@mrochek.com> wrote:
(snip)
> while we already support deep inspection capabilities for a number of other
> reasons, it's sufficiently expensive that we ship with any options depending on
> it disabled by default. That would mean that without this parameter anyone
> wanting to use EAI will have to explicitly enable it, which definitely isn't
> going to help get this deployed.

This point really makes sense to me.


-- 
a human known as yangwooko@gmail.com @ gtalk

From chl@clerew.man.ac.uk  Fri Dec 31 03:43:17 2010
Return-Path: <chl@clerew.man.ac.uk>
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 AA51D28C0F0 for <ima@core3.amsl.com>; Fri, 31 Dec 2010 03:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.861
X-Spam-Level: 
X-Spam-Status: No, score=-3.861 tagged_above=-999 required=5 tests=[AWL=-0.414, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 IqN0PvVyGjar for <ima@core3.amsl.com>; Fri, 31 Dec 2010 03:43:16 -0800 (PST)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by core3.amsl.com (Postfix) with ESMTP id 2DDFD28B23E for <ima@ietf.org>; Fri, 31 Dec 2010 03:43:15 -0800 (PST)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id CE72121FFB for <ima@ietf.org>; Fri, 31 Dec 2010 11:45:20 +0000 (GMT)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Fri, 31 Dec 2010 11:45:20 +0000
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id oBVBjHjh015997 for <ima@ietf.org>; Fri, 31 Dec 2010 11:45:19 GMT
Date: Fri, 31 Dec 2010 11:45:17 -0000
To: IMA <ima@ietf.org>
From: "Charles Lindsey" <chl@clerew.man.ac.uk>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <Pine.OSX.4.64.1012221602490.40683@mac-allocchio3.elettra.trieste.it> <68655A9F86D4BE7ED933F8A6@192.168.1.128> <4D192FF8.1030706@dcrocker.net> <9B48F59821946F2EA2DCDEA0@192.168.1.128> <4D19623F.3040804@dcrocker.net> <61939C011F6BB4A93749804C@192.168.1.128> <AANLkTi==F13UbALApdRFtNfhsDoJOAatmztwhPoAMi8a@mail.gmail.com> <0D625A27294258D00E95152A@192.168.1.128> <4D1AD148.7070000@dcrocker.net> <E5F8CCE3E3046EA5F0D8D34C@192.168.1.128> <2D0309E0-97FD-4303-83DC-3A2296B0A102@ca.afilias.info> <AANLkTikww-TsPuTVt8g9mZSHDWnr_pudZ7i+=+sZvVmY@mail.gmail.com> <82115E5B-A387-486C-A46D-70CCA176C4A8@ca.afilias.info> <4D1D24E8.8020005@bbiw.net>
Content-Transfer-Encoding: 8bit
Message-ID: <op.voktlryn6hl8nm@clerew.man.ac.uk>
In-Reply-To: <4D1D24E8.8020005@bbiw.net>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4d1dc250.13ea8-73f8-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] Unicode vs. UTF-8 / Encoding vs. Representation
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, 31 Dec 2010 11:43:17 -0000

On Fri, 31 Dec 2010 00:33:44 -0000, Dave CROCKER <dcrocker@bbiw.net> wrote:

> There is some benefit in separating ASCII from the rest of Unicode, for  
> some of the BNF, in order to facilitate adding Unicode on top of the  
> existing ASCII definitions.  But beyond that, Unicode is Unicode.  ASCII  
> is part of Unicode and the fact that a collection of Unicode happens to  
> also be all ASCII does not make it "not" Unicode.
>
> If a message is in legacy form, then it is ASCII (or, rather,  
> ASCII-only).  If it is in Unicode form, then it is in Unicode, even if  
> all the characters are x07F or below...

But you often need to recognise, or to talk about, that case, because a  
message in that form can safely be sent to a legacy server (which might be  
the only way to reach its destination).

So we need a nice, simple, uncomplicated and memorable term for that  
situation and for its opposite. I have suggested "ASCII" and  
"proper_utf8", which are disjoint sets.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

From Shawn.Steele@microsoft.com  Fri Dec 31 10:19:58 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 4822D3A6810 for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:19:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.416
X-Spam-Level: 
X-Spam-Status: No, score=-10.416 tagged_above=-999 required=5 tests=[AWL=0.183, 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 U2BzaP0ktIX3 for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:19:57 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id EDCB23A67C2 for <ima@ietf.org>; Fri, 31 Dec 2010 10:19:56 -0800 (PST)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 31 Dec 2010 10:22:03 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0255.003; Fri, 31 Dec 2010 10:22:03 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: non-EAI messages
Thread-Index: AcupFwIsXJjnWsXORPmX0etIreBsgA==
Date: Fri, 31 Dec 2010 18:22:01 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B4B021@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.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] non-EAI messages
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, 31 Dec 2010 18:19:58 -0000

> The reason it's a terrible idea is that only some subset of the messages =
a given MTA handles will be EAI messages.

I'm not sure how this is interesting? =20

If the server thought it was EAI, but it only used the ASCII range, the exa=
ct same thing would (should) happen as if it wasn't an EAI message.

So, IMO, having the client say "I speak EAI too" once it hears UTF8SMTP wou=
ld finish the handshaking.

OTOH: If I'm an EAI aware client, and I get a response from an EAI aware se=
rver that requires UTF-8, I'd really like that to happen, even if my origin=
al message & header were all ASCII.
=20
-Shawn


From Shawn.Steele@microsoft.com  Fri Dec 31 10:30:36 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 D98323A6940 for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.422
X-Spam-Level: 
X-Spam-Status: No, score=-10.422 tagged_above=-999 required=5 tests=[AWL=0.176, 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 snOc9KmQlRoD for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:30:35 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 11D7E3A6874 for <ima@ietf.org>; Fri, 31 Dec 2010 10:30:35 -0800 (PST)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 31 Dec 2010 10:32:41 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.01.0255.003; Fri, 31 Dec 2010 10:32:40 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Random thought on ASCII range
Thread-Index: AcupF+V53djy5w7pS1ilQ7YHTFLyCw==
Date: Fri, 31 Dec 2010 18:32:39 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B4B07B@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.74]
Content-Type: multipart/alternative; boundary="_000_E14011F8737B524BB564B05FF748464A11B4B07BTK5EX14MBXC137r_"
MIME-Version: 1.0
Subject: [EAI] Random thought on ASCII range
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, 31 Dec 2010 18:30:37 -0000

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

UmFuZG9tIHRob3VnaHQ6ICBVbmljb2RlIGNhbGxzIDAwLTdGIOKAnEMwIENvbnRyb2xzIGFuZCBC
YXNpYyBMYXRpbi7igJ0gIEdpdmVuIHRoYXQgdGhlIEMwIENvbnRyb2xzIGFyZSBwcmV0dHkgbXVj
aCBpbGxlZ2FsIGluIGVtYWlsIGFkZHJlc3Nlcywgd2UgY291bGQgc2hvcnRlbiB0aGF0IHRvIOKA
nEJhc2ljIExhdGlu4oCdLCB3aGljaCBpc27igJl0IHRlcnJpYmx5IHdvcmR5LCBhbmQgZXZhZGVz
IHRoZSBxdWVzdGlvbiBvZiB3aGV0aGVyIHdlIG1lYW4gdGhlIEFTQ0lJIHNldCBvZiBjaGFyYWN0
ZXJzIFUrMDAwMC1VKzAwN2Ygb3IgdGhlIGVuY29kaW5nLg0KDQotIFNoYXduDQoNCu+jou+jkO+j
p++jmyDvo6Lvo6Pvo5fvo5Tvo5kNCmh0dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZQ0KKFNl
bGZob3N0IDc5MDMpDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OkNvZGUyMDAwOw0KCXBhbm9zZS0xOjIgMCA2IDAgMCAwIDAgMCAwIDA7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBDb2RlMjAwMCI7DQoJcGFub3NlLTE6MiAwIDYg
MCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxp
Lk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu
cy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlz
aXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERl
ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4w
aW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlJhbmRvbSB0aG91Z2h0OiZuYnNwOyBVbmljb2RlIGNhbGxzIDAw
LTdGIOKAnEMwIENvbnRyb2xzIGFuZCBCYXNpYyBMYXRpbi7igJ0mbmJzcDsgR2l2ZW4gdGhhdCB0
aGUgQzAgQ29udHJvbHMgYXJlIHByZXR0eSBtdWNoIGlsbGVnYWwgaW4gZW1haWwgYWRkcmVzc2Vz
LCB3ZSBjb3VsZCBzaG9ydGVuIHRoYXQgdG8g4oCcQmFzaWMgTGF0aW7igJ0sIHdoaWNoIGlzbuKA
mXQgdGVycmlibHkgd29yZHksIGFuZCBldmFkZXMgdGhlIHF1ZXN0aW9uIG9mIHdoZXRoZXINCiB3
ZSBtZWFuIHRoZSBBU0NJSSBzZXQgb2YgY2hhcmFjdGVycyBVJiM0MzswMDAwLVUmIzQzOzAwN2Yg
b3IgdGhlIGVuY29kaW5nLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6SkEiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkpBIj4tIFNoYXduPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpKQSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iSkEiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OkNvZGUyMDAwO21zby1mYXJlYXN0LWxhbmd1YWdlOkpBIj7v
o6Lvo5Dvo6fvo5sg76Oi76Oj76OX76OU76OZPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OkNvZGUyMDAwIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48YSBocmVmPSJodHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGUi
PjxzcGFuIHN0eWxlPSJjb2xvcjpibHVlIj5odHRwOi8vYmxvZ3MubXNkbi5jb20vc2hhd25zdGU8
L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+KFNlbGZob3N0
IDc5MDMpPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_E14011F8737B524BB564B05FF748464A11B4B07BTK5EX14MBXC137r_--

From Shawn.Steele@microsoft.com  Fri Dec 31 10:37:46 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 A7F753A693F for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.428
X-Spam-Level: 
X-Spam-Status: No, score=-10.428 tagged_above=-999 required=5 tests=[AWL=0.171, 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 z6OW+IahmtNl for <ima@core3.amsl.com>; Fri, 31 Dec 2010 10:37:45 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id AAD473A67AE for <ima@ietf.org>; Fri, 31 Dec 2010 10:37:45 -0800 (PST)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 31 Dec 2010 10:39:52 -0800
Received: from TK5EX14MBXC137.redmond.corp.microsoft.com ([169.254.5.174]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.01.0255.003; Fri, 31 Dec 2010 10:39:51 -0800
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "ima@ietf.org" <ima@ietf.org>
Thread-Topic: Repeating normative text from other specifications
Thread-Index: AcupGZklGQCaL8HMRzOy3yX6rJUtpQ==
Date: Fri, 31 Dec 2010 18:39:51 +0000
Message-ID: <E14011F8737B524BB564B05FF748464A11B4B0A6@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.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] Repeating normative text from other specifications
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, 31 Dec 2010 18:37:46 -0000

> This issue is worth exploring specifically, since it is a touchstone to v=
ery=20
> different approaches in specification style.  It is an issue that occurs=
=20
> frequently in discussions about specification writing.  In my experience,=
=20
> repeating normative text is a mistake, and sometimes a very bad one.

I would also rather only list the differences, and not repeat stuff.  That =
lends to getting out-of-sync.  Also it might make reviewing simpler since i=
f it wasn't there we couldn't mess it up :)  Also we wouldn't have to worry=
 about other extensions that may impact the original RFC, or updates to tha=
t RFC.

-Shawn


From eai@troystarr.net  Fri Dec 31 12:59:55 2010
Return-Path: <eai@troystarr.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 6362A3A681E for <ima@core3.amsl.com>; Fri, 31 Dec 2010 12:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  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 QNPi-HnZI6ib for <ima@core3.amsl.com>; Fri, 31 Dec 2010 12:59:53 -0800 (PST)
Received: from mho-01-ewr.mailhop.org (mho-01-ewr.mailhop.org [204.13.248.71]) by core3.amsl.com (Postfix) with ESMTP id A78D93A6817 for <ima@ietf.org>; Fri, 31 Dec 2010 12:59:53 -0800 (PST)
Received: from user-0c2i81f.cable.earthlink.net ([24.41.32.47] helo=remote.troystarr.net) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <eai@troystarr.net>) id 1PYm6p-000Dc8-2M; Fri, 31 Dec 2010 21:01:59 +0000
Received: from FORGE.foundry.home ([fe80::ad0e:5a01:9a0:c9a8]) by FORGE.foundry.home ([fe80::ad0e:5a01:9a0:c9a8%10]) with mapi; Fri, 31 Dec 2010 13:01:56 -0800
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.41.32.47
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19q2IigGU1DHiPf/YOIzMlo
From: Troy Starr <eai@troystarr.net>
To: 'Shawn Steele' <Shawn.Steele@microsoft.com>, "ima@ietf.org" <ima@ietf.org>
Date: Fri, 31 Dec 2010 13:01:55 -0800
Thread-Topic: [EAI] non-EAI messages
Thread-Index: AcupGh+zgp27APKyRbOjTzRk+iqYrAABCXXg
Message-ID: <C32A1A5CB0814846B91BFAB307442A2B342B1F62A0@FORGE.foundry.home>
References: <E14011F8737B524BB564B05FF748464A11B4B021@TK5EX14MBXC137.redmond.corp.microsoft.com>
In-Reply-To: <E14011F8737B524BB564B05FF748464A11B4B021@TK5EX14MBXC137.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [EAI] non-EAI messages
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, 31 Dec 2010 20:59:55 -0000

Hi Shawn -

> > The reason it's a terrible idea is that only some subset of the message=
s a given MTA handles will be EAI messages.
>=20
> I'm not sure how this is interesting?

Assuming that all of the future MTAs in the message delivery chain support =
UTF8SMTPbis, then I agree, it's not interesting.  But what happens if the p=
revious MUA/MSA/MTA applied a UTF8SMTPbis flag to the entire session rather=
 than on a per-message basis, then the current MTA wants to deliver one of =
those messages to an MTA which doesn't support UTF8SMTPbis?  I see the foll=
owing possibilities:

1. The message envelope and/or headers really does contain UTF-8 characters=
.
   (a) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, bounces the e-mail back to the sender with an N=
DR.
   (b) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, parses the envelope and message headers looking=
 for non-ASCII characters.  It finds at least one non-ASCII character, so i=
t bounces the e-mail back to the sender with an NDR.
   (c) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, parses the envelope and message headers looking=
 for non-ASCII characters.  It has a bug that leads it to believe that ther=
e are no non-ASCII characters, so it assumes that the UTF8SMTPbis flag was =
an ignorable error and attempts to send the message anyway.  At this point,=
 who knows what will happen to the message since we've just violated the RF=
C 5321 SMTP specification.  Perhaps the receiving MTA will catch the violat=
ion and reject the submission.  Perhaps the receiving MTA will attempt to d=
eliver the message, but it will be corrupted.  Perhaps the message will sil=
ently go into a black hole, never to be seen again.  In any event, it is un=
defined, unpredictable, and unreliable.
   (d) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, attempts to send the message anyway.  At this p=
oint, who knows what will happen to the message since we've just violated t=
he RFC 5321 SMTP specification.  Perhaps the receiving MTA will catch the v=
iolation and reject the submission.  Perhaps the receiving MTA will attempt=
 to deliver the message, but it will be corrupted.  Perhaps the message wil=
l silently go into a black hole, never to be seen again.  In any event, it =
is undefined, unpredictable, and unreliable.

2. The message envelope and/or headers only contains ASCII characters.
   (a) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, bounces the e-mail back to the sender with an N=
DR.
   (b) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, parses the envelope and message headers looking=
 for non-ASCII characters.  It doesn't find any, so it assumes that the UTF=
8SMTPbis flag was an ignorable error and sends the message anyway.  The mes=
sage arrives successfully because there are no non-ASCII characters present=
.
   (c) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, parses the envelope and message headers looking=
 for non-ASCII characters.  It has a bug that leads it to believe there are=
 non-ASCII characters, so it bounces the e-mail back to the sender with an =
NDR.
   (d) The MTA, seeing that the MTA it's trying to deliver the message to d=
oesn't support UTF8SMTPbis, attempts to send the message anyway.  The messa=
ge arrives successfully because there are no non-ASCII characters present.

If we were to quickly summarize pros/cons of each, we would get:

(a) Trust UTF8SMTPbis flag, no parsing
Pro: It is predictable and incurs virtually no cost to the MTA.
Con: It will not attempt any "downgrade" to deliver the message which may h=
ave been deliverable if it made an extra effort.

(b) and (c) Ignore UTF8SMTPbis flag, parse
Pro: It makes an extra effort to "downgrade" and deliver the message.
Con: It imposes a message processing cost on the MTA, which may be an imple=
mentation hurdle, and may also be a significant processing cost for high-vo=
lume MTAs.  It may also be unpredictable if the parser is buggy.  Finally, =
it imposes the MTA's judgment of whether the message should be considered a=
 UTF8SMTPbis message over the original sender's judgment.

(d) Ignore UTF8SMTPbis flag
Pro: It might happen to work some of the time.
Con: Is not predictable and will often violate SMTP RFCs.

I think we can agree that (d) is a poor choice and should be rejected as an=
 option.  (a) is the simplest and least costly route since it relies on the=
 first link in the chain to properly flag a UTF8SMTPbis message as such.  I=
f that message does not contain non-ASCII characters, then it's important f=
or the first link in that chain to not flag the message as a UTF8SMTPbis me=
ssage.  (b) and (c) are the tricky ones.  All of the cons I've listed make =
me very cautious about recommending (b) as an option, let alone assuming th=
at it will be the typically implemented behavior.

As such, (a) seems to be the wisest choice IMO.

> OTOH: If I'm an EAI aware client, and I get a response from an EAI aware =
server that requires UTF-8, I'd really like that to happen, even if my orig=
inal message & header were all ASCII.

Maybe I've parsed your sentence poorly, and if so I apologize...  I don't t=
hink there's such a thing as an EAI aware server that notifies the client t=
hat it requires UTF-8 (by which I assume you mean will only accept messages=
 flagged as UTF8SMTPbis).  This RFC allows EAI aware servers to advertise t=
he option to clients to send messages as UTF8SMTPbis messages, but as an op=
tional extension to SMTP, it's still perfectly valid to send a non-UTF8SMTP=
bis message.  I haven't seen any part of the RFC that allows the server to =
advertise to the client that it only accepts messages flagged as UTF8SMTPbi=
s.

In addition, I don't see what advantage you get flagging a pure-ASCII heade=
r message with the UTF8SMTPbis flag.  Indeed, I only see disadvantages for =
the reasons I've stated above.  What are the advantages you see in flagging=
 messages as UTF8SMTPbis even if the envelope and headers are only ASCII?

- Troy Starr
