ArticleslgStudy

computer science

Protocol Wars

Protocol Wars is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Protocol Wars rather than just read about it. In short: The Protocol Wars were a long-running debate in computer science that occurred from the 1970s to the 1990s, when engineers, organizations and nations became polarized over the issue of which communication protocol would result in the best and most robust networks. This culminated in the Internet–OSI Standards War in the 1980s and early 1990s, which was ultimately "won" by the Internet protocol suite (TCP/IP) by the…

Protocol Wars — main illustration
Protocol Wars — illustration

Key takeaways

  • Protocol Wars belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Protocol Wars to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Protocol Wars from memory before moving on to harder problems.

Reference excerpt

The Protocol Wars were a long-running debate in computer science that occurred from the 1970s to the 1990s, when engineers, organizations and nations became polarized over the issue of which communication protocol would result in the best and most robust networks. This culminated in the Internet–OSI Standards War in the 1980s and early 1990s, which was ultimately "won" by the Internet protocol suite (TCP/IP) by the mid-1990s when it became the dominant protocol suite through rapid adoption of the Internet. In the late 1960s and early 1970s, the pioneers of packet switching technology built computer networks providing data communication, that is the ability to transfer data between points or nodes. As more of these networks emerged in the mid to late 1970s, the debate about communication protocols became a "battle for access standards". An international collaboration between several national postal, telegraph and telephone (PTT) providers and commercial operators led to the X.25 standard in 1976, which was adopted on public data networks providing global coverage. Separately, proprietary data communication protocols emerged, most notably IBM's Systems Network Architecture in 1974 and Digital Equipment Corporation's DECnet in 1975. The United States Department of Defense (DoD) developed TCP/IP during the 1970s in collaboration with universities and researchers in the US, UK, and France. Internet Protocol version 4 (IPv4) was released in 1981 and was made the standard for all DoD computer networking. By 1984, the international reference model OSI model, which was not compatible with TCP/IP, had been agreed upon. Many European governments (particularly France, West Germany, and the UK) and the United States Department of Commerce mandated compliance with the OSI model, while the US Department of Defense planned to transition from TCP/IP to OSI. Meanwhile, the development of a complete Internet protocol suite by 1989, and partnerships with the telecommunication and computer industry to incorporate TCP/IP software into various operating systems, laid the foundation for the widespread adoption of TCP/IP as a comprehensive protocol suite. While OSI developed its networking standards in the late 1980s, TCP/IP came into widespread use on multi-vendor networks for internetworking and as the core component of the emerging Internet.

Early computer networking

Packet switching vs circuit switching

