| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Dibakar,
Regarding the first bullet, I have requested Alfred and Ross to transfer the CID to Abhi and dequeue the document.
Thank you for pointing out so that we can focus on 26/1906.
Best Regards,
Jungjun Kim
--------- Original Message ---------
Sender : Das, Dibakar <dibakar.das@xxxxxxxxx>
Date : 2026-01-16 06:10 (GMT+9)
Title : Re: [STDS-802-11-TGBN] MAPC TTT - please review (1906 - semi-static traffic indication)
Hi Abhi,
Thanks for preparing this document. Few quick comments:
There seems to be another contribution that is working on a similar problem. While both propose similar solution, its easier to track only one doc. https://mentor.ieee.org/802.11/dcn/26/11-26-0145-01-00bn-lb291-cr-for-qos-information-exchange-in-co-tdma.docx
The Traffic Profile subelement is independent of Per-Scheme Profile.
keeping the traffic indication independent from the actual mechanism used to satisfy this is reasonable.
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.
Reusing the QoS Characteristics element to signal traffic requirements is preferable than creating a new element/field to allow future extensions and also not bloat spec text. For the changes to QoS Characteristics element to support this, I think the QoS Characteristics with Direction = Direct Link already covers almost all the parameters necessary for MAPC ( trigger periodicity, priority, medium time). 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.
Regards,
Dibakar
|
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
|
|
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
