The Internet & Networking

History of the Internet

• J.C.R. Licklider / “Intergalactic Computer Network” — psychologist and DARPA/IPTO director; his August 1962 memos to colleagues described an “Intergalactic Computer Network” of interconnected computers sharing information — the conceptual forerunner of the internet; he also funded early time-sharing research and hired the people who built ARPANET.
• Leonard Kleinrock — MIT researcher whose 1961 master’s thesis applied queuing theory to message switching, laying mathematical foundations for packet switching; later supervised the UCLA node that sent ARPANET’s first message.
• Donald Davies — British NPL researcher who coined the term “packet switching” independently of Baran in 1965-1966 and built the NPL Data Communications Network, one of the first packet-switched networks.
• ARPANET (1969) — the precursor network funded by DARPA; first message sent October 29, 1969, from UCLA to SRI; the system crashed after two characters (“lo”), making the first transmitted text unintentionally “lo.”
• Packet switching — the fundamental architectural concept underlying the internet, developed independently by Paul Baran (RAND, early 1960s) and Donald Davies (NPL, UK); data is broken into packets routed independently and reassembled at the destination.
• NCP to TCP/IP — ARPANET originally used the Network Control Program; Vint Cerf and Bob Kahn published the TCP/IP specification in 1974; the ARPANET switched to TCP/IP on January 1, 1983, known as Flag Day.
• Ray Tomlinson / email and the @ sign — BBN engineer who in 1971 wrote the first program to send messages between different computers over ARPANET (SNDMSG + CPYNET on the TENEX OS); chose the @ symbol to separate the user name from the host machine name.
• Elizabeth Feinler / NIC and HOSTS.TXT — ran the Network Information Center at SRI-NIC; maintained the HOSTS.TXT file mapping hostnames to addresses before DNS; also coined the first TLD conventions (.gov, .edu, .com, .mil, .org, .net).
• NSFNet (1986) — the National Science Foundation network that replaced ARPANET as the backbone of US academic networking; decommissioned 1990 as commercial internet providers took over.
• ARPANET decommissioning — the original ARPANET was shut down in 1990; commercial and academic networks had already taken over its function.
• World Wide Web (1989-1991) — invented by Tim Berners-Lee at CERN; proposal submitted March 1989; first website (info.cern.ch) went live December 1990; public access began August 1991. Distinct from the internet: the Web is an application running on top of the internet.
• Netscape Navigator (1994) — commercial successor to Mosaic; dominated early web use; went public in a landmark 1995 IPO; introduced the cookie and early JavaScript (co-created by Brendan Eich in 10 days in 1995).
• Brendan Eich — Netscape engineer who created JavaScript in 1995 in approximately 10 days; later co-founded Mozilla and the Brave browser; the language was originally named Mocha, then LiveScript.
• Dot-com boom and bust — roughly 1995-2001; massive speculative investment in internet companies; NASDAQ peaked in March 2000 and crashed ~78% by 2002.
• Web 2.0 (~2004-2010) — term popularized by Tim O’Reilly; characterized by user-generated content, social networking, AJAX-driven dynamic pages, and platforms like Wikipedia, YouTube, Facebook, and Twitter.
• Paul Baran / RAND distributed communications — engineer at RAND Corporation who in 1964 published “On Distributed Communications,” proposing a survivable, decentralized network that could route around destroyed nodes; his work was conducted independently of Davies and was initially dismissed by AT&T before influencing ARPANET.
• ARPANET first message — sent October 29, 1969, by Charley Kline at UCLA to Bill Duvall at SRI; intended to transmit “login” but the system crashed after two letters, making “lo” the first internet message.
• Robert Taylor — DARPA/IPTO director who funded and launched the ARPANET project in 1966-1968; later led Xerox PARC’s computer science lab and recruited the team that built Ethernet and the Alto.
• RFC 1 — “Host Software,” authored by Steve Crocker on April 7, 1969; the first RFC in the series that would eventually document all internet standards.
• Internet “Flag Day” (January 1, 1983) — the date the ARPANET officially switched from NCP to TCP/IP; all hosts had to cut over simultaneously, hence the name.
• Mosaic (1993) — first graphical browser to display images inline with text, developed at NCSA (National Center for Supercomputing Applications) by Marc Andreessen and Eric Bina; ran on Unix, Windows, and Mac; free to download; credited with triggering the web’s mass adoption.
• First commercial ISPs — The World (1989) and PSINet/UUNET (1990) were among the first commercial ISPs offering public internet access in the United States.
• Mobile era — the iPhone (2007) and Android ecosystem shifted internet access to mobile; by the mid-2010s mobile traffic exceeded desktop globally.
• Broadband displacement — dial-up (56 Kbps peak) was largely displaced by DSL and cable broadband in the 2000s; fiber (FTTH) and 4G/5G mobile broadband followed.

