[as112-ops] new prefix for AS112? (2a0b:4e04:6666::/48 in RIPE with various origins it should not have)

[Jeroen Massar]

> On 16 Oct 2024, at 09:08, Radu Anghel via as112-ops <as112-ops at dns-oarc.net> wrote:
> 
> 
> From: Radu Anghel <radu.anghel at xindi.ro>
> Subject: Re: [as112-ops] new prefix for AS112? (2a0b:4e04:6666::/48 in RIPE with various origins it should not have)
> Date: 16 October 2024 at 09:08:39 CEST
> To: as112-ops at lists.dns-oarc.net
> 
> 
> Hi Jeroen,
> 
> This looks like a 'personal' ASN, I am sure this is just an experiment done for a learning purpose and it greatly helps the Internet at large. Perhaps we should be more understanding and supportive with this type of initiatives. /s

As you have been told over and over again, and will have to be told over and over again:

There are many examples to be found of "corporations" creating issues on the Internet.

And as you can see, this issue has been resolved swiftly by contacting the operator, no such case in other such examples of wrong IRR/whois data.


> Who knows, it might even produce academic publications ;)

Fortunately no real conference will accept bullying of that kind. Also, I think it is against university academic policies to do so.

I have no idea why you need to call out single people, maybe as you assume they have no legal support to counteract your harassment?

As you are a non-operator, I suggest maybe not involving yourself in operations until you have done operations.


Please find something else to do with your time on this planet, there are lot more technical and useful problems to solve.


As many older network operators would say: /plonk.


Regards,
 Jeroen