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] Adding a "Security Information" contact?
- Previous message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
- Next message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alessandro Vesely
vesely at tana.it
Mon Jun 20 18:19:22 CEST 2022
On Tue 07/Jun/2022 20:14:49 +0200 Ángel González Berdasco via anti-abuse-wg wrote: > Gert Doering wrote: >> >> "whois, as in 'this particular way users interface with the DB'" :-) >> >> (I'm aware it's the server doing this - which makes changing the >> implementation easier, as it's "just one place" - but in the end, >> "it needs to be done" which was the point I tried to make ;-) ) > > Indeed. And many other tools interacting with the RIPE DB to find abuse > contacts, I'm afraid. The uptake of those new attributes would > necessarily be relatively slow. People who send not only to RIPE IPs will never uptake, unless this is going to be a global change, including RDAP specs. Best Ale --
- Previous message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
- Next message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]