RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports
In plain English — editorial summary, not part of the RFC
This document specifies Datagram Packetization Layer Path MTU Discovery (DPLPMTUD). This is a robust method for Path MTU Discovery (PMTUD) for datagram Packetization Layers (PLs). It allows a PL, or a datagram application that uses a PL, to discover whether a network path can support the current size of datagram. This can be used to detect and reduce the message size when a sender encounters a packet black hole. It can also probe a network path to discover whether the maximum packet size can be increased. This provides functionality for datagram transports that is equivalent to the PLPMTUD specification for TCP, specified in RFC 4821, which it updates. It also updates the UDP Usage Guidelines to refer to this method for use with UDP datagrams and updates SCTP. The document provides implementation notes for incorporating Datagram PMTUD into IETF datagram transports or applications that use datagram transports. This specification updates RFC 4960, RFC 4821, RFC 6951, RFC 8085, and RFC 8261.
Document record
- Document ID
- RFC8899
- Published
- September 2020
- Authors
- G. Fairhurst; T. Jones; M. Tüxen; I. Rüngeler; T. Völker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 35
- 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 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 9260Stream Control Transmission ProtocolCurrent
June 2022
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 4460Stream Control Transmission Protocol (SCTP) Specification Errata and IssuesObsoleted
April 2006
- RFC 2960Stream Control Transmission ProtocolObsoleted
October 2000
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?