From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [RFC bluetooth-next] ieee802154: 6lowpan: set ackreq when needed
Date: Thu, 28 May 2015 12:02:34 +0200 [thread overview]
Message-ID: <20150528100130.GA716@omega> (raw)
In-Reply-To: <5566D03B.7080209@osg.samsung.com>
On Thu, May 28, 2015 at 10:22:19AM +0200, Stefan Schmidt wrote:
> Hello.
>
> On 27/05/15 12:12, Alexander Aring wrote:
> >This patch sets the acknowledge request bit inside the 802.15.4 mac
> >header when frame retries is 0 or above. The other frame retries value
> >which is -1 indicates that the transmitter doesn't care about an
> >acknowledge frame which will be ignored after transmitting if the node
> >sends anyway an ack frame after receiving. This is currently unnecessary
> >traffic if the max frame retries parameter is -1. I hope transceivers
> >which supports AACK handling will check on this bit and doesn't send an
> >ack frame after receiving.
>
> Do we know if AACK enbaled receivers really parse this and avoid sending the
> ACK? They should but I wonder if you did run any test for this.
>
I did a test with a running at86rf231 in monitor mode, I don't see ack
frames when this isn't set, so AACK handling should take care about this
bit.
Any other suggestions? I mean this patch makes sense, if we are in a
transmit mode that doesn't care about ack frame after transmit, then we
don't need to set the ack request bit, or?
- Alex
prev parent reply other threads:[~2015-05-28 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 10:12 [RFC bluetooth-next] ieee802154: 6lowpan: set ackreq when needed Alexander Aring
2015-05-28 8:22 ` Stefan Schmidt
2015-05-28 10:02 ` Alexander Aring [this message]
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=20150528100130.GA716@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@osg.samsung.com \
/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.