Security Threats and Requirements for Emergency Call Marking and Mapping
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 12
- 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.
- Publication Date
- 2008-01-01
- Status Note
- Informational
- DOI
10.17487/RFC5069- Link
- https://doi.org/10.17487/RFC5069
- Author(s)
- Tom TaylorHannes TschofenigHenning SchulzrinneMurugaraj Shanmugam
- Keyword(s)
- ECRIT, PSAP
Latest version of IETF RFC 5069
Document Versions — IETF RFC 5069
-
▶ IETF RFC 5069 (2008-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
Bibliographic Reference(s)
- IETF RFC 3693 [Active*]
- IETF RFC 5012 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5069.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5069, Security Threats and Requirements for Emergency Call Marking and Mapping. Available at https://doi.org/10.17487/RFC5069
Snippet:
IETF RFC 5069, Security Threats and Requirements for Emergency Call Marking and Mapping. Available at https://doi.org/10.17487/RFC5069
HTML (ISO 690 compliant)
Preview:
IETF RFC 5069, Security Threats and Requirements for Emergency Call Marking and Mapping. Available at https://doi.org/10.17487/RFC5069
Snippet:
<span class="citation"><cite>IETF RFC 5069</cite>, Security Threats and Requirements for Emergency Call Marking and Mapping. Available at <a href="https://doi.org/10.17487/RFC5069" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5069</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5069, Security Threats and Requirements for Emergency Call Marking and Mapping
doi: 10.17487/RFC5069
url: https://doi.org/10.17487/RFC5069
doi: 10.17487/RFC5069
url: https://doi.org/10.17487/RFC5069
Snippet:
<li> <cite id="bib-rfc5069">IETF RFC 5069</cite>, Security Threats and Requirements for Emergency Call Marking and Mapping <span class="doi">10.17487/RFC5069</span> </li>
Referenced By
- IETF RFC 5012 [Active*]
- IETF RFC 5031 [Active*]
- IETF RFC 5222 [Active*]
- IETF RFC 5223 [Active*]
- IETF RFC 6443 [Active*]
- IETF RFC 6444 [Active*]
- IETF RFC 6881 [Active*]
- IETF RFC 7406 [Active*]