[pmtud] RFC 4821 on Packetization Layer Path MTU Discovery (fwd)

Matt Mathis <mathis@psc.edu> Fri, 30 March 2007 01:05 UTC

Return-path: <pmtud-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HX5Yd-000368-Ct; Thu, 29 Mar 2007 21:05:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HX5Yc-000363-3P for pmtud@ietf.org; Thu, 29 Mar 2007 21:05:34 -0400
Received: from [2001:5e8:2:42:2e0:81ff:fe30:e898] (helo=mailer2.psc.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HX5Yb-0005nU-P5 for pmtud@ietf.org; Thu, 29 Mar 2007 21:05:34 -0400
Received: from tesla.psc.edu (tesla.psc.edu [128.182.58.233]) by mailer2.psc.edu (8.13.8/8.13.3) with ESMTP id l2U15Knh014100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Mar 2007 21:05:21 -0400 (EDT)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.13.1/8.13.1) with ESMTP id l2U15Kmf021220; Thu, 29 Mar 2007 21:05:20 -0400
Date: Thu, 29 Mar 2007 21:05:20 -0400 (EDT)
From: Matt Mathis <mathis@psc.edu>
To: Path MTU Discovery WG <pmtud@ietf.org>
Subject: [pmtud] RFC 4821 on Packetization Layer Path MTU Discovery (fwd)
Message-ID: <Pine.LNX.4.58.0703292104230.17210@tesla.psc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Matt Zekauskas <matt@internet2.edu>
X-BeenThere: pmtud@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Maximum Transmission Unit Discovery <pmtud.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pmtud>, <mailto:pmtud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pmtud>
List-Post: <mailto:pmtud@ietf.org>
List-Help: <mailto:pmtud-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pmtud>, <mailto:pmtud-request@ietf.org?subject=subscribe>
Errors-To: pmtud-bounces@ietf.org

Done!

Thanks everyone!
--MM--
---------- Forwarded message ----------
Date: Thu, 29 Mar 2007 17:58:05 -0700
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Cc: pmtud@ietf.org, rfc-editor@rfc-editor.org
Subject: [pmtud] RFC 4821 on Packetization Layer Path MTU Discovery


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@psc.edu,
                    jheffner@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.
[STANDARDS TRACK]

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
unlimited.

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
pmtud mailing list
pmtud@ietf.org
https://www1.ietf.org/mailman/listinfo/pmtud

_______________________________________________
pmtud mailing list
pmtud@ietf.org
https://www1.ietf.org/mailman/listinfo/pmtud