IPv6 Jumbograms
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 9
- Abstract
- 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]
- Publication Date
- 1999-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2675- Link
- https://doi.org/10.17487/RFC2675
- Author(s)
- David A. BormanDr. Steve E. DeeringBob Hinden
- Keyword(s)
- IPv6, IP, Packet
Latest version of IETF RFC 2675
Document Versions — IETF RFC 2675
-
▶ IETF RFC 2675 (1999-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 768 [Active*]
- IETF RFC 793 [Superseded*]
- IETF RFC 1323 [Superseded*]
- IETF RFC 1981 [Superseded*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 2463 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2675.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2675, IPv6 Jumbograms. Available at https://doi.org/10.17487/RFC2675
Snippet:
IETF RFC 2675, IPv6 Jumbograms. Available at https://doi.org/10.17487/RFC2675
HTML (ISO 690 compliant)
Preview:
IETF RFC 2675, IPv6 Jumbograms. Available at https://doi.org/10.17487/RFC2675
Snippet:
<span class="citation"><cite>IETF RFC 2675</cite>, IPv6 Jumbograms. Available at <a href="https://doi.org/10.17487/RFC2675" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2675</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc2675">IETF RFC 2675</cite>, IPv6 Jumbograms <span class="doi">10.17487/RFC2675</span> </li>
Referenced By
- IETF RFC 3686 [Active*]
- IETF RFC 3711 [Active*]
- IETF RFC 4294 [Superseded*]
- IETF RFC 4309 [Active*]
- IETF RFC 4614 [Superseded*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 6214 [Active*]
- IETF RFC 6691 [Superseded*]
- IETF RFC 7323 [Active*]
- IETF RFC 8085 [Active*]
- IETF RFC 8468 [Active*]
- IETF RFC 9293 [Active*]
- IETF RFC 9868 [Active*]