April 26, 2004 Critical Issues Forum (Baltimore) 1 An Architecture for Next- Generation Emergency Services Henning Schulzrinne Columbia University.

Slides:



Advertisements
Similar presentations
SIP, Presence and Instant Messaging
Advertisements

SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
Fall IM 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
IM May 24, 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
VON Europe /19/00 SIP and the Future of VON Protocols SIP and the Future of VON Protocols: Presence and IM Jonathan Rosenberg.
Fall VoN 2000 SIP for IP Communications Jonathan Rosenberg Chief Scientist.
911 services: wireline, wireless and VoIP
Internet Standards- Emergency Services Hannes Tschofenig Mail comments to and/or
The current System Landline caller The emergency call process starts with a caller dialing (highly simplified) © 2011 Colorado Resource.
Johan Garcia Karlstads Universitet Datavetenskap 1 Datakommunikation II Signaling/Voice over IP / SIP Based on material from Henning Schulzrinne, Columbia.
BAI613 Module 2 - Voice over IP Technology. Module Objectives 1. Describe the benefits of IP Telephony/Packet Telephony/VoIP over traditional telephone.
THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS.
Origins of ECRIT IETF has been working on location since 2000 –Spatial BoF, eventually GEOPRIV chartered in 2001 GEOPRIV provides location information.
Emergency Services IAB Tech Chat 28 th February 2007 Hannes Tschofenig.
NENA’s 11 th Annual Technical Development Conference A proposal to support E911 calls on Voice over IP Networks Martin Dawson – Nortel Networks.
911 services: wireline, wireless and VoIP
A prototype i3 VoIP PSAP implementation Henning Schulzrinne, Anshuman Rawat, Matthew Mintz-Habib, Xiaotao Wu and Ron Shacham Dept. of Computer Science.
A Generic Event Notification System Using XML and SIP Knarig Arabshian and Henning Schulzrinne Department of Computer Science Columbia University
IETF 61 (November 2004) ECRIT1 Requirements and Architecture for Emergency Calling draft-schulzrinne-sipping-emergency-arch draft-schulzrinne-sipping-emergency-req.
Internet Real-Time Lab, Columbia University Emergency Calling for VoIP Wonsang Song, Jong Yul Kim, and Henning Schulzrinne.
911 services: wireline, wireless and VoIP Prof. Henning Schulzrinne Dept. of Computer Science Columbia University, New York FCC Solutions Summit March.
VoIP/NG E9-1-1 IP-based E9-1-1 Migratory & Long Term Solutions – A Trial/Demo Update.
Internet E-911 System Henning Schulzrinne and Knarig Arabshian Department of Computer Science Columbia University
VoIP Technology Developments and Trends Henning Schulzrinne Columbia University.
SIP vs H323 Over Wireless networks Presented by Srikar Reddy Yeruva Instructor Chin Chin Chang.
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
28 June 2015 Emergency services for SIP Henning Schulzrinne.
Providing Emergency Services in Internet Telephony Henning Schulzrinne and Knarig Arabshian Department of Computer Science Columbia University
Presence Vishal Kumar Singh and Henning Schulzrinne Feb 10, 2006.
An SAIC Company Telcordia View of NENA Progress on VoIP Migration Plan Telcordia Contacts: Nadine Abbott (732) An SAIC Company.
March 2006IETF65 - ECRIT1 Emergency Service Identifiers draft-ietf-ecrit-service-urn-01 Henning Schulzrinne Columbia University
Remote Workers Without the Hassle
Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation.
March 2004SIPPING - IETF 59 (Seoul)1 Emergency calling draft-ietf-sipping-sos draft-schulzrinne-emergency-arch Henning Schulzrinne Columbia University.
NENA’s 11 th Annual Technical Development Conference An Architecture for Next- Generation Emergency Services Henning Schulzrinne Columbia University.
SDO Emergency Services Coordination Workshop (ESW06) 1 A Location-to-Service Translation Protocol (LoST) & Mapping Protocol Architecture Ted Hardie Andrew.
© 2008 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. 1 Video Relay Service and Assignment.
NG911 technology Henning Schulzrinne
ESW – May 2010 UK Architecture for VoIP 999/112s John Medland – BT 999/112 Policy Manager.
NENA Next Generation Architecture
Implementing ISA Server Publishing. Introduction What Are Web Publishing Rules? ISA Server uses Web publishing rules to make Web sites on protected networks.
1 © NOKIA 1999 FILENAMs.PPT/ DATE / NN SIP Service Architecture Markus Isomäki Nokia Research Center.
Status and Development of VoIP based emergency calls Alexander Mayrhofer, nic.at GmbH The 1st European Security and Safety Summit Brussels, June 2007.
Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar
Introduction to SIP Based ENUM IP Telephony Infrastructure 資策會 網路及通訊實驗室 Conference over IP Team 楊政遠 博士
I2 and I3 – a status summary Henning Schulzrinne Columbia University NENA Interim Meeting Burlington, VT April 6, 2004.
Internet Telephony (VoIP) Henning Schulzrinne Dept. of Computer Science Columbia University Fall 2003.
Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa
November 2005IETF64 - ECRIT1 Emergency Service Identifiers draft-ietf-sipping-sos-01 draft-schulzrinne-sipping-service-01 Henning Schulzrinne Columbia.
The State of VoIP Peering Charles Studt Director of Product Management, VoEX.
Omar A. Abouabdalla Network Research Group (USM) SIP – Functionality and Structure of the Protocol SIP – Functionality and Structure of the Protocol By.
Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar
Project Objectives A multi-function programmable SIP user agent for multimedia communications, such as audio, video, white board, desktop sharing, shared.
Core VoIP and 911 issues and alternatives Henning Schulzrinne Columbia University August 2003.
ORBIT: Location- based services Henning Schulzrinne Columbia University.
Internet Real-Time Lab, Columbia University NG9-1-1 Prototype Demo Jong Yul Kim, Wonsang Song, and Henning Schulzrinne.
The Session Initiation Protocol - SIP
S Postgraduate Course in Radio Communications. Application Layer Mobility in WLAN Antti Keurulainen,
April 26, 2004 Critical Issues Forum (Santa Clara) 1 An Architecture for Next- Generation Emergency Services Henning Schulzrinne Columbia University.
© 2015 Airbus DS Communications, Inc. All rights reserved. Lights, Camera, NG9-1-1 Diana Gijselaers/ Solutions Engineer – NG9-1-1 GIS and Core Services.
Emergency calling for VoIP Henning Schulzrinne Columbia University Intrado (January 2004)
Postech DP&NM Lab Session Initiation Protocol (SIP) Date: Seongcheol Hong DP&NM Lab., Dept. of CSE, POSTECH Date: Seongcheol.
ECRIT - IETF 62 (March 2005) - Minneapolis 1 Requirements for Emergency Calling draft-schulzrinne-sipping-emergency-req-01 draft-ietf-sipping-sos-01 Henning.
Internet Telephony (VoIP)
IP Telephony (VoIP).
THIS IS THE WAY ENUM Variants Jim McEachern
Purpose of Project Conduct research in support of NENA’s Next Generation E9-1-1 initiative Conduct that research without endangering public safety Share.
Jong Yul Kim, Wonsang Song, and Henning Schulzrinne
Emergency Calling Architecture
Presentation transcript:

