Browse Prior Art Database

A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol (RFC7840) Disclosure Number: IPCOM000246718D
Original Publication Date: 2016-May-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 32 page(s) / 31K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Winterbottom: AUTHOR [+3]


The general Emergency Context Resolution with Internet Technology (ECRIT) calling models described in [RFC6443] and [RFC6881] require a local Location-to-Service Translation (LoST) server or network of forest guides in order to determine the address of the Public Safety Answering Point (PSAP) in the best position to handle a call. Networks of forest guides have not materialized and while PSAPs are moving towards IP networks, LoST server deployment is not ubiquitous. Some regions and countries have expressed reluctance to deploy LoST servers making aspects of the current ECRIT architecture hard to realize.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                   J. Winterbottom Request for Comments: 7840                   Winterb Consulting Services Updates: 5985, 6881                                        H. Tschofenig Category: Standards Track ISSN: 2070-1721                                                 L. Liess                                                         Deutsche Telekom                                                                 May 2016

                     A Routing Request Extension for            the HTTP-Enabled Location Delivery (HELD) Protocol


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Winterbottom, et al.         Standards Track                    [Page 1]
 RFC 7840                      HELD Routing                      May 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warran...