1 / 8

Discussion on Secured Connectivity in 802.11af

Discussion on Secured Connectivity in 802.11af. Date: 2011-06-20. Authors:. This document presents the discussion on the topic of secured connectivity in 802.11af

Download Presentation

Discussion on Secured Connectivity in 802.11af

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Discussion on Secured Connectivity in 802.11af Date: 2011-06-20 Authors: Chin-Sean Sum, NICT

  2. This document presents the discussion on the topic of secured connectivity in 802.11af This document opens up the RLQP and examine the necessity to provide further explanatory text or to modify Draft 1.0 in the course of facilitating a secured link establishment Summary Chin-Sean Sum, NICT

  3. O1: To address the requirements on secured connectivity between the STAs and the RLS • O2: To identify the existing security framework and protocols that may be used to establish a secured link for cross-referencing in Draft 1.0 • O3: To identify necessary modifications to Draft 1.0 in order to facilitate the establishment of a secured link • Focus of discussion: • Are the objectives addressing a necessary topic? • In O2, are the related existing security standards correctly referenced? • In O3, is the intent to modify Draft 1.0 necessary? Objective of this Document Chin-Sean Sum, NICT

  4. Reference: 802.11af Draft 1.0 • The RLQP enables a requesting STA (e.g. a non-AP STA) to obtain available channels from the database (utilizing the RLS) through a responding STA (e.g. an AP-STA) • Connectivity from the requesting STA to the responding STA to the RLS is required to be secured in certain regulatory domains • Example: in the US, FCC 10-174 paragraphs 96 to 100 on security • RLS may be a logical entity located within the responding STA • RLS may also be an entity separated from the responding STA by the DS Background Chin-Sean Sum, NICT

  5. RLQP Overview~ Illustration ~ DS Query Request Responding STA RLS GAS Initial Request GAS Initial Response Query Response Requesting STA Database Chin-Sean Sum, NICT

  6. Connectivity between requesting STA and responding STA is within the scope of 802.11af MAC/PHY specifications Medium is wireless Security is covered by 802.11-2007 Chapter 8 (IEEE 802.11i) Discussion point No additional specification is needed for secured link establishment On Secured Link Establishment~ Requesting STA - Responding STA ~ Chin-Sean Sum, NICT

  7. Connectivity between responding STA and RLS are further categorized into: • Case 1: RLS may be a logical entity within the responding STA • Case 2: RLS may be an entity separated from the responding STA by the DS • RLS may or may not be an 802.11 AP-STA • Discussion points • For Case 1, no security specification is needed • For Case 2, secured link can be established through specifications in other standards • Provide to Draft 1.0, an explanatory sub-clause/annex referencing the related standards On Secured Link Establishment~ Responding STA – RLS ~ Chin-Sean Sum, NICT

  8. To establish a secured link (e.g. through wired connection) between responding STA to RLS, existing upper layer specifications can be used • Multiplexing among different security protocols can be achieved by employing existing specification in the upper data link layer (logical link control sub-layer ) • Security framework and protocols for wired link in 802 systems can be found in, example the 802.1 networking protocols • Thus, an explanatory sub-clause/annex may be added to Draft 1.0 to connect all the dots of these existing standards • Refer to the word file DCN 11/879 for the proposed text Case 2~ More Details ~ Chin-Sean Sum, NICT

More Related