Non-interactive Emergency Calls
RFC 8876, “Non-interactive Emergency Calls”, is a Proposed Standard document published in September 2020 by B. Rosen, H. Schulzrinne, H. Tschofenig, R. Gellens. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8876 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8875 Working Group GitHub Administration
- RFC 8877 Guidelines for Defining Packet Timestamps
- RFC 8874 Working Group GitHub Usage Guidance
- RFC 8879 TLS Certificate Compression
- RFC 8880 Special Use Domain Name 'ipv4only.arpa'
- RFC 8881 Network File System Version 4 Minor Version 1 Protocol
- RFC 8882 DNS-Based Service Discovery Privacy and Security Requirements
- RFC 8883 ICMPv6 Errors for Discarding Packets Due to Processing Limits