Hi Tomo,
Thank you very much for the review, and I am very sorry that I could not reply earlier due to travel.
I understand your comment. For now, maybe we can stick with the current motion text, and we can definitely revisit this based on how the general MAP framework (led by other PoCs) discussions converge. What do you think?
Best
Rubayet
From: Tomo Adachi <tomo.adachi@xxxxxxxxxxxxx>
Sent: Sunday, January 12, 2025 8:49 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] P2P PoC and PDT draft
|
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.
|
Thanks Abhi,
Yes, I remember this.
I thought it should be something like,
… by enabling coordination between APs that do not *even* belong to the same ESS
… , so that it is extended from the current limitation.
tomo
From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Sent: Monday, January 13, 2025 11:31 AM
To: adachi tomoko(足立
朋子 ○ＲＤＣ□ＩＴ研○ＷＳＬ)
<tomo.adachi@xxxxxxxxxxxxx>;
STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBN] P2P PoC and PDT draft
Hi Tomo,
The baseline spec already provides guidance for APs within the same ESS to coordinate their channel usage to facilitate p2p. Please see 9.4.2.84, table 9-268 (mode 2).
Regards,
Abhi
From: Tomo Adachi <tomo.adachi@xxxxxxxxxxxxx>
Sent: Friday, January 10, 2025 9:58 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] P2P PoC and PDT draft
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Rubayet,
Thanks for preparing the PDT for P2P.
Sorry to go back to the intention of the passed motion, but isn’t the restriction for the APs not belonging to the same ESS too strong?
It won’t allow to coordinate with the APs within the same ESS… Why not?
Best regards,
tomo
From: Rubayet Shafin <r.shafin@xxxxxxxxxxx>
Sent: Thursday, January 9, 2025 11:25 PM
To: Iñaki Val Beitia <ival@xxxxxxxxxxxxx>; huangguogang <huangguogang1@xxxxxxxxxx>; Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx>;
"全映桥 (Yingqiao Quan)"
<yingqiao.quan@xxxxxxxxxx>; VIGER Pascal <Pascal.Viger@xxxxxxxxxxxx>; Alfred Asterjadhi <aasterja@xxxxxxxxxxxxxxxx>;
Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>;
serkucuk@xxxxxxxxxx; Brian Hart (brianh) <brianh@xxxxxxxxx>; '장인선'
<insun.jang@xxxxxxx>;
ming.gan@xxxxxxxxxx; zhoupei36@xxxxxxxxx; adachi tomoko(足立
朋子 ○ＲＤＣ□ＩＴ研○ＷＳＬ)
<tomo.adachi@xxxxxxxxxxxxx>; Das, Dibakar <dibakar.das@xxxxxxxxx>; Sunshine Qi <sunshine.qi@xxxxxxxxxxx>; Binita Gupta (binitag)
<binitag@xxxxxxxxx>; Peshal Nayak <p.nayak@xxxxxxxxxxx>; Jiyang Bai <jiyangbai@xxxxxxxxx>; Kumail Haider <haiderkumail@xxxxxxxx>;
Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>; Liwen Chu <liwen.chu@xxxxxxx>;
Daniel.Verenzuela@xxxxxxxx; Jeongki Kim <jeongki.kim.ieee@xxxxxxxxx>; Sindhu Verma <sindhu.verma@xxxxxxxxxxxx>; Shubhodeep
Adhikari <shubhodeep.adhikari@xxxxxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx;
asterjadhi@xxxxxxxxx
Subject: [STDS-802-11-TGBN] P2P PoC and PDT draft
Dear Fellow P2P TTT,
With the motion on peer-to-peer (P2P) communication passing, I volunteer to be the PoC of the
P2P topic. Please find attached a PDT draft that I initiated, including all TTT members in 11-24/1698r14 in the author list. Your support and comments are appreciated!
Hi Alfred,
Upon TTT members' support, we plan to queue document 11-25/0088r0 (PDT MAC P2P) for presentation/SP/motion
in the January Interim, trying our best to make it to D0.1. Could you please add it to the MAC queue?
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