doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide u and Emergency Services 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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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 /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 2 Abstract Introduction to u for the IEEE 802 emergency services ad hoc in San Francisco, CA in July Note: This presentation is based on u-D1.0 and subject to change by future standards activity.

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 3 Major Features of u External network (SSPN) interface for extended authorization New QoS features Generic Advertising Service (GAS) Emergency services recommendations (informative) –Use case #1: open network –Use case #2: public credentials

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 4 External Network (SSPN) Interface SSPN = Subscription Service Provider Network –SSP holds user credentials –May build or partner with access networks The SSPN may direct the STA-AN, for example by: –Requiring that a certain encryption type is used (e.g. CCMP only) –Setting allowed access rates for different types of traffic (e.g. 80 kbps voice, no video, and up to 500 kbps best effort) –Specifying a minimum delay bound on transmitted frames Admission Control –TSPEC processing is subject to authorized data rates as specified by SSPN

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 5 QoS Signaling in u Expedited Bandwidth Request – has only four categories (voice, video, best effort, and background) –Many STAs may request high-priority voice service –EBR allows a STA to describe the reason that it is requesting service and the network can act accordingly –Example: emergency calls and first-responder traffic can pre-empt normal voice traffic QoS Map – QoS settings only affect last-hop access; QoS Map allows APs and STAs to extend higher-layer QoS settings –Ensures correct QoS treatment of frames even if destination networks use DSCP differently

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 6 Generic Advertising Services (GAS) Interface to external information sources –Example: Carrier of data –Extensible for types beyond Native query mode –Assists STA with information stored in the access network –Example: enhances scan for multi-SSID use, so that a secondary SSID can be used for emergency services Operational details (in brief) –Multicast/unicast operation –Query size limits: administrators can configure response limit size –Emergency Services native query: type of authentication

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 7 Emergency Services Use Case #1: Dedicated SSID Uses emergency services only (ESO) bit to signal that the SSID can support emergency services without any level security Network must enforce appropriate security (out of scope for ) –Network is locked down to emergency calls only –e.g. dedicated VLAN, IP firewall AP (11u-capable) STA (11u-capable) Beacon (w/ESO bit) Association Request Association Response Initiate higher-layer call (e.g. SIP) GAS Native Query (SSID list + ES info) GAS Native Query Response Restricted Network e.g. dedicated VLAN, IP filtering, etc. Note: SSID list is optional; used in multi-SSID deployments ADDTS Request (w/Expedited BW Req.) ADDTS Response

doc.: IEEE /2078r0 Submission July 2007 Matthew Gast, Trapeze NetworksSlide 8 Emergency Services Use Case #2: Public Credentials ESO calls have no cryptographic protection (tampering, injection, forgery) To provide cryptography, i security must be used –Pre-shared key for all emergency networks is not feasible –802.11u provides a way for a network to set up an emergency public credential to use EAP methods EAP method needs clarification AP (11u-capable) STA (11u-capable) Association Request Association Response Initiate higher-layer call (e.g. SIP) GAS Native Query (emergency public credentials) GAS Native Query Response (credentials) EAPOL/EAP-Identity-Response (credentials) EAPOL/EAP-Identity-Request EAP method authentication 4-Way Handshake ADDTS Request (w/Expedited BW Request) ADDTS Response