<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-6man-ipv6-atomic-fragments" target="https://datatracker.ietf.org/doc/html/draft-ietf-6man-ipv6-atomic-fragments-03">
   <front>
      <title>Processing of IPv6 &quot;atomic&quot; fragments</title>
      <author initials="F." surname="Gont" fullname="Fernando Gont">
         </author>
      <date month="December" day="29" year="2012" />
      <abstract>
	 <t>   The IPv6 specification allows packets to contain a Fragment Header
   without the packet being actually fragmented into multiple pieces (we
   refer to these packets as &quot;atomic fragments&quot;).  Such packets
   typically result from hosts that have received an ICMPv6 &quot;Packet Too
   Big&quot; error message that advertises a &quot;Next-Hop MTU&quot; smaller than 1280
   bytes, and are currently processed by some implementations as
   &quot;fragmented traffic&quot;.  Thus, by forging ICMPv6 &quot;Packet Too Big&quot; error
   messages an attacker can cause hosts to employ &quot;atomic fragments&quot;,
   and then launch any fragmentation-based attacks against such traffic.
   This document discusses the generation of the aforementioned &quot;atomic
   fragments&quot;, the corresponding security implications, and formally
   updates RFC 2460 and RFC 5722 such that fragmentation-based attack
   vectors against traffic employing &quot;atomic fragments&quot; are completely
   eliminated.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6man-ipv6-atomic-fragments-03" />
   
</reference>
