
From internet-drafts@ietf.org  Wed Aug  1 00:03:46 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A7521F8532; Wed,  1 Aug 2012 00:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level: 
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSu34Km0oqkO; Wed,  1 Aug 2012 00:03:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18CEA21F8534; Wed,  1 Aug 2012 00:03:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120801070345.10978.89847.idtracker@ietfa.amsl.com>
Date: Wed, 01 Aug 2012 00:03:45 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-popimap-downgrade-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 07:03:46 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : Post-delivery Message Downgrading for Internationalized =
Email Messages
	Author(s)       : Kazunori Fujiwara
	Filename        : draft-ietf-eai-popimap-downgrade-07.txt
	Pages           : 21
	Date            : 2012-08-01

Abstract:
   The Email Address Internationalization (SMTPUTF8) extension to SMTP
   allows UTF-8 characters in mail header fields.  Upgraded POP and IMAP
   servers support internationalized Email messages.  If a POP/IMAP
   client does not support Email Address Internationalization, POP/IMAP
   servers cannot deliver Internationalized Email Headers to the client
   and cannot remove the message.  To avoid the situation, this document
   describes a conversion mechanism for internationalized Email messages
   to be in traditional message format.  In the process, message
   elements requiring internationalized treatment are recoded or removed
   and receivers are able to know that they received messages containing
   such elements even if they cannot process the internationalized
   elements.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-popimap-downgrade

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-popimap-downgrade-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-popimap-downgrade-07


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


From internet-drafts@ietf.org  Wed Aug  1 00:20:35 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2EC21F86C2; Wed,  1 Aug 2012 00:20:35 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVVZnQh4oOG9; Wed,  1 Aug 2012 00:20:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298AF21F866D; Wed,  1 Aug 2012 00:20:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120801072035.5227.5523.idtracker@ietfa.amsl.com>
Date: Wed, 01 Aug 2012 00:20:35 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-5738bis-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 07:20:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : IMAP Support for UTF-8
	Author(s)       : Pete Resnick
                          Chris Newman
                          Sean Shen
	Filename        : draft-ietf-eai-5738bis-07.txt
	Pages           : 11
	Date            : 2012-08-01

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-5738bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-5738bis-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-5738bis-07


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


From arnt@gulbrandsen.priv.no  Wed Aug  1 06:24:21 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B7311E84BE for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 06:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level: 
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmnBaBD7qpKI for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 06:24:20 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A8811E8102 for <ima@ietf.org>; Wed,  1 Aug 2012 06:24:20 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 0B123F8D21B; Wed,  1 Aug 2012 13:24:20 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1343827459-8717-8716/10/8; Wed, 1 Aug 2012 13:24:19 +0000
Message-Id: <50192E10.7050506@gulbrandsen.priv.no>
Date: Wed, 1 Aug 2012 15:24:32 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
Mime-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <07C040412CE5237C850BE452@JCK-EEE10> <5016D121.1070500@gulbrandsen.priv.no> <78F457593C1910CCBD98F3C3@JCK-EEE10>
In-Reply-To: <78F457593C1910CCBD98F3C3@JCK-EEE10>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Cc: ima@ietf.org
Subject: Re: [EAI] New documents coming?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 13:24:21 -0000

On 07/30/2012 08:32 PM, John C Klensin wrote:
> Assuming the WG agrees with you that we don't  need a new draft
> before discussion on Thursday, it would be reasonable for you to
> wait until the end of this week or beginning of next to generate
> a new draft.   If you had the energy to prepare a short note
> listing those changes that you consider substantive but
> uncontroversial, that would be helpful.
>
> good luck with the catchup process -- hope you are fully
> recovered at least.

All well, just struggling with the backlog.

The substantive issue was in fact not be from your review, it was the 
older open issue. Since noone has said a word about it I assume people 
don't think it's worth the bother, so I just deleted the issue and will 
keep the response code name and semantics as in the present draft.

I don't think I can manage the wordsmithing necessary for your textual 
issues today. Sorry.

Arnt


From klensin@jck.com  Wed Aug  1 06:43:02 2012
Return-Path: <klensin@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A36A21F8D37 for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 06:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.218
X-Spam-Level: 
X-Spam-Status: No, score=-2.218 tagged_above=-999 required=5 tests=[AWL=0.381,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mlKb-CJiLst7 for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 06:43:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 864CF21F8D36 for <ima@ietf.org>; Wed,  1 Aug 2012 06:43:01 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1SwZ6m-000H2n-5d; Wed, 01 Aug 2012 09:37:04 -0400
Date: Wed, 01 Aug 2012 09:42:59 -0400
From: John C Klensin <klensin@jck.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Message-ID: <7802F6FCD83B9FEF6B01CE3E@JCK-EEE10>
In-Reply-To: <50192E10.7050506@gulbrandsen.priv.no>
References: <07C040412CE5237C850BE452@JCK-EEE10> <5016D121.1070500@gulbrandsen.priv.no> <78F457593C1910CCBD98F3C3@JCK-EEE10> <50192E10.7050506@gulbrandsen.priv.no>
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] New documents coming?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 13:43:02 -0000

--On Wednesday, 01 August, 2012 15:24 +0200 Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:

> The substantive issue was in fact not be from your review, it
> was the older open issue. Since noone has said a word about it
> I assume people don't think it's worth the bother, so I just
> deleted the issue and will keep the response code name and
> semantics as in the present draft.

It might be helpful to mention it to the list, just as a last
check.  But I'll leave that to your discretion unless someone
else feels strongly about it.

> I don't think I can manage the wordsmithing necessary for your
> textual issues today. Sorry.

No problem.  I'd like those changes made before we actually hand
of for IETF Last Call, but I don't expect/intend the WG to spend
f2f time debating editorial trivia or other textual changes.  

Good luck with your backlog.
   john





From jyee@afilias.info  Wed Aug  1 16:51:03 2012
Return-Path: <jyee@afilias.info>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCD321F8986 for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 16:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=-2.624, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_INFO=1.448, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9HDvqR2raiRb for <ima@ietfa.amsl.com>; Wed,  1 Aug 2012 16:51:02 -0700 (PDT)
Received: from outbound.afilias.info (unknown [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8019C21F8982 for <ima@ietf.org>; Wed,  1 Aug 2012 16:51:02 -0700 (PDT)
Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1SwigC-0008LM-54 for ima@ietf.org; Wed, 01 Aug 2012 23:50:16 +0000
Received: from mail-gh0-f171.google.com ([209.85.160.171]) by smtp.afilias.info with esmtp (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1SwigC-0006ZL-4k for ima@ietf.org; Wed, 01 Aug 2012 23:50:16 +0000
Received: by ghy10 with SMTP id 10so7938571ghy.2 for <ima@ietf.org>; Wed, 01 Aug 2012 16:50:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=xG8IIj0htwS8dg/dmBDtzjBeoXYuMKarE8TNzUYUt88=; b=nsGzR+J8qSgnIHIju22W9Gc7oUaqGZ9qH/Z1I1XgrJzWEI7hSa7WjULYW57yAd8ciG A37Tr/IwXJerTS/VOpDqoykxIW4/kXKrLM6F7cr/DCuFU/Fx3ZvcY6phekO8IqZxRU9Y x6H+Z26RXSfNkn1iITm6jinrQsFoUo9i1heOTCr1KEXK/iV4QovHl/aigKF77+rz3K22 JtFa8K2yCmh7qd5LpQOv7kZSY6oSLEQvLvMwtq641TAeIOORejUPQ7p2Su+ORrxsR1A/ rl6oIu4qVau2vJmKuP7AiUMyqemiZZnMLMd/xSFurQNNNBSyt/BwOVX+wESYhD/UqIks fRDQ==
MIME-Version: 1.0
Received: by 10.66.90.67 with SMTP id bu3mr287066pab.26.1343865010476; Wed, 01 Aug 2012 16:50:10 -0700 (PDT)
Received: by 10.67.22.105 with HTTP; Wed, 1 Aug 2012 16:50:10 -0700 (PDT)
Date: Wed, 1 Aug 2012 19:50:10 -0400
Message-ID: <CAF1dMVHKtmSFgZi6e0rB1gcuGMOgOj0B8zPFH5SOT+4pm2MxrA@mail.gmail.com>
From: Joseph Yee <jyee@afilias.info>
To: EAI WG <ima@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQmKCpZJ2stnohd//cvEeuvctbjGUQ0vuTvaat8Mybjt1zkOXvRskipi4TyXHI/xyMDLuNPS
Subject: [EAI] slides and agenda link
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 23:51:03 -0000

All,

Just to inform everyone again where the agenda and slides are for
tomorrow's meeting.

http://tools.ietf.org/wg/eai/agenda

Regards,
Joseph

From fujiwara@jprs.co.jp  Thu Aug  2 10:15:11 2012
Return-Path: <fujiwara@jprs.co.jp>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15DC421F8516 for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:15:11 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2Tp91o7QLrI for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:15:08 -0700 (PDT)
Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 096D621F8644 for <ima@ietf.org>; Thu,  2 Aug 2012 10:15:06 -0700 (PDT)
Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id q72HF5Mk030222 for <ima@ietf.org>; Fri, 3 Aug 2012 02:15:05 +0900
X-AuditID: ac120820-b7fe56d000000cec-b1-501ab599258a
Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 2D.95.03308.995BA105; Fri,  3 Aug 2012 02:15:05 +0900 (JST)
Date: Fri, 03 Aug 2012 02:15:04 +0900 (JST)
Message-Id: <20120803.021504.241429515.fujiwara@jprs.co.jp>
To: ima@ietf.org
From: fujiwara@jprs.co.jp
X-Mailer: Mew version 6.3.50 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Aug__3_02_15_04_2012_590)--"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCIsWRmVeSWpSXmKPExsWyRoiFT3fmVqkAgxffZC2uL13H7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujCO30go29TFVHL+3mq2B8ehOxi5GTg4JAROJTZfvMkHYYhIX 7q1n62Lk4hASOMkosX7iPrAEi4C2xIRHTWA2r4C1xJrWLewgtoiAgMSytwuABnFwCAPVPNjv BxJmE5CU2Py5lRlipp3EiecrWEFKeAUEJf7uEAYJMwuES3Tv28ACYctLbH87h3kCI88shKpZ SKpmIamCsLUkemY8ZidePECisecx8wJGjlWMMvlpabrFqXkpxbnpBoZ6JZX5elkFRcV6ySB6 EyM4SDkUdjDOOGVwiFGAg1GJh3drqWSAEGtiWXFl7iFGSQ4mJVHexg1SAUJ8SfkplRmJxRnx RaU5qcWHGCU4mJVEeKuWAOV4UxIrq1KL8mFS0hwsSuK8x8/u8BMSSE8sSc1OTS1ILYLJynBw KEnw8gKjUUiwKDU9tSItM6cEIc3EwQkynAdo+K8tIMOLCxJzizPTIfKnGLU57j9/cpuR4/b3 F7cZhVjy8vNSpcR5z4GUCoCUZpTmwU17xSgO9JQw71yQLA8wKcHNeQW0gglohZ0Z2IqSRISU VAPjPJG7lpY/ekuFPp/8ee+1uXxnYIvz4+OJVR9/MhxZ/vfg9Iy/K37se/v5UPIrfvd8geg2 wfsXnvHl8DyemujLV/tvrrGS+axPNUerSz0y2x/8P9F7OGh1PQ+XbNCxNr7oZ5KxW/VDfUsj 3iVndVz6prb34lX334cy5PbwawrlfeHf9YHN2rBXiaU4I9FQi7moOBEAJC4wYgcDAAA=
Subject: [EAI] draft-ietf-eai-email-clients-01pre
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:15:11 -0000

----Next_Part(Fri_Aug__3_02_15_04_2012_590)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ernie and I tried to update draft-ietf-eai-email-clients-00 last year.

I attached new version which exist in my machine for 1.5 years.

It tried to describe "Error and re-send model".

Does anyone have an interest for the document ?

If so, I will update it.

Regards,

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

----Next_Part(Fri_Aug__3_02_15_04_2012_590)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-ietf-eai-email-clients-01pre.txt"




Email Address Internationalization                             E. Dainow
(EAI)                                                            Afilias
Internet-Draft                                               K. Fujiwara
Intended status: Informational                                      JPRS
Expires: June 20, 2010                                 December 17, 2009


             Guidelines for Internationalized Email Clients
                    draft-ietf-eai-email-clients-01

Abstract

   This document provides some guidelines for email clients that support
   Email Address Internationalization (EAI) as outlined in
   [I-D.ietf-eai-frmwrk-4952bis].  A number of interoperability cases
   between different versions of email components are reviewed.
   Recommendations are made to improve interoperability and usability
   and to minimize discrepancies between the display of composed and
   received email in different language environments.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 20, 2010.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.




Dainow & Fujiwara         Expires June 20, 2010                 [Page 1]

Internet-Draft                Email Clients                December 2009


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the BSD License.

Table of Contents

   1.  Conventions used in this document  . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Interoperability . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Interoperability Scenarios . . . . . . . . . . . . . . . .  5
   5.  Compatibility Support  . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Address Book . . . . . . . . . . . . . . . . . . . . . . .  7
     5.2.  Message Mode . . . . . . . . . . . . . . . . . . . . . . .  7
     5.3.  Message Format . . . . . . . . . . . . . . . . . . . . . .  8
     5.4.  Error Handling . . . . . . . . . . . . . . . . . . . . . .  8
     5.5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . .  9
     5.6.  Limitations  . . . . . . . . . . . . . . . . . . . . . . . 11
   6.  Mailbox Integration  . . . . . . . . . . . . . . . . . . . . . 12
   7.  Character Encoding . . . . . . . . . . . . . . . . . . . . . . 12
   8.  Normalization  . . . . . . . . . . . . . . . . . . . . . . . . 13
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 14
     12.2. Infomative References  . . . . . . . . . . . . . . . . . . 16


















Dainow & Fujiwara         Expires June 20, 2010                 [Page 2]

Internet-Draft                Email Clients                December 2009


1.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   [I-D.ietf-eai-frmwrk-4952bis] Overview and Framework for
   Internationalized Email describes changes to electronic mail (email)
   to fully support internationalized characters.  The fundamental
   change is to remove the ASCII only restriction on email addresses and
   allow them to contain UTF-8 characters.  Additional documents provide
   detailed specifications for the extensions required to email headers
   [I-D.ietf-eai-rfc5335bis] and to the protocols SMTP
   [I-D.ietf-eai-rfc5336bis], POP [I-D.ietf-eai-rfc5721bis] and IMAP
   [I-D.ietf-eai-5378bis].

   This document provides guidelines for email clients that support
   these specifications for Email Address Internationalization (EAI).
   It does not introduce any protocol extensions that are not defined in
   the above documents.  It highlights the extensions that are important
   to the design and implementation of email clients and makes a number
   of recommendations intended to improve interoperability and
   usability.

3.  Terminology

   A number of different acronyms are typically used to describe the
   major functional components of email.

   Mail User Agent (MUA)
   Message Submission Agent (MSA)
   Message Transfer Agent (MTA)
   Message Delivery Agent (MDA)
   Message Store (MS)

   The architecture of modern email systems can range from simple, with
   all components running on one server, to very complex, with
   components being distributed across multiple, geographically
   dispersed machines.  Nevertheless, the above terminology is generally
   sufficient to represent different architectures from a functional
   point of view.  For a comprehensive description of email architecture
   see [RFC5598].


   sender -> MUA -> MSA -> MTA
                           ...



Dainow & Fujiwara         Expires June 20, 2010                 [Page 3]

Internet-Draft                Email Clients                December 2009


                           MTA -> MDA -> MS -> PIF -> MUA -> recipient


   In this context, an "Email Client" is an MUA that has an interface to
   an MSA to send email and an interface to the MS to retrieve email.
   The interface to retrieve mail (PIF) is a POP or IMAP server or
   direct access to the File system.  The MUA also provides a User
   Interface (UI) that allows an end user to read (display) and write
   (compose) their email.

   A common email architecture includes the MSA function within the MTA.
   An improved architecture that better addresses security concerns is a
   separate MSA component as shown here [RFC4409], [RFC5068].

   "UTF8SMTP" is used to indicate email address internationalization as
   specified by [I-D.ietf-eai-frmwrk-4952bis] and related documents.

   "ASCII" refers to the strict 7-bit ASCII character set
   [ANSI.X3-4.1968].

   "UTF-8", Unicode Transformation Format/8-bit is a character encoding
   scheme that can represent any character in the Unicode standard
   [RFC3629].  It contains ASCII as a subset.

   "message/global" is an email message that contains UTF-8 characters
   beyond 7-bit ASCII in message headers and/or body parts
   [I-D.ietf-eai-rfc5335bis].

   "message/rfc822" is an email message that contains only 7 bit ASCII
   and does not use any UTF8SMTP extensions.  Note that the original
   message (as composed by the user) may contain non-ASCII characters
   that have been encoded into ASCII using IDNA [RFC3490], MIME body
   encoding [RFC2045] or MIME header encoding [RFC2047].

4.  Interoperability

   Internationalized Email is not compatible with legacy email systems,
   those based on prior Internet email standards [RFC5321], [RFC5322].
   Non-ASCII email addresses cannot be submitted in SMTP commands like
   MAIL FROM or RCPT TO.  In addition the Internationalized Email
   standard does not include a method to "downgrade" message/global to
   message/rfc822.

   An Internationalized message cannot be transmitted via SMTP if the
   receiving MTA does not announce UTF8SMTPbis in response to EHLO.
   There are two failure cases that an email client may have to handle
   [RFC5336bis, section 3.2].




Dainow & Fujiwara         Expires June 20, 2010                 [Page 4]

Internet-Draft                Email Clients                December 2009


   a) If the client is submitting a message to an MSA that does not
   support UTF8SMTPbis, the message will be rejected.

   b) If the MSA does support UTF8SMTPbis but a downstream MTA does not,
   then the mail will bounce.  That is, a delivery status notification
   (DSN) that the mail could not be delivered will be sent back to the
   sender.

   Incompatibility between Internationalized email and legacy systems is
   expected to be important initially during a transition period but
   less important over time as more email systems upgrade to support the
   UTF8SMTP extensions.  To the extent that this incompatibility is
   deemed important at the time an implementation is undertaken, the
   email client should provide methods to prevent or at least minimize
   these failures.

