Re: Volunteer needed to serve as IANA charset reviewer

Keith Moore <moore@cs.utk.edu> Wed, 06 September 2006 22:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL60a-0000zC-Cj; Wed, 06 Sep 2006 18:36:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL60Z-0000xp-PF for discuss@apps.ietf.org; Wed, 06 Sep 2006 18:36:35 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GL60X-0001v9-Hk for discuss@apps.ietf.org; Wed, 06 Sep 2006 18:36:35 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 271A056452; Wed, 6 Sep 2006 17:43:55 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hcDWQhEeb2yp; Wed, 6 Sep 2006 17:43:52 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43]) by shu.cs.utk.edu (Postfix) with ESMTP id ED64D56415; Wed, 6 Sep 2006 17:43:37 -0400 (EDT)
Date: Wed, 06 Sep 2006 17:45:58 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Volunteer needed to serve as IANA charset reviewer
Message-Id: <20060906174558.ff156501.moore@cs.utk.edu>
In-Reply-To: <01M6VLE70BJ60008CX@mauve.mrochek.com>
References: <p06240600c124bdb12d16@[10.0.1.2]> <BDA09F0B9086491428F8F2FC@p3.JCK.COM> <01M6VLE70BJ60008CX@mauve.mrochek.com>
X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: hardie@qualcomm.com, ietf-charsets@iana.org, discuss@apps.ietf.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

I concur with the need to maintain the current charset registry to
support legacy apps that use it.  

And I think Ned would be an excellent choice for reviewer, though it
wouldn' t bother me if he could have the assistance of people with
specialized expertise in Asian writing schemes.

As for utf-8 vs. Unicode, this is a bit tricky.  I agree that merely
specifying Unicode isn't sufficient given the potential for
incompatible CESs.  And yet I'm sympathetic to the notion that UTF-8
pessimizes storage and transmission of text written in certain
languages.  IMHO it's unreasonable to exclude the potential for a
Unicode based CES that has more-or-less equivalent information
density across a wide variety of languages.  But I do think that use of
multiple CESs in a new protocol should require substantial
justification, and that UTF-8 should be presumed to be the CES of
choice for any new protocol that requires ASCII compatibility for its
character representation.

Keith