jkrey@venera.isi.edu (Joyce K. Reynolds) (11/17/90)
A new Request for Comments is now available from the Network Information
Center in the online library at NIC.DDN.MIL.
RFC 1191:
Title: Path MTU Discovery
Author: J. Mogul and S. Deering
Mailbox: mogul@decwrl.dec.com, deering@xerox.com
Pages: 19
Characters: 47,936
pathname: RFC:RFC1191.TXT
This memo describes a technique for dynamically discovering the
maximum transmission unit (MTU) of an arbitrary internet path. It
specifies a small change to the way routers generate one type of ICMP
message. For a path that passes through a router that has not been
so changed, this technique might not discover the correct Path MTU,
but it will always choose a Path MTU as accurate as, and in many
cases more accurate than, the Path MTU that would be chosen by
current practice.
This RFC specifies a Proposed Standard Protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT (where "nnnn" refers to the number of the RFC). Login
with FTP, username "anonymous" and password "guest".
The NIC also provides an automatic mail service for those sites which
cannot use FTP. Address the request to SERVICE@NIC.DDN.MIL and in the
subject field of the message indicate the RFC number, as in "Subject:
RFC nnnn".
RFCs can also be obtained via FTP from NIS.NSF.NET. Using FTP, login
with username "anonymous" and password "guest"; then connect to the RFC
directory ("cd RFC"). The file name is of the form RFCnnnn.TXT-1
(where "nnnn" refers to the number of the RFC).
The NIS also provides an automatic mail service for those sites which
cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank. The first line of the text of
the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by
the RFC number.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Joyce K. Reynolds
USC/Information Sciences Institute