RFC 5012: Requirements for Emergency Context Resolution with Internet Technologies
In plain English — editorial summary, not part of the RFC
This document defines terminology and enumerates requirements for the context resolution of emergency calls placed by the public using voice-over-IP (VoIP) and general Internet multimedia systems, where Internet protocols are used end to end. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5012
- Published
- January 2008
- Authors
- H. Schulzrinne; R. Marshall
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5582Location-to-URL Mapping Architecture and FrameworkCurrent
September 2009
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 5031A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesUpdated
January 2008
- RFC 5069Security Threats and Requirements for Emergency Call Marking and MappingCurrent
January 2008
- RFC 5016Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices ProtocolCurrent
October 2007
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 4871DomainKeys Identified Mail (DKIM) SignaturesObsoleted
May 2007
- RFC 4823FTP Transport for Secure Peer-to-Peer Business Data Interchange over the InternetUpdated
April 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?