RFC 1 Defines the Building Block of Internet Communication

April 7, 1969

Steve Crocker, a graduate student at UCLA and part of the team developing ARPANET, writes the first “Request for Comments“. The ARPANET, a research project of the Department of Defense’s Advanced Research Projects Agency (ARPA), was the foundation of today’s modern Internet. RFC 1 defined the design of the host software for communication between ARPANET nodes. This host software would be run on Interface Message Processors or IMPs, which were the precursor to Internet routers. The “host software” defined in RFC 1 would later be known as the Network Control Protocol or NCP, which itself was the forerunner to the modern TCP/IP protocol the Internet runs on today.

There is a very interesting history to how RFCs came about, itself fittingly documented in RFC 1000. Long story short, the initial design of the ARPANET was not well defined. The students and researchers on the ARPANET team were expecting professionals from the government to come in and define their objectives more clearly. As it started to become evident that there was no specific design forthcoming and possibilities were being discussed informally, the working group decided that they should start writing down and organizing their ideas. However, they were also concerned that by formally documenting their concepts that it might seem like they were taking authority and would possibly offend some hypothetical “official protocol designers” from the government. Therefore Steve Crocker chose to carefully title the document “Request for Comments” so that the point was made that these were not official publications and that in fact, they were asking for others working on the project to add their input. As more RFC documents were written describing and defining the earliest building blocks of the ARPANET, these became the unofficial method of documentation and discussion within the ARPANET Networking Working Group (itself loosely defined in RFC 3). This laid the foundation for the eventual Internet Engineering Task Force (IETF) which today establishes many official Internet Standards. Today RFCs are the official publication of the IETF where Internet developments are proposed and official Internet Standards are defined. As of early 2023 there have been nearly 9500 RFCs published.

IBM System 360 Changes the Industry Forever

IBM System 360April 7, 1964

IBM launches the System 360 mainframe architecture, which comprised six compatible models complete with 40 peripherals. The line, dubbed the “360″ because it addressed all types and sizes of customer, cost IBM over five billion dollars to develop, and it is widely considered one of the riskiest business gambles of all time.

Up until this time, computer systems, even from the same manufacturer, were generally incompatible with each other. Software and peripherals from old systems would not work with new systems. This stifled acceptance and deployments of new systems as business customers were hesitant to lose their investments in their current systems. By developing a mutually compatible series of mainframes, customers were assured that their investments would not be lost if they purchased further System 360 models.

IBM’s gamble paid off handsomely as in just the first three months of its release, IBM will receive $1.2 billion in orders. Within five years, over thirty-three thousand units will be sold, popularizing the concept of a computer “upgrade” around the world. The 360 family was the most successful IBM system of all time, generating over $100 billion in revenue through the mid-1980’s. It became the basis for all subsequent IBM mainframe architectures, which would hold a 65% marketshare in the 1990’s.

The 360 architecture also introduced a number of industry standards to the marketplace, such as the worldwide standard of the 8-bit byte. Its enormous popularity catapulted the business world into the technology age and transformed the computer industry. Not bad for a bunch of suits!