Communication Protocols, World Wide Web and the Internet

The Internet, the World Wide Web, and Network Architectures

The Internet is the global system of interconnected computer networks—the physical cabling, satellites, routers, and servers—along with the standardised TCP/IP protocols that govern how data moves between them. Think of the World Wide Web as just one service running across that physical infrastructure: it is a massive collection of web pages, documents, and media linked together by hyperlinks and served to your browser. Services like email, file transfer, and streaming run on the Internet without being part of the Web.

Network Classifications and Topologies

Networks are categorised by their geographical scope:

• Local Area Network (LAN): Spans a small area, like your house, a single office, or your school computer room. The organisation normally owns all the switches and cables itself, delivering fast data speeds.
• Wide Area Network (WAN): Spans large geographical regions, cities, or continents, using leased telecommunications circuits and public infrastructure. The Internet is the largest example of a WAN.
• Personal Area Network (PAN): Centred around an individual over a range of a few metres, such as connecting a smartphone to wireless earbuds using Bluetooth.

Devices arrange themselves within these networks using specific physical and logical layouts known as topologies:

• Star topology: Every node links directly to a central switch or hub. If a single cable breaks, only that connected device loses access, though the central switch remains a single point of failure.
• Bus topology: All devices tap into a single backbone cable terminated at each end. It uses minimal cabling but a break in the central line disables the entire network.
• Mesh topology: Devices maintain redundant connections to multiple neighbours. While costly and complex to cable, mesh layouts provide alternate pathways if a link fails. The core backbone of the Internet operates on a mesh design.

Client-Server versus Peer-to-Peer

When you use a client-server architecture, a central machine handles all the heavy lifting: storing files, managing database access, and responding whenever client software, such as your web browser, asks for a resource. This architecture centralises backups, security policies, and access rights, but the server acts as a potential bottleneck and single point of failure.

By contrast, in a peer-to-peer (P2P) network, we drop the idea of a central coordinator completely: every connected laptop or phone functions as both a client and a server, sharing files and CPU capacity directly. While inexpensive and resilient against single-node failures, peer-to-peer arrangements make centralised security and backups far more difficult to administer.

Layered Architectures: OSI and TCP/IP

A communication protocol represents a formal set of rules establishing how devices format, transmit, and check data across networks. Protocols ensure hardware from completely different manufacturers can exchange data without conflict.

Modern networking divides these tasks into independent layers. When sending information, data moves downward through the stack on the sender's device, traverses physical network media, and travels upward through the stack on the receiving machine.

Comparing OSI and TCP/IP

The theoretical OSI model standardises network functions across seven layers. You can recall them from top to bottom using the phrase All People Seem To Need Data Processing:

1. Application: Provides the direct interface to user software.
2. Presentation: Handles data formatting, character encoding, compression, and encryption.
3. Session: Establishes, maintains, and terminates communication dialogues between applications.
4. Transport: Coordinates segmentation, flow control, sequencing, and end-to-end reliability.
5. Network: Manages logical device addressing and finds transmission paths across networks.
6. Data Link: Packages bits into frames and directs node-to-node delivery across a local physical medium.
7. Physical: Transmits raw binary streams across physical copper cables, fibre-optic strands, or radio waves.

The TCP/IP suite condenses these into a four-layer framework designed for the Internet:

Routing between separate networks happens at the Internet layer using IP addresses, while frame switching within a local network happens at the Network Access layer using MAC addresses.

Addressing, Packets, and Name Resolution

Every network interaction relies on identifying endpoints and packaging data so routers can direct traffic efficiently.

Logical and Physical Addressing

