A Delay Bound alternative revision of RFC 2598
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 11
- Abstract
- 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.
- Publication Date
- 2002-03-01
- Status Note
- Informational
- DOI
10.17487/RFC3248- Link
- https://doi.org/10.17487/RFC3248
- Author(s)
- Grenville ArmitageBrian E. CarpenterAlessio CasatiJon CrowcroftJoel M. HalpernBrijesh KumarDr. John M. Schnizlein
- Keyword(s)
- PHB, Expedited Forwarding
Latest version of IETF RFC 3248
Document Versions — IETF RFC 3248
-
▶ IETF RFC 3248 (2002-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2474 [Active*]
- IETF RFC 2475 [Active*]
- IETF RFC 2598 [Superseded*]
- IETF RFC 3246 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3248.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3248, A Delay Bound alternative revision of RFC 2598. Available at https://doi.org/10.17487/RFC3248
Snippet:
IETF RFC 3248, A Delay Bound alternative revision of RFC 2598. Available at https://doi.org/10.17487/RFC3248
HTML (ISO 690 compliant)
Preview:
IETF RFC 3248, A Delay Bound alternative revision of RFC 2598. Available at https://doi.org/10.17487/RFC3248
Snippet:
<span class="citation"><cite>IETF RFC 3248</cite>, A Delay Bound alternative revision of RFC 2598. Available at <a href="https://doi.org/10.17487/RFC3248" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3248</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3248, A Delay Bound alternative revision of RFC 2598
doi: 10.17487/RFC3248
url: https://doi.org/10.17487/RFC3248
doi: 10.17487/RFC3248
url: https://doi.org/10.17487/RFC3248
Snippet:
<li> <cite id="bib-rfc3248">IETF RFC 3248</cite>, A Delay Bound alternative revision of RFC 2598 <span class="doi">10.17487/RFC3248</span> </li>
Referenced By
- IETF RFC 3819 [Active*]