IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Sat, 30 January 2010 17:05 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 92EB23A6833 for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 09:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.574
X-Spam-Level:
X-Spam-Status: No, score=-4.574 tagged_above=-999 required=5 tests=[AWL=-1.975, 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 Lc7uC8ARqW7H for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 09:05:35 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 3D6793A67EB for <hybi@ietf.org>; Sat, 30 Jan 2010 09:05:34 -0800 (PST)
Received: (qmail invoked by alias); 30 Jan 2010 17:05:59 -0000
Received: from p508FF969.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.249.105] by mail.gmx.net (mp016) with SMTP; 30 Jan 2010 18:05:59 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX185I5Eyglg5dxJDPYcpL0Y1IkK5zNyqdd/tUz2xav uT31lYdajH7zKo
Message-ID: <4B6466EB.2090909@gmx.de>
Date: Sat, 30 Jan 2010 18:05:47 +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>
In-Reply-To: <Pine.LNX.4.64.1001300901270.22027@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.56000000000000005
Cc: WHATWG <whatwg@lists.whatwg.org>, "hybi@ietf.org" <hybi@ietf.org>, WeBMartians <webmartians@verizon.net>
Subject: Re: [hybi] [whatwg] 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: Sat, 30 Jan 2010 17:05:36 -0000

Ian Hickson wrote:
> On Fri, 4 Dec 2009, WeBMartians wrote:
>> Hmmm... Maybe it would be better to say ISO-646US rather than ASCII. 
>> There is a lot of impreciseness about the very low value characters 
>> (less than 0x20 space) in the ASCII "specifications." The same can be 
>> said about the higher end.
> 
> Where the interpretation was normative, I've used the term "ANSI_X3.4-1968 
> (US-ASCII)" and referenced RFC1345.

I think you just lost both readability and precision.

Please keep saying "ASCII" or "US-ASCII", and then have a reference to 
the ANSI or ISO spec that actually defines ASCII, such as

    [ANSI.X3-4.1986]  American National Standards Institute, "Coded
                      Character Set - 7-bit American Standard Code for
                      Information Interchange", ANSI X3.4, 1986.

(taken from the relatively recent RFC 5322).

RFC 1345 is a non-maintained, historic informational RFC that's nit 
really a good definition for ASCII. If you disagree, please name a 
single RFC that has been published in the last 20 years that uses RFC 
1345 to reference ASCII (I just searched, and couldn't find any).

Best regards, Julian

v2.23.0 | Report a Bug | By Email