Comment 9 for bug 1355813

Do we need to take into account any overhead being added by the protocol stack along the way?

For example, if the underlying MAAS machine can be told to use 9000 byte MTUs and jumbo frames, then each layer up could adopt that, but might need to chop off some of that for protocol / tunnel / encapsulation overhead. I've seen cases where your "internal" interface needs to have, say 20 byte smaller MTUs than the host. Perhaps THAT's the bit that we should focus on specifying. So MAAS gets told "just jumbo frames here" and then everything else focuses on understanding and allowing for overhead, but maximising MTU subject to that overhead.