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] objection to RIPE policy proposal 2016-01
- Previous message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
aawg at c4inet.net
Mon Mar 7 23:12:45 CET 2016
On Mon, Mar 07, 2016 at 09:08:47AM +0000, Brian Nisbet wrote: >I may have missed the logic behind this. Any RIPE WG can make >policy, why should AA-WG be any different? aawg is not different, the problem is precisely that any WG can make policy. There should be ONE list on which policy is debated and consensus, if any, is determined. Which is the way other RIRs work and which is the way RIPE was *supposed* to work before a lot of empire-building happened (see how apwg is the only list with "policy" in the name?) I do not want to be subscribed to every godsdamn mailing list @ripe.net, but I *have* to because otherwise some policy will be imposed on me that I never even heard about and that supposedly "has reached consensus". rgds, Sascha Luck
- Previous message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]