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

Re: [STDS-802-11-TGM] Teleconference reminder: June 14 @ 10am ET, re 21/0871 (Rejected Groups in SAE)



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

a.        Document 11-21/871 – Dan (HPE) – Rejected Groups in SAE

 

I have the following comments on this submission:

 

- Is the "shall" going to result in any existing devices becoming

noncompliant?

 

- "Each rejected group shall be represented as an unsigned 16-bit integer using the bit ordering conventions of 9.2.2 (Conventions)."

does not belong in Clause 12, and is already covered in Clause 9

(specifically 9.4.2.246->9.4.1.42->9.2.2).  The correct place is

Clause 9 because Clause 9 is for format/encoding and other clauses

are for behaviour.

 

- I think "in response to rejection of a previous SAE Commit message with status code set to UNSUPPORTED_FINITE_CYCLIC_GROUP"

is unclear.  Is it the previous SAE Commit message that carries that SC,

or is it the rejection of that SAE Commit message that carries that SC?

And what does “a previous” mean here?  Does it mean “the immediately previous”?

 

- I suggest the wording could be made more straightforward and

consistent as follows:

 

12.4.7.4 Encoding and decoding of SAE Commit messages

 

An SAE Commit message shall consist ofinclude a Finite Cyclic Group field (see 9.4.1.42 (Finite Cyclic Group field)) indicating a group, a Scalar field (see 9.4.1.39 (Scalar field)) containing the scalar, and an FFE field containing the element (see 9.4.1.40 (FFE field)). If the SAE Commit message is in response to an Anti-Clogging Token field request (see 12.4.7.6 (Status codes)), the an Anti-Clogging Token field is presentshall be included (see 9.4.1.38 (Anti-Clogging Token field)). When the PWE is derived using the hash-to-element method, the Anti-Clogging Token field is encapsulated in an Anti-Clogging Token Container element; otherwise, the Anti-Clogging Token field is included in the frame outside of an element as described in Table 9-41 (Presence of fields and elements in Authentication frames). If a password identifier is used in generation of the password element (PWE) the a Password identifier element shall be presentincluded and the identifier shall be encoded as a UTF-8 string in the Identifier portion of the element (see 9.4.2.216 (Password Identifier element)). If an SAE Commit message with status code set to SAE_HASH_TO_ELEMENT is being sent in response to rejection of a previous SAE Commit message with status code set to UNSUPPORTED_FINITE_CYCLIC_GROUP[MR1] , the group that was rejected shall be appended, after the rejected groups from previous attempts if applicableany, to the Rejected Groups field of the Rejected Groups element (see 9.4.2.246 (Rejected Groups element)). Each rejected group shall be represented as an unsigned 16-bit integer using the bit ordering conventions of 9.2.2 (Conventions). If the status code of thean SAE Commit message with status code set tois SAE_HASH_TO_ELEMENT is being sent and if any groups have been rejected during the current SAE session, the Rejected Groups element shall be present, otherwise it shall not be present.

 

[The first change has been made in 21/0871r1 but I can't work out how

to edit it in this email!]

 

Thanks,

 

Mark

 

--

Mark RISON, Standards Architect, WLAN   English/Esperanto/Français

Samsung Cambridge Solution Centre       Tel: +44 1223  434600

Innovation Park, Cambridge CB4 0DS      Fax: +44 1223  434601

ROYAUME UNI                             WWW: http://www.samsung.com/uk

 

From: M Montemurro <montemurro.michael@xxxxxxxxx>
Sent: Friday, 11 June 2021 16:21
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] Teleconference reminder: June 14 @ 10am ET

 

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Hi all,

 

Just a reminder that we have a teleconference scheduled for Monday June 14 at 10am ET. The agenda for the call can be found here:

 

Cheers,

 

Mike


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


 [MR1]Is it the previous SAE Commit message that carries that SC, or is it the rejection of that SAE Commit message that carries that SC?  And what does “a previous” mean here?  Does it mean “the immediately previous”?  Otherwise what does it mean (assuming no time-travel)?


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

--- This message came from the IEEE 802.11 Task Group M Technical Reflector --- ÿþ<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=unicode"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 15"> <meta name=Originator content="Microsoft Word 15"> <link id=Main-File rel=Main-File href="cid:.htm@01D76125.E5F26030"> </head> <body lang=EN-GB link=blue vlink=purple> <div style='mso-element:placeholder-text' id=C6D270A7CEDC41D19D8CE6C555EDC0D5><span class=MsoPlaceholderText><span style='font-size:11.0pt;font-family:"Calibri",sans-serif; mso-ascii-theme-font:minor-latin;mso-fareast-font-family:"Yu Gothic"; mso-fareast-theme-font:minor-fareast;mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";mso-bidi-theme-font:minor-bidi; color:gray;mso-ansi-language:EN-GB;mso-fareast-language:JA;mso-bidi-language: AR-SA'>Click or tap here to enter text.</span></span></div> </body> </html>

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