Re: [STDS-802-11-TGBN] discussion on 25/1935 for SCS

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

Hi,

Its done. https://mentor.ieee.org/802.11/dcn/25/11-25-1935-02-00bn-cr-scs.docx

Regards,

Dibakar

From: huangguogang <000017b1384624cd-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Sunday, December 7, 2025 6:36 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] 答复: discussion on 25/1935 for SCS

Hi Dibakar,

To avoid the misleading, could you keep the following paragraph in your CR document? Because I see your instruction is “update the following subclauses as shown below”. Thanks!

Regards

Guogang Huang

发件人: Das, Dibakar <dibakar.das@xxxxxxxxx>
发送时间: 2025年12月8日 10:28
收件人: huangguogang <huangguogang1@xxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: RE: discussion on 25/1935 for SCS

Hi Guogang,

I don’t remove the text from the spec. I am trying to show only the text that contains the changes relative to draft 1.1.

Regards,

Dibakar

From: huangguogang <huangguogang1@xxxxxxxxxx>
Sent: Sunday, December 7, 2025 5:30 PM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: 答复: discussion on 25/1935 for SCS

Hi Dibakar,

I object to remove the existing text on the QoS Map element without any reason or discussion. Previous discussion is only whether to apply it to the DL case. In this email thread, I also didn’t see people express the concern on including the QoS Map element for the UL.

Regards

Guogang Huang

发件人: Das, Dibakar <dibakar.das@xxxxxxxxx>
发送时间: 2025年12月8日 2:01
收件人: huangguogang <huangguogang1@xxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: RE: discussion on 25/1935 for SCS

Hi all,

I revised the doc 1935 for some CIDs. Please review. If no further comments I want to run SP on those CIDs tomorrow.

https://mentor.ieee.org/802.11/dcn/25/11-25-1935-01-00bn-cr-scs.docx

Note: I removed all CIDs that touch on the QoS Map related text. We probably need a FTF discussion to converge on them.

Regards,

Dibakar

From: huangguogang <000017b1384624cd-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 25, 2025 7:01 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] 答复: discussion on 25/1935 for SCS

Hi Dibakar,

Sorry for jumping in. I think Yan’s comment is correct. The purpose of the additional TID mechanism which is used to address HOL issue is to separate a SCS stream from other traffic. Otherwise, why do we need to define the additional TID mechanism in 11bn??? Remember that the baseline already allows multiple streams can be mapped to the same TID within 0-7 even without defining the additional TID mechanism.

And I copy the following text from the spec although it is about TID 8-15. Based on the following text, each TS has a dedicated TID within 8-15. BTW, that’s why the spec. names TID 0-7 as Traffic Category (TC) and names 8-15 as Traffic Stream (TS).

Regards

Guogang Huang

发件人: Das, Dibakar <dibakar.das@xxxxxxxxx>
发送时间: 2025年11月26日 0:06
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] discussion on 25/1935 for SCS

Hi,

“addtional TID is per SCS stream, which means other SCS stream can not use same addtional TID if such TID has been used”

That’s not true in general for SCS regardless of the additional TID aspect. When you setup SCS for any TID-x, there is no rule in baseline preventing that TID from being used for another traffic.

[HGG]It is true for the pre-UHR SCS mechanism. For the pre-UHR SCS mechanism, the intention is to map a SCS stream to a specific TID within 0-7. There is no intent to separate this SCS stream from other traffic.

Of course, it makes practical sense to dedicate that TID to the negotiated SCS stream only as much as possible. However, we leave it to the implementation to make that decision.

[HGG] In essence, TID 0-7 are shared by different traffic. For the QoS STA, the traffic will be mapped to a TID based on the DSCP-to-UP rules (which is signaled through the QoS Map element) if there is no additional TCLAS traffic filter and related TID mapping rule.

Regards,

Dibakar

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Tuesday, November 25, 2025 7:54 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] discussion on 25/1935 for SCS

Hi,

Both are allowed per the spec.

Regards,

Dibakar

From: li.yan16@xxxxxxxxxx <li.yan16@xxxxxxxxxx>
Sent: Tuesday, November 25, 2025 1:03 AM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: discussion on 25/1935 for SCS

Hi Dibakar,

Hope this could initialize discussion on 25/1935 for SCS

If i recall correctly, you have mentioned that addtional TID is per SCS stream, which means other SCS stream can not use same addtional TID if such TID has been used. However, the current spec missed such clarification and more normative text or note is needed.

My cid 4939 also refers to the similar case, where different SCS streams are set to same additional TID with different UPs that are mapped to same AC, for example:

SCS stream 1 (TID=0, UP=6) and SCS stream 2(TID=0, UP=7) are mapped to AC_VO, which follows 'All traffic that concurrently use the same additional TID shall belong to the same access category' in P271L18 of D1.1

Is the above case allowed? However, if different SCS streams can not use same addtional TID, please ignore my above question and a further question as below:

'All traffic that concurrently use the same additional TID shall belong to the same access category' seems ambiguous if addtional TID is per SCS stream

Best Regards！

Yan Li

Original

From: Das,Dibakar <dibakar.das@xxxxxxxxx>

To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>;

Date: 2025年11月12日 09:55

Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

Hi Alfred,

1935 is now available on mentor. Has 28 CIDs.

Regards,

Dibakar

From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Sent: Thursday, October 30, 2025 9:13 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

Hi Alfred,

Please add the following CR documents to the MAC queue:

11-25-1934 -CR for MAPC fairness – Technical (31 CIDs)
11-25-1935- CR for SCS related text – Technical (34 CIDs)

Regards,

Dibakar

From: Arik Klein <0000177967a59511-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, October 30, 2025 1:09 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

Hello Alfred,

Can you please help queue the following CR docs to the TGbn MAC agenda?

11-25/1912 LB291 - CR for MAPC element - Editorials 1 (14 CIDs)
11-25/1913 LB291 - CR for 37.15.1 MAPC common procedures - Editorials 2 (18 CIDs)

Regards,

Arik

From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: יום ד 29 אוקטובר 2025 23:10
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

Hi Alfred,

Can you please help queue the following CR docs to the TGbn MAC agenda?

11-25/1835 LB291: CR for CIDs assigned to Abhi - Part 4

11-25/1836 LB291: CR for CIDs assigned to Abhi - Part 5

Regards,

Abhi

From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
Sent: Monday, October 27, 2025 2:19 AM
To: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: 11bn LB291 CR request

Hi Alfred,

Can you please help queue the following CR docs to the TGbn MAC agenda?

11-25/1826 LB291: CR for CIDs assigned to Abhi - Part 2

11-25/1834 LB291: CR for CIDs assigned to Abhi - Part 3

Regards,

Abhi

From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, October 23, 2025 2:03 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

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

Hi Alfred,

Can you please help queue the following CR doc to the TGbn MAC agenda?

11-25/1825 LB291: CR for CIDs assigned to Abhi - Part 1

Regards,

Abhi

From: wangkaidong (E) <00004ea939387e7b-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, October 23, 2025 1:53 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

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

Hello Alfred,

Please help add the CR document to the MAC queue. It resolves 1 CID. Thank you!

23-Oct-2025 ET 2025 1859 0 TGbn 11bn LB291 CR for CID 4983 Kaidong Wang (Huawei)

Best regards,

Kaidong Wang

From: Fang, Juan <juan.fang@xxxxxxxxx>
Sent: Thursday, October 23, 2025 6:36 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request
Importance: High

Hi Alfred,

Please help to add following to the PHY queue, it has 8 CIDs.

22-Oct-2025 ET

2025

1837

TGbn

PHY-lb291-CIDs_subclause_38.3.15.12_ELR_SIG

intel

22-Oct-2025 18:29:52 ET

Download, Revise

Thanks,

Juan

From: Gaurang Naik <0000305a2f8ce933-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, October 22, 2025 2:59 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request

Hi Alfred,

Pls add the following to the MAC queue. It resolves 15 CIDs.

17-Oct-2025 ET

2025

1820

TGbn

LB291: CR for CIDs on UHR Parameters Update element - part 1

Gaurang Naik (Qualcomm)

All, please let me know if you have any feedback.

Thanks

Gaurang

From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Sent: Thursday, October 16, 2025 12:09 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>; ross.yujian@xxxxxxxxxx <ross.yujian@xxxxxxxxxx>
Subject: Re: 11bn LB291 CR request

Hi Alfred,

Please add the following CR document to the MAC queue. It resolves 23 CIDs.

2025

1816

TGbn

LB291: CR for CIDs on UHR Mode Change element - part 1

Gaurang Naik (Qualcomm)

Thanks

Gaurang

From: Yujian (Ross Yu) <00001792b51ef4ea-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, October 15, 2025 6:15 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGBN] 11bn LB291 CR request

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

Hi Alfred,

Please add the following CR documents into the queue, it contains 20 editorial CIDs.

https://mentor.ieee.org/802.11/dcn/25/11-25-1791-00-00bn-lb291-editorial-comments-part-1.docx

regards

于健 Ross Jian Yu

Huawei Technologies

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