How the Internet Works

Packet Switching and Routing

• Packet — a unit of data transmitted over a network; contains a header (addressing/control info) and a payload (data). IP packets typically up to 1,500 bytes (MTU for Ethernet).
• Router — a device that forwards packets between networks by inspecting IP destination addresses and consulting routing tables; operates at OSI Layer 3 (Network).
• Switch — a Layer 2 (Data Link) device that forwards frames within a LAN using MAC addresses; unlike a hub, it sends frames only to the intended port.
• Hub — a Layer 1 device that broadcasts all incoming data to every connected port; largely obsolete, replaced by switches.
• MAC address (Media Access Control) — a 48-bit hardware address burned into a network interface card; written as six colon- or hyphen-separated hex pairs (e.g., 00:1A:2B:3C:4D:5E); uniquely identifies a device on a local network; the first three octets identify the manufacturer (OUI).
• ARP (Address Resolution Protocol) — maps IP addresses to MAC addresses within a local network; a device broadcasts “who has IP X?” and the owner replies with its MAC address.
• Routing protocols — BGP (Border Gateway Protocol) is the inter-domain (internet-wide) routing protocol; OSPF and IS-IS are common interior routing protocols within a network.
• BGP (Border Gateway Protocol) — the “routing protocol of the internet”; exchanges reachability information between Autonomous Systems; a path-vector protocol; misconfigurations (“BGP hijacks”) can redirect global internet traffic.
• Autonomous System (AS) — a network or group of networks under a single administrative domain; identified by an ASN; BGP routes between ASes.
• IXP (Internet Exchange Point) — a physical facility where ISPs and networks exchange traffic; reduces cost and latency by enabling direct peering.
• Bandwidth vs. latency — bandwidth is the maximum data throughput of a link (bits per second); latency is the time for a single packet to travel from source to destination (milliseconds); high bandwidth does not imply low latency.
• Client-server model — the dominant internet architecture; clients (browsers, apps) request resources; servers process requests and return responses; contrasts with peer-to-peer (P2P) where nodes act as both.
• Peer-to-peer (P2P) — a decentralized architecture where each node can act as both client and server; used by BitTorrent, early Napster/Kazaa, and blockchain networks; distributes load but complicates moderation and security.
• Internet backbone — high-capacity fiber-optic transmission lines and routers operated by Tier-1 ISPs (AT&T, Lumen/CenturyLink, NTT, etc.) that interconnect the entire internet; Tier-1 providers peer with each other without payment.
• Submarine cables — undersea fiber-optic cables that carry ~95-99% of international internet traffic; subject to damage by ship anchors and earthquakes (e.g., 2006 Taiwan earthquake disrupted Asian internet); landing stations are critical infrastructure.

IP Addressing

