RFC 4190: Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony
In plain English — editorial summary, not part of the RFC
This document presents a framework for supporting authorized, emergency-related communication within the context of IP telephony. We present a series of objectives that reflect a general view of how authorized emergency service, in line with the Emergency Telecommunications Service (ETS), should be realized within today's IP architecture and service models. From these objectives, we present a corresponding set of protocols and capabilities, which provide a more specific set of recommendations regarding existing IETF protocols. Finally, we present two scenarios that act as guiding models for the objectives and functions listed in this document. These models, coupled with an example of an existing service in the Public Switched Telephone Network (PSTN), contribute to a constrained solution space. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4190
- Published
- November 2005
- Authors
- K. Carlberg; I. Brown; C. Beard
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current
October 2005
- RFC 4184RTP Payload Format for AC-3 AudioCurrent
October 2005
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
- RFC 4170Tunneling Multiplexed Compressed RTP (TCRTP)Current
November 2005
- RFC 4168The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)Updated
October 2005
- RFC 4166Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability StatementCurrent
February 2006
- RFC 4165Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)Current
September 2005
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
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?