<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">Hello Asamkele,<br>
Respectfully, this proposal does exactly what you're asking for — it maintains uniqueness. Flat AS-SET names can be registered by anyone, so two operators can create the same name and there is no way to tell afterwards which ASN it belongs to. That is a uniqueness failure in the registry's own data, and fixing it is squarely within the mandate you describe, not an expansion of it. The proposal adds no governance layer: it applies only to newly created AS-SETs, leaves existing objects untouched, and doesn't extend to route-sets or anything else. And the operational necessity is already demonstrated — APNIC, RIPE, ARIN, and LACNIC have all implemented hierarchical AS-SET naming, which would leave AFRINIC as the only registry whose IRR data still permits name collisions.<br>
Regards</p>
<hr style="border: 0; height: 1px; background: #333; background-image: linear-gradient(to right, #ccc, #333, #ccc);">
<p dir="auto">Hendrik Visage<br>
Director/Owner<br>
HeViS.Co Systems t/a Envisage Cloud Solutions<br>
<a href="mailto:hvisage@hevis.co.za" style="color: #3983C4;">hvisage@hevis.co.za</a><br>
GSM/SMS/Signal: +27-84-612-5345<br>
InstantMessenger: <a href="https://t.me/hvisage" style="color: #3983C4;">https://t.me/hvisage</a></p>
<p dir="auto">On 17 Jul 2026, at 19:26, Asamkele Menzeleli wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">Hello everyone,</p>
<p dir="auto">I object to this proposal.</p>
<p dir="auto">I also agree with Nonhlanhla's point regarding mandate laundering. We<br>
should be careful not to confuse policy development with expanding<br>
institutional authority.</p>
<p dir="auto">Policies should reflect demonstrated operational realities and technical<br>
necessity. They should not become governance mechanisms that gradually<br>
enlarge the registry's role beyond maintaining uniqueness, accurate<br>
records, and operational coordination.</p>
<p dir="auto">A registry should record reality, not create new layers of governance<br>
through policy.</p>
<p dir="auto">Regards,<br>
Asamkele Menzeleli</p>
</blockquote>
</div>
</div>
</body>
</html>