• IPv4 — 32-bit addresses; ~4.3 billion total (2^32); written in dotted-decimal notation (e.g., 192.168.1.1); effectively exhausted by 2011 (IANA) / 2019 (RIPE NCC for Europe).
• IPv6 — 128-bit addresses; 2^128 (~3.4 × 10^38); written in colon-separated hex groups (e.g., 2001:0db8::1); introduced to address IPv4 exhaustion.
• Private/reserved ranges — 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 are private (RFC 1918); not routable on the public internet. NAT allows many devices to share one public IP.
• NAT (Network Address Translation) — maps private IP addresses to a public IP at a gateway; temporarily delayed IPv6 adoption by extending IPv4 usability.
• CIDR (Classless Inter-Domain Routing) — notation indicating the network prefix length (e.g., /24 = 256 addresses); replaced the older class-based system (Class A/B/C).
• Subnet mask — a 32-bit number (e.g., 255.255.255.0) that divides an IP address into network and host portions; CIDR /24 is equivalent to 255.255.255.0.
• Loopback — 127.0.0.1 (IPv4) / ::1 (IPv6); always refers to the local machine.
• Broadcast address — in a subnet, the highest address (all host bits set to 1, e.g., 192.168.1.255 in a /24); packets sent here are delivered to all hosts on the subnet.
• TTL (IP Time to Live) — an 8-bit field in the IP header decremented by each router; when it reaches zero, the packet is dropped and an ICMP “Time Exceeded” message is returned; prevents infinite routing loops.
• Cloud computing — delivering computing resources (servers, storage, databases, software) over the internet on demand; IaaS (Infrastructure as a Service, e.g., AWS EC2) provides raw virtual machines; PaaS (Platform as a Service, e.g., Heroku) provides a deployment platform; SaaS (Software as a Service, e.g., Gmail, Salesforce) provides finished applications.
• Data center — a facility housing thousands of servers, networking equipment, and storage; organized into racks and rows; requires massive power, cooling, and redundancy infrastructure; hyperscale data centers (Google, Amazon, Meta) span millions of square feet.

DNS

• DNS (Domain Name System) — translates human-readable domain names into IP addresses; designed by Paul Mockapetris and Jon Postel (1983 RFC 882/883).
• Hierarchy — root zone → TLDs (.com, .org, .uk) → second-level domains (example.com) → subdomains (www.example.com).
• Root servers — 13 named root server clusters (A through M), operated by 12 organizations; widely distributed via anycast; the authoritative source for TLD delegation.
• Recursive resolver — the DNS server queried by your device; queries authoritative servers on your behalf and caches results. Typically provided by your ISP or a public resolver (8.8.8.8 Google, 1.1.1.1 Cloudflare).
• TTL (Time to Live) — controls how long a DNS record is cached; lower TTL means faster propagation of changes.
• Record types — A (IPv4 address), AAAA (IPv6), CNAME (alias to another name), MX (mail server), NS (name server), TXT (arbitrary text, used for SPF/DKIM), SOA (zone authority).
• DNSSEC — DNS Security Extensions; adds cryptographic signatures to DNS responses to prevent spoofing/cache poisoning.
• DoH (DNS over HTTPS) / DoT (DNS over TLS) — protocols that encrypt DNS queries to prevent eavesdropping or tampering by on-path observers; DoH uses port 443 and is harder for networks to block.
• gTLDs and ccTLDs — generic top-level domains (.com, .org, .net) vs. country-code TLDs (.uk, .jp, .de); ICANN dramatically expanded gTLDs from 2012 onward (e.g., .london, .bank).

The OSI and TCP/IP Models

OSI Layer	Name	TCP/IP Layer	Key Protocols/Examples
7	Application	Application	HTTP, HTTPS, SMTP, FTP, DNS, SSH
6	Presentation	Application	TLS/SSL, MIME encoding
5	Session	Application	TLS handshake, session management
4	Transport	Transport	TCP, UDP
3	Network	Internet	IP, ICMP, BGP
2	Data Link	Network Access	Ethernet, Wi-Fi (802.11), ARP
1	Physical	Network Access	cables, fiber, radio frequencies

