Browse Prior Art Database

Known TCP Implementation Problems (RFC2525)

IP.com Disclosure Number: IPCOM000003110D
Original Publication Date: 1999-Mar-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Paxson: AUTHOR [+9]

Abstract

This memo catalogs a number of known TCP implementation problems. The goal in doing so is to improve conditions in the existing Internet by enhancing the quality of current TCP/IP implementations. It is hoped that both performance and correctness issues can be resolved by making implementors aware of the problems and their solutions. In the long term, it is hoped that this will provide a reduction in unnecessary traffic on the network, the rate of connection failures due to protocol errors, and load on network servers due to time spent processing both unsuccessful connections and retransmitted data. This will help to ensure the stability of the global Internet.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group V. Paxson

Request for Comments: 2525 Editor

Category: Informational ACIRI / ICSI

M. Allman

NASA Glenn Research Center/Sterling Software

S. Dawson

Real-Time Computing Laboratory

W. Fenner

Xerox PARC

J. Griner

NASA Glenn Research Center

I. Heavens

Spider Software Ltd.

K. Lahey

NASA Ames Research Center/MRJ

J. Semke

Pittsburgh Supercomputing Center

B. Volz

Process Software Corporation

March 1999

Known TCP Implementation Problems

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Table of Contents

1. INTRODUCTION....................................................2

2. KNOWN IMPLEMENTATION PROBLEMS...................................3

2.1 No initial slow start........................................3

2.2 No slow start after retransmission timeout...................6

2.3 Uninitialized CWND...........................................9

2.4 Inconsistent retransmission.................................11

2.5 Failure to retain above-sequence data.......................13

2.6 Extra additive constant in congestion avoidance.............17

2.7 Initial RTO too low.........................................23

2.8 Failure of window deflation after loss recovery.............26

2.9 Excessively short keepalive connection timeout..............28

2.10 Failure to back off retransmission timeout..................31

2.11 Insufficient interval between keepalives....................34

2.12 Window probe deadlock.......................................36

2.13 Stretch ACK violation.......................................40

2.14 Retransmission sends multiple packets.......................43

2.15 Failure to send FIN notification promptly...................45

...