[Ecrit] RFC 8876 on Non-interactive Emergency Calls
rfc-editor@rfc-editor.org Tue, 22 September 2020 17:32 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C00A3A09C1; Tue, 22 Sep 2020 10:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kAKp_yB_obg; Tue, 22 Sep 2020 10:32:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08F103A03FC; Tue, 22 Sep 2020 10:32:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 39C69F40788; Tue, 22 Sep 2020 10:32:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ecrit@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200922173249.39C69F40788@rfc-editor.org>
Date: Tue, 22 Sep 2020 10:32:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/-D8fUcDmKE5CKviTGH-xpc4lwFw>
Subject: [Ecrit] RFC 8876 on Non-interactive Emergency Calls
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2020 17:32:58 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8876
Title: Non-interactive Emergency Calls
Author: B. Rosen,
H. Schulzrinne,
H. Tschofenig,
R. Gellens
Status: Standards Track
Stream: IETF
Date: September 2020
Mailbox: br@brianrosen.net,
hgs+ecrit@cs.columbia.edu,
Hannes.Tschofenig@gmx.net,
rg+ietf@coretechnologyconsulting.com
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ecrit-data-only-ea-22.txt
URL: https://www.rfc-editor.org/info/rfc8876
DOI: 10.17487/RFC8876
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.
This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC