<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Dear Colleagues,</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">As a former PDWG Co-chair, I generally support the intent behind strengthening the autonomy and operational
continuity of the PDWG. The policy development process ultimately belongs to the African Internet community and should remain resilient regardless of operational or governance challenges affecting AFRINIC as an organisation.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">At the same time, I believe it is important to recognize that this proposal introduces substantial structural,
operational, procedural, and governance changes to the PDP framework. In many respects, this is a major and transformative proposal rather than a routine procedural update.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">From my experience with the PDP, the community process tends to work best when addressing clearly scoped issues
through focused and easy-to-understand proposals. In contrast, this proposal attempts to address many different governance, electoral, operational, disciplinary, and procedural matters simultaneously, which makes it difficult for the community to fully analyse,
discuss, and build meaningful consensus around all aspects at once.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">IMHO, many of the ideas and intended improvements presented in this proposal are constructive and deserve serious
consideration. I also fully acknowledge and respect the extensive experience, effort, and strategic thinking of the authors in developing such a comprehensive framework proposal.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">However, considering the breadth of the changes and the number of distinct governance and operational matters
being introduced simultaneously, my respectful recommendation would be to consider withdrawing the current proposal and restructuring this work into multiple smaller and more focused proposals. I believe this would make it significantly easier for the community
to understand, analyse, discuss, and build meaningful consensus around each individual topic independently, while improving overall community engagement and participation in the process.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(33, 33, 33);">With</span><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Regards,<br>
Sami Sali.</span></p>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(33, 33, 33);">
<br>
</div>
<div id="ms-outlook-mobile-body-separator-line" data-applydefaultfontstyles="true" dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<div style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
</div>
<div id="ms-outlook-mobile-signature" dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(33, 33, 33);">
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(33, 33, 33);">
Sami Salih</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Seun Ojedeji <seun.ojedeji@gmail.com><br>
<b>Sent:</b> Monday, May 25, 2026 8:43:56 PM<br>
<b>To:</b> dacostadarwin@gmail.com <dacostadarwin@gmail.com><br>
<b>Cc:</b> rpd@afrinic.net <rpd@afrinic.net><br>
<b>Subject:</b> Re: [rpd] New Draft Policy Proposal - Amendment of the PDP Working Group (WG) Guidelines and Procedures AFPUB-2026-GEN-001-DRAFT01.</font>
<div> </div>
</div>
<div>
<div dir="ltr">Hello,
<div><br>
</div>
<div>Thanks for sharing this proposal. My initial comments after a brief review are the following:</div>
<div><br>
</div>
<div>- A typical community member could also be an AFRINIC member. There is no reason to mandate that nomination supporters for the NRO NC must be both community members and AFRINIC members. Requiring one or 2 supporters from the service region should be sufficient.</div>
<div><br>
- The rpd is open to anyone that wishes to participate irrespective of origin, region or residence. It sure makes sense to restrict election participation to those with a historical record of involvement, either online or in-person to avoid historical experience
of DDOS on election day. However, there is no reason to restrict the selectorate/electorate to those in the region alone.</div>
<div><br>
</div>
<div>- I do not see the necessity of a Number Committee; it seems to create yet another layer. The Appeal committee which also serves as the recall committee can perform any intended role of the RNC. Its composition could be the 3 NRO NC members from the region,
a past co-chair, and a past appeal committee chair in a non-voting capacity. In situations where both Co-Chairs are no more, the Chair of the Appeal committee can temporarily take over until rpd appoints a new co-chair</div>
<div><br>
- As a former co-chair of PDWG, i find the proposed responsibilities of the Co-chairs as described in section 3.3.2 to be overly granular and quite policing-like for lack of a better word.</div>
<div><br>
</div>
<div>- I believe the proposed 3.3.7 should refer to AFRINIC CoC and that should be sufficient. The proposed penalties for violations look good, though they are a bit too wordy to me and the process leading to that is quite descriptive. We really need to give
the co-chairs the privilege of managing events as they deem applicable</div>
<div><br>
</div>
<div>- The idea that a co-chair eligibility should be tied to attending in-person meetings during a specific period isn't realistic given our region's unique challenges. I understand it may be an effort to put a face to the name but restricting eligibility
to the last 2 years (which is basically last 4 PPM) isn't realistic.</div>
<div><br>
</div>
<div>- 3.3.3.3.3 suggests co-chairs will be appointed by consensus, that is an interesting point that i would definitely not support. This can lead to unnecessary subjectivity.</div>
<div><br>
</div>
<div>- I like the expectation of participation from Co-Chair hence 3.3.4 appeals to me as written.</div>
<div><br>
</div>
<div>- Use of shall in 3.3.11 suggests that ratification is the only option for the Board. There should be an option for the Board to provide reasons for not ratifying and that should not be triggered by a petition. <br>
<br>
I may have more comments in future, but that is all from me for now.</div>
<div><br>
Regards</div>
</div>
<br>
<div class="x_gmail_quote x_gmail_quote_container">
<div dir="ltr" class="x_gmail_attr">On Mon, 25 May 2026 at 10:20, <a href="mailto:dacostadarwin@gmail.com">
dacostadarwin@gmail.com</a> <<a href="mailto:dacostadarwin@gmail.com">dacostadarwin@gmail.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
Dear PDWG,<br>
<br>
We have received a new draft policy proposal - Amendment of the PDP Working Group (WG) Guidelines and Procedures AFPUB-2026-GEN-001-DRAFT01 from authors Grégoire EHOUMI, Noah Maina and Adeola A. P. AINA.<br>
<br>
The proposal contents are published at: <a href="https://afrinic.net/policy/proposals/afpub-2026-gen-001-draft01" rel="noreferrer" target="_blank">
https://afrinic.net/policy/proposals/afpub-2026-gen-001-draft01</a><br>
<br>
We encourage you to take some time to go through the proposal contents and provide feedback as follows :<br>
<br>
a) Do you support or oppose the proposal?<br>
<br>
b) If you oppose the proposal, state your reasons.<br>
<br>
c) Is there anything in the proposal that is not clear?<br>
<br>
d) What changes could be made to this proposal to make it more effective?<br>
<br>
Regards,<br>
Vincent Ngundi & Darwin Da Costa<br>
AFRINIC PDWG Co-Chairs<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote>
</div>
<div><br clear="all">
</div>
<div><br>
</div>
<span class="x_gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="x_gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">------------------------------------------------------------------------<br>
<font color="#888888">
<blockquote style="margin:0pt 0pt 0pt 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex; font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)">
</span></i>
<blockquote style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
Bringing another down does not take you up - think about your action!<br>
</blockquote>
</blockquote>
</font><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>