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] 2010-08 New Policy Proposal (Abuse contact information)
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Tue Nov 9 16:07:29 CET 2010
On Tue, Nov 9, 2010 at 14:06, Florian Weimer <fweimer at bfk.de> wrote: > I'm not concerned with data accuracy. It's with availability of the > data itself, given current policies set and implemented by RIPE NCC. I agree that the current IRT model does not scale. I, wrongly, assumed that irts could just be created without fuss as the webupdate interface pretends you can simply add them without any manual verificiation of RIPE. A staged system (created, verified, etc) might make sense for IRT. This would allow the RIPE to verify what they want to verify, yet allow the RIRs to update quickly. Alternatively, the requirements for IRTs could be losened. Finally, an unverified abuse-c could function in parallel to a verified IRT. This obviously introduces other problems. All that being said, I still feel that a mandatory, unified, non-rate-limited abuse contact Is A Good Thing. Richard
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]