4 ms·
> IP and TCP were very carefully designed How did it happen that the byte order of the multi-byte numeric fields in TCP/IP headers is big endian, which is oppo
by kazinator 5y ago
> IP and TCP were very carefully designed
How did it happen that the byte order of the multi-byte numeric fields in TCP/IP headers is big endian, which is opposite of what most machines use now? Back then, did it look as if big endian would become prevalent?
Today, almost every host attached to an IP network has to byte swap.
The IPv6 people definitely ought to have designed a little more carefully.
- lanstin 5y agoWhen IP and TCP were deployed, most machines were big-endian.
- tuatoru 5y ago> Back then, did it look as if big endian would become prevalent? Yes. Big endian was "natural" and x86 was weird and awkward, and a niche low end design that woud never be connected to networks.
- GuB-42 5y agoBig endian is better for routing applications. In the same way that little endian is better for addition. For example let's say I send a message to 1.2.3.4, the first router will decide what will be the next node based on the first number, the next one on the second, the next on the third, etc... Because it is big endian, the first router only has to read the first number to do its job, if it was little endian, it would have to read the entire address fist. Of course, it is a detail, I mean, the words "little/big endian" is a parallel to the the pointless fights in Gulliver's travels. But even if it could have gone either way, for IP, big endian is more natural.