Bug 2604 – QosData frames with Block Ack policy should be separated by SIFS as long as they belong to the same TXOP

Bug 2604 - QosData frames with Block Ack policy should be separated by SIFS as long as they belong to the same TXOP


Summary:	QosData frames with Block Ack policy should be separated by SIFS as long as t...

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wifi
Version:	ns-3.26
Hardware:	All All

Importance:	P2 major
Assigned To:	sebastien.deronne

URL:
Keywords:

Depends on:
Blocks:	2528
	Show dependency tree / graph

Reported:	2017-01-02 10:37 UTC by sebastien.deronne
Modified:	2017-01-29 17:07 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
patch to fix (5.90 KB, patch) 2017-01-02 10:47 UTC, sebastien.deronne	Details \| Diff
patch to fix (9.54 KB, patch) 2017-01-03 16:23 UTC, sebastien.deronne	Details \| Diff
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description sebastien.deronne 2017-01-02 10:37:35 UTC

When Block Ack is used, a station sends several QosData frames separated by SIFS, that will be later acknowledged by a single Block Ack. In the current implementation, a backoff is performed between each QosData frame, resulting in almost no benefit to use Block Ack mechanism.

Comment 1 sebastien.deronne 2017-01-02 10:47:41 UTC

Created attachment 2722 [details]
patch to fix

Comment 2 sebastien.deronne 2017-01-03 16:23:55 UTC

Created attachment 2729 [details]
patch to fix

Updated previous patch:
- QosData frames separated by SIFS when they fit in the same TXOP, trigger backoff otherwise
- Fix issues with txop trace

Comment 3 sebastien.deronne 2017-01-07 06:33:04 UTC

Set to LAST CALL since blocking other deliveries

Comment 4 sebastien.deronne 2017-01-24 14:03:08 UTC

I plan to deliver the patch this week

Comment 5 sebastien.deronne 2017-01-29 17:07:04 UTC

Fixed in changeset 12590:c1c446434852