1 / 8

Origins of ECRIT

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

libitha
Download Presentation

Origins of ECRIT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 ConsiderationsWho knows the location of the end host? OSI Model Common point - The end device! VoIP, Inc. (Application Service Provider) Layer 7 ISP, Inc. (Internet Service Provider) Layer 3 Last Mile, Inc. (Access Provider) Layer 2 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. ECRIT GEOPRIV Policy Emergency Service Location Generator Location Recipient Location Server LoST Server Proxy Server User Agent Service URN Service URI SIP (learned from LoST) Logical Architecture

  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.htmlhttp://www.ietf.org/html.charters/geopriv-charter.htmlhttp://www.ietf.org/html.charters/ecrit-charter.htmlhttp://www.ietf.org/html.charters/geopriv-charter.html jon.peterson@neustar.biz

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

  8. Example Geopriv block <gp:geopriv> <gp:location-info> <gml:location> <gml:Point gml:id="point96" srsName="epsg:4326"> <gml:coordinates>31:56:00S 115:50:00E</gml:coordinates> </gml:Point> </gml:location> </gp:location-info> <gp:usage-rules> <gp:retransmission-allowed>no</gp:retransmission-allowed> <gp:retention-expiry>2003-06-23T04:57:29Z </gp:retention-expiry> </gp:usage-rules> </gp:geopriv>

More Related