| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello everyone, I presented the 26/0486r0, which proposes a rejection reason for Co-RTWT negotiation, during the TGbn MAC teleconference on June 22. Please refer to the attached file for the details. This document describes how the MAPC responding AP can indicate the reason for rejecting the RTWT schedule requested by the MAPC initiating AP through a new field. This indication may help the initiating AP better understanding the rejection reason and adjust the requested RTWT schedule accordingly in a subsequent negotiation. The new field may be defined in either of the following ways:
n Based on Giovanni’s comment, Option 1 is applicable only when the MAPC Scheme Type field is set to 3 (Co-RTWT scheme) same as Option 2. So, the normative text in 37.14.1.4 (MAPC agreement negotiation) will be removed in next version of 26/0486.
The name and length of the new field are open for further discussion. (Kiseon recommended “Rejection Reason Code field”.) At this stage, I am considering Option 1 as the baseline approach. However, I would appreciate your feedback on whether Option 1 is appropriate or if Option 2 would be preferable. If you have any comments, questions or a preference between option 1 and option 2, please let me know. Looking forward to hearing from you. Best Regards SunHee Baek 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 |
Attachment:
11-26-0486-00-00bn-lb291 mac cr for Co-RTWT negotiation rejection reason.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document