Skip to main content

Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
RFC 6155

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'When a Location Information Server receives a request for location information (using the locationRequest message), described …
Received changes through RFC Editor sync (changed abstract to '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 the 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 addressed 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. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from geopriv-chairs@ietf.org, draft-ietf-geopriv-held-identity-extensions@ietf.org to (None)
2011-03-14
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-03-14
Cindy Morgan [Note]: changed to 'RFC 6155'
2011-03-11
(System) RFC published