• MAC address: Think of this as the physical fingerprint burned into a network card at the factory. It is a 48-bit hardware address written out as six pairs of hex digits (like 00:1A:2B:3C:4D:5E), and local switches use it to push frames between machines on the same physical link.
• IP address: A logical identifier assigned by software or network infrastructure, operating at the Internet layer to route packets across separate networks.
• IPv4: Uses 32 bits, expressed as four decimal numbers from 0 to 255 separated by full stops (e.g., 192.168.1.10), yielding roughly 4.3 billion addresses.
• IPv6: Because we ran out of IPv4 numbers, IPv6 expands address space to 128 bits, writing them as eight chunks of hexadecimal digits separated by colons (like 2001:0db8:85a3:0000:0000:8a2e:0370:7334). That gives us billions of addresses for every smart device and IoT gadget on earth.
• Static versus Dynamic: A static IP address remains fixed permanently and suits servers needing predictable endpoints. A dynamic IP address is leased temporarily from a pool by a DHCP server when a device joins a network.
• Public versus Private: Private IP addresses (such as 192.168.x.x) operate within home or school LANs. To keep private traffic working smoothly, your home router runs Network Address Translation (NAT), swapping your laptop's local private address for the router's single public IP whenever data heads out to the wider Internet.

Packet Structure and Packet Switching

A packet is a manageable unit of data produced when a message is segmented for transmission. A packet consists of:

• Header: Stores metadata including source IP, destination IP, packet sequence number, protocol type, and Time to Live (TTL), which decrements at each router hop to prevent lost packets circulating indefinitely.
• Payload: The actual application data being transported.
• Trailer: Sits at the tail end with an error-detecting checksum, like a cyclic redundancy check (CRC), so the receiving machine can tell if any bits flipped during transit.

In packet switching, messages break into independent packets that can travel across different network routes before reassembly at their final destination. This differs from traditional circuit switching, which reserves an exclusive, dedicated physical path for the entire duration of a communication.

Transport and Application Protocols

Different applications have different transmission needs. Web browsing demands exact data integrity, while real-time voice calls prioritise low delay.

TCP versus UDP

The transport layer provides two contrasting protocols:

TCP establishes connections through a three-way handshake:

1. SYN: The client sends a synchronise segment containing an initial sequence number to the server.
2. SYN-ACK: The server responds with an acknowledgement segment confirming the request and supplying its own synchronisation number.
3. ACK: The client sends a final acknowledgement confirming receipt. The connection is established and data transfer begins.

Application Protocol Directory

A port is a 16-bit numerical identifier in packet headers that directs incoming data to the correct application service on a host device:

Web Mechanics, Security, and Cloud Computing

The World Wide Web pairs application protocols with structured data documents, secured by cryptographic handshakes and powered by scalable cloud platforms.

URLs and Web Protocols

Every web resource needs an unambiguous address so your browser knows where to look; that is what the Uniform Resource Locator (URL) gives you:

• In https://www.example.ie:443/notes/topic1.html?id=7, https represents the scheme, www.example.ie is the domain name (.ie being the top-level domain), :443 specifies the server port, /notes/topic1.html identifies the file path on the server, and ?id=7 represents query parameters.
• Standard HTTP request methods include GET to retrieve a resource and POST to deliver form data or credentials securely within the request body.
• Because HTTP is stateless and does not retain memory of previous exchanges, servers issue cookies—small text files saved on the client machine—to preserve login states, tracking details, and user preferences between sessions.

HTTPS and Encryption Mechanics

Plain HTTP sends text out in the clear for anyone on the wire to see, which is why HTTPS wraps the connection in Transport Layer Security (TLS). This gives you confidentiality so eavesdroppers cannot read your traffic, integrity so nobody can tamper with packets along the way, and authentication so you know the server really is who it claims to be.

• Asymmetric encryption: Uses a mathematically linked key pair. To prove its identity, the server hands over a digital certificate signed by a recognised Certificate Authority (CA), which contains its public key. The private key remains secure on the server. The client verifies the certificate, then uses the public key to encrypt a temporary session key.
• Symmetric encryption: Both ends share one single secret key that encrypts and decrypts every message. It runs exceptionally fast, which is why HTTPS switches to symmetric encryption for the rest of your browsing session once the initial handshake wraps up.

Cloud Computing Models

Rather than buying and racking their own physical servers, companies rent computing power and storage over the Internet, paying only for the capacity they actually use:

• Infrastructure as a Service (IaaS): The cloud company gives you the bare bones—virtual machines, raw storage, and virtual networks—and leaves you to install, configure, and patch the operating system and software (Amazon Web Services EC2 is the classic example).
• Platform as a Service (PaaS): Providers manage hardware, virtualisation, operating systems, and developer runtimes. The customer supplies and deploys application code (e.g., Google App Engine).
• Software as a Service (SaaS): You simply log in and run finished software right in your web browser without worrying about servers or updates at all, like Google Docs or Microsoft 365.

