datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Location-to-Service Translation (LoST) Service List Boundary Extension
draft-ietf-ecrit-lost-servicelistboundary-05

RFC
Document Stream: IETF
Last updated: 2010-12-16
Replaces: draft-wolf-ecrit-lost-servicelistboundary
Intended RFC status: Experimental
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6197
IANA Action State: RFC-Ed-Ack 
Responsible AD: Robert Sparks
Send notices to: ecrit-chairs@tools.ietf.org, draft-ietf-ecrit-lost-servicelistboundary@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-lost-servicelistboundary.

Abstract:
Location-to-Service Translation (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 LoST server, in its response, does not provide context information; that is, it does not provide any additional information about the geographical region within which the returned list of services is considered valid. Therefore, this document defines a Service List Boundary that returns a local context along with the list of services returned, in order to assist the client in not missing a change in available services when moving. This document defines an Experimental Protocol for the Internet community.

Authors:
Karl Wolf <karlheinz.wolf@nic.at>

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