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

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    ecrit mailing list <ecrit@ietf.org>, 
    ecrit chair <ecrit-chairs@tools.ietf.org>
Subject: Protocol Action: 'Discovering Location-to-Service 
         Translation (LoST) Servers Using the Dynamic Host Configuration 
         Protocol (DHCP)' to Proposed Standard 

The IESG has approved the following document:

- 'Discovering Location-to-Service Translation (LoST) Servers Using the 
   Dynamic Host Configuration Protocol (DHCP) '
   <draft-ietf-ecrit-dhc-lost-discovery-04.txt> as a Proposed Standard

This document is the product of the Emergency Context Resolution with 
Internet Technologies Working Group. 

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-dhc-lost-discovery-04.txt

Technical Summary
 
The Location-to-Service Translation Protocol (LoST) 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. Such a LoST server placement provides benefits in
disaster situations with intermittent network connectivity 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).

Working Group Summary
 
There is consensus in the WG to publish this document.
 
Protocol Quality
 
Although the LoST specification has been implemented there are 
no implementations known for the DHCP-based discovery 
procedure. From a deployment point of view it is likely 
that the DNS-based discovery procedure will be available
before this document will see a deployment.