| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Working Group Reflector ---
From: Xiaogang Chen <xiaogang.chen@xxxxxxxx> --- This message came from the IEEE 802.11 Working Group Reflector ---
Hi Brian When review the document #576, I have the following questions regarding the short PPDU detection (bear with me if this has already been discussed):
Is this a typo? Should be 36 or 9 symbol? If so, the following need to be changed? If the check of the parity bit is valid and the RATE field indicates 6 Mb/s in non-HT but the LENGTH field value in the L-SIG field indicates less than
seven non-HT OFDM symbols, a PHY-RXSTART.indication primitive is not issued.
[Thanks for this! I had made a partial fix here (12->20) but not caught all the downstream changes needed. Now fixed in r7 (“nine” x2) (uploaded)]
b) the L-SIG field indicates less than
five OFDM symbols after the L-SIG field, [Thanks for this! My bad – I was mentally thinking “five or fewer”. Now fixed in r7 (“less than six”) (uploaded)] 3. IMO, if we really want to use the LENGTH field to identify non-HT PPDU, it’s better to directly use the value of L_LENGTH instead of converting to number of symbols. E.g. for VHT, minimum time after L-SIG
is 24us per your calculations, so LENTH field < 24/4*3-3 = 15 means PPDU is not VHT. [Good question. Youhan showed some interest here too. Now #symbols is important because that’s how L_LENGTH arises. If there was some future amendment where we used 9 Mbps (instead of the usual 6 Mbps) to
indicate a new PPDU type, the L_LENGTH value would not be correct (but the #symbols still would be). So I lean to including
both, with #symbols as the main idea e.g. “the LENGTH field indicates at least nine non-HT OFDM symbols after the L-SIG field (i.e., the L-SIG LENGTH is at least 22 octets at 6 Mbps)” This is what I’ve done in r7 (uploaded)] BRs, Xiaogang. From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
--- This message came from the IEEE 802.11 Working Group Reflector ---
Hi all In 11me, CID 1056, there is a proposal to add a Vendor Specific Trigger Type in order to facilitate prototyping. Any comments / concerns / suggestions / recommended directions are welcome. The latest proposed language for this is in 22/576 (and see below): TGme Editor, make the following changes to D1.0 shown by Word track changes under CID 1056 Table 9-46—Trigger Type subfield encoding(11ax)
The Trigger Dependent Common Info subfield in the Common Info field is optionally present based on the value of the Trigger Type field (see 9.3.1.22.2 (Basic Trigger frame format) to
9.3.1.22.10 (Vendor Specific Trigger frame format)) 9.3.1.22.10 Vendor Specific Trigger frame format The Trigger Dependent Common Info subfield is not present in the Vendor Specific Trigger frame. The Trigger Dependent User Info subfield of the Vendor Specific Trigger frame is defined in Figure 9-97a (Trigger Dependent User Info subfield
format in the Vendor Specific Trigger frame).
Figure 9-97a (Trigger Dependent User Info subfield format in the Vendor Specific Trigger frame) The Length field indicates the number of octets in the Trigger Dependent User Info subfield excluding the Length field. The Organization Identifier field (see 9.4.1.31 (Organization Identifier field)) identifies the entity that has defined the content of the Vendor Specific Content field. See 9.4.1.31 (Organization Identifier field) for the definition of
j. 10.28 MAC frame processing 10.28.13 Trigger frame parsing A STA that encounters an unknown Trigger Type subfield in the Common Info field of a Trigger frame shall ignore the frame.
Best regards Brian To unsubscribe from the STDS-802-11 list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 To unsubscribe from the STDS-802-11 list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 |