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] Options for extending "abuse-c:"
- Previous message (by thread): [anti-abuse-wg] RIPE 67 AA-WG Meeting Minutes
- Next message (by thread): [anti-abuse-wg] [db-wg] Options for extending "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Tue May 6 17:01:52 CEST 2014
Dear colleagues, At RIPE 67 in Athens, the RIPE NCC agreed to take another look at the implementation of RIPE Document ripe-563, "Abuse Contact Management in the RIPE Database." Two issues have been identified that are seen to be difficult to handle with the current model - partitioned subnets within one organisation and adding abuse contacts to more specifics for End Users. The RIPE NCC has considered these two issues and found what we believe to be practical solutions, available within the current model. More information about these solutions and the implementation of "abuse-c:" is available on RIPE Labs: https://labs.ripe.net/Members/denis/suggestions-for-improving-abuse-handling This topic will also be raised during the Anti-Abuse Working Group session at RIPE 68 in Warsaw. Regards, Denis Walker Business Analyst RIPE NCC Database Team
- Previous message (by thread): [anti-abuse-wg] RIPE 67 AA-WG Meeting Minutes
- Next message (by thread): [anti-abuse-wg] [db-wg] Options for extending "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]