Internet Engineering Task Force (IETF) R. Marshall, Ed.
Request for Comments: 5808 TCS
Category: Informational May 2010
ISSN: 2070-1721
Requirements for a Location-by-Reference Mechanism
Abstract
This document defines terminology and provides requirements relating
to the Location-by-Reference approach using a location Uniform
Resource Identifier (URI) to handle location information within
signaling and other Internet messaging.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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/rfc5808.
Copyright Notice
Copyright (c) 2010 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.
Marshall Informational [Page 1]RFC 5808 GEOPRIV LbyR Requirements May 2010
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 .....................................................5
3. Overview of Location-by-Reference ...............................6
3.1. Location URI Usage .........................................7
3.2. Location URI Expiration ....................................8
3.3. Location URI Authorization .................................8
3.4. Location URI Construction ..................................9
4. High-Level Requirements .........................................9
4.1. Requirements for a Location Configuration Protocol .........9
4.2. Requirements for a Location Dereference Protocol ..........11
5. Security Considerations ........................................12
6. Acknowledgements ...............................................13
7. References .....................................................13
7.1. Normative References ......................................13
7.2. Informative References ....................................13
Marshall Informational [Page 2]RFC 5808 GEOPRIV LbyR Requirements May 20101. Introduction
All location-based services rely on ready access to location
information. Location information can be used in either a direct,
Location-by-Value (LbyV) approach or an indirect, Location-by-
Reference (LbyR) approach.
For LbyV, location information is conveyed directly in the form of a
Presence Information Data Format Location Object (PIDF-LO) [RFC4119].
Using LbyV might be either infeasible or undesirable in some
circumstances. There are cases where LbyR is better able to address
location requirements for a specific architecture or application.
This document provides a list of requirements for use with the LbyR
approach, and leaves the LbyV model explicitly out of scope.