<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div>
<meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); 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; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; 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; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br></div></div></div></div><div><blockquote type="cite"><div>On 22 Jun 2026, at 21:48, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div dir="auto" style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><div><div>Hello PDWG,</div><div dir="auto"><br></div><div data-smartmail="gmail_signature">----<br>Sent from my mobile<br>kindly excuse typos<span class="Apple-converted-space"> </span></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 22 Jun 2026, 8:21 pm ALAIN AINA via RPD, <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Hello PDWG,<br><br>> On 20 Jun 2026, at 23:25, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>> wrote:<br>><span class="Apple-converted-space"> </span><br>> Hello Gregoire,<br>><span class="Apple-converted-space"> </span><br>> Thanks for putting those references, you will find that referenced roles and responsibility from other RIRs and our current PDP puts some trust in the chair(s) to do the needful based on expected outcome.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> IMO 3.3.2.1 e,f,g,I are currently worded in much granular manner. Take f for instance, why won't the Co-Chairs read presentation, so what happens if the Co-Chair missed reading the presentation or if they did but someone within the PDWG claim they didn't.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> The text Preceding 3.3.2.1 addresses a lot of the granularity of<span class="Apple-converted-space"> </span><a href="http://3.3.2.1/" rel="noreferrer noreferrer" target="_blank">3.3.2.1</a>:<br>><span class="Apple-converted-space"> </span><br>> "Organise, prepare and chair the face-to-face and on-line formal working group meetings as well as community consultation meetings."<br><br>If there is consensus that the co‑chairs’ roles and responsibilities must be explicitly defined, the next step is to agree on the precise wording. We invite others in the community to share their perspectives and suggestions<br>><span class="Apple-converted-space"> </span><br>> That said, please do not loose sight of the main concerns that I have raised already. One of them is that we need to be clear on what problem we are trying to address. The problems stated in the current proposal are not problems unique to PDWG, they are organisational problems and PDWG was rightly affected by them just like the other part of the org was affected.<br>><span class="Apple-converted-space"> </span><br>> However, PDWG is not the place to address those problems.<br><br>Could you elaborate on which forum, structure, or mechanism you consider appropriate for addressing these issues, given that they directly affect the continuity, functionality, and compliance of the PDP?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: The issue is governance matter, it affected PDWG directly just as it affected Govcom, Nomcom, AFRINIC Org, etc it even affected the CEO.</div><div dir="auto"><br></div><div dir="auto">I have stated before that I believe the bylaws is the place to address the issue at high level and there is an existing bylaws review ongoing to address those bylaws related changes that ensures that when the board losses quorum then there is a mechanism that ensures not just PDWG but every other aspect of the organisation continue to operate.</div></div></div></blockquote><div><br></div>As it stands, the bylaw has not resolved this issue and we are not sure we will have a resolution soon. Therefore it’s very prudent to think of a solution to protect this working group from such undesirable consequences.</div><div><br></div><div>I support the idea of finding the solution within the PDP which in principle is suppose to function independently of other bodies of AFRINIC. This doesn’t stop the organisation to find a global solution with the bylaws.<br><blockquote type="cite"><div><div dir="auto" style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>> This proposal is attempting to use the event that occurred to the board to turn PDWG to a self governing independent authority through policy and I do not believe that is the way to go about it.<span class="Apple-converted-space"> </span><br><br>This proposal is not attempting to “turn the PDWG into a self‑governing independent authority.” The PDWG already is a self‑governing, community‑driven authority by design. What the proposal does is address the structural weaknesses that recent events exposed; weaknesses that placed AFRINIC in breach of ICP‑2 and threatened the continuity of the entire regional registry.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: Once again I believe that Bylaw is the place to address those weakness as the event that occur didn't just affect PDWG alone. Roles and responsibilities of the Co-Chairs is a different thing which is within scope of PDWG.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>As required by ICP‑2, all RIRs must maintain a bottom‑up, self‑governance structure for developing local policies. This structure must be community‑driven, transparent, and resilient. Each RIR therefore defines a PDP that reflects its operational realities. AFRINIC is no exception.<br><br>Under AFRINIC’s governance model, the PDWG is already a self‑governing body whose authority is delegated downward to AFRINIC Ltd’s Board through the Bylaws — not the other way around. The Bylaws themselves make this clear:<br> <span class="Apple-converted-space"> </span>• Definition of the PDP (Section 23): The PDP is approved by the Internet Community. This establishes the primacy of the community in policy development.<br> <span class="Apple-converted-space"> </span>• Section 15.3: The Board determines allocation guidelines in line with the member‑driven PDP. The PDP constrains the Board.<br> <span class="Apple-converted-space"> </span>• Section 11.2: The Board calls a PPM as per requirements defined in the PDP. The PDP defines the conditions<br><br>This model has been in place since AFRINIC’s inception. What has changed is that its risk profile was never assessed, and the events affecting the Board demonstrated how fragile the system becomes when governance failures occur. The PDP stalled, the community could not advance policy, and AFRINIC fell out of compliance with ICP‑2.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: Well the PDP didn't do that, the bylaw did. Respectfully, I do not agree that PDP is what should restrict the board in this context, it is rather members who restrict the board as defined in the bylaws. I also do not agree that having a PDWG that is self sustaining while the Board is not quorate will fulfill ICP-2 either because that directly signals governance failure according to ICP 2</div></div></div></blockquote><div><br></div><span style="caret-color: rgb(55, 65, 81); font-size: 14px;">Can you please explain why having a self-sustaining PDWG while the Board is dysfunctional is itself a signal of failure? </span></div><div><span style="caret-color: rgb(55, 65, 81); font-size: 14px;">My understanding is that the governance failure is evidenced by a Board that cannot reach quorum; continuing policy development through the PDWG seems like a mitigation measure to maintain continuity, not an additional problem</span><span style="caret-color: rgb(55, 65, 81); font-family: ui-sans-serif, system-ui, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"; font-size: 14px;">.</span><br><blockquote type="cite"><div><div dir="auto" style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>The new NRO Governance Document for the Recognition, Operation, and Derecognition of RIRs, currently under discussion, introduces stricter continuity obligations. These obligations will require AFRINIC to demonstrate that its PDP and the structures supporting it can continue to function even when AFRINIC Ltd faces governance paralysis.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">And where is the best place to ensure that if not in the bylaws? </div></div></div></blockquote><div><br></div><div>Do we have this covered by the bylaws as of date?</div><br><blockquote type="cite"><div><div dir="auto" style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><div dir="auto">I do not agree that "fixing" PDP alone would fulfill requirements of the new NRO Governance document if other structures including the Board is broken. article 4.1 of the Governance document clearly states the expectation of each structure and places significant expectations on the governing body. 4.1g clearly states the expectations for PDP and continuation without the board is not one of them. Section 4.1h further states policy compliance expectations and who will ensure that if not the governing body as represented by the Board.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>For this reason, the community must review the PDP, identify the necessary amendments, and agree on the evolution required to ensure continuity. Where appropriate, these changes will trigger corresponding updates to the AFRINIC Ltd Bylaws and internal operational procedures.<br><br>This proposal is one such attempt. A community‑driven effort to strengthen the PDP, ensure compliance with ICP‑2, and prevent a repeat of the governance failures that affected AFRINIC and the region.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: I appreciate the intent but I do not agree that PDP is the mechanism to effect this. I have no problem with the review of roles and responsibilities of Co-Chairs. The PDWG is a consensus gathering mechanism it should not become a legal ratification vehicle at the same time. That role should remain with the board and we have to agree that if the board have problem then the entire organisation has problem. Infact the board will not be fulfilling 4.1f of the governing document.</div><div dir="auto"><br></div><div dir="auto">In summary If the PDWG could somehow bypass the Board entirely to implement policy(as suggested by the proposal), or if the lack of a functioning Board stalls the process indefinitely, it triggers multiple compliance failures under ICP-2. So why not avoid lack of a functioning board so that PDWG and other structures within AFRINIC can continue to function. Then we test 4.1g against our current PDP and addresses any lapses found which to me are not much</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>Hope this helps<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Thanks 🙏 </div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>—Alain<br><br><br>><span class="Apple-converted-space"> </span><br>> Nevertheless, there is merit in clarifying roles of Co-Chairs and some of the 3.3.2 texts addresses that, hence that then can become the problem statement and sections that does not relate to roles and responsibilities can be commented out.<br><br>><span class="Apple-converted-space"> </span><br>> Regards<br>><span class="Apple-converted-space"> </span><br>> ----<br>> Sent from my mobile<br>> kindly excuse typos<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> On Fri, 19 Jun 2026, 6:22 pm Gregoire EHOUMI, <<a href="mailto:gregoire.ehoumi@yahoo.fr" target="_blank" rel="noreferrer">gregoire.ehoumi@yahoo.fr</a>> wrote:<br>> Hello Seun,<br>><span class="Apple-converted-space"> </span><br>> Please see the references below. Most importantly, what do you think should not be listed under the co-chairs' roles and responsibilities in the proposal?<br>> <span class="Apple-converted-space"> </span><a href="https://www.apnic.net/community/participate/sigs/sig-guidelines/" rel="noreferrer noreferrer" target="_blank">https://www.apnic.net/community/participate/sigs/sig-guidelines/</a><br>> Chair and co-chairs roles - section 2.3<br>> <span class="Apple-converted-space"> </span><a href="https://www.lacnic.net/679/2/lacnic/policy-development-process" rel="noreferrer noreferrer" target="_blank">https://www.lacnic.net/679/2/lacnic/policy-development-process</a><br>> PDP chairs section 3.2<br>> <span class="Apple-converted-space"> </span><a href="https://www.ripe.net/publications/docs/ripe-861/" rel="noreferrer noreferrer" target="_blank">https://www.ripe.net/publications/docs/ripe-861/</a><br>><span class="Apple-converted-space"> </span><br>> RIPE Working Group Chair Job Description and Procedures — RIPE Network Coordination Centre<br>><span class="Apple-converted-space"> </span><br>> Best regards,<br>><span class="Apple-converted-space"> </span><br>> Gregoire<br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>>> On Jun 9, 2026, at 9:09 PM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>> wrote:<br>>><span class="Apple-converted-space"> </span><br>>> Hello Gregoire,<br>>><span class="Apple-converted-space"> </span><br>>> Please find the details inline:<br>>><span class="Apple-converted-space"> </span><br>>> On Tue, 9 Jun 2026 at 14:27, Gregoire EHOUMI <<a href="mailto:gregoire.ehoumi@yahoo.fr" target="_blank" rel="noreferrer">gregoire.ehoumi@yahoo.fr</a>> wrote:<br>>> Dear PDWG,<br>>><span class="Apple-converted-space"> </span><br>>> This digest summarises the key points raised by community members (Ben, Seun, and Sami) regarding this policy proposal, along with the authors’ clarifications and responses.<br>>> It is organised into four themes for easier reading.<br>>><span class="Apple-converted-space"> </span><br>>> 1. Corrections & Clarifications<br>>> Mailing list freeze clarification:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Ben): The RPD list was not frozen; only community‑discuss was moderated.<br>>> • Response: Acknowledged. The text will be corrected in Draft 2. It was meant to say “ Inactive Resource Policy Discussion mailing list”<br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> 2. Participation, Representation & Elections<br>>> Nomination support requirements:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): No need for supporters to be both AFRINIC members and community members.<br>>> • Response: The intent is to ensure support from at least one contact of the membership. Participants in the PDP and the WG activities are generally classified in 2 categories: “Registered contact of AFRINIC member” and “ Non-registered contact of AFRINIC member”<br>>><span class="Apple-converted-space"> </span><br>>> SO: Current participants of RPD do not need to be a “Registered contact of AFRINIC member” OR “ Non-registered contact of AFRINIC member”, the PDWG is and should be open to any person interested in number policy development including non AFRINIC members. Note that there is a subtle difference between non-registered contact of AFRINIC member and a non-AFRINIC member. It should be okay to require support from either an AFRINIC member OR a community member, but the current text mandates both.To illustrate a nomination supported by 2 community members should pass just as a nomination supported by 2 afrinic member, likewise 1 afrinic member and 1 community member.<br>>> <span class="Apple-converted-space"> </span><br>>> Who can vote in NRO NC elections:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): No reason to restrict voting to people in the region.<br>>> • Response: This follows existing AFRINIC rules. For NRO NC, only participants from the region(excluding staff) vote.<br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> SO: My rationale is based on the premise that the rpd is open to all; hence, PDWG co-chair voters should not be restricted to in-region. By extension, NRO NC voters should be similar. Nevertheless considering past experiences, I agree there is merit in restricting voting to in-region but that discriminates on participation as voting is a form of participation as well.<br>>><span class="Apple-converted-space"> </span><br>>> 3. Co‑Chair Roles, Eligibility & Processes<br>>> Level of detail in co‑chair responsibilities:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): Responsibilities in section 3.3.2 feel too granular and policing.<br>>> • Response: The detail is intentional, based on RFC 2418 and other RIRs practices, to avoid ambiguity. The WG should be predictable.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> SO: I do not know of an RIR process that is as granular in the responsibility of co-chairs as stated in 3.3.2. Section 6.1 of RFC 2418 that describes the role of a working group chair isn't as granular either.<br>>><span class="Apple-converted-space"> </span><br>>> Eligibility criteria — meeting attendance:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): Requiring attendance at 4 of the last 6 PPMs (including one in‑person) may be unrealistic.<br>>> • Response: at the old rhythm of 2 PPMs a year, this requirement means attending 4 of the 6 meetings held the last 3 years with at least one in-person. With Attendance A=4 and Meetings M= 6, what would you suggest for A and M?<br>>><span class="Apple-converted-space"> </span><br>>> SO: Requiring in-person attendance is my main concern, it should not be mandatory. You may find at times that it is cheaper to travel out of Africa than within Africa, so not everyone can afford an in-person meeting. Let individual voters decide on candidates based on their historical participation.<br>>><span class="Apple-converted-space"> </span><br>>> Appointment by consensus:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): Consensus‑based appointment could introduce subjectivity.<br>>> • Response: This WG makes decisions by consensus with appeal mechanisms in place. Appointing co-chairs via the same mechanisms should not be a problem. With the requirements stated at section 3.3.3, it should not be difficult to reach consensus on co-chairs candidates. While this may not be perfect, it is used worldwide by various WGs. “Community” votes rather bring more subjectivity.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> Code of Conduct reference:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): Simply refer to AFRINIC’s CoC.<br>>> • Response: By referring to “applicable CoC” the proposal avoids attaching to a particular CoC. Today we are using the “AFRINIC Community CoC” elaborated by the board (<span class="Apple-converted-space"> </span><a href="https://afrinic.net/code" rel="noreferrer noreferrer" target="_blank">https://afrinic.net/code</a><span class="Apple-converted-space"> </span>), this may change in the future. We saw some recent CoC discussions on the list.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> SO: Who determines which Code of Conduct (CoC) is "applicable" and which is not?<br>>><span class="Apple-converted-space"> </span><br>>> 4. Governance Structure & Proposal Scope<br>>> Necessity of the Number Council:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): The Appeal Committee could perform the same role; RNC may be unnecessary.<br>>> • Response: The RNC’s roles encompass calling PPM and appointing interim co-chairs. So making the AC perform RNC’s role may not be appropriate.<br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> What I am trying to communicate is that the RNC and its proposed roles are not required. There is value in having nomcom whose membership is more likely to change every year perform the role of getting nominations for PDWG Co-Chair. If both Co-Chairs resign, the Board should select one of the 3 NRO NC members to chair temporarily until a co-Chair is elected.<br>>><span class="Apple-converted-space"> </span><br>>> Splitting the proposal into smaller documents:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Sami): Consider withdrawing and splitting into multiple focused proposals.<br>>> • Response: The components are interdependent; splitting them would create incoherent intermediate states and procedural gaps.<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> SO: I looked at the problem enumerated below:<br>>><span class="Apple-converted-space"> </span><br>>> • Adopted policy proposals not ratified or not implemented<br>>> • No Public Policy Meeting - Non-renewal of co-chairs<br>>> • Non-renewal of appeal and recall committees<br>>> • Non-renewal of ASO AC/NRO NC representatives<br>>> • Frozen Resource Policy Discussion mailing list<br>>> The problems stated in the policy as listed above (apart from the last which has been corrected) all stemmed from the Board not having a quorum. The idea that the volunteer PDWG should or can effectively operate when there is no Board in the future is wishful thinking that should not be encouraged. In fact, the PDP operation is mandated by the bylaws, and the Board has the fiduciary responsibility to oversee the entire organisation. It therefore seems to me that this policy attempts to address a governance issue through policy rather than through the bylaws. Bylaws is the way to ensure that the events that happened with the Board in the past does not repeat itself.<br>>><span class="Apple-converted-space"> </span><br>>> Board ratification language:<br>>> •<span class="Apple-converted-space"> </span><br>>> Comment (Seun): “Shall” implies the Board must ratify; the Board should be able to decline with reasons.<br>>> • Response: The text as written “If a policy proposal approved by the PDWG fails to be ratified by the board (inability or refusal by the board without reasons for 60 days), a petition for ratification can be initiated by a member of the PDWG.” it is meant to cover the two scenarios below:<br>>><span class="Apple-converted-space"> </span><br>>> 1. The Board is unable to act for 60 days (No quorum, No functioning Board, Legal or operational paralysis, etc.)<br>>> 2. The Board refuses to ratify without giving reasons for 60 days (the Board says “no” but gives no justification, or The Board simply does nothing and provides no explanation.)<br>>> Any suggestions to improve the text if it is not clear enough ?<br>>><span class="Apple-converted-space"> </span><br>>> SO: I think there may be a need to review the problem statement first so the rest of the document is better guided<br>>><span class="Apple-converted-space"> </span><br>>> Regards<span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> The authors thank the community for constructive feedback.<br>>><span class="Apple-converted-space"> </span><br>>> Regards,<br>>><span class="Apple-converted-space"> </span><br>>> Grégoire<br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>>> On May 27, 2026, at 2:45 PM, Sami Salih <<a href="mailto:sami.salih@outlook.com" target="_blank" rel="noreferrer">sami.salih@outlook.com</a>> wrote:<br>>>><span class="Apple-converted-space"> </span><br>>>> Dear Colleagues,<br>>>> 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.<br>>>> 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.<br>>>> 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.<br>>>> 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.<br>>>> 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.<br>>>> With Regards,<br>>>> Sami Sali.<br>>>><span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> Sami Salih<br>>>> From: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank" rel="noreferrer">seun.ojedeji@gmail.com</a>><br>>>> Sent: Monday, May 25, 2026 8:43:56 PM<br>>>> To:<span class="Apple-converted-space"> </span><a href="mailto:dacostadarwin@gmail.com" target="_blank" rel="noreferrer">dacostadarwin@gmail.com</a><span class="Apple-converted-space"> </span><<a href="mailto:dacostadarwin@gmail.com" target="_blank" rel="noreferrer">dacostadarwin@gmail.com</a>><br>>>> Cc:<span class="Apple-converted-space"> </span><a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><span class="Apple-converted-space"> </span><<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>>>> Subject: Re: [rpd] New Draft Policy Proposal - Amendment of the PDP Working Group (WG) Guidelines and Procedures AFPUB-2026-GEN-001-DRAFT01. Hello,<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> Thanks for sharing this proposal. My initial comments after a brief review are the following:<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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.<br>>>><span class="Apple-converted-space"> </span><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.<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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<br>>>><span class="Apple-converted-space"> </span><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.<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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.<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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.<br>>>><span class="Apple-converted-space"> </span><br>>>> - I like the expectation of participation from Co-Chair hence 3.3.4 appeals to me as written.<br>>>><span class="Apple-converted-space"> </span><br>>>> - 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.<span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> I may have more comments in future, but that is all from me for now.<br>>>><span class="Apple-converted-space"> </span><br>>>> Regards<br>>>><span class="Apple-converted-space"> </span><br>>>> On Mon, 25 May 2026 at 10:20,<span class="Apple-converted-space"> </span><a href="mailto:dacostadarwin@gmail.com" target="_blank" rel="noreferrer">dacostadarwin@gmail.com</a><span class="Apple-converted-space"> </span><<a href="mailto:dacostadarwin@gmail.com" target="_blank" rel="noreferrer">dacostadarwin@gmail.com</a>> wrote:<br>>>> Dear PDWG,<br>>>><span class="Apple-converted-space"> </span><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>>>><span class="Apple-converted-space"> </span><br>>>> The proposal contents are published at:<span class="Apple-converted-space"> </span><a href="https://afrinic.net/policy/proposals/afpub-2026-gen-001-draft01" rel="noreferrer noreferrer" target="_blank">https://afrinic.net/policy/proposals/afpub-2026-gen-001-draft01</a><br>>>><span class="Apple-converted-space"> </span><br>>>> We encourage you to take some time to go through the proposal contents and provide feedback as follows :<br>>>><span class="Apple-converted-space"> </span><br>>>> a) Do you support or oppose the proposal?<br>>>><span class="Apple-converted-space"> </span><br>>>> b) If you oppose the proposal, state your reasons.<br>>>><span class="Apple-converted-space"> </span><br>>>> c) Is there anything in the proposal that is not clear?<br>>>><span class="Apple-converted-space"> </span><br>>>> d) What changes could be made to this proposal to make it more effective?<br>>>><span class="Apple-converted-space"> </span><br>>>> Regards,<br>>>> Vincent Ngundi & Darwin Da Costa<br>>>> AFRINIC PDWG Co-Chairs<br>>>> _______________________________________________<br>>>> RPD mailing list<br>>>><span class="Apple-converted-space"> </span><a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>>>><span class="Apple-converted-space"> </span><a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>>>><span class="Apple-converted-space"> </span><br>>>><span class="Apple-converted-space"> </span><br>>>> --<span class="Apple-converted-space"> </span><br>>>> ------------------------------------------------------------------------<br>>>> Seun Ojedeji,<br>>>> Bringing another down does not take you up - think about your action!<br>>>><span class="Apple-converted-space"> </span><br>>>> _______________________________________________<br>>>> RPD mailing list<br>>>><span class="Apple-converted-space"> </span><a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>>>><span class="Apple-converted-space"> </span><a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>><span class="Apple-converted-space"> </span><br>>> --<span class="Apple-converted-space"> </span><br>>> ------------------------------------------------------------------------<br>>> Seun Ojedeji,<br>>> Bringing another down does not take you up - think about your action!<br>>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> _______________________________________________<br>> RPD mailing list<br>><span class="Apple-converted-space"> </span><a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br>><span class="Apple-converted-space"> </span><a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br><br><br>_______________________________________________<br>RPD mailing list<br><a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br></blockquote></div></div></div><span style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">_______________________________________________</span><br style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><span style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">RPD mailing list</span><br style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><a href="mailto:RPD@afrinic.net" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;">RPD@afrinic.net</a><br style="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; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-line: none; text-decoration-thickness: auto; text-decoration-style: solid;"><a href="https://lists.afrinic.net/mailman/listinfo/rpd" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;">https://lists.afrinic.net/mailman/listinfo/rpd</a></div></blockquote></div><br></body></html>