TCP with ECN: The Treatment of Retransmitted Data Packets
draft-ietf-tsvwg-tcp-ecn-00
| Document | Type |
Expired Internet-Draft
(tsvwg WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sally Floyd, Dr. K. K. Ramakrishnan | ||
| Last updated | 2023-03-01 (Latest revision 2000-11-06) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 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
Dr. K. K. Ramakrishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)