Re: [EAI] Proposed resolution of List-* and downgrade- Issues

"Charles Lindsey" <chl@clerew.man.ac.uk> Tue, 29 July 2008 09:41 UTC

Return-Path: <ima-bounces@ietf.org>
X-Original-To: ima-archive@megatron.ietf.org
Delivered-To: ietfarch-ima-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8687D28C23A; Tue, 29 Jul 2008 02:41:45 -0700 (PDT)
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74ED028C23A for <ima@core3.amsl.com>; Tue, 29 Jul 2008 02:41:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.344
X-Spam-Level:
X-Spam-Status: No, score=-3.344 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mv0vCXY63CVA for <ima@core3.amsl.com>; Tue, 29 Jul 2008 02:41:43 -0700 (PDT)
Received: from v-smtp-auth-relay-4.gradwell.net (v-smtp-auth-relay-4.gradwell.net [79.135.125.43]) by core3.amsl.com (Postfix) with ESMTP id CAA4F28C1F1 for <ima@ietf.org>; Tue, 29 Jul 2008 02:41:42 -0700 (PDT)
Received: from [80.175.135.89] ([80.175.135.89] helo=clerew.man.ac.uk country=GB ident=postmaster&pop3&clerew^man$ac$uk) by v-smtp-auth-relay-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.290) id 488ee5e1.2f46.3bb for ima@ietf.org; Tue, 29 Jul 2008 10:41:53 +0100 (envelope-sender <chl@clerew.man.ac.uk>)
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 m6T9foxY027222 for <ima@ietf.org>; Tue, 29 Jul 2008 10:41:52 +0100 (BST)
Date: Tue, 29 Jul 2008 10:41:50 +0100
To: IMA <ima@ietf.org>
From: Charles Lindsey <chl@clerew.man.ac.uk>
MIME-Version: 1.0
References: <p06240609c4b3aaea35c0@[130.129.20.99]>
Message-ID: <op.ue1rv0sn6hl8nm@clerew.man.ac.uk>
In-Reply-To: <p06240609c4b3aaea35c0@[130.129.20.99]>
User-Agent: Opera Mail/9.25 (SunOS)
Subject: Re: [EAI] Proposed resolution of List-* and downgrade- Issues
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org

On Mon, 28 Jul 2008 18:34:57 +0100, Randall Gellens <randy@qualcomm.com>  
wrote:

> ----------------------------------------------
> Proposed resolution of "List-*" headers:
>
> EAI to define new versions of List-* headers which can have unencoded  
> UTF8 values. This is just a trivial revision of the current forms. Like  
> the current forms, each header can have multiple IRI, URL, URL, etc.   
> Note that this is orthogonal to new "mailto" -- when mailto-bis is  
> ready, it just drops in as any other scheme such as HTTP.

But is that not equivalent to just saying that IRIs are to be permitted  
(within the UTF8SMTP universe) in places where URIs are currently allowed?

And if it is not equivalent, then why cannot it be made so?

> A preference is for List-ID to be considered special and remain ASCII  
> (same as Message-ID).

Agreed.

> ... There is an open question on internationalized domain names: since  
> these are used in Sieve scripts, users need to be able to type them in.

Ah! So if we have
    List-Post: <mailto:list@mañana.com>
(which is presumably an IRI), then is the corresponding URI just a  
%-encoding of "mañana", or is it a punycode thereof? Actually, I think we  
have to wait for mailto-bis to answer this question, because mailto-bis  
might well allow something of the form
    List-Post: <mailto:list@mañana.com<list@manana.com>>
(i.e. and Alt address).
>
> Note that allowing UTF8 in List-* headers is equivalent to allowing UTF8  
> in address headers.  Presumably, only EAI-aware clients will see either.
>
> ----------------------------------------------
> New text in -downgrade:
>
> List-* headers which contain native UTF8 should be copied into
> Downgrade-List-* and the UTF8 IRI should be dropped (alternate:
> encoded per IRI).

No! Don't drop it. Downgrade it to a URI, and let mailto-bis sort out the  
result.
>
> Add informative reference to new 2369-bis draft along the lines of  
> "Since [2369-bis] permits UTF8 in List-* headers, which are vital to  
> user's experience of mailing lists, this document needs to specify how  
> such headers are to be downgraded and remain valid."
>
> ----------------------------------------------
> New text in -mailinglist:
>
> Where available, mailing lists SHOULD include an ASCII form of List-*  
> headers as well as a UTF8 form. Because these headers are vital to good  
> operations and use of mailing lists, special rules are defined in  
> [downgrade] so that such headers are not stripped during downgrade, but  
> are preserved with working values whenever possible.

Having invented alt-addresses for use elsewhere within EAI, let us stick  
with them here. The last thing we want is two mechanisms for achieving the  
same result.

-- 
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
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima