TCP with ECN: The Treatment of Retransmitted Data Packets
draft-ietf-tsvwg-tcp-ecn-00
| Document | Type | Expired Internet-Draft (tsvwg WG) | |
|---|---|---|---|
| Authors | Sally Floyd , K. Ramakrishnan | ||
| Last updated | 2000-11-06 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-tsvwg-tcp-ecn-00.txt
Abstract
This document makes recommendations for the use of ECN with retransmitted data packets, for an ECN-capable TCP connection. This document supplements RFC 2481 [RFC2481], which did not address the issue of retransmitted data packets. This document recommends that for ECN-capable TCP implementations, the ECT bit (ECN-Capable Transport) in the IP header SHOULD NOT be set on retransmitted data packets, and that the TCP data receiver SHOULD ignore the ECN field on arriving data packets that are outside of the receiver's current window. This is for greater security against denial-of-service attacks.
Authors
Sally Floyd
(floyd@icir.org)
K. Ramakrishnan
(kkrama@research.att.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)