prop-151: Restricting non-hierarchical as-set

Proposal text prop-151-v001
Objective

This proposal would restrict APNIC account holders from creating a non-hierarchical as-set, and notify all Members who already have non-hierarchical as-set that it is recommended they move to a hierarchical as-set.

Current status To be discussed at APNIC 55
Authors

Aftab Siddiqui

Relevant forum Policy SIG
Previous versions n/a
Secretariat impact assessment

APNIC notes this proposal would restrict APNIC account holders from
creating a non-hierarchical as-set in the APNIC Whois Database.
APNIC would be required to notify all Members who already have a
non-hierarchical as-set to recommend they move to a hierarchical
as-set as defined in Section 5 of RFC2622.

APNIC also notes that an as-set object can only be created by the
maintainer of the ASN that is used in the as-set object, and this
must be the only allowed method for creating a hierarchical as-set
in the APNIC Whois Database.

This proposal may require changes to APNIC systems. If this proposal
reaches consensus and endorsed by the EC, implementation may be
completed within three months.

Proposal history
20 January 2023 Version 1 posted to the Policy SIG mailing list for discussion and community development.