Re: [hybi] I-D ACTION:draft-ietf-hybi-thewebsocketprotocol-08.txt

Norio Kobota <norio.kobota@jp.sony.com> Thu, 09 June 2011 10:18 UTC

Return-Path: <Norio.Kobota@jp.sony.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 9EA4211E80E8 for <hybi@ietfa.amsl.com>; Thu, 9 Jun 2011 03:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.292
X-Spam-Level:
X-Spam-Status: No, score=-0.292 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 OSHW3RFGrptA for <hybi@ietfa.amsl.com>; Thu, 9 Jun 2011 03:18:00 -0700 (PDT)
Received: from ms5.sony.co.jp (ms5.sony.co.jp [IPv6:2001:cf8:0:56::201]) by ietfa.amsl.com (Postfix) with ESMTP id 4F34811E80B5 for <hybi@ietf.org>; Thu, 9 Jun 2011 03:17:58 -0700 (PDT)
Received: from mta6.sony.co.jp (mta6.sony.co.jp [137.153.71.9]) by ms5.sony.co.jp (R8/Sony) with ESMTP id p59AHsjs000810 for <hybi@ietf.org>; Thu, 9 Jun 2011 19:17:54 +0900 (JST)
Received: from mta6.sony.co.jp (localhost [127.0.0.1]) by mta6.sony.co.jp (R8/Sony) with ESMTP id p59AHren025143 for <hybi@ietf.org>; Thu, 9 Jun 2011 19:17:53 +0900 (JST)
Received: from jptkyxbh102.jp.sony.com ([43.15.31.4]) by mta6.sony.co.jp (R8/Sony) with ESMTP id p59AHr9K025102 for <hybi@ietf.org>; Thu, 9 Jun 2011 19:17:53 +0900 (JST)
Received: from jptkyxim101.jp.sony.com ([43.15.31.5]) by jptkyxbh102.jp.sony.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 9 Jun 2011 19:17:46 +0900
Received: from [43.0.235.115] ([43.0.235.115]) by jptkyxim101.jp.sony.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 9 Jun 2011 19:17:46 +0900
Message-ID: <4DF09DC7.306@jp.sony.com>
Date: Thu, 09 Jun 2011 19:17:43 +0900
From: Norio Kobota <norio.kobota@jp.sony.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Takeshi Yoshino <tyoshino@google.com>
References: <20110608173012.14596.50398.idtracker@ietfa.amsl.com> <4DF07883.4070609@warmcat.com> <BANLkTimQn-6AbRrk_2FWOZ7WS1fSRu=9Ag@mail.gmail.com> <4DF0923D.3070005@jp.sony.com> <BANLkTinq4e5cQWc+eAPcn3A6ZCgfA4pGWYOdxQ=j78jzA7EZqg@mail.gmail.com>
In-Reply-To: <BANLkTinq4e5cQWc+eAPcn3A6ZCgfA4pGWYOdxQ=j78jzA7EZqg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jun 2011 10:17:46.0060 (UTC) FILETIME=[79FAE8C0:01CC268E]
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D ACTION:draft-ietf-hybi-thewebsocketprotocol-08.txt
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: Thu, 09 Jun 2011 10:18:02 -0000

Thanks!

(2011/06/09 19:06), Takeshi Yoshino wrote:
> On Thu, Jun 9, 2011 at 18:28, Norio Kobota <norio.kobota@jp.sony.com
> <mailto:norio.kobota@jp.sony.com>> wrote:
>
>      > - The extended payload length may now use 64 bits (instead of
>     just 63).
>
>     The figure at section 4.2 shows Extended payload length(16/63).
>     But in text, payload length is 7+64 bits.(MSB==0)
>
>
> Values written after each field in Section 4.2 are the number of bits
> each field occupies. Extended payload field occupies 64 bits but still
> can hold only value <= 0x7fffffffffffffff.
>
> It may be a bit confusing that the diagram is using 63 instead of actual
> field length of 64.
>
>     Am I correct though I understood as follows?
>
>     1.extended payload length 'field' has 64 bit length.
>
>
> yes
>
>     2.but most significant bit must be 0.
>
>
> yes
>
>     3.so, the max size of extended payload length is equal to
>       INT64_MAX(0x7fffffffffffffffLL)
>
>
> yes
>