RE: Regarding A-MPDU status field

["Rao, Krishna" <kcrao-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>]

Hi,

>Makes sense to me. I guess that means we just remove the ampdu subframe index from the proposal, so we have this?
The below looks good. You can also add an implementation note that the sniffer application should order the subframes using the A-MPDU reference number and timestamp.

> A-MPDU radiotap field
>-----------------------
>bit index: TBD
>alignment: 4 bytes (u32)

>* ampdu reference number (u32)
I assume you will be adding the note about the reference number being different for every channel...

>* flags (u16)
>  - 0x01: driver reports 0-length subframes
>  - 0x02: is 0-length subframe (valid if 0x01 set)
>  - 0x04: last subframe known
>          (should be set for all subframes if driver knows)
>  - 0x08: is last subframe in ampdu (valid if 0x04 set)
>           (clear for all but last subframe)
>   - 0x10: delimiter CRC error
>   - 0x20: delimiter CRC value known
> * delimiter CRC value (u8) (valid if flag 0x20 set)
> * u8 (reserved)

>(I added the reserved field and changed the flags to u16, it seems relatively likely that other fields will need u32 alignment so it seems reasonable to reserve a byte here, maybe for VHT extensions?)
Makes sense.

Regds,
Krishna