1. SDO Emergency Services Coordination Workshop (ESW06) 1 Emergency Service Identifiers Presented by Henning Schulzrinne Columbia University hgs@cs.columbia.edu

2. SDO Emergency Services Coordination Workshop (ESW06) 2 Service URN Idea: Identifiers to denote emergency calls –and other generic (communication) services Described in draft-ietf-ecrit-service-urn-05.txt (passed WGLC; sent to the IESG)draft-ietf-ecrit-service-urn-05.txt Document defines the following emergency service identifiers: sos General emergency services sos.animal-control Animal control sos.fire Fire service sos.gas Gas leaks and gas emergencies sos.marineMaritime search and rescue sos.mountainMountain rescue sos.physicianPhysician referral service sos.poisonPoison control center sos.policePolice, law enforcement

3. SDO Emergency Services Coordination Workshop (ESW06) 3 ‘counseling’ services urn:service:counselingGeneric counseling service (call center) …:counseling.childrenrun-aways, child abuse …:counseling:mental-healthdiagnostic, treatment, and preventive care … mental health …:counseling:suicidesuicide prevention hotline

4. SDO Emergency Services Coordination Workshop (ESW06) 4 Services under discussion “211” (social service referral), “311” (non- emergency government services) Emergency services (first responders) –used by PSAP, not civilians –e.g., urn:service:es:police Non-emergency commercial services –urn:service:restaurant.italian –urn:service:transportation.taxi

5. SDO Emergency Services Coordination Workshop (ESW06) 5 UA recognition & UA resolution INVITE urn:service:sos To: urn:service:sos Route: sip:psap@leonianj.gov 9-1-1 (dial string) mapping INVITE urn:service:sos To: urn:service:sos Route: sip:fire@leonianj.gov leonianj.gov mapping may recurse location information DHCP LLDP-MED identification TBD

6. SDO Emergency Services Coordination Workshop (ESW06) 6 UA recognition & proxy resolution 9-1- 1 mapping INVITE urn:service:sos To: urn:service:sos INVITE urn:service:sos To: urn:service:sos Route: sip:psap@leonianj.gov (outbound proxy) provider.com

7. SDO Emergency Services Coordination Workshop (ESW06) 7 UA recognition & proxy resolution (proxy location determination) 9-1- 1 mapping INVITE urn:service:sos To: urn:service:sos INVITE sip:psap@leonianj.gov To: urn:service:sos Geolocation: provider.com

8. SDO Emergency Services Coordination Workshop (ESW06) 8 Proxy recognition & proxy resolution 9-1- 1 mapping INVITE sip:911@provider.com;user=phone To: sip:911@provider.com;user=phone INVITE urn:service:sos To: sip:911@provider.com;user=phone Geolocation: Route: sip:psap@leonianj.gov provider.com

9. SDO Emergency Services Coordination Workshop (ESW06) 9 Labeling requirements Needs to work even if UAC does not recognize emergency call Needs to survice multiple mappings –e.g., country  state  county Needs to play nice with SIP routing architecture –e.g., pre-loaded service routes

10. SDO Emergency Services Coordination Workshop (ESW06) 10 Alternatives considered only trust Accept-Contact from same trust domain –see P-Asserted-Identity model (RFC 3325)  brittle –or use Identity model  signed by outbound proxy unfortunately, not covered by –doesn’t help with UA rec/res model! creating a new header likely to have similar issues re-do mapping and ensure that URL matches –server can learn list of “legal” URLs after a while –can fail if mapping is dynamic (advertisement changes) then just replaces URL –forces each outbound proxy to do mapping check external source that URL is indeed a PSAP –use draft-ietf-sipping-certs for destination URL, but would need to have a role-based cert “this is a bona- fide PSAP” easy to posit, harder to deploy globally can incur significant delay but only needed when there’s service differentiation new TLD for PSAPs only

11. SDO Emergency Services Coordination Workshop (ESW06) 11 References and contact info IETF ECRIT Working Group http://www.ietf.org/html.charters/ecrit-charter.html Service URN IETF Draft http://tools.ietf.org/wg/ecrit/draft-ietf-ecrit-service-urn/