draft-ietf-6man-deprecate-atomfrag-generation-02.txt   draft-ietf-6man-deprecate-atomfrag-generation-03.txt 
IPv6 maintenance Working Group (6man) F. Gont IPv6 maintenance Working Group (6man) F. Gont
Internet-Draft SI6 Networks / UTN-FRH Internet-Draft SI6 Networks / UTN-FRH
Updates: 2460, 6145 (if approved) W. Liu Updates: 2460 (if approved) W. Liu
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: January 5, 2016 T. Anderson Expires: January 5, 2016 T. Anderson
Redpill Linpro Redpill Linpro
July 4, 2015 July 4, 2015
Deprecating the Generation of IPv6 Atomic Fragments Deprecating the Generation of IPv6 Atomic Fragments
draft-ietf-6man-deprecate-atomfrag-generation-02 draft-ietf-6man-deprecate-atomfrag-generation-03
Abstract Abstract
The core IPv6 specification requires that when a host receives an The core IPv6 specification requires that when a host receives an
ICMPv6 "Packet Too Big" message reporting an MTU smaller than 1280 ICMPv6 "Packet Too Big" message reporting an MTU smaller than 1280
bytes, the host includes a Fragment Header in all subsequent packets bytes, the host includes a Fragment Header in all subsequent packets
sent to that destination, without reducing the assumed Path-MTU. The sent to that destination, without reducing the assumed Path-MTU. The
simplicity with which ICMPv6 "Packet Too Big" messages can be forged, simplicity with which ICMPv6 "Packet Too Big" messages can be forged,
coupled with the widespread filtering of IPv6 fragments, results in coupled with the widespread filtering of IPv6 fragments, results in
an attack vector that can be leveraged for Denial of Service an attack vector that can be leveraged for Denial of Service
 End of changes. 2 change blocks. 
2 lines changed or deleted 2 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/