[EAI] UTF-8 in Message-IDs

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Sat, 13 August 2011 20:23 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 77C2C21F86C3 for <ima@ietfa.amsl.com>; Sat, 13 Aug 2011 13:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.654
X-Spam-Level:
X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=0.293, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, 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 yx26CnMs3VxM for <ima@ietfa.amsl.com>; Sat, 13 Aug 2011 13:23:02 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id E624C21F86BF for <ima@ietf.org>; Sat, 13 Aug 2011 13:23:01 -0700 (PDT)
Received: by yxp4 with SMTP id 4so3044065yxp.31 for <ima@ietf.org>; Sat, 13 Aug 2011 13:23:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=Ga4o4yAat2azVYjvp6SlYHaF1s9OoLzuezIRuKzziMQ=; b=d00+59dzsM2Z+GkBh2B86BKTjiRLJYBz3TlemrN6ZVFOKSw8JHyDYckZxWNfptC681 ZB/J3RT5BxbRg6RSz0lwsR7KGzgSZnWc2NFpwrJGRZoWerDqlvdfsX8cGsHgTK2Xr3rc d+3k/dCdZWhFq6taeCTw/hwQlqAYeNzziEe+M=
Received: by 10.143.21.4 with SMTP id y4mr994463wfi.48.1313267022075; Sat, 13 Aug 2011 13:23:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.157.2 with HTTP; Sat, 13 Aug 2011 13:23:22 -0700 (PDT)
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 13 Aug 2011 22:23:22 +0200
Message-ID: <CAHhFybo47--0YjCRcvSO4asoV_R89+ULDB3tyij+ba=O_6gKsQ@mail.gmail.com>
To: ima@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [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: Sat, 13 Aug 2011 20:23:02 -0000

Hi,

looking for something else (= state of the art wrt EAI
and SPF) yesterday I stumbled over the "81 IETF EAI
meeting minutes" in the mailing list archive, with a
note about "UTF-8 in Message-IDs".

That was certainly (bad) news from my POV, and whining
about it off list I got the tip that waiting for an
IETF Last Call is a bad plan when this could be also
addressed before WG Last Call.

>From my POV the "globally unique forever Message-ID"
in mail and news is in essence an early form of what
is now a GUID/UUID in other protocols.  Maybe a bit
more so, in theory there could be UUID collisions,
and that's not possible for Message-IDs (in theory).

This theory is relevant for NetNews, gateways from or
to NetNews, mail and news threading, APOP, and likely
other use cases I'm not aware of.

Nobody would say replace hex. by UTF-8 in GUID/UUIDs,
therefore I fail to see the point of trying something
in this direction in Message-IDs.  Gateway operators
stating that UTF-8 in Message-IDs would be no problem
in practise, or that this would be only a minor point
when they adopt EAI, might convince me that I'm only
paranoid, but I doubt it.

And the "EAI experiment" phase did not test this plan,
there's no evidence I'm aware of that UTF-8 in Message-
IDs is harmless.  Did you really check all RFCs using
or mentioning Message-IDs for potential side-effects
of introducing UTF-8 in the "local", "unique", "left"
etc. part of a Message-ID?  E.g., does it fly with the
Message-ID concept in APOP and CRAM-MD5, or do you
intend something in the direction of "updates 2195"
to make it work?

-Frank