Re: Volunteer needed to serve as IANA charset reviewer

Tim Bray <tbray@textuality.com> Wed, 06 September 2006 20:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL3ci-0001lW-7N; Wed, 06 Sep 2006 16:03:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL3ch-0001lR-8r for discuss@apps.ietf.org; Wed, 06 Sep 2006 16:03:47 -0400
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GL3cb-0003fi-Qb for discuss@apps.ietf.org; Wed, 06 Sep 2006 16:03:47 -0400
Received: from fe-amer-01.sun.com ([192.18.108.175]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k86K3f61016768 for <discuss@apps.ietf.org>; Wed, 6 Sep 2006 14:03:41 -0600 (MDT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J5600501SHCU400@mail-amer.sun.com> (original mail from tbray@textuality.com) for discuss@apps.ietf.org; Wed, 06 Sep 2006 14:03:41 -0600 (MDT)
Received: from [192.168.1.15] ([216.113.204.64]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J5600IUWT0IX731@mail-amer.sun.com>; Wed, 06 Sep 2006 14:03:41 -0600 (MDT)
Date: Wed, 06 Sep 2006 13:04:17 -0700
From: Tim Bray <tbray@textuality.com>
Subject: Re: Volunteer needed to serve as IANA charset reviewer
In-reply-to: <BDA09F0B9086491428F8F2FC@p3.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
Message-id: <5D2B3F79-EFD6-4847-ABC1-EE8401759437@textuality.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.752.2)
Content-type: text/plain; format="flowed"; delsp="yes"; charset="US-ASCII"
Content-transfer-encoding: 7bit
References: <p06240600c124bdb12d16@[10.0.1.2]> <BDA09F0B9086491428F8F2FC@p3.JCK.COM>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Ted Hardie <hardie@qualcomm.com>, discuss@apps.ietf.org, ietf-charsets@iana.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

On Sep 6, 2006, at 11:45 AM, John C Klensin wrote:

> I wonder if we
> are reaching the point at which a stronger "use Unicode on the
> wire" recommendation would be in order.   The implications of
> such a recommendation would presumably include a 2978bis that
> made the requirements for registration of a new charset _much_
> tougher, e.g., requiring a demonstration that the then-current
> version of Unicode cannot do the relevant job and/or evidence
> that the newly-proposed charset is needed in deployed
> applications.

Yes, please.  Unicode is not perfect, but it's actually very good in  
quite a few different ways, and network effects have pretty well  
taken over, so if you're doing any text on the network at all, it's  
almost certainly the right thing to use Unicode.

As a Certified Unicode Bigot(tm) I would volunteer to help with such  
a redraft.

  -Tim