RFC 7852 on Additional Data Related to an Emergency Call

rfc-editor@rfc-editor.org Sat, 30 July 2016 05:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19B712D1E4; Fri, 29 Jul 2016 22:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 MNJf7moY4VcO; Fri, 29 Jul 2016 22:16:32 -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 073B012D108; Fri, 29 Jul 2016 22:16:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B0997B80299; Fri, 29 Jul 2016 22:16:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7852 on Additional Data Related to an Emergency Call
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160730051631.B0997B80299@rfc-editor.org>
Date: Fri, 29 Jul 2016 22:16:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/NF4wdjW9YA33c0YYaaxfE0Wvzac>
Cc: drafts-update-ref@iana.org, ecrit@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2016 05:16:34 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7852

        Title:      Additional Data Related to an 
                    Emergency Call 
        Author:     R. Gellens, B. Rosen,
                    H. Tschofenig, R. Marshall,
                    J. Winterbottom
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2016
        Mailbox:    rg+ietf@randy.pensive.org, 
                    br@brianrosen.net, 
                    Hannes.Tschofenig@gmx.net,
                    rmarshall@telecomsys.com, 
                    a.james.winterbottom@gmail.com
        Pages:      113
        Characters: 239135
        Updates:    RFC 6443, RFC 6881

        I-D Tag:    draft-ietf-ecrit-additional-data-38.txt

        URL:        https://www.rfc-editor.org/info/rfc7852

        DOI:        http://dx.doi.org/10.17487/RFC7852

When an emergency call is sent to a Public Safety Answering Point
(PSAP), the originating device, the access network provider to which
the device is connected, and all service providers in the path of the
call have information about the call, the caller, or the location,
which is helpful for the PSAP to have in handling the emergency.
This document describes data structures and mechanisms to convey such
data to the PSAP.  The intent is that every emergency call carry as
much of the information described here as possible using the
mechanisms described here.

The mechanisms permit the data to be conveyed by reference (as an
external resource) or by value (within the body of a SIP message or a
location object).  This follows the tradition of prior emergency
services standardization work where data can be conveyed by value
within the call signaling (i.e., in the body of the SIP message) or
by reference.

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