RFC 8900: IP Fragmentation Considered Fragile
In plain English — editorial summary, not part of the RFC
This document describes IP fragmentation and explains how it introduces fragility to Internet communication. This document also proposes alternatives to IP fragmentation and provides recommendations for developers and network operators.
Document record
- Document ID
- RFC8900
- Published
- September 2020
- Authors
- R. Bonica; F. Baker; G. Huston; R. Hinden; O. Troan; F. Gont
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 23
- Also known as
- BCP230
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9011Static Context Header Compression and Fragmentation (SCHC) over LoRaWANCurrent
April 2021
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 9363A YANG Data Model for Static Context Header Compression (SCHC)Updated
March 2023
- RFC 8824Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)Current
June 2021
- RFC 8801Discovering Provisioning Domain Names and DataCurrent
July 2020
- RFC 9063Host Identity Protocol ArchitectureCurrent
July 2021
- RFC 8676YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) SoftwiresCurrent
November 2019
- RFC 9131Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop RoutersCurrent
October 2021
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?