Use of Target Identity in HTTP-Enabled Location Delivery (HELD)
draft-winterbottom-geopriv-held-identity-extensions-10
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hannes Tschofenig , Richard Barnes , Martin Thomson , James Winterbottom | ||
| Last updated | 2009-08-27 | ||
| Replaced by | draft-ietf-geopriv-held-identity-extensions | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-geopriv-held-identity-extensions | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Richard Barnes
Martin Thomson
James Winterbottom
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)