RFC 8876: Non-interactive Emergency Calls
In plain English — editorial summary, not part of the RFC
Use of the Internet for emergency calling is described in RFC 6443, 'Framework for Emergency Calling Using Internet Multimedia'. In some cases of emergency calls, the transmission of application data is all that is needed, and no interactive media channel is established: a situation referred to as 'non-interactive emergency calls', where, unlike most emergency calls, there is no two-way interactive media such as voice or video or text. This document describes use of a SIP MESSAGE transaction that includes a container for the data based on the Common Alerting Protocol (CAP). That type of emergency request does not establish a session, distinguishing it from SIP INVITE, which does. Any device that needs to initiate a request for emergency services without an interactive media channel would use the mechanisms in this document.
Document record
- Document ID
- RFC8876
- Published
- September 2020
- Authors
- B. Rosen; H. Schulzrinne; H. Tschofenig; R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3283Guide to Internet CalendaringCurrent
July 2002
- RFC 8873Message Session Relay Protocol (MSRP) over Data ChannelsCurrent
January 2021
- RFC 8871A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)Current
January 2021
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
January 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8887A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocketCurrent
August 2020
- RFC 8865T.140 Real-Time Text Conversation over WebRTC Data ChannelsCurrent
January 2021
- RFC 8864Negotiation Data Channels Using the Session Description Protocol (SDP)Current
January 2021
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?