Path MTU Discovery for IP version 6
RFC 8201
Document | Type |
RFC - Internet Standard
(July 2017; No errata)
Obsoletes RFC 1981
Also known as STD 87
|
|
---|---|---|---|
Authors | Jack <> , Stephen <> , Jeffrey <> , Bob Hinden | ||
Last updated | 2017-07-14 | ||
Replaces | draft-hinden-6man-rfc1981bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Ole Trøan | ||
Shepherd write-up | Show (last changed 2017-01-27) | ||
IESG | IESG state | RFC 8201 (Internet Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Suresh Krishnan | ||
Send notices to | "Ole Troan" <otroan@employees.org> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) J. McCann Request for Comments: 8201 Digital Equipment Corporation STD: 87 S. Deering Obsoletes: 1981 Retired Category: Standards Track J. Mogul ISSN: 2070-1721 Digital Equipment Corporation R. Hinden, Ed. Check Point Software July 2017 Path MTU Discovery for IP version 6 Abstract This document describes Path MTU Discovery (PMTUD) for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP version 4. It obsoletes RFC 1981. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8201. McCann, et al. Standards Track [Page 1] RFC 8201 IPv6 Path MTU Discovery July 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. McCann, et al. Standards Track [Page 2] RFC 8201 IPv6 Path MTU Discovery July 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 6 4. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 7 5. Implementation Issues . . . . . . . . . . . . . . . . . . . . 8 5.1. Layering . . . . . . . . . . . . . . . . . . . . . . . . 8 5.2. Storing PMTU Information . . . . . . . . . . . . . . . . 9 5.3. Purging Stale PMTU Information . . . . . . . . . . . . . 11 5.4. Packetization Layer Actions . . . . . . . . . . . . . . . 12 5.5. Issues for Other Transport Protocols . . . . . . . . . . 13 5.6. Management Interface . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . 15 8.2. Informative References . . . . . . . . . . . . . . . . . 15 Appendix A. Comparison to RFC 1191 . . . . . . . . . . . . . . . 17 Appendix B. Changes Since RFC 1981 . . . . . . . . . . . . . . . 17 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 McCann, et al. Standards Track [Page 3] RFC 8201 IPv6 Path MTU Discovery July 2017 1. Introduction When one IPv6 node has a large amount of data to send to anotherShow full document text