Computer science was an emerging discipline in the late 1950s that began to consider time-sharing between computer users and, later, the possibility of achieving this over wide area networks. In the early 1960s, J. C. R. Licklider proposed the idea of a universal computer network while working at Bolt Beranek & Newman (BBN) and, later, leading the Information Processing Techniques Office (IPTO) at the Advanced Research Projects Agency (ARPA, later, DARPA) of the US Department of Defense (DoD). Independently, Paul Baran at RAND in the US and Donald Davies at the National Physical Laboratory (NPL) in the UK invented new approaches to the design of computer networks. Baran published a series of papers between 1960 and 1964 about dividing information into "message blocks" and dynamically routing them over distributed networks. Davies conceived of and named the concept of packet switching using high-speed interface computers for data communication in 1965–1966. He proposed a national commercial data network in the UK, and designed the local-area NPL network to demonstrate and research his ideas. The first use of the term protocol in a modern data-communication context occurs in an April 1967 memorandum A Protocol for Use in the NPL Data Communications Network written by two members of Davies' team, Roger Scantlebury and Keith Bartlett. Licklider, Baran, and Davies all found it hard to convince incumbent telephone companies of the merits of their ideas. AT&T held a monopoly on communication infrastructure in the United States, as did the General Post Office (GPO) in the United Kingdom, which was the national postal, telegraph and telephone service (PTT). They both believed speech traffic would continue to dominate and continued to invest in traditional telegraphic techniques. Telephone companies were operating on the basis of circuit switching, alternatives to which are message switching or packet switching. Bob Taylor became the director of the IPTO in 1966 and set out to achieve Licklider's vision to enable resource sharing between remote computers. Taylor hired Larry Roberts to manage the programme. Roberts brought Leonard Kleinrock into the project; Kleinrock had applied mathematical methods to study communication networks in his doctoral thesis. At the October 1967 Symposium on Operating Systems Principles, Roberts presented the early "ARPA Net" proposal, based on Wesley Clark's idea for a message switching network using Interface Message Processors (IMPs). Roger Scantlebury presented Davies' work on a digital communication network and referenced the work of Paul Baran. At this seminal meeting, the NPL paper articulated how the data communication for such a resource-sharing network could be implemented. Larry Roberts incorporated Davies' and Baran's ideas on packet switching into the proposal for the ARPANET. The network was built by BBN. Designed principally by Bob Kahn, it departed from the NPL's connectionless network model in an attempt to avoid the problem of network congestion. The service offered to hosts by the network was connection oriented. It enforced flow control and error control (although this was not end-to-end). With the constraint that, for each connection, only one message may be in transit in the network, the sequential order of messages is preserved end-to-end. This made the ARPANET what would come to be called a virtual circuit network.

Datagrams vs virtual circuits

… excerpt ends here. Continue reading the full article.

Illustrations

Protocol Wars: Key contributors to  X.25, just after its approval in March 1976, including engineers from three PTTs (France, Japan, UK) and two private companies (Canada, US)[nb 4]
Key contributors to X.25, just after its approval in March 1976, including engineers from three PTTs (France, Japan, UK) and two private companies (Canada, US)[nb 4]
Protocol Wars: The first demonstration of the Internet, linking DARPA's three networks (the ARPANET, SATNET, and PRNET), which took place in July 1977[102]
The first demonstration of the Internet, linking DARPA's three networks (the ARPANET, SATNET, and PRNET), which took place in July 1977[102]
Protocol Wars: A cartoon sketched in 1988 by François Flückiger illustrated that "some people foresaw a division between world technologies: Internet in the United States, OSI in Europe. In this model, the two sides would have communicated via gateways."[134]
A cartoon sketched in 1988 by François Flückiger illustrated that "some people foresaw a division between world technologies: Internet in the United States, OSI in Europe. In this model, the two sides would have communicated via gateways."[134]
Protocol Wars: Vint Cerf emphasized the goal of running "IP on everything", notably with a T-shirt he wore while presenting to the 1992 IETF meeting.[162]
Vint Cerf emphasized the goal of running "IP on everything", notably with a T-shirt he wore while presenting to the 1992 IETF meeting.[162]

Worked examples

Example 1 — a first encounter with Protocol Wars

Start with the simplest possible case. Write down what Protocol Wars claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Protocol Wars before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Protocol Wars ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Protocol Wars

In research
Protocol Wars appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Protocol Wars in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Protocol Wars is common in secondary-school and first-year university syllabi. It links to neighbouring topics Communications protocols, History of the Internet, Internet protocols, so understanding it makes those chapters shorter.
In everyday life
Look for Protocol Wars outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Protocol Wars in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Protocol Wars means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Protocol Wars out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Protocol Wars in simple terms?

The Protocol Wars were a long-running debate in computer science that occurred from the 1970s to the 1990s, when engineers, organizations and nations became polarized over the issue of which communication protocol would result in the best and most robust networks. This culminated in the Internet–OS…

Why does Protocol Wars matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Protocol Wars?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Protocol Wars.

Tags

  • Communications protocols
  • History of the Internet
  • Internet protocols
  • Network protocols
  • OSI model
  • X.25

Keep exploring