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

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Mon, 15 August 2011 19:29 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 A68B411E80EB for <ima@ietfa.amsl.com>; Mon, 15 Aug 2011 12:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.671
X-Spam-Level:
X-Spam-Status: No, score=-102.671 tagged_above=-999 required=5 tests=[AWL=0.276, 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 eLx-cGYRuzDf for <ima@ietfa.amsl.com>; Mon, 15 Aug 2011 12:29:10 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2A72111E80D7 for <ima@ietf.org>; Mon, 15 Aug 2011 12:29:10 -0700 (PDT)
Received: by pzk33 with SMTP id 33so5728789pzk.18 for <ima@ietf.org>; Mon, 15 Aug 2011 12:29:56 -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; bh=4+vQdqDnnKAYY/OhCIMgxrDuWOCpE5Top/OCD31Uuf8=; b=UL0AVx7uTs5aLw0K8N2i/w3Vkmon21AxmsAHEgvheVuNJBumhNAhGOA7yaENPVDuMA GAQb9R+3iLqqgmnnzEMSjkQluYDhyyqOdBW8XvCGVTSrDjHI25rx7SnWVpgs64YloTva mMOhTRAKOFjTTvvwB/kjAF3p7/nrershN6UH4=
Received: by 10.142.169.7 with SMTP id r7mr461539wfe.13.1313436596200; Mon, 15 Aug 2011 12:29:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Mon, 15 Aug 2011 12:29:36 -0700 (PDT)
In-Reply-To: <20110815175214.4833.qmail@joyce.lan>
References: <C31E821E731AC23ED7EE191F@PST.JCK.COM> <20110815175214.4833.qmail@joyce.lan>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Mon, 15 Aug 2011 21:29:36 +0200
Message-ID: <CAHhFybo9PxBHehzTxkwj+-bCNvGcc0A66vnhbXOJi3AssMOPdw@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Mon, 15 Aug 2011 19:29:10 -0000

On 15 August 2011 19:52, John Levine <johnl@taugh.com> wrote:

> I find the most compelling argument the one that there'll be UTF-8 in
> message-ID's no matter what we say, so let's not specify something
> that we expect implementors to get wrong.

Why do you all say that implementors will get this simple point wrong,
while you expect them to get far more convoluted syntax details right?

I don't see anything "compelling" in that line of reasoning, otherwise
we could also say that using 8bit in DNS queries works, and therefore
it's okay to use UTF-8 in host names (example).  Bugs in new apps can
be fixed, but limitations in old apps will never go away (until nobody
uses such old apps anymore).

-Frank