Re: [hybi] frame length encoding

"Shelby Moore" <shelby@coolpage.com> Sun, 22 August 2010 21:13 UTC

Return-Path: <shelby@coolpage.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 00B043A6954 for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 14:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.208
X-Spam-Level:
X-Spam-Status: No, score=-2.208 tagged_above=-999 required=5 tests=[AWL=0.391, 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 hE6Ext79mPIk for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 14:13:49 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id 9FF273A68A5 for <hybi@ietf.org>; Sun, 22 Aug 2010 14:13:49 -0700 (PDT)
Received: (qmail 64929 invoked by uid 65534); 22 Aug 2010 21:14:22 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Sun, 22 Aug 2010 17:14:22 -0400
Message-ID: <ef16e51dbbd45c735d21ce310063cf36.squirrel@sm.webmail.pair.com>
In-Reply-To: <AANLkTin=urXr0eAg3mrXfnCm5jQDb6yLSpkF-QLNQYq+@mail.gmail.com>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <20ef7ed5e135c57c1ee5a741658b9d98.squirrel@sm.webmail.pair.com> <1282423311.2014.6.camel@tng> <224b9ed365bd78fd5e316b8cb5f3f837.squirrel@sm.webmail.pair.com> <1282435214.2014.14.camel@tng> <AANLkTimo0MwZEMn1t1vrASfwC1bx82Q9Z_Ls3wVb-zUS@mail.gmail.com> <b95f074b65875865802f532bb5668ff2.squirrel@sm.webmail.pair.com> <AANLkTi=AXLFPSASV2zkBiUU=1StO=YSrKq_9AZ2ZnVHy@mail.gmail.com> <8cd6ecfebb4a073ecf94c8e1aa56e642.squirrel@sm.webmail.pair.com> <77aecf89c6c8673f1b999f80fa04e005.squirrel@sm.webmail.pair.com> <AANLkTik9tpCQr9LjK0qdLuA1KfJv1MN9yK2UZ1ytxfCW@mail.gmail.com> <fb8bfae1b88ade55cad4234af724004b.squirrel@sm.webmail.pair.com> <AANLkTimAu5de0PnujHRwR0nnXFBpqdJoRWZ=UvGrLVJ7@mail.gmail.com> <65fc5176b7cc6c775ec167f4404b43ed.squirrel@sm.webmail.pair.com> <bf7fd641553e15431d35d7352d023df2.squirrel@sm.webmail.pair.com> <AANLkTin=urXr0eAg3mrXfnCm5jQDb6yLSpkF-QLNQYq+@mail.gmail.com>
Date: Sun, 22 Aug 2010 17:14:22 -0400
From: Shelby Moore <shelby@coolpage.com>
To: John Tamplin <jat@google.com>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
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: Sun, 22 Aug 2010 21:13:51 -0000

> On Sun, Aug 22, 2010 at 1:54 PM, Shelby Moore <shelby@coolpage.com> wrote:
>
>> I meant in the case where maximum size had been negotiated to 15-bits.
>>
>
>>
> Of course Option 1/15-bit would still support 8 byte size when the maximum
>> size was negotiated to larger than 32767.
>>
>
> I don't think it would be a good idea to have the interpretation of the
> framing itself vary depending on the handshake.  I realize it could work,
> but I would prefer that if the field is a 15-bit length then it always
> means
> that, not with a special case of 7FFF meaning an extra 8-byte length field
> is present, but only when the negotiated maximum frame size was greater
> than
> 32766.
>
> If people are complaining about the complexity of the existing proposals,
> I
> would hate to hear them after this.
>
> Also, it effectively ties defining the framing to defining the handshake,
> since you cannot properly interpret a frame without knowing the handshake.


So then the maximum size from the handshake is not a maximum size and the
other end can violate it.

I can really hear the complaining from that.  "What the maximum size is
not a maximum size, it is just a mild suggestion?!?!"