IPv6 Minimum Path MTU Hop-by-Hop Option
draft-hinden-6man-mtu-option-02
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bob Hinden , Gorry Fairhurst | ||
| Last updated | 2019-08-08 (Latest revision 2019-07-05) | ||
| Replaced by | draft-ietf-6man-mtu-option | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-mtu-option | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies a new Hop-by-Hop IPv6 option that is used to record the minimum Path MTU along the forward path between a source to a destination host. This collects a minimum recorded MTU along the path to the destination. The value can then be communicated back to the source using the return Path MTU field in the option. This Hop-by-Hop option is intended to be used in environments like Data Centers and on paths between Data Centers, to allow them to better take advantage of paths able to support a large Path MTU.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)