- 802.11 has a hatred of hyphens that transcends grammar, so it has to
be "Vendor specific content", sadly
> I'm curious where this hatred comes from.
I have no idea about this.
Maybe at some point someone said "it's too
hard to get hyphens right, so let's just stop using them" and no-one
objected?
> And I'm also wondering what is the 802.11 rule that I'm missing that makes the capitalization be different between "Vendor specific content"
and "Vendor Specific Trigger frames".
It's because the rule is to
capitalise the first letter of the names of
frames, fields, etc. but
not other stuff (except if it's a term from another
standard, where it's
capitalised there).
Ahaa, but here it is the name
of a field!
So it probably should be "Vendor Specific Content" and
then it should be specified as "The Vendor Specific Content field
contains vendor specific [sic] content whose interpretation is outside the
scope of this standard."
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
From:
Harkins, Dan <daniel.harkins@xxxxxxx>
Sent: Friday, 13 May 2022 07:24
To: Mark Rison <m.rison@xxxxxxxxxxx>; STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGM] Vendor specific Trigger frames
Hello,
On 5/12/22, 3:11 PM, "Mark Rison" <m.rison@xxxxxxxxxxx> wrote:
- 802.11 has a hatred of hyphens that transcends grammar, so it has to
be "Vendor specific content", sadly
- You also need to specify what the Trigger Dependent User Info subfield
is for Vendor Specific Trigger frames
I'm curious where this hatred comes from. And I'm also wondering what is the 802.11 rule that I'm missing that makes the capitalization be different
between "Vendor specific content" and "Vendor Specific Trigger frames".
Dan.
--
"the object of life is not to be on the side of the majority, but to
escape finding oneself in the ranks of the insane." – Marcus Aurelius
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
From:
Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, 12 May 2022 22:36
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] Vendor specific Trigger frames
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Hi all
In 802.11me, it was suggested that wider discussion be solicited for the following CID. Feedback welcome.
Best regards
Brian
|
1056 |
988.00 |
9.3.1.22.1 |
Pre-standards prototyping is hindered by the absence of a vendor specific trigger type |
Define a value (e.g. 15) for vendor specific triggers, where the first 3 octets of the Trigger Dependent Common Info field is an OUI |
Discussion
Trigger frames create a valuable new capability. Vendors might explore using Trigger frames in new ways such as prototyping ideas that might
feed into a future amendment. In order to enable such work, without the risk of it interfering with a future ANA assignment of the Trigger Type subfield, we recommend defining a Vendor Specific Trigger frame.
Due to the known pain of fragmenting/splitting elements, for future proofing, we further recommend the use of a 2-octet Length field.
Proposed Resolution: CID 1056
Revised.
Note to Commenter:
The commenter’s concerns are valid and are substantially addressed in 22/0576R<motionedRevision> under CID 1056.
Instruction to Editor:
Implement the proposed text updates listed under CID 1056 in 22/0576R<motionedRevision>
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)
|
Trigger Type subfield value |
Trigger frame variant |
|
0
|
Basic |
|
1
|
Beamforming Report Poll (BFRP) |
|
2
|
MU-BAR |
|
3
|
MU-RTS |
|
4
|
Buffer Status Report Poll (BSRP) |
|
5
|
GCR MU-BAR |
|
6
|
Bandwidth Query Report Poll (BQRP) |
|
7
|
NDP Feedback Report Poll (NFRP) |
|
8-15
<excluding value defined by ANA> |
Reserved |
|
<ANA> |
Vendor Specific |
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 of the Vendor Specific Trigger frame is defined in Figure 9-97a (Trigger Dependent Common Info
subfield format in the Vendor Specific Trigger frame).
|
|
Length |
Organization Identifier |
Vendor-specific content |
|
Octets |
2 |
j |
0 or more |
Figure 9-97a (Trigger Dependent Common Info subfield format in the Vendor Specific Trigger frame)
The Length field indicates the number of octets in the Trigger Dependent Common 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 particular Vendor Specific element. See 9.4.1.31 (Organization Identifier field) for the definition of
j.
To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1
|
|
To unsubscribe from the STDS-802-11-TGM list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1
To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1