Sure, see the following https://tools.ietf.org/id/draft-ietf-isis-ext-eth-01.txt https://tools.ietf.org/id/draft-ietf-isis-ext-eth-01.txt: 11. Appendix 2. Com

Sure, see the following https://tools.ietf.org/id/draft-ietf-isis-ext-eth-01.txt https://tools.ietf.org/id/draft-ietf-isis-ext-eth-01.txt: 11. Appendix 2. Comments from the draft's authors: FDDI and Ethernet use the same error checking mechanism; CRC-32. The probability of undetected errors remains constant for frame sizes between 3007 and 91639 bits (approximately 376 to 11455 bytes). Setting the maximum size of jumbo frames to 9018 bytes falls well within this range. There is no increase in undetected errors when using jumbo frames and the existing CRC-32 as the error detection mechanism. This is also worth a read: https://tools.ietf.org/html/draft-anumita-tcpm-stronger-checksum-00 https://tools.ietf.org/html/draft-anumita-tcpm-stronger-chec... >The strength of the Ethernet CRC checksum and the 16 bitTransport checksum has been found to reduce for data segments that are largerthan the standard Ethernet MTU. Koopman et. al. [Koopman] have explored a number of CRC polynomials as well as the polynomial used in the Ethernet CRC calculation. And the following on page 32: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.4.8352&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.4.8... >"Due to the nature of the CRC algorithm, the probability of undetected errors is the same for frame sizes between 376 and 11,455 bytes. Thus to maintain the same bit error rate accuracy as standard Ethernet, frames should ideally not exceed 11455 bytes."