H On Fri, Jan 30, 2026 at 3:45 PM Joseph Touch via Datatracker < [email protected]> wrote: Document: draft-ietf-intarea-rfc8335bis
Title: PROBE: A Utility for Probing Interfaces
Reviewer: Joseph Touch
Review result: Ready with Nits
The document is generally fine, with the following offered as a suggestion for clarity:
Page 10 should be updated with the text in braces []:
Otherwise, when a node receives an ICMPv4 Extended Echo Request, it
MUST format [the IPv4 header of] an ICMP Extended Echo Reply as follows:
* Don't Fragment (DF) flag is 1
* More Fragments flag is 0
* Fragment Offset is 0
[(the above indicate that the packet is not source fragmented and must not be on-path fragmented)]
* TTL is 255
* Protocol is ICMP
When a node receives an ICMPv6 Extended Echo Request, it MUST format
[the IPv6 header of] an ICMPv6 Extended Echo Reply as follows:
* Hop Limit is 255
* Next Header is ICMPv6
[* No use of the IPv6 Fragmentation Header (i.e., not source fragmented)]
Thanks, Joe, I'll make these updates.
It's surprising to see a suggestion to explicitly list not including the fragmentation header. I wonder if it would be helpful to include other things not to include? Don't include Router Alert? Don't include ASCII art of a rutabaga?
I was adding the IPv6 version of what is explicitly described for IPv4, I.e., a prohibition on source fragmentation.
If there were similar exclusions of rutabagas for IPv4, I’d have added those for IPv6 too.
Joe |
_______________________________________________
Int-area mailing list -- [email protected]
To unsubscribe send an email to [email protected]
