Path MTU discovery
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 19
- Abstract
- This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. [STANDARDS-TRACK]
- Publication Date
- 1990-11-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC1191- Link
- https://doi.org/10.17487/RFC1191
- Author(s)
- Jeffrey MogulDr. Steve E. Deering
- Keyword(s)
- IP-MTU
Latest version of IETF RFC 1191
Document Versions — IETF RFC 1191
-
▶ IETF RFC 1191 (1990-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- C. Kent and J. Mogul. Fragmentation Considered Harmful. In Proc. SIGCOMM '87 Workshop on Frontiers in Computer Communications Technology. August, 1987. EXTERNAL
- Drew Daniel Perkins. Private Communication. EXTERNAL
- Geof Cooper. IP Datagram Sizes. Electronic distribution of the TCP-IP Discussion Group, Message-ID <8705240517.AA01407@apolling.imagen.uucp>. EXTERNAL
- Van Jacobson. Congestion Avoidance and Control. In Proc. SIGCOMM '88 Symposium on Communications Architectures and Protocols, pages 314-329. Stanford, CA, August, 1988. EXTERNAL
- IETF RFC 791 [Active*]
- IETF RFC 792 [Active*]
- IETF RFC 879 [Superseded*]
- IETF RFC 905 [Active*]
- IETF RFC 1057 [Active*]
- IETF RFC 1122 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1191.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1191, Path MTU discovery. Available at https://doi.org/10.17487/RFC1191
Snippet:
IETF RFC 1191, Path MTU discovery. Available at https://doi.org/10.17487/RFC1191
HTML (ISO 690 compliant)
Preview:
IETF RFC 1191, Path MTU discovery. Available at https://doi.org/10.17487/RFC1191
Snippet:
<span class="citation"><cite>IETF RFC 1191</cite>, Path MTU discovery. Available at <a href="https://doi.org/10.17487/RFC1191" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1191</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc1191">IETF RFC 1191</cite>, Path MTU discovery <span class="doi">10.17487/RFC1191</span> </li>
Referenced By
- IETF RFC 1332 [Active*]
- IETF RFC 1435 [Active*]
- IETF RFC 1531 [Superseded*]
- IETF RFC 1533 [Superseded*]
- IETF RFC 1541 [Superseded*]
- IETF RFC 1626 [Superseded*]
- IETF RFC 1700 [Superseded*]
- IETF RFC 1812 [Active*]
- IETF RFC 1826 [Superseded*]
- IETF RFC 1853 [Active*]
- IETF RFC 1883 [Superseded*]
- IETF RFC 1885 [Superseded*]
- IETF RFC 1933 [Superseded*]
- IETF RFC 1940 [Active*]
- IETF RFC 1981 [Superseded*]
- IETF RFC 2003 [Active*]
- IETF RFC 2004 [Active*]
- IETF RFC 2131 [Active*]
- IETF RFC 2132 [Active*]
- IETF RFC 2178 [Superseded*]
- IETF RFC 2225 [Active*]
- IETF RFC 2328 [Active*]
- IETF RFC 2414 [Superseded*]
- IETF RFC 2431 [Active*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 2463 [Superseded*]
- IETF RFC 2488 [Active*]
- IETF RFC 2525 [Active*]
- IETF RFC 2581 [Superseded*]
- IETF RFC 2740 [Superseded*]
- IETF RFC 2757 [Active*]
- IETF RFC 2765 [Superseded*]
- IETF RFC 2784 [Active*]
- IETF RFC 2893 [Superseded*]
- IETF RFC 2923 [Active*]
- IETF RFC 2960 [Superseded*]
- IETF RFC 2979 [Active*]
- IETF RFC 3032 [Active*]
- IETF RFC 3124 [Active*]
- IETF RFC 3155 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3366 [Active*]
- IETF RFC 3390 [Active*]
- IETF RFC 3449 [Active*]
- IETF RFC 3481 [Active*]
- IETF RFC 3819 [Active*]
- IETF RFC 3884 [Active*]
- IETF RFC 3985 [Active*]
- IETF RFC 4023 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4302 [Active*]
- IETF RFC 4338 [Active*]
- IETF RFC 4340 [Active*]
- IETF RFC 4347 [Superseded*]
- IETF RFC 4821 [Active*]
- IETF RFC 4960 [Superseded*]
- IETF RFC 5340 [Active*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5415 [Active*]
- IETF RFC 5426 [Active*]
- IETF RFC 5681 [Active*]
- IETF RFC 5766 [Superseded*]
- IETF RFC 5838 [Active*]
- IETF RFC 5927 [Active*]
- IETF RFC 6269 [Active*]
- IETF RFC 6347 [Superseded*]
- IETF RFC 7323 [Active*]
- IETF RFC 8085 [Active*]
- IETF RFC 9000 [Active*]
- IETF RFC 9293 [Active*]