[rpd] RPD Digest, Vol 222, Issue 111

Tue Jul 21 07:35:16 UTC 2026

Dear Saul,

I understand your point about community involvement, and I agree that the
community should have a voice in how AFRINIC operates.
That said, I think the question is slightly different.

Nobody is suggesting that the community should be excluded. The question is
whether hierarchical naming needs to be a policy at all if the same result
can be achieved operationally.

If the objective is exactly the same, then why is a policy necessary? What
does making it mandatory through policy achieve that an operational
implementation cannot?
You mention that an operational approach would leave AFRINIC to decide the
details. That's true, but operational changes can still be transparent and
informed by community feedback. Not every operational decision has to
become a policy requirement.

For me, the important issue is using the right mechanism for the problem.
If an operational solution is sufficient, then I'd like to understand what
specific benefit is gained by making it a policy obligation instead.

I think answering that question would help move the discussion forward.

Kind regards,
Fundiswa

On Tue, 21 Jul 2026, 08:44 , <rpd-request at afrinic.net> wrote:

> Send RPD mailing list submissions to
>         rpd at afrinic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.afrinic.net/mailman/listinfo/rpd
> or, via email, send a message with subject or body 'help' to
>         rpd-request at afrinic.net
>
> You can reach the person managing the list at
>         rpd-owner at afrinic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of RPD digest..."
>
>
> Today's Topics:
>
>    1. Re: RPD Digest, Vol 222, Issue 111 (Fundiswa Nadia Maseko)
>    2. Re: [Last Call] Draft Policy Proposal - Hierarchical Names
>       for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Thandeka Mseleku)
>    3. Re: [Last Call] Draft Policy Proposal - Hierarchical Names
>       for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02) (Saul Stein)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 21 Jul 2026 08:34:21 +0200
> From: Fundiswa Nadia Maseko <fundiswanadia2 at gmail.com>
> To: rpd at afrinic.net
> Subject: Re: [rpd] RPD Digest, Vol 222, Issue 111
> Message-ID:
>         <
> CABV0QcQFcLoOaoZ97xyHmOBc7fU1gDJa74usFNv8mMC6ehPj5A at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Dear Jordi,
>
> Kone's point is not that every RIR must follow the same procedure. Rather,
> his point is that the same technical outcome has been achieved elsewhere
> without making it binding policy.
>
> That makes the choice of mechanism relevant.
>
> A policy process should not be used simply because it is available. The
> appropriate approach is to use the least powerful mechanism capable of
> solving the operational problem. If AFRINIC can implement hierarchical
> naming as an IRR operational change, then proponents should explain what
> additional technical benefit policy provides.
>
> Policy introduces enforcement, precedent, and rigidity. Those costs require
> justification. Saying that "the community prefers it" or "the community
> wants to move faster" does not explain why an operational matter should
> become a policy obligation.
>
> Kone also raised specific factual examples. Those examples deserve direct
> responses. Suggesting that only those with extensive experience across all
> RIRs may question the proposal risks turning expertise into gatekeeping
> rather than evidence-based discussion.
>
> The central question therefore remains: what can mandatory policy achieve
> here that an operational implementation cannot?
>
> Until that question is clearly answered, I support Kone's position and
> remain opposed.
>
> Regards,
>
> Fundiswa
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/23554e60/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 21 Jul 2026 08:36:39 +0200
> From: Thandeka Mseleku <mselekuthandeka80 at gmail.com>
> 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)
> Message-ID:
>         <CA+mVb0=
> 12opts37KFc4juGwkd0ZCP_d4F99cm2FirBCSSYqyHw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/f7a2a1e7/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 21 Jul 2026 06:43:41 +0000
> From: Saul Stein <saul at enetworks.co.za>
> To: Thandeka Mseleku <mselekuthandeka80 at gmail.com>, "rpd at afrinic.net"
>         <rpd at afrinic.net>
> Cc: "rpd-owner at afrinic.net" <rpd-owner at afrinic.net>
> Subject: Re: [rpd] [Last Call] Draft Policy Proposal - Hierarchical
>         Names for New AS-SETs (AFPUB-2026-ASN-001-DRAFT02)
> Message-ID:
>         <
> JNAP275MB1258655644EA68740D2EE98A8EC22 at JNAP275MB1258.ZAFP275.PROD.OUTLOOK.COM
> >
>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.afrinic.net/pipermail/rpd/attachments/20260721/5b95665e/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd
>
>
> ------------------------------
>
> End of RPD Digest, Vol 222, Issue 113
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260721/d31e7cf0/attachment-0001.html>