Skip to main content

Non-interactive Emergency Calls
RFC 8876

Revision differences

Document history

Date By Action
2020-09-25
(System) IANA registries were updated to include RFC8876
2020-09-25
(System) IANA Action state changed to RFC-Ed-Ack from No IANA Actions
2020-09-22
(System)
Received changes through RFC Editor sync (created alias RFC 8876, changed title to 'Non-interactive Emergency Calls', changed abstract to 'Use of the Internet for …
Received changes through RFC Editor sync (created alias RFC 8876, changed title to 'Non-interactive Emergency Calls', changed abstract to '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.', changed pages to 25, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-09-22, changed IESG state to RFC Published)
2020-09-22
(System) RFC published