[rpd] Require newly created AS-SETs to have hierarchical names AFPUB-2026-ASN-001-DRAFT01.

[James Bensley]

Hi Jaco,

Thank you for the support and your feedback.

I wrote the original proposal. Regarding this comment:

"The only thing that I found weird is that the second element has to be a name, why would "ASnum:ASnum2:AS-name" not be acceptable?"

If you have a use case for that, then that could be added to the proposal. Do you have a use case/requirement for this? I think this usage is very rare, but if you have this use case, please speak up :)


Regarding this comment:

"The purpose/function of "3. Other set types such as route sets are excluded." is unclear - everything else speaks specifically to AS-SET so why is this mention required?"

Because route-sets can also support hierarchical names and in the past people have had the thought "well if we're making this change for AS-SETs let's also making it for Route-Sets whilst we're here" - but route-sets are extremely rarely used today and this just adds scope which I think isn't needed. So it was just about trying to stop that scope creep.


With kind regards,
James Bensley (he/him)

________________________________________
From: Jaco Kroon <jaco at uls.co.za>
Sent: 21 May 2026 14:06
To: dacostadarwin at gmail.com <dacostadarwin at gmail.com>; rpd at afrinic.net <rpd at afrinic.net>
Subject: Re: [rpd] Require newly created AS-SETs to have hierarchical names AFPUB-2026-ASN-001-DRAFT01.

Hi,

Definitely in support.

The only thing that I found weird is that the second element has to be a
name, why would "ASnum:ASnum2:AS-name" not be acceptable?

The purpose/function of "3. Other set types such as route sets are
excluded." is unclear - everything else speaks specifically to AS-SET so
why is this mention required?

Kind regards,
Jaco

On 2026/05/20 19:37, dacostadarwin at gmail.com wrote:

> Dear PDWG,
>
> We have received a new draft policy proposal - Require newly created AS-SETs to have hierarchical names, ID AFPUB-2026-ASN-001-DRAFT01 from author James Bensley.
>
> The proposal contents are published at:
> https://afrinic.net/policy/proposals/afpub-2026-asn-001-draft01
>
> We encourage you to take some time to go through the proposal contents and  provide feedback as follows:
>
> a) Do you support or oppose the proposal?
>
> b) If you oppose the proposal, state your reasons?
>
> c) Is there anything in the proposal that is not clear?
>
> d) What changes could be made to this proposal to make it more effective?
>
> Regards,
> Vincent Ngundi & Darwin Da Costa
> AFRINIC PDWG Co-Chairs
>
>
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd

_______________________________________________
RPD mailing list
RPD at afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
[CompanySignature]
Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: hello at inter.link<mailto:hello at inter.link> | Web: inter.link<https://inter.link>