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

Re: [STDS-802-11-TGBH] CID3016, CID3122

Hi Jay,

 

Good catch.  Yes, I agree the other locations are correct.

Please do change the resolutions.

 

Thanks

Graham

 

From: Jay Yang <yang.zhijie@xxxxxxxxxx>
Sent: Wednesday, June 19, 2024 10:41 PM
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBH] CID3016, CID3122

 

Hi Graham, Mark, all,

 

For the resolution on the following CIDs, some member remind me we need do the same change in other places as well,like subelement and KDE for both Device ID and IRM. Because the status field of the subelement and KDE refer to the status field of the element defined in subclause 9.4..2.X

3016

Smith, Graham

27/32

As the Device ID Status filed is omitted when sent from non-AP STA to AP, the Octets should be "0 or 1".

At 27.33 under "Device ID Status" change "1" to "0 or 1"

Accepted--

3122

DeLaOlivaDelgado, Antonio

28

/16

The IRM status length is 0 or 1, for coherence we should have the same as in the status of device ID, which is always present but reserved in one direction.

Either change device ID Status length to 0 or 1 (and say it is not present) or change IRM status to 1 and indicate it is reserved.

Revised--

At 27.33 under "Device ID Status" change "1" to "0 or 1"

 

The proposed NEW resolution for both CIDs:

 

1)  At 27.33,29.52, 40.28, under "Device ID Status" change "1" to "0 or 1"

2) At 30.4, 40.46  under "IRM Status" change "1" to "0 or 1"

 

Welcome more thought on this.

 

Thanks

 

Best Regards

 

Jay Yang (杨志杰)

 

 

To unsubscribe from the STDS-802-11-TGBH list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBH&A=1

To unsubscribe from the STDS-802-11-TGBH list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBH&A=1