Re: [EAI] Proposed resolution of List-* and downgrade- Issues
Martin Duerst <duerst@it.aoyama.ac.jp> Wed, 30 July 2008 06:27 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 A33BC3A6AA1; Tue, 29 Jul 2008 23:27:43 -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 467D83A6867 for <ima@core3.amsl.com>; Tue, 29 Jul 2008 23:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.262
X-Spam-Level: **
X-Spam-Status: No, score=2.262 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_23=0.6, SARE_FWDLOOK=1.666]
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 UjoQRMYl9weH for <ima@core3.amsl.com>; Tue, 29 Jul 2008 23:27:41 -0700 (PDT)
Received: from scmailgw2.scop.aoyama.ac.jp (scmailgw2.scop.aoyama.ac.jp [133.2.251.195]) by core3.amsl.com (Postfix) with ESMTP id 3403E3A69F7 for <ima@ietf.org>; Tue, 29 Jul 2008 23:27:40 -0700 (PDT)
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw2.scop.aoyama.ac.jp (secret/secret) with SMTP id m6U6RsDN014930 for <ima@ietf.org>; Wed, 30 Jul 2008 15:27:54 +0900 (JST)
Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp id 6886_a481ee94_5e00_11dd_960d_0014221fa3c9; Wed, 30 Jul 2008 15:27:54 +0900
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:50684) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S2B8755> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 30 Jul 2008 15:21:42 +0900
Message-Id: <6.0.0.20.2.20080730151421.0847dc08@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Wed, 30 Jul 2008 15:18:15 +0900
To: Randall Gellens <randy@qualcomm.com>, ima@ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
In-Reply-To: <p06240609c4b3aaea35c0@[130.129.20.99]>
References: <p06240609c4b3aaea35c0@[130.129.20.99]>
Mime-Version: 1.0
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org
For the Archived-At header, defined in http://www.ietf.org/rfc/rfc5064.txt, which is related to list headers but somewhat different because it indicates per-message archival location, I took a forward-looking approach and included this: 2.4. Syntax Extension for Internationalized Message Headers There are some efforts to allow non-ASCII text directly in message header field bodies. In such contexts, the URI non-terminal in the syntax defined in Section 2.1 is to be replaced by an Internationalized Resource Identifier (IRI) as defined in [RFC3987]. The specifics of the actual octet encoding of the IRI will follow the rules for general direct encoding of non-ASCII text. For conversion between IRIs and URIs, the procedures defined in [RFC3987] are to be applied. My understanding is that this is enough for people to figure out that with EAI, they can use IRIs (encoded in UTF-8) in the Archived-At header(s) of EAI messages. If somebody thinks that's not enough, and a revision of RFC 5064 is needed, please tell me. Regards, Martin. At 02:34 08/07/29, Randall Gellens 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. > >This is accomplished by creating a new WG document for 2369-bis to extend List-* headers to "permit UTF8 whenever UTF8 is otherwise permitted in header fields". There isn't a need to do more than adding this one sentence to the existing 2369, I think. So hopefully it will be very simple to produce. We need to be very clear that, as 2369-bis is being done by EAI, its scope is strictly limited to permitting UTF8 and not to any other changes that anyone might desire in 2369. > >A preference is for List-ID to be considered special and remain ASCII (same as Message-ID). 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. > >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). > >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. > >---------------------------------------------- >New text in -framework-bis: > >New versions of List-* headers are also defined, which permit native UTF8. > >---------------------------------------------- >-utf8headers: > >My suggestion is to create an I-D for utf8headers-bis which adds >List-* headers, and keep it around as an I-D for when we go to >standards track. > >-- >Randall Gellens >Opinions are personal; facts are suspect; I speak for myself only >-------------- Randomly-selected tag: --------------- >Nobody can be exactly like me. Even I have trouble doing it. > --Tallulah Bankhead >_______________________________________________ >IMA mailing list >IMA@ietf.org >https://www.ietf.org/mailman/listinfo/ima #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp _______________________________________________ IMA mailing list IMA@ietf.org https://www.ietf.org/mailman/listinfo/ima
- [EAI] Proposed resolution of List-* and downgrade… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Martin Duerst
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey