[rfc-dist] RFC 4821 on Packetization Layer Path MTU Discovery

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Mar 29 17:58:05 PDT 2007

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

        RFC 4821

        Title:      Packetization Layer Path MTU Discovery 
        Author:     M. Mathis, J. Heffner
        Status:     Standards Track
        Date:       March 2007
        Mailbox:    mathis at psc.edu, 
                    jheffner at psc.edu
        Pages:      32
        Characters: 75665
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pmtud-method-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4821.txt

This document describes a robust method for Path MTU Discovery
(PMTUD) that relies on TCP or some other Packetization Layer to probe
an Internet path with progressively larger packets.  This method is
described as an extension to RFC 1191 and RFC 1981, which specify
ICMP-based Path MTU Discovery for IP versions 4 and 6, respectively.  

This document is a product of the Path MTU Discovery
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list