Numbers in networking often come back around again and again. This is especially true if those numbers are powers of two. You see 256, 512, and 32768 very often when you’re doing networking tasks. These values are often easy to figure out based on mathematical calculations that come up when looking a packet or a value of a priority. But sometimes there are arbitrary numbers that get thrown into the mix without rhyme or reason.
One such number is the maximum transmission unit (MTU) size of a packet. Why is it 1500 bytes? That’s an oddly specific number that looks like it was picked by a human and not math. As it turns out, the reasoning behind it is actually pretty fascinating. Ivan Pepelnjak dives into the subject thanks to a question from one of his readers. As he says:
After the original thick-cable Ethernet became a great hit someone within IEEE got the wonderful idea that whatever they do afterwards has to be compatible with that initial implementation. That’s why we still have 1500-byte MTU and half-duplex Gigabit Ethernet messing up P2P links ;))… and Innokentiy explained in his comment why we never got past 9K MTU.
Read more at How Did We End with 1500-byte MTU?
- Moving Past The Edge with Aruba SD-Branch - February 26, 2020
- Does SPB Mean “Secure Path Bridging”? - February 12, 2020
- Cloud Isn’t Your Key To Compliance - February 10, 2020
- Breaking IoT Security - February 7, 2020
- Answers at Your Fingertips with Forward Networks - February 4, 2020
- Priming Your Application Performance with Intel Application Device Queues - January 29, 2020
- Is Cisco SD Access Intent Based Networking? - January 28, 2020
- Captivating Wireless Connectivity with Cisco OpenRoaming - January 22, 2020
- Does the Apple Airport Extreme Use VLANs? - January 21, 2020
- Predicting Data Patterns with Cradlepoint - January 16, 2020