Discussion on CID2199 Date: Authors: Jan 2014 Name Company

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0509r3 Submission Proposed Resolution to CID 72, 119 and 128 Qian ChenSlide 1 May 2014 Date:
Advertisements

Submission doc.: IEEE 11-10/0259r0 March 2013 Jarkko Kneckt (Nokia)Slide 1 CID 266 & CID 281 Date: Authors:
Doc.: IEEE /0782r2 Submission Proposed Resolution to CID 120 Slide 1 July 2014 Qian Chen.
Doc.: IEEE /0433r0 SubmissionSlide 1 Date: Presenter: MAC Protocol to Support Dynamic Bandwidth for aj (60GHz) Xiaoming Peng.
Doc.: IEEE /0041r1 AP Location Capability January 2007 Donghee Shim et alSlide 1 AP Location Capability Notice: This document has been prepared.
Doc.: IEEE /1291r0 SubmissionSlide 1 Date: Presenter: Dynamic Bandwidth Control for aj (60GHz New Technique Proposal) KB Png.
TBTT Information Field Type (TIFT) Clarification for P802.11REVmd
EDMG Capability and Operation Element Channel Indications
Power Save Delivery for 11ay
doc.: IEEE <doc#>
11ay Features and Design Principles
Multiple BSSID and MU Date: Authors: Nov 2016 Liwen Chu
Asymmetric beamforming training procedure enhancements
Dynamic Generation of Password Identifier
Multi-band Discovery Assistance
Multi-band Discovery Assistance
Discovery Assistance for ay
OCT based 6 GHz AP Operation Discussion
QoS Resource Query Overview
BRP frame exchange in TDD SP
Multi-band Discovery Assistance for ay (CR on CID 1771)
QoS Resource Query Overview
Multi-BF Procedure for 11ay
FILS Reduced Neighbor Report
Doc.: IEEE /XXXr0 10 May 2011 Sep 19, 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title:
AP Location Capability
Resolution for CID 118 and 664 Date: Authors: Month Year
Proposed resolution of CID 3518
Proposed resolution of CID 3518
Proposed resolution of CID 3518
June 2006 doc.: IEEE /0851r0 June 2006 LB84 Frame Format Ad-hoc Comment Resolution CID# 701, 7239, 9979, 3773, 7127 Date: Authors:
Multi-band Discovery Assistance for ay (CR on CID 1771)
Adding control trailer to control mode PPDUs
Discovery Assistance for ay
Backward Compatibility Feature for aj
doc.: IEEE /454r0 Bob Beach Symbol Technologies
Protection Assurance Method
Solution for 40MHz in 2.4 GHz band
Discussion on CID2199 Date: Authors: Jan 2014 Name Company
MAC Protocol to Support Dynamic Bandwidth for aj (60GHz)
Multi-BF Procedure for 11ay
Centralized Clustering Resolution to CID 127
Backward compatibility of 11aj with 11ad
TGai FILS: GAS/ANQP Signaling Reduction
Protection Assurance Method
Centralized Clustering Resolution to CID 127
Generalized Multi-Beamforming for 11ay
LB97 Coex: Duplicate DSSS
April 2009 doc.: IEEE /xxxxr0 July 2010
Synchronization related comment resolution
CR for CID 1115 Date: Authors: May 2019
EDMG Support Discovery
Timing Measurement Date: Authors: Jan 2010 November 2007
Proposed resolution of CID 3518
doc.: IEEE <doc# >
doc.: IEEE <doc# >
Month Year doc.: IEEE yy/xxxxr0 November 2013
Non-AP STA Location Capability
11ay Features and Design Principles
BSS Transition with Bearing
Multi-band comments resolution
Month Year doc.: IEEE yy/xxxxr0
Timing Measurement Date: Authors: Jan 2010 November 2007
Proposed Resolution to CID 147 in CC12
On the Need for an ai Annex
Greenfield protection mechanism
SM Power Save for 11ay Date: Authors: August 2017
Request for Legacy IE ID for RSN Extension
Scheduling Allocations Over Multiple Channels
Element definitions do not need to list frames
Presentation transcript:

