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

"Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Thu, 31 July 2008 15:44 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 9DEB93A68A2; Thu, 31 Jul 2008 08:44:00 -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 5AD1A3A6949 for <ima@core3.amsl.com>; Thu, 31 Jul 2008 08:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.528
X-Spam-Level: *
X-Spam-Status: No, score=1.528 tagged_above=-999 required=5 tests=[AWL=-1.739, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=3.196, HTTP_ESCAPED_HOST=0.134, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_URI_LHOST30=1.666, URIBL_GREY=0.25, URI_NOVOWEL=1.62]
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 QyyZjpuEmUnF for <ima@core3.amsl.com>; Thu, 31 Jul 2008 08:43:58 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 6AD173A6A97 for <ima@ietf.org>; Thu, 31 Jul 2008 08:43:58 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KOaJU-0006HJ-Qf for ima@ietf.org; Thu, 31 Jul 2008 15:43:37 +0000
Received: from rain.gmane.org ([80.91.229.7]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ima@ietf.org>; Thu, 31 Jul 2008 15:43:36 +0000
Received: from hmdmhdfmhdjmzdtjmzdtzktdkztdjz by rain.gmane.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ima@ietf.org>; Thu, 31 Jul 2008 15:43:36 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ima@ietf.org
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Thu, 31 Jul 2008 17:44:35 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 64
Message-ID: <g6smit$cmn$1@ger.gmane.org>
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>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: rain.gmane.org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
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-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org

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:

http://hmdmhdfmhdjmzdtjmzdtzktdkztdjz.googlepages.com/IDN-IRI-koi8-r.html

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

Extended by some Message-ID, as Archived-At gives you
the location per message, not only some archive URL.

Nobody (maybe except some XML and LEIRI geeks) has the
faintest idea what a <http://archive.ma%C3%b1ana.com/>
might be.  It is a "syntactically valid" URL in some
non-DNS parallel universe I don't care about, but it
is not produced by following RFC 3987 rules.

Excluding XML LEIRI abominations unrelated to a "real"
world as defined by DNS, Googlebot, and W3C validator.

> IDNAbis/whoever clarifies the matter. They might well
> decree that valid URIs for that purpose have to be in
> punycode

IDNAbis won't touch URIs with a stick.  The IRI to URI
rules are in RFC 3987, and that uses IDNA for <ihost>:
No percent characters in labels of host names, percent
is not LDH.

> mailto-bis is more likely to be whatever Martin 
> proposes, and we are in a better position to lean on  
> Martin :-) 

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.

But if they are transformed to a mailto-bis URL they
might not more work, neither EAI nor 2822upd.

Mailto-bis is very near to hopeless, I'd be delighted
if it at least manages all STD 66 and 2822upd hurdles,
ignoring additional mailto-i18n obstacles.

 Frank
-- 
<http://omniplex.blogspot.com/2008/07/html5-asinine-selfish.html>

_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima