Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard

Mykyta Yevstifeyev <evnikita2@gmail.com> Wed, 13 July 2011 02:38 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3770F21F877A for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 19:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.502
X-Spam-Level:
X-Spam-Status: No, score=-3.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 r5psDxZYngTN for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 19:38:25 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFA821F8762 for <hybi@ietf.org>; Tue, 12 Jul 2011 19:38:25 -0700 (PDT)
Received: by fxe4 with SMTP id 4so6959899fxe.27 for <hybi@ietf.org>; Tue, 12 Jul 2011 19:38:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ijiWVKU24q5/1yIcarQDNOlqSAdIpIbhYr//zL/Mo14=; b=Uie/sW/vL08FNy1IFAaOWCbphycFFDxpYLQbef5Ikkak0trDEK0sF5naSkMdpigaal JCeWF3/eu1Ijgq0ZbeWOkde+nfDr/nzKFjKZT9UoKy0qQfrC1qo1faDgunb4/mRGnYJ5 vjuArzT5ErzooNjDF0sR8brjlPYzK5oh2sdcU=
Received: by 10.223.54.90 with SMTP id p26mr928130fag.44.1310524701992; Tue, 12 Jul 2011 19:38:21 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id u20sm8098123fac.18.2011.07.12.19.38.19 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 19:38:20 -0700 (PDT)
Message-ID: <4E1D0549.2040900@gmail.com>
Date: Wed, 13 Jul 2011 05:39:05 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Thomson, Martin" <Martin.Thomson@commscope.com>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <8B0A9FCBB9832F43971E38010638454F040B419E9E@SISPE7MB1.commscope.com> <4E1C0CE9.10009@gmail.com> <8B0A9FCBB9832F43971E38010638454F040B419F6D@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F040B419F6D@SISPE7MB1.commscope.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 12 Jul 2011 21:04:06 -0700
Cc: "hybi@ietf.org" <hybi@ietf.org>, "draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org" <draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 13 Jul 2011 02:38:26 -0000

13.07.2011 2:39, Thomson, Martin wrote:
> On 2011-07-12 at 18:59:21, Mykyta Yevstifeyev wrote:
>> ABNF is designed to deal with characters represented in octets.
> Not true again.  ABNF has terminal values that are both characters and numeric.  A character mapping (e.g. ASCII, Unicode) can be used to map one to the other.
No, you're probably misunderstanding RFC 5234.  Everything after 
"%x/d/b" is treated as hexadecimal, decimal or binary representation of 
a particular ASCII/Unicode character, note vice versa.
>
>     Rules resolve into a string of terminal values, sometimes called
>     characters.  In ABNF, a character is merely a non-negative integer.
>
> i.e.,
> %xHH is a number
> "a" is a character that is mapped to a number using the selected character mapping (Unicode, ASCII)
No, a number is mapped to the character, which is implied by the 
aforementioned statement.
>
> The number or non-negative integer is the terminal value.  That number might then be encoded using the encoding (UTF-8, ASCII), but that's not interesting to ABNF.
>
> If you want, you can define the terminal value to be a number of 1-bit size.
How?  ASCII values are hex 00-7F, all 1 octet.  What we currently find 
in the draft like %h0 means the ASCII hexadecimal character 00, NUL, not 
bit 0.  %b0 will mean ASCII binary character 00000000, NUL, too.  So 
it's incorrect that ABNF is suitable for mapping its definitions to bits.

Mykyta
>    The string literal can either have no meaning at all, since the strings are ASCII [1].  Then you end up with a 1-bit terminal value which is trivially encoded.
>
> --Martin
>
> [1] Alternatively, a string literal could be redefined to map "0" to 0 and "1" to 1 with all other values invalid - ABNF isn't a law or anything.
>
>
>