<div dir="ltr"><pre class="gmail-zcmsgcnt gmail-textL" dir="auto" 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;font-size:15.008px;letter-spacing:0.01px">Hi Andrew,<br style="box-sizing:border-box;margin:0px;padding:0px;outline:none"> <br style="box-sizing:border-box;margin:0px;padding:0px;outline:none">I see the value, but I'm cautious.<br><br>Conduct rules have been twisted to protect insiders and exclude criticism. Adding a conduct code could make things worse. We should limit it to clear harm like harassment and spam, not vague tone complaints. The IETF model only works because of its open culture. Let's not copy the form without the substance. Will need to see the draft and the oversight plan before I can support it.<br><br>Regards,<br>Theresa</pre></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, May 27, 2026 at 11:49 AM <<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: Gauging Interest in a possible policy change<br>
(<a href="mailto:jordi.palet@consulintel.es" target="_blank">jordi.palet@consulintel.es</a>)<br>
2. Re: Gauging Interest in a possible policy change<br>
(Dewole Ajao [AFRINIC])<br>
3. Re: Gauging Interest in a possible policy change (Benson Muite)<br>
4. Re: Gauging Interest in a possible policy change (Seun Ojedeji)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 27 May 2026 08:49:24 +0200<br>
From: "<a href="mailto:jordi.palet@consulintel.es" target="_blank">jordi.palet@consulintel.es</a>" <<a href="mailto:jordi.palet@consulintel.es" target="_blank">jordi.palet@consulintel.es</a>><br>
To: RPD <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] Gauging Interest in a possible policy change<br>
Message-ID: <<a href="mailto:69DABC60-221A-4223-90BB-C114E3C46BE2@consulintel.es" target="_blank">69DABC60-221A-4223-90BB-C114E3C46BE2@consulintel.es</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Andrew,<br>
<br>
A few years ago, in LACNIC we had similar issues with behaviours against the spirit of the equivalent list to this one.<br>
<br>
As I was IETF sergeant at arms for the IETF mailing list, and also participate in many other exploders that have AUPs (Acceptable Usage Policy), I used my experience to design a proposal for LACNIC, you can see the last version here:<br>
<br>
<a href="https://politicas.lacnic.net/politicas/detail/id/LAC-2018-13/language/en" rel="noreferrer" target="_blank">https://politicas.lacnic.net/politicas/detail/id/LAC-2018-13/language/en</a><br>
<br>
It took a long time to discuss the proposal, and when it was almost reaching consensus (in my opinion), LACNIC decided to make a CoC which somehow superseddes the AUP.<br>
<br>
Nevertheless, I still have encountered feelings if an AUP may be also needed in parallel to the CoC, as the CoC is quite generic while the AUP can provide a ore clear path to co-chairs.<br>
<br>
So if you reach the conclusion that this is good to have, I?m happy to work with you/others in that, or feel free to use that proposal as a starting point that was discussed during 3 years in a very similar context. <br>
<br>
Regards,<br>
Jordi<br>
<br>
@jordipalet<br>
<br>
<br>
> El 27 may 2026, a las 7:53, Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>> escribi?:<br>
> <br>
> Hi Guys,<br>
> <br>
> I've been giving this a lot of thought and want to gauge interest in adding a policy relating to the code of conduct.<br>
> <br>
> Effectively, what I foresee is language added to the policy which acts similar to the IETF Notewell, and specifies appropriate/inappropriate conduct both on the PDP List and during PDP meetings.<br>
> <br>
> Ideally speaking this will also include enforcement actions for the code of conduct, appeal procedures etc. <br>
> <br>
> Within the IETF framework for example, disruptive behavior can result in the temporary or permanent loss of posting rights to the list, and such enforcement actions are subject to a robust appeal mechanism.<br>
> <br>
> Before I start drafting however, I'd like to hear the PDP's thoughts on whether this is worth doing.<br>
> <br>
> Thanks<br>
> <br>
> Andrew<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>
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/20260527/9c03f681/attachment-0001.html" rel="noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260527/9c03f681/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 27 May 2026 08:00:58 +0100<br>
From: "Dewole Ajao [AFRINIC]" <<a href="mailto:dewole.ajao@afrinic.net" target="_blank">dewole.ajao@afrinic.net</a>><br>
To: Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>><br>
Cc: RPD <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] Gauging Interest in a possible policy change<br>
Message-ID: <<a href="mailto:D4558FF9-B614-4172-A7BA-588D9EE6DB07@afrinic.net" target="_blank">D4558FF9-B614-4172-A7BA-588D9EE6DB07@afrinic.net</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Thanks, Andrew. <br>
<br>
While I am not currently making any comments on the subject matter at this point, <br>
<br>
I would like to commend the approach of coming to the list to check for interest in working together to solve what you believe may be a problem that needs to be solved.<br>
<br>
By getting to a wider understanding of whether or not there is a problem to be solved (and possibly the root causes), before policy text is proposed, the working group will be more efficient in its deliberations and even the first draft (if it ever gets to draft stages) will be more robust because it would ideally carry inputs from the discussions within the working group (even if members choose not to join as authors).<br>
<br>
This has been suggested to policy proposal authors over the years and I hope we can do more of this type of engagement in our policy development. <br>
<br>
With warm regards,<br>
Dewole.<br>
<br>
> On 27 May 2026, at 06:53, Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>> wrote:<br>
> <br>
> Hi Guys,<br>
> <br>
> I've been giving this a lot of thought and want to gauge interest in adding a policy relating to the code of conduct.<br>
> <br>
> Effectively, what I foresee is language added to the policy which acts similar to the IETF Notewell, and specifies appropriate/inappropriate conduct both on the PDP List and during PDP meetings.<br>
> <br>
> Ideally speaking this will also include enforcement actions for the code of conduct, appeal procedures etc. <br>
> <br>
> Within the IETF framework for example, disruptive behavior can result in the temporary or permanent loss of posting rights to the list, and such enforcement actions are subject to a robust appeal mechanism.<br>
> <br>
> Before I start drafting however, I'd like to hear the PDP's thoughts on whether this is worth doing.<br>
> <br>
> Thanks<br>
> <br>
> Andrew<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>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 27 May 2026 10:35:17 +0300<br>
From: Benson Muite <<a href="mailto:benson_muite@emailplus.org" target="_blank">benson_muite@emailplus.org</a>><br>
To: Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>>, RPD <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] Gauging Interest in a possible policy change<br>
Message-ID: <<a href="mailto:87jysp2tl6.fsf@emailplus.org" target="_blank">87jysp2tl6.fsf@emailplus.org</a>><br>
Content-Type: text/plain<br>
<br>
Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>> writes:<br>
Hi,<br>
<br>
(Will avoid gendered pronouns in case anyone feels left out)!<br>
<br>
> Hi Guys,<br>
><br>
> I've been giving this a lot of thought and want to gauge interest in adding<br>
> a policy relating to the code of conduct.<br>
><br>
> Effectively, what I foresee is language added to the policy which acts<br>
> similar to the IETF Notewell, and specifies appropriate/inappropriate<br>
> conduct both on the PDP List and during PDP meetings.<br>
<br>
This would probably be helpful. The IETF has much more transparency<br>
than AFRINIC. It is not structured as a private company so legal<br>
requirements for transparency in decision making, and in use of funds<br>
are stricter. Every other RIR is structured as an non-profit public<br>
benefit non governmental organization.<br>
<br>
Within the IETF, there are structures to get input from outside the IETF<br>
for some decisions, for example from ISOC a broader community of<br>
internet stakeholders.<br>
<br>
A code of conduct could help streamline useful input but should not not<br>
prevent dissenting voices from being heard - this can be difficult in<br>
large communities with diverse backgrounds.<br>
<br>
When there is disruptive behavior in the IETF, one can ask for further<br>
details and decide on whether a warranted point is being made - some of<br>
the post quantum standards are at least worthy of further individual<br>
investigation. IETF processes have originated from a specific culture,<br>
they are generally good, but could still be improved in terms of getting<br>
dissenting voices heard. Not all elements may work well for AFRINIC,<br>
but the experience is something that AFRINIC could learn from and use to<br>
improve.<br>
<br>
><br>
> Ideally speaking this will also include enforcement actions for the code of<br>
> conduct, appeal procedures etc.<br>
><br>
<br>
Codes of conduct are often not drafted by people with any legal<br>
background so are often guidelines for desired behavior and can be<br>
difficult to enforce in some jurisdictions as they maybe in conflict<br>
with local laws. Codes of conduct are easier to change than by-laws and<br>
as changes would probably be needed, having this would be better than<br>
putting it in the by-laws until they stabilise.<br>
<br>
> Within the IETF framework for example, disruptive behavior can result in<br>
> the temporary or permanent loss of posting rights to the list, and such<br>
> enforcement actions are subject to a robust appeal mechanism.<br>
><br>
> Before I start drafting however, I'd like to hear the PDP's thoughts on<br>
> whether this is worth doing.<br>
><br>
<br>
In my personal opinion this would be helpful, though my opinion is that<br>
AFRINIC also needs broader restructuring and if such a restructuring<br>
were to occur, how much would be carried over?<br>
<br>
Benson<br>
<br>
> Thanks<br>
><br>
> Andrew<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 27 May 2026 05:48:51 -0500<br>
From: Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>><br>
To: Andrew Alston <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>><br>
Cc: RPD <<a href="mailto:rpd@afrinic.net" target="_blank">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] Gauging Interest in a possible policy change<br>
Message-ID:<br>
<<a href="mailto:CAD_dc6g9tBzMH6O3NJC3wnirT%2BjHjZrTJCw_3-QfPhmLTWJD2Q@mail.gmail.com" target="_blank">CAD_dc6g9tBzMH6O3NJC3wnirT+jHjZrTJCw_3-QfPhmLTWJD2Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Andrew,<br>
<br>
AFRINIC does have an existing code of conduct[1] whether it is sufficient<br>
in present realities is a different thing.<br>
<br>
I do not believe the rpd need to have a different CoC but I think it may be<br>
appropriate for rpd to document the process to follow when AFRINIC CoC is<br>
violated.<br>
<br>
Regards<br>
[1] <a href="https://afrinic.net/code" rel="noreferrer" target="_blank">https://afrinic.net/code</a><br>
----<br>
Sent from my mobile<br>
kindly excuse typos<br>
<br>
On Wed, 27 May 2026, 12:55?am Andrew Alston, <<a href="mailto:aa@alstonnetworks.net" target="_blank">aa@alstonnetworks.net</a>> wrote:<br>
<br>
> Hi Guys,<br>
><br>
> I've been giving this a lot of thought and want to gauge interest in<br>
> adding a policy relating to the code of conduct.<br>
><br>
> Effectively, what I foresee is language added to the policy which acts<br>
> similar to the IETF Notewell, and specifies appropriate/inappropriate<br>
> conduct both on the PDP List and during PDP meetings.<br>
><br>
> Ideally speaking this will also include enforcement actions for the code<br>
> of conduct, appeal procedures etc.<br>
><br>
> Within the IETF framework for example, disruptive behavior can result in<br>
> the temporary or permanent loss of posting rights to the list, and such<br>
> enforcement actions are subject to a robust appeal mechanism.<br>
><br>
> Before I start drafting however, I'd like to hear the PDP's thoughts on<br>
> whether this is worth doing.<br>
><br>
> Thanks<br>
><br>
> Andrew<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260527/2c2c8a43/attachment.html" rel="noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260527/2c2c8a43/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 220, Issue 41<br>
************************************<br>
</blockquote></div>