Re: [apps-discuss] Documenting UTF-1 as Historic

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 13 June 2011 07:08 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DEA11E808D for <apps-discuss@ietfa.amsl.com>; Mon, 13 Jun 2011 00:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.79
X-Spam-Level:
X-Spam-Status: No, score=-99.79 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtSxclPSMYEl for <apps-discuss@ietfa.amsl.com>; Mon, 13 Jun 2011 00:08:54 -0700 (PDT)
Received: from acintmta01.acbb.aoyama.ac.jp (acintmta01.acbb.aoyama.ac.jp [133.2.20.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9D84F228011 for <apps-discuss@ietf.org>; Mon, 13 Jun 2011 00:08:53 -0700 (PDT)
Received: from acmse02.acbb.aoyama.ac.jp ([133.2.20.226]) by acintmta01.acbb.aoyama.ac.jp (secret/secret) with SMTP id p5D78nZv016736 for <apps-discuss@ietf.org>; Mon, 13 Jun 2011 16:08:49 +0900
Received: from (unknown [133.2.206.133]) by acmse02.acbb.aoyama.ac.jp with smtp id 6c7f_34ff_fc987cd6_958b_11e0_9751_001d0969ab06; Mon, 13 Jun 2011 16:08:49 +0900
Received: from [IPv6:::1] ([133.2.210.5]:49306) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S151B557> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 13 Jun 2011 16:08:46 +0900
Message-ID: <4DF5B770.50407@it.aoyama.ac.jp>
Date: Mon, 13 Jun 2011 16:08:32 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
References: <4DF23976.4080301@gmail.com>
In-Reply-To: <4DF23976.4080301@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-discuss list <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Documenting UTF-1 as Historic
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 07:08:55 -0000

I agree with what others have said, and will stay short (and 
unfortunately a bit blunt):

UTF-1, like most UTF-X (where X isn't 8/16/32, and maybe also 7) are 
totally irrelevant. Spending time on such stuff is just wasteful. The 
'historic' description is to relabel stuff that was in an RFC without a 
'historic' label. That doesn't apply to UTF-1. UTF-1 is in the IANA 
charset registry (http://www.iana.org/assignments/character-sets), but 
so are several others that are completely useless, too. Enough said.

Regards,   Martin.

On 2011/06/11 0:34, Mykyta Yevstifeyev wrote:
> Hello,
>
> There are a number of RFCs defining transformation formats of ISO
> 10646/Unicode - various UTFs. I mean RFC 3629 (UTF-8), RFC 2152 (UTF-7),
> RFC 2781 (UTF-16) and others. However, I've noticed UTF-1 isn't properly
> documented (or, at least, there is no formal record of it). However,
> since UTF-1 has never been widely used, I suppose it could be formally
> documented in Historic RFC, taking
> http://www.itscj.ipsj.or.jp/ISO-IR/178.pdf as a basis. Any thoughts on
> this?
>
> Mykyta Yevstifeyev
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>