April 26, 2004 Critical Issues Forum (Baltimore) 1 An Architecture for Next- Generation Emergency Services Henning Schulzrinne Columbia University

April 26, Overview How does VoIP differ from landline and wireless PSTN? How does VoIP differ from landline and wireless PSTN? Getting from here to there: I1, I2 and I3 Getting from here to there: I1, I2 and I3 IETF efforts IETF efforts status status assumptions assumptions Common URL for emergency services Common URL for emergency services Routing emergency calls Routing emergency calls Common location format Common location format Configuration of local emergency call numbers Configuration of local emergency call numbers Security issues Security issues

April 26, PSTN vs. Internet Telephony Signaling & Media Signaling Media PSTN: Internet telephony: China Belgian customer, currently visiting US Australia

April 26, SIP trapezoid outbound proxy registrar 1 st request 2 nd, 3 rd, … request voice traffic RTP destination proxy (identified by SIP URI domain)

April 26, SIP addressing Users identified by SIP or tel URIs Users identified by SIP or tel URIs tel: URIs describe E.164 number, not dialed digits (RFC 2806bis) tel: URIs describe E.164 number, not dialed digits (RFC 2806bis) tel URIs  SIP URIs by outbound proxy tel URIs  SIP URIs by outbound proxy A person can have any number of SIP URIs A person can have any number of SIP URIs The same SIP URI can reach many different phones, in different networks The same SIP URI can reach many different phones, in different networks sequential & parallel forking sequential & parallel forking SIP URIs can be created dynamically: SIP URIs can be created dynamically: GRUUs GRUUs conferences conferences device identifiers device identifiers Registration binds SIP URIs (e.g., device addresses) to SIP “address-of-record” (AOR) Registration binds SIP URIs (e.g., device addresses) to SIP “address-of-record” (AOR) tel:110 domain  via NAPTR + SRV

