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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] WHOIS (AS204224)
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Fri Nov 6 05:54:55 CET 2015
In message <563BF492.2020106 at yahoo.co.uk>, denis <ripedenis at yahoo.co.uk> wrote: >On 06/11/2015 00:58, Ronald F. Guilmette wrote: >> In message <563BDB1C.4020408 at yahoo.co.uk>, >> denis <ripedenis at yahoo.co.uk> wrote: >>> This really does matter. Even with a valid RIPE ASN they cannot 'steal' >>> RIPE address space. >> >> Really??? >> >> If so, that's great news! >> >> Did everyone finally agree to use only fully authenticated route >> announcement protocols while I was sleeping?? Or is BGP fundamentally >> still wide open? > >I am only concerned with the RIPE Database and making sure what is in >there is properly authenticated. I understand. I'm just highlighting that your goals and mine are different. I want to be able to _identify_ the bad guys, no matter what they steal and no matter what mechanisms or subterfuges they may use to steal it. Even if they are making crooked route announcements that have no corresponding route objects in the data base, I still want as many clues as I can lay my hands on to help me figure out who they really are. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]