Re: [EAI] Deciding what to do with IRIs in List-* headers

fujiwara@jprs.co.jp Wed, 20 August 2008 08:47 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 342743A6ADB; Wed, 20 Aug 2008 01:47:20 -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 1C3363A6ADB for <ima@core3.amsl.com>; Wed, 20 Aug 2008 01:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 KKJ7f6NzS+rX for <ima@core3.amsl.com>; Wed, 20 Aug 2008 01:47:17 -0700 (PDT)
Received: from send01.jprs.co.jp (send01.jprs.co.jp [202.11.17.113]) by core3.amsl.com (Postfix) with ESMTP id 29EFA3A6920 for <ima@ietf.org>; Wed, 20 Aug 2008 01:47:16 -0700 (PDT)
Received: from send01.jprs.co.jp (localhost [127.0.0.1]) by send01.jprs.co.jp (8.12.10+Sun/8.12.11) with SMTP id m7K8knho014542; Wed, 20 Aug 2008 17:47:02 +0900 (JST)
Received: (from localhost [172.18.4.53]) by send01.jprs.co.jp (SMSSMTP 4.0.4.64) with SMTP id M2008082017470126222 ; Wed, 20 Aug 2008 17:47:01 +0900
Date: Wed, 20 Aug 2008 17:47:01 +0900
Message-Id: <20080820.174701.226800747.fujiwara@jprs.co.jp>
To: harald@alvestrand.no
From: fujiwara@jprs.co.jp
In-Reply-To: <48AA7A2C.8000908@alvestrand.no> <48AB2B86.5060605@alvestrand.no>
References: <48AA7A2C.8000908@alvestrand.no>
X-Mailer: Mew version 6.1 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: ima@ietf.org
Subject: Re: [EAI] Deciding what to do with IRIs in List-* headers
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org

> From: Harald Alvestrand <harald@alvestrand.no>
> at our Dublin meeting, the issue of how to handle headers with URLs that contain non-ASCII characters (that is, they are IRIs in an URI slot) came up - in the context of List-* headers.
> 
> I see two possible ways forward:
> 
> 1 - Don't address the issue at this time. Let such headers be turned into Downgraded-* headers, effectively hidden from the user's MUA. Add a comment that this will happen. This is the fastest path to getting -downgrade submitted.
> 
> 2 - Add a new mechanism to -downgrade section 5

Does draft-ietf-eai-utf8headers-12 allow IRIs in List-* header fields ?

If "no", option 1 
If "yes", option 2

> From: Harald Tveit Alvestrand <harald@alvestrand.no>
> By the time we can have a new mailto: spec out, I'm afraid that there will already be an installed base that doesn't do IRI->URI downconversion on these headers, and we may have UAs that expect the Downgraded-List-* headers.

Current EAI document sets are in EXPERIMENTAL,
there are no such problems, I think.

Regards,

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima