On 22/01/2018 15:09, Nick Hilliard wrote:
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.
No, it isn't. It's a statement that the process has many steps and that the NCC both say they do and clearly do whatever they can to not reach the termination point of the process. I'm not saying it could never happen, I'm saying that it if happens it's may have been started by 2017-02 but the deregistration would happen because over ~9 months the NCC would be unable to in contact with the LIR in any way. "The RIPE NCC will validate the “abuse-mailbox:” attribute at least annually. Where the attribute is deemed incorrect, it will follow up in compliance with relevant RIPE Policies and RIPE NCC procedures." No new procedures are being proposed here, no new powers. This would be invalid information in the database.
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.
Well, it's stated in the impact analysis rather than the original (or even version 2) policy text by the authors. The policy text "simply" says that other policies will be followed. If there's work to do on them, that is arguably a different matter and this affects far more than just 2017-02. But so noted. Brian Co-Chair, RIPE AA-WG