Computer Science - ICT Grade 8 Computer Networks TCPIP DNS HTTP

Grade 8 Computer Science – Computer Networks: TCP/IP, DNS, HTTP

1. The Driving Question

"If you type ‘youtube.com’ into your browser, your video loads in seconds—but how does your computer actually find YouTube’s servers, ask for the video, and get it back without mixing it up with someone else’s request? And why doesn’t the video just disappear if one tiny piece of data gets lost along the way?"

2. The Core Idea – Built, Not Listed

Imagine you’re sending a handwritten letter to a friend in another city. You don’t just drop it in a mailbox and hope—you follow a system: - You write their address on the envelope (like an IP address).
- You put your return address so they can reply.
- You drop it in a mailbox, and the postal service sorts it through hubs and routes (like routers on the internet).
- If the letter gets torn, the postal service notices and asks you to resend it (like TCP checking for lost data).
- But you don’t write their full address every time—you just write “Sarah’s House” and your brain (or a phone book) remembers the real address (like DNS translating “youtube.com” to an IP address).
- Finally, when you ask for a video, your computer doesn’t just say “send me a video”—it uses a specific language (like HTTP) to say, “GET this exact video file, please.”

This system—TCP/IP—is the internet’s postal service. It breaks data into packets, labels them, sends them through the fastest routes, and makes sure they arrive intact. Without it, the internet would be like mailing a puzzle without the box: pieces would get lost, mixed up, or delivered to the wrong person.

Key Vocabulary:
- TCP (Transmission Control Protocol)
Definition: A set of rules that ensures data sent over the internet arrives completely and in the correct order.
Example: If you download a song, TCP checks that all the audio chunks arrive and reassembles them in the right sequence—like a DJ making sure every beat of a mixtape is in place.
(Note: In college networking, TCP is just one part of the "transport layer"; other protocols like UDP skip error-checking for speed, like live video calls where a few lost pixels don’t matter.)

• IP Address (Internet Protocol Address)
  Definition: A unique numerical label assigned to every device on a network, like a home address for computers.
  Example: Your phone’s IP address might be 192.168.1.5 at home, but when you use mobile data, it changes to something like 104.28.12.34—like how your mailing address changes if you move.
  (Note: IPv4 (e.g., 192.168.1.1) is running out of addresses, so IPv6 (e.g., 2001:0db8:85a3::8a2e:0370:7334) was created to handle more devices.)

• DNS (Domain Name System)
  Definition: A system that translates human-readable website names (like google.com) into machine-readable IP addresses (like 172.217.3.110).
  Example: When you type “netflix.com,” DNS is like a phonebook that looks up the number (IP address) so your computer knows where to call.
  (Note: DNS is hierarchical—like a tree. .com is a top-level domain, netflix is a subdomain, and www is a sub-subdomain. College courses dive into DNS security and how attacks like "DNS spoofing" can redirect you to fake websites.)

• HTTP/HTTPS (Hypertext Transfer Protocol [Secure])
  Definition: The language browsers and servers use to request and send data (like web pages, images, or videos).
  Example: When you click a YouTube link, your browser sends an HTTP GET request—like raising your hand in class and saying, “Can I have the video for ‘Cat Fails Compilation’?” (Note: HTTPS adds encryption (the "S" stands for "Secure"). In cybersecurity, you’ll learn how HTTPS prevents "man-in-the-middle" attacks where hackers eavesdrop on your data.)

3. Assessment Translation

How This Appears on State Tests (Grade 8):
- Multiple Choice: Questions test understanding of how protocols work together (e.g., “Which protocol ensures data arrives in order?” → TCP).
Distractor Patterns: - Confusing TCP (error-checking) with UDP (faster, no error-checking).
- Mixing up DNS (name-to-IP) with IP addresses (the actual address).
- Thinking HTTP handles file transfers (it’s for web pages; FTP is for files).
- Short Answer: “Explain how DNS and IP work together to load a website.” (Expect 2–3 sentences with terms like translate, request, IP address.) - Diagram Labeling: Label a flowchart of how a browser loads a webpage (e.g., “User types URL → DNS lookup → TCP connection → HTTP request → Server response”).

Proficient vs. Developing Responses:
| Proficient | Developing | |----------------|----------------| | “DNS translates the website name into an IP address so your computer knows where to send the request. TCP breaks the data into packets and makes sure they all arrive correctly, then HTTP asks the server for the specific webpage.” | “DNS is like a phonebook. TCP sends data. HTTP is for websites.” (Missing how they work together.) | | Labels all steps in a diagram with correct terms. | Skips steps or uses vague terms like “the internet finds the website.” |

Model Proficient Response (Short Answer):
Question: “Describe what happens when you type ‘wikipedia.org’ into your browser and press Enter.” Answer: 1. Your browser asks DNS to translate wikipedia.org into an IP address (like 91.198.174.192).
2. Your computer uses TCP to open a connection to that IP address, breaking the request into packets.
3. Your browser sends an HTTP GET request to the server, asking for the Wikipedia homepage.
4. The server sends back the webpage data (also in packets), which TCP reassembles and displays in your browser.

4. Mistake Taxonomy

Mistake 1: Confusing DNS with IP Addresses
- Question: “What is the role of DNS in loading a website?” - Common Wrong Answer: “DNS is the address of the website.” - Why It Loses Credit: DNS translates names to addresses—it’s not the address itself.
- Correct Approach: - DNS is like a phonebook: you look up “Pizza Hut” to find its phone number (IP address).
- The IP address is the actual “number” (e.g., 34.102.136.180).
- Without DNS, you’d have to memorize IP addresses for every website.

Mistake 2: Thinking HTTP Handles Error-Checking
- Question: “Which protocol ensures that all parts of a downloaded file arrive correctly?” - Common Wrong Answer: “HTTP” (or “DNS”).
- Why It Loses Credit: HTTP is for requesting data; TCP is for delivering it reliably.
- Correct Approach: - HTTP is like ordering food: you ask for a burger (GET request).
- TCP is like the delivery driver who checks the order is complete and correct before handing it to you.
- If a packet is lost, TCP asks for it to be resent.

Mistake 3: Skipping Steps in a Network Flowchart
- Question: “Label the steps in how a browser loads a webpage.” - Common Wrong Answer: Skips DNS or TCP, e.g., “Type URL → HTTP request → Server sends webpage.” - Why It Loses Credit: Missing steps show incomplete understanding of how the internet works.
- Correct Approach: 1. User types URL (e.g., twitter.com).
2. DNS lookup translates twitter.com to an IP address.
3. TCP establishes a connection to the IP address.
4. HTTP sends a GET request for the webpage.
5. Server sends data back (via TCP), which the browser displays.

5. Connection Layer

1. Within Computer Science:
   TCP/IP → Network Security — Understanding how data is broken into packets helps explain why firewalls inspect individual packets (like checking each envelope in the mail for bombs).

2. Across Subjects:
   DNS → Linguistics — DNS is like a language’s grammar rules: it defines how words (domain names) map to meanings (IP addresses). Without rules, communication breaks down (like a sentence with no grammar).

3. Outside School:
   HTTP/HTTPS → Online Shopping — When you see a padlock icon in your browser’s address bar, that’s HTTPS encrypting your credit card info. Without it, hackers could steal your data like a thief opening your mail.

6. The Stretch Question

“If the internet is just a bunch of computers sending packets, why can’t you just send a file directly to your friend’s computer by typing their IP address into your browser? What’s actually stopping you?”

Pointer Toward the Answer:
- Your friend’s computer isn’t listening for HTTP requests like a web server is—it’s like calling someone’s phone when they’re not expecting a call.
- Most home IP addresses are dynamic (they change) and hidden behind NAT (Network Address Translation), which acts like a receptionist redirecting calls.
- Even if you knew their IP, firewalls and ISPs block unsolicited connections for security—like a bouncer at a club checking IDs.
- To send a file directly, you’d need a program (like BitTorrent or a file-sharing app) that speaks a different protocol (like FTP or WebRTC) and bypasses these barriers.