Deployment strategies vary between public clouds (shared multi-tenant infrastructure), private clouds (dedicated solely to one enterprise for greater control), and hybrid clouds (combining private storage for sensitive records with public resources for fluctuating demand).

Network Hardware Reference

Hardware devices direct signals and enforce security boundaries across networks:

Societal, Ethical, Legal, and Emerging Trends

Ubiquitous networking creates important societal, environmental, and ethical challenges:

• Digital Divide: The socioeconomic gap separating individuals who have reliable high-speed broadband and digital devices from those who do not. This disparity restricts access to online education, remote employment opportunities, and civic services.
• Net Neutrality: This principle insists that Internet service providers must treat all web traffic exactly the same. An ISP cannot slow down competitors, block legal sites, or charge extra fees to speed up specific streaming services.
• Data Protection (GDPR): Legal frameworks establishing individual control over personal information, guaranteeing rights such as data access, rectification, and erasure, while requiring data processors to report breaches promptly.
• Environmental Footprint: Large-scale cloud data centres consume substantial electricity to power computing racks and cooling infrastructure. Hardware replacement cycles also generate significant electronic waste (e-waste).
• Internet of Things (IoT): We now have everyday physical objects fitted with sensors to read their environment and actuators to carry out physical tasks, talking to each other over the Internet without human help. Think of a smart thermostat reading the room temperature and turning on the radiator valve automatically. IoT devices drive the shift toward IPv6 addresses due to their sheer numbers, while edge computing handles processing on local devices to reduce latency and bandwidth use.

Key terms

The Internet

The global system of interconnected computer networks that communicate using the standardised TCP/IP protocol suite.

World Wide Web

An information service of hyperlinked multimedia documents and web pages hosted on servers and accessed using web browsers.

Communication Protocol

A formal set of rules and conventions governing how devices format, transmit, and receive data across a network.

Uniform Resource Locator (URL)

A standardised web address used to reference and locate a specific resource hosted on an Internet server.

Transmission Control Protocol (TCP)

A connection-oriented transport protocol that provides reliable, ordered, and error-checked delivery of packet streams using sequence numbers and acknowledgements.

Internet Protocol (IP)

The fundamental network layer protocol that encapsulates data into packets with logical source and destination addresses to handle routing across networks.

Domain Name System (DNS)

A distributed naming service that translates human-readable domain names into the numeric IP addresses computers require for routing.

Packet

A small formatted unit of data containing a header, payload, and trailer into which larger network messages are divided for transmission.

MAC Address

A unique, permanent 48-bit physical hardware identifier assigned to a network interface card by its manufacturer.

IP Address

A unique logical address assigned by software to identify a device on a network so packets can be routed to it.

HTTP

An unencrypted application layer request-response protocol running over port 80 used for transferring hypertext resources.

HTTPS

A secure application protocol running over port 443 that encrypts HTTP communications using TLS to ensure confidentiality and integrity.

Port

A 16-bit numerical identifier within a packet header indicating which application service or process should receive the data.

Bandwidth

The theoretical maximum volume of data that can transmit across a network connection in a given time, measured in bits per second.

Latency

The time delay incurred for a data packet to travel across a network from source to destination, measured in milliseconds.

Encryption

The mathematical process of encoding plaintext into unreadable ciphertext such that only authorised parties with the correct key can decrypt it.

Firewall

A hardware or software security system that monitors incoming and outgoing network traffic and filters packets according to security rules.

Router

A layer 3 networking device that inspects destination IP addresses to forward packets across different networks.

Network Switch

A layer 2 networking device that inspects MAC addresses to direct incoming frames exclusively to the intended recipient's physical port.

Gateway

A network node that connects and translates communications between systems operating on incompatible protocol suites.

Cloud Computing

The on-demand delivery of hosted computing resources such as servers, storage, databases, and software over the Internet on a pay-as-you-go model.

Internet of Things (IoT)

A global network of physical devices embedded with sensors, software, and network connectivity that autonomously collect and exchange data.