From: Johannes Berg <johannes@sipsolutions.net>
To: radiotap@radiotap.org
Cc: Richard Sharpe <realrichardsharpe@gmail.com>
Subject: EHT definitions - U-SIG
Date: Fri, 03 Dec 2021 09:35:26 +0100 [thread overview]
Message-ID: <81f624878a2191586e72543a5b5dabc95d5673a6.camel@sipsolutions.net> (raw)
Hi,
I'm slowly digging through what's necessary for EHT, and so far I'm only
really happy with what I have for the easy part (U-SIG), so sending that
out here.
Note that the alignment of 4 bytes is harmless because this is going
into a TLV field that anyway requires 4-byte alignment in the first
place.
I am wondering if we should have two additional bits there - "CRC
checked" and "CRC bad", as there will be cases where we might be able to
provide parts of the U-SIG but not the entire CRC for offline checking,
and if the PLCP is indicated as bad
(https://www.radiotap.org/fields/RX%20flags.html) then I guess bad U-SIG
CRC would be indicated as that, and then having an extra two bits here
would let you figure out if it was bad in the U-SIG? But OTOH I'm not
sure it's really possible to provide the information anyway if the
checksums are bad somewhere along the line, so I haven't included that.
Note also that the U-SIG is meant to be forward-compatible in a sense,
so only some fields are defined to be fixed. Hence the inclusion of the
mask for all bits.
Comments welcome!
johannes
---
title: U-SIG
categories: [suggested]
---
Type
: 32
Structure
- u32 common
- u32 value, mask
Required Alignment
: 4
Unit(s)
: none
This field indicates - if known - the contents of the U-SIG.
Note that the common/value/mask fields are ordered in this way
so if they're all known, the U-SIG bits are all contiguous in
memory in the same way as over the air from bit 12 of the common
field to the end of the value field.
## common
| **`0x00000001`** | PHY version identifier known |
| **`0x00000002`** | BW known |
| **`0x00000004`** | UL/DL known |
| **`0x00000008`** | BSS Color known |
| **`0x00000010`** | TXOP known |
| **`0x00000fe0`** | (reserved) |
| **`0x00007000`** | PHY version identifier |
| **`0x00038000`** | BW |
| **`0x00040000`** | UL/DL |
| **`0x01f80000`** | BSS Color |
| **`0xfe000000`** | TXOP |
## value / mask
Contains a known mask and value for the remaining U-SIG bits
that can only be interpreted depending on the PHY version.
The bits are in the on-air order, i.e. U-SIG-1 `B20-25` followed
by U-SIG-2 `B0-25`. Thus, U-SIG-1 `B20-25` are in `mask` and
`value` bits `0x0000003f`.
Dissectors should show these per spec, in a PHY version specific
namespace (e.g. "U-SIG::EHT::PPDU-Type-And-Compression-Mode").
For the only currently defined version (PHY Version identifier 0
for EHT), the bits are shown in the following tables:
### EHT MU PPDU U-SIG contents
An EHT PPDU is an EHT MU PPDU if
* the UL/DL field is set to 0 and the PPDU Type And Compression Mode field is set to 0, 1 or 2;
* the UL/DL field is set to 1 and the PPDU Type And Compression Mode field is set to 1.
| **bits** | **U-SIG reference** | **Content** |
| **`0x0000001f`** | `U-SIG-1 B20-B24` | Disregard (all ones) |
| **`0x00000020`** | `U-SIG-1 B25` | Validate (must be 1) |
| **`0x000000c0`** | `U-SIG-2 B0-B1` | PPDU Type And Compression Mode |
| **`0x00000100`** | `U-SIG-2 B2` | Validate (must be 1) |
| **`0x00003e00`** | `U-SIG-2 B3-B7` | Punctured Channel Information |
| **`0x00004000`** | `U-SIG-2 B8` | Validate (must be 1) |
| **`0x00018000`** | `U-SIG-2 B9-B10` | EHT-SIG MCS |
| **`0x003e0000`** | `U-SIG-2 B11-B15` | Number Of EHT-SIG Symbols |
| **`0x03c00000`** | `U-SIG-2 B16-B19` | CRC (for the bits `U-SIG-1 B0` to `U-SIG-2 B15`) |
| **`0xfc000000`** | `U-SIG-2 B20-B25` | Tail (must be 0) |
### EHT TB PPDU U-SIG contents
An EHT PPDU is a EHT TB PPDU if
* the UL/DL field is set to 1 and the PPDU Type And Compression Mode field is set to 0.
| **bits** | **U-SIG reference** | **Content** |
| **`0x0000003f`** | `U-SIG-1 B20-B25` | Disregard (all ones) |
| **`0x000000c0`** | `U-SIG-2 B0-B1` | PPDU Type And Compression Mode |
| **`0x00000100`** | `U-SIG-2 B2` | Validate (must be 1) |
| **`0x00001e00`** | `U-SIG-2 B3-B6` | Spatial Reuse 1 |
| **`0x0001e000`** | `U-SIG-2 B7-B10` | Spatial Reuse 2 |
| **`0x003e0000`** | `U-SIG-2 B11-B15` | Disregard (...) |
| **`0x03c00000`** | `U-SIG-2 B16-B19` | CRC (for the bits `U-SIG-1 B0` to `U-SIG-2 B15`) |
| **`0xfc000000`** | `U-SIG-2 B20-B25` | Tail (must be 0) |
next reply other threads:[~2021-12-03 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 8:35 Johannes Berg [this message]
2021-12-03 8:36 ` EHT definitions - U-SIG Johannes Berg
2021-12-06 15:52 ` Johannes Berg
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=81f624878a2191586e72543a5b5dabc95d5673a6.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).