Newbie Questions: How-to remove spurious IRR records (and keep them out for good)?

Sat Oct 31 01:26:11 UTC 2020

YMMV, but my take:
1 - You should worry a little, but not much. Filters allowing unwanted
announcements might be created using these erroneous IRR records, but
they won't do any damage by themselves. An actual wrong BGP
announcement is required for any damage to happen, and even without
those IRR records, a wrong announcement will cause some havoc since
not everyone builds filters based on IRR and not everyone runs RPKI
validation.
2 - Most IRR databases will take reports from the RIR-registered
contact of the block seriously. Some databases will react faster than
others; for instance, in TC any such objects will be removed upon
knowledge and if the maintainer recreates those objects, the
maintainer may be permanently excluded from the database.
3 - Unfortunately there is not much you can do since this is caused by
relaxed submission filtering at IRR databases, The RIR-connected IRR
databases are usually very good in preventing such, but the
independent ones usually are not. IRRd versions prior to v4 (thanks
NTT for v4) are also more prone to accept non-compliant records and
can only eliminate them after inclusion.

Rubens

On Fri, Oct 30, 2020 at 10:11 PM Pirawat WATANAPONGSE <pirawat.w at ku.th> wrote:
>
>
> Dear Guru(s),
>
>
> I am seeking advice concerning someone else announcing IRR records on resources belonging to me.
> [I was referred to this mailing list from the DNS-OARC community.]
>
> Context:
> I have already registered all my IP address blocks with ROA/RPKI
> [evidence: https://stat.ripe.net/widget/as-routing-consistency#w.resource=AS9411]
> However, HE reports a lot of spurious IRR records on my resources
> [example: https://bgp.he.net/net/158.108.0.0/16#_irr]
>
> Question #1:
> Should I worry about those spurious records [Yes | No | Depends]?
> My fear is that other sites might accept those records without checking and thus be misled somewhere else, since ROV is not yet the behavior-in-majority.
> My other reasoning is that, if we are not going to keep accurate records, why bother keeping them at all anyway.
>
> Question #2:
> What can I do about it [in case the answer to Question #1 is Yes]?
> Should I notify those Database Admins? Will they consider me a nuisance?
> And most importantly: Will they erase those records for me, or will they just ignore me?
>
> Question #3:
> Did I not do something that can prevent those spurious records from happening in the first place?
> And, anything I can do now to prevent it from ever happening again?
>
>
> Thanks in advance for your advice(s),
>
> Pirawat.
>