IPv4 Resource Transfers within the AFRINIC region (AFPUB-2016-v4-003-DRAFT-01)

Recipient qualification standard · Draft 2 replaces the broadly worded recipient membership/other-requirements clause with an explicit requirement to qualify for the transferred amount under the same standards as a direct AFRINIC allocation or assignment at the time of request. Membership remains required by the separate source-and-recipient clause.

Staff assessment of the activation trigger · The draft-2 snapshot adds staff concerns that tying activation to phase 2 of the soft-landing policy could become inapplicable if that policy changed or ceased to have a phase 2. These are assessment comments; draft 2 itself retains the phase-2 trigger.

Staff assessment of prior transfers · New staff commentary identifies a possible distinction in the 12-month source restriction: its wording could permit a recent inbound inter-RIR recipient to transfer within AFRINIC while preventing a recent intra-AFRINIC recipient from doing so. The proposed restriction itself is retained; the commentary is not a newly enacted exception.

Staff request for a dispute definition · The draft-2 snapshot adds a request to define disputes and clarify how disputes involving the receiving organisation would affect a transfer. The underlying requirement that the source hold undisputed resources is retained. A staff request for clarification is not treated as a completed policy definition.

Staff assessment of the need horizon · Added staff comments identify a mismatch between the draft's 12-month recipient need horizon and the cited soft-landing allocation period of eight months, suggesting alignment or deletion because current-policy qualification already applies. Draft 2 still contains the 12-month clause; the comments alone do not amend it.

Recorded page status · The retained draft-1 page is labelled Under Discussion and the draft-2 page Implemented. This is a difference between page metadata captured in the archive; it does not establish when implementation occurred or prove that draft 2 was implemented on its submission date.

Trigger and CPM integration · Draft 3 frames the proposal as new CPM article 5.7 and applies it to justified IPv4 needs AFRINIC cannot satisfy. It removes the dependency on reaching phase 2 of the soft-landing policy, expressly confirmed in its revision history.

Transfer-source eligibility · Draft 3 allows resources to come from either an existing AFRINIC member's account or a legacy holder in AFRINIC's service region. This expands the prior rule that both parties must be AFRINIC members. The recipient remains subject to a separate AFRINIC membership and RSA requirement.

Legacy status after transfer · Draft 3 explicitly states that transferred IPv4 legacy resources lose legacy status. The previous recipient conditions required current-policy compliance and an RSA but contained no corresponding legacy-status provision.

Recipient need horizon · Draft 3 removes the standalone requirement to demonstrate up to a 12-month supply and explains that justification follows policies in force. It also removes the separate direct-allocation-equivalence sentence as already covered by the retained need-justification clause. These edits do not eliminate AFRINIC's approval of recipient need.

Recorded page status · The draft-2 snapshot is labelled Implemented, while the draft-3 snapshot is labelled Last Call. These captured labels are retained as a metadata discrepancy; the comparison does not infer a reversal of implementation or overwrite the proposal's authoritative current status.