Skip to main content

Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
RFC 5223

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Location-to-Service Translation (LoST) Protocol describes an XML- based protocol for mapping service identifiers and geospatial …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from ecrit-chairs@ietf.org, draft-ietf-ecrit-dhc-lost-discovery@ietf.org to (None)
2008-08-05
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2008-08-05
Cindy Morgan [Note]: 'RFC 5223' added by Cindy Morgan
2008-08-05
(System) RFC published