Re: [STDS-802-11-TGBC] Revised document for 12.15
Hello Bahar,
Thanks for the feedback.
> 1) Section 12.15.2.1
> My understanding is that
> Allowable time difference, Certificate of the AP, and the Signature
> in the eBCS info frame are not updated regularly, is that correct? Is it fair to assume that for most applications, they remain the same for length of a user session using the service?
Yes. Your understanding is correct.
> 2) Section 12.15.2.3
> In the following formula for the Signature,
> Signature = Sign(The eBCS transmitter’s private key, SHAKE128(Transmitter’s MAC address | /* to be determined */))
> why the same Signature as in DL is not used? It seems best to have the same definition for UL and DL data frames... Is there something that prevents "to be determined" to be set to "from the Sequence Number field to the last field before the Frame Signature Length field in the E-BCS DL frame"?
The reason is just because of not completed the frame format of the eBCS Info.
Best Regards,
—
Hitoshi MORIOKA
SRC Software Inc.
hmorioka@xxxxxxxxxxxx
> 2020/05/19 8:12、Sadeghi, Bahareh <bahareh.sadeghi@xxxxxxxxx>のメール:
>
> Hello Morioka-san,
>
> Thank you for the update to the document.
> It looks good to me and addresses my comment from last call. Thank you very much.
> To answer your comments embedded in the document:
> * Is timestamp check required for UL? I believe it is required only if the timestamp field is present in the frame.
> * The caching certificate is not required for the UL? Correct. I do not believe it is required.
>
> Not related to the UL case, I have also two questions. I apologize if they have been discussed previously in the group:
>
> 1) Section 12.15.2.1
> My understanding is that
> Allowable time difference, Certificate of the AP, and the Signature
> in the eBCS info frame are not updated regularly, is that correct? Is it fair to assume that for most applications, they remain the same for length of a user session using the service?
>
> 2) Section 12.15.2.3
> In the following formula for the Signature,
> Signature = Sign(The eBCS transmitter’s private key, SHAKE128(Transmitter’s MAC address | /* to be determined */))
> why the same Signature as in DL is not used? It seems best to have the same definition for UL and DL data frames... Is there something that prevents "to be determined" to be set to "from the Sequence Number field to the last field before the Frame Signature Length field in the E-BCS DL frame"?
>
> Thank you,
>
> -bahar
>
> -----Original Message-----
> From: Hitoshi MORIOKA <hmorioka@xxxxxxxxxxxx>
> Sent: Friday, May 15, 2020 9:43 PM
> To: STDS-802-11-TGBC@xxxxxxxxxxxxxxxxx; Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>; Sadeghi, Bahareh <bahareh.sadeghi@xxxxxxxxx>
> Subject: Revised document for 12.15
>
> Hi Abi, Bahar and all,
>
> I have uploded the revised document.
> https://mentor.ieee.org/802.11/dcn/20/11-20-0040-05-00bc-draft-text-for-12-15-security.docx
>
> I have written some comments about UL cases.
> If possible, please give me feedback before next telco.
>
> Best Regards,
> —
> Hitoshi MORIOKA
> SRC Software Inc.
> hmorioka@xxxxxxxxxxxx
>
>
________________________________________________________________________
To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1