RFC 4542: Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite
In plain English — editorial summary, not part of the RFC
RFCs 3689 and 3690 detail requirements for an Emergency Telecommunications Service (ETS), of which an Internet Emergency Preparedness Service (IEPS) would be a part. Some of these types of services require call preemption; others require call queuing or other mechanisms. IEPS requires a Call Admission Control (CAC) procedure and a Per Hop Behavior (PHB) for the data that meet the needs of this architecture. Such a CAC procedure and PHB is appropriate to any service that might use H.323 or SIP to set up real-time sessions. The key requirement is to guarantee an elevated probability of call completion to an authorized user in time of crisis. This document primarily discusses supporting ETS in the context of the US Government and NATO, because it focuses on the Multi-Level Precedence and Preemption (MLPP) and Government Emergency Telecommunication Service (GETS) standards. The architectures described here are applicable beyond these organizations. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4542
- Published
- May 2006
- Authors
- F. Baker; J. Polk
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 42
- Also known as
- —
- Updated by:
- RFC 5865
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4860Generic Aggregate Resource ReSerVation Protocol (RSVP) ReservationsCurrent
May 2007
- RFC 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 2002
- RFC 3248A Delay Bound alternative revision of RFC 2598Current
March 2002
- RFC 3140Per Hop Behavior Identification CodesCurrent
June 2001
- RFC 4594Configuration Guidelines for DiffServ Service ClassesUpdated
August 2006
- RFC 8100Diffserv-Interconnection Classes and PracticeCurrent
March 2017
- RFC 4126Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance ComparisonsCurrent
June 2005
- RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior)Current
March 2002
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?