1. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 1 Joiint TGU-802.21: Emergency Identifiers Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2007-03-13 Authors:

2. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 2 Abstract Proposal to address the Emergency services related issues specifically for scenario where user has no security credentials Seek input if IEEE 802.21 information services can provide some support here

3. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 3 Emergency Support in IETF IETF –Assumes network access is made –Develops architectural framework and protocols for location and call routing to PSAP –Standardizes identifier for emergency, called URN used in SIP signaling

4. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 4 Emergency Support in TGu Capability advertisement –Emergency service support capability –Emergency services realm (to identify the default realm for authentication etc.) –Emergency services only indication to identify the SSID for open authentication for E911 only Network access –Open auth ssid for emergency use –Assumes a public identifier for EAP based dummy authentication to AS Establishing QoS for emergency calls –Expedited bandwidth request –Works regardless of type of network access authentication

5. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 5 Problem-1 FCC mandates that emergency calls must work in all possible cases –Users with no authentication credentials need to make emergency calls Currently, TGu considers two mechanisms i) Open authentication SSID, with no link security ii) 802.1x for RSN capable AP with or without link security For ii) the user must provide an identifier that AS can use to authenticate, problem when the user has no identifier to use, options: –Use a well-known/public identifier that is standardized elsewhere and provide a realm information to create a NAI together => where to standardize this id and use of realm is not clear or sufficient –IEEE 802.11 considered that this ID (NAI) can be configured by local network and provided in the beacon => can be long up to 253 bytes for RADIUS and much longer for DIAMETER

6. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 6 Problem-2 The identifier can be used for dummy authentication What about link security keys? How do we derive session keys needed for link security for E911? –but there are no long-term shared keys Usually, authentication method is determined by the AS/network provider -Do we need to standardize emergency auth methods? -Need something simple that is implemented in all STA -Error and failure recovery mechanisms when not supported

7. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 7 Possible Approach Avoid standardization for the identifiers and authentication methods Provide flexibility for networks or industry alliances to configure and provision to users, either for –link type basis or –service provider basis Provide a backend service to provide this information What can be provided for this use –Identifier for dummy emergency authentication – one or more Authentication types for emergency use Could 802.21 be utilized for this query?

8. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 8 802.21 IS to the rescue IEEE 802.21 IS framework is well-supported for pre- authentication queries IEEE 802.21 already supports emergency related information, additionally provide –the emergency identifier and auth types Downside is a point of failure in case of 9/11 kind of emergency If Tgu is okay with this approach, we can ask 802.21 for this support

9. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 9 Sequence Diagram STAAP 802.21 IS Get Information Req (Request for Emergency IE) State-1 Query Mechanisms Get Information Resp (Emergency IE ) Determine the AUTH support Authenticate Determine Location Information (may be after IP addressing info) Place an Emergency Call AS

10. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 10 Comments

11. doc.: IEEE 802.11-07/0448r0 Submission March, 2007 Srinivas SreemanthulaSlide 11 Conclusions Emergency identities and related support managed outside of 802.11 –802.11 will indicate only the IW capability Is this approach right? –If so, 802.21 can be asked to handle this Comments and Q&A