Re-ECN: A Framework for adding Congestion Accountability to TCP/IP
draft-briscoe-tsvwg-re-ecn-tcp-motivation-02

Document Type Expired Internet-Draft (individual)
Authors Bob Briscoe  , Arnaud Jacquet  , Toby Moncaster  , Alan Smith 
Last updated 2010-10-25
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-briscoe-tsvwg-re-ecn-tcp-motivation-02.txt

Abstract

This document describes the framework to support a new protocol for explicit congestion notification (ECN), termed re-ECN, which can be deployed incrementally around unmodified routers. Re-ECN allows accurate congestion monitoring throughout the network thus enabling the upstream party at any trust boundary in the internetwork to be held responsible for the congestion they cause, or allow to be caused. So, networks can introduce straightforward accountability for congestion and policing mechanisms for incoming traffic from end- customers or from neighbouring network domains. As well as giving the motivation for re-ECN this document also gives examples of mechanisms that can use the protocol to ensure data sources respond correctly to congestion. And it describes example mechanisms that ensure the dominant selfish strategy of both network domains and end- points will be to use the protocol honestly.

Authors

Bob Briscoe (bob.briscoe@bt.com)
Arnaud Jacquet (arnaud.jacquet@bt.com)
Toby Moncaster (toby@moncaster.com)
Alan Smith (alan.p.smith@bt.com)

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