Thank you for the detailed document. I have the following concerns:
In the scenario you are considering, P2P STAs need to be associated with the same AP. This scenario seems too narrow and does not cover Wi-Fi Direct scenarios.
The STA acting as the STA leader may not be able to determine which AP other P2P STAs are associated with, or whether they are associated with an AP at all.
If the P2P Group ID is only used to distinguish traffic characteristics, does this mean that a single P2P communication could have multiple Group IDs? Then, as the traffic changes during communication, does the AP need to dynamically assign new Group IDs in real-time? This could add complexity to management. How does the AP decide when it needs to issue a new Group ID? Will the update of this Group ID be promptly communicated to each STA in the group?
How does the STA leader know the traffic requirements of other P2P STAs?
Compared to the gains from TXOP Group Sharing, the resource waste from the initial negotiation or real-time information collection process might be even greater.
Best Regards
Chun Huang
Original
From: RubayetShafin <r.shafin@xxxxxxxxxxx>
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>;
Date: 2025年05月04日 23:57
Subject: [STDS-802-11-TGBN] P2P PDT
Dear P2P TTT members,
I am attaching the PDT document for clause 37.16 (Peer-to-peer communications). It has two main subclauses—
37.16.1 on TXOP sharing for a group of P2P STAs
37.16.2 on Coordinated Channel Recommendation (Co-CR).
It would be great if you could review and provide your feedback.
Please feel free to reach out if you have any comments.
Best
Rubayet
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