Summary

  • ARIN's transfer page conditions inter-RIR 8.4 transfers on counterpart registries sharing "reciprocal, compatible, needs-based policy", then publishes the outcome as status wording in a table naming APNIC, LACNIC and RIPE NCC.
  • The page reviewed does not name the body that decides compatibility or describe how the list is revised; the closest thing to a dated finding is the ARIN 57 Day 1 transcript of 20 April 2026, which ARIN warns is not an authoritative representation of the meeting.

ARIN does not make anyone guess the rule. Under Inter-RIR Transfers, its transfer page states that "In both cases, an 8.4 transfer can only be conducted between RIRs that share reciprocal, compatible, needs-based policy." ARIN transfer page

Then it publishes the answer. A table carries the status wording "Approved for Transfers" against APNIC, LACNIC and RIPE NCC. In the copy reviewed on 12 November 2026, AFRINIC does not appear in that table. The same table shows the resource scope narrowing by counterpart: APNIC and RIPE NCC listed for IPv4 and ASNs, LACNIC for IPv4 only, and ARIN's inter-RIR transfers excluding IPv6.

A rule in public, an outcome in public, the scope of each arrangement visible. As registry transparency goes, that is better than most.

The trouble begins one click later.

The page states the rule. It does not name the decider.

The reviewed page does not identify the body that determines whether a counterpart registry's policy is compatible, does not name who maintains the approved list, and does not describe a procedure for revising it or for a registry to contest a status.

ARIN does reserve authority over the individual transaction — it can request evidence and reject a transfer that does not comply. That stated authority runs to the case in front of it. It is not the same thing as authority over the list that decides which cases can exist at all.

For a registry the difference is not academic. Whether its members' address space can move into ARIN's region is a commercial fact about its region, priced into every transfer negotiation and every multi-year network plan. A status column is an allocation decision. This one is published without saying whose decision it is.

The determination, on the record, informally

On 20 April 2026, during the Policy Implementation and Experience Report at the ARIN 57 Public Policy and Members Meeting, John Sweeting reported that ARIN had assessed AFRINIC's policy as compatible and intended to permit transfers once AFRINIC completed implementation. The transcript records review by staff and review with some executives. ARIN 57 Day 1 transcript

That is the closest this review came to a compatibility determination with a date and a named speaker attached to it. It is also, by ARIN's own warning on that page, a document that may contain transcription or formatting errors and is not an authoritative representation of the meeting.

Read the two documents together and an institutional sequence becomes visible: an assessment made, an executive review completed, a permission held conditional on implementation elsewhere — and no page that carries the determination as a decision rather than as a status word.

The open question, dated

The two documents sit at different points in time. The April 2026 transcript reports a favourable assessment of AFRINIC's policy, conditioned on implementation. The transfer page as reviewed lists three approved registries. The transcript does not establish that implementation was completed, and this review did not establish that the table was updated afterwards. Both readings stay open.

What is established is narrower and more useful: the only located public account of the determination is the less authoritative of the two documents.

What a counterparty can rely on

A registry planning cross-regional movement is making an assumption about someone else's internal process. It can read the outcome. It can read the policy condition. What it cannot read on the pages reviewed here is the criteria that turn one into the other, the office that applies them, or the route to challenge a status it believes wrong.

For the operator on the other end of a transfer, that gap converts into diligence work: written confirmations, contractual conditions, a buffer for the possibility that a status changes between signature and registry action.

The fix is cheap and unglamorous. State the criteria. Name the deciding role. Date the table. Publish a revision path. Regional registries ask exactly this of the networks they regulate, in policy proposals that run for months and are argued line by line. A table of approved counterparties is a reasonable place to start applying the same standard to themselves.

This review obtained ARIN's transfer page and the ARIN 57 Day 1 transcript. APNIC's own transfer page and the APNIC, LACNIC, RIPE NCC and AFRINIC policy texts were not obtained, so the reciprocity is documented from ARIN's side only. Nothing here is a finding that any registry lacks published criteria.

BTW follows this subject in the directory entry on Inter-RIR Transfer of Internet Number Resources.