• OSI model — 7-layer conceptual framework for network communication; developed by ISO in the late 1970s. Useful for understanding and troubleshooting, but real protocols do not map cleanly to it.
• TCP/IP model — 4-layer practical model (Application, Transport, Internet, Network Access) that describes actual internet protocols.
• Encapsulation — the process by which each OSI/TCP-IP layer wraps the layer above’s data in its own header (and sometimes trailer); at the receiver, each layer strips its header and passes data up.
• MTU (Maximum Transmission Unit) — the largest packet/frame a link will carry; standard Ethernet MTU is 1,500 bytes; exceeding it causes IP fragmentation or a “packet too big” ICMP error (used in Path MTU Discovery).

Core Protocols

TCP and UDP

• TCP (Transmission Control Protocol) — connection-oriented; guarantees delivery and ordering via a three-way handshake (SYN, SYN-ACK, ACK), sequence numbers, and acknowledgements. Higher overhead.
• UDP (User Datagram Protocol) — connectionless; no delivery guarantee; lower overhead; used for real-time applications (video streaming, VoIP, online gaming, DNS lookups).
• Three-way handshake — TCP connection establishment: client sends SYN → server replies SYN-ACK → client sends ACK.
• Port — a 16-bit number identifying a specific process/service on a host; 0-1023 are well-known ports.

Common Ports

Port	Protocol	Service
20/21	TCP	FTP (data/control)
22	TCP	SSH
25	TCP	SMTP
53	TCP/UDP	DNS
80	TCP	HTTP
110	TCP	POP3
143	TCP	IMAP
443	TCP	HTTPS
465/587	TCP	SMTP (TLS)
3306	TCP	MySQL
5432	TCP	PostgreSQL

HTTP and HTTPS

• HTTP (HyperText Transfer Protocol) — the application-layer protocol of the web; stateless; client sends a request, server sends a response.
• HTTP methods — GET (retrieve), POST (submit data), PUT (replace), PATCH (partial update), DELETE (remove), HEAD (headers only), OPTIONS (capabilities).
• HTTP status codes — 1xx informational, 2xx success (200 OK, 201 Created, 204 No Content), 3xx redirection (301 Moved Permanently, 302 Found), 4xx client error (400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests), 5xx server error (500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable).
• HTTP/1.1 (1997) — added persistent connections, chunked transfer encoding, host headers enabling virtual hosting.
• HTTP/2 (2015) — binary framing, multiplexing (multiple requests over one connection), header compression (HPACK); significantly reduces latency.
• HTTP/3 (2022) — runs over QUIC (Quick UDP Internet Connections) instead of TCP; QUIC is built on UDP, provides built-in TLS 1.3, and eliminates TCP’s head-of-line blocking.
• HTTPS — HTTP over TLS; encrypts traffic; requires a certificate from a Certificate Authority; standard for all modern sites.

Other Key Protocols

• SMTP — Simple Mail Transfer Protocol; used for sending email between servers; commonly on ports 25 (server-to-server), 587 (submission with authentication).
• IMAP / POP3 — protocols for reading email from a server; IMAP (port 143/993) syncs messages across devices; POP3 (port 110/995) downloads and typically deletes from server.
• FTP — File Transfer Protocol; plain-text, largely replaced by SFTP (FTP over SSH) or FTPS (FTP with TLS) for security.
• SSH (Secure Shell) — encrypted protocol for remote login and command execution; port 22; uses public-key cryptography for authentication.
• DHCP — Dynamic Host Configuration Protocol; automatically assigns IP addresses, subnet masks, gateways, and DNS servers to devices on a network.
• ICMP — Internet Control Message Protocol; used for network diagnostics (ping = ICMP Echo Request/Reply; traceroute uses ICMP or UDP TTL expiry).
• QUIC — a transport protocol developed by Google, standardized in RFC 9000 (2021); runs over UDP; provides TLS 1.3 encryption, stream multiplexing, and connection migration; the basis for HTTP/3.
• NTP (Network Time Protocol) — synchronizes clocks across internet hosts; port 123/UDP; crucial for TLS certificate validation and distributed systems; designed by David Mills.
• SNMP (Simple Network Management Protocol) — used to monitor and manage network devices (routers, switches, servers); operates on port 161/UDP.

