> We're back to this again... more of our space is being hijacked using > a RIPE IRR entry: > > route: 108.160.128.0/20 > descr: 2nd route > origin: AS19529 > mnt-by: ADMASTER-MNT > created: 2017-11-15T17:41:46Z > last-modified: 2017-11-15T17:41:46Z > source: RIPE > > Same ASN. > > Can RIPE purge all the IRR entries created by this maintainer? They > don't appear to be legitimate.
and we are supposed to use the high quality ripe irr as authoritative data for routing validation?
