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

Takeshi Yoshino <tyoshino@google.com> Thu, 09 June 2011 10:06 UTC

Return-Path: <tyoshino@google.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 7721011E80BD for <hybi@ietfa.amsl.com>; Thu, 9 Jun 2011 03:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.1
X-Spam-Level:
X-Spam-Status: No, score=-105.1 tagged_above=-999 required=5 tests=[AWL=0.877, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 uEQx-pN6wxkI for <hybi@ietfa.amsl.com>; Thu, 9 Jun 2011 03:06:37 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id B168511E80B1 for <hybi@ietf.org>; Thu, 9 Jun 2011 03:06:37 -0700 (PDT)
Received: from kpbe19.cbf.corp.google.com (kpbe19.cbf.corp.google.com [172.25.105.83]) by smtp-out.google.com with ESMTP id p59A6auK008353 for <hybi@ietf.org>; Thu, 9 Jun 2011 03:06:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307613996; bh=cMrtunPtJ44UxYg2r+cDZGkGFiY=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=ezMDEMzMVPlMuom0tdyZvw7vNyI/9fSC/qGzc5QK+EyILJoVQ5bxKZNUbuxUE9ahf 1vDMbi5wOuaSVwB9W/3LA==
Received: from yib18 (yib18.prod.google.com [10.243.65.82]) by kpbe19.cbf.corp.google.com with ESMTP id p59A6YNH017466 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Thu, 9 Jun 2011 03:06:35 -0700
Received: by yib18 with SMTP id 18so1048242yib.31 for <hybi@ietf.org>; Thu, 09 Jun 2011 03:06:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tVGvi1k6ilwZ6wpJSXHpEFBTpOTtYJKvRAhw6XG17Cw=; b=t1yQ9nUZQK53m8WpezqcnVKfsm2liPms8mwpKEEt74wuxv4+OKdoOq+rusbvmHeZJl qSU98+RBgxXFNJ4ST/2g==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=TKlYEK4/LRcaLaXbWbm4dNNp6EnS+J862evnAlxvZLKQa4PXie5SFp0wnyoVfy3xQk 3Q+mD1S6AZwTMT+WOAPA==
Received: by 10.91.33.27 with SMTP id l27mr1793852agj.136.1307613994595; Thu, 09 Jun 2011 03:06:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.218.9 with HTTP; Thu, 9 Jun 2011 03:06:13 -0700 (PDT)
In-Reply-To: <4DF0923D.3070005@jp.sony.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>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 9 Jun 2011 19:06:13 +0900
Message-ID: <BANLkTinq4e5cQWc+eAPcn3A6ZCgfA4pGWYOdxQ=j78jzA7EZqg@mail.gmail.com>
To: Norio Kobota <norio.kobota@jp.sony.com>
Content-Type: multipart/alternative; boundary=0016e640cbfea6b4a904a5449bbd
X-System-Of-Record: true
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:06:38 -0000

On Thu, Jun 9, 2011 at 18:28, Norio Kobota <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