Computing · JC 1 · Computer Networks and Web Applications · 1.º Período

The TCP/IP Model and Protocols

Understanding the four layers of the TCP/IP model and the concept of packet switching. Students will learn the functions of common protocols like HTTP, FTP, and IP.

• MOE Syllabus Outcomes
• 9569 5.2.1 Explain the layers of the TCP/IP model
• 9569 5.2.2 Describe the concept of packet switching

About This Topic

The web and the client-server model are the primary ways we interact with the internet. Students learn how a browser (the client) requests resources from a server using HTTP and HTTPS. We explore the role of the Domain Name System (DNS) in translating human-readable URLs into machine-readable IP addresses. This topic is essential for understanding how modern web applications are built and secured.

In the JC1 curriculum, we also discuss the difference between stateful and stateless protocols. Since HTTP is stateless, students learn how cookies and sessions are used to 'remember' a user's identity across different pages. This is a key concept for understanding privacy and security on the web. This topic particularly benefits from hands-on, student-centered approaches where students simulate the 'handshake' between a browser and a server.

Key Questions

1. What is the purpose of the TCP/IP model?
2. How does packet switching enable data transmission over the Internet?
3. What roles do IP addresses and MAC addresses play?

Learning Objectives

• Compare the process of sending a physical letter with sending data packets over a network, identifying key similarities and differences.
• Explain the role of protocols in ensuring reliable data transmission and interoperability between network devices.
• Analyze the potential consequences of data loss or packet reordering during network communication.
• Identify the fundamental steps involved in breaking down data into packets and reassembling them at the destination.

Before You Start

Introduction to Computer Networks

Why: Students need a basic understanding of what a network is and the concept of connected devices before learning how data travels.

Client-Server Model

Why: Understanding how clients request information from servers provides context for why data needs to be transmitted between devices.

Key Vocabulary

Packet	A small, discrete unit of data transmitted over a network. Packets contain both the data itself and control information like the source and destination addresses.
Protocol	A set of rules or procedures governing the transmission and reception of data between devices on a network. Protocols ensure devices can communicate effectively.
IP Address	A unique numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. It serves as an identifier for routing data.
Router	A networking device that forwards data packets between computer networks. Routers perform traffic directing functions on the Internet.
TCP/IP	A suite of communication protocols used to interconnect network devices on the internet. TCP (Transmission Control Protocol) handles reliable data delivery, while IP (Internet Protocol) handles addressing and routing.

Watch Out for These Misconceptions

Common Misconception

The web and the internet are the same thing.

What to Teach Instead

The internet is the infrastructure (cables, routers), while the web is an application that runs on top of it using HTTP. A 'service vs. infrastructure' discussion helps students distinguish between the two.

Common Misconception

HTTPS means the website itself is safe and trustworthy.

What to Teach Instead

HTTPS only means the connection is encrypted, not that the site owner is honest. A 'fake site' activity where a malicious site has a valid HTTPS certificate helps students understand the limits of encryption.

Active Learning Ideas

Simulation Game: The DNS Phonebook

One student acts as the 'Root Name Server,' another as the '.com TLD Server,' and another as the 'Authoritative Server.' A 'Client' student must navigate this hierarchy to find the IP address for a specific website, demonstrating the recursive nature of DNS.

30 min·Whole Class

Inquiry Circle: Inspecting the Web

Using the 'Developer Tools' in a browser, pairs inspect the network traffic of a popular site. They identify the HTTP request methods (GET, POST), the status codes (200, 404), and look for cookies being sent back and forth.

40 min·Pairs

Think-Pair-Share: The Stateless Dilemma

Students brainstorm how an online shopping cart would work if the server 'forgot' who they were every time they clicked a new link. They pair up to discuss how cookies solve this problem and what the privacy risks are.

20 min·Pairs

Real-World Connections

• When you stream a video on Netflix or YouTube, the video data is broken into thousands of packets. Routers across the internet direct these packets to your device, and protocols like TCP ensure they arrive in the correct order to play smoothly.
• Online banking transactions rely heavily on secure and reliable data transmission. Protocols ensure that your financial information is broken into packets, sent accurately to the bank's servers, and reassembled without errors for processing.

Assessment Ideas

Quick Check

Present students with a scenario: 'Imagine sending a large image file to a friend. Describe, in your own words, how this file might be broken down and sent across the internet, mentioning at least two key concepts from today's lesson.'

Discussion Prompt

Facilitate a class discussion using the prompt: 'Why is it crucial for every device on the internet to agree on and follow the same communication rules (protocols)? What might happen if a router decided to ignore the rules for sending packets?'

Exit Ticket

Ask students to write down one analogy for how data travels on a network (e.g., mail delivery, a convoy of trucks) and explain how their analogy relates to the concept of packets and protocols.

Frequently Asked Questions

What happens when I type a URL into my browser?

Your browser first checks its cache for the IP address. If not found, it asks a DNS server. Once it has the IP, it establishes a connection to the server (usually via a TCP handshake) and sends an HTTP GET request. The server then sends back the HTML, CSS, and images needed to display the page.

What is the difference between a GET and a POST request?

A GET request is used to retrieve data from a server and the parameters are visible in the URL. A POST request is used to send data to a server (like a password or a form) and the data is hidden in the body of the request, making it more secure for sensitive information.

How can active learning help students understand the client-server model?

Role-playing the 'HTTP Request-Response Cycle' is very effective. One student acts as the client and another as the server. By physically passing 'request headers' and 'response bodies' (on index cards), students see exactly what information is exchanged and why certain status codes (like 404 Not Found) are triggered. This makes the invisible 'chatter' of the web visible and logical.

Why do we need cookies?

Because HTTP is a stateless protocol, the server doesn't remember you from one request to the next. Cookies are small files stored on your computer that the browser sends to the server with every request, allowing the server to 'remember' your login status or shopping cart items.