<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;">Hi Seun,<div><br></div><div>The contact from board to IETF is what the IETF page suggests. I’m not saying I agree with IETF doing right with that discriminatory classification, on the contrary.</div><div><br></div><div>However that’s irrelevant:</div><div><br></div><div>*** If organization A always plan ahead 6 years of meeting dates and organization B often plan ahead just a few months or 1-2 years what the logic say? Obviously is up to organization B to avoid the clash, because there is no way organization A can avoid it when B has not planed already.</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 16 sept 2026, a las 12:53, Seun Ojedeji <seun.ojedeji@gmail.com> escribió:</div><br class="Apple-interchange-newline"><div><div dir="auto"><div><div>Hi Jordi,</div><div dir="auto"><br></div><div>Just a comment, please see inline below:</div><div data-smartmail="gmail_signature">----<br>Sent from my mobile<br>kindly excuse typos </div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, 16 Sept 2026, 3:33 am jordi.palet--- via RPD, <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space"><div>.</div><div><br></div><div>Obviously this doesn’t excuse the clear discrimination being done by IETF between 1 RIR vs the other 4.</div><div><br></div><div>Also note that it is up to AFRINIC staff (or board) to contact IETF to change that. </div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: It should be up to IETF to contact AFRINIC Board when there is clash as well, there is no reason to hardcode a commitment in AFRINIC working document just because of an IETF date clash incidence. If it were other RIR maybe I would have some sympathy for that and even that should not justify hardcoding date requirements as AFRINIC always ensure to avoid date clashes as much as possible.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space"><div>I will do my best anyway to ensure that the list is the web page is not discriminating AFRINIC/AFNOG. I urge the staff and board, and other RPD members to complain to the IETF about that, probably reply to all to my previous email so it get copied to <a href="mailto:meeting-planning@ietf.org" target="_blank" rel="noreferrer">meeting-planning@ietf.org</a>.</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">SO: You don't have to do the talking anymore Jordi it is not necessary. Things like these does not have to be lobbied for to be done.</div><div dir="auto"><br></div><div dir="auto">I join others in opposing this policy. Maybe if you get similar policy proposed at other RIR and it passes we can reconsider.</div><div dir="auto"><br></div><div dir="auto"> Regards </div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space"><div><br id="m_-5076839664678896404lineBreakAtBeginningOfMessage"><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 16 sept 2026, a las 10:15, Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>> escribió:</div><br><div><div dir="ltr">Jordi,<div><br></div><div>I'd like to point out that even looking at the IETF Clash list - AfriNIC is not even on the IETF must not clash list.</div><div><br></div><div>According to that list, IETF meetings MUST NOT clash with the following: </div><div><br></div><div><ul style="box-sizing:border-box;padding-left:2rem;margin-bottom:1rem;margin-top:0px;color:rgb(51,55,65);font-family:Inter,Helvetica,arial,sans-serif;font-size:16px"><li style="box-sizing:border-box">APNIC</li><li style="box-sizing:border-box">APRICOT</li><li style="box-sizing:border-box">ARIN</li><li style="box-sizing:border-box">3GPP *</li><li style="box-sizing:border-box">ICANN *</li><li style="box-sizing:border-box">IEEE 802 *</li><li style="box-sizing:border-box">ITU-T (selected meetings)*</li><li style="box-sizing:border-box">LACNIC</li><li style="box-sizing:border-box">NANOG</li><li style="box-sizing:border-box">OMA *</li><li style="box-sizing:border-box">RIPE</li><li style="box-sizing:border-box">W3C *</li></ul><div><div>There is a separate list of events they prefer not to clash with but where the conflict matters less—and AfriNIC is only on that second list. See <a href="https://www.ietf.org/meeting/planning/clash-list/" target="_blank" rel="noreferrer">https://www.ietf.org/meeting/planning/clash-list/</a></div><div><br></div><div>Until such time as other organisations have to do not clash lists - and are willing to publish those - and there is reciprocity, I remain opposed to this policy.</div><div><br></div><div>Andrew</div><div><br></div><div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 16, 2026 at 11:05 AM jordi.palet--- via RPD <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@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"><div>Hi all,<div><br></div><div>Responding to several emails on this with a single response.</div><div><br></div><div>1) There is no such policy in other RIRs, becuase it was not needed, as didn’t happened such clash. Policy proposals must be both proactive and reactive, which means that sometimes we can see a problem “before” it happens and try to avoid it with a policy proposal. Other times, we react to what already happened, like this one. This doesn’t mean at all, that any RIR is 1st or 2nd or 3rd class. Otherwise, as the policies in the RIRs have differences, we could always state that. No sense, same as the no sense that if the board decides to repeat the clash in the coming years the community have nothing to do against that? For sure that no other RIR will do that, and if they do, the community will reach with similar policy proposals.</div><div><br></div><div>2) If you read carefully the proposal, I’ve, on purpose, used “should” and not “must” and also for other events “whenever possible”. So this perfectly allows “emergency” situations.</div><div><br></div><div>3) Repeating again, if “other events” are co-located, this is in the proposal “whenever possible”, so it doesn’t disallow it. My view is that the result usually is that the PPM will get less attention that those collocated event if they clash (previous experience in another RIR show it). This is not the same as AIS, as it is a “joint” event, with shared agenda, I don’t see it as a clash - we have this in other RIRs and again, is not a problem, because it is a shared agenda.</div><div><br></div><div>4) Of course, if you create clash with other events where few people from Africa take part in, will actually avoid those people to even consider taking part in those!</div><div><br></div><div>5) Despite what I’ve said in 2 above, my understanding is that the current PDP and bylaws doesn’t allow “emergency” PPMs. The bylaws call for “the board” will do what they wish, and enforce their actions even if the community doesn’t reach consensus on that. Which, again, in my opinion (I said that many times already) is a terrible mistake, against bottom-up process, and should be corrected, as otherwise, Afrinic will be against the new ICP-2, but this is a topic for another discussion.</div><div><br id="m_-5076839664678896404m_-7100104617194811220lineBreakAtBeginningOfMessage"><div>
<div>Regards,<br>Jordi<br><br>@jordipalet<br></div>
</div>
<div><br><blockquote type="cite"><div>El 16 sept 2026, a las 8:30, Ben Roberts - AfriNIC via RPD <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>> escribió:</div><br><div><div dir="auto">+1 Andrew. The nature of these PPM events is that it is necessary to hold them alongside other African events in order to make it worth the trip for what is actually a short meeting. This year we held one PPM alongside the AIS (as has been traditional) and now experimenting with co-locating it alongside AfricaCom which is the biggest African industry event of the year. I would rather we see how the experiment works before introducing policies to tie us in knots by settling to not clash with global meetings that very few people from Africa take part in. <div><br></div><div><br id="m_-5076839664678896404m_-7100104617194811220lineBreakAtBeginningOfSignature"><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On 16 Sep 2026, at 08:58, Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank" rel="noreferrer">aa@alstonnetworks.net</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Hi RPD / RPD Chairs,<div><br></div><div>I oppose this policy. While I believe that AfriNIC should endeavor to ensure that meetings do not clash, the reality is that this is sometimes unavoidable. Furthermore, I stand to be corrected, but I am unsure if other organisations have such a policy. Embedding this in our policy manual effectively relegates AfriNIC to second-class status compared to other global organisations that do not have similar policies prohibiting scheduling conflicts with AfriNIC.</div><div><br></div><div>Furthermore, there may be times when an emergency policy meeting needs to be called to address an urgent issue, and this clause could pose a serious problem in that scenario.</div><div><br></div><div>To repeat my stance above, I do not doubt the policy's intent, and while clashes should obviously be avoided, but I do not believe that this should be made a rule that restricts the PDP to the scheduling whims of other organisations.</div><div><br></div><div>Thanks</div><div><br></div><div>Andrew</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 14, 2026 at 6:49 PM Hytham El-Nakhal <<a href="mailto:hytham@tra.gov.eg" target="_blank" rel="noreferrer">hytham@tra.gov.eg</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">Dear PDWG,<br>
<br>
<br>
We have received a new draft policy proposal named PPM Dates with ID AFPUB-2026-GEN-003-DRAFT01 from author Jordi Palet.<br>
<br>
<br>
The proposal contents are published at: <<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>
<br>
<a href="https://www.afrinic.net/afpub-2026-gen-003-draft01" rel="noreferrer noreferrer" target="_blank">https://www.afrinic.net/afpub-2026-gen-003-draft01</a><br>
<br>
<br>
We encourage you to take some time to go through the proposal contents and provide feedback as follows: -<br>
<br>
?<br>
<br>
a) Do you support or oppose the proposal?<br>
<br>
<br>
b) If you oppose the proposal, state your reasons.<br>
<br>
<br>
c) Is there anything in the proposal that is not clear?<br>
<br>
<br>
d) What changes could be made to this proposal to make it more effective?<br>
<br>
<br>
Kindly, as a way for better following up and archiving, keep the name and proposal ID in the subject line of your posts.<br>
<br>
<br>
Regards,<br>
<br>
Haitham el Nakhal & Darwin Da Costa<br>
<br>
AFRINIC PDWG Co-Chairs<br>
<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>
<span>_______________________________________________</span><br><span>RPD mailing list</span><br><span><a href="mailto:RPD@afrinic.net" target="_blank" rel="noreferrer">RPD@afrinic.net</a></span><br><span><a href="https://lists.afrinic.net/mailman/listinfo/rpd" target="_blank" rel="noreferrer">https://lists.afrinic.net/mailman/listinfo/rpd</a></span><br></div></blockquote></div></div>_______________________________________________<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" target="_blank" rel="noreferrer">https://lists.afrinic.net/mailman/listinfo/rpd</a><br></div></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com/" target="_blank" rel="noreferrer">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>
</div>_______________________________________________<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></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com/" target="_blank" rel="noreferrer">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>
</div>_______________________________________________<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>
</div></blockquote></div><br></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<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>
</body></html>