Discussion on CID2199 Date: 2014-01-11 Authors: Jan 2014 Name Company Sept 2012 doc.: IEEE 802.11-012/xxxxr0 Jan 2014 Discussion on CID2199 Date: 2014-01-11 Authors: Name Company Address Phone Email Carlos Cordeiro Intel Carlos.Cordeiro@intel.com Carlos Cordeiro Xiaoming Peng / I2R

CID2199 and goals for this presentation Jan 2014 CID2199 and goals for this presentation 2199 10.3.4.1 1411 32 Section 10.3.4.1 states that DMG STAs do not support authentication and deauthentication. This appears to be an optimisation that should only apply to cases where the Open Authentication algorithm is used, otherwise 11ad STAs cannot make use of other authentication algorithms such as SAE, Fast BSS Transition and those in 11ai. Even when Open Authentication is in use I'm not sure how multi-band operation is affected by this restriction. Restrict this optimisation to cases where the Open Authentication algorithm is in use. This will require also changes in other parts of the draft, such as Figure 10-12 which shows authentication and association states. The purpose of this presentation is to discuss a conceptual resolution to this CID Text contribution would be crafted after TG agreement Carlos Cordeiro

Implications of rejecting the comment Jan 2014 Implications of rejecting the comment As noted by the commenter, by not supporting authentication and deauthentication, “11ad STAs cannot make use of other authentication algorithms such as SAE, Fast BSS Transition and those in 11ai” Such algorithms could be beneficial for DMG in the future, even though today we do not see market demand Carlos Cordeiro

Jan 2014 Proposed resolution 1 Proposed resolution along the following lines: change the last sentence of 10.3.4.1 as follows “Authentication and deauthentication are not supported by DMG STAs when the Open System Authentication algorithm is in use. The value of the Authentication Algorithm Number field within Authentication frames transmitted by a DMG STA shall be different than 0.” More changes needed in other places in the spec (De)Authentication frames and associated behavior would become mandatory in DMG when Open System Authentication is NOT in use This would cause interoperability problems with legacy 11ad STAs, assuming there are STAs using algorithms other than Open System Authentication Also need to add a capability field indicating whether a STA is using Open System Authentication Carlos Cordeiro

Jan 2014 Proposed resolution 2 An alternate resolution might be to define authentication and deuthentication as an optional capability of DMG STAs This would allow implementations to make use of the capability without breaking interoperability with legacy STAs that implement other algorithms other than Open Authentication (assuming they exist) Carlos Cordeiro

Proposed resolution 2 Jan 2014 Define a new “Authentication Supported” capability as part of the DMG Capabilities element If set to 0 (default), the STA does not support (de)authentication. Legacy STAs would use this configuration If set to 1, then the DMG STA supports (de)authentication and can then make use of existing authentication algorithms. A DMG STA with Authentication Supported=1 is capable of operating with a DMG STA with Authentication Supported=0 A DMG STA with Authentication Supported=1 would be allowed to perform (de)authentication with a peer STA only if the peer STA also has Authentication Supported=1 DMG STA B (Responder) Authentication Supported = 0 Authentication Supported = 1 DMG STA A (Initiator) (De)Authentication not performed, i.e., legacy behavior (De)Authentication may or may not be performed Carlos Cordeiro

Some additional implications of the proposed resolutions Jan 2014 Some additional implications of the proposed resolutions Resolution 1 Resolution 2 Backward compatible to 11ad No Yes State machine (10.3) description needs to be amended to accommodate new behaviour for DMG STAs In a DMG BSS (where the PCP/AP supports (de)authentication), some STAs might use (de)authentication and some might not A DMG STA needs to first discover the (de)authentication capability of a peer DMG STA before initiating (de)authentication with that peer DMG STA Can be done through DMG Beacon and/or probe exchange Carlos Cordeiro