<div dir="auto"><p>Hi Saul,</p>
<p>That split is too neat. Community input does not require every operational change to become binding policy. AFRINIC can consult publicly, document the implementation, and remain accountable without creating another enforcement rule.</p>
<p>Once policy is adopted, the community does not enforce it. AFRINIC does. The question remains: what technical result requires policy that a transparent operational process cannot deliver?</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, 8:44 am <<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: RPD Digest, Vol 222, Issue 111 (Fundiswa Nadia Maseko)<br>
2. Re: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Thandeka Mseleku)<br>
3. Re: [Last Call] Draft Policy Proposal - Hierarchical Names<br>
for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Saul Stein)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 21 Jul 2026 08:34:21 +0200<br>
From: Fundiswa Nadia Maseko <<a href="mailto:fundiswanadia2@gmail.com" target="_blank" rel="noreferrer">fundiswanadia2@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Subject: Re: [rpd] RPD Digest, Vol 222, Issue 111<br>
Message-ID:<br>
<<a href="mailto:CABV0QcQFcLoOaoZ97xyHmOBc7fU1gDJa74usFNv8mMC6ehPj5A@mail.gmail.com" target="_blank" rel="noreferrer">CABV0QcQFcLoOaoZ97xyHmOBc7fU1gDJa74usFNv8mMC6ehPj5A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Jordi,<br>
<br>
Kone's point is not that every RIR must follow the same procedure. Rather,<br>
his point is that the same technical outcome has been achieved elsewhere<br>
without making it binding policy.<br>
<br>
That makes the choice of mechanism relevant.<br>
<br>
A policy process should not be used simply because it is available. The<br>
appropriate approach is to use the least powerful mechanism capable of<br>
solving the operational problem. If AFRINIC can implement hierarchical<br>
naming as an IRR operational change, then proponents should explain what<br>
additional technical benefit policy provides.<br>
<br>
Policy introduces enforcement, precedent, and rigidity. Those costs require<br>
justification. Saying that "the community prefers it" or "the community<br>
wants to move faster" does not explain why an operational matter should<br>
become a policy obligation.<br>
<br>
Kone also raised specific factual examples. Those examples deserve direct<br>
responses. Suggesting that only those with extensive experience across all<br>
RIRs may question the proposal risks turning expertise into gatekeeping<br>
rather than evidence-based discussion.<br>
<br>
The central question therefore remains: what can mandatory policy achieve<br>
here that an operational implementation cannot?<br>
<br>
Until that question is clearly answered, I support Kone's position and<br>
remain opposed.<br>
<br>
Regards,<br>
<br>
Fundiswa<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/23554e60/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/23554e60/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Jul 2026 08:36:39 +0200<br>
From: Thandeka Mseleku <<a href="mailto:mselekuthandeka80@gmail.com" target="_blank" rel="noreferrer">mselekuthandeka80@gmail.com</a>><br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Cc: <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
Message-ID:<br>
<CA+mVb0=<a href="mailto:12opts37KFc4juGwkd0ZCP_d4F99cm2FirBCSSYqyHw@mail.gmail.com" target="_blank" rel="noreferrer">12opts37KFc4juGwkd0ZCP_d4F99cm2FirBCSSYqyHw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear colleagues,<br>
<br>
I support Kone's observations. The examples from other RIRs show that<br>
hierarchical AS-SET naming can be implemented through operational practices<br>
without necessarily becoming a policy requirement.<br>
<br>
Before introducing additional policy obligations, it is important to<br>
demonstrate why existing operational approaches would not adequately<br>
address the concerns raised. Where practical alternatives exist, they<br>
deserve careful consideration.<br>
<br>
Policy should remain focused on addressing clearly demonstrated needs<br>
rather than replacing operational decisions that can be managed through<br>
established registry practices.<br>
<br>
For these reasons, I remain opposed to AFPUB-2026-ASN-001-DRAFT02.<br>
<br>
BR,<br>
Thandeka Mseleku<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/f7a2a1e7/attachment-0001.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/f7a2a1e7/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 21 Jul 2026 06:43:41 +0000<br>
From: Saul Stein <<a href="mailto:saul@enetworks.co.za" target="_blank" rel="noreferrer">saul@enetworks.co.za</a>><br>
To: Thandeka Mseleku <<a href="mailto:mselekuthandeka80@gmail.com" target="_blank" rel="noreferrer">mselekuthandeka80@gmail.com</a>>, "<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>"<br>
<<a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a>><br>
Cc: "<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>" <<a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a>><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical<br>
Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
Message-ID:<br>
<<a href="mailto:JNAP275MB1258655644EA68740D2EE98A8EC22@JNAP275MB1258.ZAFP275.PROD.OUTLOOK.COM" target="_blank" rel="noreferrer">JNAP275MB1258655644EA68740D2EE98A8EC22@JNAP275MB1258.ZAFP275.PROD.OUTLOOK.COM</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
So let?s look at this differently:<br>
<br>
Policy: community driven<br>
Operational: AFRINIC driven (no community input ? its operational)<br>
<br>
The statements that have been made is that the policy is giving to many rights to the ?organisation?<br>
<br>
Now, you are suggesting that this idea and it is managed be taken away from the community.<br>
<br>
Understand, if this is operational, AFRIINC decide what and how.<br>
<br>
Thus having this as a policy is more empowering.<br>
<br>
<br>
<br>
From: Thandeka Mseleku <<a href="mailto:mselekuthandeka80@gmail.com" target="_blank" rel="noreferrer">mselekuthandeka80@gmail.com</a>><br>
Sent: Tuesday, 21 July 2026 08:37<br>
To: <a href="mailto:rpd@afrinic.net" target="_blank" rel="noreferrer">rpd@afrinic.net</a><br>
Cc: <a href="mailto:rpd-owner@afrinic.net" target="_blank" rel="noreferrer">rpd-owner@afrinic.net</a><br>
Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)<br>
<br>
Dear colleagues,<br>
<br>
I support Kone's observations. The examples from other RIRs show that hierarchical AS-SET naming can be implemented through operational practices without necessarily becoming a policy requirement.<br>
<br>
Before introducing additional policy obligations, it is important to demonstrate why existing operational approaches would not adequately address the concerns raised. Where practical alternatives exist, they deserve careful consideration.<br>
<br>
Policy should remain focused on addressing clearly demonstrated needs rather than replacing operational decisions that can be managed through established registry practices.<br>
<br>
For these reasons, I remain opposed to AFPUB-2026-ASN-001-DRAFT02.<br>
<br>
BR,<br>
Thandeka Mseleku<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20260721/5b95665e/attachment.html" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/pipermail/rpd/attachments/20260721/5b95665e/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 113<br>
*************************************<br>
</blockquote></div>