Hi Alfred,
Please add the following two motions to the PHY motions queue:
- Move to add the following rules for Co-BF in the TGbn spec in
37.15.2.1.4 Co-BF transmission procedure?
- If the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame corresponds to Navbits > 3888 bits for a user of the coordinated AP, then the coordinated
AP may indicate that 2xLDPC will be used for the user in the Co-BF Response frame.
- If the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame corresponds to Navbits ≤ 3888 bits for a user of the coordinated AP, then the coordinated
AP shall not indicate that 2xLDPC will be used for the user in the Co-BF Response frame.
- A coordinating AP shall not choose a value for the Length field in the L-SIG field of the Co-BF PPDU in the Co-BF Trigger frame that corresponds to a number of OFDM symbols in the
Data field which is smaller than the minimum number of data OFDM symbols the coordinating AP had indicated in the Co-BF Invite frame
Note: These changes for the TGbn editor are reflected in the word document below
https://mentor.ieee.org/802.11/dcn/25/11-25-1670-00-00bn-2x-ldpc-related-spec-text-changes-for-cobf.docx
Supporting documents: 11-25/1609r2 and 11-25/1670r0
SP result: Passed unanimously
- Move to add the following recommendation for Co-BF to the TGbn spec in
37.15.2.1.4 Co-BF transmission procedure?
- To help the coordinated AP choose an appropriate LDPC codeword length, the minimum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame should be greater
than or equal to 0.5 times the maximum number of data OFDM symbols of the Co-BF transmission indicated in the Co-BF Invite frame.
Note: These changes for the TGbn editor are reflected in word document below
https://mentor.ieee.org/802.11/dcn/25/11-25-1670-00-00bn-2x-ldpc-related-spec-text-changes-for-cobf.docx
Supporting documents: 11-25/1609r2 and 11-25/1670r0
SP result: Passed unanimously
Thanks,
Sameer