prop-150: ROA/whois object with Private, Reserved and Unallocated (reserved/available) Origin ASN

Proposal text prop-150-v002
Objective

This proposal suggests APNIC restrict an account holder’s right to create ROAs with private, reserved, or unallocated ASNs.

The proposal also suggests APNIC notify account holders if the Origin ASN in their ROA is unallocated (reserved/available), and to not automatically renew ROAs with unallocated (reserved/available) ASNs.

Current status To be discussed at APNIC 55
Authors

Aftab Siddiqui

Relevant forum Policy SIG
Previous versions prop-150-v001
Secretariat impact assessment

A similar proposal was presented at the APNIC 52 OPM and was accepted
as a guideline with the understanding that it will assist APNIC
account holders in not creating ROAs (Routing Origin Authorizations)
with Private, Reserved, and unallocated ASN ranges. This guideline was
published in December 2021.

APNIC notes this proposal would restrict an account holder’s ability
to create ROAs (Routing Origin Authorizations) with private, reserved,
or unallocated ASNs (Autonomous System Numbers) as listed on the IANA
website, except for AS 0 (zero), which may be used to identify
non-routed networks. Internet number resources visible in account holders’
MyAPNIC portal can only be used to create ROAs.

APNIC must notify the account holder as to why the ASN used to create the
ROA is unacceptable and must not renew the ROAs and route/route6 objects
currently in the APNIC Whois Database. All these unacceptable objects
must automatically be deleted from the APNIC Whois Database.

APNIC also needs to notify the account holder in case the Origin ASN used
in creating a ROA is unallocated and/or reserved and should be removed,
and the same proposed solution would apply for creating corresponding
route/route6 objects in the APNIC Whois Database.

This proposal may require changes to APNIC systems and procedures. 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.

30 January 2023

Version 2 posted to the Policy SIG mailing list for discussion and community development.