this post was submitted on 01 Jan 2026
595 points (99.3% liked)
Microblog Memes
10095 readers
1511 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Once upon a time there were more protocols than just TCP/IP. You could have IPX/SPX, Baynes and others.
Hell. Even now with the introduction of Quic, it’s starting to change the use of TCP/IP, so having a general understanding of the layers in an abstracted manner let you map them to the different syntaxes that are out there. Kind of like programming languages.
We’ve also had UDP this whole time
Yup. Quic, for example, layers on UDP instead of TCP. It’s still an IP based protocol. But then you can also get things like FCoE which don’t even use TCP/UDP. Or even ATM which uses its own frame structure. There’s plenty of reasons to need to understand the OSI model.
The "TCP/IP model" is a common but informal name for what is probably more properly termed the "Internet protocol suite". UDP is included.
I'm actually not sure where QUIC fits in though. Wikipedia's pages on both the IP suite and the OSI model say it's on the transport layer of the IP suite, and layer 4 of OSI, but so is UDP. So I guess it's another example of how the OSI model is more of a theoretical idea than something that represents reality?