[rpd] [Last Call] Draft Policy Proposal - Hierarchical Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)

[Thandeka Mseleku]

👍

Thandeka reacted via Gmail
<https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=et&utm_campaign=emojireactionemail#app>

On Tue, 21 Jul 2026, 10:16 Gugu Dhlamini, <gugudhlamini343 at gmail.com> wrote:

> Dear Saul,
>
> That framing creates a false choice.
>
> An operational change does not have to mean “no community input.” It can
> be publicly documented, consulted on, tested, reviewed, and reversed where
> necessary. The question is not whether the community may advise AFRINIC. It
> may. The question is whether that advice must become a binding policy
> obligation.
>
> Policy is not automatically empowering. Once adopted, the community does
> not enforce it. AFRINIC interprets, administers, and enforces it. The
> community discusses; the registry holds the lever. Confusing participation
> with continuing authority is precisely how mandate laundering occurs.
>
> If the same technical outcome can be achieved through a transparent,
> community-reviewed operational process, then policy adds an enforcement
> layer without adding technical value.
>
> Kone’s question therefore remains unanswered: what technical necessity
> requires binding policy rather than an operational implementation?
>
> I support Kone’s observations and remain opposed to
> AFPUB-2026-ASN-001-DRAFT02.
>
> Regards,
> Gugu
>
>
>
> On Tue, 21 Jul 2026, 8:46 am Saul Stein via RPD <rpd at afrinic.net> wrote:
>
>> So let’s look at this differently:
>>
>>
>>
>> Policy: community driven
>>
>> Operational: AFRINIC driven (no community input – its operational)
>>
>>
>>
>> The statements that have been made is that the policy is giving to many
>> rights to the “organisation”
>>
>>
>>
>> Now, you are suggesting that this idea and it is managed be taken away
>> from the community.
>>
>>
>>
>> Understand, if this is operational, AFRIINC decide what and how.
>>
>>
>>
>> Thus having this as a policy is more empowering.
>>
>>
>>
>>
>>
>>
>>
>> *From:* Thandeka Mseleku <mselekuthandeka80 at gmail.com>
>> *Sent:* Tuesday, 21 July 2026 08:37
>> *To:* rpd at afrinic.net
>> *Cc:* rpd-owner at afrinic.net
>> *Subject:* Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical
>> Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
>>
>>
>>
>> Dear colleagues,
>>
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>>
>> Policy should remain focused on addressing clearly demonstrated needs
>> rather than replacing operational decisions that can be managed through
>> established registry practices.
>>
>>
>>
>> For these reasons, I remain opposed to AFPUB-2026-ASN-001-DRAFT02.
>>
>>
>>
>> BR,
>>
>> Thandeka Mseleku
>> _______________________________________________
>> RPD mailing list
>> RPD at afrinic.net
>> https://lists.afrinic.net/mailman/listinfo/rpd
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/vnd.google.email-reaction+json
Size: 37 bytes
Desc: not available
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e4097517/attachment.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260721/e4097517/attachment.html>