Maximum transmission unit (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Maximum transmission unit" in English language version.

refsWebsite
Global rank English rank
214th place
176th place
2nd place
2nd place
low place
low place
6,278th place
3,907th place
11th place
8th place
6,184th place
4,465th place
4,121st place
2,662nd place
low place
low place
5th place
5th place
2,882nd place
2,105th place
low place
low place
6,805th place
4,220th place
low place
low place

cisco.com

dell.com

doi.org

  • RFC 791. p. 25. doi:10.17487/RFC0791.
  • Murray, David; Terry Koziniec; Kevin Lee; Michael Dixon (2012). "Large MTUs and internet performance". 2012 IEEE 13th International Conference on High Performance Switching and Routing. pp. 82–87. doi:10.1109/HPSR.2012.6260832. ISBN 978-1-4577-0833-6. S2CID 232321.
  • RFC 791. p. 24. doi:10.17487/RFC0791. Every internet destination must be able to receive a datagram of 576 octets either in one piece or in fragments to be reassembled.
  • RFC 2460. p. 13. doi:10.17487/RFC2460.
  • RFC 791. p. 24. doi:10.17487/RFC0791. Every internet module must be able to forward a datagram of 68 octets without further fragmentation.
  • RFC 791. p. 12. doi:10.17487/RFC0791. Total Length is the length of the datagram, measured in octets, including internet header and data. This field allows the length of a datagram to be up to 65,535 octets.
  • RFC 1191. doi:10.17487/RFC1191.
  • J. Mogul; S. Deering (November 1990). Path MTU Discovery. Network Working Group. doi:10.17487/RFC1191. RFC 1191. Draft Standard. Obsoletes RFC 1063.
  • J. McCann; S. Deering; J. Mogul (July 2017). R. Hinden (ed.). Path MTU Discovery for IP version 6. IETF. doi:10.17487/RFC8201. STD 87. RFC 8201. Internet Standard 87. Obsoletes RFC 1981.
  • M. Mathis; J. Heffner (March 2007). Packetization Layer Path MTU Discovery. Network Working Group. doi:10.17487/RFC4821. RFC 4821. Proposed Standard. Updated by RFC 8899.
  • G. Fairhurst; T. Jones; M. Tüxen; I. Rüngeler; T. Völker (September 2020). Packetization Layer Path MTU Discovery for Datagram Transports. IETF. doi:10.17487/RFC8899. ISSN 2070-1721. RFC 8899. Proposed Standard. Updates RFC 4821, 4960, 6951, 8085 and 8261.

ietf.org

datatracker.ietf.org

  • RFC 791. p. 25. doi:10.17487/RFC0791.
  • RFC 791. p. 24. doi:10.17487/RFC0791. Every internet destination must be able to receive a datagram of 576 octets either in one piece or in fragments to be reassembled.
  • RFC 2460. p. 13. doi:10.17487/RFC2460.
  • RFC 791. p. 24. doi:10.17487/RFC0791. Every internet module must be able to forward a datagram of 68 octets without further fragmentation.
  • RFC 791. p. 12. doi:10.17487/RFC0791. Total Length is the length of the datagram, measured in octets, including internet header and data. This field allows the length of a datagram to be up to 65,535 octets.
  • RFC 1191. doi:10.17487/RFC1191.
  • RFC 2460
  • RFC 2675, p. 1, "The IPv6 header [IPv6] has a 16-bit Payload Length field and, therefore, supports payloads up to 65,535 octets long. This document specifies an IPv6 hop-by-hop option, called the Jumbo Payload option, that carries a 32-bit length field in order to allow transmission of IPv6 packets with payloads between 65,536 and 4,294,967,295 octets in length. Packets with such long payloads are referred to as 'jumbograms'."
  • RFC 2460
  • RFC 1356
  • Network Working Group of the IETF, RFC 894: A Standard for the Transmission of IP Datagrams over Ethernet Networks, Page 1, "The maximum length of the data field of a packet sent over an Ethernet is 1500 octets, thus the maximum length of an IP datagram sent over an Ethernet is 1500 octets.", ERRATA
  • RFC 2516 with the standard Ethernet MTU of 1500 bytes; extensions exist
  • RFC 4638
  • J. Mogul; S. Deering (November 1990). Path MTU Discovery. Network Working Group. doi:10.17487/RFC1191. RFC 1191. Draft Standard. Obsoletes RFC 1063.
  • J. McCann; S. Deering; J. Mogul (July 2017). R. Hinden (ed.). Path MTU Discovery for IP version 6. IETF. doi:10.17487/RFC8201. STD 87. RFC 8201. Internet Standard 87. Obsoletes RFC 1981.
  • M. Mathis; J. Heffner (March 2007). Packetization Layer Path MTU Discovery. Network Working Group. doi:10.17487/RFC4821. RFC 4821. Proposed Standard. Updated by RFC 8899.
  • G. Fairhurst; T. Jones; M. Tüxen; I. Rüngeler; T. Völker (September 2020). Packetization Layer Path MTU Discovery for Datagram Transports. IETF. doi:10.17487/RFC8899. ISSN 2070-1721. RFC 8899. Proposed Standard. Updates RFC 4821, 4960, 6951, 8085 and 8261.

juniper.net

mikrotik.com

help.mikrotik.com

murdoch.edu.au

researchrepository.murdoch.edu.au

networkworld.com

  • Scott Hogg (2013-03-06), Jumbo Frames, Network World, retrieved 2013-08-05, Most network devices support a jumbo frame size of 9216 bytes.

rfc-editor.org

  • Network Working Group of the IETF, RFC 894: A Standard for the Transmission of IP Datagrams over Ethernet Networks, Page 1, "The maximum length of the data field of a packet sent over an Ethernet is 1500 octets, thus the maximum length of an IP datagram sent over an Ethernet is 1500 octets.", ERRATA

semanticscholar.org

api.semanticscholar.org

stsauver.com

  • Joe St Sauver (2003-02-04). "Practical Issues Associated With 9K MTUs" (PDF). uoregon.edu. p. 67. Retrieved 2016-12-15. you still need to insure that ALL upstream Ethernet switches, including any switches in your campus core, are ALSO jumbo frame capable

thenetworkencyclopedia.com

  • jabber, The Network Encyclopedia, retrieved 2016-07-28

worldcat.org