April 26, How does VoIP differ from landline and wireless PSTN? Telephone companies are no longer needed Telephone companies are no longer needed there are still carriers for DSL and cable “IP dial tone” there are still carriers for DSL and cable “IP dial tone” but unaware of type of data carried but unaware of type of data carried VSP may be in another state or country VSP may be in another state or country Corporations and universities don’t have carriers, either Corporations and universities don’t have carriers, either voice service provider (RTP, SIP) ISP (IP, DHCP, DNS) dark fiber provider Yahoo MCI NYSERNET

April 26, Why is VoIP ≠ wireless? VoIP devices may not have phone numbers as lookup keys VoIP devices may not have phone numbers as lookup keys e.g., e.g., Location information for devices is civic, not longitude/latitude Location information for devices is civic, not longitude/latitude e.g., service address for VSPs e.g., service address for VSPs GPS not available (nor functional) on indoor devices GPS not available (nor functional) on indoor devices plus, accuracy of 50 m (67%) or 150 m spans many buildings… plus, accuracy of 50 m (67%) or 150 m spans many buildings… no floor information no floor information Cell phones don’t work in our building… Cell phones don’t work in our building… so A-GPS is unlikely to work there, either so A-GPS is unlikely to work there, either Plus, wireless E911 complexity due to old signaling mechanism Plus, wireless E911 complexity due to old signaling mechanism 50m

April 26, IETF efforts IETF = Internet Engineering Task Force IETF = Internet Engineering Task Force “The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual.” “The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual.”(IETF) Efforts on 911 services go back to 2001, … Efforts on 911 services go back to 2001, … but only recent high-impact efforts but only recent high-impact efforts individuals working both in NENA and IETF WGs individuals working both in NENA and IETF WGs

April 26, Current IETF drafts draft-taylor-sipping-emerg-scen-01 draft-taylor-sipping-emerg-scen-01 scenarios, e.g., hybrid VoIP-PSTN scenarios, e.g., hybrid VoIP-PSTN draft-schulzrinne-sipping-emergency-arch-00 draft-schulzrinne-sipping-emergency-arch-00 overall architecture for emergency calling overall architecture for emergency calling draft-ietf-sipping-sos-00 draft-ietf-sipping-sos-00 describes ‘sos’ SIP URI describes ‘sos’ SIP URI draft-rosen-dns-sos-00 draft-rosen-dns-sos-00 new DNS resource records for location mapping new DNS resource records for location mapping

April 26, Three stages to VoIP 911 spec. available? use 10- digit admin. number? mobilitycallback number to PSAP? caller location to PSAP? PSAP modificatio n ALI (DB) modification new services I1nowallowedstationarynononononone I2 Dec nostationarynomadicyesyes no (8 or 10 digit) updatenone I3 late 2004 late 2004nostationarynomadicmobileyesyesIP-enabled ALI not needed MSAG replaced by DNS location in- band GNPmultimedia international calls

