EF PHB Redefined
draft-charny-ef-definition-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Anna Charny | ||
| Last updated | 2000-11-29 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document proposes text aiming at providing clarification to RFC 2598. The primary motivation for this draft is that the definition of EF PHB given in RFC 2598 does not match the intuition of the EF PHB, and has been determined to be unimplementable in a manner compliant with the definition. In particular, no work-conserving scheduler, including all of the schedulers listed in the Implementation Examples section of RFC 2598, can comply with the definition given in that RFC. This draft gives a rigorous definition of EF PHB which in our opinion preserves the spirit of the EF PHB as intended by RFC 2598 while allowing a number of reasonable compliant implementations. The document also provides implementation guidance and lists several possible implementation examples which conform to the definition given in this draft.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)