IETF Logo Mail Archive

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

"Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Wed, 30 July 2008 09:09 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 37D6C3A6B9C; Wed, 30 Jul 2008 02:09:56 -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 F286E28C1A1 for <ima@core3.amsl.com>; Wed, 30 Jul 2008 02:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.289
X-Spam-Level:
X-Spam-Status: No, score=-0.289 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=3.196, RCVD_IN_DNSWL_LOW=-1]
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 NSjlOFI5EXSK for <ima@core3.amsl.com>; Wed, 30 Jul 2008 02:09:54 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 3B74328C1C1 for <ima@ietf.org>; Wed, 30 Jul 2008 02:09:39 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KO7go-0002uP-Ux for ima@ietf.org; Wed, 30 Jul 2008 09:09:47 +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>; Wed, 30 Jul 2008 09:09:46 +0000
Received: from hmdmhdfmhdjmzdtjmzdtzktdkztdjz by rain.gmane.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ima@ietf.org>; Wed, 30 Jul 2008 09:09:46 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ima@ietf.org
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Wed, 30 Jul 2008 11:10:47 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 15
Message-ID: <g6pb4f$mi3$1@ger.gmane.org>
References: <p06240609c4b3aaea35c0@[130.129.20.99]> <6.0.0.20.2.20080730151421.0847dc08@localhost>
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org

Martin Duerst wrote:

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

Not at this time, let's wait until the dust of IDNAbis and EAI
settles.  BCP 9 mumbles something about "six months", but IMO
an RFC 5064 promotion can wait until EAI, 2822upd, and IDNAbis
catch up.

 Frank

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

v2.23.0 | Report a Bug | By Email