RadioTap Archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: radiotap@radiotap.org
Cc: Richard Sharpe <realrichardsharpe@gmail.com>
Subject: Re: EHT definitions - U-SIG
Date: Mon, 06 Dec 2021 16:52:47 +0100	[thread overview]
Message-ID: <c03df0feebbc88cb87f6aca1b5f039efbe2d59d0.camel@sipsolutions.net> (raw)
In-Reply-To: <81f624878a2191586e72543a5b5dabc95d5673a6.camel@sipsolutions.net>

Hi,

Since it's all hard to read in plain markdown, I've uploaded it to the
suggested fields:

https://www.radiotap.org/fields/U-SIG

https://www.radiotap.org/fields/EHT

The EHT one got pretty big, but OTOH since we have TLVs now we can make
it variable size, and don't need the split like we had with HE where we
did HE, HE-MU and HE-MU-other-user, which is nice.

Comments welcome. I'll probably (have to) continue to tweak it as our
implementation progresses, but all the bigger open questions I had are
resolved, and it looks like I can put everything our sniffer will report
into it.

The only thing I know of right now that I'm not entirely sure about is
the Content Channel Index thing - i.e. "which preamble of the
transmission did I capture". Our DSP appears to provide this in trigger-
based RU allocation format, and I have to check how to use that
properly.

johannes

  parent reply	other threads:[~2021-12-06 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  8:35 EHT definitions - U-SIG Johannes Berg
2021-12-03  8:36 ` Johannes Berg
2021-12-06 15:52 ` Johannes Berg [this message]
2022-10-20 11:55   ` 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=c03df0feebbc88cb87f6aca1b5f039efbe2d59d0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=radiotap@radiotap.org \
    --cc=realrichardsharpe@gmail.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 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).