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

"Charles Lindsey" <chl@clerew.man.ac.uk> Mon, 04 August 2008 11:10 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 505E13A69A4; Mon, 4 Aug 2008 04:10:54 -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 9D0EB3A69A4 for <ima@core3.amsl.com>; Mon, 4 Aug 2008 04:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.088
X-Spam-Level:
X-Spam-Status: No, score=-3.088 tagged_above=-999 required=5 tests=[AWL=-0.489, 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 lCXMgnencB7G for <ima@core3.amsl.com>; Mon, 4 Aug 2008 04:10:51 -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 C25043A692C for <ima@ietf.org>; Mon, 4 Aug 2008 04:10:50 -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 4896e39e.1903.25 for ima@ietf.org; Mon, 4 Aug 2008 12:10:22 +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 m74BAIH8026195 for <ima@ietf.org>; Mon, 4 Aug 2008 12:10:22 +0100 (BST)
Date: Mon, 04 Aug 2008 12:10:18 +0100
To: IMA <ima@ietf.org>
From: Charles Lindsey <chl@clerew.man.ac.uk>
MIME-Version: 1.0
References: <p06240609c4b3aaea35c0@[130.129.20.99]> <6.0.0.20.2.20080730151421.0847dc08@localhost> <g6pb4f$mi3$1@ger.gmane.org> <op.ue5h8sha6hl8nm@clerew.man.ac.uk> <g6smit$cmn$1@ger.gmane.org>
Message-ID: <op.ufczzgfa6hl8nm@clerew.man.ac.uk>
In-Reply-To: <g6smit$cmn$1@ger.gmane.org>
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 Thu, 31 Jul 2008 16:44:35 +0100, Frank Ellermann  
<hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> wrote:

> Charles Lindsey wrote:
>
>> What we would want to write is
>>    Archived-At: <http://archive.mañana.com>
>> which is an IRI (using UTF-8, as always with IRIs)
>
> JFTR, s/as always with IRIs/as always with EAI/
>
> EAI always uses UTF-8, while IRIs can be in any charset
> determined by the context.  And for EAI that context is
> of course UTF-8.  But in a KOI8-R document it's KOI8-R:

Not quite. It the IRI appears in a document written in KO18-R, then:
1. You convert the KO18-R into unicode
2. You convert the unicode into UTF-8
3. You %-encode the UTF-8
4. Now you have the proper URI

Of course if the context is headers within a UTF8SMTP message, then steps  
1 and 2 are redundant.

>> which, upon conversion to a URI, would simply %-encode
>> that 'ñ'.
>
> For an <ipath>, <iquery>, or an <ifragment>.  But your
> example has the ñ in the <ihost>, and there you would
> use IDNA(bis) rules to convert this into an URL:
>
> Archived-At: <http://archive.xn--maana-pta.com/>

RFC 3987 says you MAY (possibily even SHOULD) convert to punycode in this  
case, but you also MAY just %-encode it and hope whatever comes next knows  
how to punycode it before doing any DNS lookup.

OTOH, IRIs are not currently allowed in the 'http' scheme, so it would  
need an explicit EAI extension (plus downgrade) to permit the Archived-At  
header field to use IRIs. Likewise for any List-* header fields.

Likewise for the 'mailto' scheme unless and until mailto-bis tells us  
otherwise. I think we really need Martin to publish a mailto-bis draft  
before we can proceed much further with List-* headers.

> Mailto-bis IRIs on a KOI8-R page would be interesting:
>
> If they are transformed to UTF-8 (the first step in a
> IRI to URI conversion) they might work with EAI UTF-8.

The rule is clear that you first apply the 4 steps I gave above. before  
you try interpreting them further.

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