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

[Jaco Kroon]

Sorry, just a correction, APNIC should block the creation ... but even 
if they don't since no tool should ever query them for that name ...

On 2026/07/27 13:01, Jaco Kroon via RPD wrote:

> Hi,
>
> On 2026/07/27 12:19, Phetulo Dhlamini wrote:
>> Dear Jaco,
>>
>> As I have been following the discussions very closely, thank you for 
>> taking the time to explain your position. I accept that hierarchical 
>> naming can strengthen creation authorisation within the AFRINIC 
>> database.
>>
>> I have a different concern, however. The proposal binds an AS-SET 
>> name to an ASN, but it does not bind that name to a particular IRR 
>> source.
>>
>> For example, AS12345:AS-CUSTOMERS identifies the ASN namespace, but 
>> it does not tell a resolver whether the intended object is from 
>> AFRINIC, RADB, RIPE, or another source. IRR software already 
>> recognises that sets with the same primary key may exist in different 
>> sources and may return them separately.
>
> It's implicit since a specific AS is already bound to a specific RIR.  
> When looking for a hierarchical name a tool first maps the AS to a 
> specific RIR, then queries that RIR for the name, as such if you 
> deploy AS12345:AS-CUSTOMERS to both RIPE and APNIC, only RIPE will 
> ever be queried for it.  And RIPE should block creation of the 
> relevant object since they're not authoritative for the specific AS 
> anyway.
>
> Kind regards,
> Jaco
>
>
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd