RFC 2675: IPv6 Jumbograms
In plain English — editorial summary, not part of the RFC
This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2675
- Published
- August 1999
- Authors
- D. Borman; S. Deering; R. Hinden
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
- Obsoletes:
- RFC 2147
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2711IPv6 Router Alert OptionUpdated
October 1999
- RFC 2734IPv4 over IEEE 1394Current
December 1999
- RFC 2590Transmission of IPv6 Packets over Frame Relay Networks SpecificationUpdated
May 1999
- RFC 2526Reserved IPv6 Subnet Anycast AddressesCurrent
March 1999
- RFC 2497Transmission of IPv6 Packets over ARCnet NetworksUpdated
January 1999
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 2473Generic Packet Tunneling in IPv6 SpecificationCurrent
December 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?