[RFC] L-SIG field

[RFC] L-SIG field

[Johannes Berg]

Looks like we need this, any thoughts? Seems like a straight-forward
extension.

---
title: L-SIG
categories: [suggested]
---
Bit Number
: 27 (tentatively assigned, field data may change)

Structure
  - u16 data1, data2

Required Alignment
: 2

Unit(s)
: none

This field indicates - if known - the contents of the L-SIG.

## data1

| **`0x0001`** | rate known |
| **`0x0002`** | length known |
| **`0xfffc`** | (reserved) |

## data2

| **`0x000f`** | rate |
| **`0xfff0`** | length |

Re: [RFC] L-SIG field

[Simon Barber]

I'd love to see this! It would be very useful for the Wireshark timeline, to accurately display aggregate duration when not all the subframes are passed up by the driver.

Simon

> On Jul 2, 2018, at 7:37 AM, Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> 
> Looks like we need this, any thoughts? Seems like a straight-forward
> extension.
> 
> ---
> title: L-SIG
> categories: [suggested]
> ---
> Bit Number
> : 27 (tentatively assigned, field data may change)
> 
> Structure
>  - u16 data1, data2
> 
> Required Alignment
> : 2
> 
> Unit(s)
> : none
> 
> This field indicates - if known - the contents of the L-SIG.
> 
> ## data1
> 
> | **`0x0001`** | rate known |
> | **`0x0002`** | length known |
> | **`0xfffc`** | (reserved) |
> 
> ## data2
> 
> | **`0x000f`** | rate |
> | **`0xfff0`** | length |
>