Instead the receiver uses the L-SIG length to determin the RXTIME, from which the symbol count is determined. as an invalid 802.11 signal and switch to weaker energy detect for CCA as was done with previous amendments (e.g. invalid Rate in 802.11a). With the cited sentence, a future amendment may use non-modulo 3 Length values and 802.11ac devices will still defer based on Length. The receiver does not need “out-of-band communication of TXTIME”, as it does not need to calculate TXTIME. It merely extracts Length from L-SIG. 4112 Adrian 263.56 22.3.21 "If the received Group ID in VHT-SIG-A has a value indicating an SU PPDU (see 9.17a (Group ID and Partial AID in VHT PPDUs)), the PHY entity may choose not to decode This breaks layering. The PHY should not need to understand any meaning defined in the MAC, unless the MAC tells it. If there was a single fixed "SU" value, then it should be defined in the PHY - but that is not the case. Add to the (22.26) a parameter SU_GROUP_ID", with description: "The SU_GROUP_ID parameter specifies a value that is used by the receiver to determine that a VHT PPDU is an SU PPDU, and that the PPDU is to be received." and modify this description to refer to it: "If the received Group ID in VHT-SIG-A has a value indicating an SU PPDU (i.e., matching the SU_GROUP_ID of the the PHY entity may choose not to decode VHT-SIG-B." J Rejected. The PHY has the Group ID information from VHT-SIG-A. Layering is not broken by referring a person reading a PHY clause to a definition in a MAC clause. 4113 Adrian 264.07 22.3.21 There's no notion in the 22.3.21 description of what to do when we don't care about the received PPDU. Add a statement along these lines: (264.06 may be a suitable location) "The PLCP determines J Revised. Make changes as shown in <this-doc> under CID 4113 and Figure
Padding if needed" and "Tail Bits (if BCC)" before it is scrambled and encoded to a C-PSDU. In rx, they're apparently always present- In tx, the MAC passes an while in rx the MAC is passed an MPDU- There is no PMD data indication or data end indication- This is covered by the NOTE, but in rx the does not make it to the PLCP- In rx it's just but in tx it's VHT Training Symbols, and neither says what these are- In rx it's and L-LTF but in tx it's just Non-VHT Training Symbols- There are some dots between start and end in tx, but not rx the second sentence of the NOTE- Show how the PARTIAL_AID/GROUP_ID are passed down for tx- Rename "VHT-Training" in rx and "VHT Training Symbols" in tx to or "VHT-STF" and "VHT-LTF"- Rename Non-VHT Training Symbols from the PLCP and rename it to or "L-STF" and in tx- Remove the line of dots at the top of tx Discussion, 22.6.5.2 indicates that DATA.indications are for each bit of SIGNAL or data, after decoding. Another comment changes the unit to the symbol, so we should have a data.indication in the rx procedure for each signal field or data field symbol. Proposed resolution: Revised. In figure 22-25 (tx procedure). Change “Tail Bits (if BCC)” to “Tail Bits”. This is because the note indicates that operational features are not described, so we can assume BCC. In figure 22-27 (rx procedure). Change “Pad and Tail …” to “Pad (if present) and Tail…” In figure 22-27 (rx procedure). Change “MPDU” to “A-MPDU”. In figure 22-27 (rx procedure):