-
"Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information", Henning Schulzrinne, Hannes Tschofenig, John Morris, Jorge Cuellar, James Polk, 26-Jun-08. ( bytes)
- This document defines an authorization policy language for
controlling access to location information. It extends the Common
Policy authorization framework to provide location-specific access
control. More specifically, this document defines condition elements
specific to location information in order to restrict access based on
the current location of the Target. Furthermore, it offers location-
specific transformation elements to reduce the granularity of the
returned location information.
-
"Carrying Location Objects in RADIUS and Diameter", Hannes Tschofenig, Farid Adrangi, Mark Jones, Avi Lior, Bernard Aboba, 31-Jan-08. ( bytes)
- This document describes procedures for conveying access network
ownership and location information based on a civic and geospatial
location format in Remote Authentication Dial In User Service
(RADIUS) and Diameter.
The distribution of location information is a privacy sensitive task.
Dealing with mechanisms to preserve the user's privacy is important
and addressed in this document.
-
"GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations", James Winterbottom, Martin Thomson, Hannes Tschofenig, 19-Feb-08. ( bytes)
- The Presence Information Data Format Location Object (PIDF-LO)
specification provides a flexible and versatile means to represent
location information. There are, however, circumstances that arise
when information needs to be constrained in how it is represented.
In these circumstances the range of options that need to be
implemented are reduced. There is growing interest in being able to
use location information contained in a PIDF-LO for routing
applications. To allow successful interoperability between
applications, location information needs to be normative and more
tightly constrained than is currently specified in the RFC 4119
(PIDF-LO). This document makes recommendations on how to constrain,
represent and interpret locations in a PIDF-LO. It further
recommends a subset of GML that is mandatory to implement by
applications involved in location based routing.
-
"A Document Format for Filtering and Reporting Location Notications in the Presence Information Document Format Location Object (PIDF-LO)", Rohan Mahy, Brian Rosen, 14-Jul-08. ( bytes)
- This document describes filters which limit asynchronous location
notifications to compelling events. The resulting location
information is conveyed in existing location formats wrapped in
GEOPRIV privacy extensions to the Presence Information Document
Format (PIDF-LO)
-
"GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements", Hannes Tschofenig, Henning Schulzrinne, 29-Jun-08. ( bytes)
- This document provides a problem statement, lists requirements and
captures design aspects for a Geopriv Layer 7 Location Configuration
Protocol L7 (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 Protocol (LoST) or to
convey location within SIP to other entities.
-
"HTTP Enabled Location Delivery (HELD)", Mary Barnes, James Winterbottom, Martin Thomson, Barbara Stark, 10-Jul-08. ( bytes)
- A Layer 7 Location Configuration Protocol (L7 LCP) is described that
is used for retrieving location information from a server within an
access network. The protocol includes options for retrieving
location information in two forms: by value and by reference. The
protocol is an extensible application-layer protocol that is
independent of session-layer. This document describes the use of
HyperText Transfer Protocol (HTTP) and HTTP over Transport Layer
Security (HTTP/TLS) as transports for the protocol.
-
"Requirements for a Location-by-Reference Mechanism", Roger Marshall, 8-Jul-08. ( bytes)
- This document defines terminology and provides requirements relating
to Location-by-Reference approach using a location URI to handle
location information within signaling and other Internet messaging.
-
"Discovering the Local Location Information Server (LIS)", Martin Thomson, James Winterbottom, 10-Jul-08. ( bytes)
- A method is described for the discovery of a Location Information
Server. The method uses a Dynamic Host Configuration Protocol (DHCP)
option. DHCP options are defined for both IPv4 and IPv6 DHCP. A
URI-enabled NAPTR (U-NAPTR) method is described for use where the
DHCP option is unsuccessful. This document defines a U-NAPTR
Application Service for a LIS, with a specific Application Protocol
for the HTTP Enabled Location Delivery (HELD) protocol. The held:
URI scheme, the product of the discovery process, is defined by this
document.
-
"Dynamic Host Configuration Protocol (DHCP) Option for a Location Uniform Resource Identifier (URI)", James Polk, 16-Jun-08. ( bytes)
- This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for the Location Uniform Resource Identifier (URI) of an
endpoint. For example, an endpoint can be a Session Initiation
Protocol (SIP) User Agent (i.e., a phone). This Location-URI can be
included in a UA's signaling messages to inform other nodes of that
entity's geographic location, once the URI is dereferenced by a
Location Recipient.
-
"Implications o. ( bytes)
- This document explores an ambiguity in the interpretation of the
element of the Presence Information Data
Format for Location Objects (PIDF-LO) in cases where PIDF-LO is
conveyed by the Session Initiation Protocol (SIP). It provides
recommendations for how the SIP location conveyance mechanism should
adapt to these ambiguities.
Documents standardizing the SIP location conveyance mechanisms will
be standards-track documents processed according to the usual SIP
process. This document is intended primarily to provide the SIP
working group with a statement of the consensus of the GEOPRIV
working group on this topic. It secondarily provides tutorial
information on the problem space for the general reader.
IETF Secretariat - Please send questions, comments, and/or
suggestions to ietf-web@ietf.org.
Return to Internet-Draft directory.
Return to IETF home page.