<div dir="ltr"><div dir="ltr"><pre class="gmail-zcmsgcnt gmail-textL" id="gmail-posted-message-container" style="box-sizing:border-box;margin:0px 26px 0px 0px;padding:0.1px 0px 0px;outline:0px;border:0px;vertical-align:baseline;background:transparent;font-family:inherit;white-space:pre-wrap;line-height:24px;font-size:15.008px;font-variant-ligatures:none"><span dir="auto" style="box-sizing:border-box;margin:0px;padding:0px;outline:0px;border:0px;vertical-align:baseline;background:transparent;font-family:inherit">Good day,<br style="box-sizing:border-box;margin:0px;padding:0px;outline:none"><br style="box-sizing:border-box;margin:0px;padding:0px;outline:none">CPM 3.3 provides that the PDWG has two Chairs to perform its administrative functions. It sets no candidate qualifications, and the PDP provides none. The four published conditions, age of majority, three years of activity on this or another RIR's mailing list, familiarity with current draft proposals, and not being the author of a proposal under discussion, appear nowhere in the CPM or the PDP. Conditions that decide who may stand for a community chair are substantive, not administrative. If qualification tests are thought necessary, they must come as a policy proposal through the PDP, not from an election-guideline page issued for one election.<br style="box-sizing:border-box;margin:0px;padding:0px;outline:none"><br style="box-sizing:border-box;margin:0px;padding:0px;outline:none">On authorship, the published text refers to an author; as written it does not reach a co-author. If co-authors are meant to be covered, the guideline should say so. In any case, a co-chair is elected for the term after the meeting, and a proposal adopted or withdrawn before that term begins is not a conflict. The thread's example points to recusal as the way to manage an interest where a chair has one; that is what two chairs make possible.<br style="box-sizing:border-box;margin:0px;padding:0px;outline:none"><br>I think AFRINIC should reconsider these conditions and allow the community to discuss them through the PDP.
<br style="box-sizing:border-box;margin:0px;padding:0px;outline:none">Zenalo<br></span></pre></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, 19 Nov 2026 at 13:19, <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:rpd-request@afrinic.net" target="_blank">rpd-request@afrinic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:rpd-owner@afrinic.net" target="_blank">rpd-owner@afrinic.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: co-chairs are also community members<br>
(<a href="mailto:jordi.palet@theipv6company.com" target="_blank">jordi.palet@theipv6company.com</a>)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 19 Nov 2026 12:16:58 +0100<br>
From: "<a href="mailto:jordi.palet@theipv6company.com" target="_blank">jordi.palet@theipv6company.com</a>"<br>
<<a href="mailto:jordi.palet@theipv6company.com" target="_blank">jordi.palet@theipv6company.com</a>><br>
To: rpd List <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] co-chairs are also community members<br>
Message-ID: <<a href="mailto:7C450B36-4C95-4146-81F6-2677725B40DF@theipv6company.com" target="_blank">7C450B36-4C95-4146-81F6-2677725B40DF@theipv6company.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Seun,<br>
<br>
Some responses below, in-line.<br>
<br>
Regards,<br>
Jordi<br>
<br>
@jordipalet<br>
<br>
> El 19 nov 2026, a las 1:04, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> escribi?:<br>
> <br>
> Hello Jordi,<br>
> <br>
> I did not fully participate at the session today due to conflicts. However I see a lot of merit in your mail. Some of the candidate requirements are definitely strange and can be subjective. <br>
> <br>
> 1. The text says "majority," which seems like a typo; I am assuming "maturity" was intended? If yes then I don't see why maturity is a requirement. I have no problem with putting an age requirement to reflect that an adult is expected to chair PDWG. That can be 18 years or older.<br>
<br>
You can check it at 6.3.4 in <a href="https://elections.afrinic.net/election-guidelines-2026#section-6-3" rel="noreferrer" target="_blank">https://elections.afrinic.net/election-guidelines-2026#section-6-3</a><br>
<br>
I think majority was intended, at least it is also the term that I will use in Spanish. However, you?re right that the right term should be maturity, because this is what we expect from a co-chair. In fact I will completely remove that restriction, because it needs to be evaluated (if it happens) on a case-by-case basis. If someone with 16 years has already been participating in the list, we can see if he/she is mature enough from its contributions.<br>
<br>
In some countries majority is even 16 for many aspects, such as voting, driving, acting against law, etc. Also, what country, the origin country (it should be, but is not clear). I will say that we can?t disqualify in terms of age. How many people today with 13-14 years it is already running an IT business. They are mature enough to participate. I was developing software and selling it at 13. At that time RIRs where not there, but how come I could be restricted if RIRs existed of participating in the RPD (we don?t have such limitation), and consequently participate in elections, volunteer for co-chair, vote, etc., etc. Much more very young people today is mature enough with much lower ages.<br>
<br>
And we can have a 30-40 or older person not mature enough to be a good co-chair, right?<br>
<br>
> <br>
> 2. It is absurd and strange that a PDWG member who is an author cannot run for Co-chair; in fact, such a person should be more welcome as it means he/she/they are active and very much engaged. The only exception that I think can be added is to flag that should a situation arise where both elected Co-Chairs happen to be authors of the same policy the RPD would appoint a chair for that policy alone from the floor while they both recuse themselves. <br>
<br>
Yes, totally agree in that case.<br>
<br>
> <br>
> Now that is a very unlikely situation; hence, PDWG will always have a co-chair who is not conflicted. When I was co-chair, I authored a draft policy and as per conflict of interest I simply recused myself and my co chair chaired the session. Co-chairs are adults; we should allow some level of trust and of good faith<br>
<br>
Aha! I didn?t remember about that. So how come the board unilaterally is taking now such discriminatory decisions?<br>
<br>
> <br>
> 3. I have no problem requiring 2 resource members. I am not sure what "distinct" means, and regardless, there's no reason to require it. Requiring only a resource member is sufficient. That could be qualified with "member in good standing." <br>
<br>
I don?t agree on that. I agree that a candidate must have the support for a couple of resource members, but not necessarily be a resource member. This is the case in all the other RIRs if I recall correctly.<br>
<br>
Just to show a simple example: What happens if the current co-chairs, which are resource members (I believe), change their job, and their new employee is not a resource member, but they still agree to continue the term, or even participate in elections in the next term? Do you believe they loose their ability to properly judge consensus, understand the proposals, the CPM, the PDP, etc., etc., because they changed the job? (regardless if the new job is still Internet/IT related or not).<br>
<br>
> <br>
> I hope we will not be too restrictive, thereby unintentionally disqualifying good candidates.<br>
<br>
I?d had a proposal some years ago, which also reached consensus in LACNIC, about the elections, it was much simpler and it worked well for many years. Will need to revive it!<br>
<br>
> <br>
> Regards<br>
> ----<br>
> Sent from my mobile<br>
> kindly excuse typos<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On Wed, 18 Nov 2026, 3:56?pm jordi.palet--- via RPD, <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a> <mailto:<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>>> wrote:<br>
>> Hi all,<br>
>> <br>
>> This afternoon we had this discussion, with for me it is a shame.<br>
>> <br>
>> How come anyone in the world can understand from the existing PDP (3.3):<br>
>> <br>
>> ?The Policy Development Working Group has two Chairs to perform its administrative functions.?<br>
>> <br>
>> This other sentence:<br>
>> ?The Policy Development Working Group has two Chairs to perform *EXCLUSIVELY* its administrative functions.?<br>
>> <br>
>> So the interpretation being done by AFRINIC (organization, Board, legal counsel, etc.), means that when community members are elected as co-chairs, they LOSE their rights as community members.<br>
>> <br>
>> So they can?t provide ?hat-off? (personal, not as co-chair), opinions. This is contrary to what is being done in the other RIRs or the IETF. Chairs, staff, board members, are also community members, and volunteering (or being paid for) a specific position, doesn?t take away their LEGAL rights to still participate as a regular individual.<br>
>> <br>
>> The only need is to ensure demonstrating their neutrality, to clearly state, as done in other RIRs, IETF, etc., ?hat-off ? my personal view or experience on this is xxx?.<br>
>> <br>
>> This doesn?t mean they will act subjectively when judging consensus!<br>
>> <br>
>> Otherwise, it is like saying to someone "you?re not allowed to come into this shop because you?re a thief?, even if never he/she committed a robbery before in that shop.<br>
>> <br>
>> And here there is no need to amend the PDP for that: it is just a matter of not *reading* words that don?t exist in the PDP like *EXCLUSIVELY*. May be I?m somehow blind and these words are in the PDP in a color that I can?t see?<br>
>> <br>
>> Furthermore, we need to consider that the *real* participants in the RPD and PPM discussions is always a reduced group of the same people. If we don?t allow some of them, because they volunteered for co-chair, board, nomcom, appeal or other committees to also contribute, we are reducing the chances for wider discussions and inputs.<br>
>> <br>
>> And this is also related to the co-chair election process, which is discriminatory for the same reason (and many others), which in many jurisdictions will be a clear discrimination act and can be brought to courts.<br>
>> <br>
>> When a previous co-chair, being co-author of a policy proposal, volunteered to serve as a co-chair, it was reminded by the staff to withdraw as co-author. I openly complained against that, same argument, being a co-chair doesn?t mean you lose the ?status? of community member. Never got a response on that.<br>
>> <br>
>> This time, *in exactly the same situation* another co-author who volunteered for co-chair, has been discriminated (vs the previous case) by not reminding him to withdraw as co-author. How come we can accept that?<br>
>> <br>
>> The real problem is how the board reached the conclusion that they can discriminate people for being elegible for a community position. Looking into the rule for being a co-chair (<a href="https://elections.afrinic.net/election-guidelines-2026" rel="noreferrer" target="_blank">https://elections.afrinic.net/election-guidelines-2026</a>) I can see several discriminatory points:<br>
>> <br>
>> 1) have attained the age of majority??????? 1st, I don?t know if it is the same age in all the countries in the region, but then, where in the PDP say anything about age of majority? So if a person with 16-17 years is today perfectly capable of using the Internet and participating in the discussions, why he/she will not be able to be a co-chair? It is not about age, it is about being able to understand the process. Of course, I don?t expect this to happen, but if it happens?<br>
>> <br>
>> 2) ?or that of any other RIR? ? I don?t think this is being used in any other RIR. I think the point is just to have been active in this region.<br>
>> <br>
>> 3) ?as well as of current draft proposals? ? no sense at all. Those proposals may reach consensus before the candidate term starts. What is needed is an understanding of the process and any proposal, if a proposal is not clear, then the proposal has a problem, not the candidate.<br>
>> <br>
>> 4) ?not be the author ?? totally ridiculous. One of the reasons we have multiple co-chairs is to resolve this situation, when one of the chairs needs to abstain for whatever reason with a specific proposal. A co-chair, in all the regions and in the IETF, can be an author. A co-chair may decide to write a proposal while he is a co-chair, and there is nothing that prevents that. A co-chair may be the only author of a proposal and needs to withdraw it before volunteering, even if this proposal my reach consensus BEFORE he is elected? A co-chair, may participate as an individual (stating hats-off) in any discussion. This is honest. Anything else is just not transparent and against the full PDP. By the way, the rules say ?author? not ?co-author?, so one more contradictory point that once more shows how a candidate has been discriminated.<br>
>> <br>
>> Further, a bad faith co-chair candidate, may be behind a policy proposal using a colleague to drive it thru the process and missmanage the process to get consensus on that proposal. This is much worst than a co-chair clearly abstaining (and thus being honest and transparent) from declaring consensus in a proposal that he is authoring or co-authoring. <br>
>> <br>
>> This decision consequently MUST BE APPEALED. I?m happy to start that and even consider courts, if the candidate that was discriminated in this election doesn?t want to appeal himself.<br>
>> <br>
>> In addition to that, the RPD community needs to clearly have a discussion on all this (that?s why this email) and take a firm position and the board follow it, because the board is not on top of the community on PDP matters, and the co-chairs and their functions are part of the PDP, not AFRINIC as an organization.<br>
>> <br>
>> Similar point as for the code of conduct, if it must be followed by RPD members, it needs to be discussed with the community. I recall it was done some time ago, why not this time? Send a draft, we discuss it, and we provide suggestions, etc.<br>
>> <br>
>> Otherwise (and this is just an example) the community should send policy a proposal and have our own code of conduct. Ah ? of course, I forgot the point, then maybe the board will not ratify it, even if this is not play against the organization.<br>
>> <br>
>> Once more, as I said during the day, several times, by-laws of AFRINIC of course, need to have specific considerations because is based in Mauritius so it is different that all the other RIRs, but this doesn?t mean the by-laws need to encroach the community and the bottom-up process.<br>
>> <br>
>> Hopefully we can have a good discussion on these points.<br>
>> <br>
>> Note that I?m not, in this email, discussing any specific policy proposal (I will work in other email threads in the next days for that), just open discussion that clearly shows that the co-chairs don?t have ?exclusivity? and the election process is a community process, with our own rules, not a board decided rules that are clearly discriminatory. I?m fine if the board prefer to have the nomcom to be used to facilitate the process, but doing the rules a) Not contradicting the PDP (the exclusivity thing), b) Being arranged in an open discussion with the community, at least until the community has (if necessary) a policy proposal more specific for elections.<br>
>> <br>
>> And with all that said I will shut up for today. Safe trip back home to those traveling!<br>
>> <br>
>> Regards,<br>
>> Jordi<br>
>> <br>
>> @jordipalet<br>
>> <br>
>> <br>
>> **********************************************<br>
>> IPv4 is over<br>
>> Are you ready for the new Internet ?<br>
>> <a href="http://www.theipv6company.com" rel="noreferrer" target="_blank">http://www.theipv6company.com</a> <<a href="http://www.theipv6company.com/" rel="noreferrer" target="_blank">http://www.theipv6company.com/</a>><br>
>> The IPv6 Company<br>
>> <br>
>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
>> <br>
>> <br>
>> <br>
>> <br>
>> _______________________________________________<br>
>> RPD mailing list<br>
>> <a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a> <mailto:<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>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com" rel="noreferrer" target="_blank">http://www.theipv6company.com</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20261119/f404b32a/attachment.html" rel="noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20261119/f404b32a/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<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>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 226, Issue 27<br>
************************************<br>
</blockquote></div></div>