<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 24, 2022, at 06:55, JORDI PALET MARTINEZ via RPD <<a href="mailto:rpd@afrinic.net" class="">rpd@afrinic.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">Hi Dewole,<o:p class=""></o:p></span></div><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">And as I said many times, and it match your analysis, the bylaws are VERY BROKEN. It can be easily said that 11.3 and 15.3 of bylaws are contradictory, but this is not the only broken point.<o:p class=""></o:p></span></div><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">The bylaws are encroaching the community sovereignty in many aspects, which means that the RIR is not complying with the ICP-2.</span></div></div></div></blockquote><div><br class=""></div>The time to raise any objections under ICP-2 was when ICANN was considering AFRINIC’s accreditation as an RIR under the ICANN administered IANA functions.</div><div><br class=""></div><div>ICP-2 is a process for accrediting a new RIR. It is not a governing document applicable to RIRs once they are accredited.</div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""><br class=""></span></div><div>There is no mechanism in ICANN for revoking the accreditation of an RIR, nor is there any rule anywhere that provides for any form of requirement for an RIR to continue to abide by ICP-2 once it is accredited.</div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""><br class=""></span></div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class="">If you have any document you can offer which contradicts my assertions here, please present it.</span></div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""><br class=""></span></div><div><font face="Calibri, sans-serif" size="3" class="">ICP-2 does not. It clearly states that it is the process for accrediting new RIRs by ICANN. It’s not even clear it would continue to apply if the IANA functions contract were awarded to a different entity.</font></div><div><font face="Calibri, sans-serif" size="3" class=""> </font><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">Some of those points can be addressed by the PDP by authorizing those “mistakes” of the bylaws, however, some aspects must be corrected in the bylaws.</span></div></div></blockquote><div><br class=""></div>Wouldn’t it be better to have the membership correct the mistakes by amending the bylaws than to codify acceptance of the mistakes through the PDP?</div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""> </span><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">There is no RIR bylaws doing anything like that.</span></div></div></blockquote><div><br class=""></div></div><div>Your meaning here is unclear to me.</div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""> </span><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class=""><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">If board and membership keeps ignoring that, instead of solving it, then AFRINIC is insisting in endangering the organization.</span></div></div></div></blockquote><div><br class=""></div>The board currently insists on ignoring the bylaws as written and ignoring the CPM as written. They have already endangered the organization as evidenced by the variety of litigation they have attracted.</div><div><span style="font-size: 12pt; font-family: Calibri, sans-serif;" class=""> </span><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class=""><div style="margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" style="font-size: 12pt;" class="">What you’re proposing will only increatse to breach of ICP-2. The PDP is in the hands of the community, and that means we can’t accept that only members do certain things, including selecting chairs.</span></div></div></div></blockquote><div><br class=""></div>ICP-2 is not a governing document or a stone tablet handed down from on high. Moses did not bring ICP-2 back from the burning manzanita outside the ICANN offices.</div><div><br class=""></div><div>Continuing to pretend that ICP-2 has magical powers or some authority over the operation of an RIR once it is accredited is counter productive.</div><div><br class=""></div><div>Owen</div><div><br class=""></div><br class=""></body></html>