nanog mailing list archives
Re: route: 0.0.0.0/32 in LEVEL3 IRR
From: Frank Habicht <geier () geier ne tz>
Date: Thu, 1 Feb 2024 10:19:55 +0300
On 01/02/2024 01:45, Tom Beecher wrote:
Seems a bit dramatic. Companies all over the world have been using other people's public IPs internally for decades. I worked at a place 20 odd years ago that had an odd numbering scheme internally, and it was someone else's public space. When I asked why, the guy who built it said "Well I just liked the pattern."If you're not announcing someone else's space into the DFZ, or otherwise trying to do anything shady, the three letter agencies aren't likely to come knocking. Doesn't mean anyone SHOULD be doing it, but still.
Well...If you're using 20.20.20.0/24 which is not "yours" (as I've seen happen), then certainly your customers can't get to the real 20.20.20.x And even if that's not announced and used /today/ - this can change quickly...
Frank
Current thread:
- route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Dave Taht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Rubens Kuhl (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Tom Beecher (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Owen DeLong via NANOG (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Rubens Kuhl (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Dave Taht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Job Snijders via NANOG (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 30)