This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] 196.52.0.0/14 revoked, cleanup efforts needed
- Previous message (by thread): [anti-abuse-wg] 196.52.0.0/14 revoked, cleanup efforts needed
- Next message (by thread): [anti-abuse-wg] 196.52.0.0/14 revoked, cleanup efforts needed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Wed Jan 20 14:57:43 CET 2021
Cynthia Revström via anti-abuse-wg wrote on 20/01/2021 13:40: > First of all this mailing list is not intended to discuss individual > cases of abuse (especially ones not related to the RIPE NCC), but rather > to discuss and develop new methods for dealing with it in general. > (Brian, please correct me if I am wrong here) > > Nonetheless, while I certainly don't represent them, I believe RADb does > delete objects if you email them and can show proof that you are the > holder of that IP space. there is a RIPE policy aspect to this, namely what to do with RIPE IRRDB objects of address space which is revoked by other RIRs. In this specific situation, there are a bunch of route: entries in the RIPE-NONAUTH DB, and maybe it would be good for the DBWG to have a think about this? http://irrexplorer.nlnog.net/search/196.52.0.0/16 http://irrexplorer.nlnog.net/search/196.53.0.0/16 http://irrexplorer.nlnog.net/search/196.54.0.0/16 http://irrexplorer.nlnog.net/search/196.55.0.0/16 Ostap, can you bring this up on DB-WG? Nick
- Previous message (by thread): [anti-abuse-wg] 196.52.0.0/14 revoked, cleanup efforts needed
- Next message (by thread): [anti-abuse-wg] 196.52.0.0/14 revoked, cleanup efforts needed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]