datatracker.ietf.org
Sign in
Version 5.9.0, 2014-12-18
Report a bug

Location-to-Service Translation (LoST) Service List Boundary Extension
RFC 6197

Internet Engineering Task Force (IETF)                           K. Wolf
Request for Comments: 6197                                        nic.at
Category: Experimental                                        April 2011
ISSN: 2070-1721

 Location-to-Service Translation (LoST) Service List Boundary Extension

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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6197.

Wolf                          Experimental                      [Page 1]
RFC 6197                   serviceListBoundary                April 2011

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction ....................................................3
   2. Terminology .....................................................4
   3. LoST Extensions .................................................4
      3.1. Extensions to <listServicesByLocation> .....................4
      3.2. Retrieving the <serviceListBoundary> via
           <getServiceListBoundary> ...................................7
      3.3. <serviceListBoundary> ......................................8
      3.4. Implementation Considerations ..............................9
           3.4.1. Server Side .........................................9
           3.4.2. Client Side .........................................9
   4. Security and Privacy Considerations ............................10
   5. IANA Considerations ............................................10
      5.1. Relax NG Schema Registration ..............................10
      5.2. Namespace Registration ....................................13
   6. Acknowledgements ...............................................14
   7. References .....................................................14
      7.1. Normative References ......................................14
      7.2. Informative References ....................................15

Wolf                          Experimental                      [Page 2]

[include full document text]