Your customer wants to migrate their network from IPv4 to IPv6. They currently have Control Plane Policing deployed to protect their network devices from illegitimate ICMP traffic flooding. How do you

ICMPv6 must still be policed to protect the control plane from flooding attacks; the expanded LAN functionality is a reason to tune carefully, not a justification to omit policing entirely.

ICMPv6 serves expanded roles compared to ICMPv4, including Neighbor Discovery Protocol (NDP, which replaces ARP) and Multicast Listener Discovery (MLD, which replaces IGMP). If the CoPP rate limit is set too aggressively, these essential control-plane functions can be disrupted and break IPv6 connectivity; if too permissive, the device remains exposed to floods. The policy must be carefully tuned to protect the control plane while allowing sufficient ICMPv6 for NDP and MLD to function correctly.

No standard guidance mandates policing ICMPv6 at a lower absolute rate than ICMPv4 based solely on packet size; rate limits must reflect expected legitimate traffic volumes and functional requirements.

The ICMPv4 and ICMPv6 policies cannot simply remain identical because ICMPv6 carries NDP and MLD traffic that was handled by separate protocols in IPv4, requiring different and more careful rate-limit thresholds.