Re: [hybi] hum #3: Message

Arman Djusupov <arman@noemax.com> Fri, 06 August 2010 14:58 UTC

Return-Path: <arman@noemax.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C12E3A68C5 for <hybi@core3.amsl.com>; Fri, 6 Aug 2010 07:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.462
X-Spam-Level:
X-Spam-Status: No, score=-2.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zd6bJM3prf3x for <hybi@core3.amsl.com>; Fri, 6 Aug 2010 07:58:47 -0700 (PDT)
Received: from mail.noemax.com (mail.noemax.com [64.34.201.8]) by core3.amsl.com (Postfix) with ESMTP id 2F6A43A6840 for <hybi@ietf.org>; Fri, 6 Aug 2010 07:58:47 -0700 (PDT)
Received: from [192.168.1.21] by mail.noemax.com (IceWarp 9.4.1) with ASMTP (SSL) id OWN67221; Fri, 06 Aug 2010 17:59:21 +0300
Message-ID: <4C5C2341.2000509@noemax.com>
Date: Fri, 06 Aug 2010 17:59:13 +0300
From: Arman Djusupov <arman@noemax.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: John Tamplin <jat@google.com>
References: <4C5AE93D.4040803@ericsson.com> <Pine.LNX.4.64.1008051758290.5947@ps20323.dreamhostps.com> <AANLkTik0kbh14s2JZARY2MFh0iNGV7H+B4Px4yG+wX44@mail.gmail.com> <71BCE4BF-D3F6-4F94-BE76-306BDF6A2E67@apple.com> <Pine.LNX.4.64.1008051930160.5947@ps20323.dreamhostps.com> <4C5B1695.6070704@gmx.de> <F8E2F702-9F74-4316-B3B2-D5A731409ABF@apple.com> <AANLkTin=gO9D8K5NVhqCRKki-jrDmTYqF-gBjp9X41GN@mail.gmail.com> <4C5BF15E.1090608@noemax.com> <AANLkTinXLPmBACd3ji0V9wkAWmxOR7qBMED19KKMvJrd@mail.gmail.com> <AANLkTi=RWdqDDgy24C6qtUSr+5R5p=P15B=+aUZuE16Q@mail.gmail.com> <4C5C07D6.1030208@noemax.com> <AANLkTimj9RvzL8E+FmH=vT_TeECVNmDPXY0ymPnvBHSZ@mail.gmail.com>
In-Reply-To: <AANLkTimj9RvzL8E+FmH=vT_TeECVNmDPXY0ymPnvBHSZ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] hum #3: Message
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 06 Aug 2010 14:58:48 -0000

John Tamplin wrote:
> Ok, does this summarize the various positions regarding chunking and
> lengths?
> 
> 
>    - We want to have a length of the complete message when it is available
>    to make buffer management simpler for the receiver
>    - We want to be able to fragment messages to avoid extra buffering when
>    the length of the entire message is not known up front, such as when sending
>    dynamic content, compressing frames, etc.
>    - We want to keep small frames having small overhead (though there is a
>    limit on how much this matters given TCP/IP overhead)
>    - We want to be able to send very large files in a single fragment so we
>    can just hand it off to sendfile or equivalent

Yes.

> What about the following:
> 
>    - 1 bit - Initial fragment
>    - 1 bit - Final fragment
>    - 1 bit - reserved
>    - 5 bits - opcode
>    - 8 bits - short length
>    - [if length = 255: 8 bytes - length]
>    - [if Initial = 1 and Final = 0: 8 bytes - overall message length, with 0
>    meaning "unknown"]
>    - length bytes of payload
> 
> This could be extended with any of the extension or padding proposals out
> there, just trying to get the basic idea of having initial/fragment bits
> with an optional overall message length up for discussion.  The length could
> be a variable-length integer as in v76 if you prefer, likewise for the
> message length.
> 

I would agree with such a proposal. 

Arman