| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi all,
CID 159 and CID276 in 1369r2 are defered from last call. Let's have some discussion in this mail loop and make the decision to address them.
CID276:
As the commenter said, we define dot11DeviceID in Annex C but never use it in the normative text.
To address the commenter's concern,one approach is to remove the defination of dot11DeviceID from Annex C.
Another approach is to have some text change in subclause 9 and And in subclause 12.2.11.1(in red font) as bellow, I would like to know our group's preference.
" The Device ID field contains a device ID dot11DeviceID or an opaque identifier (see Annex AD.1)."
"Assign a new device ID value dot11DeviceID in Device ID field, and set Device ID Status field of Device ID KDE or Device ID element to 0 to indicate that AP recognizes the non-AP STA in the appropriate frame."
"When an AP with dot11DeviceIDActivated equal to true receives a first PASN frame containing a device ID which is recognized,the AP shall assign a new device ID value dot11DeviceID to the non-AP STA,via setting a new device ID in Device ID field with the Device ID Status field of Device ID element set to 0 to indicate that the AP recognizes the non-AP STA in the second PASN frame."
276
27/61
dot11DeviceID is not referenced in body text
Either add that the Device ID field contains the ID from dot11DeviceID here and add behavioral text (probably in clause 12) that sets the attribute when a Device ID is received at a non-AP STA, or remove the MIB attribute from Annex C.
Revised--
CID 159:
Based on the commenter's suggestion, I think we need change to description in the note as bellow(in red font):
9.3.3.5 Association Request frame format/9.3.3.6 Association Response frame format/9.3.3.7 Reassociation Request frame format/9.3.3.8 Reassociation Response frame format
Order Information Notes
Device ID If dot11DeviceIDctivated is true and dot11FILSActivated is true,the Device ID element is optionally present when using FILS
authentication; otherwise, it is not present.
63
IRM
If dot11IRMActivated is true and dot11FILSActivated is true, the IRM element is optionally present when using FILS authentication;
otherwise, it is not present.
Best Regards
Jay Yang (杨志杰)
Wi-Fi Standard Research Engineer
ZTE Corporation
R&D Building I, No.899 Bibo, Pudong District, Shanghai, P. R. China
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