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

Mykyta Yevstifeyev <evnikita2@gmail.com> Tue, 12 July 2011 09:24 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 00B2621F9108 for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 02:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.351
X-Spam-Level:
X-Spam-Status: No, score=-3.351 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 yuPl+jLB-tDM for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 02:24:04 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 99EFF21F9129 for <hybi@ietf.org>; Tue, 12 Jul 2011 02:24:03 -0700 (PDT)
Received: by bwb17 with SMTP id 17so4546207bwb.31 for <hybi@ietf.org>; Tue, 12 Jul 2011 02:24:02 -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=R1dVH4rGI4wj64hqKTpgwuWwqDifNpa/h37VFSI0aY4=; b=beYp0Sf9MPq9fUFFS+e9JqJoBdp3MHybQuBWai966L6Jo037OkLaeX07Hip4QamdLF 0hluNSUTG7sfr0kxeZ5FCmzJbe4q5CBdP0YcRxPO3gBqlvwaskE9PibhSxiLbfsYgTVv R4snLHGdYMI5+uRCYD53/2PoBHRBy3boChuEA=
Received: by 10.205.83.140 with SMTP id ag12mr1875487bkc.336.1310462642723; Tue, 12 Jul 2011 02:24:02 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id f16sm1297957bke.37.2011.07.12.02.24.00 (version=SSLv3 cipher=OTHER); Tue, 12 Jul 2011 02:24:01 -0700 (PDT)
Message-ID: <4E1C12DE.9060703@gmail.com>
Date: Tue, 12 Jul 2011 12:24:46 +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: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com> <8B0A9FCBB9832F43971E38010638454F040B419E9E@SISPE7MB1.commscope.com> <4E1C0CE9.10009@gmail.com> <CALiegf=22nxQTZKBTrJnjt+u_OYQX-hknzqQOE4v0GeUKJuDUw@mail.gmail.com>
In-Reply-To: <CALiegf=22nxQTZKBTrJnjt+u_OYQX-hknzqQOE4v0GeUKJuDUw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 12 Jul 2011 02:24:46 -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: Tue, 12 Jul 2011 09:24:05 -0000

12.07.2011 12:20, Iñaki Baz Castillo wrote:
> 2011/7/12 Mykyta Yevstifeyev<evnikita2@gmail.com>om>:
>>> That's not true.  RFC 5234 merely uses ASCII in its example.  The terminal
>>> values for this particular application of ABNF could be a single bit in
>>> place of a character.  5234 doesn't prohibit this
>> ABNF is designed to deal with characters represented in octets.  The
>> terminal value %xHH stands for ASCII character HH, so it's true that %x0
>> stands for NUL; so does %b0.  The<BIT>  production doesn't denote actual
>> bits, but rather representation of bits.
>>
>>> BIT            =  "0" / "1"
>> implies that<BIT>  may be either ASCII 0x31 - "1" - or ASCII 0x30 - "0".
>>   Once more, ABNF is for chars/octets, not bits.
>
> Just a comment: RFC 5234 (ABNF) says:
>
>    BIT            =  "0" / "1"
>
>     bin-val        =  "b" 1*BIT
>                          [ 1*("." 1*BIT) / ("-" 1*BIT) ]
>                             ; series of concatenated bit values
>                             ;  or single ONEOF range
>
>
> Is it speaking about real bits? or about ones and zeroes (chars)?
Chars. See Section 2.3 of RFC 5234 on p. 5:

>     ABNF permits the specification of literal text strings directly,
>     enclosed in quotation marks.

<bin-val> denotes the value of ASCII char in binary form.  Eg, 
%b01100011 stands for "c" (see RFC 20).

Mykyta
>