Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread scott via NANOG
Crap, that was supposed to be private. scott On 10/12/23 11:29 PM, scott via NANOG wrote: UGH, you called me out and I have no defense.  I was thinking of our non-NAT customers. scott On 10/12/23 11:20 PM, Mark Andrews wrote: On 13 Oct 2023, at 08:31, scott wrote: On 10/11/23

Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread scott via NANOG
UGH, you called me out and I have no defense. I was thinking of our non-NAT customers. scott On 10/12/23 11:20 PM, Mark Andrews wrote: On 13 Oct 2023, at 08:31, scott wrote: On 10/11/23 7:47 PM, Mark Andrews wrote: Virtually no home network on the planet has fully functional IPv4

Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread Mark Andrews
> On 13 Oct 2023, at 08:31, scott wrote: > > > > > On 10/11/23 7:47 PM, Mark Andrews wrote: >> Virtually no home network on the planet has fully functional IPv4 available >> to it. > > > Hawaiian Telcom customers have it. No blocks at all. So they don’t use NAT? The internet is a peer

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Niels Bakker
* Laura Smith [Thu 12 Oct 2023, 19:01 CEST]: I mean, most (all ?) of the registries still can't be bothered to validate the information the resource holders post to the database.  Last time I asked, e.g. RIPE about it, they basically said "not my problem guv" , pointed me to some policy documen

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Delong.com via NANOG
RIPE != ARIN RIPE has a very lessez faire attitude towards network abuse and always has. It’s rather unfortunate. ARIN, OTOH, has a clear understanding of their mandate, and they won’t pursue abuse outside of that mandate (e.g. general SPAM complaints, DDOS, etc.), but they will pursue complai

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Andrew Latham
As mentioned weekly email complia...@arin.net with details. On Wed, Oct 11, 2023 at 8:58 PM Eric Kuhnke wrote: > Is anyone else receiving spam from this organization? Based on the > contents of the cold solicitations they are sending us, and the addresses > being sent to, they have scraped ARIN

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Mel Beckman
Laura, just a couple of weeks ago, I reported and ARIN abuse here on NANOG, and ARIN responded immediately, contacting the offender and getting them to stop. The system works, and ARIN has the power to deter repeat offenders. -mel > On Oct 12, 2023, at 10:01 AM, Laura Smith via NANOG wrote:

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Laura Smith via NANOG
Honestly Mike I don't think they care. I mean, most (all ?) of the registries still can't be bothered to validate the information the resource holders post to the database.  Last time I asked, e.g. RIPE about it, they basically said "not my problem guv" , pointed me to some policy document that

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Tom Beecher
Sure. I have no issues ARIN handling what is reported to them. That only works if victims report spam and compare notes. > I don't agree with the 'compare notes' part. That's ARIN's job in the processing of reports. On Thu, Oct 12, 2023 at 12:01 PM Mel Beckman wrote: > Tom, > > When an ARIN me

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Mike Hammett
Do we know if the organizations with key Internet resources (ARIN, RIPE, PeeringDB, etc.) have any honeypots in their arsenal? Obviously, publicly knowing about it kind of defeats the purpose of it, but that might be a way to help be proactive - make fake entries with unique contact information

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Mel Beckman
Tom, When an ARIN member violates their agreement and spams from ARIN’s databases, it’s not just an “Internet is fertile ground” deal. It’s a betrayal of a legal trust, one that demands accountability. I’m quite happy that ARIN promptly responds to these abuses, and gets results. That only work

Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread Owen DeLong via NANOG
> On Oct 12, 2023, at 01:42, Willy Manga wrote: > > . > >> On 12/10/2023 10:00, Owen DeLong wrote: >> [...] However, IF YY is paying attention, and YY wants to advertise 2001:db8::/32 as well as allow 2001:db8:8000::/36 and 2001:db8:f000::/36, I would expect AS YY would gene

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread Tom Beecher
> > It's ridiculous that they resort to scraping public lists and DBs to try > and achieve what they're attempting to do. > Everyone is always looking for information they can use to advance some agenda or purpose. The internet is fertile ground for that. Always has been, always will be. Not taki

Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread Dale W. Carder
Thus spake Delong.com (o...@delong.com) on Wed, Oct 11, 2023 at 12:44:35PM -0700: > > > > On Oct 11, 2023, at 11:50, Dale W. Carder wrote: > > > > Thus spake Delong.com via NANOG (nanog@nanog.org) on Tue, Oct 10, 2023 at > > 04:52:07PM -0700: > >> However, IF YY is paying attention, and YY wa

Re: constraining RPKI Trust Anchors

2023-10-12 Thread Joelja Bogus
Sent from my iPhone > On Oct 11, 2023, at 15:29, Randy Bush wrote: > >  >> >> So while each RP should be able to make policy decisions based on its >> own local criteria, managing a default set of constraints is something >> that is best done centralized. Who do you envision should manage th

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

2023-10-12 Thread John Stitt
Our organization has also received cold contact emails from this company, and their unsubscribe link doesn’t appear to have slowed them down. They now hit my junk folder. John Stitt HES Energynet On Oct 11, 2023, at 6:56 PM, Peter Potvin via NANOG wrote:  Definitely have received this same s

Re: maximum ipv4 bgp prefix length of /24 ?

2023-10-12 Thread Willy Manga
. On 12/10/2023 10:00, Owen DeLong wrote: [...] However, IF YY is paying attention, and YY wants to advertise 2001:db8::/32 as well as allow 2001:db8:8000::/36 and 2001:db8:f000::/36, I would expect AS YY would generate ROAs for 2001:db8::/32 with ORIGIN-AS=YY MAXPREFIXLEN=36