AFPUB-2019-GEN-006-DRAFT03

When AFRINIC issues a ROA with AS0 for unallocated address space under AFRINIC’s administration, BGP announcements covering this space will be marked as Invalid by networks doing RPKI based BGP Origin Validation using APNIC’s TAL.

When AFRINIC issues a ROA with AS0 for unallocated address space under AFRINIC’s administration, BGP announcements covering this space will be marked as Invalid by networks doing RPKI based BGP Origin Validation using AFRINIC’s TAL.

Address space can only be allocated once the ROA or ROAs with origin AS0 have been fully removed and are not visible in the repositories.

The AS0 ROAs could be under a distinct Trust Anchor Locator (TAL), so it becomes an opt-in service and provides separate measurements, at least in the initial deployment phases. This and other operational details are left to the discretion of AFRINIC.

AFRINIC will create ROAs with origin AS0 for all the unallocated and unassigned address space (IPv4 and IPv6) for which it is the current administrator.

unallocated and unassigned space here means available and reserved space as per the AFRINIC extended delegated stats file. New prefixes received from IANA/PTI would immediately have AS0 ROA's. Any prefixes returned by or reclaimed from members will also have AS0 ROAs

The process for ROA validity periods and release of ROAs before assignment/allocation by AFRINIC is left for AFRINIC staff to define in internal procedures.

The validity period for these ROAs shall be 10 years (as it currently is for all ROAs) unless a specific validity period is specified by the policy proposal authors.

The process for ROA validity periods and release of ROAs before assignment/allocation by AFRINIC is left for AFRINIC staff to define in internal procedures.

Impact on RPKI On the RPKI side, 3 options have been scoped notably, Use the existing AFRINIC RPKI Tree Additional Production certificate (0/0) for unallocated space only New Trust Anchor with a single Production Certificate AFRINIC recommends option C because it then becomes an opt-in service and does not pollute the current RPKI. Legal Assessment No comments 5.0 Implementation Timeline The policy can be implemented as written within 6 months from the Last Call.

4.0 References An equivalent proposal has already reached consensus in APNIC (https:// www.apnic.net/community/policy/proposals/prop-132) )and has been proposed in RIPE NCC (https:// www.ripe.net/participate/policies/proposals/2019-08). )It is also in preparation for submission to the other RIRs.

4.0 References An equivalent proposal has already reached consensus in APNIC and LACNIC.

AFRINIC will create ROAs with origin AS0 for all the unallocated and unassigned address space (IPv4 and IPv6) for which it is the current administrator.

AFRINIC should add reclaimed resources only at the end of the reclamation process.

AFRINIC recommends option C because it then becomes an opt-in service and does not pollute the current RPKI.

5.0 Implementation Should this proposal reaches consensus and is ratified, the implementation will be done on a new (separate) Trust Anchor so that it becomes an opt-in service and does not impact the current RPKI setup

5.0 Implementation Timeline The policy can be implemented as written within 6 months from the Last Call.

We have been advised that the policy can be fully implemented by Q2-2022.

3.0 AFRINIC Staff Clarification Requests What will be the validity period of these AS0 ROAs? 10 years?

3.0 AFRINIC Staff Clarification Requests None.

Date Submitted 2020-08-03 Author(s) Refer to Proposal Tab Status Archived

Date Submitted 19 April 2021 Author(s) Haitham El-Nakhal, Yazid Akanho Version 3 Obsoletes None Status Ratified