RFC 6155: Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6155
- Published
- March 2011
- Authors
- J. Winterbottom; M. Thomson; H. Tschofenig; R. Barnes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 27
- Also known as
- —
- Updated by:
- RFC 6915
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6157IPv6 Transition in the Session Initiation Protocol (SIP)Current
April 2011
- RFC 6140Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 6135An Alternative Connection Model for the Message Session Relay Protocol (MSRP)Current
February 2011
- RFC 6128RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) SessionsCurrent
February 2011
- RFC 6184RTP Payload Format for H.264 VideoCurrent
May 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 6118Update of Legacy IANA Registrations of EnumservicesCurrent
March 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?