Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Mark, The proposed text for CID 16 is uploaded(https://mentor.ieee.org/802.11/dcn/23/11-23-0459-00-00bh-cr-for-cid16.docx), please help revie and put it
in the queue. BTW, I found the resolution for CID16 overlap with CID32, how to handle such case? In my humble opinion, we should put the two CIDs in one document and provide the uniform resolution. What’s your thought, Mark, and Antonio? Thanks Best Regards Jay Yang From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Thanks, Jay. Note that we already have the Device ID in the frames. It is just the MLME primitives to be updated (I believe), and just for the FILS situation, so you can mirror the FILS-only information that
is currently there. I think that applies to both MLME-AUTHENTICATE and perhaps MLME-ASSOCIATE (and Reassociation flavor) primitives. Mark From: Zhijie Yang (NSB) <zhijie.yang@xxxxxxxxxxxxxxx>
Hi Mark, For CID 16, I understand device ID just a new parameter in MLME-association. Request/confirm frame,etc., if so, I can volunteer on CID 16. Thanks Best Regards Jay Yang From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx>
All, I have uploaded an update to the TGbh comment resolution/tracking spreadsheet, here:
https://mentor.ieee.org/802.11/dcn/22/11-22-0973-16-00bh-cc41-comments-against-d0-2.xlsx
Please everyone review these updated CIDs, to make sure the resolution is right/ready for motion (other than filling in the final document rev number): 8, 12, 15, 17, 27, 45, 47, 58, and 63. A few notes:
Mark 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 |