Re: [hybi] Framing take IV

Greg Wilkins <gregw@webtide.com> Wed, 04 August 2010 01:07 UTC

Return-Path: <gregw@webtide.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 D4AA83A68DE for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 18:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 dkVgv-VAfHWu for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 18:07:23 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 9E9F03A6908 for <hybi@ietf.org>; Tue, 3 Aug 2010 18:07:22 -0700 (PDT)
Received: by fxm16 with SMTP id 16so1457670fxm.31 for <hybi@ietf.org>; Tue, 03 Aug 2010 18:07:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.121.147 with SMTP id h19mr8075186far.76.1280884070925; Tue, 03 Aug 2010 18:07:50 -0700 (PDT)
Received: by 10.223.57.12 with HTTP; Tue, 3 Aug 2010 18:07:50 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com>
Date: Wed, 04 Aug 2010 11:07:50 +1000
Message-ID: <AANLkTi=3CJDKu37LV+6CG=d7VP5fOe-JNV9Cd=99BjjA@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary="001636c5bb4b0bc732048cf51079"
Cc: hybi@ietf.org
Subject: Re: [hybi] Framing take IV
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: Wed, 04 Aug 2010 01:07:24 -0000

On 4 August 2010 10:53, Ian Hickson <ian@hixie.ch> wrote:

> On Wed, 4 Aug 2010, Greg Wilkins wrote:
> >
> > I think that we have reasonable consensus on something like:
> >
> >   +--------------------------------------------------+
> >   | frag(1) |unused(3) | opcode(4) |  Length(16)     |
> >   +--------------------------------------------------+
> >   |                      Data                        |
> >   +--------------------------------------------------+
>
> Why would we have a fixed length field with fragmentation rather than a
> variable length field?
>
> If we can have a variable width length field, do we need to support
> fragmentation in the first version? I could see an argument for supporting
> fragmentation in the case of multiplexing, but without that it doesn't
> seem to actually gain us anything.
>
>
Ian,

at the f2f there was a very loud hum for a single framing mechanism.
Following that, there were loud hums for fragmentation and fixed length
frames, even without consideration of multiplexing.

I believe the feeling was that fragmentation makes sending and receiving big
messages simpler.  It also prepares the ground for multiplexing extensions.
There was very little support for variable length lengths, as that was just
seen as more complex than fragmentation.

But if you have a counter proposal that meets the single framing hum, then
please post it.

cheers