<p dir="ltr">Hello Hans kindly find my response inset:</p>
<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.<br>
On 3 Jan 2015 16:20, "Hans Petter Holen" <<a href="mailto:hph@oslo.net">hph@oslo.net</a>> wrote:<br>
><br>
> Hi Seun,<br>
> I am not on the CRISP team, but will add my thoughts on your suggestion:<br>
><br>
> On 03.01.15 07.47, Seun Ojedeji wrote:<br>
>><br>
>> - I made a suggestion on minor changes on the gPDP, may I also know what the crisp has determined about that?<br>
><br>
> First, as I read the charter for the CRISP, reviewing the Global Policy Development Process is outside the charter. <br>
><br>
Could you refer me to a section that indicated that in the charter? If that is indeed the case then there is no need to further on this discussion except that I will say gPDP is one of the existing accountability measure and looking to strengthen existing accountability measure should be the main goal of this transition.</p>
<p dir="ltr">> I also think it is unwise to open up the Global Policy Development Process at the same time as we are discussing the implementation.<br>
><br>
I am not sure I get your point, do you care to explain further? why is discussing gPDP unwise, I mean could you tell me a better time to discuss it; is there any existing formal process to discuss gPDP update?</p>
<p dir="ltr">> So my strong opinion is that changes to the Global Policy Development Process and the ASO MOU, should in my opinion be handled separately from the NTIA transition.<br>
><br>
Isn't one of the numbers accountability source referred to by NTIA in it's contract the gPDP? So why would you say reviewing the existing mechanism with the possibility of improving on it out of this NTIA transition scope. Personally I would even say adding SLA as attachment C to the ICANN/NRO MOU and including a few lines in the agreement to reflect the transition changes would have been a neater way to reflect this transition in the first place.</p>
<p dir="ltr">> So to your proposal:<br>
><br>
> I had a look trough the archives and assume you refer to:<br>
><br>
> On 19.12.14 07.20, Seun Ojedeji wrote:<br>
>><br>
>> Finally on a related note, i suggest a minor update of section 10 of the gPDP as follow:<br>
>><br>
>> In case Step 9 (c), should at least two of the RIRs agree that changes need to be made<br>
><br>
> If I get this right you are suggesting that two, rather than one, RIRs has to agree with a simple majority of the ICANN boards request to make changes to a policy proposal, for the proposal to be sent back to step 1 in the policy development process. In the event that the ICANN board.<br>
><br>
yes.... in the event that ICANN board disagree with the policy proposal, it should require at least 2 RIR in agreement to take us back to step 1. My rationale for this is that while a number of 1 out of 4 RIR may be fine as at the time the agreement was signed. However now that we have 5 RIRs, ensuring the view of the majority wins is important hence my reason for suggesting the minor update.</p>
<p dir="ltr">> Personally I would rather see ICANN giving input much earlier in the process rather than having this power at the very end of the process, so I think this proposal requires more detailed discussion in all regions to archive consensus on changes to the Global PDP.<br>
><br>
Could you clarify your statement above. Kindly note that I am referring to global policy proposals that have achieved entire RIR community consensus and then awaits ICANN board approval.</p>
<p dir="ltr">Regards<br>
><br>
> Context for reference:<br>
><br>
> Refering to the ASO MOU attachment A, <br>
> <a href="http://archive.icann.org/en/aso/aso-mou-attachmentA-29oct04.htm">http://archive.icann.org/en/aso/aso-mou-attachmentA-29oct04.htm</a><br>
><br>
> 9. Within 60 days of receipt of the proposed policy, including such consultation as may occur in Step 8, the ICANN Board may either:<br>
><br>
> accept the proposal by a simple majority vote; or<br>
> reject the proposed policy by a supermajority (2/3) vote; or<br>
> by a simple majority vote request changes to the proposed policy; or<br>
> take no action.<br>
> 10. If the ICANN Board takes no action (that is, fails to take actions (a), (b) or (c) in Step 9) within the 60-day window, the proposed policy is deemed to be accepted by the ICANN Board and it becomes global policy. <br>
><br>
> In case Step 9 (c), should at least one of the RIRs agree that changes need to be made, the status of the proposed policy reverts to Step 1. <br>
><br>
> If none of the RIRs accept the case for changes, then the proposed policy continues to Step 11.<br>
><br>
><br>
><br>
> -- <br>
> Hans Petter Holen<br>
> Mobile +47 45 06 60 54 | <a href="mailto:hph@oslo.net">hph@oslo.net</a> | <a href="http://hph.oslo.net">http://hph.oslo.net</a><br>
><br>
><br>
> _______________________________________________<br>
> ianaxfer mailing list<br>
> <a href="mailto:ianaxfer@nro.net">ianaxfer@nro.net</a><br>
> <a href="https://www.nro.net/mailman/listinfo/ianaxfer">https://www.nro.net/mailman/listinfo/ianaxfer</a><br>
><br>
</p>