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

[Thandeka Mseleku]

Dear Hendrik,

Thank you for your response.

While I appreciate your explanation, I remain unconvinced that the proposal
establishes a sufficient basis for mandatory hierarchical naming.

The discussion continues to distinguish between authenticating who may
create an object and validating the correctness, completeness, and
operational reliability of the information contained within that object.
Hierarchical naming may assist with identifying the maintainer of an
AS-SET, but it does not itself ensure that the routing information is
accurate, current, or safe for operational use.

For that reason, I do not believe the proposal has demonstrated that
registry-enforced naming is the least restrictive mechanism available.
Improving provenance should not automatically justify expanding registry
authority where existing operational practices and voluntary conventions
already provide flexibility for network operators.

As previously raised by several community members, the registry's role
should remain focused on maintaining accurate records and supporting
interoperability, rather than extending policy into areas where clear
technical necessity has not been demonstrated.

For these reasons, I continue to support the concerns raised by Asamkele,
Gugu, Tshepo and Nonhlanhla, and 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/20260719/c38fce13/attachment.html>