| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Dibakar, Thank you for your inputs. >> However, the design doesn’t allow changing one profile in the list without making changes to all. Maybe its simpler to just not have the Control field and replace the Traffic Profile List with an
SCS Descriptor element. That way each profile will have an SCSID to identify it.
I don’t want to add complexity to the design to optimize the signaling. These will be infrequent individually addressed mgmt. frames exchanged between two MAPC APs. If we were to add some form of flow identifier,
then we would need to include an ‘action’ or ‘operation’ field to indicate whether a traffic profile is being added, removed, or updated. Instead, the framework let an AP provide the latest information for all the traffic profiles that it wants to be considered
for MAPC sharing. >> Maybe rather than entering the debate to say which fields are reserved etc., its simpler to extend the Direction field value 2 (currently corresponding to Direct Link) to also be for MAPC when included
in MAPC Mgt frames and make corresponding updates to the text in clause 9. I reviewed clause 9 and found that there are specific actions tied to Direction == 2 which won’t apply to MAPC. It will cleaner if we call out which fields are present and if so how to interpret them when
carried in a MAPC frame.
From: Das, Dibakar <dibakar.das@xxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Abhi, Thanks for preparing this document. Few quick comments:
Regards, Dibakar From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi MAPC TTT members, I have prepared the following CR document that addresses several comments related to traffic indication between APs. The proposed resolution introduces a flexible and extensible framework that allows an AP
to convey its traffic info to a peer AP. A coordinating AP can then consider such information when making decisions related to TXOP sharing (poll/invite). The framework also includes a mechanism that enables an AP to update its traffic info whenever changes
occur. Could you please review the following doc and let me know if you have any suggestions? Hi
@Alfred Asterjadhi, can you please help queue this document to the TGbn MAC agenda? Regards, Abhi 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 |