Search RPD Archives
[rpd] RPD : Prolicy proposal "Internet Number Resources review by AFRINIC" informations update
Marcus K. G. Adomey
madomey at hotmail.com
Fri Apr 12 14:16:49 UTC 2019
"Non-consensus" but most importantly "consensus" in our context of rough consensus must be recognised.
We shall also recognise decisions made by those we selected to decide on consensus and widely use the recourse mechanisms and only when necessary.
In the case of this proposal, and the archives can remind, if you forgot as, you claim to not have interest in this proposal, they made several time, decisions on consensus and we all know what happened.
If this community can not work out a consensual policy on INRs review, I wonder what value does it bring in and what is mission and role of AFRINIC.
From: Sander Steffann <sander at steffann.nl>
Sent: Thursday, April 11, 2019 8:32 PM
To: Marcus K. G. Adomey
Cc: rpd >> AfriNIC Resource Policy
Subject: Re: [rpd] RPD : Prolicy proposal "Internet Number Resources review by AFRINIC" informations update
> You chose to not positively impact the history being written for AFRINIC. You now persist in denying AFRINIC community the ability, like other RIRs to enforce accountability, best practices and adopt an INR review policy.
> Why do you want to see responses to the fanciful points on a policy proposal which you buried long ago?
> This is a PDP working group where participants are expected to discuss and provide suggestions and texts to improve proposals. Please bring texts and suggestions.
I have no interest in the policy itself. I don't mind if it passes or fails. But I do want to see Afrinic strong in making its own policy, and for that consensus building has to be done properly, non-consensus has to be recognised, and discussions should be about content, not personal.
When I was a working group chair I have had to declare non-consensus on policies that I thought would be good for the community. In a consensus-based community you don't always get the changes you would like through, but that's the way it is. The default is always to stay with the current policy. That can make it difficult to change things, but it also provides a lot of stability.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the RPD