--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Jon, My arguments (note that I was wrong on the call today, and have modified my thinking as a result): - The Beacon frame is one of the management frames defined in 9.3.3. As such, it has defined fields called “Address 1”, “Address 2” … (Note, this is unlike Control frames defined in 9.2.1 subclauses, which have fields named “RA”, “TA, etc. – and that’s where I was wrong on the call today.)
- Nothing in 9.3.3.2, where the Beacon frame body is defined, changes the description/definition in 9.3.3. So, we are left that Beacon frames have the numbered Address fields.
- The text in question in this comment is calling out the “transmitter address field of a Beacon frame”. I claim there is no such field, and this is confusing/misleading.
- Doing anything with noting that “transmitter address” is also “TA” doesn’t help or alter this.
And, separately: - In 9.3.3.1, where the Address <#> fields are described, it is explicit with phrasing like, “The Address 2 field of the Management frame is …” “If the STA is an AP [other conditions], then this address is the transmitted BSSID.”
- Where Address 3 is described, it says “If the STA is an AP, the Address 3 field is the same as the Address 2 field.”
All this leads me to the conclusion that it is most correct to refer to this as the “Address 2 field”, and nothing to do with the TA. (I’ll note that this is muddied slightly, but the start of the Address 2 text in 9.3.3.1, which says (going on from the quote above): “The Address 2 field of the Management frame is the TA (=SA) and is the address of the STA transmitting the frame.” To be completely strict about it, this is in conflict with bullet #3 directly under this sentence, which says “… this address is the transmitted BSSID”, so it is now defined to be two different things (which have, by definition, the same value). Yuck…) So, I think in the definition for BSSID we should be saying: “The BSSID included in the medium access control (MAC) header transmitter address Address 2 field of a Beacon frame when the multiple BSSID capability is supported” Mark From: Jon Rosdahl <jrosdahl@xxxxxxxx>
Sent: Monday, October 25, 2021 4:06 PM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGM] GEN AdHoc CID 372 - TA field vs transmitter address (TA) field. --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- Further to the email discussion, from the May 24th Minutes: 1.1.1. CID 372 (GEN): 1.1.1.1. Reviewed proposed resolution, to add “(TA)” after “transmitter address”. 1.1.1.2. The field is just called “TA” field. We don’t need to expand the name. 1.1.1.3. Straw Poll: Proposed Resolution for CID 372 A) Change "...transmitter address field..." to "...transmitter address (TA) field…" B) Change to "...transmitter address field..." to "...TA field…" C) Abstain. 1.1.1.4. Results: 4-4-2 (8 no response) 1.1.1.5. Consider rejecting? Disagree with rejecting, no one is speaking in favor of the existing text. Existing text says “transmitter address field” which is not a defined field. 1.1.1.6. ACTION ITEM #4: Emily (Editor): Will bring to Working Group editor to ask for their input on CID 372: Change "...transmitter address field..." to "...transmitter address (TA) field…" or "...TA field…" or something else. 1.1.1.6.1. If the editors agree to expand the terms (in field names, in the definitions), we should do that consistently throughout. 1.1.1.7. (From Chat: Unexpanded terms in D0.0: HT Control, QoS Control field, Management MIC element, RDG/More PPDU subfield, EOF subfield, FILS Authentication frame, DMG Beacon frame, VHT Capabilities element) 1.1.1.8. Will bring back. 1.1.1.9. Move to Comment Group: “Definitions Clause 3” and Status = Discuss. Jon ----------------------------------------------------------------------------- Jon Rosdahl Engineer, Senior Staff
IEEE 802 Executive Secretary Qualcomm Technologies, Inc.
office: 801-492-4023 10871 North 5750 West
cell: 801-376-6435 Highland, UT 84003
A Job is only necessary to eat!
A Family is necessary to be happy!!
In an effort to clean up the remaining CIDs, we started to review what we had discussed last May. "transmitted basic service set identifier (BSSID): The BSSID included in the medium access control (MAC) header transmitter address field of a Beacon frame when the multiple BSSID capability is supported." "transmitted basic service set identifier (BSSID): The BSSID included in the medium access control
(MAC) header transmitter address field of a Beacon frame when the multiple BSSID capability is supported." -- "transmitter address" should be "TA" since the field is referred to as the TA field
Proposed change: "As it says in the comment" Proposed Resolution: Revised
on p199.51 Straw Poll for a Proposed Resolution for CID 372: A) Change "...transmitter address field..." to "...transmitter address (TA) field…"
B) Change to "...transmitter address field..." to "...TA field…"
C) Abstain.
Results: 4-4-2 (8 no response)
Proposed Resolution: Revised
p199.51
Change "...transmitter address field..." to "...transmitter address (TA) field…" There are 32 instances of "transmitter address" in the D0.0 standard. In the definitions clause 3.2, transmitter address is used 3 times: p175.58: "bandwidth signaling transmitter address (TA): A TA that is used......" p187.27: "nonbandwidth signaling transmitter address (TA): An address in the TA field of an medium access" p199.51(D0.0) - one in question. "transmitted basic service set identifier (BSSID): The BSSID included in the medium access control (MAC) header transmitter address field of a Beacon frame when the multiple BSSID capability is supported." TA transmitter address or transmitting station address TTAK TKIP-mixed transmitter address and key The use of "transmitter address" followed by (TA) in two of 3 instances in the definition clause leads to justification for using it in the 3rd definition. Interesting the TA in the first two instances has a pre adjective given in both cases, but the acronym TA is used without the pre adjective when used in the definition. The "Medium Access Control (MAC)" is spelled out and an acronym given, which also gives support for the use of transmitter address (TA). There are 8 instances of "transmitter address (TA)" in the standard. Your feedback and thoughts on which of the two solutions should be used is welcome, ----------------------------------------------------------------------------- Jon Rosdahl Engineer, Senior Staff
IEEE 802 Executive Secretary Qualcomm Technologies, Inc.
office: 801-492-4023 10871 North 5750 West
cell: 801-376-6435 Highland, UT 84003
A Job is only necessary to eat!
A Family is necessary to be happy!!
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 |