April 26, Architectural assumptions and goals for I3 SIP-based for interchange SIP-based for interchange other protocols (e.g., H.323) via gateway other protocols (e.g., H.323) via gateway avoid complexity of multiple protocols everywhere avoid complexity of multiple protocols everywhere H.248/MGCP not used for interdomain signaling  not needed here H.248/MGCP not used for interdomain signaling  not needed here International International devices bought anywhere can make emergency calls anywhere devices bought anywhere can make emergency calls anywhere limit biases in address formats, languages, … limit biases in address formats, languages, … avoid built-in bias for “911” or “112” (mostly) avoid built-in bias for “911” or “112” (mostly) use term “ECC” (emergency call center) instead of “PSAP” use term “ECC” (emergency call center) instead of “PSAP” Multimedia Multimedia support non-audio media if available in PSAP support non-audio media if available in PSAP e.g., images or video for situational awareness e.g., images or video for situational awareness

April 26, Goals, cont’d. Support other communications modes Support other communications modes IM IM maybe later maybe later Support access for callers with disabilities Support access for callers with disabilities real-time text real-time text video for sign language video for sign language Easy access to external data Easy access to external data hazmat records hazmat records sensor data (collision data, video images, …) sensor data (collision data, video images, …)

April 26, Architecture components 1. Common URL for emergency calls 2. Convey local emergency number to devices 3. Allow devices to obtain their location 4. Route calls to right destination

April 26, Component 1: Common URL for emergency services Emergency numbers may be dialed from many different places Emergency numbers may be dialed from many different places about 60 (national) different emergency service numbers in the world about 60 (national) different emergency service numbers in the world many are used for other services elsewhere (e.g., directory assistance) many are used for other services elsewhere (e.g., directory assistance) End systems, proxies and gateways should be able to tell easily that a call is an emergency call End systems, proxies and gateways should be able to tell easily that a call is an emergency call Thus, need common identifier for calls Thus, need common identifier for calls

April 26, Common URL for emergency calls IETF draft suggests IETF draft suggests home-domain: domain of caller home-domain: domain of caller Can be recognized by proxies along the way Can be recognized by proxies along the way short cut to emergency infrastructure short cut to emergency infrastructure If not, it reaches home proxy of subscriber If not, it reaches home proxy of subscriber Call can be routed from there easily Call can be routed from there easily global access to routing information (see later) global access to routing information (see later)

April 26, Service identification In some countries, specialized numbers for police, fire, … In some countries, specialized numbers for police, fire, … We add SIP protocol header that identifies call service: We add SIP protocol header that identifies call service: Accept-Contact: * ;service=“sos.mountain” Generally, not user visible Generally, not user visible sos.fire fire brigade sos.rescueambulance sos.marine marine guard sos.policepolice sos.mountain mountain rescue sos.test only testing

April 26, Other call identifiers Using SIP caller preferences/callee capabilities Using SIP caller preferences/callee capabilities Caller languages Caller languages automatically route to PSAP or call taker that speaks French automatically route to PSAP or call taker that speaks French Accept-Language: fr Accept-Language: fr Caller media preferences Caller media preferences automatically route to PSAP or call taker that can deal with typed text automatically route to PSAP or call taker that can deal with typed text Accept-Contact: *;text;require Accept-Contact: *;text;require

April 26, Component 2: Translating dialed digits Always available: 112 and 911 Always available: 112 and 911 Configuration mechanisms: Configuration mechanisms: SIM cards (GSM phones) SIM cards (GSM phones) XCAP configuration XCAP configuration local (outbound) proxy local (outbound) proxy home proxy home proxy DNS DNS Default configuration if no other information available: Default configuration if no other information available: 000, 08, 110, 999, 118 and , 08, 110, 999, 118 and 119

April 26, Emergency number configuration via DNS NAPTR "u" "SOS" de.sos.arpa country=DE DHCP server add 110 to list of emergency dial strings

April 26, Translating dialed numbers to emergency identifiers “9-1-1”no.URIservice911sossos 110sossos.police 112sossos.fire On many telephone-like systems, only numbers are available  number translation

