RFC 3248: A Delay Bound alternative revision of RFC 2598
In plain English — editorial summary, not part of the RFC
For historical interest, this document captures the EF Design Team's proposed solution, preferred by the original authors of RFC 2598 but not adopted by the working group in December 2000. The original definition of EF was based on comparison of forwarding on an unloaded network. This experimental Delay Bound (DB) PHB requires a bound on the delay of packets due to other traffic in the network. At the Pittsburgh IETF meeting in August 2000, the Differentiated Services working group faced serious questions regarding RFC 2598 - the group's standards track definition of the Expedited Forwarding (EF) Per Hop Behavior (PHB). An 'EF Design Team' volunteered to develop a re-expression of RFC 2598, bearing in mind the issues raised in the DiffServ group. At the San Diego IETF meeting in December 2000 the DiffServ working group decided to pursue an alternative re-expression of the EF PHB. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3248
- Published
- March 2002
- Authors
- G. Armitage; B. Carpenter; A. Casati; J. Crowcroft; J. Halpern; B. Kumar; J. Schnizlein
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2598An Expedited Forwarding PHBObsoleted
June 1999
- RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior)Current
March 2002
- RFC 3140Per Hop Behavior Identification CodesCurrent
June 2001
- RFC 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 2002
- RFC 4542Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol SuiteUpdated
May 2006
- RFC 4860Generic Aggregate Resource ReSerVation Protocol (RSVP) ReservationsCurrent
May 2007
- RFC 2836Per Hop Behavior Identification CodesObsoleted
May 2000
- RFC 2597Assured Forwarding PHB GroupUpdated
June 1999
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?