Re: [hybi] US-ASCII vs. ASCII in Web Socket Protocol

Julian Reschke <julian.reschke@gmx.de> Tue, 02 February 2010 07:46 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA1533A6AC7 for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 23:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.184
X-Spam-Level:
X-Spam-Status: No, score=-4.184 tagged_above=-999 required=5 tests=[AWL=-1.585, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2G4Smw+xHqTe for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 23:46:50 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 845DA3A6AB8 for <hybi@ietf.org>; Mon, 1 Feb 2010 23:46:49 -0800 (PST)
Received: (qmail invoked by alias); 02 Feb 2010 07:47:22 -0000
Received: from p508FC2DE.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.194.222] by mail.gmx.net (mp002) with SMTP; 02 Feb 2010 08:47:22 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/XKdQ+cZnX9a9ywzoYnpaNwPaNjOl5zajVu6wavS Nm6K7XgFzd+7V6
Message-ID: <4B67D87F.60401@gmx.de>
Date: Tue, 02 Feb 2010 08:47:11 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <9124e09b0911052218y5106a2d4qcda01ff67577679b@mail.gmail.com> <Pine.LNX.4.62.0912032337580.15540@hixie.dreamhostps.com> <4B1905FC.1000205@verizon.net> <Pine.LNX.4.64.1001300901270.22027@ps20323.dreamhostps.com> <4B6466EB.2090909@gmx.de> <4B656465.1080005@airemix.jp> <Pine.LNX.4.64.1002020027000.3846@ps20323.dreamhostps.com> <6.2.5.6.2.20100201163955.09373f40@resistor.net> <Pine.LNX.4.64.1002020055080.21600@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1002020055080.21600@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.59999999999999998
Cc: hybi@ietf.org
Subject: Re: [hybi] US-ASCII vs. ASCII in Web Socket Protocol
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 07:46:50 -0000

Ian Hickson wrote:
> On Mon, 1 Feb 2010, SM wrote:
>> At 16:30 01-02-10, Ian Hickson wrote:
>>> I used "ANSI_X3.4-1968" because that's the canonical name for US-ASCII,
>>> and I used RFC1345 because that's the canonical reference. If you disagree
>>> with these choices, please update the IANA registry.
>> Julian Reschke is correct; RFC 1345 should not be used as a normative 
>> reference.  Please use the reference that he suggested 
>> ([ANSI.X3-4.1986]).
> 
> Again, I'm just using what the IANA uses. If the IANA's reference is out 
> of date, then please update the IANA registry. I've no intention of 
> playing reference hot potato, where every 3 months the "best reference" 
> changes and I have to update all the references.
> 
> RFC1345 works fine as a reference for the purposes of the Web Socket 
> spec, anyway.

RFC 1345 never was the "best reference"; actually, as far as I can tell, 
it never has been used as a normative reference for US-ASCII in *any* RFC.

BR, Julian