RFC 7840: A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol
In plain English — editorial summary, not part of the RFC
For cases where location servers have access to emergency routing information, they are able to return routing information with the location information if the location request includes a request for the desired routing information. This document specifies an extension to the HTTP-Enabled Location Delivery (HELD) protocol that updates RFC 5985 to support this function. Allowing location and routing information to be acquired in a single request response exchange updates RFC 6881, as current location acquisition and route determination procedures are separate operations.
Document record
- Document ID
- RFC7840
- Published
- May 2016
- Authors
- J. Winterbottom; H. Tschofenig; L. Liess
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8787Location Source Parameter for the SIP Geolocation Header FieldCurrent
May 2020
- RFC 8147Next-Generation Pan-European eCallCurrent
May 2017
- RFC 8148Next-Generation Vehicle-Initiated Emergency CallsCurrent
May 2017
- RFC 8606ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header FieldCurrent
June 2019
- RFC 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 8917The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service TagCurrent
October 2020
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
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?