Re: [STDS-802-11-TGBN] PDT C-TDMA fairness (address editorial issues)

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Hi Mark, all,

Please check this version if this works.

Note: I remove the “etc.” in the parentheses. I would like to keep the rest of the parentheses text to abide by the motion text. But I also heard some objection from Mark for this. In order to make progress, unless other members feel strongly, I am fine to delete it too.

Regards,

Dibakar

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Wednesday, May 14, 2025 12:30 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] PDT C-TDMA fairness (address editorial issues)

Hi Mark,

I got the following comments from you on 479r6 (and inline response):

"the procedure of time sharing during a TXOP" should be just "TXOP sharing": done
“first para says "etc." but second para only covers the two explicit examples” -> I am fine to remove this. But we heard from other members who wanted to keep it as well. Can we keep this to at least align with the general motion text (about the which left the door open for other protocols if needed ?
do we have the concept of a "TXOP owner AP"? -> with quick check for “TXOP owner” in REVme, I found no such instance. However, there is at least one instance of “AP is the TXOP owner”. We could align it to that but it becomes cumbersome. Are you okay with replacing instances of “TXOP owner AP” with “AP that is TXOP owner” everywhere ?
what does "primary AC" mean here? The AC of the EDCAF that won contention? -> other members pointed out during discussion the term exists in REVme. “primary access category (AC): [primary AC] The AC that is the AC of(#2030) the enhanced distributed

channel access function (EDCAF) that gains channel access.”

"performs either Co-TDMA or TXS mode 2 procedure" should be "performs either Co-TDMA or the TXS mode 2 procedure" -> done.
"data or management frame" should be "Data or management frame" -> think there instances in REVme where lower-case “management frame” is used. So, replaced “data” with “Data”.
delete "own" in "its own associated STAs" -> done.
"except if" does not need bullet: was trying to avoid a very very long sentence. Welcome to other wordings.
not clear what happens if "except if" case is true
"-72dBm" missing space
"in the range (-72dBm)" not clear -> please check the current text.
is it "C-TDMA" or "Co-TDMA" (or "CTDMA")? -> should be Co-TDMA everywhere now.
"AC VI" should be "AC_VI" -> done (think it was already the case in the text body)
why AC_VI and not AC_VO? -> that was discussed during the motion. The assumption was AC_VI typically has longer TXOP limit than AC_VO. And we wanted to set this limit big enough to accommodate both AC_VI and AC_VO traffic.

Please check the attached doc especially the ones related to the red part above.

Regards,

Dibakar

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Sunday, May 11, 2025 4:13 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Submission Request - TDBs and CR (52 CIDs) MAC resolution (doc 11-25/0627)

Hi Alfred,

Please add document https://mentor.ieee.org/802.11/dcn/25/11-25-0479-04-00bn-cr-for-cid-1378.docx to the MAC queue.

This was already presented once in telecon and includes some changes following offline discussion.

Regards,

Dibakar

From: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Sent: Sunday, May 11, 2025 1:07 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Submission Request - TDBs and CR (52 CIDs) MAC resolution (doc 11-25/0627)

Hi Alfred,

Please add document 11-25/0627 to the MAC queue

https://mentor.ieee.org/802.11/dcn/25/11-25-0627-07-00bn-cc50-cr-for-p-edca.docx

The document provide resolution for all remaining TBDs and contain resolution for 52 CIDs

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