4.1.  Interoperability Scenarios

   The following scenarios cover the different cases of sending mail
   from an Internationalized server to a legacy server.

   'I' indicates an Internationalized address (a non-ASCII address on an
   Internationalized mail server).

   'IA' indicates an ASCII address on an Internationalized server.

   'LA' indicates an address on a Legacy mail server, which must be
   ASCII.

   Case 1.  The simple compatibility case

   From:    IA1 (or LA1)
   To:      LA2
   Subject: ...
   Body     ...

   The message will be successfully sent as long as the email client
   sends message/rfc822 rather than message/global.

   Case 2.  The simple incompatibility case

   From:    I1
   To:      LA2
   Subject: ...
   Body     ...

   The message will be rejected by the MSA or will bounce from a
   downstream SMTP server.



Dainow & Fujiwara         Expires June 20, 2010                 [Page 5]

Internet-Draft                Email Clients                December 2009


   If user I1 also has an ASCII email address IA1 or LA1, there may be a
   simple workaround.  If the email client supports multiple email
   accounts, the user just has to switch the From address to an ASCII
   address and it becomes Case 1.

   Case 3.  The general incompatibility cases

   The general case is a mix of Internationalized and legacy addresses.
   While many combinations are possible, the two cases below essentially
   cover all possibilities.

   From: I1
   To:   LA2
   Cc:   I3

   The message will be sent to I3 but it will bounce from LA2.

   Switching the From address to an ASCII address as in Case 2 is not a
   solution, as the following case demonstrates.

   From: IA1 (or LA1)
   To:   LA2
   Cc:   I3

   This message will bounce from LA2 since the address in the Cc header
   cannot be transmitted to a legacy server.

   In these cases, users will likely send the message twice in order to
   reach all intended recipients.  First, to the original list and then
   using an ASCII address to the bounced recipients.

   If users know beforehand which addresses are on legacy servers, they
   can avoid bounced messages by removing those addresses, but they
   still have to send a second email to reach recipients that were
   removed.

5.  Compatibility Support

   An email client can provide support to minimize the incompatibility
   problems outlined in section 4.  There may be several ways to do
   this.  Following are guidelines on some of the ways that this can be
   accomplished.

   At the very least, to provide basic compatibility between
   Internationalized and legacy systems, if all email addresses in the
   SMTP envelope and the message headers are ASCII, then a message/
   rfc822 should be sent (Case 1 above).




Dainow & Fujiwara         Expires June 20, 2010                 [Page 6]

Internet-Draft                Email Clients                December 2009


   For Case 2, the email client should support multiple email accounts
   and allow the user to switch the From address at any time during
   composition of the message.

   For Case 3, several mechanisms may be required to provide
   compatibility support.  These are outlined in the following sub
   sections.

5.1.  Address Book

   Each contact in the address book should be able to have several email
   addresses, each of which is configured to be either an
   Internationalized or a Legacy address.

   The user may not necessarily know if an ASCII address they enter in
   their address book is on a legacy server or not.  If it is configured
   as an Internationalized address and that turns out to be wrong, then
   email sent to that contact may bounce.  The user can then re-
   configure the address as Legacy so the email client can provide
   warnings of a possible bounce on subsequent messages.

5.2.  Message Mode

   Message composition should have an option to use "Internationalized
   Mode" or "Legacy Mode".

   If the type of each address in the headers does not conform to the
   message mode, then the user is given a warning about those addresses
   that don't match the mode.  In a graphical user interface this might
   be done by setting such addresses to a different color such as red.

   The user would typically first change the message mode to see if the
   warnings disappear.

   When the mode is switched, the email client switches addresses in
   message header fields to match the mode, selecting from the list of
   addresses in each contact.

   There are cases where both modes provide warnings (see Example 5
   below).  In these cases, the user can remove the addresses that don't
   conform to the mode.

   For Internationalized mode, the user has an additional option to send
   the message anyway, without removing flagged addresses.  They would
   have to handle bounced messages from Legacy servers later.  The
   option to send anyway cannot be provided in Legacy mode, as it is not
   possible to compose a message/rfc822 if any sender or recipient
   address is not ASCII.



Dainow & Fujiwara         Expires June 20, 2010                 [Page 7]

Internet-Draft                Email Clients                December 2009


   Where both modes provide warnings, users will likely want to send the
   message in each mode in order to reach all recipients.  The email
   client should make it easy to do this.  There are many possible
   designs to accomplish this.  The following is one example.

   An option is provided when composing email to add a second message
   header section in the other mode that allows the user to move
   addresses between sections.  This is in addition to making individual
   changes to address headers as in normal email composition.  The
   Subject and Body are common so the user can compose a single message
   but have it sent in the two different modes to different recipients.

   Following is an example of this for Case 3 above.

   ---------------------------------------------
   Legacy                   Internationalized
   From: IA1                From: I1
   To:   LA2       <--->    To:
   Cc:             <--->    Cc:   I3
   ---------------------------------------------
   Subject: ...
   Body:    ...
   ---------------------------------------------

5.3.  Message Format

   In Internationalized Mode, mail should be sent as message/global.
   The aim of Internationalized Email is 8 bit clean messages using
   UTF-8 encoding to represent Unicode characters in header fields and
   the message body.

   In Legacy Mode, mail must be sent as message/rfc822.  This may
   include non-ASCII characters that are encoded into ASCII using MIME
   body encoding [RFC2045] or MIME header encoding [RFC2047].  Any
   encoding should be based on UTF-8.  In the interest of
   interoperability, charsets other than UTF-8 are prohibited in mail
   addresses and message headers [RFC4952bis, section 7.1].

5.4.  Error Handling

   If a message is rejected by the MSA with a response code that
   indicates incompatibility with legacy email [RFC5336bis, section
   3.4], the compose window should be kept open so that the user can
   make changes and retry.  The email client should provide guidance to
   the user about switching the Message Mode, reconfiguring the type of
   an address in the address book or adding an ASCII legacy address for
   a contact in the address book.




Dainow & Fujiwara         Expires June 20, 2010                 [Page 8]

Internet-Draft                Email Clients                December 2009


   Similarly, if a message bounces, the email client could parse the
   delivery status notifications and message disposition notifications
   [RFC5337bis-dsn] to determine if the failure was a compatibility
   problem and if so, which addresses caused the problem.

5.5.  Examples

   The following examples illustrate most of the different possible
   cases.

   Suppose the user (Sender) has set up the following email account
   containing two email addresses, an Internationalized address and an
   ASCII address on an Internationalized server.

   Sender: I0, IA0

   Examples are not provided for the following cases:

   a) Sender: I0, LA0

   If the Sender has both Internationalized and Legacy addresses, then
   this is equivalent to the above.

   b) Sender: I0

   If the Sender has only Internationalized addresses, then it cannot
   send Legacy messages.  The email client cannot provide an option to
   switch the Message Mode to Legacy.

   c) Sender: LA0

   If the Sender has only accounts on Legacy servers, then it cannot
   send Internationalized messages.  The email client cannot provide an
   option to switch the Message Mode to Internationalized.

   The address book has the following contacts with email addresses.

   Contact1: I1, IA1
   Contact2: I2
   Contact3: IA3
   Contact4: LA4

   Example 1:

   From: Sender
   To:   Contact1
   CC:   Contact2




Dainow & Fujiwara         Expires June 20, 2010                 [Page 9]

Internet-Draft                Email Clients                December 2009


   This message can be sent in Internationalized mode.

   In Legacy mode the email client would flag Contact2, who does not
   have an ASCII address.

   Example 2:

   From: Sender
   To:   Contact1
   CC:   Contact3

   This message can be sent in either Internationalized or Legacy mode.

   Example 3:

   From: Sender
   To:   Contact1
   CC:   Contact4

   This message cannot be sent in Internationalized mode.  Contact4
   would be flagged since it is not on an Internationalized server.

   This message can be sent in Legacy mode.

   Example 4:

   From: Sender
   To:   Contact2
   CC:   Contact3

   This message can be sent in either Internationalized mode or Legacy
   mode.

   Example 5:

   From: Sender
   To:   Contact2
   CC:   Contact4

   This message cannot be sent in either mode.

   Internationalized mode would flag Contact4 which is on a Legacy
   server.  The user can remove Contact4 or use the send anyway option.

   Legacy mode would flag Contact2 who does not have an ASCII address.
   The user would have to remove Contact2 in order to send this message.





Dainow & Fujiwara         Expires June 20, 2010                [Page 10]

Internet-Draft                Email Clients                December 2009


