Re: [EAI] UTF-8 in Message-IDs

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Thu, 06 October 2011 00:35 UTC

Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6136A1F0C41 for <ima@ietfa.amsl.com>; Wed, 5 Oct 2011 17:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.753
X-Spam-Level:
X-Spam-Status: No, score=-102.753 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VziSBWEnPJli for <ima@ietfa.amsl.com>; Wed, 5 Oct 2011 17:35:04 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id A5D8B1F0C36 for <ima@ietf.org>; Wed, 5 Oct 2011 17:35:03 -0700 (PDT)
Received: by wwf22 with SMTP id 22so2392113wwf.13 for <ima@ietf.org>; Wed, 05 Oct 2011 17:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=RtKWdi64jZOBZvqfOzKyg1//SbeyvZbNe87hq4cEfJY=; b=F8z0h/UQXYL7T+5IuqfWmQfov6sCjAWe2YwcVybh4y/21BlxS3opo8mmAjmcDTylqg ewkSF/UPx5oUN12q9KyisGUNRqT/hpUmnjaEhfiOhn27EUfUkz4ot0F5cB1zECzmDPSs Ig1Qjz5dpFyWWOdLg++Yuko7Ka9jRYsxPQyEU=
Received: by 10.216.137.104 with SMTP id x82mr275154wei.77.1317861491138; Wed, 05 Oct 2011 17:38:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.80.134 with HTTP; Wed, 5 Oct 2011 17:37:31 -0700 (PDT)
In-Reply-To: <4E8CDFE5.2040008@trigofacile.com>
References: <20111004014257.8027.qmail@joyce.lan> <op.v2viju2m6hl8nm@clerew.man.ac.uk> <34E8E4E5F1CBE344994E3F8B@PST.JCK.COM> <CAHhFybrr0jWaSMxHwnJ4NuKFBJRSzw423aYHnEmta8M+1=2+1Q@mail.gmail.com> <4E8CDFE5.2040008@trigofacile.com>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Thu, 6 Oct 2011 02:37:31 +0200
Message-ID: <CAHhFybq=oRabs248V0HY4QKsXkxQBrfaT+R3ZuTvqo=kJyYOsA@mail.gmail.com>
To: =?ISO-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IMA <ima@ietf.org>
Subject: Re: [EAI] UTF-8 in Message-IDs
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Thu, 06 Oct 2011 00:35:04 -0000

On 6 October 2011 00:53, Julien ÉLIE wrote:

>> The mailto: URLs are almost  ready for EAI, and the
>> news: URLs can be "fixed" by an erratum.

> Wouldn't it be proper to update the RFCs instead of
> adding an erratum?
> (which would probably be "held for document update")

> It is not an error; it is a technical update.

The EAI mailto: IRIs are documented in an existing I-D:
<http://tools.ietf.org/html/draft-duerst-eai-mailto-01>

news: IRIs are documented in 5538, modulo one erroneous
statement (if this WG gets its amended will in an IETF
Last Call.)  I'm not aware of "implementation reports"
or any other reasons justifying more work than a simple
"erratum":  The secrets of percent-encoding are already
covered by 3986 + 3987 + 5538.

Maybe if Usefor and/or NNTP are updated for EAI it could
make sense to work on a 5538bis.  But as long as Usenet
sticks to 5322/5536 Message-IDs that point is moot.

> Incidentally, we could try to do some work on USEAGE
> too, if Charles agrees.

Well, I'm willing to review drafts, IIRC there were some
pending IANA issues to be covered in USEAGE or "manually".

Otherwise I'm not much tempted by serious IETF work at
the moment, unless it is about 4408bis, 5321bis, 6068bis.

> I hope it will not split Usenet into two distinct
> "feeding areas":  the UTF-8-aware one (with UTF-8
> moderated newsgroup names, message-IDs, etc.) and the
> legacy one.

My best wishes for this hope,
 Frank