4.4. Processing Rules There are several rules that govern processing of ICMP packets. They can be found in RFC 4443 and are summarized as follows: If a node receives an ICMPv6 error message of unknown type, it must pass it to the upper layer. If a node receives an ICMPv6 informational message of unknown type, it must be silently discarded. As much as possible of the packet that caused the ICMP error message will be included in the ICMP message body. The ICMP packet should not exceed the minimum IPv6 MTU. If the error message has to be passed to the upper-layer protocol, the protocol type is determined by extracting it from the original packet (present in the body of the ICMPv6 error message). In case the protocol type cannot be found in the body of the ICMPv6 message (because there were too many extension headers present in the original packet, and the part of the header that contained the upper-layer protocol type was truncated), the ICMPv6 message is silently discarded.
An ICMPv6 error message must not be sent in the following cases: As a result of an ICMPv6 error message. As a result of an ICMPv6 redirect message. As a result of a packet sent to an IPv6 multicast address. There are two exceptions to this rule: the Packet Too Big message that is used for Path MTU discovery, and the Parameter Problem with the code value 2 for an unrecognized IPv6 option. As a result of a packet sent as a link-layer multicast (exceptions just described apply). As a result of a packet sent as a link-layer broadcast (exceptions just described apply). As a result of a packet whose Source address does not uniquely identify a single node. This could be an IPv6 unspecified address, an IPv6 multicast address, or an IPv6 address known to be an anycast address.
Every IPv6 node must implement a rate-limiting function that limits the rate of ICMPv6 messages it sends, and it should be configurable. If this function is implemented properly, it protects against Denial of Service attacks. |