RFC 5222: LoST: A Location-to-Service Translation Protocol
In plain English — editorial summary, not part of the RFC
This document describes an XML-based protocol for mapping service identifiers and geodetic or civic location information to service contact URIs. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5222
- Published
- August 2008
- Authors
- T. Hardie; A. Newton; H. Schulzrinne; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 69
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 8917The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service TagCurrent
October 2020
- RFC 9036Changing the Location-to-Service Translation (LoST) Location Profiles Registry PolicyCurrent
June 2021
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7852Additional Data Related to an Emergency CallCurrent
July 2016
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 5223Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)Current
August 2008
- RFC 5245Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer ProtocolsObsoleted
April 2010
- RFC 5069Security Threats and Requirements for Emergency Call Marking and MappingCurrent
January 2008
- RFC 5031A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesUpdated
January 2008
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 5016Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices ProtocolCurrent
October 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?