An ICMP Echo request from the DHCP server to the IP address its about to allocate is used to determine if the IP address about to be assigned is already in use on the network.
If a response is received from that IP the DHCP server will assign a different address.
The ARP request on the newly received address from the client would do the same, check if another device is using that address and responding to ARP. If so it knows the address it received is already in use.
The RFC you linked to does mention later on:
Servers need not reserve the offered network address, although the protocol will
work more efficiently if the server avoids allocating the offered
network address to another client. When allocating a new address,
servers SHOULD check that the offered network address is not
already in use; e.g., the server may probe the offered address
with an ICMP Echo Request. Servers SHOULD be implemented so that
network administrators MAY choose to disable probes of newly
allocated addresses.
I am not certain if all DHCP servers implement this requirement but as far as I am aware there is no other way a DHCP server could reliably become aware of another device using an IP that is available in its DHCP pool.
Also from the same RFC regarding ARP from the clients:
if the client is on a network that
supports ARP, the client may issue an ARP request for the suggested
request. ... If the network address appears to be in use, the client MUST send a
DHCPDECLINE message to the server
Best Answer
On ASR9k running IOS-XR ICMP packets destined to the router are handled by LTPS (Local Packet Transport System). I believe that under normal circumstances the entire processing of such packet is done on ingress linecard CPU.
Once the NP on ingress LC detects the packet is for-us, it hands it over to LTPS. LTPS will perform policing, conforming packets are then passed either to LC CPU or RP.
The counters for different kinds of traffic for particular LC can be checked with following command: