• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: November 21st, 2023

help-circle











  • Apologies, that’s my fault, I thought you wrote “TCP model(/protocol)” and not “TCP/IP model”, which are indeed two very different things.

    I feel that the OSI model focuses more on the specific layers with their relations and physical/digital setup, while the TCP/IP model has more of a abstract and “high-level”-focus. I think both have their ups and downs, though I’m still confused what about OSI is “theoretical and has never been used”.


  • What do you mean “Theoretical” and “Never been used”? Are you writing this by sending off radio waves purely with your mind? Am I the only one using a modem and computer? (/j, but it seems to me that you’re asking “why a plane needs engines and wings, when it already has a payload”)

    TCP (and UDP) just describe how to assemble the data into packages which can be somewhat reliably reassembled on the other end.

    While it does have an address stamped on top (IP), it doesn’t know how to get anywhere by itself. That’s where the bottom 3 OSI layers come in (the physical wires - or wireless spectra/wavelengths - the data is transmitted through, the specifications of how the embedded devices talk to each other over these wires, and how to discover other embedded or other devices on a network). I can very much assure you that the wires do exist and are indeed in use.

    Contrary, the upper layers are more about keeping communication going once a connection has been established.