Re: [STDS-802-11-TGBN] [EXT] Re: [STDS-802-11-TGBN] CID 18627 in 11-26/1765

[Liwen Chu <liwen.chu@xxxxxxx>]

But if most members prefer to reject the CID, I can reject it.

 

Best Regards,

Liwen

 

NXP Confidential

From: Liwen Chu
Sent: Wednesday, October 21, 2026 11:45 AM
To: Yongho Seok <yongho.seok@xxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] Re: [STDS-802-11-TGBN] CID 18627 in 11-26/1765

 

Hi Yongho,

 

Although subclause 9 defines the coding requirement, it is not guaranteed that a non-AP STA will always send the request with the valid parameters. That is why the baseline spec includes many valid related sentences, and the spec defines various rules defining what happens if the invalid frames are received.

 

Best Regards,

Liwen

 

From: Yongho Seok <yongho.seok@xxxxxxxxx>
Sent: Wednesday, October 21, 2026 10:49 AM
To: Liwen Chu <liwen.chu@xxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXT] Re: [STDS-802-11-TGBN] CID 18627 in 11-26/1765

 

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button

 

Hi Liwen, 

My preference is to reject, as the encoding requirements in Clause 9 already apply. Under Clause 9 requirements, a non-AP STA already includes only valid parameter values in the Mode Tuple field.

 

Best regards,

Yongho Seok 

 

2026년 10월 20일 (화) 오전 9:29, Liwen Chu <liwen.chu@xxxxxxx>님이 작성:

Hi Gaurang and all,

 

You and some other members have the concern of the valid parameters being used in the following text

(#18627) A non-AP MLD that enables or updates a mode through a UHR OMP request shall include valid parameters in the Mode Tuple field corresponding to the mode in the UHR OMP request.

It seems valid field are widely used in baseline spec, e.g.

            ……A STA that receives at least one frame in a PSDU can update its NAV with the information from any valid Duration field in the PSDU…..

            ……VHT-MCS = valid value, NUM_STS = valid value in the MFB subfield, MFSI in the range 0 to 6:….

            ……CMMG-MCS = valid value, NUM_STS = valid value in the MFB subfield, MFSI in the range……

 

So the text change to #18627 should be ok. If you have the different opinion, please provide the text change suggestion.

 

Best Regards,

Liwen

 

 

NXP Confidential

---

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