AFRINIC Number Resources Transfer Policy (Draft-2)

AFRINIC Staff Assessment

Date of Assessment	Relevant to Proposal
Sept 2020	AFPUB-2019-GEN-002-DRAFT02

1.0 Staff Understanding of the Proposal

• ASN's shall be transferrable both inter and intra-region

• Legacy IPv4 space in the AFRINIC region can be transferred out. Transferred IPv4 space from other regions into AFRINIC can also be transferred out.

• Number resources are non-transferable and are not assignable to any other organisation unless AFRINIC has expressly and in writing approved a request for transfer. AFRINIC's approval is usually documented electronically in tickets.

• IPv4 addresses and ASNs can be transferred only if the transfer requests are evaluated against and in accordance with this policy.

• AFRINIC does not recognise transfers outside of approved transfer policies and requires organisations holding such resources to return them to the appropriate registries. Meaning that any transfers that happened outside any approved AFRINIC policies are not valid and the recipient organisations will be required to return the space to AFRINIC or the RIRs

• AFRINIC recognizes the following types of transfers - bother inter and intra-RIR:

• merger, acquisition or takeover,

• between AFRINIC members,

• between an AFRINIC member and an organization in another region,

• between a Legacy resource holder and an AFRINIC member,

• between a Legacy resource holder and an organization in another region.

• The policy requires some categorisation"marking" that will, in turn, require AFRINIC to tag currently delegated resources and available resources.

• The resource will be covered by AFRINIC policies after transfer into the region. Legacy resources will no longer be legacy

The transfer conditions have been summarised in the table below:-

Policy Condition	Source	Recipient	Resource Type	Final Tag	Transfer Type	Conditions
			Allowed	Denied
3.3.1	AFRINIC Member	AFRINIC Member	Regional, Global or Legacy	Reserved	* Legacy -> Global * Regional -> no change * Global -> no change	Intra-RIR
3.3.2	Legacy	AFRINIC Member	Legacy	Reserved, Regional and Global	Legacy -> Global	Inter-RIR & Intra-RIR
3.3.3	Legacy	RIR	Legacy	Reserved, Regional and Global	N/A	Inter-RIR
3.3.4	AFRINIC Member	RIR	Global	Reserved, Regional	N/A	Inter-RIR
3.3.5	RIR	AFRINIC Member	Any IPv4/ASN	N/A	Global	Inter-RIR

3.4 Conditions on resources to be transferred

• The size of the IPv4 address prefix should be a minimum of /24.

• The resource must qualify for the type of transfer requested.

• The resource will be covered by AFRINIC policies after transfer into the region.

1.2 Staff Need more clarification from Authors

None

2.0 Staff Comments On Areas of Impact

If the proposal reaches consensus:

2.1 Impact on Systems

1. The Transfer tool on MyAFRINIC will require further adjustments to accommodate inter-RIR transfers

2. Reverse DNS impacts to be considered (for majority /8s)

3. RPKI ROAs

4. Transfer logs

5. RT (AFRINIC Ticketing System)

6. Resource tagging to be implemented on MyAFRINIC

2.2 Impact on Processes and procedure

1. Processes and procedures will require a review.

2. Coordination with the RIRs who have compatible inter-RIR transfer policies will also be required

2.3 Impact on Operations

1. Resource Transfer evaluation are resource-intensive and MS department would require additional staffing needs to facilitate officiate and timely evaluations

2. Resources will also be required in the software engineering team to implement the transfer on the AFRINIC systems.