April 26, GEOPRIV and SIMPLE architectures target location server location recipient rule maker presentity caller presence agent watcher callee GEOPRIV SIP presence SIP call PUBLISH NOTIFY SUBSCRIBE INVITE publication interface notification interface rule interface INVITE

April 26, Component 3: Determining locations Conveyed via DHCP from IP-level provider Conveyed via DHCP from IP-level provider Formats: Formats: geospatial (longitude, latitude, altitude or floor) geospatial (longitude, latitude, altitude or floor) civic (country, administrative units, street) civic (country, administrative units, street) Provider usually knows Provider usually knows Does not depend on being a voice service provider Does not depend on being a voice service provider triangulation triangulation GPS (for mobile devices) GPS (for mobile devices) Via configuration protocol (XCAP) Via configuration protocol (XCAP) relies on VSP having accurate service location information relies on VSP having accurate service location information User-configured (last resort) User-configured (last resort)

April 26, Enhancing DHCP for locations use MAC address backtracing to get location information use MAC address backtracing to get location information can use existing DHCP servers and clients can use existing DHCP servers and clients DHCP server 458/17  Rm /18  Rm. 816 DHCP answer: sta=DC loc=Rm815 lat= long= :0:20:ab:d5:d CDP + SNMP 8:0:20:ab:d5:d  458/17

April 26, Conveying location along the call path INVITE From: To: Content-Type: multipart/mixed PA University Park on boot placing emergency call

April 26, GEOPRIV geospatial format GEOPRIV = IETF working group for geospatial privacy GEOPRIV = IETF working group for geospatial privacy Location within call signaling Location within call signaling not ALI reference not ALI reference Based on GML mark-up Based on GML mark-up <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" T20:57:29Z 31:56:00S 115:50:00E no T04:57:29Z

April 26, GEOPRIV civic format Based on NENA XML elements Based on NENA XML elements Except internationalized administrative divisions: Except internationalized administrative divisions: A1 national subdivisions (state, region, province, prefecture) A2 county, parish, gun (JP), district (IN) A3 city, township, shi (JP) A4 city division, borough, city district, ward, chou (JP) A5 neighborhood, block A6street US NJ Bergen Leonia Westview Ave 313 Schulzrinne

April 26, Location-based call routing – UA knows its location GPS 48° 49' N 2° 29' E INVITE DHCP outbound proxy server 48° 49' N 2° 29' E  Paris fire department

April 26, Location-based call routing – network knows location IP 48° 49' N 2° 29' E TOA include location info in 302 INVITE INVITE map location to (SIP) domain outbound proxy

April 26, A quick review of DNS DNS = mapping from hierarchical names to resource records DNS = mapping from hierarchical names to resource records commonly, but not necessarily IP addresses commonly, but not necessarily IP addresses Authoritative server for each domain operated by domain Authoritative server for each domain operated by domain e.g., columbia.edu server is owned & operated by Columbia University e.g., columbia.edu server is owned & operated by Columbia University pc.example.com leonia.nj.us caches results leonia.nj.us?

April 26, A quick review of DNS Thus, globally visible database, with delegated control of content Thus, globally visible database, with delegated control of content Replication of DNS servers mandatory Replication of DNS servers mandatory at least 2, often more at least 2, often more automatically synchronized automatically synchronized Robustness by caching Robustness by caching typically life time of 24 hours typically life time of 24 hours end system may not notice outage of authoritative server end system may not notice outage of authoritative server Host security  modification control Host security  modification control DNS security (DNSsec) to ensure authenticity of content DNS security (DNSsec) to ensure authenticity of content

April 26, How does the PSAP find the caller’s location? Largest difference to existing E911 system Largest difference to existing E911 system In-band, as part of call setup In-band, as part of call setup carried in body of setup message carried in body of setup message rather than by reference into external database rather than by reference into external database May be updated during call May be updated during call moving vehicles moving vehicles late availability of information (GPS acquisition delay) late availability of information (GPS acquisition delay) Also possible: subscribe to location information Also possible: subscribe to location information

