| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Arik, Thanks for providing updates after the call in r3, and for the great work on this! Some additional comments from my side: On the subclause structure: I do not think that the ‘split’ in level 37.7.x (Common and Particular) is particularly needed (the split would be quite clear even without these as ‘separators’), but if majority prefers to
keep it I can live with it. Reference text 1 This
Comments 1:
Reference text 2: access point identifier: [AP ID] A value used for identifying an AP Comments 2: I do not know if the assignment info is going to be delivered within the request for a feature agreement, the response, or some other previous or later step. Since we do not have this level of
clarity in agreements, (an also in definitions it is ok to be more succinct and have the protocol level details in the related subclause), I believe it is better to avoid this text in the definition. Reference text 3: “The
Multi-AP Coordination feature includes a set of schemes and procedures in which OBSS APs coordinate their transmission to improve communication reliability.”
Comments 3: Seems it would be convenient to have an acronym for Multi-AP coordination, e.g., [MAPC], which you already use in Table 9-64. Suggesting the following definition: “Multi-AP coordination: [MAPC] a framework that includes a set of features including Co-BF, Co-SR, Co-TDMA, and Co-RTWT and procedures for OBSS APs to coordinate their transmissions and improve
communications reliability.” This definition can be considered to revise the first sentence in 37.7.7.1. Thanks again, Best, Giovanni From: Arik Klein <0000177967a59511-dmarc-request@xxxxxxxxxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hello everyone, Thanks for the further comments I’ve received from Jiayi, Robbe, Haorui, You-Wei, I’ve updated the proposed draft text document for the Multi-AP Coordination framework (r2) in the following link: https://mentor.ieee.org/802.11/dcn/24/11-24-2049-02-00bn-pdt-mac-m-ap-coordination-framework.docx Please let me know if you have any further comments. Regards, Arik From: Arik Klein Hello everyone, Happy New Year ! Thanks for the useful comments I’ve received from Jay, Xiaofei and Giovanni, I’ve updated the proposed draft text document for the Multi-AP Coordination framework (r1) in the following link: https://mentor.ieee.org/802.11/dcn/24/11-24-2049-01-00bn-pdt-mac-m-ap-coordination-framework.docx Your comments and feedback are highly appreciated. Regards, Arik From: Arik Klein <0000177967a59511-dmarc-request@xxxxxxxxxxxxxxxxx>
Hello everyone, Please use this thread to start the discussion on the M-AP Coordinated framework. The initial version of the proposed draft text document can be found here:
https://mentor.ieee.org/802.11/dcn/24/11-24-2049-00-00bn-pdt-mac-m-ap-coordination-framework.docx Your comments are appreciated. Regards, Arik 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 |