Re: [hybi] Is it important to know frame length at the start of frame? (was: Re: Discontinuation of mux ...)

Zhong Yu <zhong.j.yu@gmail.com> Mon, 24 February 2014 20:29 UTC

Return-Path: <zhong.j.yu@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2E01A02BB for <hybi@ietfa.amsl.com>; Mon, 24 Feb 2014 12:29:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20mzBtBMMqP4 for <hybi@ietfa.amsl.com>; Mon, 24 Feb 2014 12:29:05 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 642701A02A0 for <hybi@ietf.org>; Mon, 24 Feb 2014 12:29:05 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id va2so4594626obc.6 for <hybi@ietf.org>; Mon, 24 Feb 2014 12:29:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sA6C11eckZhD1bz4dCw1rAJMotrp5hh/GzcRq0jlsrs=; b=f2NibJcdnPI5vCdOlUIMYZhfsgprqen14WvS0X+ISPpgLMBN/C0CXJEP5/G3/Ymcgf WaJH2WsoeVTP4ImuX797zC0W08Ez4GnmSo74JFBPYkh7rse6tuH97OiRIEeVqfJSDP3A oG0xs+2cEwVKsrC7cAk5H+wcZfRsCLpY5obrlWVc468EsViHusaNW5mdYvo12aDawEw9 czE8vQLkPDhL+co/KUuRUshH3kA6D+HOMVcgoiE5EC33GTr+Jp4JsUxz0af64at12rO4 nSZj7kKhjzMny0I4LUgDjYyytcGYe3+RWQmdoRqUYRX1p/jYo0b/1TyKd8uQMx8gxhkF vzOg==
MIME-Version: 1.0
X-Received: by 10.60.70.142 with SMTP id m14mr9067617oeu.65.1393273744726; Mon, 24 Feb 2014 12:29:04 -0800 (PST)
Received: by 10.76.106.162 with HTTP; Mon, 24 Feb 2014 12:29:04 -0800 (PST)
In-Reply-To: <CAH9hSJY4NResx4DskJM8agd5ZXo9yHELYaXOpWG-xXK8P4+9zw@mail.gmail.com>
References: <CAH9hSJbf_ABT7ECL9eS=_ADrncX8qBtxZv=uLcdu9_6GUv23Uw@mail.gmail.com> <CACuKZqEcA1Pv8RpWfmThMjTzi2BbVMMKXqujs6BxVfxRPZJ9NQ@mail.gmail.com> <CAG4zZZCr4aTfVpw2coX2g0qw++4kdgNCFVze6tHKZ+fJNqb0aQ@mail.gmail.com> <CAG4zZZA4WR50Ea2e36XEgTgpJURwiMFn+DXeYuxHFfZatYzDOQ@mail.gmail.com> <CAH9hSJYv5VXGjS7AfG12-ArEvE6Uj_eE6pPxAiQcchcgV8vHcg@mail.gmail.com> <CAH9hSJbzra7uz7yfKQwfZaP_jhnxwdZyx8JnwCmBGhiMk6rbtg@mail.gmail.com> <CAG4zZZC1cmaH36znAvVLZE_MyJ+ThNk1Ky7tQ-QnKf_qwiQNDw@mail.gmail.com> <CAG4zZZB3h6TTFLUp-ucYQP7tMf-8=h5fh1UqufMh3w-0JN+hSw@mail.gmail.com> <CAH9hSJaeCrLjkhHUzaaGDw-apiSv-eaPZeYGEHBuwRoF3yPCOA@mail.gmail.com> <CAH9hSJY4NResx4DskJM8agd5ZXo9yHELYaXOpWG-xXK8P4+9zw@mail.gmail.com>
Date: Mon, 24 Feb 2014 14:29:04 -0600
Message-ID: <CACuKZqHTr0vufQr5mEHM2__NconW_d6jrzTpD0JKEzsiP09uwg@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/r6lAyXELEIsH7jE-tCcTyT-nBXw
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] Is it important to know frame length at the start of frame? (was: Re: Discontinuation of mux ...)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 24 Feb 2014 20:29:06 -0000

It there any problem if we mandate that 1 http frame corresponds to 1
ws frame, and 1 ws frame must reside in 1 http frame? What's the point
of supporting ws frames that need multiple http frames?

On Mon, Feb 24, 2014 at 12:28 PM, Takeshi Yoshino <tyoshino@google.com> wrote:
> Thanks all for your comments.
>
> First, please note that I wanted to discuss the question in the context of
> WS/HTTP/2.0 layering. Not about redesign of RFC 6455 itself.
>
> I asked this question since the length header is the biggest field when
> encoded into HTTP/2.0 HEADERS format. Whether we can eliminate it or not in
> WS/HTTP/2.0 is one of the most important points to evaluate the plans
> employing HTTP/2.0 HEADERS.
>
> Though the ranges the length headers represent differ (HTTP/2.0: 14 bit, WS
> length format: 63 bit), it seems everyone can live without a header of
> "original WebSocket frame size".
>
> Please reply to this post if you have any objection, but please don't write
> objection to use of HTTP/2.0 HEADERS itself in this thread.
>
> Thanks