RFC 9268: IPv6 Minimum Path MTU Hop-by-Hop Option
In plain English — editorial summary, not part of the RFC
This document specifies a new IPv6 Hop-by-Hop Option that is used to record the Minimum Path MTU (PMTU) along the forward path between a source host to a destination host. The recorded value can then be communicated back to the source using the return Path MTU field in the Option.
Document record
- Document ID
- RFC9268
- Published
- August 2022
- Authors
- R. Hinden; G. Fairhurst
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9869Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP OptionsCurrent
October 2025
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 5927ICMP Attacks against TCPCurrent
July 2010
- RFC 4821Packetization Layer Path MTU DiscoveryUpdated
March 2007
- RFC 9259Operations, Administration, and Maintenance (OAM) in Segment Routing over IPv6 (SRv6)Current
June 2022
- RFC 9250DNS over Dedicated QUIC ConnectionsCurrent
May 2022
- RFC 9249A YANG Data Model for NTPCurrent
July 2022
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?