Skip to main content

Usefullness of three drop precedences in Assured Forwarding service
draft-elloumi-diffserv-threevstwo-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Stefaan De Cnodder
Last updated 1999-07-13
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 informational memo points out advantages of using three drop precedences (compared to two) in the Assured Forwarding (AF) Per- Hop-Behavior (PHB) when the traffic is composed of responsive TCP and non responsive UDP traffic. Our simulation results show that while two drop precedences can, in some cases, guarantee to an aggregate consisting of TCP traffic the full utilization of the reserved bandwidth, they cannot allow to access the unreserved bandwidth in the presence of high bit rate unresponsive UDP traffic. When three drop precedences are appropriately used TCP aggregates can fully use the minimum reserved bandwidth and share the unreserved one.

Authors

Stefaan De Cnodder

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)