RFC 4375: Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain
In plain English — editorial summary, not part of the RFC
This document presents a list of requirements in support of Emergency Telecommunications Service (ETS) within a single administrative domain. This document focuses on a specific set of administrative constraints and scope. Solutions to these requirements are not presented in this document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4375
- Published
- January 2006
- Authors
- K. Carlberg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5364Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource ListsUpdated
October 2008
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 3006Integrated Services in the Presence of Compressible FlowsCurrent
November 2000
- RFC 2975Introduction to Accounting ManagementCurrent
October 2000
- RFC 2815Integrated Service Mappings on IEEE 802 NetworksCurrent
May 2000
- RFC 2752Identity Representation for RSVPObsoleted
January 2000
- RFC 2751Signaled Preemption Priority Policy ElementObsoleted
January 2000
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?