| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
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 |