Hi Li-Hsiang,
That’s right.
Thanks,
Duncan
From: L. S. <lsun2005@xxxxxxxxx>
Sent: Thursday, September 24, 2020 10:55 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] 答复: [STDS-802-11-TGBE] PDT-MLO-Setup-Security
CAUTION: This email originated from outside of
the organization.
Just want to get a clarification on 12.5.3.3.7 in 20/1445r2, whether the change on PTKSA applies.
If non-AP MLD must support GCMP-256, then its RSNE in association request will have one pairwise cipher suite which is GCMP-256 (otherwise how to test non-AP MLD
really supports it?). In this case GCMP-256 must be used for unicast data traffic?
Li-Hsiang Sun (interdigital)
Hi Duncan,
I’m trying to understand the MLD-level RSNE and individual RSNE mentioned in your annotation in Page 7. What
do you mean MLD-level RSNE? In my understanding, each AP affiliated with the AP MLD reuses the current RSNE. I don’t see what’s the problem. Could you explain it?
Regards
Guogang Hang
Hi Duncan,
While I think I understand your intentions, if I just read the text below (on page 16), since IGTK KDE and BIGTK KDE are explicitly mentioned,
it doesn’t convey that the MLO KDEs are to be used for the other links. I would think it is good to explicitly specify the MLO KDEs where necessary to avoid confusions.
…,
the IGTK KDE of each setup link, and if beacon protection is enabled, the
BIGTK KDE(#2116) for each setup link,
Also, format of the MLO KDEs are defined but their usage is not referenced anywhere else in your PDT, so it is not clear where they are
used.
Regards,
Rojan
Hi Rojan,
Thanks for the comments. I corrected the 1st one. Re the second one, my thought is the AP MLD is still carrying the actual GTK/IGTK/BIGTK
values of each link, just carried in different KDEs i.e., the regular “GTK KDE” is used on the link where the 4way handshake is performed and the “MLO GTK KDE” is used for the other links. Similarly for IGTK and BIGTK.
Thanks,
Duncan
CAUTION:
This email originated from outside of the organization.
Hi Duncan,
Two additional comments:
Page 14:
The LinkID field contains the link identifier that corresponds to the link this GTK applies.
The KeyRSC field contains the Key RSC field that corresponds to the
STAlink
for which this GTK applies (see Table 12-8 (Key RSC field).
Page 16:
—
For generating a single PTK between a non-AP MLD associated with an AP MLD, the AP’s Beacon/Probe Response frame’s RSNE for the current operating band, and,
optionally, a second RSNE that is the Authenticator’s pairwise cipher suite assignment for the current operating band, and, if a group cipher has been negotiated,
the GTK and the GTK’s key identifier (see 12.7.2 (EAPOL-Key frames)) of each setup link (see (see 33.3.2 (Multi-link (re)setup procedure), and if management frame protection is negotiated,
the IGTK KDE of each setup link, and if beacon protection is enabled, the
BIGTK KDE(#2116) for each setup link, and when this message 3 is part of a fast BSS transition initial mobility domain association or an association started through the FT protocol, the PMKR1Name calculated
according to the procedures of 12.7.1.6.4 (PMK-R1) in the (#2205)PMKID List field of the RSNE and the FTE with the same contents as in the (Re)Association Response frame, the MDE with the same contents as in the (Re)Association Response frame, the reassociation
deadline timeout set to the minimum of dot11FTReassociationDeadline and the key lifetime in the TIE[ReassociationDeadline], and the PTK lifetime in the TIE[KeyLifetime]
I think the highlighted sentences should say the newly defined MLO … KDEs and not GTK/IGTK/BIGTK KDE right?
Hi Rojan,
Thanks a lot for reviewing the doc in details! Really appreciate it.
I’ve accepted/addressed all your comments (attached) but please let me know if I’ve missed anything or you have further comments.
Thanks,
Duncan
CAUTION:
This email originated from outside of the organization.
Hi Duncan,
Thanks for preparing the PDT. Attached please find my comments.
Hi Alfred,
Could you please help me queue this to the Agenda of the MAC calls?
Thanks,
Duncan
CAUTION:
This email originated from outside of the organization.
Hi MLO-Setup-Security TTT members, and all,
I’ve uploaded 1445r0
here. Please let me know if you have any questions or comments.
Thanks,
Duncan
CAUTION:
This email originated from outside of the organization.
Hi Soft-AP TTT members,
Thanks for volunteering for Soft-AP operation as TTT.
I uploaded 1407r0 on the server. Please review and comment.
Thanks,
Kaiying
Hi Edward,
I would like to volunteer for the following topics as TTT
* MLO-Multi-link channel access: STA ID
* Enhanced multi-link operation mode
* Soft AP MLD operation
Best Regards,
Sanghyun Kim
Sanghyun Kim, Ph.D
WILUS Inc.
5th Fl., 216 Hwangsaeul-ro Bundang-gu,
Seongnam-si Gyeonggi-do 13595, Korea
T +82 31 712 0523
www.wilusgroup.com
-----Original Message-----
From: "Edward Au"<edward.ks.au@xxxxxxxxx>
To: <STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx>;
Cc:
Sent: 2020-09-06 (일) 01:23:40 (GMT+09:00)
Subject: [STDS-802-11-TGBE] Revision 32 (note on the 3 recent new TTTs in case you're interested) - IEEE802.11be D0.1 Spec Text Writing: Volunteers Assignment
Revision 32 of the volunteers assignment is posted at:
[1] an addition of another new TTT,
[2] updated status of selected PDT texts
NOTE - the 3 recent new TTTs are
MAC
|
MLO-Multi-link channel access: STA ID
|
Yongho Seok
|
|
R1
|
Uploaded:
Presented:
Straw Polled:
|
Motion #122, #SP160
Motion #122, #SP161
|
MAC
|
Enhanced multi-link
operation mode
|
Young Hoon Kwon
|
Duncan Ho, Xiandong Dong
|
R1
|
Uploaded:
Presented:
Straw Polled:
|
Motion #124, #SP187
|
MAC
|
Soft AP MLD operation
|
Kaiying Lu
|
Jinjing Jiang
|
R1
|
Uploaded:
Presented:
Straw Polled:
|
Motion #125
|
Revision 31 of the volunteers assignment is posted at:
[1] an addition of a new TTT,
[2] an update on the name of an existing TTT,
[3] an update on the status of select PDT texts, and
[4] inclusion of new motions for selected TTTs.
Revision 30 of the volunteers assignment is posted at:
[2] the confirmation on R1/R2 on selected TTTs
Revision 29 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 9:45am ET today (September 3).
Revision 28 of the volunteers assignment is posted at:
[1] additional text submissions that have been uploaded to the mentor till
12:50pm ET today (September 2),
[2] presentation and approval status of selected PDT texts up to the MAC ad-hoc
call today, and
[3] update on the list of motions of a few TTTs.
Revision 27 of the volunteers assignment is posted at:
[1] additional text submissions that have been uploaded to the mentor till
12:15pm ET today (September 1),
[2] presentation and approval status of selected PDT texts,
[3] additional TTT volunteer assignments, and
[4] update on the list of motions of a few TTTs.
Revision 26 of the volunteers assignment is posted at:
[1] additional text submissions that have been uploaded to the mentor till 5:15pm
ET today (August 31), and
[2] presentation status of PDT texts.
Revision 25 of the volunteers assignment is posted at:
[1] additional text submissions that have been uploaded to the mentor till
4:00pm ET today (August 28), and
[2] additional approved motions to a few TTTs.
Revision 24 of the volunteers assignment is posted at:
[1] additional text submissions that have been uploaded to the mentor till 10:30pm
ET today (August 28),
[2] additional TTT assignments,
[3] additional approved motions to a few TTTs, and
[4] presentation status of PDT texts.
Revision 23 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 10:15am ET today (August 28).
Revision 22 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 6:40pm ET today (August 27).
Revision 21 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 9:45am ET today (August 27).
Revision 20 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 9:45am ET today (August 26).
Revision 19 of the volunteers assignment is posted at:
This version includes additional text submissions that have been uploaded to
the mentor till 11:15pm ET today (August 25).
Revision 18 of the volunteers assignment is posted at:
This version includes the 15 PDT text submissions and 4 visio files that have
been uploaded to the mentor since the last revision.
Revision 17 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 6:00pm ET today
(August 23). I've also added a column about the status of the PDT text(s) per topic.
Revision 16 of the volunteers assignment is posted at:
This revision incorporates all the inputs we have discussed during the Joint
call today (August 20).
Revision 15 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 11:40am ET today
(August 19).
Revision 14 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 11:30am ET on
August 14 (today).
Revision 13 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 3:15pm ET on
August 9 (today).
Revision 12 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 4:00pm ET on
August 6 (today).
Revision 11 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 9:15am ET on
August 5.
Revision 10 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 9:30am ET on
August 1.
Revision 8 of the volunteers assignment is posted at:
This revision incorporates all the inputs I have received till 19:45 ET today
(July 29).
Revision 7 of the volunteers assignment is posted at:
https://mentor.ieee.org/802.11/dcn/20/11-20-0997-07-00be-tgbe-spec-text-volunteers-and-status.docx
Revision 6 of the volunteers assignment is posted at:
Per our WG chair's message on July 20, if you are a POC on a particular topic,
please send an e-mail to Alfred and me with a list of motions that are expected to be covered by that topic (some of them already include this information as provided by respective POCs).
A revised version of the document is uploaded with POCs for topics narrowed down to one
(unless requested to be ON HOLD). I narrowed down the POCs for certain rows for which I did not see any e-mail or conclusion. Please take a look at the document and let me know if anything is missing.
Also, if you are a POC on a particular topic, please send an e-mail to Edward and me with
a list of motions that are expected to be covered by that topic (some of them already include this
information as provided by respective POCs).
--
Qualcomm Technologies Inc.
Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
|
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
*********** MEDIATEK Confidentiality Notice ***********
The information contained in this e-mail message (including any
attachments) may be confidential, proprietary, privileged, or
otherwise exempt from disclosure under applicable laws. It is
intended to be conveyed only to the designated recipient(s). Any
use, dissemination, distribution, printing, retaining or copying
of this e-mail (including its attachments) by unintended recipient(s)
is strictly prohibited and may be unlawful. If you are not an
intended recipient of this e-mail, or believe that you have received
this e-mail in error, please notify the sender immediately
(by replying to this e-mail), delete any and all copies of this
e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person. Thank you!
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
|