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

[Hendrik Visage]

Good day Tshepo,

Three short points, and then I'll leave the record to the Co-Chairs.

First: your scenario requires an inter-RIR ASN transfer. AFRINIC does
not perform inter-RIR transfers - not for ASNs, not for anything.
There is no policy for it in the CPM, and the other registries list
AFRINIC as not approved for transfers in either direction. So the
event your whole scenario depends on cannot occur in this region
under any rule that exists - and a NAMING proposal can neither create
that capability nor govern it. If our community one day adopts an
inter-RIR transfer policy, THAT policy is where object handling on
transfer gets defined - which is exactly where the deployed
registries define it today (APNIC's transfer conditions, for example,
spell out which dependent objects get deleted when a resource
moves). You are asking the wrong document to answer, before the
right document exists.

Second: the "how do tools distinguish the current authoritative
object from the historical one" question has a running answer
already: the delegated statistics files every RIR publishes daily,
which record each ASN's current registry - transfers included,
single-valued at every instant. That is the map the whole IRR
tooling world uses today. And notice: under flat names your
succession scenario is strictly worse, because then there is no map
at all.

Third, on Question 7: I asked for the technical issues and real-world
examples where this policy would negatively affect YOUR current or
future operations. A hypothetical relying operator, in a transfer
type that is not available in this region, is not that. So I note,
with appreciation for the attempt, that Question 7 still stands
unanswered. And to be fair on the record: of the six questions of
(015344), yours in (015348) remain the only point-by-point answers
given - answers I credited in (015404) - the rest of the opposition
has answered none.

The record is now complete enough for the Co-Chairs to do their work,
and I am content to leave it to them.

Regards,
Hendrik Visage (AS329532; also AS213481)