Re: [hybi] hum #3: Message

Douglas Otis <dotis@mail-abuse.org> Thu, 05 August 2010 18:46 UTC

Return-Path: <dotis@mail-abuse.org>
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 9DC7F3A6B20 for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 11:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.337
X-Spam-Level:
X-Spam-Status: No, score=-106.337 tagged_above=-999 required=5 tests=[AWL=0.262, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 jgdcmJE5kSAl for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 11:46:32 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id AE9E83A6A74 for <hybi@ietf.org>; Thu, 5 Aug 2010 11:46:32 -0700 (PDT)
Received: from sjc-office-nat-210.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id ACD92A944D4 for <hybi@ietf.org>; Thu, 5 Aug 2010 18:46:59 +0000 (UTC)
Message-ID: <4C5B0723.9090406@mail-abuse.org>
Date: Thu, 05 Aug 2010 11:46:59 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: hybi@ietf.org
References: <4C5AE93D.4040803@ericsson.com> <Pine.LNX.4.64.1008051758290.5947@ps20323.dreamhostps.com> <AANLkTik0kbh14s2JZARY2MFh0iNGV7H+B4Px4yG+wX44@mail.gmail.com>
In-Reply-To: <AANLkTik0kbh14s2JZARY2MFh0iNGV7H+B4Px4yG+wX44@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 05 Aug 2010 18:46:33 -0000

On 8/5/10 11:42 AM, John Tamplin wrote:
> On Thu, Aug 5, 2010 at 2:22 PM, Ian Hickson <ian@hixie.ch 
> <mailto:ian@hixie.ch>> wrote:
>
>     When transfering large blocks of data, chunking is quite
>     inefficient. This
>     means that we'd need to make sure that the fixed width field is at
>     least
>     long enough to handle large chunks of data.
>
>     At terabit Ethernet speeds, 32 bits is not enough since you could
>     transfer
>     that much in mere seconds, so presumably we'll use 64 bits.
>
>     Do we really want a length that long?
>
>
> Let's assume the most recent proposal, which is a 4-byte header 
> including a 2-byte length field.  So, if you need to send a message of 
> 2^32 bytes, it will be sent as a 65538 frames, incurring an overhead 
> of 262152 bytes for header overhead, or a total of 4295229448 bytes 
> with .0006% overhead over the payload data.  It is true that this is 
> higher overhead than a single large frame with a variable-length 
> length field, but it hardly rises to "quite inefficient".  Also, other 
> reasons have been given for why you don't want to send a single frame 
> that long anyway, and for why you don't want to have to keep an 
> arbitrarily large buffer in the sender just so you can count the bytes 
> of the entire message before you send it.
+1

-Doug