5.6.  Limitations

   In summary, the guidelines outlines in Sections 5 and 6 will provide
   the following compatibility solutions:

   1.  When there is an ASCII address for all contacts in the message,
   then a single legacy compatible message can be sent to all
   recipients.

   2.  When some contacts in the message do not have an ASCII address
   and some have only ASCII addresses on legacy servers, then the
   message can be split into two.  One message is sent as an
   Internationalized message to recipients on Internationalized servers.
   The other is sent as a legacy compatible message to recipients on
   legacy servers.

   These guidelines have a number of limitations.

   a) Unknown Address Types

   Message Mode is effective only if users are fairly disciplined about
   keeping addresses in their address book and configuring the type
   correctly as Internationalized or Legacy.

   When replying to an email, the message may have addresses that are
   not in the address book.  The user may also enter addresses directly
   during message composition that are not in the address book.

   The email client may determine by inspection that some addresses are
   Internationalized.  If an address contains any non-ASCII character,
   then it must be Internationalized.  However, an ASCII address may be
   on either an Internationalized server or a Legacy server and there is
   no way software can determine this automatically.

   In such cases, it may be useful for the email client to flag unknown
   address types in a message so that the user is not lead to believe
   that the message will not bounce just because there were no
   incompatibility warnings.

   b) Address Removal

   When email addresses are removed from a message to meet compatibility
   requirements, recipients do not see everyone who was intended to be
   part of the conversation.  The email client can provide the address
   of removed recipients by using an empty group.  This technique is
   described in [draft-ietf-eai-popimap-downgrade, section 4.1.7].

   This is not an ideal solution, since replies to the message will not



Dainow & Fujiwara         Expires June 20, 2010                [Page 11]

Internet-Draft                Email Clients                December 2009


   reach everyone intended.  But at least it provides the necessary
   contact information to recipients who may be able to use other
   methods to reply to all intended.

6.  Mailbox Integration

   If more than one email address is used for the sender, then mail may
   arrive at different email accounts.  There are several ways to
   provide mailbox integration so the user is able to view all mail in
   one location, such as a single 'Inbox' folder.

   If integration is done on the server, through the use of aliases,
   then the email client does not need to do anything.  All mail will be
   received at the client from one address.

   The email client should provide mailbox integration for cases where
   server side integration is not available and for more flexibility on
   the part of the user.  Many email clients already provide a
   convenient way to manage multiple email accounts.

   An option to view all mail from a group of accounts in one integrated
   folder should also be provided.

7.  Character Encoding

   Email message bodies may be composed and displayed using many
   different character encoding schemes.  Numerous character encodings
   have been developed over time in order to best represent different
   language scripts.  In recent years there has been a trend to prefer
   Unicode as a "universal" character set and UTF-8 as the preferred
   encoding method.

   A good general principle to follow is to minimize character
   conversions.  This will reduce the chance that the received message
   is displayed differently from how it was composed.  Displaying
   received mail SHOULD use the character encoding of the received mail.

   Since older MUAs may not be able to parse UTF-8, the MUA SHOULD try
   to reply to mail using the character encoding of the received mail.
   This may not be possible if the sender adds new characters that
   cannot be encoded in the original encoding.  For example, if the
   received message is encoded in ISO-2022-JP and characters in ISO-
   8859-1 are added to the message, the text cannot be carried in ISO-
   2022-JP and conversion to UTF-8 may be the best solution.

   For new mail, A UTF8SMTP compliant MUA SHOULD use UTF-8 as the
   default encoding if the message type is global or if the envelope
   contains non-ASCII addresses.  If email clients utilize this default,



Dainow & Fujiwara         Expires June 20, 2010                [Page 12]

Internet-Draft                Email Clients                December 2009


   character conversions will be minimized and there will be less chance
   that someone will receive mail in an unrecognized encoding.

   If the message type is rfc822, other considerations may apply, such
   as using the system locale/language.

   Notwithstanding the above, there may be cases where the default does
   not work well.  There SHOULD be options for the user to reset the
   default character encoding.  There SHOULD also be options to change
   the encoding when reading or writing individual email messages.

8.  Normalization

   Different sequences of UTF-8 characters may represent the same thing.
   Normalization is a process that converts all canonically equivalent
   sequences to a single unique form.

   For example, in the Japanese environment, special consideration is
   needed for the "@" symbol used to separate the local name from the
   domain name in email addresses.  Normalization is necessary to
   replace FULLWIDTH COMMERCIAL AT (U+FF20) with ASCII "@", COMMERCIAL
   AT (U+0040) for proper parsing of email addresses.

   Normalization of email headers is specified in
   [I-D.ietf-eai-rfc5335bis]-Section 4.1.  The MUA SHOULD normalize all
   email addresses in the envelope and message headers.

   If the MUA saves email addresses (such as in an address book), they
   SHOULD be stored in normalized form.  For example, an email address
   entered as

   user@host*domain

   where * represents IDEOGRAPHIC FULL STOP (U+3002), as used in some
   Asian languages, would display as

   user@host.domain

   For message bodies that contain UTF-8 characters (message/global),
   the "Net-Unicode" standardized text transmission format specified in
   [RFC5198] SHOULD be followed.  It covers both normalization and
   control characters that may affect display of text.

9.  Security Considerations

   This document does not introduce any security considerations beyond
   those already covered by the normative references for Email Address
   Internationalization (EAI).



Dainow & Fujiwara         Expires June 20, 2010                [Page 13]

Internet-Draft                Email Clients                December 2009


10.  IANA Considerations

   IANA changes are covered by the normative references for Email
   Address Internationalization (EAI).

11.  Acknowledgments

12.  References

12.1.  Normative References

   [ANSI.X3-4.1968]               American National Standards Institute,
                                  "USA Code for Information
                                  Interchange", ANSI X3.4, 1968.

   [I-D.ietf-eai-5378bis]         Resnick, P., Newman, C., and S. Shen,
                                  "IMAP Support for UTF-8",
                                  draft-ietf-eai-5378bis-00 (work in
                                  progress), November 2010.

   [I-D.ietf-eai-frmwrk-4952bis]  Klensin, J. and Y. Ko, "Overview and
                                  Framework for Internationalized
                                  Email",
                                  draft-ietf-eai-frmwrk-4952bis-10 (work
                                  in progress), September 2010.

   [I-D.ietf-eai-rfc5335bis]      Yang, A. and S. Steele,
                                  "Internationalized Email Headers",
                                  draft-ietf-eai-rfc5335bis-07 (work in
                                  progress), December 2010.

   [I-D.ietf-eai-rfc5336bis]      Yao, J. and W. MAO, "SMTP Extension
                                  for Internationalized Email Address",
                                  draft-ietf-eai-rfc5336bis-07 (work in
                                  progress), December 2010.

   [I-D.ietf-eai-rfc5721bis]      Gellens, R., Newman, C., Yao, J., and
                                  K. Fujiwara, "POP3 Support for UTF-8",
                                  draft-ietf-eai-rfc5721bis-00 (work in
                                  progress), September 2010.

   [RFC1652]                      Klensin, J., Freed, N., Rose, M.,
                                  Stefferud, E., and D. Crocker, "SMTP
                                  Service Extension for 8bit-
                                  MIMEtransport", RFC 1652, July 1994.

   [RFC2045]                      Freed, N. and N. Borenstein,
                                  "Multipurpose Internet Mail Extensions



Dainow & Fujiwara         Expires June 20, 2010                [Page 14]

Internet-Draft                Email Clients                December 2009


                                  (MIME) Part One: Format of Internet
                                  Message Bodies", RFC 2045,
                                  November 1996.

   [RFC2047]                      Moore, K., "MIME (Multipurpose
                                  Internet Mail Extensions) Part Three:
                                  Message Header Extensions for Non-
                                  ASCII Text", RFC 2047, November 1996.

   [RFC2119]                      Bradner, S., "Key words for use in
                                  RFCs to Indicate Requirement Levels",
                                  BCP 14, RFC 2119, March 1997.

   [RFC2231]                      Freed, N. and K. Moore, "MIME
                                  Parameter Value and Encoded Word
                                  Extensions: Character Sets, Languages,
                                   and Continuations", RFC 2231,
                                  November 1997.

   [RFC3490]                      Faltstrom, P., Hoffman, P., and A.
                                  Costello, "Internationalizing Domain
                                  Names in Applications (IDNA)",
                                  RFC 3490, March 2003.

   [RFC3629]                      Yergeau, F., "UTF-8, a transformation
                                  format of ISO 10646", STD 63,
                                  RFC 3629, November 2003.

   [RFC4409]                      Gellens, R. and J. Klensin, "Message
                                  Submission for Mail", RFC 4409,
                                  April 2006.

   [RFC5068]                      Hutzler, C., Crocker, D., Resnick, P.,
                                  Allman, E., and T. Finch, "Email
                                  Submission Operations: Access and
                                  Accountability Requirements", BCP 134,
                                  RFC 5068, November 2007.

   [RFC5198]                      Klensin, J. and M. Padlipsky, "Unicode
                                  Format for Network Interchange",
                                  RFC 5198, March 2008.

   [RFC5322]                      Resnick, P., Ed., "Internet Message
                                  Format", RFC 5322, October 2008.

   [RFC5598]                      Crocker, D., "Internet Mail
                                  Architecture", RFC 5598, July 2009.




Dainow & Fujiwara         Expires June 20, 2010                [Page 15]

Internet-Draft                Email Clients                December 2009


12.2.  Infomative References

   [RFC5504]                      Fujiwara, K. and Y. Yoneya,
                                  "Downgrading Mechanism for Email
                                  Address Internationalization",
                                  RFC 5504, March 2009.

   [RFC5825]                      Fujiwara, K. and B. Leiba, "Displaying
                                  Downgraded Messages for Email Address
                                  Internationalization", RFC 5825,
                                  April 2010.

Authors' Addresses

   Ernie Dainow
   Afilias Canada
   4141 Yonge Street
   Toronto, Ontario  M2P 2A8
   Canada

   Phone:
   EMail: edainow@afilias.info


   Kazunori Fujiwara
   Japan Registry Services Co., Ltd.
   Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda
   Chiyoda-ku, Tokyo  101-0065
   Japan

   Phone: +81 3 5215 8451
   EMail: fujiwara@jprs.co.jp



















Dainow & Fujiwara         Expires June 20, 2010                [Page 16]


----Next_Part(Fri_Aug__3_02_15_04_2012_590)----

From johnl@iecc.com  Thu Aug  2 10:21:41 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 707A311E817D for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.124
X-Spam-Level: 
X-Spam-Status: No, score=-111.124 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SA+M4DM4jwZs for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:21:40 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBBA11E817C for <ima@ietf.org>; Thu,  2 Aug 2012 10:21:40 -0700 (PDT)
Received: (qmail 35322 invoked from network); 2 Aug 2012 17:21:39 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Aug 2012 17:21:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding:vbr-info; s=501ab723.xn--30v786c.k1208; i=johnl@user.iecc.com; bh=5wsR3fEt4rd4XcaspMIBxIPvjBoBsaYqFGtYSJ9LK/c=; b=A1m61FTn66/9rOHuS3FJeQ2qD2aOH2JT/j+FqmFrcxjKj2j3c6ppQk9E3AOQodbg4w4rCpX8Ce+u5wy4IqOksqvUum6d2sdBpAdvvWQ8XBeqjfU4+2ENZiTrPAcBBVGrN5edx4lX3KpLHNxCuZb/xIecaycAEQk15NXR794Eocc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding:vbr-info; s=501ab723.xn--30v786c.k1208; olt=johnl@user.iecc.com; bh=5wsR3fEt4rd4XcaspMIBxIPvjBoBsaYqFGtYSJ9LK/c=; b=uYAB3qs6saE4XP+kYcJHTaUzN7o7m//XDernoyuCH5mte7QYNmNAJL88UD2cbD7awUUS0OCsEPieuGd/3lur8bBKrK3xQd8sZyioOhzRp7FHC5icUghdSXK2YaU3bvLeYaXWiLtmxz/RwkvlfL6zvKlWLcXkdoVgqnJO4xH1QLw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Aug 2012 17:21:16 -0000
Message-ID: <20120802172116.64387.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ima@ietf.org
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: [EAI] What some MUAs did with a message with an empty From group
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:21:41 -0000

Executive summary: nothing broke.

* Alpine (my normal client)

Displayed OK.  Invented a matching Reply-To: line.  If I reply, the To: line is empty.

* Thunderbird

Displayed OK. Reply put the same empty From: group on the To: line, rejects attempts to
send it with a message saying to fix the To: line.

* Evolution

Displayed OK. Reply has a blank To: line.

* Android mail

Displayed OK. Reply has a blank To: line.

* Squirrelmail (popular webmail IMAP client)

Displayed OK, reply put the null group on the To: line and let you try
to send mail to it.

* Yahoo Mail

Filed as spam but displayed reasonably.  Reply had an empty To: line.

* Gmail

Filed as spam but displayed reasonably.  Reply had an empty To: line.

* Hotmail aka outlook.com

Displayed OK. Reply put the same empty From: group on the To: line, rejects attempts to
send it with a message saying to fix the To: line.

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

Here's the messge.

Date: Thu, 2 Aug 2012 09:24:15
From: A foreign person:  ;
To: john.levine@gmail.com
Cc: johnl@taugh.com
Subject: let's have lunch

at the sushi place at 1230

Regards,


