Upload
dorcas-poole
View
213
Download
0
Embed Size (px)
Citation preview
March 2007
Matthew Gast, Dave Stephenson
Slide 1
doc.: IEEE 802.11-07/0270r0
Submission
Emergency Call Setup Procedure
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 <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 [email protected] 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 <[email protected]>.
Date: 2007-02-22
Name Company Address Phone email Matthew Gast Trapeze Networks 5753 W. Las Positas
Blvd, Pleasanton, CA 94588 USA
+1 (925) 474-2273
Dave Stephenson Cisco Systems 170 W. Tasman Dr. San Jose, CA 95134
+1 408 527 7991
Angelo Centonza Roke Manor Research Ltd
Old Salisbury Lane, Romsey, Hampshire, SO51 0ZN, UK
+44 1794 833185
Authors:
March 2007
Matthew Gast, Dave Stephenson
Slide 2
doc.: IEEE 802.11-07/0270r0
Submission
Abstract
Frame exchange diagram for Emergency Call Setup process of an 802.11u-capable STA.
Diagrams developed at February 2007 TGu/802.21 Ad Hoc Meeting (San Jose, California, USA)
March 2007
Matthew Gast, Dave Stephenson
Slide 3
doc.: IEEE 802.11-07/0270r0
Submission
AP(11u-capable)
STA(11u-capable)
Configured by Hotspot owner / administrator
Beacon (ESR)Association request (SSID : Foo)
Association Response (…)
EAP Success (include PMK?)
dela
y
Emergency Call Setup Message Flow
EAPOL/EAP-Response/Identity (anonymous@ESR)
EAPOL/EAP-Request/Identity
4-Way Handshake
March 2007
Matthew Gast, Dave Stephenson
Slide 4
doc.: IEEE 802.11-07/0270r0
Submission
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– EAP method (non-standard?) probably does not need to be used– e.g. EAP-TLS not required.
March 2007
Matthew Gast, Dave Stephenson
Slide 5
doc.: IEEE 802.11-07/0270r0
Submission
AP(11u-capable)
STA(11u-capable)
Carrier Network
VLAN #5
Use Case #1
IEEE 802.21Information Server
AAA
DHCP
SSID #5
March 2007
Matthew Gast, Dave Stephenson
Slide 6
doc.: IEEE 802.11-07/0270r0
Submission
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
March 2007
Matthew Gast, Dave Stephenson
Slide 7
doc.: IEEE 802.11-07/0270r0
Submission
Additional Notes 1
• Beacon Management Frames– AP’s BSSID
– SSID – Foo
– ESSID
– Interworking Capability IE (ESO)
– GAS Capability IE
– WIID• homogenous services
March 2007
Matthew Gast, Dave Stephenson
Slide 8
doc.: IEEE 802.11-07/0270r0
Submission
Layer Parameters
• L2 ACLs: SA, DA, ET, Pri, ULAN ID
• L3 ACLs: SA, DA, DSCP, SP, DP, IPP
March 2007
Matthew Gast, Dave Stephenson
Slide 9
doc.: IEEE 802.11-07/0270r0
Submission
AP QoS Parameters
Use T/F Max Rate
AC - VO T ~160 kbps
VI F
BE T ~100 kbps
BK F