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

[Frank Habicht]

Hi,

On 7/29/2026 9:06 PM, Tshepo Masuku wrote:
[snip]
> Consider this case:
> 
> AS65000:AS-CUSTOMERS exists in the AFRINIC database and is maintained by 
> the previous holder or a delegated maintainer. AS65000 later changes 
> holder or authoritative registry. The proposal does not define what 
> happens to that AS-SET.

I am convinced that when AfriNIC deletes an IPv4 allocation - an inetnum 
object from the database, then AfriNIC also deleted inetnum objects of 
subnets. These people are paid to keep the database in order.

I see in January object
inetnum:        154.66.228.0 - 154.66.231.255
was deleted [1]. And the same day object
inetnum:        154.66.229.0 - 154.66.229.255
was deleted as well. I trust this was AfriNIC procedure, as it should be.

So if AfriNIC were in the future (or maybe already now) to delete an 
aut-num object (an ASN), then I am convinced that it will be in the 
AfriNIC procedures that hierarchical AS-SET objects beginning with that 
ASN will also get deleted.

I would like to say that this detail does not need to be written in the 
proposal. Just like the mechanism for IPv4 resources (subnets) is not 
written in policy.

Thank you.

Frank Habicht
operating a few networks in Africa

[1]
the /22 is the allocation - delegated file from last year:
afrinic|MU|ipv4|154.66.228.0|1024|20131209|allocated|F36BE2CF



> If the old object remains while the new holder creates the same 
> hierarchical name in the new authoritative source, two objects with the 
> same supposedly unique name may coexist. Both may have been validly 
> authorised when created, but they represent different holders and 
> different points in time.

per above, I don't believe the object will remain.


> What is needed is a documented and tested state transition explaining:
this can be internal AfriNIC documentation.
And if you want you can ask AfriNIC to share it.

> whether dependent AS-SETs move with the ASN;
the holder can create the AS-SET object in the new registry.
AfriNIC will surely ensure the AS-SET object(s) get deleted when the 
aut-num is moving away (see above).
I can not confirm, but AfriNIC can.

> whether they remain under delegated maintainers;
> 
> whether the old source publishes a tombstone or transfer status;
> 
> whether the new holder may recreate the same name elsewhere; and

of course a holder may create a new hierarchical AS-SET in the new 
registry...


> how tools distinguish the current authoritative object from the 
> historical one.
> 
> 
> Without that, the statement that the ASN-to-registry map always provides 
> a deterministic authoritative source is not established by running 
> implementation.

when an aut-num gets deleted, any hierarchical AS-SET with that ASN gets 
deleted.
==> ASN-to-registry map has deterministic authoritative source

Regards,
Frank