Connected: An Internet Encyclopedia
4.3.2.7 When Not to Send ICMP Errors

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1812
Up: 4. INTERNET LAYER - PROTOCOLS
Up: 4.3 INTERNET CONTROL MESSAGE PROTOCOL - ICMP
Up: 4.3.2 GENERAL ISSUES
Prev: 4.3.2.6 Source Route
Next: 4.3.2.8 Rate Limiting

4.3.2.7 When Not to Send ICMP Errors

4.3.2.7 When Not to Send ICMP Errors

An ICMP error message MUST NOT be sent as the result of receiving:

Furthermore, an ICMP error message MUST NOT be sent in any case where this memo states that a packet is to be silently discarded.

NOTE: THESE RESTRICTIONS TAKE PRECEDENCE OVER ANY REQUIREMENT ELSEWHERE IN THIS DOCUMENT FOR SENDING ICMP ERROR MESSAGES.

DISCUSSION

These rules aim to prevent the broadcast storms that have resulted from routers or hosts returning ICMP error messages in response to broadcast packets. For example, a broadcast UDP packet to a non- existent port could trigger a flood of ICMP Destination Unreachable datagrams from all devices that do not have a client for that destination port. On a large Ethernet, the resulting collisions can render the network useless for a second or more.

Every packet that is broadcast on the connected network should have a valid IP broadcast address as its IP destination (see Section [5.3.4] and [INTRO:2]). However, some devices violate this rule. To be certain to detect broadcast packets, therefore, routers are required to check for a link-layer broadcast as well as an IP-layer address.

IMPLEMENTATION

This requires that the link layer inform the IP layer when a link-layer broadcast packet has been received; see Section [3.1].


Next: 4.3.2.8 Rate Limiting

Connected: An Internet Encyclopedia
4.3.2.7 When Not to Send ICMP Errors