draft-ietf-ipngwg-pmtuv6-02.txt   draft-ietf-ipngwg-pmtuv6-03.txt 
INTERNET-DRAFT J. McCann, Digital Equipment Corporation INTERNET-DRAFT J. McCann, Digital Equipment Corporation
April 22, 1996 S. Deering, Xerox PARC May 23, 1996 S. Deering, Xerox PARC
J. Mogul, Digital Equipment Corporation J. Mogul, Digital Equipment Corporation
Path MTU Discovery for IP version 6 Path MTU Discovery for IP version 6
draft-ietf-ipngwg-pmtuv6-02.txt draft-ietf-ipngwg-pmtuv6-03.txt
Abstract Abstract
This document describes Path MTU Discovery for IP version 6. It is This document describes Path MTU Discovery for IP version 6. It is
largely derived from RFC-1191, which describes Path MTU Discovery for largely derived from RFC-1191, which describes Path MTU Discovery for
IP version 4. IP version 4.
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
skipping to change at page 1, line 39 skipping to change at page 1, line 39
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Distribution of this document is unlimited. Distribution of this document is unlimited.
Expiration Expiration
October 22, 1996 November 23, 1996
Contents Contents
Abstract........................................................1 Abstract........................................................1
Status of this Memo.............................................1 Status of this Memo.............................................1
Contents........................................................2 Contents........................................................2
1. Introduction.................................................3 1. Introduction.................................................3
2. Terminology..................................................3 2. Terminology..................................................3
3. Protocol overview............................................4 3. Protocol overview............................................4
4. Protocol Requirements........................................5 4. Protocol Requirements........................................5
5. Implementation suggestions...................................6 5. Implementation Issues........................................6
5.1. Layering...................................................6 5.1. Layering...................................................6
5.2. Storing PMTU information...................................7 5.2. Storing PMTU information...................................7
5.3. Purging stale PMTU information.............................9 5.3. Purging stale PMTU information.............................9
5.4. TCP layer actions.........................................10 5.4. TCP layer actions.........................................10
5.5. Issues for other transport protocols......................11 5.5. Issues for other transport protocols......................11
skipping to change at page 6, line 20 skipping to change at page 6, line 20
but rather must include a Fragment header in those packets [IPv6- but rather must include a Fragment header in those packets [IPv6-
SPEC]. SPEC].
A node MUST NOT increase its estimate of the Path MTU in response to A node MUST NOT increase its estimate of the Path MTU in response to
the contents of a Packet Too Big message. A message purporting to the contents of a Packet Too Big message. A message purporting to
announce an increase in the Path MTU might be a stale packet that has announce an increase in the Path MTU might be a stale packet that has
been floating around in the network, a false packet injected as part been floating around in the network, a false packet injected as part
of a denial-of-service attack, or the result of having multiple paths of a denial-of-service attack, or the result of having multiple paths
to the destination, each with a different PMTU. to the destination, each with a different PMTU.
5. Implementation suggestions 5. Implementation Issues
This section discusses a number of issues related to the This section discusses a number of issues related to the
implementation of Path MTU Discovery. This is not a specification, implementation of Path MTU Discovery. This is not a specification,
but rather a set of notes provided as an aid for implementors. but rather a set of notes provided as an aid for implementors.
The issues include: The issues include:
- What layer or layers implement Path MTU Discovery? - What layer or layers implement Path MTU Discovery?
- How is the PMTU information cached? - How is the PMTU information cached?
skipping to change at page 16, line 32 skipping to change at page 16, line 32
Jeffrey Mogul Jeffrey Mogul
Digital Equipment Corporation Western Research Laboratory Digital Equipment Corporation Western Research Laboratory
250 University Avenue 250 University Avenue
Palo Alto, CA 94301 Palo Alto, CA 94301
Phone: +1 415 617 3304 Phone: +1 415 617 3304
Email: mogul@pa.dec.com Email: mogul@pa.dec.com
Expiration Expiration
October 22, 1996 November 23, 1996
 End of changes. 6 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/