From: Christian Lamparter <chunkeey@googlemail.com>
To: Johan Danielsson <joda@kth.se>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211 and RX of A-MPDU with missing back agreement
Date: Wed, 9 Jan 2013 18:43:05 +0100 [thread overview]
Message-ID: <201301091843.05314.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAESKgcj1YD2-TwOQ4ZH3nFs8CCgfKHzp4gM4YUsjaqgn4cAMGw@mail.gmail.com>
On Wednesday, January 09, 2013 11:05:20 AM Johan Danielsson wrote:
> > [...] I argued that if we have no (or no longer) a BA agreement
> > [even if the peer never got the DELBA] we can discard the AMPDU data
> > and sent a DELBAs to the HT peer once it tries sent us an A-MPDU
> > (again). This is actually what we should do according to 802.11-2012
> > 10.5.4 - instead of calling dont_reorder.
>
> I think this is a reasonable interpretation, even though 10.5.4
> doesn't explicitly cover this case (since the Ack Policy is set to
> Normal Ack).
This is were RX_FLAG_AMPDU_DETAILS would come into the game.
If this rx flag is set we know that the frame was part of
an AMPDU and not a normal non-aggregated QoS-Data frame.
Regards,
Chr
next prev parent reply other threads:[~2013-01-09 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 10:32 mac80211 and RX of A-MPDU with missing back agreement Johan Danielsson
2013-01-07 19:53 ` Christian Lamparter
2013-01-08 10:39 ` Johan Danielsson
2013-01-08 16:15 ` Christian Lamparter
2013-01-08 21:47 ` Johan Danielsson
2013-01-08 23:38 ` Christian Lamparter
2013-01-09 10:05 ` Johan Danielsson
2013-01-09 17:43 ` Christian Lamparter [this message]
2013-01-09 18:32 ` Christian Lamparter
2013-01-09 10:54 ` Stanislaw Gruszka
2013-01-09 12:02 ` Johannes Berg
2013-01-09 13:46 ` Christian Lamparter
2013-01-09 13:54 ` Johannes Berg
2013-01-09 18:05 ` Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201301091843.05314.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=joda@kth.se \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.