GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
RFC 5687
Internet Engineering Task Force (IETF) H. Tschofenig
Request for Comments: 5687 Nokia Siemens Networks
Category: Informational H. Schulzrinne
ISSN: 2070-1721 Columbia University
March 2010
GEOPRIV Layer 7 Location Configuration Protocol:
Problem Statement and Requirements
Abstract
This document provides a problem statement, lists requirements, and
captures design aspects for a GEOPRIV Layer 7 (L7) Location
Configuration Protocol (LCP). This protocol aims to allow an end
host to obtain location information, by value or by reference, from a
Location Information Server (LIS) that is located in the access
network. The obtained location information can then be used for a
variety of different protocols and purposes. For example, it can be
used as input to the Location-to-Service Translation (LoST) Protocol
or to convey location within the Session Initiation Protocol (SIP) to
other entities.
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/rfc5687.
Tschofenig & Schulzrinne Informational [Page 1]
RFC 5687 GEOPRIV L7 LCP: Problem Statement March 2010
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.
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Scenarios .......................................................4
3.1. Fixed-Wired Environment ....................................4
3.2. Mobile Network .............................................7
3.3. Wireless Access ............................................8
4. Discovery of the Location Information Server ....................9
5. Identifier for Location Determination ..........................11
6. Requirements ...................................................14
7. Security Considerations ........................................16
8. Contributors ...................................................17
9. Acknowledgements ...............................................18
10. References ....................................................18
10.1. Normative References .....................................18
10.2. Informative References ...................................18
Tschofenig & Schulzrinne Informational [Page 2]
RFC 5687 GEOPRIV L7 LCP: Problem Statement March 2010
1. Introduction
This document provides a problem statement, lists requirements, and
captures design aspects for a GEOPRIV Layer 7 (L7) Location
Configuration Protocol (LCP). The protocol has two purposes:
o It is used by a device to obtain its own location (referred as
"Location by Value" or LbyV) from a dedicated node, called the
Location Information Server (LIS).
o It enables the device to obtain a reference to location
information (referred as "Location by Reference" or LbyR). This
reference can take the form of a subscription URI, such as a SIP
presence-based Uniform Resource Identifier (URI), an HTTP/HTTPS
URI, or another URI. The requirements related to the task of
obtaining an LbyR are described in a separate document, see
Show full document text