Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Remove internal links—those don't seem to have survived the Confluence migration well

...

Traditional (RFC1191) Path MTU Discovery

121340970 RFC 1191 describes a method for a sender to detect the Path MTU to a given receiver. (121340970 RFC 1981 describes the equivalent for IPv6.) The method works as follows:

...

This method is widely implemented, but is not robust in today's Internet because it relies on ICMP packets sent by routers along the path. Such packets are often suppressed either at the router that should generate them (to protect its resources) or on the way back to the source, because of firewalls and other packet filters or rate limitations. These problems are described in 121340970RFC 2923. When packets are lost due to MTU issues without any ICMP "Too Big" message, this is sometimes called a (MTU) black hole. Some operating systems have added heuristics to detect such black holes and work around them. Workarounds can include lowering the MTU estimate or disabling PMTUD for certain destinations.

Packetization Layer Path MTU Discovery (PLPMTUD, RFC 4821 and RFC 8899)

An IETF Working Group (pmtud) was chartered to define a new mechanism for Path MTU Discovery to solve these issues. This process resulted in RFC 4821, Packetization Layer Path MTU Discovery ("PLPMTUD"), which was published in March 2007. This scheme requires cooperation from a network layer above IP, namely the layer that performs "packetization". This could be TCP, but could also be a layer above UDP, let's say an RPC or file transfer protocol. PLPMTUD does not require ICMP messages. The sending packetization layer starts with small packets, and probes progressively larger sizes. When there's an indication that a larger packet was successfully transmitted to the destination (presumably because some sort of ACK was received), the Path MTU estimate is raised accordingly.

...

A user-space implementation over UDP is included in the VFER bulk transfer tool.

RFC 8899, published in September 2020, updates RFC 4821 by extending its use to datagram-oriented transports.

Minimum Path MTU Hop-by-Hop Option

Recently, the IETF 6man Working Group has adopted an Internet-Draft (see reference below) proposing an IPv6 hop-by-hop option that would allow discovering the Path MTU with assistance from routers. Note that this still requires a mechanism to "echo" the discovered PMTU back to the sender. (Some people are skeptical about the chances that this option will see successful deployment, for example Geoff Huston in his August 2021 IETF 111 report.

References

Implementations

  • for Linux 2.6 - integrated in mainstream kernel as of 2.6.17. However, it is disabled by default (see net.ipv4.tcp_mtu_probing sysctl)
  • for NetBSD

-- HankNussbacher - 2005-07-03
– SimonLeinen - 2006-07-19 - 20192021-09-1004