datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Use of Target Identity in HTTP-Enabled Location Delivery (HELD)
draft-winterbottom-geopriv-held-identity-extensions-10

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2009-08-27
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-geopriv-held-identity-extensions
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-winterbottom-geopriv-held-identity-extensions

Abstract

When a Location Information Server receives a request for location information (using the locationRequest message), described in the base HTTP Enabled Location Delivery (HELD) specification, it uses the source IP address of arriving message as a pointer to the location determination process. This is sufficient in environments where the location of a Device can be determined based on its IP address. Two additional use cases are addresses by this document. In the first, location configuration requires additional or alternative identifiers from the source IP address provided in the request. In the second, an entity other than the Device requests the location of the Device. This document extends the HELD protocol to allow the location request message to carry Device identifiers. Privacy and security considerations describe the conditions where requests containing identifiers are permitted.

Authors

Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Richard Barnes <rbarnes@bbn.com>
Martin Thomson <martin.thomson@andrew.com>
James Winterbottom <james.winterbottom@andrew.com>

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