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] Recommendations for ISPs
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Recommendations for ISPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brian Rak
brak at gameservers.com
Mon Dec 9 22:19:10 CET 2013
Are there detailed instructions for datacenters about how they should be creating abuse-c records? I've been in contact with a datacenter that has one generic abuse-c contact for their organization, but then each individual network has some remarks saying 'please contact this email address instead'. If you email their general abuse email, they tell you to check WHOIS and email the address in the comments. This completely breaks the RIPE abuse contact finder, as well as my scripts to automatically send abuse emails. They don't seem to see the problem with this, so I was hoping for some decent documentation I could show them about it. How should this generally be handled for network providers with lots of reassigned subnets? Am I right in believing this pretty much defeats the purpose of the abuse-c record?
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Recommendations for ISPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]