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] [routing-wg] An arrest in Russia
- Previous message (by thread): [anti-abuse-wg] [routing-wg] An arrest in Russia
- Next message (by thread): [anti-abuse-wg] [routing-wg] An arrest in Russia
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Fri Jan 3 22:40:41 CET 2020
In message <20200103165918.GL72330 at Space.Net>, Gert Doering <gert at space.net> wrote: >On Fri, Jan 03, 2020 at 04:14:07PM +0000, Suresh Ramasubramanian wrote: >> So the RIR has absolutely no role in maintaining say IRR data? I agree >validating LOAs and such for routing changes would be on providers. Though >if the changes were to be made in IRR data who would validate it? > >IRR data is authenticated by registry data in RIPE land, if the resource >holder chooses so. Short story. > >So, nobody can create routes for, say, my address space unless I >authorize that. Yes. Nowadays, the RIPE IRR is better in this respect than any other IRR that I am aware of. Don't even get me started about RADB! They don't check anything, and there are stale entires in there from 10+ years go for routes to bogons. As far as I can tell, there is zero quality control and zero maintenance, the result being that it has become one big playground for routing crooks. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] [routing-wg] An arrest in Russia
- Next message (by thread): [anti-abuse-wg] [routing-wg] An arrest in Russia
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]