1 / 7

Update on Location-to-Service Translation (LoST) Protocol

Update on Location-to-Service Translation (LoST) Protocol. Andrew Newton, SunRocket, Inc. Tuesday, 10 April 2007 ESW’07, Washington, D.C. LoST Background. Central work item of IETF/ECRIT. For emergency calling, its purpose is to map location information to PSAP URIs.

quynh
Download Presentation

Update on Location-to-Service Translation (LoST) Protocol

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. Update on Location-to-Service Translation (LoST) Protocol Andrew Newton, SunRocket, Inc. Tuesday, 10 April 2007 ESW’07, Washington, D.C.

  2. LoST Background • Central work item of IETF/ECRIT. • For emergency calling, its purpose is to map location information to PSAP URIs. • Though LoST is applicable in other areas. • Bits on the wire properties: • XML over HTTP/HTTPS • Decentralized and multi-rooted. • Utilizes caching and multi-service node model for robustness. ESW'07

  3. Standards Progress • Sixth draft (-05) completed ECRIT working group last call. • Last call comments to be incorporated into -06, which is coming very soon. • Next stop, IETF last call and IESG evaluation. ESW'07

  4. Changes Since ESW’06 • Better compartmentalization of response data: • New <mapping> element which holds the important result data, and the ability to have multiple of <mapping> elements. Not only does this organize the data better, it will better enable re-use of these items in other specs (such as the fg-to-fg syncing spec) and with future things like XML DSig. • New Warnings and Errors section. • Separated out address validation. • Added NO-CACHE and NO-EXPIRATION to caching semantics. ESW'07

  5. Changes Since ESW’06 cont’d • Requests and responses now have a new <path> element which contains the <via> elements. This better enables loop detection. • The <listServices> query has had the location version separated out into a new query called <listServicesByLocation>. • Removal of LoST URI. • New terms & definitions. • More clarifying text. • Bug fixes in examples. ESW'07

  6. LoST -06 (in progress) • Usual “oops” clean-up • A few more warnings/errors to be added. • Define whether <listServicesByLocationResponse> and <listServicesResponse> need ‘expires’ parameter? • Caching of the <serviceList>. • DONE • until the IESG gets their hands on it... ESW'07

  7. Implementations • Implementations and interop testing in progress • Wonsang Song and Yong-Jul Kim (Columbia U.) • completed -05 seeker, resolver, authoritative server, FG, ... • Krzysztof Rzecki, Piotr Blaszczyk, Anna Makarowska, Michal Niedzwiecki (CCNS SA with cooperation of Institute of Telecomputing at Cracow University of Technology) ESW'07

More Related