3 ms·
>It's not like there's an intrinsic reason TCP packets are the way they are now, it's largely an arbitrary choice that we standardized on. This is incredibly o
by rabite 5y ago
>It's not like there's an intrinsic reason TCP packets are the way they are now, it's largely an arbitrary choice that we standardized on.
This is incredibly off-base. There was a huge effort to force an OSI-designed networking protocol stack that was designed by a committee of government bureaucrats and big blue sales engineers. It was a total disaster, but the vast amount of resources that were dedicated to forcing the OSI memes was in the billions of dollars. Large amounts of actual physical hardware were produced conforming to protocol standards nobody doing anything real actually wanted to use because a lot of government agencies required all network equipment to be compatible with the OSI protocol stack.
TCP, UDP, and the modern routing protocols (BGP, OSPF, etc) and their associated address resolution systems were not an arbitrary choice -- they represented orders of magnitude level improvements over the government-backed OSI standards and getting them to succeed was the product of intense collective effort of some of the most brilliant minds of the past century.
https://en.wikipedia.org/wiki/Protocol_Wars https://en.wikipedia.org/wiki/Protocol_Wars
- walshemj 5y agoAs a former OSI person (UK third line X.400/500 support ) I think that TCP/IP won as it was simpler and good enough. TCP/IP was in no way an technical improvement over OSI
- rabite 5y agoX.400 was actually pretty great and was definitely better designed than the disaster of SMTP (I spent my youth in the email deliverability industry and know all the ingredients of that sausage), but it wasn't a network transport protocol. There is no way that the Internet could have been built on the OSI transport and routing implementations. They were not good. Nothing has stood up to as much scrutiny and scale as TCP/IP. The simplicity is definitely an important part of it. Protocols that are used by trillions of devices need to be simple, and the equipment used to switch and route their traffic have to defer as much handling of state to the clients as possible. The more state that routers have to maintain, the less reliable they will be. TCP/IP accomplished that and that's why it was better.