File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 6443, RFC 6881

Authors:

R. Gellens
B. Rosen
H. Tschofenig
R. Marshall
J. Winterbottom

Stream:

IETF

Source:

ecrit (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7852

Discuss this RFC: Send questions or comments to the mailing list ecrit@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7852

Abstract

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.