Return-path: Received: from mail-pz0-f42.google.com ([209.85.210.42]:54671 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220Ab1I1AOr (ORCPT ); Tue, 27 Sep 2011 20:14:47 -0400 Received: by pzk1 with SMTP id 1so18877403pzk.1 for ; Tue, 27 Sep 2011 17:14:47 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Javier Cardona Date: Tue, 27 Sep 2011 17:14:27 -0700 Message-ID: (sfid-20110928_021450_729284_65EB67C7) Subject: =?windows-1252?Q?Re=3A_Channel_type_negotiation_=96_HT_support_for_mesh?= To: "Luis R. Rodriguez" Cc: Ashok Nagarajan , thomas , devel@lists.open80211s.org, Sidharth Thakur , linux-wireless Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Luis, On Tue, Sep 27, 2011 at 4:29 PM, Luis R. Rodriguez wrote: > (...) > A while back we had heard 802.11s support will *not* support > aggregation, Javier, did the spec go out like that? No it did not. HT support (and aggregation) was a relatively late addition to the draft and we never got to implement it. But the spec assumes it is doable. For A-MSDU aggregation, the Mesh Control header should go on the first fragment. I don't see anything special required to support A-MPDU aggregation in mesh. > Why was aggregation thought to not be possible with 802.11s? > I can't see why right now. Probably because when we had that conversation, HT support was not yet specified in the draft? Not sure. > If we want to do comparable throughput tests for HT rates > with Mesh we'd need to setup an AP with aggregation disabled, and the > same WMM parameters. OK Thanks! Javier -- Javier Cardona cozybit Inc. http://www.cozybit.com