ArticleslgStudy

computer science

Internet protocol suite

Internet protocol suite 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 Internet protocol suite rather than just read about it. In short: The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP).

Internet protocol suite — main illustration
Internet protocol suite — illustration

Key takeaways

  • Internet protocol suite 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 Internet protocol suite to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Internet protocol suite from memory before moving on to harder problems.

Reference excerpt

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP). Early versions of this networking model were known as the Department of Defense (DoD) Internet Architecture Model because the research and development were funded by the Defense Advanced Research Projects Agency (DARPA) of the United States Department of Defense. The Internet protocol suite provides end-to-end data communication specifying how data should be packetized, addressed, transmitted, routed, and received. This functionality is organized into four abstraction layers, which classify all related protocols according to each protocol's scope of networking. An implementation of the layers for a particular application forms a protocol stack. From lowest to highest, the layers are the link layer, containing communication methods for data that remains within a single network segment (link); the internet layer, providing internetworking between independent networks; the transport layer, handling host-to-host communication; and the application layer, providing process-to-process data exchange for applications. The technical standards underlying the Internet protocol suite and its constituent protocols are maintained by the Internet Engineering Task Force (IETF). The Internet protocol suite predates the OSI model, a more comprehensive reference framework for general networking systems.

History

Early research

The Internet protocol suite has its roots in research and development into computer networks sponsored by the Defense Advanced Research Projects Agency (DARPA) in the late 1960s. In August 1968, BBN was selected by ARPA to build the Interface Message Processors (IMPs) for the ARPANET, the precursor to the modern Internet. The IMPs were the very first generation of gateways, known today as routers. Under the leadership of Frank Heart and Bob Kahn, four IMPs were produced for nearly US$1 million from September to December 1969. The first IMP was shipped to the University of California, Los Angeles in September 1969 and the second to the Stanford Research Institute a month later. The first message between the two IMPs was "LO" — phonetically, "Hello" — but the SRI host crashed before the UCLA researcher could complete typing the "LOGIN" command. After DARPA initiated the pioneering ARPANET in 1969, Steve Crocker established a "Network Working Group" which developed a host-host protocol, the Network Control Program (NCP). In the early 1970s, DARPA started work on several other data transmission technologies, including mobile packet radio, packet satellite service, local area networks, and other data networks in the public and private domains. In 1972, Bob Kahn joined the DARPA Information Processing Technology Office, where he worked on both satellite packet networks and ground-based radio packet networks, and recognized the value of being able to communicate across both. In the spring of 1973, Vinton Cerf, at Stanford University, began collaborating with Kahn on the goal of designing the next protocol generation for the ARPANET to enable internetworking. They drew on the experience the international research community, through the International Network Working Group (INWG), chaired by Cerf, which included researchers from the ARPANET community, Xerox PARC, the United Kingdom and France. During the summer of 1973, Kahn and Cerf worked out a fundamental reformulation, in which the differences between local network protocols were hidden by using a common internetwork protocol, and, instead of the network being responsible for reliability, as in the existing ARPANET protocols, this function was delegated to the hosts. Cerf and Kahn credit several members of INWG with important influences on this design, which was published in May 1974. The first specification of this Transmission Control Program was written in December 1974 by Cerf, Yogen Dalal and Carl Sunshine at Stanford University. DARPA contracted with BBN Technologies, Stanford University, and University College London to begin developing operational versions of the protocol on several hardware platforms in 1975. Several versions were developed through discussion via the Internet Experiment Note (IEN) series. Initially, the Transmission Control Program, the precursor to the later protocol suite, provided only a reliable byte stream service, not datagrams. As experience with the protocol grew, collaborators recommended division of functionality into layers of distinct protocols, providing direct access to datagram service. Advocates included Bob Metcalfe, Yogen Dalal and John Shoch at Xerox PARC; Danny Cohen, who needed it for his packet voice work; and Jonathan Postel of the University of Southern California's Information Sciences Institute, who edited the Request for Comments (RFCs), the technical and strategic document series that has both documented and catalyzed Internet development. Postel stated, "We are screwing up in our design of Internet protocols by violating the principle of layering." Encapsulation of different mechanisms was intended to create an environment where the upper layers could access only what was needed from the lower layers. A monolithic design would be inflexible and lead to scalability issues. In version 4, written in 1978, Postel split the Transmission Control Program into two distinct protocols, the Internet Protocol (IP) as a connectionless layer and the Transmission Control Protocol (TCP) as a reliable connection-oriented service.

… excerpt ends here. Continue reading the full article.

Illustrations

Internet protocol suite: Diagram of the first internetworked connection. On a rainy Tuesday, November 22, 1977, data flowed from the van to SRI in Menlo Park and the University of Southern California via England, Boston, and Sweden across three types of networks: packet radio, the satellite network, and the ARPANET.[29]
Diagram of the first internetworked connection. On a rainy Tuesday, November 22, 1977, data flowed from the van to SRI in Menlo Park and the University of Southern California via England, Boston, and Sweden across three types of networks: packet radio, the satellite network, and the ARPANET.[29]
Internet protocol suite: Conceptual data flow in a simple network topology of two hosts (A and B) connected by a link between their respective routers. The application on each host executes read and write operations as if the processes were directly connected to each other by some kind of data pipe. After establishment of this pipe, most details of the communication are hidden from each process, as the underlying principles of communication are implemented in the lower protocol layers. In analogy, at the transport layer the communication appears as host-to-host, without knowledge of the application data structures and the connecting routers, while at the internetworking layer, individual network boundaries are traversed at each router.
Conceptual data flow in a simple network topology of two hosts (A and B) connected by a link between their respective routers. The application on each host executes read and write operations as if the processes were directly connected to each other by some kind of data pipe. After establishment of this pipe, most details of the communication are hidden from each process, as the underlying principles of communication are implemented in the lower protocol layers. In analogy, at the transport layer the communication appears as host-to-host, without knowledge of the application data structures and the connecting routers, while at the internetworking layer, individual network boundaries are traversed at each router.
Internet protocol suite: Encapsulation of application data descending through the layers described in RFC 1122
Encapsulation of application data descending through the layers described in RFC 1122

Worked examples

Example 1 — a first encounter with Internet protocol suite

Start with the simplest possible case. Write down what Internet protocol suite 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 Internet protocol suite 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 Internet protocol suite 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 Internet protocol suite

In research
Internet protocol suite 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 Internet protocol suite 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
Internet protocol suite is common in secondary-school and first-year university syllabi. It links to neighbouring topics History of the Internet, Internet protocols, Network architecture, so understanding it makes those chapters shorter.
In everyday life
Look for Internet protocol suite 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 Internet protocol suite in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Internet protocol suite 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 Internet protocol suite out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Internet protocol suite in simple terms?

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagra…

Why does Internet protocol suite 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 Internet protocol suite?

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 Internet protocol suite.

Tags

  • History of the Internet
  • Internet protocols
  • Network architecture
  • Reference models

Keep exploring