Just an idea:
I think that lesson 6 kind of stumbles a bit. We’ve been working in the internet simulator so far, we’ve built a network, we have data flowing across the network in packets, we can handle packets that are lost or out of order, and we can even deal with ip address changes. But when we get to http, the part that most people consider “the internet”, we watch a video and answer questions.
It would be wonderful if we could add just one more level up to the internet simulator. The last version adds dns servers. If (even in that same level) there were http servers, it would help show off the layers that we end up discussing. It could be something simple like the dns server, each http server responds to a GET request with some text. Students could be asked to get the “IP” address of the server from their DNS then get the answer to some question from the http server. It could even be a vocabulary server that responds with definitions for words requested.
That way students could see the answer to what happens when they type a url into the browser and press enter as was posed way back in lesson 2.1.
Hi @dahlem_brian,
Thanks for your feedback about the lesson! Keep ‘em comin’ 
I’m digging up this old post because I finally had time to think this through and implement a solution: The students are web browsers and web servers. I have another web page that works along-side the internet simulator to facilitate both the server and client roles that the students take on.
As an instructor you create a WWW session on the ActiveBits website ( bits.mycode.run/manage ) then give students the direct url or join code for bits.mycode.run . Students join up and enter the hostname from code.org’s internet simulator. You then press a button and they are given files to serve and an html page with “fragments” that they need to request.
Here is a lesson plan and explanation of the activity.
Here is my presentation for the activity. I use Nearpod so the presentation includes some Nearpod activities for the warmup question and videos. Feel free to copy and modify as you see fit.
Do note, this is being run on a free server so it may need to spin up when first accessed. Once a session is created, it should stay up as long as someone is connected to the session.