Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets
draft-kuzmanovic-ecn-syn-00

Document Type Replaced Internet-Draft (individual)
Last updated 2005-11-30 (latest revision 2005-10-04)
Replaced by draft-ietf-tsvwg-ecnsyn
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-ecnsyn
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-kuzmanovic-ecn-syn-00.txt

Abstract

This draft specifies a modification to RFC 3168 to allow TCP SYN/ACK packets to be ECN-Capable. For TCP, RFC 3168 only specified setting an ECN-Capable codepoint on data packets, and not on SYN and SYN/ACK packets. However, because of the high cost to the TCP transfer of having a SYN/ACK packet dropped, with the resulting retransmit timeout, this document is specifying the use of ECN for the SYN/ACK packet itself, when sent in response to a SYN packet with the two ECN flags set in the TCP header, indicating a willingness to use ECN. Setting TCP SYN/ACK packets as ECN-Capable can be of great benefit to the TCP connection, avoiding the severe penalty of a retransmit timeout for a connection that has not yet started placing a load on the network. The sender of the SYN/ACK packet must respond to an ECN mark by reducing its initial congestion window from two, three, or four segments to one segment, reducing the subsequent load from that connection on the network.

Authors

Aleksandar Kuzmanovic (akuzma@northwestern.edu)

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