Use of Device Identity in HTTP-Enabled Location Delivery
RFC 6155, “Use of Device Identity in HTTP-Enabled Location Delivery”, is a Proposed Standard document published in March 2011 by J. Winterbottom, M. Thomson, H. Tschofenig, R. Barnes. It has since been updated by RFC 6915. The canonical text is published by the RFC Editor.
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 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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6155 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6154 IMAP LIST Extension for Special-Use Mailboxes
- RFC 6156 Traversal Using Relays around NAT Extension for IPv6
- RFC 6153 DHCPv4 and DHCPv6 Options for Access Network Discovery and Selection Function Discovery
- RFC 6157 IPv6 Transition in the Session Initiation Protocol
- RFC 6152 SMTP Service Extension for 8-bit MIME Transport
- RFC 6158 RADIUS Design Guidelines
- RFC 6151 Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms
- RFC 6159 Session-Specific Explicit Diameter Request Routing