The IPv6 Jumbo Payload Option
draft-ietf-ipngwg-jumbo-00
| Document | Type |
Expired Internet-Draft
(ipngwg WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bob Hinden , Dr. Steve E. Deering | ||
| Last updated | 1998-08-07 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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 describes the Jumbo Payload option for IPv6, which is used to send IPv6 packets with payloads longer than 65,535 octets. This option is relevant only for IPv6 nodes that may be attached to links with a link MTU greater than 65,575 octets, and need not be implemented or understood by IPv6 nodes that do not support attachment to links with such large MTUs.
Authors
Bob Hinden
Dr. Steve E. Deering
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)