| 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 ---
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 |