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] Notice: Fradulent RIPE ASNs
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Tue Jan 22 10:57:54 CET 2013
Suresh, [ using your top-posting style in this reply, to avoid "crossing the streams" ] We can have transparent processes, that have no "teeth" as you say. We can also have strict policies that are enforced in secret. Both transparency and effectiveness are important. I do think ISPs are more likely to support a fair and transparent policy that will punish abusers than they will to support a fair and secretive policy that will punish abusers, because they will have no guarantees that they will be safe under such a system. Cheers, -- Shane On Tuesday, 2013-01-22 07:20:26 +0530, Suresh Ramasubramanian <ops.lists at gmail.com> wrote: > I think we are missing the main point rfg raised and going around in > circles about transparency. > > How do we give enough teeth to ripe ncc's audit processes, and it's ip > allocation processes, especially through LIRs, so that the issue we > are concerned about is mitigated?
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]