| Hi Alice,
Thank you for the reply. The paragraph above Table 9-46a in 9.3.1.22.1 (refer to 11-25/442r2) is about how to determine the variant of the user info field. Just mentioned in separate subclauses.
If your purpose is to explain how to use PHY version Identifier subfield to interpret the variant of Common info field, then it is better to have both Common info field and User info field in one place. It will be better if you can add a column in Table 9-46a for Common info field variant since they are not always the same as User Info field variant depending on B54, B55 and B39 values.
Thanks Yan On May 6, 2025, at 9:28 AM, Alice Jialing Li Chen <jialing.li.phd2@xxxxxxxxx> wrote:
Hi Yan,
Thanks for your questions/comments. Please see my replies below.
1) The paragraph above Table 9-46a in 9.3.1.22.1 (refer to 11-25/442r2) is about how to determine the variant of the user info field. Just mentioned in separate subclauses.
2) We'll relocate that subclause of the feedback user info field to 9.3.1.22.7. The contents of that subclause is under preparation by another group of contributors.
3) You're right. Will correct it.
Regards, Hi Alice,
Thank you for preparing the document.
I have some questions on 634r0.
1) on Page 6, "The PHY Version Identifier subfield indicates the variant of a Common Info field that is not an HE variant, and [#3273, 2091]the PHY version of the solicited TB PPDU that is not an HE TB PPDU. The PHY Version Identifier subfield is set to 0 for EHT or and is set to 1 for UHR. The values from 12 to 7 are reserved.” I am not clear why PHY Version Identifier subfield only indicates the variant of a Common Info field that is not an HE variant, but not the variant of User info field.
2) I am ok that you rename user info field with STA AID 2008 to Feedback User Info field. But I don’t see any contents in the new subclause “9.3.1.22.12.1 Feedback User Info field”. Are you going to add the contents later?
3) Table 9-46i—AID12 subfield encoding, for STA AID 0 or 2045 RA-RU, I think it is not applicable for EHT/UHR variant. It is not allowed in EHT, please check 11be spec.
Thanks Yan
Dear all,
The following PDT-CR documents on the Trigger frame will be presented in a TGbn Joint call in the IEEE May meeting. Could you please review and let me know if you have any comments and questions? Your timely feedback is much appreciated! - 11-25/442r2 Part 1 to resolve CIDs in 9.3.1.22 and 9.3.1.22.1
- 11-25/634r0 Part 3 to resolve CIDs in 9.3.1.22.3
- 11-25/636r2 Part 5 to resolve CIDs in 9.3.1.22.7 – 9.3.1.22.9
- 11-25/637r2 Part 6 to resolve CIDs in 9.3.1.22.10 – 9.3.1.33.16
Two more PDT-CR documents on the Trigger frame are under preparation. Will let you know when they are ready. - 11-25/633r0 Part 2 to resolve CIDs in 9.3.1.22.2
- 11-25/635r0 Part 4 to resolve CIDs in 9.3.1.22.6
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|