<div dir="auto"><p>Dear Taye,</p>
<p>Thank you for your thoughtful and mature intervention. I appreciate that you addressed the substance without turning the discussion into a contest over personalities, familiarity, or writing tools.</p>
<p>I agree that participation should remain open and inclusive, with each contributor responsible for what they submit. Moderation should address actual abuse or flooding, not the use of AI, translation, or drafting assistance.</p>
<p>I also appreciate your support for keeping the distinction between technical implementation and permanent policy authority. Community participation can guide and test an operational change, but it should not automatically convert every implementation choice into an institutional mandate.</p>
<p>This is the respectful and constructive discussion the PDWG needs.</p>
<p>Regards,<br>
Nonhlanhla</p>
<p></p></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Jul 2026, 6:19 pm <<a href="mailto:rpd-request@afrinic.net">rpd-request@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send RPD mailing list submissions to<br>
<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">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 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" rel="noreferrer">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" rel="noreferrer">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: AS-SETs ... Actual Stupidity and Artificial Intelligence<br>
(Taye Medoye)<br>
2. Re: Policy supremacy (<a href="mailto:ben.roberts@frinic.net" target="_blank" rel="noreferrer">ben.roberts@frinic.net</a>)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2026 18:15:26 +0200<br>
From: Taye Medoye <<a href="mailto:daniel.medoye@gmail.com" target="_blank" rel="noreferrer">daniel.medoye@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] AS-SETs ... Actual Stupidity and Artificial<br>
Intelligence<br>
Message-ID:<br>
<<a href="mailto:CACXLxYcXNzLKL8CzWjC2nkiBALwPsYe08A4vGWoCckORisfqpA@mail.gmail.com" target="_blank" rel="noreferrer">CACXLxYcXNzLKL8CzWjC2nkiBALwPsYe08A4vGWoCckORisfqpA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear All,<br>
<br>
I agree with Nonhlanhla that a technical specification does not<br>
automatically require an institutional mandate. Her view that policy<br>
creates permanence, interpretation risk, and precedent beyond the immediate<br>
database change is noted, and supported as highlighted herein. In her<br>
opinion, which l agree with, is that ?It affects AFRINIC, not resource<br>
holders? is therefore not a complete safeguard, because AFRINIC remains the<br>
institution interpreting and enforcing the resulting rule. Until this<br>
standard is reviewed, and or reversed, it stands.<br>
<br>
On AI tools, the standard should be tool-neutral. Moderate actual flooding<br>
or automated nuisance, but judge ordinary contributions by their substance.<br>
A person who reviews and submits a message remains responsible for it.<br>
<br>
On this point, l am inclined to agree with Paul on the need to use AI tools in<br>
- order to improve the clarity of expression and to assist with<br>
language in their<br>
contribution. I also support the view that participants using AI tools are<br>
encouraged to align such tools with brevity and technical clarity.<br>
<br>
In closing, l support the position of Nonhlanhla that the registry should<br>
implement what the system technically requires. It should not turn<br>
implementation convenience into permanent policy authority.<br>
<br>
<br>
Taye Medoye.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/7f9da57c/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/7f9da57c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jul 2026 18:18:29 +0200<br>
From: "<a href="mailto:ben.roberts@frinic.net" target="_blank" rel="noreferrer">ben.roberts@frinic.net</a>" <<a href="mailto:ben.roberts@afrinic.net" target="_blank" rel="noreferrer">ben.roberts@afrinic.net</a>><br>
To: Tshepo Masuku <<a href="mailto:TshepoMasuku26@hotmail.com" target="_blank" rel="noreferrer">TshepoMasuku26@hotmail.com</a>><br>
Cc: "<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>" <<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
Subject: Re: [rpd] Policy supremacy<br>
Message-ID: <AC68E767-E105-F04B-B38D-B1C26DE99442@hxcore.ol><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/8737fe94/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/8737fe94/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" 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>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 222, Issue 150<br>
*************************************<br>
</blockquote></div>