From barryleiba.mailing.lists@gmail.com  Thu Aug  2 10:35:21 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE4011E8186 for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMdmyDIbSu+W for <ima@ietfa.amsl.com>; Thu,  2 Aug 2012 10:35:20 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2533911E80D1 for <ima@ietf.org>; Thu,  2 Aug 2012 10:35:19 -0700 (PDT)
Received: by lahm15 with SMTP id m15so12475lah.31 for <ima@ietf.org>; Thu, 02 Aug 2012 10:35:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ds2IkrGilN8hRMlU29G4/fEXejNC+DNTn5WI8Dkb2xM=; b=ESXdAKAbfz/hNiVln78WGslIVH6uCHam5FjDdbv/nYfje/AEtLJcLUQHtM3liUenCZ M/mGlEZ6+MwIrD5If7q0j2BrynIU5SVFruvCkyqJh8g+M9xq2ERHbrNdGZY8xmECHAEs SGZLbu2Kfu/cg+rzisE1L7hpbUR4nMcwSi2z5WlTZNDEUUawoR5Qsjqf9/paMQs+a5I7 lCfi3rURCb6U5acKtpeZbykWqzQLl15wr+w+JH388Vmg51lz44QsJj1zw+vwp5bjqOHm 9zdcDmfEAWBPaaTxiTz/oAn73arrfE0rzsvIGKiRF5t9ezemtBt9C3Aef1o71RDNn3Lj 1BVw==
MIME-Version: 1.0
Received: by 10.152.111.200 with SMTP id ik8mr22204226lab.15.1343928919070; Thu, 02 Aug 2012 10:35:19 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Thu, 2 Aug 2012 10:35:18 -0700 (PDT)
In-Reply-To: <20120802172116.64387.qmail@joyce.lan>
References: <20120802172116.64387.qmail@joyce.lan>
Date: Thu, 2 Aug 2012 13:35:18 -0400
X-Google-Sender-Auth: Mm4fQluMTYNq2lnLbuYCGkhGdao
Message-ID: <CAC4RtVAu0JYhiSQc9R==hnUeb+dOvCmzFBg5UUQmMv-a_uvNUA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=f46d04089131d3159404c64bd58e
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] What some MUAs did with a message with an empty From group
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 17:35:21 -0000

--f46d04089131d3159404c64bd58e
Content-Type: text/plain; charset=ISO-8859-1

Will you please re-post this to the thread on <ietf-822@ietf.org> ?

Barry

On Thursday, August 2, 2012, John Levine wrote:

> Executive summary: nothing broke.
>
> * Alpine (my normal client)
>
> Displayed OK.  Invented a matching Reply-To: line.  If I reply, the To:
> line is empty.
>
> * Thunderbird
>
> Displayed OK. Reply put the same empty From: group on the To: line,
> rejects attempts to
> send it with a message saying to fix the To: line.
>
> * Evolution
>
> Displayed OK. Reply has a blank To: line.
>
> * Android mail
>
> Displayed OK. Reply has a blank To: line.
>
> * Squirrelmail (popular webmail IMAP client)
>
> Displayed OK, reply put the null group on the To: line and let you try
> to send mail to it.
>
> * Yahoo Mail
>
> Filed as spam but displayed reasonably.  Reply had an empty To: line.
>
> * Gmail
>
> Filed as spam but displayed reasonably.  Reply had an empty To: line.
>
> * Hotmail aka outlook.com
>
> Displayed OK. Reply put the same empty From: group on the To: line,
> rejects attempts to
> send it with a message saying to fix the To: line.
>
> -----------------------------------
>
> Here's the messge.
>
> Date: Thu, 2 Aug 2012 09:24:15
> From: A foreign person:  ;
> To: john.levine@gmail.com <javascript:;>
> Cc: johnl@taugh.com <javascript:;>
> Subject: let's have lunch
>
> at the sushi place at 1230
>
> Regards,
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/ima
>

--f46d04089131d3159404c64bd58e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Will you please re-post this to the thread on &lt;<a href=3D"mailto:ietf-82=
2@ietf.org">ietf-822@ietf.org</a>&gt; ?<br><br>Barry<span></span><br><br>On=
 Thursday, August 2, 2012, John Levine  wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
Executive summary: nothing broke.<br>
<br>
* Alpine (my normal client)<br>
<br>
Displayed OK. =A0Invented a matching Reply-To: line. =A0If I reply, the To:=
 line is empty.<br>
<br>
* Thunderbird<br>
<br>
Displayed OK. Reply put the same empty From: group on the To: line, rejects=
 attempts to<br>
send it with a message saying to fix the To: line.<br>
<br>
* Evolution<br>
<br>
Displayed OK. Reply has a blank To: line.<br>
<br>
* Android mail<br>
<br>
Displayed OK. Reply has a blank To: line.<br>
<br>
* Squirrelmail (popular webmail IMAP client)<br>
<br>
Displayed OK, reply put the null group on the To: line and let you try<br>
to send mail to it.<br>
<br>
* Yahoo Mail<br>
<br>
Filed as spam but displayed reasonably. =A0Reply had an empty To: line.<br>
<br>
* Gmail<br>
<br>
Filed as spam but displayed reasonably. =A0Reply had an empty To: line.<br>
<br>
* Hotmail aka <a href=3D"http://outlook.com" target=3D"_blank">outlook.com<=
/a><br>
<br>
Displayed OK. Reply put the same empty From: group on the To: line, rejects=
 attempts to<br>
send it with a message saying to fix the To: line.<br>
<br>
-----------------------------------<br>
<br>
Here&#39;s the messge.<br>
<br>
Date: Thu, 2 Aug 2012 09:24:15<br>
From: A foreign person: =A0;<br>
To: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;john=
.levine@gmail.com&#39;)">john.levine@gmail.com</a><br>
Cc: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;john=
l@taugh.com&#39;)">johnl@taugh.com</a><br>
Subject: let&#39;s have lunch<br>
<br>
at the sushi place at 1230<br>
<br>
Regards,<br>
<br>
_______________________________________________<br>
IMA mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;IMA@ietf=
.org&#39;)">IMA@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ima" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/ima</a><br>
</blockquote>

--f46d04089131d3159404c64bd58e--

