RFC 7852: Additional Data Related to an Emergency Call
In plain English — editorial summary, not part of the RFC
When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, the access network provider to which the device is connected, and all service providers in the path of the call have information about the call, the caller, or the location, which is helpful for the PSAP to have in handling the emergency. This document describes data structures and mechanisms to convey such data to the PSAP. The intent is that every emergency call carry as much of the information described here as possible using the mechanisms described here. The mechanisms permit the data to be conveyed by reference (as an external resource) or by value (within the body of a SIP message or a location object). This follows the tradition of prior emergency services standardization work where data can be conveyed by value within the call signaling (i.e., in the body of the SIP message) or by reference.
Document record
- Document ID
- RFC7852
- Published
- July 2016
- Authors
- R. Gellens; B. Rosen; H. Tschofenig; R. Marshall; J. Winterbottom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 113
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5222LoST: A Location-to-Service Translation ProtocolUpdated
August 2008
- RFC 8917The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service TagCurrent
October 2020
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 7851Peer-to-Peer (P2P) Overlay DiagnosticsCurrent
May 2016
- RFC 7850Registering Values of the SDP 'proto' Field for Transporting RTP Media over TCP under Various RTP ProfilesCurrent
April 2016
- RFC 7848Mark and Signed Mark Objects MappingCurrent
June 2016
- RFC 7845Ogg Encapsulation for the Opus Audio CodecUpdated
April 2016
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
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?