What does MTU depend on?
Clash Royale CLAN TAG#URR8PPP
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked Feb 25 at 18:09
VasilisVasilis
192115
add a comment |
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked Feb 25 at 18:09
VasilisVasilis
192115
add a comment |
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
asked Feb 25 at 18:09
VasilisVasilis
192115
I'm trying to understand what factors determine the MTU. For instance, why 802.11 has MTU of 2304 while Ethernet MTU of 1500? Are there restrictions of the physical medium or arbitrary design decisions?
ethernet ieee-802.11 mtu
ethernet ieee-802.11 mtu
asked Feb 25 at 18:09
VasilisVasilis
192115
asked Feb 25 at 18:09
VasilisVasilis
192115
asked Feb 25 at 18:09
VasilisVasilis
192115
asked Feb 25 at 18:09
VasilisVasilis
192115
asked Feb 25 at 18:09
VasilisVasilis
192115
192115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "496"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57206%2fwhat-does-mtu-depend-on%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
add a comment |
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
add a comment |
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
The MTU is the size of the payload allowed for the data-link protocol. That is determined when the protocol is standardized, and various criteria go into the decision on the payload size. The ethernet payload size was based on a compromise for a reasonable size of the amount of data to be sent against having a host monopolize the shared segment for a long period of time.
It is not really a physical medium limitation (although having a shared medium had something to do with the original decision of payload size). There are many implementations of ethernet that support jumbo frames, although that is non-standard. Ethernet also runs over various media at various speed, and the ethernet MTU is still 1500 octets for the various ethernet standards.
Trying to change something so basic as the MTU on an established standard creates a lot of problems. For example, the ethernet jumbo frames can cause big problems unless the use is carefully planned (every interface in the path must support the same jumbo frame MTU, and ethernet does not have fragmentation or retransmission, so frames too large for an interface are simply dropped).
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
edited Feb 25 at 18:51
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
answered Feb 25 at 18:16
Ron Maupin♦Ron Maupin
67.5k1369126
67.5k1369126
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
add a comment |
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
Thanks, so it's a design decision. Wouldn't it make sense for all physical protocols to use the same MTU, since end-to-end traffic most likely crosses many segments? I'm asking because fragmentation presumably adds overhead
– Vasilis
Feb 25 at 18:37
3
3
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
Do not assume that all the protocols are designed by the same people. Bob Metcalfe designed ethernet (1500), IBM created token ring (4464 for 4 Mbps, and 17914 for 16 Mbps), etc., all before the IEEE took over the protocols. There are also non-IEEE protocols for which each developer chose a different payload size.
– Ron Maupin♦
Feb 25 at 18:44
add a comment |
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57206%2fwhat-does-mtu-depend-on%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
