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/db-wg@ripe.net/
[db-wg] Getting fraudulent entries removed
- Previous message (by thread): [db-wg] Getting fraudulent entries removed
- Next message (by thread): [db-wg] Updating the database via HTTP API - best practices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brian Rak
brak at choopa.com
Thu Apr 5 21:56:27 CEST 2018
On 4/5/2018 2:27 PM, Nick Hilliard via db-wg wrote: > Randy Bush via db-wg wrote: >> and we are supposed to use the high quality ripe irr as authoritative >> data for routing validation? > the current plan is to re-mark all out-of-region route / route6 / autnum > objects with source: RIPE-NONAUTH and to disable creation of these > objects in future. Unless something has been missed, this should be an > improvement over the current situation? > > Nick > Is there going to be a cleanup process for existing entries? For example: https://apps.db.ripe.net/db-web-ui/#/query?bflag&inverse=mnt-by&searchtext=ADMASTER-MNT&source=RIPE&types=route route: 104.143.112.0/20 Not currently advertised, belongs to a managed services provider in the US: https://whois.arin.net/rest/net/NET-104-143-112-0-1/pft?s=104.143.112.0 route: 141.193.96.0/19 Not currently advertised. ARIN claims this belongs to RIPE: https://whois.arin.net/rest/net/NET-141-0-0-0-0 RIPE claims this belongs to... someone else? https://apps.db.ripe.net/db-web-ui/#/query?searchtext=141.193.96.0 route: 192.73.128.0/18 Currently advertised by 30237 ARIN says this belongs to the US Air Force https://whois.arin.net/rest/net/NET-192-73-82-0-1 It largely looks like all of these route objects created by ADMASTER-MNT are (or have been) used for hijacking mostly unused ARIN space.
- Previous message (by thread): [db-wg] Getting fraudulent entries removed
- Next message (by thread): [db-wg] Updating the database via HTTP API - best practices
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]