Re: [EAI] UTF-8 in Message-IDs

"Charles Lindsey" <chl@clerew.man.ac.uk> Wed, 05 October 2011 10:08 UTC

Return-Path: <chl@clerew.man.ac.uk>
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 020C921F8B51 for <ima@ietfa.amsl.com>; Wed, 5 Oct 2011 03:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.129
X-Spam-Level:
X-Spam-Status: No, score=-4.129 tagged_above=-999 required=5 tests=[AWL=-0.682, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 RjrJe7olFFeR for <ima@ietfa.amsl.com>; Wed, 5 Oct 2011 03:08:02 -0700 (PDT)
Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by ietfa.amsl.com (Postfix) with ESMTP id 1687921F8B0F for <ima@ietf.org>; Wed, 5 Oct 2011 03:08:01 -0700 (PDT)
Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 605AE2223F for <ima@ietf.org>; Wed, 5 Oct 2011 11:11:07 +0100 (BST)
Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Wed, 05 Oct 2011 11:11:06 +0100
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id p95AAXHY000605 for <ima@ietf.org>; Wed, 5 Oct 2011 11:11:06 +0100 (BST)
Date: Wed, 05 Oct 2011 11:10:32 +0100
To: IMA <ima@ietf.org>
From: Charles Lindsey <chl@clerew.man.ac.uk>
Content-Type: text/plain; format="flowed"; delsp="yes"; charset="iso-8859-1"
MIME-Version: 1.0
References: <20111004014257.8027.qmail@joyce.lan>
Content-Transfer-Encoding: 8bit
Message-ID: <op.v2viju2m6hl8nm@clerew.man.ac.uk>
In-Reply-To: <20111004014257.8027.qmail@joyce.lan>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4e8c2d3a.11cc7-63c0-2
X-Gradwell-Auth-Method: mailbox
X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk
Subject: Re: [EAI] UTF-8 in Message-IDs
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, 05 Oct 2011 10:08:04 -0000

On Tue, 04 Oct 2011 02:42:57 +0100, John Levine <johnl@taugh.com> wrote:

>>> If then, as is likely, they start to appear, then we will see how they
>>> cope and decide how best to regulate them in a future standard.
>>
>> Meanwhile, the propagation of such articles will be very bad.
>
> News servers aren't going to be thrilled about messages with
> unencoded UTF-8 in other headers, either.
>
> They'll have to upgrade to handle EAI, just like mail servers will.  I
> suppose we might want to invent some new NNTP verb that lets hosts
> tell each other whether they can accept EAI messages, but this is most
> definitely not the current EAI group's problem.

No they won't. User agents will have to be upgraded if people want to read  
the utf-8 stuff, or to reply by mail to articles From: people with utf-8  
addresses. But the existing servers will handle all this just fine except  
insofar as they might be rejecting (unnecessarily) utf-8 in some headers  
where it did not matter.

Servers will expect to be able to compare Message-IDs for equality by a  
simple octet-by-octet comparison, and they will expect Dates to be  
comparable (<,=,>), but I don't think EAI has changed that. Even Newsgroup  
names with utf-8 in them will work, as has alredy been demonstrated on the  
existing network, (so long as octet-by-octet comparison works, which means  
some severe normalization).

As to whether it is any of this WG's business, it is certainly NOT the  
business of this WG to put obstacles in the way of other mail-like  
protocols which might want to follow the EAI path.

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