π Lecture 1 β Course Introduction
π Overview: This lecture introduces the foundational motivations for studying computer networking, from everyday applications to the scale of the Internet. It explains why networking matters in modern life and outlines the course structure, including practical troubleshooting and simulation tools. This sets the stage for understanding how networks function at a high level before diving into technical details.
ποΈ Topics Covered
The lecture covers three main motivations for studying computer networking: the ability to access information remotely (e.g., bank accounts, news), daily life applications (e.g., email, web, streaming, video conferencing) and their common problems (delays, slow servers), and the Internet as the largest engineered system ever created with billions of connected devices. It then introduces the course composition, which has three parts: networking fundamentals from a practical viewpoint, packet analysis using Wireshark for troubleshooting, and network simulation using Packet Tracer.
π Lecture Summary
Motivation1: Information I can receive
Now-a-days, we can get a lot of information while sitting in front of the computer. For example, we can access our bank accounts; we can receive world news, look at the weather forecast etc. This has become possible because of computer networking.
π‘ Why this matters: This shows that networking is the invisible infrastructure that enables remote access to data and services.
Motivation 2: Daily life Applications
Email, web, instant messaging, P2P file sharing, network games, streaming videos, and real-time video conferencing are those applications that we use in our daily lives. We may encounter issues such as response delays and slow application at the server.
Motivation 3: Internet
The largest engineered system ever created by mankind is the Internet which consists of hundreds of millions of connected computers, communication links, and switches. There are billions of users who connect via laptops, tablets, and smartphones.
π‘ Why this matters: The Internet's unprecedented scale and complexity make understanding its operation essential for troubleshooting and innovation.
In this course, we will look at how the computer networks work, how we can troubleshoot their problems using Wireshark, and how we can simulate new networks using Packet Tracer.
Course Composition
We have divided the course into three Main Parts.
- Part 1 presents the networking fundamentals from practical point-of-view and does not delve into the theoretical nitty-gritties.
- Part 2 describes how analyzing packets with the Wireshark tool can help a student to troubleshoot his network.
β Key Takeaways
Computer networking enables modern life by providing remote access to information and supporting daily applications like email, web, and video conferencing, though issues like response delays can occur. The Internet is the largest engineered system ever created, with hundreds of millions of connected computers and billions of users. This course takes a practical approach, focusing on how networks work, troubleshooting with Wireshark, and simulating networks with Packet Tracer. The course is divided into three parts: practical networking fundamentals (Part 1) and packet analysis with Wireshark (Part 2). Students must understand that networking is the foundation for all modern digital services and communication tools.
π§ Quick Revision Questions
- What are two examples of information you can access remotely thanks to computer networking?
- Name four daily-life applications that rely on computer networks.
- What two common problems do users encounter with network applications?
- Why is the Internet described as the "largest engineered system ever created by mankind"?
- What two software tools will be used in this course for troubleshooting and simulation?
π Lecture 2 β What is a Network?
π Overview: This lecture defines a computer network as a combination of hardware, software, and cabling that enables communication between computing devices. It explores a simple single-site network's components, the role of a switch, and presents different professional perspectives (Server Guy, Cabling Guy) to illustrate how various experts view the network.
ποΈ Topics Covered
This lecture begins by defining a computer network and illustrating a simple single-site network diagram using a cloud to hide implementation details. It then provides a closer look at the network's physical components, including PCs, cables, wall sockets, wiring closets, and the central switch. Finally, it contrasts the perceptions of different networking professionals, specifically the Server Guy and the Cabling Guy, showing how their roles shape their view of the same network.
π Lecture Summary
Topic 2: What is a Network?
This topic provides the basic know-how of a simple computer network. A computer network is a combination of hardware, software, and cabling. This combination allows multiple computing devices to communicate with each other and thus gives computers the ability to communicate with each other. A simple network is shown in a diagram, which is a typical small network used by a company at a single site. In a network diagram, we use a cloud to hide details such as hardware, software, and cabling when those details are not important to the current discussion. A server provides some form of service to the users.
A closer look at the simple network reveals that a user's PC has networking software installed, and a cable that connects his PC to a socket on the wall. That socket has a cable on the hidden other side of the wall plate. Cables normally run under the floor, in the ceiling, or some other hidden place, with the other end being in a wiring closet. All the cables connect to a switch inside the wiring closet. A switch consists of specialized hardware and software that forwards the network traffic back and forth between the various network devices on the network. There are many places (called switch ports) into which you can plug in one of the networking cables.
Now, we look at the different perceptions three different people have according to their work on a different aspect of a network. First, we study the Server Guy, who is responsible for the server and needs some PC hardware skills, but more importantly, needs strong skills with software. The server guy views the rest of the network as a network utility, i.e., he treats the rest of the network just like you think of the telephone, electrical power, and water system. There is no need to think about it unless it's not working. Next is the Cabling Guy, also known as an electrician. He runs the cables from each cubicle back to the wiring closet. His job requires physical dexterity and knowledge of how to conform to electrical building standards. He focuses on installing, testing, and troubleshooting the cabling from each wall plate to the wiring closet. He makes sure that there's a working cable running from the wiring closet to each place in the building where a computer needs to connect to the network. π‘ Why this matters: Understanding these different perspectives is crucial because network design, troubleshooting, and management require collaboration between specialists who view the network at different layers.
π Definition β Computer Network: A combination of hardware, software, and cabling that allows multiple computing devices to communicate with each other. π Definition β Cloud: A symbol in network diagrams used to hide details that are not important to the current discussion. π Definition β Server: A device that provides some form of service to the users. π Definition β Wiring Closet: A location where all cables from various wall sockets terminate and connect to networking equipment. π Definition β Switch: Specialized hardware and software that forwards network traffic back and forth between various network devices on the network. π Definition β Switch Ports: Places on a switch into which you can plug in one of the networking cables. π Definition β Network Utility: A view of the network (held by the Server Guy) where it is treated like an essential service (electricity, water, telephone) that is only thought about when it is not working.
β Key Takeaways
A computer network is fundamentally a combination of hardware, software, and cabling enabling device communication, with a simple single-site network consisting of user PCs, cables, wall sockets, a wiring closet, and a central switch that forwards traffic. The switch is the core device that interconnects all other devices on the network. Different professionals, like the Server Guy (who views the network as a utility) and the Cabling Guy (who focuses on physical cable installation), have vastly different perceptions of the same network. Understanding these perspectives is essential for effective teamwork in network design and maintenance. The cloud symbol is used in diagrams to abstract away unnecessary details.
π§ Quick Revision Questions
- What are the three core components that make up a computer network according to this lecture?
- What is the primary function of a switch in a simple single-site network?
- How does the "Server Guy" perceive the rest of the network, and what term is used to describe this perception?
- What is the main responsibility of the "Cabling Guy"?
- Why is a cloud symbol used in network diagrams, and what information does it hide?
π Lecture 3 β Traditional Computer Networks
π Overview: This lecture explores traditional computer networks, focusing on two major examples: Enterprise WANs and the Internet. Understanding these network types is essential because they form the backbone of modern organizational and global communication.
ποΈ Topics Covered
This lecture examines two well-known examples of computer networks: Enterprise WANs, which connect all sites of a large company located at multiple locations, and the Internet, which connects almost all enterprise networks and individual users worldwide through Internet Service Providers (ISPs).
π Lecture Summary
Topic 3: Traditional Computer Networks
In this topic, we study different traditional computer networks. There are two well-known examples of computer networks. They are named an Enterprise WAN and the Internet.
An Enterprise WAN is a network that should have the ability to connect all sites of a big company, located at multiple sites. You call it an enterprise network because the network is owned by and created by one company, and a company can be considered to be an enterprise.
A typical enterprise has three remote branch offices, each with few PCs and a printer. The headquarters site has more users (hence, more PCs), as well as several servers. Each remote site consists of a simple network.
The Internet is a unique computer network as it connects almost all enterprise networks and individual users. The Internet works with the help of companies called Internet service providers (ISPs), which provide service to companies and individuals to connect them to the Internet. This makes almost all computers on the planet can communicate with each other.
π Definition β Enterprise WAN: A network owned and created by one company that connects all sites of a large enterprise located at multiple locations. π Definition β Internet: A unique computer network that connects almost all enterprise networks and individual users worldwide. π Definition β Internet Service Provider (ISP): A company that provides service to companies and individuals to connect them to the Internet.
π‘ Why this matters: Understanding the distinction between private enterprise networks and the public Internet is fundamental to grasping how organizations manage their internal communications versus how global connectivity is achieved.
β Key Takeaways
An Enterprise WAN is a private network owned by a single company that connects multiple branch offices and headquarters, often featuring remote sites with few PCs and printers alongside a larger headquarters with more users and servers. The Internet is a global, public network that connects enterprise networks and individual users together, operating through ISPs that provide connection services. ISPs enable almost all computers on the planet to communicate with each other, making the Internet unique in its scope and connectivity. Each remote site in an enterprise WAN consists of a simple network, while the headquarters has more resources and users. The key distinction between these networks lies in ownership, purpose, and scale of connectivity.
π§ Quick Revision Questions
- What are the two well-known examples of traditional computer networks discussed in this lecture?
- Why is an enterprise network called an "enterprise network"?
- What is the typical structure of an enterprise WAN in terms of branch offices and headquarters?
- How does the Internet connect almost all computers on the planet?
- What role do Internet Service Providers (ISPs) play in the Internet?
π Lecture 4 β Using the Network by Accident
π Overview: This lecture explores the concept of "accidental" network servicesβnetwork functions that operate invisibly to end users. Using the narrative of an employee named Fred, the lecture demonstrates how users can unknowingly utilize network resources, and introduces fundamental network services like file sharing, printer sharing, and naming services that operate transparently.
ποΈ Topics Covered
The lecture covers the scenario of using the network without conscious awareness, introduces the concept of "accidental" network services through the story of Fred and Wilma, explains the shift from manual diskette-based file transfer to automatic network operations, and discusses the key network services that enable this transparency including file sharing and printer sharing.
π Lecture Summary
Using the Network by Accident
This topic discusses the scenario when we use the network by accident. Some of the most common network services hide the network from the end user. We call them "accidental" network services. To understand this concept, let's assume an employee named Fred working at a remote office. He is the master of his own domain; he has a PC, a printer, and he can do all his work without much interruption from the home office.
Fred's daily tasks include opening a document with a word processor, changing some of the text contained in it, and printing it. He then mails the letter to the customer and saves the changes to the letter.
π Definition β Accidental Network Services: Network services that operate transparently, hiding the network from the end user who may not even be aware they are using network resources.
Fred's PC Setup
As Fred's company grows, Home office sends Wilma to Fred's office to work with him and help him get all the work done. She brings her fast high-end PC with her to the new office and installs a network. She takes over Fred's old printer and connects it to her own PC. Also copies all the customer letters from Fred's PC over to her PC.
π‘ Why this matters: In this new network setup, Fred has no idea about the network at all. Wilma knows how it works, but Fred remains unaware. This sets up the scenario for "accidental" network usage.
Fred's Manual Workaround
To do his job on the very next day, Fred starts up his word processor, grabs a diskette, and walks over to Wilma's computer and copies a customer letter onto the diskette. He walks back to his desk, updates the letter using his old computer, and then walks back to Wilma's computer with the diskette. Then Fred copies the file onto the hard drive of Wilma's computer, then prints the file on his old printer. This is a working network in which Fred is unaware of the network's existence. He uses the network only by "accident"βin the sense that Wilma set up the network, but Fred never explicitly uses it.
π Example: Fred's manual process without knowing about the network:
- Starts word processor
- Grabs diskette
- Walks to Wilma's computer
- Copies customer letter onto diskette
- Walks back to his desk
- Updates the letter using his old computer
- Walks back to Wilma's computer with diskette
- Copies the file onto Wilma's hard drive
- Prints the file on his old printer
The Concept of "Using the Network by Accident"
This demonstrates a working network where Fred remains completely unaware of the network's existence. He uses the network only by "accident"βin the sense that Wilma set up the network, but Fred never explicitly uses it. This illustrates how network services can be completely transparent to end users who benefit from network connectivity without conscious knowledge of it.
π Definition β Using the Network by Accident: The scenario where a user benefits from network services (like file sharing or printer sharing) without explicitly knowing they are using a network, because the services operate transparently.
β Key Takeaways
This lecture introduces the fundamental concept that many network services are designed to be invisible to end users. The story of Fred demonstrates that users can effectively utilize network resourcesβsuch as file access and printingβwithout any awareness of the underlying network infrastructure. These "accidental" network services are among the most common and important in everyday computing. The key insight is that network transparency reduces user complexity and enables seamless workflow, even for users who have no technical knowledge of how networks operate. This invisibility is a deliberate design feature of many network services.
π§ Quick Revision Questions
- What are "accidental" network services and why are they called "accidental"?
- In the scenario with Fred and Wilma, what physical device did Fred use to transfer files before the network was transparent to him?
- How did Fred unknowingly use the network when printing the updated letter?
- What is the fundamental characteristic that distinguishes "accidental" network services from explicit network services?
- Why might a user like Fred never realize they are using network resources?
π Lecture 5 β Using the Network on Purpose
π Overview: This lecture examines the deliberate use of computer networks, particularly the Internet, when users are consciously aware they are accessing resources beyond their local machine. It contrasts this with transparent network usage (like file servers) and highlights the fundamental shift in awareness that occurs when connecting to the global network. Understanding this distinction is crucial for grasping how modern computing environments operate and how users interact with distributed resources.
ποΈ Topics Covered
The lecture begins by contrasting the "sneakernet" method (physically carrying files via floppy disk) with transparent network use, where shared files and printers appear locally. It then introduces the concept of using the network on purpose, primarily through the Internet, explaining that users are typically aware they are accessing resources across a network. The text emphasizes the Internet's role as a global network connecting organizations worldwide, using the analogy of making a phone call to illustrate the global reach and awareness required when using the network intentionally.
π Lecture Summary
The Sneakernet Method
This section describes an inefficient manual method of file transfer where Fred physically carries a floppy disk between computers. Fred copies a file from his PC to a floppy disk, walks it over to Wilma's computer, copies it there, modifies it with a word processor, copies the updated file back onto the floppy disk, walks back to his own computer, replaces the old file, then returns to Wilma's computer to use her word processor and printer to produce a hard copy for a customer. This physical transport of data is called sneakernet.
π Definition β Sneakernet: A method of transferring data by physically carrying storage media (like floppy disks, USB drives) from one computer to another, rather than using a computer network.
Transparent Network Use (The Contrast)
This section shows how the same job could be done more efficiently if Fred used a network without even knowing it. By simply looking on his C drive in a folder called "Customers," Fred could access all the same filesβwhich are actually stored on Wilma's PC, functioning as a file serverβbut this is hidden from him. Similarly, when Fred clicks the Print icon from his word processor, he sees a printer called "same old printer." If he prints to that printer, it will print on his "same old printer," even though it's actually connected to Wilma's PC, which is set up as a print server. The network's presence is completely transparent to Fred.
π Definition β File Server: A computer on a network that stores files that can be accessed by other computers on the network, making shared files appear as if they were local.
π Definition β Print Server: A computer on a network that manages printing for multiple users, allowing them to print to a printer as if it were directly connected to their own computer.
Using the Network on Purpose
This topic studies the case when we use the network on purpose. When we use the Internet, chances are high that we will be aware that we are using a network. The Internet is the global network to which almost every company and organization in the world is connected.
π Example: The lecture compares Internet usage to making a phone call to almost anyoneβthe user is consciously aware they are connecting to another location or system, unlike the transparent network scenario where Fred doesn't realize he's accessing remote resources.
π‘ Why this matters: This distinction between transparent and intentional network use is fundamental: the Internet requires active awareness and purposeful action from the user, whereas local network services (like file sharing) can be designed to be invisible, providing seamless functionality without requiring user knowledge of the underlying network infrastructure.
β Key Takeaways
This lecture establishes the critical difference between transparent network use (where users access shared resources like files and printers without realizing a network is involved) and intentional network use (where users are consciously aware they are connecting to the global Internet). The contrast is illustrated through the inefficient sneakernet method versus the invisible file server and print server model. The Internet is defined as the global network connecting virtually all organizations worldwide, requiring deliberate user awareness. Understanding these two modes of network interactionβtransparent vs. intentionalβis essential for grasping how both local area networks and the global Internet function in practice.
π§ Quick Revision Questions
- What is "sneakernet" and why is it inefficient compared to network-based file access?
- In Fred's transparent network scenario, what two roles does Wilma's PC serve?
- How does Fred access files and printers located on Wilma's PC without knowing he's using a network?
- According to the lecture, what is the key difference between using a local network (file server) and using the Internet?
- What analogy does the lecture use to describe the awareness level required when using the Internet?
π Lecture 6 β Well-known Network Applications
π Overview: This lecture explores the fundamental working principles of three major network applications that power the Internet: web browsing, e-mail, and Voice over IP (VoIP). Understanding these applications is essential because they represent the most common ways people and businesses communicate and share information online daily.
ποΈ Topics Covered
The lecture covers the conceptual view of the Internet and how ISPs interconnect networks, then dives into three well-known network applications: Web Browsing (how browsers request and display web pages using URLs), E-Mail (how users send and receive messages through mail servers), and Voice over IP (VoIP) (how voice calls are made over Internet connections using digitized voice packets).
π Lecture Summary
Conceptual View of the Internet
Most computers can communicate with each other over the Internet because most computer networks connect to each other through Internet Service Providers (ISPs). Networking connections among enterprises, individual home users, and other ISPs are provided by ISPs. For example, ISP1's network allows individual computers like Fred's to connect to it, and Fred could communicate with computers inside Company A if security policies permit. Company A created its enterprise network using hardware, software, and cabling paid for by Company A. ISP1 also creates its network using its own funds. ISP1 agrees to allow Company A's traffic to pass through ISP1 and on to other ISPs so that Company A can communicate with the rest of the world. In return, Company A pays ISP1 an ongoing fee.
Web Browsing
A web browser allows you to sit at one computer and display information that resides in a web server somewhere on the Internet. A web server consists of software that resides on the computer accessible to the end user via the Internet. The information can be in many forms, including simple text, graphics images, animation, video streams, and audio clips. Well-known examples of web browsers are Internet Explorer, Google Chrome, and Firefox Mozilla. After a browser requests a web page from a web server, the server replies by sending the contents of the web page back to the browser. Companies, organizations, and even individuals can create their own websites on the Internet.
π Definition β URL (Universal Resource Locator): A string of characters that uniquely identifies a particular web page.
π Example: A client such as Fred brings up the web browser software on his computer and points to the URL of the website, such as www.fredsco.com, to access that web page.
E-mail allows a user to create, send, and receive messages electronically. E-mail is sent between one user and another user, or in some cases, to multiple other users. The person sending the mail needs to know the e-mail address of the person who needs to receive the e-mail.
π Definition β E-mail address: A text string that represents the address of a person for the purposes of sending and receiving e-mail, much like a mailing address used for postal mail.
π Example: An e-mail address example is abc@yahoo.com. In a typical scenario, Barney wants to e-mail the sales department at Fred's Company by sending an e-mail to sales@fredsco.com. Barney does not actually send the e-mail directly to the recipient.
Voice over IP (VoIP)
VoIP (Voice over IP) allows users to talk to each other over the Internet. The analog voice signal is converted to a digital signal that can be sent over the Internet. Each side of the conversation generates about 50 packets per second using a codec (coder/decoder or compressor/decompressor). A CODEC is a device used to convert analog signals to digital signals and vice versa. Each VoIP packet includes the source and destination IP addresses. The packets are sent over the Internet as small chunks of digitized voice data. When these packets arrive at the destination, they are reassembled in the correct sequence and played back to the recipient.
π Definition β CODEC: A device used to convert analog signals to digital signals and vice versa.
π Formula: 50 packets per second β Each side of a VoIP conversation generates approximately 50 packets per second.
π Example: When two people talk over VoIP, each person's voice is digitized, broken into 50 packets per second, labeled with source and destination IP addresses, sent over the Internet, and reassembled at the other end for playback.
π‘ Why this matters: VoIP has revolutionized telecommunications by allowing voice calls to travel over the same Internet infrastructure used for data, dramatically reducing costs compared to traditional telephone networks.
β Key Takeaways
The Internet functions as a network of networks interconnected by ISPs, with enterprises paying fees for connectivity. Web browsing relies on browsers requesting web pages from web servers using URLs, with servers sending content back to the requesting browser. E-mail communication requires knowing the recipient's e-mail address and works through mail servers rather than direct sender-to-recipient transmission. VoIP converts analog voice to digital signals using a CODEC, generating approximately 50 packets per second per conversation, with each packet containing source and destination IP addresses for routing across the Internet.
π§ Quick Revision Questions
- What is the role of an ISP in connecting enterprise networks to the Internet?
- How does a web browser retrieve and display a web page from a web server?
- What is a URL and what is its purpose in web browsing?
- How does e-mail transmission differ from direct one-to-one communication?
- What is a CODEC and how many packets per second does a VoIP conversation typically generate?
π Lecture 7 β Building a Network: Starts with a Plan
π Overview: This lecture explains why rules and standards are crucial for networking, drawing an analogy from electrical standards. It introduces the basic physical components needed to build a simple network and emphasizes that both hardware and software must follow the same standards for communication to work.
ποΈ Topics Covered
The lecture begins by illustrating the importance of standards using everyday examples like electrical sockets and lamps. It then defines standards in networking, introduces the concept of physical connectivity, and lists the essential componentsβcabling, networking devices, and Network Interface Cards (NICs)βrequired to build a simple network. The summary concludes by highlighting that both hardware and software standards must be mutually implemented for successful data transfer.
π Lecture Summary
Topic 7: Building a Network: Starts with a Plan
In this topic, we study why rules and standards are important for networking. Standards are rules that make life a lot easier. To understand this idea, letβs have a look at a power socket on a nearby wall. You may find an electrical socket with three holes β two that accept flat metal prongs, and one that accepts a round metal prong. The flat metal prongs are parallel to each other. If you go to a store to buy an electrical device such as a lamp, you will expect that its power cord would fit into the wall socket of your house. In case it does not fit into the power socket, you will get very confused.
Letβs now imagine that you bought a new lamp. You plug it in, and the light bulb instantly is broken. You put in a new bulb, and it doesnβt light up. You decide that there is some problem with the lamp. So you bring it back to the store and replace it with an identical lamp. When you get it home, the same thing happens to this lamp too. What to do next? Letβs call the customer service to inquire about the problem. This is our special 'We light up your life' model of lamp. It uses the same kind of power cord you are used to using but requires less electrical voltage, saving you money. If you read the instructions for the lamp, you will see that it directs you to rewire and change the voltage coming out of the sockets you want to use for the lamp. 'If you plug this lamp into a normal wall socket, the extra voltage will fry the lamp, and it will no longer light up your life.' So contact an electrician and get your socket changed.
A standard therefore tends to define a particular thing, such as the shape of the wall socket and connector used by an electrical socket and electrical power cable. Another standard might dictate how much voltage flows through the wall socket, whether it is AC or DC, how much current, and the like. Both standards are important and must be followed to prevent exploding lamps. Similarly, networking has standards. First, the PCs in the network need some form of physical connectivity. Physical connectivity refers to the combination of cabling, networking devices, and network interface cards (NICs) in the computers, which together provide the physical capability to transmit and receive data across a network. Next, we show this idea.
π Definition β Standards: Rules that make life a lot easier by defining particular things like shape, voltage, or communication protocols. π‘ Why this matters: Just as electrical standards prevent exploding lamps, networking standards ensure that computers can successfully exchange data without errors or incompatibility.
π Definition β Physical Connectivity: The combination of cabling, networking devices, and Network Interface Cards (NICs) in computers, which together provide the physical capability to transmit and receive data across a network. π‘ Why this matters: Physical connectivity is the foundation upon which all network communication is built. Without the correct physical components and standards, no data can be sent or received.
Figure 7.1: Components of a Simple Network Both PCs have an NIC installed, and each card has a receptacle into which a cable can be connected. To emphasize their existence, the NICs are shown outside the PCs. The two computers must implement the same standards for how the networking software on each computer tells the other what it wants to do.
β Key Takeaways
Standards are fundamental for networking, just as they are for electrical systems, ensuring compatibility and preventing failures. Physical connectivity is the essential first step, requiring the correct combination of cabling, networking devices, and NICs. Both the hardware (NICs, cables) and the networking software must implement the same standards for two computers to communicate successfully. The NIC provides the physical receptacle for the cable, and each computer's software must follow identical rules to initiate and manage data transfer.
π§ Quick Revision Questions
- Why are standards important for networking? Provide an analogy used in the lecture.
- What are the three key components that together provide physical connectivity in a simple network?
- What is the role of a Network Interface Card (NIC) in a network?
- Besides hardware, what else must implement the same standards for two computers to communicate?
- According to the lecture's example, what happens when a deviceβs standard (e.g., voltage requirement) is not followed?
π Lecture 8 β Examples of Good Rules for Networking
π Overview: This lecture illustrates how networking standards and protocols enable successful computer communication by providing concrete examples. It demonstrates why both sending and receiving devices must agree on common rules for data transmission, including voltage levels for bit encoding and packet structures.
ποΈ Topics Covered
The lecture presents two main examples of networking implementation: Example 1 demonstrates human-to-computer communication analogy and voltage-level encoding standards for binary data transmission, using Fred and Wilma's computers as a case study. Example 2 shows how devices send data bits in groups called packets, with Wilma sending a file to Fred using a three-packet transmission.
π Lecture Summary
Example 1
When two humans communicate, one person says something and the other person listens. The two people need to understand the same language. Similarly, when computers communicate with each other over a network, the sending application needs to send some information to an application on the receiving side. Let's assume Fred's computer is using Wilma's computer, which is configured as a file server.
Over the network, the file will be transmitted in the form of binary digits (bits). The file server reads the file from the disk. A networking standard will define the encoding rules so that data can be transmitted. For example, it can ask the sender to change the voltage to one level to mean a binary 0, and another to mean a binary 1.
In the example shown in Figure 7.2, the NIC (Network Interface Card) inside Wilma's computer sends some electrical signal over the cable. The device on the other end of the cableβFred's PC NICβinterprets the incoming electrical signal. This will work if both NICs agree to some standard means of transmission.
For instance, imagine that Wilma's NIC sends a +5 volts to transmit a binary 0 and +10 volts to send a binary 1. If Fred's NIC expects to receive a +2 volt signal for binary 0 and +4 volts for binary 1, the network will not work because Fred will not understand what Wilma is sending him.
π Definition β Binary digit (bit): The smallest unit of data in computing, represented as either 0 or 1 π Formula/Standard: Voltage encoding β +5V = binary 0, +10V = binary 1 (example standard) π Example: Wilma's NIC sends +5V (binary 0) and +10V (binary 1), but Fred's NIC expects +2V for 0 and +4V for 1 β network fails because voltage levels don't match π‘ Why this matters: Both devices must agree on the same voltage encoding scheme for successful communication
Example 2
Devices in a network send bits in groups, generally called packets. Assume Wilma wants to send a file to Fred. She sends the data bits in the form of three packets.
π Definition β Packet: A group of bits transmitted together as a single unit over a network π Example: Wilma sends a file to Fred by dividing the data into three separate packets for transmission
β Key Takeaways
For successful network communication, both sending and receiving devices must agree on common standards, including the same encoding rules for representing binary data as voltage levels. The NICs on both ends must interpret electrical signals consistently, or data transmission will fail entirely. Data is transmitted in groups called packets rather than as individual bits. The human communication analogy helps understand that just as people need a common language, computers need common protocols to exchange information.
π§ Quick Revision Questions
- What must both NICs agree upon for successful network communication?
- In Example 1, what voltage levels did Wilma's NIC use to transmit binary 0 and binary 1?
- What happens when Fred's NIC expects different voltage levels than what Wilma's NIC sends?
- How are bits organized when devices send data over a network?
- What is the role of a networking standard in data transmission?
π Lecture 9 β Proprietary and Public Models
π Overview: This lecture explores the historical evolution from vendor-proprietary networking models to open, standardized models. It explains the problems created by proprietary systems like IBM's SNA and DEC's DECnet, and examines both short-term and long-term solutions that ultimately led to the public, interoperable networks we use today.
ποΈ Topics Covered
The lecture begins with a simple protocol for error recovery, explaining how packet numbering and retransmission enable reliable communication. It then transitions to the core topic of proprietary versus public networking models, covering the rise of vendor-specific systems like IBM's SNA and DEC's DECnet in the late 1960s-1970s. The discussion highlights the fundamental incompatibility problem between these proprietary networks and presents two key solutions: the short-term gateway emulation approach and the long-term development of public, open models.
π Lecture Summary
A Simple Protocol for Error Recovery
The lecture first illustrates a basic error recovery mechanism using an example where Fred receives three packets but the second packet contains corrupted bits, possibly due to electrical interference β where nearby electrical signals alter the intended voltage. For instance, if both NICs agreed that +5 volts equals binary 0 and +10 volts equals binary 1, receiving +7.5 volts creates confusion. The error recovery protocol works in three steps: (1) the sender numbers the packets, (2) the receiver (Fred) detects the error and sends a message asking the sender (Wilma) to resend the specific packet, and (3) Wilma resends packet 2.
π Definition β Error Recovery Protocol: A networking protocol that provides a method to recognize and recover from errors by having the sender number packets and allowing the receiver to request retransmission of specific corrupted packets.
Proprietary and Public Models
Networks emerged as part of each computer vendor's offerings from the late 1960s, becoming popular by the late 1970s. Each vendor created its own networking model so computers from that single vendor could communicate easily. The two largest vendors at networking's advent were International Business Machines (IBM) and Digital Equipment Corporation (DEC). IBM created Systems Network Architecture (SNA), and DEC created DECnet. These vendor-proprietary models allowed networks to function but had a critical flaw: proprietary networks cannot communicate with other networks. IBM computers could not communicate with DEC computers, so a company owning both types would need two separate networks.
π Definition β Proprietary Network Model: A networking model created by a single vendor that only allows its own computers to communicate easily, with no built-in ability to communicate with other vendors' networks.
Short-term Solution: Gateway Emulation
Two solutions emerged: a short-term and a long-term one. For the short-term solution, since IBM was roughly 10 times larger in gross revenues, DEC made its computers conform to the IBM SNA model. DEC created software that converted between DECnet standards and SNA standards, specifically a DEC-to-SNA gateway, which allowed the DEC and IBM SNA devices to talk to each other.
π Definition β Gateway: Software or hardware that converts between different networking standards, allowing communication between previously incompatible vendor-specific networks.
π Example: DEC created a DEC-to-SNA gateway that allowed its DECnet computers to communicate with IBM's SNA network, enabling a company with both IBM and DEC computers to form a single, interconnected network rather than maintaining two separate networks.
π‘ Why this matters: The gateway solution was only a temporary fix β it didn't solve the fundamental problem of proprietary lock-in, which led to the long-term need for open, public networking models that would allow any vendor's equipment to interoperate.
β Key Takeaways
The most critical concepts from this lecture are: (1) Error recovery in networking requires packet numbering and retransmission requests to handle corrupted data from electrical interference. (2) Early networking was dominated by proprietary models β IBM's SNA and DEC's DECnet β which only worked within each vendor's ecosystem. (3) Proprietary networks created a fundamental interoperability problem, forcing companies with multi-vendor environments to maintain separate networks. (4) The short-term solution was gateway emulation, where smaller vendors (like DEC) built conversion software to interface with dominant systems (like IBM's SNA). (5) This incompatibility problem ultimately drove the need for public, standardized networking models that would enable universal communication between any vendor's equipment.
π§ Quick Revision Questions
-
What is the three-step error recovery protocol described in the lecture, and why is packet numbering essential to this process?
-
What were the two dominant proprietary networking models in the late 1960s-1970s, and which vendors created each?
-
What is the fundamental disadvantage of proprietary networking models, as illustrated by the IBM and DEC example?
-
How did DEC solve the short-term interoperability problem with IBM's SNA network?
-
What caused the +7.5 volts problem in the error recovery example, and how does the protocol address such ambiguous signals?