Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBN] Updated P2P PDT

Hi Arik,

 

Thank you for your review.

 

Good catch. Clarified that “The Co-CR Agreement ID field is reserved when the corresponding MAPC element is carried in a MAPC Negotiation Request frame”. This should do.

 

Please kindly let me know if it looks good to you.

 

Best

Rubayet

 

From: Arik Klein <0000177967a59511-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, July 3, 2025 10:24 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Updated P2P PDT

 

Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hello Rubayet and Jonghoe,

 

Thanks for sharing the P2P PDT.

 

I have a clarification question regarding the Co-CR part:

I understand the Agreement ID is assigned by the Co-CR responding AP in the MAPC Negotiation Response frame.

However, the Agreement ID is included in the MAPC Per Scheme Info field of the Co-CR profile,  which is included in the MAPC Negotiation Request frame.

Can you please specify how the Agreement ID field is set (i.e. specific value? Reserved field?) when the MAPC Per Scheme Info field is included in the MAPC Negotiation Request frame? I have not fine any normative behavior in 37.13.2.5.2 clause.

 

Thanks for your swift response.

 

Regards,

Arik

 

From: Jonghoe Koo <jh89.koo@xxxxxxxxxxx>
Sent: יום ב 30 יוני 2025 15:59
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Updated P2P PDT

 

Hi Alfred,

 

Could you please indicate in the agenda that this document (P2P PDT doc 11-25/764) resolves 14 CIDs when adding it to the agenda?

The Abstract text box in the cover sheet of the uploaded document seems to be positioned in a way that obscures the list of CIDs that the document aims to address.

 

As attached, this document proposes resolutions for following 14 CIDs as part of CC50 comments:

229, 230, 849, 875 876, 1997, 2078, 2167, 2521, 2573, 3113, 3129, 3130, 3621

 

 

Dear all,

 

As shared by Rubayet and as described in the revision history of this document, we have made efforts to reflect as many technical comments as possible that we have received after the first version of the P2P PDT document was shared.

As part of these effort, numerous parts have been modified or removed.

We kindly request that members actively share your feedbacks on the revised contents as well, so that the document can undergo sufficient offline discussions and revisions before it is discussed.

Any editorial and/or technical comments would be greatly appreciated.

 

Regards,

Jonghoe KOO

Communications Standards Research Team, Samsung Research

Samsung Electronics

 

From: Rubayet Shafin <r.shafin@xxxxxxxxxxx>
Sent: Saturday, June 28, 2025 2:11 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Updated P2P PDT

 

Hi Alfred,

Could you please add P2P PDT doc 11-25/764 to the MAC queue for SP?

 

Dear P2P TTTs,

 

Hope you all are doing well. I wanted to share some updates on the P2P PDT. Based on extensive discussions and feedback received from numerous members, either offline, online, or F2F (thanks to you all!), I have made significant changes to address the comments. One major change is that provisioning-related procedures have been entirely removed from the TXSPG for simplicity and ease of implementation. On the other hand, the Co-CR is now harmonized with the MAPC framework PDT. A summary of the changes is as follows—

 

TXSPG--

  • Removed the Provisioning part and all provisioning-related procedures/frames/elements
  • Added the MIB variable for TXSPG
  • Added an entry for the definition of TXSPG in clause 3.2
  • Removed Mode-3 based TXOP allocation procedure. Added text to reuse mode TXS Mode-2
  • Added that only AP can assign the Group ID.
  • Removed the new Direction field value (3—P2P group) in the QoS characteristics element; re-using value 2 (Direct Link)
  • Added that only the TXSPG requesting STA can send the SCS request for the P2P group; 
  • Added that only the TXSPG requesting STA can return the TXOP
  • Added that TXSPG shall follow the TXS fairness rules introduced in 11bn for CTDMA
  • Changed the AID12 addressee to be the generic P2P group (AID12 = 2047);

Co-CR:

  • Harmonized the text with the MAPC framework PDT (11-25/599r16--Giovanni).
  • Moved to the subclause 37.13.2 (Procedures for specific multi-AP coordination schemes) the content of the detailed Co-CR operation between Co-CR requesting AP and Co-CR responding AP described in the subclause (Coordinated channel recommendation (Co-CR)) proposed by this document
  • As a part of Co-CR profile, specified the format of MAPC Per-Scheme Info field and the format of the Co-CR Parameter Set field that is contained in the MAPC Request Parameter Set field

 

The revised PDT can be found here and is also attached. I would appreciate it if you could review the document and let me know whether you have any comments on the revised PDT.

 

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

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