For Today: Please do some very basic research so that you can construct a basic 'proposal' for you protocol/packet project:
Design a graphical presentation of some sort that shows the process where packets are created, sent to a server on the interweb and then new packets are created by an internet server and returned back to your computer.
Each layer of a sample packet should be clearly represented. You do not need to show the guts of each and every packet sent from your computer to your home modem/router to your ISP, through a bunch of routers and received by the internet server and then sent by that server through routers to your ISP to your home modem/router and then received by your computer should suffice <gulp>.
To the extent possible, each step should show the actual IP Addresses, Port Numbers and Mac ID/Physical addresses for as many routers/computers as possible (it will take some research to determine which information you can easily obtain, which information will take some work and which information is so difficult to obtain that you probably wont' be able to get it)
If you start this project at the last minute, you'll be 
I hope that is obvious.
Plan ahead, take pride in your work, come visit me with any questions
Please, Please, Please do us BOTH a favor and don't turn in a flaming pile of 
═══════════════════════════
TOOLS
═══════════════════════════
PORTS
Ports 0 - 1023 are used for well-known apps/processes.
Ports 1024- 49151 are reserved for user server applications (I don't know if all of those are taken though)
Ports above 49151 are NOT reserved and available (I assume?) to whoever wants to use them. Why is this typically NOT a problem?
Take a gander at the Wikipedia page for common ports. Just for giggles go and see what port is assigned to the video game DOOM.
TRACERT
Here is a sample screen courtesy of our frenemies @ chatgpt:

traceRT (or just plain lowercase: tracert) is a tracert program that should allow you to trace a good portion of your path. See if you can try it now (you'll need to get into the cmd window first though - try Ctrl + Alt + T)
WHOIS
WHOIS lets you type in an IP address and it will tell you who is assigned that address. Try typing that into your browser with an IP Address.
WIRESHARK
There is a tool called WIRESHARK that verges on being a hacking tool but it is widely available and very helpful. I checked with our district tech admin and he is fine with us using WIRESHARK since virtually all communication is encrypted these days.
That is by way of saying it will show the addresses and such but all the personal info and application layer stuff will be encrypted.
Once again, this is a very, very deep dive technically speaking. I quickly got bored with WIRESHARK and frankly just didn't much care to dive further. Having said that I had a couple of students the last time we did that that dove in whole hog and did an AWESOME job.
It is also VERY VERY technical. It will tell you most if not all of what you want to know of every connection that you make between your computer and the server on the web that is the final destination for your communications for that application.