[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:28 PM, Tshepo Masuku wrote:
[snip]
> The proposal can reasonably claim that a new name is unique and 
> authenticated inside the AFRINIC database at creation time. It should 
> not be credited with continuous, globally deterministic source 
> resolution unless that behaviour is demonstrated across the actual 
> tooling that consumes the data.

I think this is too high a threshold.
*maybe*, just maybe, the tooling will only get created after the policy 
is in place?
Or maybe it will get created in two weeks regardless.
This is not a good reason to stop this useful proposal.

You don't have to get proof of the existence of the good tooling.
We just have to accept the possibility of the good tooling.


> Third, you asked for effects on current or future operations, but then 
> excluded the future scenario because AFRINIC does not currently support 
> inter-RIR ASN transfers. Those positions cannot both stand.

When a future scenario with inter-RIR ASN transfers is considered as 
policy proposal, all concerns can be addressed. Or consciously left for 
AfriNIC internal procedures.

> A policy intended to remain in force cannot use the present absence of 
> another policy as proof that its own assumptions will remain valid 
> indefinitely.

Any policy can be reviewed at a later stage. Assumptions can be made and 
reviewed later.

> If a future transfer policy must define the object 
> transition, then that confirms the present proposal does not define it.

I don't see this as a problem.

> I am not asking this proposal to solve every transfer problem. I am 
> asking that its text and Impact Assessment claim only what the mechanism 
> actually guarantees.

I think they do. Don't they?

> The unresolved issue is therefore specific: the proposal creates local, 
> creation-time naming and authentication rules, while its supporters 
> attribute to it a global and continuing authority property that has not 
> been demonstrated in running tools.

I have created AS37084:AS-37084-PEERS
Can you create this in any other IRR?

Or can you create
as-set:         AS3320:AS-DTAG
in AfriNIC?


Thanks,
Frank