1. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 1 Support for un-authenticated Emergency Services Date: 2008-01-11 Authors:

2. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 2 Un-authenticated emergency service support in TGu From annex T.1: –Emergency Services define the IEEE 802.11 functionality to support an Emergency Call (e.g. E911) service as part of an overall, multi-layer solution, specifically capability advertisement and authentication issues. “Multi-layer” indicates that Emergency Services will be provided by protocols developed in part by other standards bodies. There are no links/references to the other standard bodies nor it is described how the TGu details fit into the big picture

3. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 3 Architectures supporting Unauthenticated Emergency Services 3GPP/3GPP2 defined IMS architecture The extended architecture for IETF Ecrit described in http://www.ietf.org/internet-drafts/draft-schulzrinne- ecrit-unauthenticated-access-01.txt

4. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 4 Proposal 1 Add references to the documents which describe the big picture where the TGu piece fits: –Extended ECRIT architecture supporting unauthenticated emergency services: http://www.ietf.org/internet-drafts/draft- schulzrinne-ecrit-unauthenticated-access-01.txthttp://www.ietf.org/internet-drafts/draft- schulzrinne-ecrit-unauthenticated-access-01.txt –3GPP IMS emergency sessions architecture: 3GPP TS 23.167 –3GPP2 IMS emergency sessions architecture:

5. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 5 Extended ECRIT architecture supporting un-authenticated Emergency Services

6. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 6 Mobility during emergency service call in the extended Ecrit architecture Boundary of PSAP1 Boundary of PSAP2 PSAP1 PSAP2 ESRP2 ESRP1 ESRP4 ESRP3 AN 1 AN 2 AN 3 AN 4 AN 8 AN 7 AN 6 AN 5 esrp= Emergency Services Routing Proxy

7. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 7 What can TGu further define? Procedures to help the STA handover to an AN which is connected to the same ESRP –Make the address of the ESRP accessible for download using GAS Native query This involves: –Adding a new application ID for DHCP ESRP discovery is using RFC3263 Deployment guidelines: ANs within the same ESS should have the same ESRP ESSs should not cross PSAP boundaries IETF will further define SIP procedures to handle cases which do not fall into the above (and requires heavy SIP procedures to maintain session continuity)

8. doc.: IEEE 802.11-08/0115r0 Submissions January 2008 Gabor Bajko, NokiaSlide 8 Proposal 2 Define a new Advertisement Protocol ID (value=4 ) for transporting DHCP messages and options DHCP server has similarities with a 802.21 IS server, it can be used to bootstrap lots of useful information before or without associating to the AP. Beneficial in case there is no 802.21 IS server in the backend, but there is DHCP server Example of existing DHCP options: –Access network name, timezone, geo and civic location, DNS, SIP proxy, ESRP, etc.