%% You should probably cite rfc8021 instead of this I-D.
@techreport{ietf-6man-deprecate-atomfrag-generation-05,
    number =    {draft-ietf-6man-deprecate-atomfrag-generation-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-6man-deprecate-atomfrag-generation/05/},
    author =    {Fernando Gont and Will (Shucheng) LIU and Tore Anderson},
    title =     {{Generation of IPv6 Atomic Fragments Considered Harmful}},
    pagetotal = 10,
    year =      2016,
    month =     jan,
    day =       20,
    abstract =  {RFC2460 requires that when a host receives an ICMPv6 "Packet Too Big" message reporting an MTU smaller than 1280 bytes, the host includes a Fragment Header in all subsequent packets sent to that destination, without reducing the assumed Path-MTU. The simplicity with which ICMPv6 "Packet Too Big" messages can be forged means that an attacker can leverage this functionality (the generation of IPv6 atomic fragments) to trigger the use of fragmentation for any arbitrary IPv6 flow, and subsequently perform any fragmentation-based attack. This document discusses the security implications of the generation of IPv6 atomic fragments and a number of interoperability issues associated with IPv6 atomic fragments, and concludes that the aforementioned functionality is undesirable, thus documenting the motivation for removing this functionality in the revision of the core IPv6 protocol specification {[}I-D.ietf-6man-rfc2460bis{]}.},
}