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
Fri Sep 17 15:43:29 CEST 2021
Gert Doering <gert at space.net> writes: > On Fri, Sep 17, 2021 at 03:23:24PM +0200, Bjørn Mork wrote: >> Using RFC1918 on links in your own network is fine. And having >> them show up in traceroutes is a feature. > > s/feature/sign of sloppy network design, and a RFC1918 violation/ Sorry for being slow. but I need a direct reference to the paragraph this violates. Not that I'm against violating some parts of RFC1918 where required. The part disallowing leakage of RFC1918 into DNS is too impractical and unjustified. 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 ]