TL;DR: In this article, the authors present solutions that prevent congestion collapse in the ARPANET IMP-based networks, and examine TCP behavior under various conditions, and have solved some widely prevalent problems with TCP.
Abstract: 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.
TL;DR: The article describes a series of congestion related performance difficulties in a TCP/IP network at Ford Aerospace, and suggested some "cures", but fails to address the root causes of the performance difficulties that Mr Nagle discusses.
Abstract: The article "Congestion control in IP/TCP Internetworks" by John Nagle is an excellent illustration of problems inherent in Arpanet and Milnet technology. The article describes a series of congestion related performance difficulties in a TCP/IP network at Ford Aerospace, and suggested some "cures".What in fact the article describes is what appear to be adequate "band-aids" for the basic inadequacies of Arpanet technology. However, it fails to address the root causes of the performance difficulties that Mr. Nagle discusses. It is suggested that all of these problems result from an uncritical adherence to the Arpanet paradigm, without regard to the research and standardization work of the past 15 years.
TL;DR: This is a detailed compilation of host-level information which provides the details required to locate resources, send mail to colleagues and friends worldwide, and answer questions about how to access major national and international networks.
Abstract: This is a detailed compilation of host-level information which provides the details required to locate resources, send mail to colleagues and friends worldwide, and answer questions about how to access major national and international networks. Extensive cross-referenced information on ARPANET/MILNET, BITNET, CSNET, ESnet, NSFNET, SPAN, THEnet, USENET and many others is included. There are also detailed lists of hosts, site contracts, administrative domains and organizations. The book also includes a tutorial chapter with reference tables which reveal electronic mail "secrets" that make it easier to take advantage of networking.
TL;DR: The ARPANET, initiated in 1969 by the Advanced Research Projects Agency (DARPA) of the Department of Defense, was the first wide area packet switching network; it has grown to be very large; it now consists of over 330 networks, hundreds of gateways, and tens of thousands of hosts.
Abstract: The ARPANET, initiated in 1969 by the Advanced Research Projects Agency (DARPA) of the Department of Defense (DoD), was the first wide area packet switching network. In 1984, the ARPANET, which had grown to over 100 nodes, was separated into two parts: an operational component, the MILNET, to serve the operational needs of the DoD, and a research component that retained the ARPANET name. After the network split, the MILNET expanded, and it should reach over 250 nodes within a year. The DARPA Internet was formed in the 1970s in response to a requirement to interconnect different types of packet‐switching networks that were being implemented. It has grown to be very large; it now consists of over 330 networks, hundreds of gateways, and tens of thousands of hosts. Where the ARPANET used to connect hosts that were single computers into a network, many of these hosts now serve as gateways to local campus networks, regional networks, and other national networks, such as the NSFNET. The impact of this growing system of inter‐connected networks on research, communications, and library access will be profound.
TL;DR: This Note lays a foundation by tracing the history of the Internet and, with it, the creation of innumerable computer security threats, from the simple virus to complex, system-specific worms.
Abstract: "If you spend more on coffee than on IT security, then you will be hacked What's more, you deserve to be hacked"1 I Introduction On January 28, 2011, Egypt vanished-not literally, but digitally Following massive demonstrations against Egyptian President Hosni Mubarak's regime,2 the Egyptian government shut off Internet access across the country, a move "unprecedented in Internet history"3 With access to social-networking sites cut off, even more citizens stormed the streets of Cairo, adding Internet connectivity to their list of political demands and transforming Tahrir Square into a "street Twitter"4 Though the logistics of Egypt's "Internet kill switch" remain foggy,5 the event has set the stage for a serious debate about cybersecurity issues within the United States, including whether or not the United States government should be given access to a kill switch of its own6 A series of high-profile Internet attacks in the last two years underscores the severity of the problem7 The dizzying array of approaches to the issue illustrates the need for clarity and uniformity8 This Note proceeds in five parts Part II lays a foundation by tracing the history of the Internet and, with it, the creation of innumerable computer security threats, from the simple virus to complex, system-specific worms In Part III, a handful of stories demonstrate the vulnerability of Internetconnected networks and much of America's critical infrastructure Part IV reviews the various proposals, both on and off the books, to cope with the cybersecurity problem Drawing upon those and other ideas, Part V offers an initial framework for protecting the Internet Part VI briefly concludes II Historical Background A The Rise of the Internet The history of the Internet begins with a satellite President Dwight Eisenhower, in response to the launch of the Russian satellite Sputnik in 1958, created the Advanced Research Projects Agency (ARPA)9 to develop technologies for use by America's military10 Initial projects focused on traditional military systems like missile defense, but by 1962, ARPA's Information Processing Techniques Office had begun to drive the field of computer science forward11 ARPA's goal was to bring together researchers from across the country via a computer network humbly named ARPANET12 The potential military uses of such a network were quickly realized by ARPA's tech gurus13 The single-network ARPANET was transformed into the multi-network Internet over the next ten years14 As ARPANET's user base grew (limited primarily to Department of Defense officials and contractors), its users began to realize the usefulness of features like electronic mail15 Simultaneously, the American military was busily introducing computer technology in myriad ways, which required ARPA to expand the network in a way that incorporated those different systems16 Ultimately, the diverging needs of ARPA's research users and its military users forced the Department of Defense to bifurcate the network: ARPANET would provide an experimental platform for defense researchers, while MILNET would provide a stable, restricted-access network for military communications17 Coincidentally, separating the operational military components also made it easier for ARPANET to be commercialized and emerge as the Internet of today18 Commercialization and privatization of the Internet resulted in rapid expansion In 1998, the Department of Commerce was still defining "the Internet" in its economic reports19 Commerce attributed the Internet's tremendous growth to "its strength as a medium of communication, education and entertainment, and as a tool for electronic commerce"20 By 2010, the need to define the ubiquitous network was wholly unnecessary: roughly two billion people were Internet users, double the number of users connected just five years earlier21 The Internet continues to spread hand-in-hand with new tools for connecting and reconnecting with others …