RFC 8021: Generation of IPv6 Atomic Fragments Considered Harmful
In plain English — editorial summary, not part of the RFC
This document discusses the security implications of the generation of IPv6 atomic fragments and a number of interoperability issues associated with IPv6 atomic fragments. It concludes that the aforementioned functionality is undesirable and thus documents the motivation for removing this functionality from an upcoming revision of the core IPv6 protocol specification (RFC 2460).
Document record
- Document ID
- RFC8021
- Published
- January 2017
- Authors
- F. Gont; W. Liu; T. Anderson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7739Security Implications of Predictable Fragment Identification ValuesCurrent
February 2016
- RFC 8883ICMPv6 Errors for Discarding Packets Due to Processing LimitsCurrent
September 2020
- RFC 8019Protecting Internet Key Exchange Protocol Version 2 (IKEv2) Implementations from Distributed Denial-of-Service AttacksCurrent
November 2016
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 6952Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
May 2013
- RFC 9288Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit RoutersCurrent
August 2022
- RFC 9416Security Considerations for Transient Numeric Identifiers Employed in Network ProtocolsCurrent
July 2023
- RFC 9715IP Fragmentation Avoidance in DNS over UDPCurrent
January 2025
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?