1. Origins of ECRIT IETF has been working on location since 2000 –Spatial BoF, eventually GEOPRIV chartered in 2001 GEOPRIV provides location information along with privacy directives –For commercial location-based services, privacy is paramount –Concern about location being used for unsolicited advertisements, especially targeting mobile phones –Emergency services was always an important use case ECRIT first meets in 2004 –Building off of the GEOPRIV work and architecture –And the ‘sipping-emergency’ design team of SIPPING –Initial focus on using location information to learn how to direct emergency calls on the Internet

2. Architectural Considerations Who knows the location of the end host? Last Mile, Inc. (Access Provider) ISP, Inc. (Internet Service Provider) VoIP, Inc. (Application Service Provider) OSI Model Layer 7 Layer 2 Layer 3 Common point - The end device! The access network, the Internet service and the application service provider might not be the same party.

3. Architectural Components Signaling Protocol –While little of the work is truly SIP-specific, most was designed with SIP in mind Signaling protocols must understand presence and URIs Presence –Building off previous presence work in the IETF, PIDF –Location information is provided in a presence document, consisting of Location format, basically a container –GML and civic location formats are specified –Other formats can be carried as well Privacy rules Directory Lookups –Mappings of service URNs (indication of the type of service) and locations to the proper network PSAP

4. Logical Architecture User Agent Proxy Server Service URN SIP Location Generator Location Server Policy Location Recipient GEOPRIV LoST Server Emergency Service Service URI (learned from LoST) ECRIT

5. Progress GEOPRIV work substantially complete –Still some work on location configuration methods ECRIT work is maturing –Requirements and service URN work is leaving the group –LoST Protocol still under development Much future work –Work on support for emergency calls in SIP endpoints The IETF is not going to define user interfaces Protocol support for service identifiers

6. http://www.ietf.org/html.charters/ecrit-charter.html http://www.ietf.org/html.charters/ecrit-charter.html http://www.ietf.org/html.charters/geopriv-charter.html jon.peterson@neustar.biz

7. Geopriv architecture Location Server Publication Location Generator Location Recipient Notification Policy

8. Example Geopriv block 31:56:00S 115:50:00E no 2003-06-23T04:57:29Z