doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 1 Emergency Call Setup Procedure Notice: This document has been prepared to assist IEEE 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. ieee802.org/guides/bylaws/sb-bylaws.pdf Date: Authors:

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 2 Abstract Frame exchange diagram for Emergency Call Setup process of an u-capable STA. This is an informative presentation summarizing some of the work which has produced other normative text for inclusion within the IEEE u draft. Diagrams developed at February 2007 TGu/ Ad Hoc Meeting (San Jose, California, USA)

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 3 AP (11u-capable) STA (11u-capable) Carrier Network VLAN #5 Note: There does NOT need to be a 1-to-1 mapping between this and SSID #5. Architecture IEEE Information Server AAA DHCP SSID #5

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 4 AP (11u-capable) STA (11u-capable) Configured by Hotspot owner / administrator Beacon (ESN) Association request (SSID : Foo) Association Response (…) EAP Success (include PMK) delay Emergency Call : ESR Case EAPOL/EAP-Response/Identity (e.g. EAPOL/EAP-Request/Identity 4-Way Handshake

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 5 AP (11u-capable) STA (11u-capable) Beacon (SSID: Foo, ESO bit) Association request (SSID : Foo) Association Response (…) Emergency Call : ESO Case

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 6 Event Flow Step 1: Get on network –Crypto (EAPOL required) vs clear –ESO (anonymous) vs ESN (public credentials) Step 2: Get location –Currently liaising with 11v about location provision for Emergency calls. –Which format (geospatial/civic)? See RFC 3619 (privacy protection issues) Step 3: Place call –Authentication again, at app layer –Network design impact: restrict calls to emergency dispatch only –Establish media stream

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 7 Emergency Call with IS

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 8 Questions and notes NAI or ESR (Emergency Service Realm) Well known format, assigned by hotspot administrator or by AAA configuration (AP MIB?) –e.g sos.dot11.org Need ESR text. Update to Annex P? –ESR is used to route authentication request to the right AAA server, but ESR will be replaced with NAI How do we ‘officially’ change this? –msg’s – ESR -> ESN –objects – restricted / colorful? EAP primitive (EAP native) messages can possibly be used –a new EAP method that would be a "null" authentication but enable derivation of a PMK –transmitting the PMK in an EAP message –standardizing a pre-shared PMK for all emergency calls.

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 9 Additional Notes 1 Beacon Management Frames –AP’s BSSID –SSID – Foo –ESSID (or WIID) –Interworking Capability IE (ESO) –GAS Capability IE

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 10 Layer Parameters L2 ACLs: SA, DA, ET, Pri, ULAN ID L3 ACLs: SA, DA, DSCP, SP, DP, IPP

doc.: IEEE /0270r2 Submission March 2007 Matthew Gast, Dave StephensonSlide 11 AP QoS Parameters Use T/FMax Rate AC - VOT~160 kbps VIF BET~100 kbps BKF