Visual RFC.
ALL RFCs / RFC 8200
Read the RFC ↗
RFC 8200 / MECHANISMS

Fit packets to the path

04

Every IPv6 link supports at least a 1280-octet packet, directly or through lower-layer fragmentation.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5 ↗
RFC 8200 · § 5EXAMPLE
3 / 3
Fit packets to the pathAn oversized packet is rejected at a narrower link; the source reduces its size.WORKED EXAMPLE · PATH MTU1500128015001280 octetsfits the bottleneckOnly the source adapts or fragmentsRouters do not fragment IPv6 packets
03
Send a packet that fits.

The source lowers its size to fit the reported path MTU.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The smallest link MTU constrains the path.

  • Path MTU is the minimum link MTU along the route.
  • IPv6 routers do not fragment packets; source nodes adapt or fragment.
  • Path MTU Discovery is recommended; a minimal implementation can restrict packets to at most 1280 octets.
DETAILS

An ICMPv6 Packet Too Big message can inform the source about a smaller path limit. Discovery details are in RFC 8201.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Addresses identify interfaces
  2. Read the fixed IPv6 header
  3. Follow the next header chain
  4. Fit packets to the path
  5. Reassemble source fragments
  6. Forward with explicit limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