Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

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

Mphoentle Mokheseng ST10120874 at vcconnect.edu.za
Thu Jul 30 07:47:54 UTC 2026


Dear Hendrik,

Thank you for clarifying the claim.

I understand that the proposal does not guarantee a continuous or globally authoritative identity. It guarantees only that a new AS-SET name is unique and authenticated within the AFRINIC database at the moment of creation.

That clarification does not remove the objection. It defines the limited benefit more precisely.

Creation-time authentication confirms who was authorised to create an object under a particular name. It does not validate the object’s contents, guarantee that those contents remain correct, establish continuing control, or make the object authoritative across every database and operational context in which the name may later be used.

Those are not invented claims attributed to supporters. They are relevant limits of the actual guarantee being offered.

The policy therefore closes one narrow naming and attribution gap, while leaving the more consequential questions of data quality, continued accuracy, cross-database use, and operational trust unresolved. The community is entitled to ask whether that narrow benefit justifies a mandatory naming rule and the additional registry enforcement attached to it.

It is also not enough to answer each concern by repeating that the proposal is “only about naming.” If it is only about naming, then its necessity must be demonstrated at that same narrow level. The proposal should show concrete AFRINIC-specific harm caused by the creation of new flat AS-SET names, explain why existing validation or tooling cannot address it, and demonstrate that mandatory hierarchy is the least coercive remedy.

So the objection is not to a claim nobody made.

The objection is that the proposal offers a limited creation-time assurance, but seeks to convert that limited assurance into a mandatory policy obligation. Authentication of creation is not the same as correctness, operational safety, or enduring authority.

That distinction remains central, and for that reason I continue to object to the proposal as written.

Regards,

Mphoentle
Disclaimer This email and the information contained herein are Advtech Ltd confidential and are protected by law. Please navigate to our website for more information https://www.groupadvtech.com. Use of this information or this email by any person for any purposes other than that for which it is intended is prohibited and may result in civil and/or criminal liability. This email is not to be shared with any 3rd parties not included within this email, without the written consent of its Author. If you have received this message in error, please notify Advtech immediately, telephone number +27 11 676 8000. Advtech leads the private sector in the fields of education and resourcing, contributing meaningfully towards the sustainable development of human capacity in South Africa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260730/11baf64c/attachment.html>


More information about the RPD mailing list