Re-ECN: Adding Accountability for Causing Congestion to TCP/IP
draft-briscoe-tsvwg-re-ecn-tcp-09
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2010-10-25 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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) | ||
https://www.ietf.org/archive/id/draft-briscoe-tsvwg-re-ecn-tcp-09.txt
Abstract
This document introduces a new protocol for explicit congestion notification (ECN), termed re-ECN, which can be deployed incrementally around unmodified routers. The protocol works by arranging an extended ECN field in each packet so that, as it crosses any interface in an internetwork, it will carry a truthful prediction of congestion on the remainder of its path. The purpose of this document is to specify the re-ECN protocol at the IP layer and to give guidelines on any consequent changes required to transport protocols. It includes the changes required to TCP both as an example and as a specification. It briefly gives examples of mechanisms that can use the protocol to ensure data sources respond correctly to congestion, but these are described more fully in a companion document.
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.)