RFC 5069: Security Threats and Requirements for Emergency Call Marking and Mapping

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…

Read RFC 5069 on the RFC Editor

Outgoing relationships (3 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 3693: Geopriv Requirements
Informative reference — RFC 5012: Requirements for Emergency Context Resolution with Internet Technologies

Incoming relationships (8 related RFCs)

Normatively referenced by — RFC 6444: Location Hiding: Problem Statement and Requirements
Informatively referenced by — RFC 5012: Requirements for Emergency Context Resolution with Internet Technologies
Informatively referenced by — RFC 5031: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
Informatively referenced by — RFC 5582: Location-to-URL Mapping Architecture and Framework
Informatively referenced by — RFC 5223: Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
Informatively referenced by — RFC 6601: Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
Informatively referenced by — RFC 8147: Next-Generation Pan-European eCall
Informatively referenced by — RFC 8148: Next-Generation Vehicle-Initiated Emergency Calls