Security Threats and Requirements for Emergency Call Marking and Mapping
RFC 5069, “Security Threats and Requirements for Emergency Call Marking and Mapping”, is an Informational document published in January 2008 by T. Taylor, H. Tschofenig, H. Schulzrinne, M. Shanmugam. The canonical text is published by the RFC Editor.
Abstract
This document reviews the security threats associated with the marking of signalling messages to indicate that they are related to an emergency, and with the process of mapping locations to Universal Resource Identifiers (URIs) that point to Public Safety Answering Points (PSAPs). This mapping occurs as part of the process of routing emergency calls through the IP network.
Based on the identified threats, this document establishes a set of security requirements for the mapping protocol and for the handling of emergency-marked calls. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5069 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5077 Transport Layer Security Session Resumption without Server- Side State
- RFC 5060 Protocol Independent Multicast MIB
- RFC 5059 Bootstrap Router Mechanism for Protocol Independent Multicast
- RFC 5088 OSPF Protocol Extensions for Path Computation Element Discovery
- RFC 5089 IS-IS Protocol Extensions for Path Computation Element Discovery
- RFC 5090 RADIUS Extension for Digest Authentication
- RFC 5097 MIB for the UDP-Lite protocol
- RFC 5098 Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters