Congestion Exposure Mechanism Description
draft-conex-mechanism-00

Document Type Expired Internet-Draft (individual)
Authors Bob Briscoe  , Richard Woundy  , Toby Moncaster  , John Leslie 
Last updated 2010-06-21
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-conex-mechanism-00.txt

Abstract

Internet Service Providers (ISPs) are facing problems where congestion prevents full utilization of the path between sender and receiver at today's "broadband" speeds. ISPs desire to control the congestion, which often appears to be caused by a small number of users consuming a large amount of bandwidth. Building out more capacity along all of the path to handle this congestion can be expensive; and network operators have sought other ways to manage congestion. The current mechanisms all suffer from difficulty measuring the congestion (as distinguished from the total traffic). The ConEx Working Group is designing a mechanism to make congestion along any path visible at the Internet Layer. This document discusses this mechanism.

Authors

Bob Briscoe (bob.briscoe@bt.com)
Richard Woundy (Richard_Woundy@cable.comcast.com)
Toby Moncaster (toby@moncaster.com)
John Leslie (john@jlc.net)

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