From: "Alwin Beukers" <alwin-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Simon Barber <simon-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
Cc: "radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org"
<radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: RE: [RFC] VHT fields
Date: Tue, 19 Jun 2012 11:37:09 +0000 [thread overview]
Message-ID: <C6E8EE2D6B3ACB4582C1249E834B3065061857@SJEXCHMB13.corp.ad.broadcom.com> (raw)
In-Reply-To: <4FDF7426.2050202-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
Hi Simon,
> I'm not very familar with 11ac - but does this information together
> with the packet data give you enough to calculate precisely the
> packet's duration in time? Are there any duration fields, as there are
> in 11n that might be useful?
Haven't tried it, but I think you would have all the required info.
Section 22.3.2 of the 11ac draft has the durations of the training and
signal fields. The duration of VHT-LTF depends on the total number
of space-time streams (NSTS), which you can get from the SU_VHT
and MU_VHT fields.
The radiotap header doesn't contain the data length from the
VHT-SIG-B field, but I guess you can get that from the packet data
itself. There is a datarate calculation in the Wireshark patch I sent
with the proposal.
Alwin
>
> Simon
next prev parent reply other threads:[~2012-06-19 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 8:15 [RFC] VHT fields Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306505FEEE-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-06-15 8:29 ` Johannes Berg
2012-06-18 12:01 ` Johannes Berg
[not found] ` <1340020862.4615.8.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-06-19 10:56 ` Alwin Beukers
2012-06-18 18:32 ` Simon Barber
[not found] ` <4FDF7426.2050202-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
2012-06-19 11:37 ` Alwin Beukers [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-14 11:24 Alwin Beukers
2012-06-12 15:05 Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306505D68C-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-06-12 16:51 ` Johannes Berg
[not found] ` <1339519879.4531.13.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-06-13 10:42 ` Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306505E99C@SJEXCHMB13.corp.ad.broadcom.com>
[not found] ` <1339672828.4461.0.camel@jlt3.sipsolutions.net>
[not found] ` <1339672828.4461.0.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-06-14 12:05 ` Arend van Spriel
2012-07-04 17:18 ` Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306506E807-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-07-05 8:37 ` Johannes Berg
[not found] ` <1341477463.4455.17.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-07-23 13:43 ` Alwin Beukers
2012-07-05 9:08 ` Johannes Berg
[not found] ` <1341479327.4455.35.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-07-23 14:47 ` Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306508054B-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-07-23 15:25 ` Johannes Berg
[not found] ` <1343057111.4584.22.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-07-27 14:41 ` Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B306508499C-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-08-20 16:42 ` Johannes Berg
[not found] ` <1345480938.4459.40.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-08-24 7:46 ` Alwin Beukers
[not found] ` <C6E8EE2D6B3ACB4582C1249E834B30650B4151-HXj2mutaA2obnnZVN+9SiJr/X4hKkxxPpWgKQ6/u3Fg@public.gmane.org>
2012-08-24 9:00 ` Johannes Berg
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=C6E8EE2D6B3ACB4582C1249E834B3065061857@SJEXCHMB13.corp.ad.broadcom.com \
--to=alwin-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@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 read-only IMAP folder(s) and NNTP newsgroup(s).