Hi All,
Regarding the second topic, we did not finish the discussion due to the time limit. In my view, it is possible to put a field after an element in the authentication frame body. The detailed reason is explained as follows:
If we put a field after the element, such a field must be combined with a special element. That is, the decoding results of the special element will determine whether to continue decoding the subsequent field. (The ideas is quite similar to 11bi draft5.0, whether to decode 9b, it relies on the decode result of 9a)
For example, let's assume the element as element A, including the indication field B, and a separated field as field C.
How does the receiver decode it?
- If element A is not present, field C is also not present. The receiver does not need to decode field B if it cannot find element A based on element A's TLV information.
- If element A is present, based on the indication field B. For example, if field B indicates that field C is present, the receiver will continue to decode C after decoding element A.
- If element A is present, based on the indication field B. For example, if field B indicates that field C is not present, the receiver will not decode C after finishing the decoding of element A. Instead, it will continue to decode other elements based on the TLV information.
An exact example (for the 9a and 9b cases) can be found in https://mentor.ieee.org/802.11/dcn/26/11-26-1215-00-00bi-cr-for-cid-r1-10.docx
Welcome to further insights.
Thanks
Best Regards
Jay Yang (杨志杰)
Original
From: EdwardAu <edward.ks.au@xxxxxxxxx>
To: STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx <STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx>;
Date: 2026年06月12日 09:20
Subject: Re: [STDS-802-11-EDITORS] Editors' teleconference: style guide related to "non-AP <entity> STA" vs. "<entity> non-AP STA"
--- This message came from the IEEE 802.11 Editors' Reflector ---
Dear Editors,
cc. Working Group participants,
It is a friendly reminder that Editors will meet remotely from 12:00pm ET to 1:00pm ET on Monday, 15 June 2026, and discuss on the following 2 items:
1) A contribution prepared by Matt, 11-26/1208, on his thoughts and proposed Editor's style guide related to adjectival ordering within entity names
2) An open discussion led by Carol on the current arrangement of the Authentication frame body table, and whether we should split the table into two - one for fields and another for elements.
Have a nice weekend and talk to you soon : )
Regards,
Edward
cc. Working Group participants,
It is a friendly reminder that Editors will meet remotely from 12:00pm ET to 1:00pm ET on Monday, 15 June 2026, and discuss on the following 2 items:
1) A contribution prepared by Matt, 11-26/1208, on his thoughts and proposed Editor's style guide related to adjectival ordering within entity names
2) An open discussion led by Carol on the current arrangement of the Authentication frame body table, and whether we should split the table into two - one for fields and another for elements.
Revision 1 of the tentative agenda items is available at:
https://mentor.ieee.org/802.11/dcn/26/11-26-1114-01-0000-editors-agenda-15-june-2026.pptx
https://mentor.ieee.org/802.11/dcn/26/11-26-1114-01-0000-editors-agenda-15-june-2026.pptx
Regards,
Edward
On Thu, May 21, 2026 at 12:57 PM Edward Au <edward.ks.au@xxxxxxxxx> wrote:
Dear Editors,cc. Working Group participants,Hope all is well.As mentioned in my closing report of the Editors' meeting in the May 2026 wireless interim (see the snapshot below), we will organize a teleconference call from 12:00pm ET to 1:00pm ET on Monday, 15 June 2026, and discuss on the style guide related to "non-AP <entity> STA" vs. "<entity> non-AP STA". In particular, we will hear a presentation from Matt Fischer (thanks!) on his thoughts on this specific matter.Please kindly join our discussion if you may be interested.Regards,Edward
To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1