datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
draft-ietf-ecrit-dhc-lost-discovery-03

RFC
Document Stream: IETF
Last updated: 2008-05-29
Replaces: draft-polk-ecrit-dhc-lost-discovery
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 5223
IANA Action State: RFC-Ed-Ack 
Responsible AD: Jon Peterson
Send notices to: ecrit-chairs@tools.ietf.org, draft-ietf-ecrit-dhc-lost-discovery@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ecrit-dhc-lost-discovery.

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.

Authors:
James Polk <jmpolk@cisco.com>
Hannes Tschofenig <hannes.tschofenig@nsn.com>
Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)