Discovering Location-to-Service Translation Servers Using the Dynamic Host Configuration Protocol
RFC 5223, “Discovering Location-to-Service Translation Servers Using the Dynamic Host Configuration Protocol”, is a Proposed Standard document published in August 2008 by H. Schulzrinne, J. Polk, H. Tschofenig. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5223 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5222 LoST: A Location-to-Service Translation Protocol
- RFC 5224 Diameter Policy Processing Application
- RFC 5221 Requirements for Address Selection Mechanisms
- RFC 5225 RObust Header Compression Version 2 : Profiles for RTP, UDP, IP, ESP and UDP-Lite
- RFC 5220 Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules
- RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
- RFC 5219 A More Loss-Tolerant RTP Payload Format for MP3 Audio
- RFC 5227 IPv4 Address Conflict Detection