Internet Services and Protocols
AdvancedThe internet interconnects countless networks through the TCP/IP suite: IP addresses and forwards packets, TCP guarantees reliable ordered delivery, DNS resolves domain names into IP addresses, HTTP and HTTPS fetch web pages, SMTP and POP handle email, and FTP transfers files.
- Protocols are the common rules of network communication; the internet is built on the TCP/IP suite.
- IP handles addressing and delivery, TCP handles reliability and order — IP manages the route, TCP manages the quality.
- DNS resolves domain names into IP addresses, the translator between web addresses and numbers.
文體小知識:科技知識說明文——拆解互聯網的核心服務與 TCP/IP、HTTP、DNS 等協定的分工,理解資料如何在網絡之間可靠傳送。
§Text Passage
1The internet is a network of networks linking countless networks worldwide. For devices of different brands and regions to communicate, they must follow common rules called protocols. The internet is built on the TCP/IP suite: IP handles addressing and packet delivery, while TCP ensures data arrives complete and in order.
2Every connected device has an IP address, which works like a house number so data knows where to go. A common IPv4 address consists of four numbers from 0 to 255 separated by dots. Since humans struggle to memorise numbers, the Domain Name System was invented: after a web address is typed in, a DNS server resolves the domain name into the matching IP address so the browser can locate the target server.
3The web uses the Hypertext Transfer Protocol: the browser sends a request to a web server, which returns the web page — a request-and-response model. Plain HTTP sends text in the clear that can be intercepted en route; HTTPS adds encryption and identity verification, making it essential for sensitive operations such as online payment and login.
4Email relies on two families of protocols: the Simple Mail Transfer Protocol sends mail from the sender to mail servers and on to the recipient, while the Post Office Protocol lets the recipient download mail from the server onto a device. The File Transfer Protocol uploads and downloads files between client and server, a common tool for website management and large-file exchange.
5Internet services go far beyond these: search engines help find information among billions of pages; cloud services move storage and software online for access anywhere; streaming plays audio and video while downloading; instant messaging and online forums have transformed human communication. Understanding how protocols divide the work behind these services is the key to data-response questions.
1Summary 重點摘要
The internet interconnects countless networks through the TCP/IP suite: IP addresses and forwards packets, TCP guarantees reliable ordered delivery, DNS resolves domain names into IP addresses, HTTP and HTTPS fetch web pages, SMTP and POP handle email, and FTP transfers files.
2Vocabulary cards Vocabulary
A set of communication rules that devices on a network follow, such as IP, TCP and HTTP.
The protocol that addresses data packets and delivers them from the source network to the destination network.
The unique numeric identity of a device online; common IPv4 addresses have four numbers from 0 to 255 separated by dots.
The protocol working with IP: it numbers data segments and guarantees complete, in-order delivery, retransmitting any loss.
The system that resolves domain names into IP addresses so users need not memorise numbers.
The protocol fetching web pages between browser and web server in a request-and-response model, sending text in the clear.
The secure version of HTTP adding encryption and identity verification, essential for sensitive transfers such as payment and login.
The protocol that sends email from the sender to mail servers and on to the recipient's mail server.
The protocol that downloads mail from a mail server onto the user's device for reading.
The protocol for uploading and downloading files between client and server, widely used for website management and large files.
3Step by step Steps
- Step 1: The internet and why protocols matterThe internet is not one giant network but a network of networks interlinking countless smaller ones worldwide. For devices of different brands and countries to communicate, they must agree on common data formats and procedures — these rules are protocols. Without them, data sent by one side would be unreadable to the other. For example, a Hong Kong computer exchanging data with an American server works only because both follow the TCP/IP protocol suite, their common language.
- Step 2: Division of labour between IP and TCPThe Internet Protocol handles addressing and delivery: it labels each packet with source and destination addresses so packets hop across networks. The Transmission Control Protocol, working above IP, guarantees quality: it numbers the data segments, waits for acknowledgements, and retransmits anything lost or out of order. For example, a large attachment is split into many packets taking different routes, and TCP reassembles them in sequence — IP manages the route, TCP manages reliability.
- Step 3: The format of an IP addressAn IP address is a device's house number on the network. The common version, IPv4, has four numbers each from 0 to 255 separated by dots, such as 192.168.1.101; the newer IPv6 uses eight groups of hexadecimal digits, providing vastly more addresses for exploding device numbers. Addresses may be static or dynamic: servers usually keep static addresses so users can find them, while home devices get dynamic addresses assigned automatically. For example, 300.12.5.1 is invalid because 300 exceeds the limit of 255 — a common exam check.
- Step 4: How DNS resolves a domain nameHumans remember www.example.com but not strings of digits; the Domain Name System is the translator between the two. After a web address is typed, the computer first asks a DNS server for the IP address matching the domain name, and only then sends the request to the target web server. Resolution is cached, so frequently used domain names are stored locally to speed up later visits. For example, when DNS fails, browsing by web address stops even though the network is fine, but entering the IP address directly still works — proof of its translating role.
- Step 5: HTTP versus HTTPSThe web runs on a request-and-response model: the browser sends an HTTP request to a web server, which returns the page. Plain HTTP transmits in the clear, so content can be intercepted or even altered en route, and site identity is hard to verify. HTTPS adds an encryption layer beneath HTTP: data is encrypted before sending, unreadable even if captured, and the server's identity can be verified; the address starts with https. For example, payment and login operations involving passwords and card numbers must use HTTPS — a standard conclusion in data-response questions.
- Step 6: How email protocols cooperateEmail is completed by two families of protocols in relay. When sending, the Simple Mail Transfer Protocol carries the mail from the sender's device to the sending mail server, and passes it between servers to the recipient's mail server. When receiving, the Post Office Protocol or similar downloads the mail from the receiving server to the recipient's device. For example, picture the postal system: SMTP is handing a letter to the post office and relaying it between offices, while POP is collecting mail from your post-office box to read at home — both are indispensable.
- Step 7: FTP and other internet servicesThe File Transfer Protocol uploads and downloads files between client and server; administrators commonly use it to upload finished pages to a web server. Beyond file transfer, internet services include search engines locating information among billions of pages by keywords, cloud services offering online storage and software, streaming playing audio and video while still receiving, and instant messaging and forums supporting text, voice and video. For example, memorise services with their protocols: the web with HTTP, email with SMTP and POP — a reliable answering technique.
4Diagrams Diagrams
5Worked example Example
Data question: an online bookstore's website has a product browsing page, a member login page and an online payment page. From a security perspective, explain which pages must use HTTPS and state the difference between HTTPS and HTTP.
- Classify the data: the payment page carries card numbers and passwords, the login page carries member names and passwords — all sensitive personal data; the browsing page sends only public product information.
- Point out HTTP's weakness: HTTP sends text in the clear, so anything intercepted en route can be read completely, and site identity is hard to verify.
- Explain how HTTPS works: HTTPS adds an encryption layer beneath HTTP, encrypting data before transmission so captured data stays unreadable, and verifying the server's identity.
- Draw the conclusion: the login and payment pages must use HTTPS; the browsing page could run on HTTP, but whole-site HTTPS is now the norm and also protects member privacy.
- Answer: The member login page and the online payment page must use HTTPS because they transmit passwords, card numbers and other sensitive data; HTTPS adds encryption and identity verification to HTTP, preventing interception or tampering in transit. Plain HTTP suits only public content that needs no confidentiality, such as the browsing page; for security and user confidence, the whole site should adopt HTTPS.
6Common mistakes Mistakes
7Quick check Quick check
Q1Which is a valid IPv4 address: 192.168.1.1 or 300.12.5.1?
Q2After a web address is typed into the browser, what role does DNS play?
Q3What guarantee does TCP provide on top of IP?
Q4Which two protocols mainly handle sending and receiving email?
Q5Why must online payment use HTTPS instead of HTTP?
8Recap Recap
- Protocols are the common rules of network communication; the internet is built on the TCP/IP suite.
- IP handles addressing and delivery, TCP handles reliability and order — IP manages the route, TCP manages the quality.
- DNS resolves domain names into IP addresses, the translator between web addresses and numbers.
- HTTP sends in the clear while HTTPS adds encryption and verification; use HTTPS for anything involving passwords or payment.
- Email sends and relays with SMTP and downloads with POP; FTP handles uploading and downloading files.