cted for the ARPANET was called the Net- work Control Protocol (NCP). It was designed to handle the emergent requirements of the low-volume architecture of the ARPANET network. As traffic grew, however, it proved to be inadequate to handle the load, and in 1974 a more robust protocol suite was implemented, based on the TCP - an ironclad protocol designed for end-to-end network communi- cations control. In 1978, a new design split the responsibilities for end-to- end VS. node-to-node transmission between two protocols: the newly crafted IP, designed to route packets from device to device and TCP, designed to offer reliable, end-to-end communications. Since TCP and IP were originally envisioned as a single protocol, they are now known as the TCP/IP protocol suite, a name that also incorporates a collection of protocols and applications that also handle routing, QoS, error control, and other functions. One problem that occurred that the ARPANET planners didn't envi- sion when they sited their nodes at college campuses was visibility. Nat- urally, they placed the switches in the raised floor facilities of the computer science department, and we know what is also found there: Undergraduus Nerdus, the dreaded computer science (or worse yet, engi- neering) student. In a matter of weeks the secret was out- - ARPA's top secret network was top secret no longer. So, in 1983, the ARPANET was Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website. Transport Technologies Transport Technologies split into two networks. One half, still called ARPANET, continued to be used to interconnect research and academic sites; the other, called MIL- NET, was specifically used to carry military traffic and ultimately became part of the Defense Data Network. That year was also a good year for TCP/IP. It was included as part of the communications kernel for the University of Cal