From: David Young <dyoung@pobox.com>
To: radiotap@radiotap.org, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Proposal]TX flags
Date: Thu, 16 Apr 2009 10:37:24 -0500 [thread overview]
Message-ID: <20090416153724.GX25412@ojctech.com> (raw)
In-Reply-To: <69e28c910904141733m72ce521ap8f1865bec991fff7@mail.gmail.com>
On Wed, Apr 15, 2009 at 02:33:05AM +0200, G?bor Stefanik wrote:
> I propose the following suggested Radiotap features to be standardised:
>
> * A new, 16-bit wide "TX flags" field (field number 15), containing
> the following flags:
> - TX failed due to excessive retries,
> - CTS-to-self protection,
> - RTS/CTS-handshake,
> - Frame shall not be ACKed ("No-ACK"), and
> - Sequence number shall not be recalculated ("No-Seq").
Thanks.
FWIW, these assignments are compatible with NetBSD. They appear to be
compatible with FreeBSD, too.
> If no one objects to this proposal in 7 days, I will resubmit it as a
> formal RFA, to allow eventual adoption.
Great!
Dave
--
David Young OJC Technologies
dyoung@ojctech.com Urbana, IL * (217) 278-3933
next prev parent reply other threads:[~2009-04-16 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:33 [Proposal]TX flags Gábor Stefanik
2009-04-16 15:37 ` David Young [this message]
2009-04-16 17:28 ` Johannes Berg
2009-04-16 18:47 ` Gábor Stefanik
2009-04-16 18:59 ` Johannes Berg
2009-04-16 19:10 ` Michael Buesch
2009-04-16 20:48 ` David Young
2009-04-17 1:24 ` Gábor Stefanik
2009-04-17 9:50 ` Johannes Berg
2009-04-16 20:33 ` David Young
2009-04-16 20:48 ` Johannes Berg
2010-03-22 19:32 ` Michael Stahn
2010-03-23 0:42 ` Bruno Randolf
2010-03-23 15:50 ` Michael Stahn
2010-03-24 11:15 ` Bruno Randolf
2010-03-24 19:43 ` Pavel Roskin
2010-03-24 20:26 ` Gábor Stefanik
2010-03-25 1:22 ` Michael Stahn
2010-03-25 20:32 ` Gábor Stefanik
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=20090416153724.GX25412@ojctech.com \
--to=dyoung@pobox.com \
--cc=linux-wireless@vger.kernel.org \
--cc=radiotap@radiotap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).