[Ns-developers] Mac layer 802.11n
mk.banchi at gmail.com
Sat Jan 10 11:31:22 PST 2009
Mathieu Lacage ha scritto:
> On Sat, 2009-01-10 at 15:51 +0100, Mirko Banchi wrote:
>> How and when aggregation (both) is an user's choice. User will be able
>> to select two algorithms that have the job of perform aggregations.
>> A-MDSU and A-MPDU are independent each other.
> So, this means that we don't have to worry about the A-MPDU aggregation
> for now which is good (tm).
>> At the moment we are working on MSDU aggregation. When this feature will
>> be operative i'll ask you or Tom, if will be possible, for a
>> mercurial repository on your server. Just then we would try to merge.
> It would be nice to be able to review first the part which creates a
> QapWifiMac+QstaWifiMac with a simple non-aggregation-aware EdcaTxop
> class. Aggregation capability seems more complex and could be done as a
> second step.
> Possible review/merge milestones:
> 1) QstaWifiMac+QapWifiMac+EdcaTxop
> 2) modified MacLow according to previous discussion
> 3) extended EdcaTxop using MacLow to implement aggregation
Ok...About EdcaTxop, what do you think about a unique class EdcaTxopN?
Another way could be to create a common abstract class which EdcaTxop
and EdcaTxopN inherits from.In the first implementation would be not
possible to use only 802.11e standard features without the 802.11n
features. There would be only possible (in an easy manner) to switch off
aggregation.Maybe the second implementation is better...with a common
interface we could use, in QstaWifiMac and in QapWifiMac, EdcaTxop or
EdcaTxopN.This also would help us to have in the same wlan many types of
terminals (for example 802.11e and 802.11n terminals).
what do you think about?
e-mail: mk.banchi at gmail.com
e-mail: mk.banchi at virgilio.it
id-jabber: mk.banchi at jabber.org
id-msn: mb11684 at hotmail.com
PGP key fingerprint:
308F BFB1 4E67 2522 C88E
DC69 7631 52ED 32A5 6456
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3410 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.isi.edu/pipermail/ns-developers/attachments/20090110/1c00ad6f/smime-0001.bin
More information about the Ns-developers