[tsvwg] RFC 8899 on Packetization Layer Path MTU Discovery for Datagram Transports

rfc-editor@rfc-editor.org Fri, 11 September 2020 23:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9522D3A0B0F; Fri, 11 Sep 2020 16:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id PtfnrYJoZbAb; Fri, 11 Sep 2020 16:22:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 144783A0951; Fri, 11 Sep 2020 16:22:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 98A19F40766; Fri, 11 Sep 2020 16:21:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200911232144.98A19F40766@rfc-editor.org>
Date: Fri, 11 Sep 2020 16:21:44 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Sob2dO32KlPjUKNkXCZoaMHuOrc>
Subject: [tsvwg] =?utf-8?q?RFC_8899_on_Packetization_Layer_Path_MTU_Disco?= =?utf-8?q?very_for_Datagram_Transports?=
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2020 23:22:12 -0000

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

        RFC 8899

        Title:      Packetization Layer Path MTU Discovery 
                    for Datagram Transports 
        Author:     G. Fairhurst, 
                    T. Jones,
                    M. Tüxen,
                    I. Rüngeler,
                    T. Völker
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2020
        Mailbox:    gorry@erg.abdn.ac.uk, 
        Pages:      35
        Updates:    RFC 4821, RFC 4960, RFC 6951, RFC 8085, RFC 8261

        I-D Tag:    draft-ietf-tsvwg-datagram-plpmtud-22.txt

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

        DOI:        10.17487/RFC8899

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

This specification updates RFC 4960, RFC 4821, RFC 6951, RFC 8085,
and RFC 8261.

This document is a product of the Transport Area 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

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
Association Management Solutions, LLC