[Ltru] Re: Solving the UTF-8 problem

"Doug Ewell" <dewell@roadrunner.com> Wed, 04 July 2007 05:08 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5x6M-0003b9-GA; Wed, 04 Jul 2007 01:08:30 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I5x6L-0003aj-1l for ltru-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 01:08:29 -0400
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5x6K-0003ab-OU for ltru@ietf.org; Wed, 04 Jul 2007 01:08:28 -0400
Received: from mta9.adelphia.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5x68-0002vW-El for ltru@ietf.org; Wed, 04 Jul 2007 01:08:28 -0400
Received: from DGBP7M81 ([]) by mta9.adelphia.net (InterMail vM. 201-2131-123-102-20050715) with SMTP id <20070704050815.BLMO6326.mta9.adelphia.net@DGBP7M81>; Wed, 4 Jul 2007 01:08:15 -0400
Message-ID: <001901c7bdf9$53955370$6401a8c0@DGBP7M81>
From: Doug Ewell <dewell@roadrunner.com>
To: LTRU Working Group <ltru@ietf.org>, ietf-languages@iana.org
References: <E1I5koD-0003BE-4q@megatron.ietf.org>
Date: Tue, 03 Jul 2007 22:08:14 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [Ltru] Re: Solving the UTF-8 problem
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

John Cowan <cowan at ccil dot org> wrote:

> I still think the email argument is the compelling one.  We *will* 
> have corruption no matter what.

My suggestion is that we send new and changed records to IANA in UTF-8, 
as file attachments, possibly zipped or gzipped or wrapped in some other 
sort of binary armor to help protect against damage.  I'm not worried 
about that part; I haven't received a corrupted GIF or JPEG sent that 
way in 10 years.

The part I'm not sure about is convincing the list that the record 
submitted to IANA, in this high-security way, is the exact same as the 
one list members have agreed upon.  This is a bit touchy because of the 
two recent submissions whose Comments fields were altered before being 
sent to IANA.  I'm sure we can come up with a solution that will satisfy 
almost everyone; I'm just not sure what that solution will be.

Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14

Ltru mailing list