The World Wide Web

• Internet vs. Web — the internet is the global network infrastructure; the web is one application running on it (others: email, VoIP, torrents, SSH).
• URL (Uniform Resource Locator) — structure: scheme://host:port/path?query#fragment. The host is resolved via DNS.
• HTML (HyperText Markup Language) — the markup language describing web page structure; current standard is HTML5 (2014, WHATWG Living Standard).
• CSS (Cascading Style Sheets) — describes the presentation/layout of HTML documents; handles fonts, colors, layout (Flexbox, Grid), and responsive design.
• JavaScript — the scripting language of the web; runs in browsers; enables dynamic content, DOM manipulation, and modern single-page applications; V8 (Google) and SpiderMonkey (Mozilla) are major JS engines.
• Browser — renders HTML/CSS/JS; major engines: Blink (Chrome, Edge, Opera), Gecko (Firefox), WebKit (Safari).
• Cookie — a small piece of data stored by a browser and sent with subsequent requests to the same origin; used for sessions, authentication, and tracking. Set via Set-Cookie response header.
• REST — Representational State Transfer; an architectural style for APIs using HTTP verbs, stateless requests, and resource-oriented URLs; coined by Roy Fielding (2000 dissertation).
• WebSocket — a protocol providing full-duplex communication over a single TCP connection; initiated by an HTTP upgrade; used for real-time apps (chat, live data).
• CDN (Content Delivery Network) — geographically distributed servers that cache and serve content closer to users; reduces latency and origin server load.
• DOM (Document Object Model) — the in-memory tree representation of a parsed HTML/XML document; JavaScript manipulates the DOM to change page content dynamically without a full reload.
• AJAX (Asynchronous JavaScript and XML) — a technique using XMLHttpRequest (or the modern Fetch API) to send/receive data in the background without reloading the page; coined by Jesse James Garrett (2005); foundational to Web 2.0.
• URI vs. URL vs. URN — a URI (Uniform Resource Identifier) is the general concept; a URL specifies location (https://example.com); a URN specifies a persistent name (urn:isbn:…); all URLs are URIs.
• PageRank — the algorithm developed by Larry Page and Sergey Brin at Stanford (1998) that scores web pages by the number and quality of inbound links; the foundation of Google’s search engine.
• Search engine — indexes the web via crawlers; major milestones: AltaVista (1995), Yahoo (1995), Google (1998); Google dominates with ~90% market share as of the mid-2020s.
• Web 3.0 / Semantic Web — Berners-Lee’s vision of machine-readable, linked data across the web; partially realized through schema.org markup; the term was later co-opted by blockchain/decentralization advocates for an unrelated concept.
• Caching — storing copies of responses to serve future identical requests faster; occurs at multiple levels: browser cache, CDN edge, reverse proxy (e.g., Varnish), and application; controlled by HTTP headers (Cache-Control, ETag, Last-Modified).

TLS and Encryption

• TLS (Transport Layer Security) — the protocol providing encryption, authentication, and integrity for HTTPS and other protocols; TLS 1.3 (2018) is current; SSL is the deprecated predecessor.
• TLS handshake — client and server negotiate cipher suites, authenticate the server (via certificate), and establish a shared session key using asymmetric cryptography (key exchange), then switch to symmetric encryption for data.
• Certificate Authority (CA) — a trusted third party that issues digital certificates binding a public key to a domain/organization. Browsers ship with a list of trusted root CAs.
• X.509 — the standard format for public-key certificates used in TLS.
• Let’s Encrypt — a free, automated, open CA launched 2016 by ISRG; dramatically increased HTTPS adoption.
• Symmetric encryption — the same key encrypts and decrypts; fast; used for bulk data transfer in TLS. Examples: AES-256-GCM.
• Asymmetric encryption — mathematically linked key pair; the public key encrypts (or verifies), private key decrypts (or signs); used in TLS key exchange and signatures. Examples: RSA, ECDH.
• HSTS (HTTP Strict Transport Security) — a header instructing browsers to only connect via HTTPS for a specified duration; prevents downgrade attacks.
• Public-key infrastructure (PKI) — the system of CAs, certificates, and policies that underpins trust on the internet; relies on a hierarchy of root CAs pre-installed in browsers and operating systems.
• Forward secrecy (PFS) — a TLS property ensuring that compromise of a long-term private key does not expose past session keys; achieved via ephemeral Diffie-Hellman key exchange (ECDHE).
• Diffie-Hellman key exchange — a 1976 method (Whitfield Diffie and Martin Hellman) allowing two parties to establish a shared secret over a public channel without prior shared knowledge; foundational to TLS and modern cryptography.

Security Concepts and Attacks

• Firewall — hardware or software that filters network traffic based on rules (IP, port, protocol); stateful firewalls track connection state.
• VPN (Virtual Private Network) — encrypts traffic and tunnels it through a server, masking the user’s IP and protecting data on untrusted networks.
• DDoS (Distributed Denial of Service) — overwhelming a server/network with traffic from many sources to make it unavailable.
• SQL injection — inserting malicious SQL into input fields to manipulate a database; one of the most common and dangerous web vulnerabilities.
• XSS (Cross-Site Scripting) — injecting malicious scripts into web pages viewed by other users; exploits the browser’s trust in the site.
• CSRF (Cross-Site Request Forgery) — tricks a user’s browser into making unwanted requests to a site where they are authenticated.
• Phishing — social engineering via fake emails or websites to steal credentials or install malware.
• Man-in-the-Middle (MITM) — attacker intercepts communication between two parties; HTTPS/TLS mitigates this.
• Certificate pinning — hard-coding expected certificate/public key in an application to prevent MITM even with rogue CAs.
• Zero-day exploit — a vulnerability unknown to the software vendor; attackers can exploit it before a patch is available; high-value zero-days are sold for millions on gray and black markets.
• Ransomware — malware that encrypts a victim’s files and demands payment (typically cryptocurrency) for the decryption key; high-profile attacks include WannaCry (2017, exploited EternalBlue/NSA leak) and NotPetya (2017).
• Botnet — a network of compromised machines (bots/zombies) controlled by an attacker (botmaster) via a command-and-control server; used for DDoS, spam, and credential stuffing.
• Social engineering — manipulating people rather than systems to gain unauthorized access; phishing, vishing (voice), and pretexting are subtypes; the human is consistently the weakest link.
• Zero Trust architecture — a security model that eliminates the concept of a trusted internal network; every request must be authenticated and authorized regardless of origin; popularized by Google’s BeyondCorp.
• verify: The exact year HTTPS usage crossed 50% of web traffic globally (often cited as ~2017 per Firefox telemetry); confirm precise figure.

Key Organizations and Standards

• IETF (Internet Engineering Task Force) — develops and promotes internet standards via Request for Comments (RFC) documents; open participation; no formal membership. Published TCP/IP, HTTP, TLS, DNS, and most core internet protocols.
• RFC (Request for Comments) — the document series for internet standards and informational documents; numbered sequentially; e.g., RFC 791 (IP), RFC 793 (TCP), RFC 2616 (HTTP/1.1), RFC 7540 (HTTP/2).
• W3C (World Wide Web Consortium) — founded by Tim Berners-Lee (1994); develops web standards: HTML, CSS, XML, SVG, accessibility guidelines (WCAG).
• ICANN (Internet Corporation for Assigned Names and Numbers) — coordinates the DNS root, IP address allocation, and protocol parameters; a private non-profit under US oversight until 2016.
• IANA (Internet Assigned Numbers Authority) — function operated by ICANN; manages IP address allocation (to RIRs), AS numbers, the DNS root, and protocol port/number registries.
• RIRs (Regional Internet Registries) — allocate IP addresses within regions: ARIN (North America), RIPE NCC (Europe/Middle East), APNIC (Asia-Pacific), LACNIC (Latin America), AFRINIC (Africa).
• IEEE 802 — IEEE standards for local area networks; 802.3 (Ethernet), 802.11 (Wi-Fi), 802.1Q (VLANs).
• WHATWG — Web Hypertext Application Technology Working Group; maintains the HTML Living Standard; a rival to W3C that now effectively controls the HTML spec.
• Net neutrality — the principle that ISPs must treat all internet traffic equally, without throttling, blocking, or paid prioritization; the FCC’s 2015 Open Internet Order (Title II classification) was repealed in 2017 and debated continuously since; the EU’s net neutrality rules (2016) remain in force.
• Section 230 — a provision of the US Communications Decency Act (1996) that shields internet platforms from liability for user-generated content; foundational to the modern web; frequently challenged legislatively.
• GDPR — the EU’s General Data Protection Regulation (effective May 2018); sets strict rules for collection, processing, and transfer of personal data; introduced the right to erasure and data portability; fines up to 4% of global annual revenue.
• verify: Whether ICANN’s transition away from US government oversight (the IANA stewardship transition) formally completed in October 2016, and the exact nature of the multistakeholder community that assumed control.

Key Figures

• Vint Cerf and Bob Kahn — co-designed TCP/IP (1974); widely called “Fathers of the Internet.”
• Tim Berners-Lee — invented the World Wide Web (1989-1991); founded the W3C; knighted 2004.
• Paul Baran — developed packet-switching theory at RAND in the early 1960s.
• Jon Postel — edited hundreds of foundational RFCs; managed IANA for decades; wrote the “robustness principle” (Postel’s Law): “be conservative in what you send, liberal in what you accept.”
• Marc Andreessen — co-created Mosaic (1993), co-founded Netscape (1994).
• Paul Mockapetris — designed DNS (RFC 882/883, 1983).
• Roy Fielding — defined REST architecture in his 2000 PhD dissertation; co-author of HTTP/1.1.
• Larry Roberts — chief scientist who led ARPANET development at DARPA.
• Douglas Engelbart — SRI researcher who demonstrated hypertext, video conferencing, collaborative editing, and the computer mouse in the “Mother of All Demos” (December 9, 1968); directly influenced Berners-Lee’s hypertext thinking.
• Claude Shannon — mathematician whose 1948 paper “A Mathematical Theory of Communication” founded information theory; defined the bit, channel capacity, and entropy; foundational to all digital communications.
• Whitfield Diffie and Martin Hellman — published public-key cryptography concepts in “New Directions in Cryptography” (1976); Diffie-Hellman key exchange enabled secure communication without pre-shared keys; Turing Award 2015.
• Radia Perlman — invented the Spanning Tree Protocol (STP, 1985), which prevents loops in Ethernet networks and made large LAN architectures feasible; called the “Mother of the Internet” (though she disputes the title).
• Stewart Brand — counterculture figure and editor of the Whole Earth Catalog; early internet culture influencer; co-founded the WELL (1985), an influential early online community; coined the phrase “information wants to be free.”
• Aaron Swartz — internet prodigy who co-authored RSS 1.0 at age 14 and co-created Reddit’s early codebase; co-founded Demand Progress; arrested (2011) for bulk-downloading JSTOR articles; his prosecution and death (2013) became a flashpoint in open-access debates.
• Edward Snowden — NSA contractor who in 2013 disclosed mass surveillance programs (PRISM, XKeyscore) revealing bulk collection of internet metadata and content; spurred widespread adoption of end-to-end encryption and HTTPS.
• verify: Whether Tim Berners-Lee’s original 1989 proposal was titled “Information Management: A Proposal” and whether his supervisor Mike Sendall’s annotation “Vague but exciting” is accurately quoted.