From yaojk@cnnic.cn  Sun Aug 12 19:22:41 2012
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5129121F8674 for <ima@ietfa.amsl.com>; Sun, 12 Aug 2012 19:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.352
X-Spam-Level: 
X-Spam-Status: No, score=-99.352 tagged_above=-999 required=5 tests=[AWL=-1.106, BAYES_50=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GMGXlcOOJpQ for <ima@ietfa.amsl.com>; Sun, 12 Aug 2012 19:22:40 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 6FF8B21F8668 for <ima@ietf.org>; Sun, 12 Aug 2012 19:22:38 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 13 Aug 2012 10:22:34 +0800
Message-ID: <2C99065D1FF1473ABDEEE8823F8F338D@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Arnt Gulbrandsen" <arnt@gulbrandsen.priv.no>
References: <07C040412CE5237C850BE452@JCK-EEE10><5016D121.1070500@gulbrandsen.priv.no><78F457593C1910CCBD98F3C3@JCK-EEE10> <50192E10.7050506@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 10:22:34 +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.6157
Cc: ima@ietf.org
Subject: Re: [EAI] New documents coming?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 02:22:41 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFybnQgR3VsYnJhbmRzZW4i
IDxhcm50QGd1bGJyYW5kc2VuLnByaXYubm8+DQpUbzogIkpvaG4gQyBLbGVuc2luIiA8a2xlbnNp
bkBqY2suY29tPg0KQ2M6IDxpbWFAaWV0Zi5vcmc+DQpTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAw
MSwgMjAxMiA5OjI0IFBNDQpTdWJqZWN0OiBSZTogW0VBSV0gTmV3IGRvY3VtZW50cyBjb21pbmc/
DQoNCg0KPiBPbiAwNy8zMC8yMDEyIDA4OjMyIFBNLCBKb2huIEMgS2xlbnNpbiB3cm90ZToNCj4+
IEFzc3VtaW5nIHRoZSBXRyBhZ3JlZXMgd2l0aCB5b3UgdGhhdCB3ZSBkb24ndCAgbmVlZCBhIG5l
dyBkcmFmdA0KPj4gYmVmb3JlIGRpc2N1c3Npb24gb24gVGh1cnNkYXksIGl0IHdvdWxkIGJlIHJl
YXNvbmFibGUgZm9yIHlvdSB0bw0KPj4gd2FpdCB1bnRpbCB0aGUgZW5kIG9mIHRoaXMgd2VlayBv
ciBiZWdpbm5pbmcgb2YgbmV4dCB0byBnZW5lcmF0ZQ0KPj4gYSBuZXcgZHJhZnQuICAgSWYgeW91
IGhhZCB0aGUgZW5lcmd5IHRvIHByZXBhcmUgYSBzaG9ydCBub3RlDQo+PiBsaXN0aW5nIHRob3Nl
IGNoYW5nZXMgdGhhdCB5b3UgY29uc2lkZXIgc3Vic3RhbnRpdmUgYnV0DQo+PiB1bmNvbnRyb3Zl
cnNpYWwsIHRoYXQgd291bGQgYmUgaGVscGZ1bC4NCj4+DQo+PiBnb29kIGx1Y2sgd2l0aCB0aGUg
Y2F0Y2h1cCBwcm9jZXNzIC0tIGhvcGUgeW91IGFyZSBmdWxseQ0KPj4gcmVjb3ZlcmVkIGF0IGxl
YXN0Lg0KPiANCj4gQWxsIHdlbGwsIGp1c3Qgc3RydWdnbGluZyB3aXRoIHRoZSBiYWNrbG9nLg0K
PiANCg0KaG93IGFib3V0IHlvdXIgYmFja2xvZz8NCg0KSSB0aGluayB0aGF0IGNoYWlycyBhcmUg
d2FpdGluZyBmb3IgeW91ciBuZXcgdmVyc2lvbiBkcmFmdCBiZWZvcmUgc2VuZGluZyA0IGRyYWZ0
cyB0byBBRC4NCg0KSWYgZXZlcnl0aGluZyBpcyBvaywgY291bGQgeW91IGtpbmRseSB1cGRhdGUg
dGhlIGRyYWZ0IEFTQVA/DQoNCkppYW5rYW5nIFlhbw0KDQoNCj4gVGhlIHN1YnN0YW50aXZlIGlz
c3VlIHdhcyBpbiBmYWN0IG5vdCBiZSBmcm9tIHlvdXIgcmV2aWV3LCBpdCB3YXMgdGhlIA0KPiBv
bGRlciBvcGVuIGlzc3VlLiBTaW5jZSBub29uZSBoYXMgc2FpZCBhIHdvcmQgYWJvdXQgaXQgSSBh
c3N1bWUgcGVvcGxlIA0KPiBkb24ndCB0aGluayBpdCdzIHdvcnRoIHRoZSBib3RoZXIsIHNvIEkg
anVzdCBkZWxldGVkIHRoZSBpc3N1ZSBhbmQgd2lsbCANCj4ga2VlcCB0aGUgcmVzcG9uc2UgY29k
ZSBuYW1lIGFuZCBzZW1hbnRpY3MgYXMgaW4gdGhlIHByZXNlbnQgZHJhZnQuDQo+IA0KPiBJIGRv
bid0IHRoaW5rIEkgY2FuIG1hbmFnZSB0aGUgd29yZHNtaXRoaW5nIG5lY2Vzc2FyeSBmb3IgeW91
ciB0ZXh0dWFsIA0KPiBpc3N1ZXMgdG9kYXkuIFNvcnJ5Lg0KPiANCj4gQXJudA0KPiANCj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSU1BIG1haWxp
bmcgbGlzdA0KPiBJTUFAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pbWE=


From arnt@gulbrandsen.priv.no  Sun Aug 12 23:32:37 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D0621F857D for <ima@ietfa.amsl.com>; Sun, 12 Aug 2012 23:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b66B0e8Xy2eH for <ima@ietfa.amsl.com>; Sun, 12 Aug 2012 23:32:36 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id A621621F8578 for <ima@ietf.org>; Sun, 12 Aug 2012 23:32:36 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4A2B1F8C517; Mon, 13 Aug 2012 06:32:35 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1344839554-16755-16754/10/6; Mon, 13 Aug 2012 06:32:34 +0000
Message-Id: <50289F8A.9000300@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 08:32:42 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
Mime-Version: 1.0
To: ima@ietf.org
References: <07C040412CE5237C850BE452@JCK-EEE10> <5016D121.1070500@gulbrandsen.priv.no> <78F457593C1910CCBD98F3C3@JCK-EEE10> <50192E10.7050506@gulbrandsen.priv.no> <2C99065D1FF1473ABDEEE8823F8F338D@LENOVO47E041CF>
In-Reply-To: <2C99065D1FF1473ABDEEE8823F8F338D@LENOVO47E041CF>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [EAI] New documents coming?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 06:32:37 -0000

On 08/13/2012 04:22 AM, Jiankang YAO wrote:
> how about your backlog?

I ended Friday (almost) without one.

> I think that chairs are waiting for your new version draft before =
sending 4 drafts to AD.
>
> If everything is ok, could you kindly update the draft ASAP?

There's an excellent chance I'll get it done today.

Arnt


From yaojk@cnnic.cn  Mon Aug 13 00:53:00 2012
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B31D21F8639 for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 00:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.294
X-Spam-Level: 
X-Spam-Status: No, score=-99.294 tagged_above=-999 required=5 tests=[AWL=-1.048, BAYES_50=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yJXUSX99Jc7 for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 00:52:59 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 1784221F851B for <ima@ietf.org>; Mon, 13 Aug 2012 00:52:56 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 13 Aug 2012 15:52:53 +0800
Message-ID: <1CB9069147A54B28B0862FD5084542BB@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "Arnt Gulbrandsen" <arnt@gulbrandsen.priv.no>, <ima@ietf.org>
References: <07C040412CE5237C850BE452@JCK-EEE10><5016D121.1070500@gulbrandsen.priv.no><78F457593C1910CCBD98F3C3@JCK-EEE10><50192E10.7050506@gulbrandsen.priv.no><2C99065D1FF1473ABDEEE8823F8F338D@LENOVO47E041CF> <50289F8A.9000300@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 15:52:52 +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.6157
Subject: Re: [EAI] New documents coming?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 07:53:00 -0000

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFybnQgR3VsYnJhbmRzZW4i
IDxhcm50QGd1bGJyYW5kc2VuLnByaXYubm8+DQpUbzogPGltYUBpZXRmLm9yZz4NClNlbnQ6IE1v
bmRheSwgQXVndXN0IDEzLCAyMDEyIDI6MzIgUE0NClN1YmplY3Q6IFJlOiBbRUFJXSBOZXcgZG9j
dW1lbnRzIGNvbWluZz8NCg0KDQo+IE9uIDA4LzEzLzIwMTIgMDQ6MjIgQU0sIEppYW5rYW5nIFlB
TyB3cm90ZToNCj4+IGhvdyBhYm91dCB5b3VyIGJhY2tsb2c/DQo+IA0KPiBJIGVuZGVkIEZyaWRh
eSAoYWxtb3N0KSB3aXRob3V0IG9uZS4NCj4gDQo+PiBJIHRoaW5rIHRoYXQgY2hhaXJzIGFyZSB3
YWl0aW5nIGZvciB5b3VyIG5ldyB2ZXJzaW9uIGRyYWZ0IGJlZm9yZSBzZW5kaW5nIDQgZHJhZnRz
IHRvIEFELg0KPj4NCj4+IElmIGV2ZXJ5dGhpbmcgaXMgb2ssIGNvdWxkIHlvdSBraW5kbHkgdXBk
YXRlIHRoZSBkcmFmdCBBU0FQPw0KPiANCj4gVGhlcmUncyBhbiBleGNlbGxlbnQgY2hhbmNlIEkn
bGwgZ2V0IGl0IGRvbmUgdG9kYXkuDQo+IA0KDQpHcmVhdCEhDQoNCkppYW5rYW5nIFlhbw0KDQo+
IEFybnQNCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IElNQSBtYWlsaW5nIGxpc3QNCj4gSU1BQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaW1h


From internet-drafts@ietf.org  Mon Aug 13 04:47:40 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F28F421F8702; Mon, 13 Aug 2012 04:47:39 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1hv+TRVfXUYZ; Mon, 13 Aug 2012 04:47:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 681DB21F870A; Mon, 13 Aug 2012 04:47:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120813114739.1174.72705.idtracker@ietfa.amsl.com>
Date: Mon, 13 Aug 2012 04:47:39 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 11:47:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : Simplified POP/IMAP Downgrading for Internationalized Em=
ail
	Author(s)       : Arnt Gulbrandsen
	Filename        : draft-ietf-eai-simpledowngrade-06.txt
	Pages           : 8
	Date            : 2012-08-13

Abstract:
   This document specifies a method for IMAP and POP servers to serve
   internationalized messages to conventional clients. The specification
   is simple, easy to implement and provides only rudimentary results.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-simpledowngrade

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-simpledowngrade-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-simpledowngrade-06


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


From arnt@gulbrandsen.priv.no  Mon Aug 13 04:55:10 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652FB21F8713 for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 04:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHG8VWBL8RXt for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 04:55:10 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2DFB21F8705 for <ima@ietf.org>; Mon, 13 Aug 2012 04:55:09 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 5C544FA053A; Mon, 13 Aug 2012 11:55:09 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1344858908-16755-16754/10/8; Mon, 13 Aug 2012 11:55:08 +0000
Message-Id: <5028EB24.5040500@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 13:55:16 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
Mime-Version: 1.0
To: IMA Discussion <ima@ietf.org>
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com>
In-Reply-To: <20120813114739.1174.36751.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Subject: Re: [EAI] New Version Notification - draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 11:55:10 -0000

On 08/13/2012 01:47 PM, internet-drafts@ietf.org wrote:
> A new version (-06) has been submitted for draft-ietf-eai-simpledowngrade:
> http://www.ietf.org/internet-drafts/draft-ietf-eai-simpledowngrade-06.txt

Wording only.

I even changed one item with which I violently disagree. Clearly I need 
a vacation.

Arnt


From barryleiba.mailing.lists@gmail.com  Mon Aug 13 07:30:52 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B1621F8513 for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 07:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.02
X-Spam-Level: 
X-Spam-Status: No, score=-103.02 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3prrujya7Kg for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 07:30:51 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 87E5621F84F9 for <ima@ietf.org>; Mon, 13 Aug 2012 07:30:51 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so2181652lbb.31 for <ima@ietf.org>; Mon, 13 Aug 2012 07:30:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QYjQp37mZeqxDfzIA+vaKYrUFV7Mu+pSVKeKh8ETY5s=; b=X/dox6bnCAdkXeJeGONtF9x4ecn3mrd8yO4XJ86w80ifQhKGvmc3YT0tMGIlIUszW8 kO5/HUP8hRXykGxfxcJnZ/i+wji2mr3b9uqDbhBlYT4TYBexqDiTo74yg5TkiuWWBnu1 MCNaDa8l0Z9fZtP/zX5sB0Km+EYDXbPTloitSQLBlOg19/q5L70KiyWuJCWcnA/fTs6A K/gxlKMAwb1hvMcF+OAellR14iYBL7UItFMREieeix3m+4JxsjwpixbRkdiUxLgUbwLK kLP6STa3Aihvcu6Qp2hZyMIA+vjx3/sjGMI9Ov9Fpc7Zpo+eMmh1ZHAdT9XTPPupnD8w 5ZAw==
MIME-Version: 1.0
Received: by 10.112.23.40 with SMTP id j8mr6522189lbf.31.1344868250438; Mon, 13 Aug 2012 07:30:50 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Mon, 13 Aug 2012 07:30:50 -0700 (PDT)
In-Reply-To: <5028EB24.5040500@gulbrandsen.priv.no>
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com> <5028EB24.5040500@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 10:30:50 -0400
X-Google-Sender-Auth: J6pN8AYL4uvHcdeK_4Xc9kfkPdM
Message-ID: <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IMA Discussion <ima@ietf.org>
Subject: Re: [EAI] New Version Notification - draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 14:30:52 -0000

>> A new version (-06) has been submitted for draft-ietf-eai-simpledowngrade:
>> http://www.ietf.org/internet-drafts/draft-ietf-eai-simpledowngrade-06.txt

The last paragraph of 2.1 doesn't set off "for example" properly with
commas, and because "Received" is a regular word I'm afraid the RFC
Editor might get it wrong.

OLD
   The affected header fields are Bcc, Cc, From, Reply-To, Resent-Bcc,
   Resent-Cc, Resent-From, Resent-Sender, Resent-To, Return-Path, Sender
   and To.  Any addresses present in other header fields, Received for
   example, are not regarded as addresses by this specification.

NEW
   The affected header fields are Bcc, Cc, From, Reply-To, Resent-Bcc,
   Resent-Cc, Resent-From, Resent-Sender, Resent-To, Return-Path, Sender
   and To.  Any addresses present in other header fields, such as Received,
   are not regarded as addresses by this specification.

If you really want to use "for example", you have to do it this way
(and I think it's more awkward): "Any addresses present in other
header fields -- Received, for example -- are not regarded as
addresses by this specification."

In Section 3, version -05 introduced a typo, "nFETCH"; please fix
that, because the RFC Editor won't know what to do with it.

In Section 5, you aren't consistent in capitalizing header field names
(which you do in the rest of the document):

   If any excised information is significant, then that information does
   not arrive at the recipient. Notably, the message-id, in-reference-to
   and/or references fields may be excised, which might cause a lack of
   context when the recipient reads the message.

Please fix that (three field names); the RFC Editor won't.

Also introduced in -05:
OLD
   Some POP/IMAP clients delete the original message and use only the
   what they downloaded, Fetchmail is one well-known example. This may
   lead to permament loss of information.

Apart from the spurious "the", the misspelling, and the comma splice,
there's a general problem with how this paragraph explains the
situation.  I suggest this:

NEW
   Some POP or IMAP clients, such as Fetchmail, download messages
   and delete the version on the server.  This may lead to permanent loss
   of information when the only remaining version of a message is the
   downgraded one.

While you're making changes: in section 7, just get the registry name
right (which you pretty much have) and you don't have to babble at the
RFC Editor:

OLD
   The IANA is requested to add DOWNGRADED to the IMAP response code
   registry.

   (RFC editor: Please edit the previous paragraph suitably once the
   IANA has added the code. The registry is the one specified in RFC
   5530.)

NEW
   The IANA is requested to add DOWNGRADED to the IMAP Response
   Codes registry.

-----------

That's it; the RFC Editor will sort out the rest of the
language/grammar issues, so with the above changes I think this is
ready to go.

--
Barry

From klensin@jck.com  Mon Aug 13 08:22:08 2012
Return-Path: <klensin@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE9E21F87AF for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 08:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8+X4P5eRlu2v for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 08:22:07 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 397CA21F8775 for <ima@ietf.org>; Mon, 13 Aug 2012 08:22:07 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1T0wMq-000Eoz-Ti; Mon, 13 Aug 2012 11:15:44 -0400
Date: Mon, 13 Aug 2012 11:21:49 -0400
From: John C Klensin <klensin@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Message-ID: <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.com>
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com> <5028EB24.5040500@gulbrandsen.priv.no> <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.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 Discussion <ima@ietf.org>
Subject: Re: [EAI] New Version Notification -	draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 15:22:09 -0000

--On Monday, August 13, 2012 10:30 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>>> A new version (-06) has been submitted for
>>> draft-ietf-eai-simpledowngrade:
>>> http://www.ietf.org/internet-drafts/draft-ietf-eai-simpledow
>>> ngrade-06.txt
> 
> The last paragraph of 2.1 doesn't set off "for example"
> properly with commas, and because "Received" is a regular word
> I'm afraid the RFC Editor might get it wrong.
> 
> OLD
>    The affected header fields are Bcc, Cc, From, Reply-To,
> Resent-Bcc,    Resent-Cc, Resent-From, Resent-Sender,
> Resent-To, Return-Path, Sender    and To.  Any addresses
> present in other header fields, Received for    example, are
> not regarded as addresses by this specification.
> 
> NEW
>    The affected header fields are Bcc, Cc, From, Reply-To,
> Resent-Bcc,    Resent-Cc, Resent-From, Resent-Sender,
> Resent-To, Return-Path, Sender    and To.  Any addresses
> present in other header fields, such as Received,    are not
> regarded as addresses by this specification.
> 
> If you really want to use "for example", you have to do it
> this way (and I think it's more awkward): "Any addresses
> present in other header fields -- Received, for example -- are
> not regarded as addresses by this specification."

An alternate way to deal with this is to use the convention
about header field names used in many other documents.  That
would turn the original paragraph into:

	The affected header fields are "Bcc:", "Cc:", "From:",
	"Reply-To:", "Resent-Bcc:", "Resent-Cc:",
	"Resent-From:", "Resent-Sender:", "Resent-To:",
	"Return-Path:", "Sender:" and "To:".  Any addresses
	present in other header fields, "Received:" for example,
	are not regarded as addresses by this specification.

Barry's suggestion about setting '"Received:" for example' off
with dashes would further improve even that form, IMO.

The choice is left to author discretion as far as I'm concerned.
But I vaguely recall a recent debate with the RFC Editor about
header field names and would predict that, if you go with the
unquoted alternative, we will have questions to answer during
the editing process.


>...
> -----------
> 
> That's it; the RFC Editor will sort out the rest of the
> language/grammar issues, so with the above changes I think
> this is ready to go.

See above.  

best,
   john

p.s. Barry, thanks for the careful checking.


From barryleiba@gmail.com  Mon Aug 13 09:17:58 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECEE21F870A for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 09:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.019
X-Spam-Level: 
X-Spam-Status: No, score=-103.019 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G4S+FFtEAJXA for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 09:17:57 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8B35A21F86F3 for <ima@ietf.org>; Mon, 13 Aug 2012 09:17:57 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so4011394vbb.31 for <ima@ietf.org>; Mon, 13 Aug 2012 09:17:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ntKgnAFzxCjZAw2yHED+L2Igcn8g3EHC5AAY49unwKs=; b=fbtNOd8Vsb+E7w1GdO2GHB0eUCdq6ZPKSiiodyA4VmpTHVF3MY+FHWeE5wDrNTzgoL e/qfdt4Dw/bM0RFecUY+FZDqBFiM7BTRzjRj36thvUli7LEtbGDgrc4IuXRZ3AFk6GCV +Jz8RwVqB4pBT547JoWahH0uwfgPktA1wxUOgpMLhv6inM5yRk7mDVwJVmur5DvunhL+ f1fy3aV1f4Zq2DHafQsvIHFuVTYT+y2j/ZXm0k2+bQC+1/ReTI+bX/Jcl+j8AESOh54Q U2rGeku5Q8J6RmLqvBjnKMrO1lMqqJcc8ooL9u0H9EiZxaZDEE8EMFl8HzhDbs+9qHyi MtUw==
MIME-Version: 1.0
Received: by 10.52.36.33 with SMTP id n1mr436028vdj.27.1344874676610; Mon, 13 Aug 2012 09:17:56 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.220.63.6 with HTTP; Mon, 13 Aug 2012 09:17:56 -0700 (PDT)
In-Reply-To: <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com>
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com> <5028EB24.5040500@gulbrandsen.priv.no> <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.com> <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com>
Date: Mon, 13 Aug 2012 12:17:56 -0400
X-Google-Sender-Auth: uby634oeAkv_oVz_MtlRbOGRIxs
Message-ID: <CALaySJ+OKfWJBki5YfP3UGRKtiM7oeqK2=uaj4tDpxBR2q+VHA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <klensin@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, IMA Discussion <ima@ietf.org>
Subject: Re: [EAI] New Version Notification - draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 16:17:58 -0000

> An alternate way to deal with this is to use the convention
> about header field names used in many other documents.  That
> would turn the original paragraph into:
>
>         The affected header fields are "Bcc:", "Cc:", "From:",

Yeah, I really wanted to avoid the ugly gobs of quotation marks.  If
the RFC Editor will put them in anyway, we might as well.  But if we
can manage without them, I think the document will read better without
them.  Why don't we try?

>         present in other header fields, "Received:" for example,
>         are not regarded as addresses by this specification.
>
> Barry's suggestion about setting '"Received:" for example' off
> with dashes would further improve even that form, IMO.

I think it's quite necessary, actually.  Consider this sentence:

   I have a lot of friends, John for example.

That's simply wrong.  First, it's a comma splice (a form of a run-on
sentence), and second, "for example" itself needs to be separated from
"John" by a comma.  That's why I think the long-dash isn't just nice,
but necessary:

  I have a lot of friends -- John, for example.

In any case, as long as we fix it so it's unambiguous, the RFC Editor
will take care of the fine grammatical points.  I'm just worried about
what the RFC Editor might not quite understand.  So, yes, adding all
those icky quotation marks will make it clear.

b

From klensin@jck.com  Mon Aug 13 09:35:12 2012
Return-Path: <klensin@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5D221F8594 for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 09:35:12 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxoKl713KfSO for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 09:35:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E346421F858E for <ima@ietf.org>; Mon, 13 Aug 2012 09:35:11 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1T0xVb-000Ezi-Ao; Mon, 13 Aug 2012 12:28:51 -0400
Date: Mon, 13 Aug 2012 12:34:56 -0400
From: John C Klensin <klensin@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <C1A2069F6AB1C05AB3A974EB@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJ+OKfWJBki5YfP3UGRKtiM7oeqK2=uaj4tDpxBR2q+VHA@mail.gmail.com>
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com> <5028EB24.5040500@gulbrandsen.priv.no> <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.com> <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com> <CALaySJ+OKfWJBki5YfP3UGRKtiM7oeqK2=uaj4tDpxBR2q+VHA@mail.gmail.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: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, IMA Discussion <ima@ietf.org>
Subject: Re: [EAI] New Version Notification - draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 16:35:12 -0000

--On Monday, August 13, 2012 12:17 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> An alternate way to deal with this is to use the convention
>> about header field names used in many other documents.  That
>> would turn the original paragraph into:
>> 
>>         The affected header fields are "Bcc:", "Cc:", "From:",
> 
> Yeah, I really wanted to avoid the ugly gobs of quotation
> marks.  If the RFC Editor will put them in anyway, we might as
> well.  But if we can manage without them, I think the document
> will read better without them.  Why don't we try?

Wfm.  As with other things, I'm much happier going into the
review and editing process with "we discussed that, and...".

>>         present in other header fields, "Received:" for
>>         example, are not regarded as addresses by this
>>         specification.
>> 
>> Barry's suggestion about setting '"Received:" for example' off
>> with dashes would further improve even that form, IMO.
> 
> I think it's quite necessary, actually.  Consider this
> sentence:
> 
>    I have a lot of friends, John for example.
> 
> That's simply wrong.  First, it's a comma splice (a form of a
> run-on sentence), and second, "for example" itself needs to be
> separated from "John" by a comma.  That's why I think the
> long-dash isn't just nice, but necessary:
> 
>   I have a lot of friends -- John, for example.

Indeed.  The original sentence read badly to me for other
reasons and I would have preferred, using this example, 

    I have a lot of friends including, for example, John.

or, using the original sentence,

	Any addresses present in other header fields such as
	"Received:" are not regarded as addresses by this
	specification.

with the question of whether there should be commas around 'such
as "Received:"' (and before "including," is part of another
discussion (the RFC Editor would probably say "yes").

But I think this is a matter that would be certain to be spotted
and fixed by the RFC Editor so, other than getting rid of the
original (and clearly incorrect) sentence, I think this can be
left to author discretion and to them.

    john


    
> In any case, as long as we fix it so it's unambiguous, the RFC
> Editor will take care of the fine grammatical points.  I'm
> just worried about what the RFC Editor might not quite
> understand.  So, yes, adding all those icky quotation marks
> will make it clear.
> 
> b





From arnt@gulbrandsen.priv.no  Mon Aug 13 13:59:09 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEBE421F867F for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 13:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFMIdP7r-opK for <ima@ietfa.amsl.com>; Mon, 13 Aug 2012 13:59:09 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2552821F8671 for <ima@ietf.org>; Mon, 13 Aug 2012 13:59:08 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 20550FA03ED; Mon, 13 Aug 2012 20:59:08 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1344891547-16224-16223/10/2; Mon, 13 Aug 2012 20:59:07 +0000
Message-Id: <50296AA3.8010409@gulbrandsen.priv.no>
Date: Mon, 13 Aug 2012 22:59:15 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
Mime-Version: 1.0
To: ima@ietf.org
References: <20120813114739.1174.36751.idtracker@ietfa.amsl.com> <5028EB24.5040500@gulbrandsen.priv.no> <CAC4RtVByE3hL8UpXGtfxzSRRPcswrG8orSGHghC628EnYVbr2g@mail.gmail.com> <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com>
In-Reply-To: <E224C4E3E473D85E07FEC934@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [EAI] New Version Notification -	draft-ietf-eai-simpledowngrade-06.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 20:59:09 -0000

On 08/13/2012 05:21 PM, John C Klensin wrote:
> An alternate way to deal with this is to use the convention
> about header field names used in many other documents.  That
> would turn the original paragraph into:

... would turn the paragraph into something rather foreign. We (the 
audience for the RFC) don't usually quote field names when writing to 
each other, so why should an RFC?

Barry: I'm too tired to attend to your mail tonight.

Arnt

From internet-drafts@ietf.org  Tue Aug 14 13:11:16 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC2521F8621; Tue, 14 Aug 2012 13:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.422
X-Spam-Level: 
X-Spam-Status: No, score=-102.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OaWd6Y9RrcN; Tue, 14 Aug 2012 13:11:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D34321E8063; Tue, 14 Aug 2012 13:11:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120814201115.9083.78431.idtracker@ietfa.amsl.com>
Date: Tue, 14 Aug 2012 13:11:15 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-simpledowngrade-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 20:11:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : Simplified POP/IMAP Downgrading for Internationalized Em=
ail
	Author(s)       : Arnt Gulbrandsen
	Filename        : draft-ietf-eai-simpledowngrade-07.txt
	Pages           : 8
	Date            : 2012-08-14

Abstract:
   This document specifies a method for IMAP and POP servers to serve
   internationalized messages to conventional clients. The specification
   is simple, easy to implement and provides only rudimentary results.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-simpledowngrade

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-simpledowngrade-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-simpledowngrade-07


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


From barryleiba.mailing.lists@gmail.com  Tue Aug 14 14:04:23 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA3521E80B0 for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 14:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.017
X-Spam-Level: 
X-Spam-Status: No, score=-103.017 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6itOiVKlZDhT for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 14:04:22 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 65F3C21E809D for <ima@ietf.org>; Tue, 14 Aug 2012 14:04:22 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so527228lbb.31 for <ima@ietf.org>; Tue, 14 Aug 2012 14:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Z06iqMkDdyhQDZcu09404AMq5BbJRxxup6/rwS8G/ig=; b=i1tZclXAtMy2YXRb3vV7h3TykaRFhl4DNQi8DTOf2USmKmPioWMcsIFMpAV7AkQp0J qub5ZsfaBPwLcCOT84Ce0Ksk7u3Zs1WsADvv7QxT7EdZ6GCDKckS0bCyDBxRfnOlQ96v yCa0pLVvwfZvkg1N1ftmfm74m3MLVIO4QksZ2XumzNr/tMozzqDnOniq3PXFKgXKjmVg uB1sI+hDt/Hl+wnM5oOaMu7KfkEvdzAD7IJpZqAkR4IWRI7jFiYgtCYW+C0sCEqGChEx C7GLS/pT54+LqQaCsG+RTsoPy6aIXafqOx1jOjlc5wmv0kiZu+aOHCF3vVPpMP9Hm/If eIcw==
MIME-Version: 1.0
Received: by 10.112.46.136 with SMTP id v8mr4387118lbm.5.1344978261341; Tue, 14 Aug 2012 14:04:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Tue, 14 Aug 2012 14:04:21 -0700 (PDT)
In-Reply-To: <20120814201115.9083.78431.idtracker@ietfa.amsl.com>
References: <20120814201115.9083.78431.idtracker@ietfa.amsl.com>
Date: Tue, 14 Aug 2012 17:04:21 -0400
X-Google-Sender-Auth: uISwgtdJ3gyVipJRkpS-V92JefQ
Message-ID: <CAC4RtVBGdXemGjx=rVJ==XWCrfYPNsoH0rD5kUNkPdTorsm1fw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "ima@ietf.org" <ima@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec554d22a7f77da04c7402721
Subject: Re: [EAI] I-D Action: draft-ietf-eai-simpledowngrade-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:04:23 -0000

--bcaec554d22a7f77da04c7402721
Content-Type: text/plain; charset=ISO-8859-1

> Text changes from Barry Leiba. I hate case sensitivity in human
> language, but right now I need to pack my suitcases, not argue.

Ah, well, waddyagonnado?  'tis a fact of life.  You can hate the moon, but
it's not going away.

This version's ready to ship.

Barry

--bcaec554d22a7f77da04c7402721
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span class=3D"Apple-style-span" style><div>&gt; Text changes from Barry Le=
iba. I hate case sensitivity in human</div><div>&gt;=A0<span class=3D"Apple=
-style-span" style>language, but right now I need to pack my suitcases, not=
 argue.</span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>Ah, well, waddyagonnado? =A0&#39;tis a fact o=
f life. =A0You can hate the moon, but it&#39;s not going away.</span></div>=
<div>
<span class=3D"Apple-style-span" style><br></span></div><div><span class=3D=
"Apple-style-span" style>This version&#39;s ready to ship.</span></div><div=
><span class=3D"Apple-style-span" style><br></span></div><div><span class=
=3D"Apple-style-span" style>Barry</span></div>
</span>

--bcaec554d22a7f77da04c7402721--

From arnt@gulbrandsen.priv.no  Tue Aug 14 14:58:10 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF5D421E80B7 for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 14:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkcTfIHcSxMB for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 14:58:10 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAAF21E8050 for <ima@ietf.org>; Tue, 14 Aug 2012 14:58:10 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 3D55AF8D3E1; Tue, 14 Aug 2012 21:58:09 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1344981488-16224-16223/10/8; Tue, 14 Aug 2012 21:58:08 +0000
Message-Id: <502AC9FA.6070307@gulbrandsen.priv.no>
Date: Tue, 14 Aug 2012 23:58:18 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
Mime-Version: 1.0
To: ima@ietf.org
References: <20120814201115.9083.78431.idtracker@ietfa.amsl.com> <CAC4RtVBGdXemGjx=rVJ==XWCrfYPNsoH0rD5kUNkPdTorsm1fw@mail.gmail.com>
In-Reply-To: <CAC4RtVBGdXemGjx=rVJ==XWCrfYPNsoH0rD5kUNkPdTorsm1fw@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [EAI] I-D Action: draft-ietf-eai-simpledowngrade-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:58:11 -0000

On 08/14/2012 11:04 PM, Barry Leiba wrote:
> Ah, well, waddyagonnado?  'tis a fact of life.  You can hate the moon,
> but it's not going away.

Sometimes it's a fact of time, more often it can be argued. If you want 
I'll argue it after my vacation, which starts tomorrow. Network access 
will be excellent, but perhaps not too often used.

Arnt

From barryleiba.mailing.lists@gmail.com  Tue Aug 14 15:09:54 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7FE21E80BB for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 15:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.017
X-Spam-Level: 
X-Spam-Status: No, score=-103.017 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OB84GG06bxGS for <ima@ietfa.amsl.com>; Tue, 14 Aug 2012 15:09:54 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF9DF21E80BE for <ima@ietf.org>; Tue, 14 Aug 2012 15:09:53 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so554398lbb.31 for <ima@ietf.org>; Tue, 14 Aug 2012 15:09:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NqkiEtxtEFy+Nvw0tZtLG4UCj7Cdi/XZQIxJxKLe+II=; b=dSujO44q9FFh1WKJV8CeMEE7VoKGDlptvbJUeTVda0rYPyWxZhEvNtcBIoQ3n8g9ov 624muyfn6r9zeYH1iqwol2gxEtY18McBs7q+6W/Z55r7zQLVf+E5e4+17Eh2zdbHhw7H Lc0v3xaFOLnZuQc5TYdwLNtOmJ5TGdI+iK+LbIoGKHWuZQd/5Ks2MUJh/kv+qfWWJlsw voaqy+AZw8Ce1l7wfpfMoh7c3QLfvLc/du5lfnXJqa/pCPfGCjVsnVm3vKM0m6zW27A5 GlJoP2tCSwBFMu4F16kBYR6VY0ukwnz7P6JRqYYeEBpL4ltS20Y8ZSyEwN7zqwiE5gwt u1fw==
MIME-Version: 1.0
Received: by 10.152.112.136 with SMTP id iq8mr13914302lab.18.1344982192868; Tue, 14 Aug 2012 15:09:52 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Tue, 14 Aug 2012 15:09:52 -0700 (PDT)
In-Reply-To: <502AC9FA.6070307@gulbrandsen.priv.no>
References: <20120814201115.9083.78431.idtracker@ietfa.amsl.com> <CAC4RtVBGdXemGjx=rVJ==XWCrfYPNsoH0rD5kUNkPdTorsm1fw@mail.gmail.com> <502AC9FA.6070307@gulbrandsen.priv.no>
Date: Tue, 14 Aug 2012 18:09:52 -0400
X-Google-Sender-Auth: zHjxrzE4mgbNN8Z-jvR5MBK_Ijs
Message-ID: <CAC4RtVDviSdjYxqx0tcFsgXKVp61mw8s6YG+2ZNQ80Q_+BTPsg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ima@ietf.org
Subject: Re: [EAI] I-D Action: draft-ietf-eai-simpledowngrade-07.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 22:09:54 -0000

> If you want I'll argue it

Nah.

> after my vacation, which starts tomorrow.

Enjoy.

b

From iesg-secretary@ietf.org  Wed Aug 15 13:54:52 2012
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C1311E80CC; Wed, 15 Aug 2012 13:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QBaC0NCBk8lx; Wed, 15 Aug 2012 13:54:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0C711E8098; Wed, 15 Aug 2012 13:54:51 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120815205451.9633.43183.idtracker@ietfa.amsl.com>
Date: Wed, 15 Aug 2012 13:54:51 -0700
Cc: ima@ietf.org
Subject: [EAI] Last Call: <draft-ietf-eai-mailinglistbis-05.txt> (Mailing Lists and	non-ASCII Addresses) to Informational RFC
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 20:54:52 -0000

The IESG has received a request from the Email Address
Internationalization WG (eai) to consider the following document:
- 'Mailing Lists and non-ASCII Addresses'
  <draft-ietf-eai-mailinglistbis-05.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-08-29. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes considerations for mailing lists with the
   introduction of non-ASCII UTF-8 email addresses.  It outlines some
   possible scenarios for handling lists with mixtures of non-ASCII and
   traditional addresses, but does not specify protocol changes or offer
   implementation or deployment advice.

   *NOTE TO REVIEWERS: Missing or odd-looking references between
   sections are due to bugs in xml2rfc.  The XML is OK, and the HTML
   output looks reasonable.*




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-eai-mailinglistbis/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-eai-mailinglistbis/ballot/


No IPR declarations have been submitted directly on this I-D.



From jyee@afilias.info  Wed Aug 22 12:15:47 2012
Return-Path: <jyee@afilias.info>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6A0F21F8648 for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 12:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[AWL=-0.743,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lm-RZIOKq1tP for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 12:15:45 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id CC68721F85EA for <ima@ietf.org>; Wed, 22 Aug 2012 12:15:43 -0700 (PDT)
Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1T4GP0-0003Vj-6I for ima@ietf.org; Wed, 22 Aug 2012 19:15:42 +0000
Received: from mail-pb0-f43.google.com ([209.85.160.43]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1T4GP0-0002BO-5u for ima@ietf.org; Wed, 22 Aug 2012 19:15:42 +0000
Received: by pbbrq2 with SMTP id rq2so1803759pbb.2 for <ima@ietf.org>; Wed, 22 Aug 2012 12:15:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=pugu4EnBe8IXwlE7/Zsr4TupDEpqOPQGoMcmp4KsWvs=; b=AAPhGRd+2roo3I1uA3+6r5tc5UHn0LRg9tKvXqP3zV8oLZZCxTZmhAEVK5DjhwklLS R4HnfScuqR+h7Qu813ftipQV5z+/Uiff1KKpQSslLlzt0Xyr//nWyqbhCh21h8iPr4pO 6C1YbV+3S4Cad1QWXWbGM9HENrV0jA8F//AHwGDI4jSyZ3kHiB6bU668DG/BiZ/jzz34 gm2Bh88RxklWozGSz7vItpUICM17dIay77Gd6QhncZAPtM3zzotqjlSWGUfWYrwhLQPw ifq3UxHNa9GBt+h00suPRlORz/Fn/6gxDbe+FuE42AERKUHR2FYvJrlf5VMmD3aOAJLq L4Vw==
MIME-Version: 1.0
Received: by 10.68.237.74 with SMTP id va10mr55572053pbc.46.1345662936993; Wed, 22 Aug 2012 12:15:36 -0700 (PDT)
Received: by 10.66.11.105 with HTTP; Wed, 22 Aug 2012 12:15:36 -0700 (PDT)
Date: Wed, 22 Aug 2012 15:15:36 -0400
Message-ID: <CAF1dMVFdXzHdwgybb6TGNNKB+eY4WojJzpWUGzE+jHxTeKOC2w@mail.gmail.com>
From: Joseph Yee <jyee@afilias.info>
To: EAI WG <ima@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQkus2ZikDTOMMAPIKL5/ww/0X3v68Wh3+bg6YP7fMNcZOjzQUCCUJiPsrWtj1G/t8xtbhCJ
Subject: [EAI] IETF 84 EAI Minutes Uploaded
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 19:15:47 -0000

All,

The minutes of IETF84 uploaded and available at URL below:
http://www.ietf.org/proceedings/84/minutes/minutes-84-eai

Text also available below.

Please advise of any corrections needed.

Regards,
Joseph

--------


EAI (IETF 84) Meeting Minutes

IETF 84 Vancouver
2012-08-02 09:00 AM
Chairs: John Klensin
        Joseph Yee
Scribe: JianKang Yao

Agenda bashing: no changes

Summary:

Mailing List bis:
(draft-ietf-eai-mailinglistbis)
Ready for IESG review, no objections during meeting

Next 4 drafts - POP, IMAP, Downgrade-Display, Simple-Downgrade-Display:
	(draft-ietf-eai-rfc5721bis-06)
	(draft-ietf-eai-5738bis-06)
	(draft-ietf-eai-popimap-downgrade-06)
	(draft-ietf-eai-simpledowngrade-05)
Chair asked if any objection to send these 4 drafts to last call, no
objection to any of them
Chair asked and confirmed that no need to distribute shepherd reports
before submitting to IESG


Discussion of the draft of empty group syntax:
(draft-leiba-5322upd-from-group-03)
John Levine has summary of how some current mail clients managed empty
group syntax, will distribute to EAI and ietf-822 mailing lists

Mailto:
The issue is complex, and we are concerned whether the WG has energy
(and enough subject matter experts on URI/IRI and other issues) to
review the draft. AD Pete Resnick is concerned about possible EAI work
on mailto, and agreed that mailto is not necessary to be handled in
EAI.  There are discussions of impact if mailto dropped from EAI, all
agreed that IRI issues must be settled as prerequisite for IRI-mailto
specification.  Some suggested that IRI adopt the mailto draft and
write an informational draft documenting issues between
internationalization and mailto, but that is not EAI's decision to
make.

[Decision] Tentative agreement that EAI will not work on mailto.

[Action] Chair will bring this tentative agreement to mailing list for
   consensus.

Presentation:
EAI deployment in China & Concerns from software and service
providers (YAO, JianKang)
Many showed interest if there was another demo event.

Some discussion on Sent Messages.

Advice Doc and WG:
[Decision] Best to leave some time for implementation and deployment
   experiences before moving advice docs forward
[Decision] WG will be suspended or killed after the 4 core drafts and
   mailinglist-bis published.  It will be reopened when there are more
   implementation, deployment, and operation experiences.  WG mailing
   list will remain open.
[Decision] EAI will not have WG session in next the IETF meeting
   (IETF85, Atlanta)

------

From jyee@afilias.info  Wed Aug 22 12:56:08 2012
Return-Path: <jyee@afilias.info>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1E7E21F86AA for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 12:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.667
X-Spam-Level: 
X-Spam-Status: No, score=-2.667 tagged_above=-999 required=5 tests=[AWL=-0.690, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eO7oQhK2rP9S for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 12:56:07 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 86B2F21F86B6 for <ima@ietf.org>; Wed, 22 Aug 2012 12:56:07 -0700 (PDT)
Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1T4H27-0005eN-3I for ima@ietf.org; Wed, 22 Aug 2012 19:56:07 +0000
Received: from mail-pb0-f43.google.com ([209.85.160.43]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1T4H26-0003Qt-69 for ima@ietf.org; Wed, 22 Aug 2012 19:56:06 +0000
Received: by pbbrq2 with SMTP id rq2so1844638pbb.2 for <ima@ietf.org>; Wed, 22 Aug 2012 12:56:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=lG0sZ2Og7H+sDFW2N1/SYRbqe5M6V9M1/mEfzzylgQs=; b=D35WbkidQMIMIL9lgfZdPcO/ls8IWjKeHp8R0b2ol5YLdMynxnXSNvB4CAHZ5aSsDx YqX5hQYsMOxJeeNwXe6H/ZzLNc3DY0yZ+ZKdXbzYwEv1GdayvQS8z2A+nigVREg/5n+g E/KrdVjoKENs9Q879EJfkFYLrAt3bZ9Q4ttNC2O2K9RqApuTlpOJmEyOWjVTNX4vFphJ 3Wh36waFMUlJ4FnzbZmU2Ub+U+y2aCuaFVeHKK/cHCSEgAA++GrNsrpIL0s6/75oim7W 06WFyOzbZH2GgbtfvZ7VivGHuDUeelB8RhFxt8CZR1bJeI8lTs8wizprMc39MQTyhhsL 0scg==
MIME-Version: 1.0
Received: by 10.66.76.106 with SMTP id j10mr48335649paw.51.1345665361048; Wed, 22 Aug 2012 12:56:01 -0700 (PDT)
Received: by 10.66.11.105 with HTTP; Wed, 22 Aug 2012 12:56:01 -0700 (PDT)
Date: Wed, 22 Aug 2012 15:56:01 -0400
Message-ID: <CAF1dMVGfVPq=PBw4Pb7kjUPNm62F_7fw=PaXbc5648H8thJ73g@mail.gmail.com>
From: Joseph Yee <jyee@afilias.info>
To: EAI WG <ima@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQmzwQ7ox+FGIR9mw5hFDE9UuUiN0vbP0YkltxjjZAYlAUrP/5/oneP5yiHfDPoXk5mtV13f
Subject: [EAI] EAI Consensus Call on mailto draft
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 19:56:08 -0000

All,

Based on WG discussion at IETF84 (see minutes:
http://www.ietf.org/proceedings/84/minutes/minutes-84-eai), there's a
tentative agreement during meeting for EAI not to take on mailto
draft.  The chairs are looking for broad consensus in the working
group.

Please use this thread for discussion.  The end date of discussion is
August 29, 2012 20:00 UTC and consensus will be announced afterwards.

Regards
John & Joseph

From jyee@afilias.info  Wed Aug 22 14:39:06 2012
Return-Path: <jyee@afilias.info>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBB2621F862B for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 14:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[AWL=-0.644, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id quu8oN1Xl1EW for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 14:39:06 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDD721F8625 for <ima@ietf.org>; Wed, 22 Aug 2012 14:39:05 -0700 (PDT)
Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1T4Idl-000160-46 for ima@ietf.org; Wed, 22 Aug 2012 21:39:05 +0000
Received: from mail-pb0-f43.google.com ([209.85.160.43]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1T4Idl-0005xH-3j for ima@ietf.org; Wed, 22 Aug 2012 21:39:05 +0000
Received: by pbbrq2 with SMTP id rq2so72873pbb.2 for <ima@ietf.org>; Wed, 22 Aug 2012 14:38:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=FFPid03qF9Kao11bHz7QvBMiwV5Ms6MVNFBa7IF8QW8=; b=f2nI0WaCQaeNRp6eWVCfMRmJydsCyROLqOE/7K+rJ+NAqS8yO20DGIl8+qMwBTWdqp 1ybkDmBcNRCrNtaB745pc4LEw4/6x5T+tyCZyXJXOjFdeY7G1EakMNok6a4IWYy2zv1H kHJQZJM8RGhcbxjIcmjQcnC/9oNQ4ft/Qo8414POTWy3aUrGrYSphKVTxvjgnFW3tgqJ 4EFLFpAYqSwUE5DUMyrsbl0UKfC/QAhbCiAfPTvaaDnDGUIwkZtVCumNBeWoyHmZWP7T 4KZClws2ufbAWknjV654cmkEQtGDprl+5sDi+yO9VeaDKuKUZgjeqxoQ8gjQnGx6/Qhz nb1g==
MIME-Version: 1.0
Received: by 10.68.219.226 with SMTP id pr2mr56043258pbc.1.1345671539382; Wed, 22 Aug 2012 14:38:59 -0700 (PDT)
Received: by 10.66.11.105 with HTTP; Wed, 22 Aug 2012 14:38:59 -0700 (PDT)
Date: Wed, 22 Aug 2012 17:38:59 -0400
Message-ID: <CAF1dMVErk1G69_AWaw4X=SWMORggrXOT6DTw3ytDZ8=qZG8nwA@mail.gmail.com>
From: Joseph Yee <jyee@afilias.info>
To: EAI WG <ima@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQlUEAJWHS1FGi5/etl+vKd3HxxL055meWRyHJs5HiiRlZx+dCT/dnvi2KJlsKDuol0Ink6W
Subject: [EAI] Minutes of EAI Interim Meeting at May 14, 2012
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 21:39:07 -0000

All,

The minutes of EAI Interim Meeting held at May 14, 2012 is available
at URL below.
http://www.ietf.org/proceedings/interim/2012/05/14/eai/minutes/minutes-interim-2012-eai-1

Text also available below.

Regards,
Joseph

--------


Meeting Minutes and Summary of EAI Jabber Interim Meeting May 14, 2012
The summary below was organized by topic and document; it only loosely
reflects the order of the meeting discussion.

A summary of critical-path issues for the WG was posted to the
mailing list just before the meeting started:
http://www.ietf.org/mail-archive/web/ima/current/msg04787.html.  The
Jabber log for the meeting is at
http://www.ietf.org/jabber/logs/eai/2012-05-14.html

There was a general discussion about whether the EAI POP and IMAP
documents should be shown as updating the associated base
specifications (RFCs ???? and 3501 respectively).  The conclusion,
after much circling around, was that they are extensions that actually
don't update or change the base documents.  However, the question of
whether extension specifications update base document is really a
matter for the IESG to decide and shepherd's reports will reflect that
observation.


Regarding IMAP-UTF8 draft

- IMAP LANG will return language list in no specific order.

- IMAP LANG will not return 'default' in the language list.

- IMAP use ENABLE to manage mode switch -- no additional commands or
options to support partial UTF-8 header field or address capability.

- As a result, the UTF8 parameters were dropped from SELECT, EXAMINE,
LIST, LSUB, hence all of the related responses as well

- New text suggested dealing with text about transitions and
downgrading by concentrating the discussion into this draft (to be
referenced from the POP-UTF8 one) after as much text as possible has
been moved into the downgrade documents.  The idea of removing as
much transitional text as possible to the downgrade documents was to
avoid clutter once EAI capability is widely deployed.  Group at
interim meeting supported this approach and the general outline for
proposed text.


Regarding both downgrade drafts

- Neither downgrade drafts will update RFC5322, RFC3501

- Downgrade docs will not critique each other: the WG's conclusion is
that they may be appropriate under different circumstances and that
yet other circumstances may call for yet other approaches (such as
simply refusing to deliver an extended message to a legacy client).
The WG does not believe it would be productive to try to create a case
analysis of which techniques would be most appropriate under which
circumstances at least until some experience accumulates (and possibly
ever because the decisions may be determined by local operational
circumstances).

- There is no WG consensus to try to use ".invalid" email addresses in
the downgrade process.   A separate email will be sent to the WG
mailing list about this issue.

- Both downgrade drafts will publish as Proposed Standard, with PROTO write
up addressing the rationale.



Regarding approach to downgrade and empty group at "From:"

- A suggestion made about writing a 'mini-doc' that updates RFC 5322
and specifies the use of an empty group in "FROM:".  The suggestion
will be brought to the mailing list for further discussion even though
this WG is probably not the right place to process that specification.
If agreed, Barry Leiba and John Klensin will try for first rough
draft.


------

From barryleiba.mailing.lists@gmail.com  Wed Aug 22 16:56:39 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9D121F8653 for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 16:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.005
X-Spam-Level: 
X-Spam-Status: No, score=-103.005 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SrMfN-U5h165 for <ima@ietfa.amsl.com>; Wed, 22 Aug 2012 16:56:39 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id A2FC621F8648 for <ima@ietf.org>; Wed, 22 Aug 2012 16:56:38 -0700 (PDT)
Received: by lahm15 with SMTP id m15so93567lah.31 for <ima@ietf.org>; Wed, 22 Aug 2012 16:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hAcOZm11ryz9MtDLjxCOnhTHD2YuFmqklgsQvW4puS8=; b=zmGmY+sc7UtjmHmt0kfviXJnhBD6yO/d5noxUabweYcZSgFim7MS4g0AVTxpUBz9XR kfsNe0GxL/Z/dAI6vEW15JhQIhLhiA/+tDTuAW3R55YE9/o715XVvjIrydhhWdL6v3oH gOstfwGT5KUXBC3iPWle9+grvQnEigxUJ+L54xzcuvSrGlkxOJOX4nOUcORw3l6Rflc1 milv4qWb4/Ipd5Nr/DoxD67Hn3CHvRnJCS4MZKDxPZ6AXkbiGcOIDtA9cI/gGHRDfsfR sOSx551usha1I3/lTOQmTy3qiBlTsz8jOsMrQsO/d3Pl0SWg94yiCsTlz/PHVdArQco8 MKfA==
MIME-Version: 1.0
Received: by 10.112.10.198 with SMTP id k6mr10192158lbb.83.1345679797592; Wed, 22 Aug 2012 16:56:37 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.113.196 with HTTP; Wed, 22 Aug 2012 16:56:37 -0700 (PDT)
In-Reply-To: <CAF1dMVGfVPq=PBw4Pb7kjUPNm62F_7fw=PaXbc5648H8thJ73g@mail.gmail.com>
References: <CAF1dMVGfVPq=PBw4Pb7kjUPNm62F_7fw=PaXbc5648H8thJ73g@mail.gmail.com>
Date: Wed, 22 Aug 2012 19:56:37 -0400
X-Google-Sender-Auth: Coh-vK3ytWV8B3YZa91A2ZvVySk
Message-ID: <CAC4RtVCM1zMfONPP4ka+G8=hfC496m8=yuzrEqOhtY4==OTtBw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Joseph Yee <jyee@afilias.info>
Content-Type: multipart/alternative; boundary=e0cb4efe350251247a04c7e37ef4
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] EAI Consensus Call on mailto draft
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 23:56:39 -0000

--e0cb4efe350251247a04c7e37ef4
Content-Type: text/plain; charset=ISO-8859-1

Indeed; I do not see the energy nor interest to do it.  Let's not.

Barry, participant

On Wednesday, August 22, 2012, Joseph Yee wrote:

> All,
>
> Based on WG discussion at IETF84 (see minutes:
> http://www.ietf.org/proceedings/84/minutes/minutes-84-eai), there's a
> tentative agreement during meeting for EAI not to take on mailto
> draft.  The chairs are looking for broad consensus in the working
> group.
>
> Please use this thread for discussion.  The end date of discussion is
> August 29, 2012 20:00 UTC and consensus will be announced afterwards.
>
> Regards
> John & Joseph
> _______________________________________________
> IMA mailing list
> IMA@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/ima
>

--e0cb4efe350251247a04c7e37ef4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Indeed; I do not see the energy nor interest to do it. =A0Let&#39;s not.<di=
v><br></div><div>Barry, participant<span></span><br><br>On Wednesday, Augus=
t 22, 2012, Joseph Yee  wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
Based on WG discussion at IETF84 (see minutes:<br>
<a href=3D"http://www.ietf.org/proceedings/84/minutes/minutes-84-eai" targe=
t=3D"_blank">http://www.ietf.org/proceedings/84/minutes/minutes-84-eai</a>)=
, there&#39;s a<br>
tentative agreement during meeting for EAI not to take on mailto<br>
draft. =A0The chairs are looking for broad consensus in the working<br>
group.<br>
<br>
Please use this thread for discussion. =A0The end date of discussion is<br>
August 29, 2012 20:00 UTC and consensus will be announced afterwards.<br>
<br>
Regards<br>
John &amp; Joseph<br>
_______________________________________________<br>
IMA mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;IMA@ietf=
.org&#39;)">IMA@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ima" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/ima</a><br>
</blockquote></div>

--e0cb4efe350251247a04c7e37ef4--

From arnt@gulbrandsen.priv.no  Thu Aug 23 01:31:21 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8141D21F854A for <ima@ietfa.amsl.com>; Thu, 23 Aug 2012 01:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i9B7w1KDtn1R for <ima@ietfa.amsl.com>; Thu, 23 Aug 2012 01:31:21 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3FE21F8549 for <ima@ietf.org>; Thu, 23 Aug 2012 01:31:20 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 59675F8E82D; Thu, 23 Aug 2012 08:31:19 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1345710678-22818-22817/11/16; Thu, 23 Aug 2012 08:31:18 +0000
Message-Id: <5035EA55.60901@gulbrandsen.priv.no>
Date: Thu, 23 Aug 2012 10:31:17 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
Mime-Version: 1.0
To: ima@ietf.org
References: <CAF1dMVGfVPq=PBw4Pb7kjUPNm62F_7fw=PaXbc5648H8thJ73g@mail.gmail.com> <CAC4RtVCM1zMfONPP4ka+G8=hfC496m8=yuzrEqOhtY4==OTtBw@mail.gmail.com>
In-Reply-To: <CAC4RtVCM1zMfONPP4ka+G8=hfC496m8=yuzrEqOhtY4==OTtBw@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [EAI] EAI Consensus Call on mailto draft
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 08:31:21 -0000

I couldn't stomach spending effort on that draft, even though I know 
quite a bit about all the areas whoever listed during the WG meeting.

IMO, if the rules are too complex to be done in three lines of perl, 
they're too complex, because three lines of perl is what they'll get. 
Maybe four of there's example code in the draft. And the thought of 
fighting over complexity limits is... not very inspiring.

Arnt

From klensin@jck.com  Thu Aug 23 07:43:30 2012
Return-Path: <klensin@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE07D21F855D for <ima@ietfa.amsl.com>; Thu, 23 Aug 2012 07:43:29 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1hKpx74MGRY for <ima@ietfa.amsl.com>; Thu, 23 Aug 2012 07:43:29 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5B86521F8559 for <ima@ietf.org>; Thu, 23 Aug 2012 07:43:20 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1T4Ycw-000PBr-QR; Thu, 23 Aug 2012 10:43:18 -0400
Date: Thu, 23 Aug 2012 10:43:13 -0400
From: John C Klensin <klensin@jck.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ima@ietf.org
Message-ID: <ACF043A73F2E0A961256AADB@JcK-HP8200.jck.com>
In-Reply-To: <5035EA55.60901@gulbrandsen.priv.no>
References: <CAF1dMVGfVPq=PBw4Pb7kjUPNm62F_7fw=PaXbc5648H8thJ73g@mail.gmail.com> <CAC4RtVCM1zMfONPP4ka+G8=hfC496m8=yuzrEqOhtY4==OTtBw@mail.gmail.com> <5035EA55.60901@gulbrandsen.priv.no>
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] EAI Consensus Call on mailto draft
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 14:43:30 -0000

--On Thursday, August 23, 2012 10:31 +0200 Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:

> I couldn't stomach spending effort on that draft, even though
> I know quite a bit about all the areas whoever listed during
> the WG meeting.
> 
> IMO, if the rules are too complex to be done in three lines of
> perl, they're too complex, because three lines of perl is what
> they'll get. Maybe four of there's example code in the draft.
> And the thought of fighting over complexity limits is... not
> very inspiring.

Speaking personally only... your observation about complexity
exactly captures my feelings on the matter.

   john


From internet-drafts@ietf.org  Thu Aug 30 18:52:32 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CDE21F84F9; Thu, 30 Aug 2012 18:52:32 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLY6lpuk+YFi; Thu, 30 Aug 2012 18:52:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0FD921F84DF; Thu, 30 Aug 2012 18:52:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120831015231.27371.39742.idtracker@ietfa.amsl.com>
Date: Thu, 30 Aug 2012 18:52:31 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-5738bis-08.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2012 01:52:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : IMAP Support for UTF-8
	Author(s)       : Pete Resnick
                          Chris Newman
                          Sean Shen
	Filename        : draft-ietf-eai-5738bis-08.txt
	Pages           : 11
	Date            : 2012-08-30

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-5738bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-5738bis-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-5738bis-08


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


From internet-drafts@ietf.org  Thu Aug 30 20:40:30 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EEE711E80DE; Thu, 30 Aug 2012 20:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jbc5Yr2Pmxm6; Thu, 30 Aug 2012 20:40:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A9511E80EC; Thu, 30 Aug 2012 20:40:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120831034030.26098.87104.idtracker@ietfa.amsl.com>
Date: Thu, 30 Aug 2012 20:40:30 -0700
Cc: ima@ietf.org
Subject: [EAI] I-D Action: draft-ietf-eai-5738bis-09.txt
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2012 03:40:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Email Address Internationalization Workin=
g Group of the IETF.

	Title           : IMAP Support for UTF-8
	Author(s)       : Pete Resnick
                          Chris Newman
                          Sean Shen
	Filename        : draft-ietf-eai-5738bis-09.txt
	Pages           : 11
	Date            : 2012-08-30

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-5738bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-5738bis-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eai-5738bis-09


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

