AFPUB-2026-ASN-001-DRAFT01 - Require newly created AS-SETs to have hierarchical names - AFRINIC

AFPUB-2026-ASN-001-DRAFT01: Require newly created AS-SETs to have hierarchical names

Proposal Details
Proposal Name	Require newly created AS-SETs to have hierarchical names
ID	AFPUB-2026-ASN-001-DRAFT01	Date Submitted	2020-12-07
Author(s)	Refer to Proposal Tab	Status	Archived

Adds new section 7.8 article to the CPM, as follows:

Proposed
7.8 AS-SET 1. AS-SETs need to have hierarchical names at the time of creation in the AFRINIC whois database. 2. The definition of a hierarchical set name is already defined in RFC 2622 Section 5 (https://www.rfc-editor.org/rfc/rfc2622.html#page-13). A summary is provided below: * There must be at least one colon (:) character in the name * The first element of the name must be an ASN * The second element of the name must be an AS-SET name starting with 'AS-' * Any further elements can be either ASNs or AS-SET names 3. Other set types such as route sets are excluded. 4. Existing AS-SETs will not be renamed due to the massive data inconsistencies this would create, and because there is no way to programmatically determine which ASNs the existing AS-SETs in the AFRINIC DB relate to. 5. Existing AS-SETs which have a non-hierarchical name may continue to do so; 6. Editing an existing AS-SET MUST NOT require the maintainer to also rename the set to have a hierarchical name.

Proposed

7.8 AS-SET 1. AS-SETs need to have hierarchical names at the time of creation in the AFRINIC whois database. 2. The definition of a hierarchical set name is already defined in RFC 2622 Section 5 (https://www.rfc-editor.org/rfc/rfc2622.html#page-13). A summary is provided below: * There must be at least one colon (:) character in the name * The first element of the name must be an ASN * The second element of the name must be an AS-SET name starting with 'AS-' * Any further elements can be either ASNs or AS-SET names 3. Other set types such as route sets are excluded. 4. Existing AS-SETs will not be renamed due to the massive data inconsistencies this would create, and because there is no way to programmatically determine which ASNs the existing AS-SETs in the AFRINIC DB relate to. 5. Existing AS-SETs which have a non-hierarchical name may continue to do so; 6. Editing an existing AS-SET MUST NOT require the maintainer to also rename the set to have a hierarchical name.

5. References

APNIC have implemented this under PROP-151: https://www.apnic.net/community/policy/proposals/prop-151/
RIPE have implemented this under NWI-19: https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items/
LACNIC implemented this as part of their initial IRR daemon deployment.
ARIN have accepted the request to enforce hierarchical naming: https://www.arin.net/participate/community/acsp/consultations/2025/2025-1/

AFRINIC is the only major RIR which has not currently implemented this feature, or is not currently working towards implementing it. If/when AFRINIC implements it, AS-SET squatting in the 5 major RIRs will no longer be possible and AS-SETs will be have become more secure globally.

Revision History

Date	Details
15th May 2026	Version 1: AFPUB-2026-ASN-001-DRAFT01 Initial Draft Posted to RPD

Require newly created AS-SETs to have hierarchical names

AFPUB-2026-ASN-001-DRAFT01: Require newly created AS-SETs to have hierarchical names

Revision History

AFRINIC Staff Assessment (To be available soon)