This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] All-Probe Traceroute + detect RFC1918 addresses
- Previous message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
- Next message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bjørn Mork
bjorn at mork.no
Thu Sep 16 11:23:33 CEST 2021
Philip Homburg <philip.homburg at ripe.net> writes: > On 2021/09/15 21:59 , Bjørn Mork wrote: >> I believe it's better to ignore the formalities here and forward those >> packets. It's certainly harmless. At least as harmless as forwarding >> any other ICMP error messages. > > In my opinion this is the wrong approach. If there is a good reason to > violate the standard, then the thing to do is to bring up in the IETF. You are of course correct. Let's hope someone else cares enough to do that :-) An additional argument for allowing the ICMP errors, and only those, is that you can't send back any dest unreachable with "Beyond scope of source address". Bjørn
- Previous message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
- Next message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]