Re: Volunteer needed to serve as IANA charset reviewer

Ned Freed <ned.freed@mrochek.com> Thu, 07 September 2006 00:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL8DZ-0003sC-L9; Wed, 06 Sep 2006 20:58:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GL8DY-0003ru-Ia for discuss@apps.ietf.org; Wed, 06 Sep 2006 20:58:08 -0400
Received: from [206.117.180.234] (helo=mauve.mrochek.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GL8AH-00005i-2F for discuss@apps.ietf.org; Wed, 06 Sep 2006 20:54:46 -0400
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01M6VTGROUB400OH84@mauve.mrochek.com> for discuss@apps.ietf.org; Wed, 6 Sep 2006 17:54:22 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01M6VIKB0I6O0008CX@mauve.mrochek.com>; Wed, 06 Sep 2006 17:54:11 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Message-id: <01M6VTGKMA620008CX@mauve.mrochek.com>
Date: Wed, 06 Sep 2006 15:58:19 -0700
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Volunteer needed to serve as IANA charset reviewer
In-reply-to: "Your message dated Wed, 06 Sep 2006 17:45:58 -0400" <20060906174558.ff156501.moore@cs.utk.edu>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <p06240600c124bdb12d16@[10.0.1.2]> <BDA09F0B9086491428F8F2FC@p3.JCK.COM> <01M6VLE70BJ60008CX@mauve.mrochek.com> <20060906174558.ff156501.moore@cs.utk.edu>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: hardie@qualcomm.com, Ned Freed <ned.freed@mrochek.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.

Any such assistance would be hugely welcome. As an aside, it would also be nice
if more people would post comments to the list...

> 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.

This is pretty much where I'm at as well. I have no problem with UTF-16 or
UTF-32 if there is a compelling reason to allow them, but I really want to at
least try and close the door to additional CESes to the greatest extent
possible. Of course this is really an issue for the IAB and not the charset
reviewer - thank goodness.

				Ned