Skip to main content

Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior)

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3247.
Authors Kent Benson, Dr. K. K. Ramakrishnan , Jon Bennett , Shahram Davari , Charles Kalmanek , Angela Chiu , William Courtney, Victor Firoiu , Jean-Yves Le Boudec , Anna Charny
Last updated 2020-01-21 (Latest revision 2001-06-11)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Additional resources
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3247 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3247

        Title:      Supplemental Information for the New Definition of
                    the EF PHB (Expedited Forwarding Per-Hop Behavior)
        Author(s):  A. Charny, J. Bennet, K. Benson, J. Boudec, 
                    A. Chiu, W. Courtney, S. Davari, V. Firoiu, 
                    C. Kalmanek, K. Ramakrishnan 
        Status:     Informational
        Date:       March 2002
        Pages:      25
        Characters: 53786
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-diffserv-ef-supplemental-01.txt


This document was written during the process of clarification of
RFC 2598 "An Expedited Forwarding PHB" that led to the publication of
revised specification of EF "An Expedited Forwarding PHB".  Its
primary motivation is providing additional explanation to the revised
EF definition and its properties.  The document also provides
additional implementation examples and gives some guidance for
computation of the numerical parameters of the new definition for
several well known schedulers and router architectures.

This document is a product of the Differentiated Services Working
Group of the IETF.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.