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

Re: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

Hi GeonHwan,

 

Thanks for your information. However, as I mentioned, single protection also introduces collision, which may not be better than ‘over protection’.

 

BR,

Chaoming

 

发件人: 김건환 <geonhwan.kim@xxxxxxx>
发送时间: 2024年11月21日 13:33
收件人: 罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
抄送: 조한규 리더님 <hg.cho@xxxxxxx>
主题: RE: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

Hi Chaoming,

This is GeonHwan Kim from LG Electronics.

 

Before Sanket’s response, I would like to respond to your question based on my knowledge.

 

Regarding what you mentioned as "multiple protection mechanisms", I covered that topic in my contribution (24/227).

If there are multiple polled APs sending responses, an overprotection problem (extensive range of protection) occurs.

To prevent this problem, single protection mechanism can be used.

 

Best Regards,

GeonHwan Kim

LG Electronics

 

From: 罗朝明(Chaoming Luo) [mailto:000015d97e832564-dmarc-request@xxxxxxxxxxxxxxxxx]
Sent: Thursday, November 21, 2024 12:31 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

Hi Sanket,

 

A follow up question: how does it work if the ICF sent at the beginning of the TXOP uses single protection mechanism under EDCA (as indicated by “The Duration field of the frame is set to the length of time required to transmit the solicited response frame plus one SIFS”)?

According to the baseline, the STAs associated with the TXOP owner AP will resume to contend the medium after the response frame, since the basic NAV counts down to zero at that time.

IMHO, we need to use multiple protection mechanism under EDCA for a TXOP that contains multiple frame exchange sequences.

 

Please help correct me if I missed anything you’ve discussed.

 

BR,

Chaoming

 

发件人: 周培 <zhoupei36@xxxxxxxxx>
发送时间: 2024年11月21日 10:12
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

Hi Sanket,

 

Thank you for preparing this PDT. I have attached some minor edits based on Chaoming's revision.


Best regards,

Pei Zhou

TCL

 

 

罗朝明(Chaoming Luo) <000015d97e832564-dmarc-request@xxxxxxxxxxxxxxxxx> 于2024年11月21日周四 10:00写道：

Hi Sanket,

 

My2cents attached.

 

BR,

Chaoming

 

发件人: Sanket Kalamkar <000033b8f79f2eb4-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间: 2024年11月21日 6:01
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

Dear Co-TDMA TTT members,

 

We made significant progress on Co-TDMA during the November IEEE meeting, with six motions being passed. Based on these motions and the feedback received on r0 (many thanks to Brian Hart!), I have prepared an initial draft of r1 of the PDT.

 

Attached to this email, you will find both the redline and clean versions of the initial draft of r1 of the PDT. This draft also includes some additional text that I believe is a straightforward extension of the passed motions.

 

I kindly request your comments and suggestions within the next 24 hours, by 2pm Thursday (Pacific Time).

 

Additionally, I have attached my point-by-point responses to Brian’s comments on r0.

 

Best,

Sanket Kalamkar

 

From: Brian Hart (brianh) <00000c7561051aea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 19, 2024 10:02 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi Sanket

 

Many thanks for kicking this effort off! My comments attached.

 

Best wishes

Brian

 

 

Cisco Confidential

From: Sanket Kalamkar <000033b8f79f2eb4-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, November 14, 2024 5:19 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] PDT-MAC-C-TDMA

 

This is the initial email for:

 

Proposed Draft Text for C-TDMA

 

As the PoC for C-TDMA, I have created the initial PDT document 11-24-1961r0 for C-TDMA. This document includes proposed text based on the motion passed until September 2024. We will update the PDT as additional motions are passed. The current version r0 is at a very high level, based on just one motion.

 

The author list in r0 is based on the 1:1 TTT requests received to me after the TGbn Chair’s guideline to send TTT request to PoCs. The author list will be updated based on the list of members in the TTT for C-TDMA (about 80 members) mentioned in the document by Ross 11-24/1698r12. If you wish to be removed from the TTT or the current (and future) author list, please e-mail me at sankal@xxxxxxxxxxxxxxxx. I will update the author list accordingly in the next revised version (r1).

 

Please send any comments on the draft text (excluding the author list) in 11-24-1961r0 to this e-mail thread. This allows all TTT members to see and discuss your comments, facilitating debate on any changes to the document. This will be our general process for including text in the document.

 

At some point, as the group passes more motions to C-TDMA, we will try to find volunteers to create draft text sections corresponding to those motions. Depending on the size/complexity of that text, it should appear for discussion within this e-mail thread either as:

  1. Text included directly in an email (for small additions/changes)
  2. Text in a new WORD document sent as an attachment (not an official 802.11 submission)
  3. Text in a copy of the 11-24/1961rx WORD document showing additions and changes, attached to the email thread.

 

We will aim to discuss any new proposed draft text within this thread and reach a super-majority agreement (e.g., 75% of the TTT membership). However, even 75% is challenging due to the fluid nature of TTT membership. Deciding when to close the debate on new text will be a judgment call, typically when objections reduce to a small number (e.g., less than 25%, or about 15-20 people). If objections persist, we may need to conduct a straw poll in TGbn and update our document 11-24-1961rx based on the outcome. Future text additions will follow a similar process, aiming for super-majority agreement.

 

Thank you for your cooperation.

 

P.S. You might have noticed that the guidelines in this e-mail are straight from Matthew Fischer's playbook. Thanks, Matt—it saved me a ton of time and probably a few gray hairs!

 

Best,

Sanket Kalamkar

 

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

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

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