[CID18 and CID111 Resolution for LB274]
![[CID18 and CID111 Resolution for LB274]](https://cdn1.slideorbit.com/296353/september-2023-n.jpg)
This document, authored by Okan Mutgan from Nokia, addresses the resolutions related to CID18 and CID111 within the IEEE 802.11-23/1427r2 standard. It provides insights into these resolutions, contributing valuable information to the field of wireless communications.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
September 2023 doc.: IEEE 802.11-23/1427r2 [CID18 and CID111 Resolution for LB274] Date: 2023-08-27 Authors: Name Okan Mutgan Affiliations Nokia Address Phone email okan.mutgan@nokia- sbell.com Submission Slide 1 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 Abstract This document proposes a solution to address CID18 and CID111, which are about non-AP STA to non-AP STA identification. Rev.0 initial version Rev.1 device ID removed, only IRM left, IRM action frame usage rather than TDLS action frame usage. Rev.2 IRM action frame usage modification Submission Slide 2 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 CID18 and CID111 Two CIDs about communication between non-AP STAs CID 18 Comment two non-AP STA commnucation is improtant, and widely used in Wi-Fi industry, like Wi-Fi Mirocast . But one STA to identify another STA with RCM via IRM is missing,11bh SPEC should add this part support. D1.0 does not address some of the scenarios such as TDLS. Proposed Change add non-AP STAs' identification with RCM 111 If applicable, add support for IRM and/or device ID in TDLS. Submission Slide 3 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 Recap: TDLS TDLS (Tunnel Direct Link Setup) enables at least two non-AP STAs to communicate with each other (while they are associated) to the same AP (ESS) Submission Slide 4 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 Recap: TDLS TDLS uses action frames (called TDLS Action frames). These frames are encapsulated in data frames so they are protected, such as: This is seen in the air (Encrypted Data Frame) This is the real content in the encrypted Data Frame Submission Slide 5 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 What CID18 and CID111 want? The current 802.11bh D1.0 only addresses AP (ESS) to identify the non-AP STA. It does not address a (non-AP) STA identifying the other (non-AP) STA in the same ESS for TDLS. Example: STA1 (e.g., phone) AP STA2 (e.g., TV) Association Association Initial Connection (device ID/IRM allocation) TDLS connection (device ID/IRM allocation) TDLS connection AP identifies STA1 and STA2 Association Association Next Connection (device ID/IRM usage) TDLS connection (device ID/IRM usage) TDLS connection STA1 and STA2 don t identify each other Submission Slide 6 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 Proposal to address CID18 and CID111 Each STA provides IRM to the other STA in IRM Action Frame. In the initial connection, STA1 and STA 2 associate with AP (IRM allocation for AP) TDLS initiator (e.g. STA1) sends its IRM to TDLS responder (e.g. STA2) in IRM Action Frame. TDLS responder (e.g. STA2) sends its IRM to TDLS initiator (e.g. STA1) in IRM Action Frame. In the next connection, STA1 and STA 2 associate with AP (IRM usage so that AP identifies them) STA1 and STA2 identify each other in TDLS based on IRM provided in the initial connection. Submission Slide 7 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 STA1 has IRM1 STA2 has IRM2 STA1 provides IRM1 to STA2 via AP STA2 provides IRM2 to STA1 via AP Submission Slide 8 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 Further Consideration [1392r5] already defines IRM Action Frame. It might be better to add another action value for TDLS connection. Action field value 0 1 2 3-255 Meaning Duplicate IRM New IRM IRM for TDLS Reserved IRM for TDLS Action Frame Format: MAC Header Category IRM Action RA=AP TA=STA1 RA=STA2 TA=AP IRM Peer STA s MAC STA1 s IRM STA2 s MAC STA1 -> AP STA2 s MAC STA1 s IRM AP -> STA2 Submission Slide 9 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 SP1 Q: Do you think 802.11bh should address identification between two non-AP STA s? Yes, No, Don t care, Abstain Submission Slide 10 Okan Mutgan, Nokia
September 2023 doc.: IEEE 802.11-23/1427r2 SP2 Q: Do you think the proposal in this document (IRM exchange with IRM Action Frame for TDLS connection) is a good way to address STA to STA identification for TDLS ? Yes, No, Don t care, Abstain Submission Slide 11 Okan Mutgan, Nokia
