Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size

Francis Brosnan Blazquez <francis@aspl.es> Wed, 13 July 2011 11:39 UTC

Return-Path: <francis@aspl.es>
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 03A6421F86EE; Wed, 13 Jul 2011 04:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.713
X-Spam-Level: *
X-Spam-Status: No, score=1.713 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, HOST_MISMATCH_NET=0.311]
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 wwULTg-mAJLw; Wed, 13 Jul 2011 04:39:13 -0700 (PDT)
Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id 36F0621F85F4; Wed, 13 Jul 2011 04:39:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id 866111170002; Wed, 13 Jul 2011 13:39:10 +0200 (CEST)
X-Virus-Scanned: amavisd-new at aspl.es
Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJYwWvo1rEHq; Wed, 13 Jul 2011 13:39:10 +0200 (CEST)
Received: from [192.168.0.132] (barracuda [10.0.0.4]) by mail.aspl.es (Postfix) with ESMTP id 003AA1170001; Wed, 13 Jul 2011 13:39:09 +0200 (CEST)
From: Francis Brosnan Blazquez <francis@aspl.es>
To: Len Holgate <len.holgate@gmail.com>
In-Reply-To: <1bd101cc4136$01193390$0a00a8c0@Venus>
References: <20110711140229.17432.23519.idtracker@ietfa.amsl.com> <4E1BD054.7010103@gmail.com><1310480036.26452.329.camel@vulcan.aspl.local> <CAH_y2NF3pxbUJctg7P1qGNR+mvzaw80+Axh6kCYwx93HiQocug@mail.gmail.com> <1bd101cc4136$01193390$0a00a8c0@Venus>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: ASPL
Date: Wed, 13 Jul 2011 13:39:11 +0200
Message-ID: <1310557151.26452.1232.camel@vulcan.aspl.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-hybi-thewebsocketprotocol@tools.ietf.org, 'Hybi' <hybi@ietf.org>, ietf@ietf.org, 'Greg Wilkins' <gregw@intalio.com>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard: request for max frame size
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: Wed, 13 Jul 2011 11:39:14 -0000

Hi Len,

> I agree that this would be very useful. 
> 
> Would this be one frame size for both directions, or could it be specified
> in each direction? 

It should be done in both directions, assuming each party may have
different requirements..

> I'm a little wary of intermediaries being allowed to adjust this unless
> they're only allowed to reduce the amount...

My impression is that this max frame size value would help
intermediaries, and peers, to know how to fragment or coalesce
application level messages. Without such indication they are blind...