Framework for Emergency Calling Using Internet Multimedia
RFC 6443
Document | Type |
RFC - Informational
(December 2011; No errata)
Updated by RFC 7852
|
|
---|---|---|---|
Authors | Brian Rosen , James Polk , Andrew Newton , Henning Schulzrinne | ||
Last updated | 2015-10-14 | ||
Replaces | draft-rosen-ecrit-framework | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6443 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Robert Sparks | ||
IESG note |
IETF LC ends Mar 10. Marc Linsner (mlinsner@cisco.com) is the document shepherd. |
||
Send notices to | (None) |
Internet Engineering Task Force (IETF) B. Rosen Request for Comments: 6443 NeuStar Category: Informational H. Schulzrinne ISSN: 2070-1721 Columbia U. J. Polk Cisco Systems A. Newton TranTech/MediaSolv December 2011 Framework for Emergency Calling Using Internet Multimedia Abstract The IETF has standardized various aspects of placing emergency calls. This document describes how all of those component parts are used to support emergency calls from citizens and visitors to authorities. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6443. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Rosen, et al. Informational [Page 1] RFC 6443 Emergency Call Framework December 2011 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 2. Terminology .....................................................6 3. Overview of How Emergency Calls Are Placed ......................8 4. Which Devices and Services Should Support Emergency Calls? .....12 5. Identifying an Emergency Call ..................................12 6. Location and Its Role in an Emergency Call .....................14 6.1. Types of Location Information .............................16 6.2. Location Determination ....................................17 6.2.1. User-Entered Location Information ..................17 6.2.2. Access Network "Wire Database" Location Information ........................................18 6.2.3. End System Measured Location Information ...........19 6.2.4. Network Measured Location Information ..............19 6.3. Who Adds Location, Endpoint, or Proxy? ....................20 6.4. Location and References to Location .......................20 6.5. End System Location Configuration .........................21 6.6. When Location Should Be Configured ........................22 6.7. Conveying Location ........................................23 6.8. Location Updates ..........................................24 6.9. Multiple Locations ........................................24 6.10. Location Validation ......................................25 6.11. Default Location .........................................26 6.12. Location Format Conversion ...............................26 7. LIS and LoST Discovery .........................................26 8. Routing the Call to the PSAP ...................................27 9. Signaling of Emergency Calls ...................................29 9.1. Use of TLS ................................................29 9.2. SIP Signaling Requirements for User Agents ................30 9.3. SIP Signaling Requirements for Proxy Servers ..............30 10. Call Backs ....................................................30 11. Mid-Call Behavior .............................................31 12. Call Termination ..............................................31 13. Disabling of Features .........................................32 14. Media .........................................................32 15. Testing .......................................................32Show full document text