RFC 5985: HTTP-Enabled Location Delivery (HELD)
In plain English — editorial summary, not part of the RFC
This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of the session layer. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5985
- Published
- September 2010
- Authors
- M. Barnes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 39
- Also known as
- —
- Updated by:
- RFC 7840
Topics
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 5986Discovering the Local Location Information Server (LIS)Current
September 2010
- RFC 5993RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)Current
October 2010
- RFC 5968Guidelines for Extending the RTP Control Protocol (RTCP)Current
September 2010
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 5947Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)Current
September 2010
- RFC 6035Session Initiation Protocol Event Package for Voice Quality ReportingCurrent
November 2010
- RFC 5924Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 CertificatesCurrent
June 2010
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
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?