RFC 9869 on Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options

rfc-editor@rfc-editor.org Tue, 07 October 2025 23:24 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8DD236EFDE9E; Tue, 7 Oct 2025 16:24:22 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 6A1AFC000065; Tue, 7 Oct 2025 16:24:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9869 on Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP Options
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251007232422.6A1AFC000065@rfcpa.rfc-editor.org>
Date: Tue, 07 Oct 2025 16:24:22 -0700
Message-ID-Hash: L3BSMMQLS7MD4SO7IS4VWCRZEWS6KENZ
X-Message-ID-Hash: L3BSMMQLS7MD4SO7IS4VWCRZEWS6KENZ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/00PIy8MTEQDqEaC9FyCwrCTLQ6s>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9869

        Title:      Datagram Packetization Layer Path MTU 
                    Discovery (DPLPMTUD) for UDP Options 
        Author:     G. Fairhurst,
                    T. Jones
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2025
        Mailbox:    gorry@erg.abdn.ac.uk,
                    tom@erg.abdn.ac.uk
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-udp-options-dplpmtud-15.txt

        URL:        https://www.rfc-editor.org/info/rfc9869

        DOI:        10.17487/RFC9869

This document specifies how a UDP Options sender implements Datagram
Packetization Layer Path MTU Discovery (DPLPMTUD) as a robust method
for Path MTU Discovery (PMTUD). This method uses the UDP Options
packetization layer. It allows an application to discover the largest
size of datagram that can be sent across a network path. It also
provides a way to allow the application to periodically verify the
current Maximum Packet Size (MPS) supported by a path and to update
this when required.

This document is a product of the Transport and Services Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team