congestion control in ip/tcp internetworks congestion control is a recognized problem in complex networks. we have discovered that the department of defense's internet protocol (ip), a pure datagram protocol, and transmission control protocol (tcp), a transport layer protocol, when used together, are subject to unusual congestion problems caused by interactions between the transport and datagram layers. in particular, ip gateways are vulnerable to a phenomenon we call congestion collapse, especially when such gateways connect networks of widely different bandwidth. we have developed solutions that prevent congestion collapse.these problems are not generally recognized because these protocols are used most often on networks built on top of arpanet imp technology. arpanet imp based networks traditionally have uniform bandwidth, identical switching nodes, and are sized with substantial excess capacity. this excess capacity, and the ability of the imp system to throttle the transmissions of hosts has for most ip/tcp hosts and networks, been adequate to handle congestion. with the recent split of the arpanet into two interconnected networks and the growth of other networks with differing properties connected to the arpanet, however, reliance on the benign properties of the imp system is no longer enough to allow hosts to communicate rapidly and reliably. improved handling of congestion is now mandatory for successful network operation under load.ford aerospace and communications corporation, and its parent company, ford motor company, operate the only private ip/tcp long-haul network in existence today. this network connects six facilities (one in michigan, two in california, one in colorado, one in texas, and one in england) some with extensive local networks. this net is cross-tied to the arpanet but uses its own long-haul circuits; traffic between ford facilities flows over private leased circuits, including a leased transatlantic satellite connection. all switching nodes are pure ip datagram switches with no node-to-node flow control, and all hosts run software either written or heavily modified by ford or ford aerospace. bandwidth of links in this network varies widely, from 1200 to 10,000,000 bits per second. in general, we have not been able to afford the luxury of excess long-haul bandwidth that the arpanet possesses, and our long-haul links are heavily loaded during peak periods. transit times of several seconds are thus common in our network.because of our pure datagram orientation, heavy loading, and wide variation in bandwidth, we have had to solve problems that the arpanet/milnet community is just beginning to recognize. our network is sensitive to suboptimal behavior by host tcp implementations, both on and off our own net. we have devoted considerable effort to examining tcp behavior under various conditions, and have solved some widely prevalent problems with tcp. we present here two problems and their solutions. many tcp implementations have these problems; if throughput is worse through an arpanet/milnet gateway for a given tcp implementation than throughput across a single net, there is a high probability that the tcp implementation has one or both of these problems. john nagle