Skip to main content

Location-to-Service Translation Protocol (LoST) Extension: ServiceListBoundary
draft-wolf-ecrit-lost-servicelistboundary-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Karl Wolf
Last updated 2009-10-01
Replaced by draft-ietf-ecrit-lost-servicelistboundary
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ecrit-lost-servicelistboundary
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

LoST maps service identifiers and location information to service contact URIs. If a LoST client wants to discover available services for a particular location, it will perform a <listServicesByLocation> query to the LoST server. However, the response from the LoST server does not provide information about the geographical region for which the returned service list is valid. Therefore, this document proposes a ServiceListBoundary to assist the client to not miss a change in available services when moving.

Authors

Karl Wolf

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