RFC 5223: Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
In plain English — editorial summary, not part of the RFC
The Location-to-Service Translation (LoST) Protocol describes an XML- based protocol for mapping service identifiers and geospatial or civic location information to service contact Uniform Resource Locators (URLs). LoST servers can be located anywhere, but a placement closer to the end host, e.g., in the access network, is desirable. In disaster situations with intermittent network connectivity, such a LoST server placement provides benefits regarding the resiliency of emergency service communication. This document describes how a LoST client can discover a LoST server using the Dynamic Host Configuration Protocol (DHCP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5223
- Published
- August 2008
- Authors
- H. Schulzrinne; J. Polk; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5222LoST: A Location-to-Service Translation ProtocolUpdated
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
- RFC 5432Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)Current
March 2009
- RFC 5012Requirements for Emergency Context Resolution with Internet TechnologiesCurrent
January 2008
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?