Send ICMPv6 error messages in response to IPv6 packets that cannot be handled
Open
area: networking
priority: p2
type: enhancement
- Dominant language
- Go
- Stars
- 19.3k
- Forks
- 2k
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 264
Description
Currently, the stack does not send ICMPv6 errors in response to IPv6 packets that cannot be parsed/handled.
An example is when the Next Header field is unrecognized (e.g. not TCP, UDP or a known extension header). This scenario is described in RFC 8200 section 4, which requires an node to send an ICMP Parameter Problem message to the source of the packet, with an ICMP Code value of 1 ("unrecognized Next Header type encountered")...
Contributor guide
Assessment
This issue has not been assessed yet.