<i>&gt;In the interest of making the topic easier to comprehend, we will start with a fairly high-level overview, and then dive into each individual component as we go along. Our journey starts with a user called Alice. Alice owns a laptop, and wants to send e-mail to a person called Bob.  ... [wall of text...]</i><p>I understand the enthusiasm to spread knowledge but a wall of text like that isn&#x27;t going to be helpful for novices.  When technical people try to impart knowledge, the text they write usually suffers from the Curse of Knowledge[1].  For example,  &quot;DHCP&quot; and &quot;UDP&quot; is mentioned several times which is a level of detail that is not necessary for an introductory overview.<p>Instead, to explain how the internet works would require lots of diagrams, pictures, videos, etc. illustrating different scenarios.  E.g., sending SMTP is different from HTTP and both use DNS.  All these &quot;mental buckets&quot; (and many others) are difficult to separate for novices.  Instead of drilling into a timeline of bytes sent from Alice to Bob, new concepts can be taught as &quot;progressive layers&quot; of detail (with the timeline rewound each time.)  Answering the question of &quot;how the internet works&quot; is so open-ended that apparently, some tech interviewers like to use it for evaluating job candidates.<p>[1]<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Curse_of_knowledge" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Curse_of_knowledge</a>