Re: [hybi] Interface for Large Frames

"Thomson, Martin" <Martin.Thomson@commscope.com> Wed, 22 June 2011 23:15 UTC

Return-Path: <Martin.Thomson@commscope.com>
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 9298721F853B for <hybi@ietfa.amsl.com>; Wed, 22 Jun 2011 16:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 YTgsIMd1izND for <hybi@ietfa.amsl.com>; Wed, 22 Jun 2011 16:15:40 -0700 (PDT)
Received: from cdcsmgw01.commscope.com (fw.commscope.com [198.135.207.129]) by ietfa.amsl.com (Postfix) with ESMTP id 8669A21F8478 for <hybi@ietf.org>; Wed, 22 Jun 2011 16:15:40 -0700 (PDT)
X-AuditID: 0a0404e8-b7baaae0000009ea-5c-4e0277a743ad
Received: from ACDCE7HC1.commscope.com ( [10.86.20.102]) by cdcsmgw01.commscope.com (Symantec Brightmail Gateway) with SMTP id 1B.33.02538.7A7720E4; Wed, 22 Jun 2011 18:15:51 -0500 (CDT)
Received: from CDCE10HC1.commscope.com (10.86.20.21) by ACDCE7HC1.commscope.com (10.86.20.102) with Microsoft SMTP Server (TLS) id 8.3.159.2; Wed, 22 Jun 2011 18:15:56 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by CDCE10HC1.commscope.com (10.86.20.21) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 22 Jun 2011 16:15:36 -0700
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Thu, 23 Jun 2011 07:15:34 +0800
From: "Thomson, Martin" <Martin.Thomson@commscope.com>
To: Bob Gezelter <gezelter@rlgsc.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Thu, 23 Jun 2011 07:15:33 +0800
Thread-Topic: [hybi] Interface for Large Frames
Thread-Index: AcwxK438y/PQpV1OQaGo6VpGS5CCzwABiSqw
Message-ID: <8B0A9FCBB9832F43971E38010638454F040B26C35F@SISPE7MB1.commscope.com>
References: <20110622152637.ef1fc80126c74c6c202a919c41c7bb0b.727d09b396.wbe@email03.secureserver.net>
In-Reply-To: <20110622152637.ef1fc80126c74c6c202a919c41c7bb0b.727d09b396.wbe@email03.secureserver.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [hybi] Interface for Large Frames
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, 22 Jun 2011 23:15:41 -0000

On 2011-06-23 at 08:26:37, Bob Gezelter wrote:
> Andy and Willy,
> 
> Agreed. I just wanted to explicitly mention the critical efficiency 
> issue. Since frames can be extremely large, perhaps it would be 
> appropriate to designate a term for some sub-frame quantum to be 
> handled. Such a quantum (e.g., a segment) would be small enough to be 
> processed with reasonable resources.

Such a concept might be useful within an API, but the protocol can (and should) remain ignorant of such details.

To some extent, it depends on how capable you want your API to be.  I can easily imagine a simple API that passes frames whole and rejects frames larger than it wants to handle.  For a lot of applications, I imagine that this would be sufficient.  A generic API doesn't have that luxury, so I'll be interested to see how it is solved.

--Martin