April 26, Using DNS for determining PSAPs Define new domain, e.g., sos.arpa Define new domain, e.g., sos.arpa.arpa used for infrastructure functions.arpa used for infrastructure functions top-level queries done only rarely top-level queries done only rarely results are cached at client results are cached at client *.us.sos. arpa *.sos. arpa *.nj.us.sos. arpa     firedept.leonia.nj.gov leonia.nj.us.sos.arpa?

April 26, Obtaining all sub-regions us.sos. arpa nj.us.sos. arpaus.sos.arpaPTRal.us.sos.arpaus.sos.arpaPTRak.us.sos.arpa us.sos.arpaPTRnj.us.sos.arpa …PTR… CN=us A1=nj A2=bergen A3=leonianj.us.sos.arpaPTRsussex.nj.us.sos.arpanj.us.sos.arpaPTRpassaic.nj.us.sos.arpa nj.us.sos.arpaPTRbergen.nj.us.sos.arpa …PTR…

April 26, What about geo addresses? Store one DNS record for each PSAP Store one DNS record for each PSAP or whatever the last caller-visible SIP proxy is or whatever the last caller-visible SIP proxy is could be state, county, city, … could be state, county, city, … Point to record containing PSAP boundary Point to record containing PSAP boundary retrieved via HTTP (web) retrieved via HTTP (web) cached as needed cached as needed Records polygon edges of PSAP service area (longitude-latitude tuples) Records polygon edges of PSAP service area (longitude-latitude tuples) Same descent of hierarchy Same descent of hierarchy at each level, search all leaves for match at each level, search all leaves for match Bergen Passaic Atlantic …

April 26, Address hiding Some advocate hiding IP addresses of PSAPs (or groups of PSAPs) Some advocate hiding IP addresses of PSAPs (or groups of PSAPs) Not clear what this means Not clear what this means if call made, IP address will be returned in packets if call made, IP address will be returned in packets Can, however, have different perimeters Can, however, have different perimeters source address of SIP and audio packets

April 26, Routing layers firewall boundary

April 26, Privacy and authentication Want to ensure privacy of call setup information Want to ensure privacy of call setup information prevent spoofing of call origins prevent spoofing of call origins but can’t enforce call authentication but can’t enforce call authentication need to authenticate call destination need to authenticate call destination ideally, certificate for PSAPs ideally, certificate for PSAPs but initially just verify that reached DNS-indicated destination but initially just verify that reached DNS-indicated destination use TLS (SSL), as in use TLS (SSL), as in host certificates widely available host certificates widely available just need a domain name and a credit card just need a domain name and a credit card

April 26, Testing emergency calls Current E911 system has no good way to test 911 reachability without interfering with emergency services Current E911 system has no good way to test 911 reachability without interfering with emergency services With VoIP, more distributed system  more need for testing With VoIP, more distributed system  more need for testing Use SIP OPTIONS request  route request, but don’t reach call taker Use SIP OPTIONS request  route request, but don’t reach call taker Also, DNS model allows external consistency checking Also, DNS model allows external consistency checking e.g., nationwide 911 testing agency e.g., nationwide 911 testing agency

April 26, Open issues Technical (protocol) issues: Technical (protocol) issues: details of DNS records details of DNS records top-level DNS domain? top-level DNS domain? how to do testing with minimal impact? how to do testing with minimal impact? Operational issues: Operational issues: who runs sos.arpa and us.sos.arpa? who runs sos.arpa and us.sos.arpa? export of MSAG information into DNS? export of MSAG information into DNS? will DSL and cable modem carriers provide location information? will DSL and cable modem carriers provide location information? Funding issues: Funding issues: use IP-layer funding for 911, not voice services use IP-layer funding for 911, not voice services

April 26, Conclusion Good news: Good news: VoIP-based 911 is not nearly as hard as Phase II wireless VoIP-based 911 is not nearly as hard as Phase II wireless can be leveraged to provide simpler Phase II services for non-VoIP terminals can be leveraged to provide simpler Phase II services for non-VoIP terminals PC-based end system can be maintained as is PC-based end system can be maintained as is use of COTS, across national borders use of COTS, across national borders Challenges: Challenges: cannot simply add one more patch to existing circuit- switched 911 system cannot simply add one more patch to existing circuit- switched 911 system