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

Re: [STDS-802-11-TGBH] 24/0898r5



Yes, but that seems OK

 

Please see attached.  I have made a few edits, which I think are necessary.

 

Please look at my changes and hopefully post as r6.

 

Thanks

Graham

 

From: Okan Mutgan (Nokia) <okan.mutgan@xxxxxxxxx>
Sent: Thursday, June 20, 2024 4:04 PM
To: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>; li.yan16@xxxxxxxxxx
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: 24/0898r5

 

Hi Graham,

 

For that, I believe that we need IRM support in RSNXE in Assoc Req/Resp, no?

 

BR,

Okan

 

From: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 20, 2024 10:01 PM
To: Okan Mutgan (Nokia) <okan.mutgan@xxxxxxxxx>; li.yan16@xxxxxxxxxx
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: 24/0898r5

 

 

CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

 

Hi Okan,

Thanks for posting.

I spotted just one error.  In Figure AX-7 in the bottom exchange 4-way HS M4, you need to add (IRM(IRM3))

 

Thanks

Graham

 

From: Okan Mutgan (Nokia) <okan.mutgan@xxxxxxxxx>
Sent: Thursday, June 20, 2024 11:41 AM
To: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>; li.yan16@xxxxxxxxxx
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBH] TGbh D4.0 Example Texts and Figures

 

Hi,

 

@Graham, thanks for the figures.

@Yan Li,

  1. Fixed.
  2. Fixed (using round brackets always to keep it simple)
  3. We need EAP or 4W HS in initial connection in FILS. When returning, no EAP or 4W HS is needed (the figure seems to be correct)
  4. Done.
  5. Done.

 

I will upload the document and talk about it today.

 

Thanks!

BR,

Okan

 

From: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 20, 2024 4:34 PM
To: li.yan16@xxxxxxxxxx; Okan Mutgan (Nokia) <okan.mutgan@xxxxxxxxx>
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-11-TGBH] TGbh D4.0 Example Texts and Figures

 

 

CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

 

Excellent.  Thanks Li Yan.  I admit I concentrated on getting the device ID  + PASN ID right (and compatible with your proposal) and did not pay too much attention to the rest of the diagrams.

So it’s great that you did!

 

Okan,

Are you OK with making these changes?  As you know we have only today to get this sorted.  I think we are good with Li Yan’s proposal, so we just need your Annex to be good to go.

 

Thanks

Graham

 

From: li.yan16@xxxxxxxxxx <li.yan16@xxxxxxxxxx>
Sent: Thursday, June 20, 2024 5:15 AM
To: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>
Cc: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBH] TGbh D4.0 Example Texts and Figures

 

Hi Graham and Okan,

    I find some minor issues about the figures attached:

    1.  a typo for Asociationshould be Associationin figure 1 and 4

    2. some editorial issues about brackets, please keep the round and square brackets matched

    3. In figure 2(DevID FILS), i think we don't need EAP or 4-HS if FILS used, given that FILS authen/assoc frame exchange has already established PTKSA(see P3097L10 REVME_D4.2)

 

    4. In figure 3, you may ignore to remove PASN ID support in the beacon/probe response transmitted from AP-2(i see the frame from AP-1 is correct)

    5. I'm confused about the introduction of the content of 'initial connection' in figure 1 and 3.  In figure 1, initial connection is 4-HS, so it's correct to say No device ID. But in figure 3, initial connection is PASN authen. In my opinion, it's enough to say No PASN ID. Please remove the phrase ‘No device ID’

     

 

Best Regards

李炎 Li Yan

 

Original

From: GSmith <gsmith@xxxxxxxxxxxxxxxxxxx>

Date: 20240620 03:41

Subject: Re: [STDS-802-11-TGBH] TGbh D4.0 Example Texts and Figures

Hi Okan,

Here attached are the “corrected” figures for Device ID and the joint IRM/Device ID. 

The IRM figures are correct and I have not touched them.

 

These figures now comply with the device ID/PASN ID proposal as per 24/0789r7.  (I have sent edits on this document to Li Yan)

 

All that remains is make the text agree with the figures :>)  Hopefully that should not be difficult.

 

I was confused by the last figure as it jumped form 4w HS to PASN and back.  I simply made it a combined 4w HS example.  I don’t think we need to mix PASN as well.  If doing PASN, and using IRM I can’t think of any possible reason why a STA would also try to use PASN ID. 

 

Thanks

Graham

 

From: Okan Mutgan (Nokia) <okan.mutgan@xxxxxxxxx>
Sent: Wednesday, June 19, 2024 2:34 PM
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Cc: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx>; Yang.zhijie@xxxxxxxxxx; li.yan16@xxxxxxxxxx; Joseph Levy <Joseph.Levy@xxxxxxxxxxxxxxxx>; Mark Hamilton <mark.hamilton2152@xxxxxxxxx>
Subject: [STDS-802-11-TGBH] TGbh D4.0 Example Texts and Figures

 

Hi all,

 

As we discussed in the call today, to move forward, Graham volunteered to modify the example figures and text (thanks a lot Graham) for this submission.
Jay and Yan Li, as well as others, are also welcome to put any input.

 

Thanks!

 

BR,

Okan


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

Attachment: 11-24-0898-05-00bh-sa-cr-for-cid3131- GS Edits raise to r6.docx
Description: 11-24-0898-05-00bh-sa-cr-for-cid3131- GS Edits raise to r6.docx