1. mm/dd/yyyy802 Emergency Services Tutorial 2/4/2010 Con Call output This version is Geoff's edits as taken in the conference call. It includes implementation of the editing instructions talked about in the 1/29 conference call Further edits through Feb 4 11:00 AM, 2010Geoff Thompson Edits during conference call Feb 4, 2010 2:00 PM – 3:37 PM by Geoff Thompson Further Edits by Geoff Thompson in prep for Con Call 2:00 PM PST Feb 11, 2010

2. mm/dd/yyyy802 Emergency Services Tutorial 802 EMERGENCY SERVICES TUTORIAL Why 802 needs an Emergency Services Project and what we think it should look like. 802 ES-ECSG Geoff Thompson/InterDigital Scott Henderson/RIM Others from.16 (Barber?) &.11?

3. mm/dd/yyyy802 Emergency Services Tutorial Agenda New Break up in to separate presentations and presenters Who will present for ES and how will the tutorial be broken into presenters? Presenter 1/Topic Presenter 2/Topic Presenting for 802.11? Presenting for 802.16 (Barber?) Presenting for 802.1?

4. mm/dd/yyyy802 Emergency Services Tutorial Technical/Regulatory Problem Statement (US Historical Case) 911 Call Origination Identification: Originally based on the wireline legacy incumbent local exchange carriers' databases of their customers. This system fell apart or was seriously weakened as: Local phone service ceased to be dominated by a wireline monopoly. Cellular phones became significant. (They had no built-in location mechanism. They also had a weakened sense of just where they wanted to call for 911.) VoIP phone services grew. VoIP has no inherent caller or call target physical location knowledge. Wireless inherent authentication was weakened.

5. mm/dd/yyyy802 Emergency Services Tutorial Regulatory Technical Problem Statement Emergency Services calls need: To be directed to the appropriate PSAP Carry originating location information To provide sufficient information for PSAP call-back Further (possible future but not current): Systems are required to provide service to any user. (Authorized subscriber or not) some countries Some prioritization capability should be considered

6. mm/dd/yyyy802 Emergency Services Tutorial FCC Consumer Info Sheet http://www.fcc.gov/cgb/consumerfacts/voip911.pdf

7. mm/dd/yyyy802 Emergency Services Tutorial (Example:) US Requirement (adapted from: http://www.fcc.gov/cgb/consumerfacts/voip911.pdf )http://www.fcc.gov/cgb/consumerfacts/voip911.pdf The US FCC has imposed the following requirement: All interconnected VoIP providers must automatically provide 911 service to all their customers as a standard, mandatory feature without customers having to specifically request this service. VoIP providers may not allow their customers to “opt-out” of 911 service.

8. mm/dd/yyyy802 Emergency Services Tutorial Requirements: Other countries Many other countries have similar requirements. There are national differences, especially with respect to: Emergency numbers other than “911”. Some countries have several numbers Some countries prohibit location info. Other details

9. mm/dd/yyyy802 Emergency Services Tutorial Defined Problem lies in Multiple Domains IP, routing and higher layer portions of the problem belong to the IETF. These problems are being addressed primarily by IETF ECRIT. The below Layer 3 portion of the problem is for 802 to address. 802.11 and 802.16 have already done some explicit work in this area. Needs to be handled uniformly across 802.

10. mm/dd/yyyy802 Emergency Services Tutorial 802 Problem IEEE 802 needs a single standard so that IP applications “should” not need to know which 802 MAC is currently being used. This is envisioned as a “shim layer” that goes between an 802 end station MAC and its upper layer client. There will be similar pieces required for 802.1 relays to add per-hop location information (required for location back-up information when no end-location information is provided).

11. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (2) needs title maybe “Complex Problem” SUPPORT OF EMERGENCY SERVICES and THEIR (present and future) REQUIREMENTS FOR PACKET NETWORKS IS A HUGE, COMPLEX PROBLEM FOR WHICH THE PROBLEM ITSELF IS NOT YET FULLY DEFINED. A successful Emergency Call depends on all layers of the network For our proposed scope we feel that the problem is fully defined.

12. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (2) needs title maybe “Complex Problem” SUPPORT for the full scope of EMERGENCY SERVICES and THEIR (present and future) REGULATORY REQUIREMENTS FOR PACKET NETWORKS IS A HUGE, COMPLEX PROBLEM FOR WHICH THE PROBLEM ITSELF IS NOT YET FULLY DEFINED. The scope for this project is much smaller and well defined i.e.: Only support VoIP citizen to authority calls.

13. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (3)need title There are pieces of the ES problem that: Are well defined today Have existing regulatory requirements Are not addressed across 802. (Do we still need this slide after edits on previous slide? Does it need to be modified?)

14. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (4) The biggest piece: 802 originated (and VoIP originated) “calls” to the PSTN don't carry the information required (e.g. location) for emergency calls (There are proprietary exceptions) There are uncoordinated pieces within some WGs. There are existing regulatory requirements for these ES calls that are not being met.

15. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (5) Regulatory Requirements for ES calls: Call request directed to the correct PSAP Provide calling party location (most countries) Non-subscriber access to network (country specific) PSAP can call back Very high priority Call integrity (no drop, spoof-proof) Security/Encryption

16. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (2) need title maybe “Complex Problem” (Delete this one or other one?) SUPPORT OF EMERGENCY SERVICES and THEIR (present and future) REGULATORY REQUIREMENTS FOR PACKET NETWORKS IS A HUGE, COMPLEX PROBLEM FOR WHICH THE PROBLEM ITSELF IS NOT YET FULLY DEFINED. For our proposed scope we feel that it is fully defined.

17. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (6) Why VoIP doesn't work for ES calls today: The Internet was designed to be “location neutral”. Traditional “911/112” was designed around and serviced by a localized static wired infrastructure (end office circuit switched systems) VoIP services are highly decentralized and often cross national boundaries (regulatory problem)

18. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (7) Why VoIP doesn't work today (cont'd): Today, the VoIP service provider has no knowledge of the caller's location within the Internet (almost true) A PSAP has no prior knowledge that a caller is within their service area. Therefore, associating caller and proper PSAP is a big problem VoIP service providers are not sufficiently regulated to fully handle the ES problem; there are significant technical, geopolitical and legal jurisdiction problems involved.

19. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (8) The IETF – ECRIT group has taken on the task of solving this problem for the upper layers. See: http://www.ietf.org/dyn/wg/charter/ecrit-charter.html http://www.ietf.org/dyn/wg/charter/ecrit-charter.html 7 Internet drafts, 7 RFCs Includes “Framework” and “Best Current Practices” See also R. Barnes/Hannes Tschofenig IETF preso: http://geopriv.dreamhosters.com/esw6/PEACE-Vortrag_v5.ppt

20. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (9) The IETF – ECRIT group has taken on the task of solving this problem for the upper layers. 802 needs to liaise with ECRIT to Provide a complete solution that encompasses 802 end networks. Agree precisely on requirements from 802 The solution should look the same to ECRIT without regard to which 802 technology is in use.

21. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (10) What does ECRIT need from 802 to meet these requirements? What can IEEE 802 provide to ECRIT to meet these requirements? Provide better location than just the router Emergency calls should be given priority in the 802 network (Consider, not fully supported across 802) Callback is currently a problem Spoofing and security are issues Prefer LOCAL connection (e.g. bypass various tunneling schemes) Provide service to unauthenticated user (Initiate & handover/callback)

22. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (11) What we believe 802 needs to finish the task : Specific referenced external req'ts from ECRIT Specific interface specs from ECRIT harmonized and reconciled to our requirements Agreement within various 802 W.G.s to tweak their pieces. An ES WG to generate a single standard to reconcile the upper layer interface.

23. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (12) What 802 needs to provide to finish the task : A standard that includes means to: Provide end & per hop location in 802 networks. Give emergency calls priority in 802 networks Provide information to enable Callback Provide a LOCAL connection mechanism (e.g. bypass various tunneling schemes) Provide service to unauthenticated users to a default VoIP router. Spoofing and security are issues

24. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (13) IN SHORT: ES-ECSG intends to provide what ECRIT needs.

25. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (14) Possible technical concepts: Provide end location in 802 networks. 802 ES to provide/harmonize end station location MIB to ECRIT format requirements. Provide per-hop location in 802 networks. Adapt/use existing mechanism from 802.1ag and equivalents from 802.11.

26. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (15) Possible technical concepts: Give emergency calls priority in 802 networks. Use existing priority mechanisms in 802.1Q

27. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (16) Possible technical concepts: Provide information to enable Callback. Provide both originating terminal location MIB information and per-hop network information as part of session initiation information to the network attachment router. This would provide “hints” that the 802 network could use if call is disconnected and straightforward callback turns out to be a problem.

28. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (17) Possible technical concepts: Provide a LOCAL connection mechanism (e.g. bypass various tunneling schemes). Provide a VLAN (or equivalent) across all 802 networks that is dedicated exclusively to Emergency Services. It would have a single destination, i.e. the network attachment router. We anticipate that packets will be steered to this new dedicated VLAN by the use of a new EtherType.

29. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (18) Possible technical concepts: Provide service to unauthenticated users. This could be difficult, but is a firm regulatory requirement. (Provide pointer) We believe a dedicated VLAN will make it easier than it would be to do otherwise. No authentication is needed to use the dedicated VLAN, but it can only be used to get to the PSAP.

30. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (19) Spoofing: End and per-hop location information as provided will be available as a tool for use in dealing with this classical problem.

31. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (20) Security: A dedicated VLAN sidesteps some of the issues associated with security. Providing location information is forbidden in some countries, mandatory in others. Provided location information is considered to be sensitive information. Information integrity across the call is a security issue. Information needed for call back is considered to be sensitive. The actual content of the call may be considered to be sensitive.

32. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (21) Security (2): The security considerations for ECRIT are put forth in IETF RFC-5069 There are a few problems which seem to be intractable in a wireless environment with unauthenticated users. Originating call location information from unauthenticated users will be visible (“Hollywood Paparazzi Problem”) unless we encrypt (at least) the over-the-air portion of those calls. We believe that the current population of public access points has no way to provide encryption for unauthenticated users. We believe that the current population of 802.11 access points has no way to preserve security while switching SSIDs (for further investigation).

33. mm/dd/yyyy802 Emergency Services Tutorial TUTORIAL (22) Security (3): First hop encryption is a significant challenge. First hop encryption will possibly require changes from the wireless MAC groups. First hop encryption should not be allowed to delay work on the primary functionality of “getting the call through”.

34. mm/dd/yyyy802 Emergency Services Tutorial Diagrams Generate new topology and block functionality diagram which is like older 2 below but has at least 2 relay points. A diagram that actually describes a call sequence flow(?) chart: (and remove this slide)

35. mm/dd/yyyy802 Emergency Services Tutorial IEEE 802 MAC Call origination Upper Layer Client (presumably IP) Call destination Upper Layer Client (1 st Router) IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY Relay Sub-Layer Location Determination Reconciliation Sub-Layer Location Determination Reconciliation Sub-Layer IEEE 802 EMERGENCY SERVICES ARCHITECTURE RE: Location Determination AirAir, wire or fiber Location Ranging Module & MIB 1 st Access point for Wireless instance

36. mm/dd/yyyy802 Emergency Services Tutorial IEEE 802 MAC Call origination Upper Layer Client (presumably IP) Call destination Upper Layer Client (1 st Router) IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY Location Determination Reconciliation Sub-Layer IEEE 802 EMERGENCY SERVICES ARCHITECTURE RE: Location Determination AirAir, wire or fiber IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY Relay Sub-Layer Location Determination Reconciliation Sub-Layer Location Determination Reconciliation Sub-Layer IEEE 802 PHY IEEE 802 MAC Relay Sub-Layer Location Determination Reconciliation Sub-Layer Location Ranging Module & MIB 802 → ECRIT Handover Reconciliation Sub-Layer 1 st Access point for Wireless instance

37. mm/dd/yyyy802 Emergency Services Tutorial IEEE 802 MAC Call origination Upper Layer Client (presumably IP) Call destination Upper Layer Client (1 st Router) IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY IEEE 802 MAC IEEE 802 PHY Relay Sub-Layer Location Determination Reconciliation Sub-Layer IEEE 802 EMERGENCY SERVICES ARCHITECTURE re: Location Determination Wire or fiberAir, wire or fiber Location Determination Reconciliation Sub-Layer Generic relay point Assume for the time being that network to the right side of the line is: a) Not dynamic b) Secure on a hop by hop basis 802 involvement ends at the 1 st router when the frame is separated from the SA/DA & Type fields

38. mm/dd/yyyy802 Emergency Services Tutorial Call sequence via wireless end link 802.11 not 802.16 How to fix? AP->Sta Beacon of SSID for ES VLAN STA picks a beacon STA sends “Authenticate request” AP sends “Authenticate reply” STA send “Associate request” AP sends “Authenticate reply” STA sends DHCP request AP passes back DHCP response DHCP response contains IP address for station, gateway IP address. STA send ARP request with Gateway IP addr to get Gateway DA AP passes back ARP response from Gateway with its DA STA can now communicate directly to Gateway via IP

39. mm/dd/yyyy802 Emergency Services Tutorial Call sequence via wireless end link STA sends ES SIP Request to Gateway (Is location information sent at this point or in subsequent packets)? About now, 802 has pretty much set up its job except when the time comes for Call-Back. (Handover and roaming problems excluded) Advance information query can come back after call is established. We need to say more about roaming and handover. Much study needed in multiple WGs.

40. mm/dd/yyyy802 Emergency Services Tutorial Issues U.S. Government preference is for infrastructure based location over that from end station based location information. (GPS reliability in cities and inside buildings is a problem, as is spoofing.) 802.16 distance and angle measurement is not of sufficient accuracy to meet the requirements E911 & NG911. 802.11 service leaking into adjacent properties is a well known problem for which we have no solution. That is, being able to provide accurate street address information of the caller.

41. mm/dd/yyyy802 Emergency Services Tutorial Issues (2) This is all a contentious technical area, both from a feature/content point-of-view and from a division of work/layer/SDO assignment point-of-view. Just what are the regulatory requirements (from around the world)? What technical work needs to be done first/now? (We can't just wait until everything is written in stone to start.) What pieces will get done: in what layer? In what SDO? Getting good answers to all of this is the first task for the group.