Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

B. Rosen
H. Schulzrinne
H. Tschofenig
R. Gellens

Stream:

IETF

Source:

ecrit (art)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Use of the Internet for emergency calling is described in RFC 6443,'Framework for Emergency Calling Using Internet Multimedia'. In somecases of emergency calls, the transmission of application data is allthat is needed, and no interactive media channel is established: asituation referred to as 'non-interactive emergency calls', where,unlike most emergency calls, there is no two-way interactive mediasuch as voice or video or text. This document describes use of a SIPMESSAGE transaction that includes a container for the data based onthe Common Alerting Protocol (CAP). That type of emergency requestdoes not establish a session, distinguishing it from SIP INVITE,which does. Any device that needs to initiate a request foremergency services without an interactive media channel would use themechanisms in this document.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.