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] IPv4 squatting -- Courtesy of AS44050, AS58552
- Previous message (by thread): [anti-abuse-wg] IPv4 squatting -- Courtesy of AS44050, AS58552
- Next message (by thread): [anti-abuse-wg] IPv4 squatting -- Courtesy of AS44050, AS58552
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Thu Dec 3 22:40:30 CET 2020
In message <CA+E3quJWF96vhbDmfX-taQ-AJaTGNfsV9q5kKLLWnmm1F+1GUw at mail.gmail.com>, IP Abuse Research <ipabuseresearch at gmail.com> wrote: >What the >continued findings indicate is a need for IANA and the RIRs to adapt to a >new stage in the resource issuance and governance lifecycle. Since this is >by definition a working group, would it make sense to establish some >metrics to quantify the perceived impact of this phenomenon on abuse? > >If we establish a process to collect these observations of either >"abandoned" resources, prefixes or ASNs, which then re-appear mysteriously >or in the case of an ASN start routing space that is unexpectedly, >"hijack", we can take a step as a community to quantify the phenomenon? This kind of stuff certainly could be done, but this would be a serious research project, requiring sme serious manpower expenditure. That's not to say that it would not be worth the investment. I think it would be. But someone or something would have to step up to make the investment. In the meantime, there is other work, and other steps that would obviously be worthwhile. The first is doing everything possible to try to get RPKI adopted more widely. The second is persuading everyone, certainly including Petersburg Internet, to stop even trying to use an data from RADB. That thing has -zero- security. Any fool can use that at any time to create any route object he/she/it wants. And speaking of which, I for one would love to know if Petersburg Internet was performing -any- checking on those route announcements it was passing on behalf of its customer in this case. If not, then that right there constitutes some "low hanging fruit" in terms of moving things forward so as to prevent repeats of this kind of situation. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] IPv4 squatting -- Courtesy of AS44050, AS58552
- Next message (by thread): [anti-abuse-wg] IPv4 squatting -- Courtesy of AS44050, AS58552
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]