radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
To: radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org,
	simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org,
	"ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org"
	<ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org
Subject: Re: Standardisation - adding 2 bit STBC and Ness to MCS (repost 3)
Date: Thu, 16 May 2013 11:01:30 +0200	[thread overview]
Message-ID: <5194A06A.3000103@rempel-privat.de> (raw)
In-Reply-To: <518B72AE.4010402-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>

Hallo all,

so, there is no updates or critic on this topic. That mean, every thing 
is OK.

I assume  "suggested-fields/MCS extension for STBC and Ness"
http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness

can be moved to "defined-fields/MCS"
http://www.radiotap.org/defined-fields/MCS

Johannes, your word ;)


Am 09.05.2013 11:55, schrieb Oleksij Rempel:
> Hallo all,
>
> this is probably third repost of this standardisation request.
>
> History:
> - 11 May 2012. initial request made by Simon Barber.
> http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness
>
>
> - 1 Okt 2012, Wireshark support this fields. Patches provided by
> Wojciech Dubowik.
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6720
>
> - 1 Nov 2012. patches for intel adapters, ieee80211 and wireshark was
> uploaded by Simon.
> http://www.radiotap.org/suggested-fields/MCS%20extension%20for%20STBC%20and%20Ness?action=AttachFile
>
>
> - 17 Nov 2012. Simon posted new thread as suggested Johannes Berg.
>
> - 1 May 2013. I restarted this discussion.
>
> link to initial discussion:
> http://comments.gmane.org/gmane.network.wireless.radiotap/302
>
> As you can see it is already long standing issue...
>
> Now to proposal mad by Simon. Please add comments like: agreed or not
> agreed and why.
>
> ======================== Proposal ===========================
>
> This proposal is to extend the current MCS radiotap header to carry STBC
> and Ness information. This information is carried in the 802.11 HT-SIG
> field that carries all the other fields currently in this radiotap MCS
> header. Both STBC and Ness fields are needed alongside the others to
> calculate the length (duration in time) of a frame. This proposal adds 3
> bits to the known field and the flags field. See below for proposed text.
>
> = MCS =
>
>   Bit Number:: 19
>   Structure:: u8 known, u8 flags, u8 mcs
>   Required Alignment:: 1
>
> The `mcs` field indicates the MCS rate index as in
> [[http://en.wikipedia.org/wiki/IEEE_802.11n-2009#Data_rates|IEEE_802.11n-2009]]
>
>
> The `known` field indicates which information is known:
> ||'''flag'''||'''definition'''||
> || `0x01` || bandwidth ||
> || `0x02` || MCS index known (in `mcs` part of the field) ||
> || `0x04` || guard interval ||
> || `0x08` || HT format ||
> || `0x10` || FEC type ||
> || `0x20` || STBC known ||
> || `0x40` || Ness known (Number of extension spatial streams) ||
> || `0x80` || Ness data - bit 1 (MSB) of Number of extension spatial
> streams ||
>
> The `flags` field is any combination of the following:
> || '''flag''' || '''definition''' ||
> || `0x03` || bandwidth - 0: 20, 1: 40, 2: 20L, 3: 20U ||
> || `0x04` || guard interval - 0: long GI, 1: short GI ||
> || `0x08` || HT format - 0: mixed, 1: greenfield ||
> || `0x10` || FEC type - 0: BCC, 1: LDPC ||
> || `0x60` || Number of STBC streams ||
> || `0x80` || Ness - bit 0 (LSB) of Number of extension spatial streams |
>


-- 
Regards,
Oleksij

       reply	other threads:[~2013-05-16  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <518B72AE.4010402@rempel-privat.de>
     [not found] ` <518B72AE.4010402-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-16  9:01   ` Oleksij Rempel [this message]
     [not found]     ` <5194A06A.3000103-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2013-05-16 13:22       ` Standardisation - adding 2 bit STBC and Ness to MCS (repost 3) Johannes Berg
2013-05-09  9:55 Oleksij Rempel

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=5194A06A.3000103@rempel-privat.de \
    --to=linux-yek0n+yfykbzxqdaratxbw@public.gmane.org \
    --cc=ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org \
    --cc=simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.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).