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] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Previous message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Jan 22 16:09:30 CET 2018
Brian Nisbet wrote: > I believe the NCC have stated very clearly how incredibly unlikely > deregistration of resources would be and I honestly don't believe the > exaggeration for emphasis or otherwise is useful. this seems to be a statement that just because an extreme policy compliance enforcement mechanism hasn't been used in the past, it would be appropriate to maintain it as a compliance enforcement mechanism in the future for this situation. This is a deeply non-compelling argument. The core issue is proportionality. We're talking here about a tickbox compliance mechanism to further the aims of a fuzzily stated principal where the authors have taken a potshot at and sunk their own rationale. The final sanction for non-compliance has - unusually for a RIPE policy document - been reiterated as termination of contract and withdrawal of resources. For most LIRs, this would cause either serious or terminal operational problems. There is nothing proportional about this, and because of a gross lack of proportionality, the policy should not be adopted in its current form. Nick
- Previous message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]