<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><blockquote type="cite" cite="mid:A7E5DD50-FE84-46FC-87FE-106639A789F8@consulintel.es" class=""><pre class="moz-quote-pre" wrap="" style="font-size: 15px;">7) The PDP can’t avoid having competing proposals, it is good for the process and the community to investigate several choices. It is a way for an author or a group of them to block the community progress. If I've an idea and send a proposal and the community don't like it but I'm not improving the text along the discussions, a possible way out is an alternative proposal.</pre></blockquote><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">Competing proposals have not brought constructive outcomes for our community and we all concur to that. To address the problem you raised above, section 3.5.1.1 has the following provision “Once adopted by the working group, the initiator(s) grant(s) all rights to the working group and the proposal becomes a community document.”</p></div></blockquote><br class="">This simply isn’t true. You may not like how we got there, you may not like the outcome, but competing proposals have definitely led to constructive outcomes in the past.</div><div><br class=""></div><div>For example, a competing proposal led to the abandoment of the so-called SL-BIS proposal. That was most definitely a constructive outcome.</div><div><br class=""></div><div>I’m not 100% convinced that a competing (somewhat contrary) proposal isn’t just the thing needed to help steer the discussion around the resource review proposal, either.</div><div><br class=""></div><div>Prohbiiting proposals is a clear channel for PDP DOS. If someone wants to avoid positive progress on a topic, all they need to do is submit a negative proposal and keep “updating it” periodically without fully addressing anyone’s concerns. Since a competing proposal would not be allowed, they can thus preclude the community from advancing a more positive policy. Since there is no mechanism for the community to reject a proposal and it can remain on the docket so long as the author(s) continue to update it once per year, it becomes trivial to preserve the status quo for any (or even all) portions of the CPM as long as an author desires.</div><div><br class=""></div><div>In fact, under that proposal, it could even become trivial for one individual to block any change to the PDP to get out of that situation.</div><div><br class=""></div><div>This is a very serious flaw with the current proposed PDP Bis.</div><div><br class=""></div><div><blockquote type="cite" class=""><blockquote type="cite" cite="mid:A7E5DD50-FE84-46FC-87FE-106639A789F8@consulintel.es" class="" style="font-size: 15px;"><pre class="moz-quote-pre" wrap="">10) Impact analysis should include “more”, but just objective inputs, and not bias the community.</pre></blockquote><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">more than the followings ?</p><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">• AFRINIC Ltd’s understanding of the proposed policy</p><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">• Impact on the registry and Internet Number Resources</p><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">• Impact on AFRINIC Ltd’s operations/services</p><p style="margin-bottom: 0cm; line-height: 12px; font-size: 15px;" class="">• Legal impact We trust staff to be objective in their analysis and community has the right to question and discuss the staff analysis</p></blockquote><div><br class=""></div>Yes… The analysis should also include the following:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>+<span class="Apple-tab-span" style="white-space:pre"> </span>Cost to AfriNIC to implement/sustain the policy (revenue impact, implementation costs, administration costs)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>+<span class="Apple-tab-span" style="white-space:pre"> </span>Any identifiable ambiguities or other flaws in the policy language which can cause difficulty in implementation</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>+<span class="Apple-tab-span" style="white-space:pre"> </span>Feasibility of implementation and timeline after board ratification (how long will it take to implement, what is required</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>for implementation)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>+<span class="Apple-tab-span" style="white-space:pre"> </span>Any risks to the community or the organization identified in implementation of the policy<br class=""><blockquote type="cite" class=""><blockquote type="cite" cite="mid:A7E5DD50-FE84-46FC-87FE-106639A789F8@consulintel.es" class="" style="font-size: 15px;"><pre class="moz-quote-pre" wrap=""></pre></blockquote></blockquote></div><div>Owen</div><div><br class=""></div><br class=""></body></html>