AFRINIC · RIR Watchdog
Out-Of-Region Use of AFRINIC Internet Number Resources
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- afpub-2014-gen-002
- RIR
- AFRINIC
- Official status
- Withdrawn
- Normalized status
- Withdrawn
- Introduced
- Jul 3, 2014
- Last source update
- Sep 11, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
ceiling_calculation · The ceiling remains 40% of resources in use. The formula changes from x-y, with x defined as allocation/assignment size, to y explicitly defined as used space. The revision history attributes the arithmetic clarification to draft-02 and the allocation-only terminology to draft-03; this comparison does not treat Douglas's nearby suggestion of 30% as adopted draft text.
Source facts −
Total space in use shall be calculated as follows: if x be the > allocation/assignment size; and x-y the amount of space in use at time z, > then 40% of (x-y) shall be the ceiling).Source facts ↗
Source facts +
Total space in use shall be calculated as follows: if x be the allocation size; and y the amount of space in use at time z, then 40% of y shall be the ceiling).Source facts ↗
resource_scope · The operative scope narrows from allocations and assignments to allocations. The draft-03 history explicitly says assignments were removed. The summary still contains allocated/assigned wording, so the source retains an editorial inconsistency; this is a proposal comparison, not proof of adoption or current enforceability.
Source facts −
f. This policy shall apply to past, present and future > allocations/assignments made by AFRINIC.Source facts ↗
Source facts +
This policy shall apply to present and future allocations made by AFRINIC.Source facts ↗
retrospective_application · The express reference to past allocations is removed while present and future allocations remain. The draft-03 changelog identifies retrospective application as the reason; it does not establish an exemption for every currently used older allocation.
Source facts −
This policy shall apply to past, present and future > allocations/assignments made by AFRINIC.Source facts ↗
Source facts +
Remove “past” from 3.f. This is to solve the issue of applying the policy retrospectivelySource facts ↗
stated_beneficiary · The problem statement shifts its reference from AFRINIC's best interests to those of the AFRINIC community. This changes the stated rationale, without changing the 40% ceiling, staff compliance discretion or the cited soft-landing termination condition.
Source facts −
resources for sale or use outside the region - a practice that is not in > AFRINIC's best interests.Source facts ↗
Source facts +
resources for sale or use outside the region -- a practice that is not in the best interests of the AFRINIC community.Source facts ↗
Permission and threshold for out-of-region use · Draft 4 retains the 40% ceiling and the requirement that out-of-region use be preceded by in-region use, while expressing the permission as applying after ratification and defining the ceiling against the amount in use. The comparison reports the proposal wording without treating it as an enacted rule.
Source facts −
This policy allows up to 40% of Internet number resources in use by a member to be outside the region.Source facts ↗
Source facts +
Upon ratification of this policy, out-of-region use of AFRINIC's number resources shall be permitted as long it is preceded by use within the region. Notwithstanding 3a, the number resources used outside the region at any time shall not exceed 40% of theSource facts ↗
Measurement evidence and staff assessment · Draft 3 leaves assessment to AFRINIC staff's discretion using whatever means are available. Draft 4 adds Whois and global routing table evidence, allows other consistency criteria, and directs staff to use that defined basis for due diligence. This is a proposal comparison, not proof of implementation.
Source facts −
AFRINIC staff shall at their discretion, and using whatever means are available, assess compliance with 3.a/b. This policy shall forthwith be part of the acceptableSource facts ↗
Source facts +
Regional Internet Number resources usage will be determined using Whois database information, global routing table announcements, and for purposes of consistency, other criteria prescribed by AFRINIC. AFRINIC staff shall by use of 3c, carryout due diligence to assess compliance with 3a and 3b. This policy shall forthwith be part of the acceptable use policy for Internet numbers and aSource facts ↗
Temporal scope of allocations · Draft 3 says the policy applies to present and future allocations. Draft 4 says it applies to past, present and future allocations. The comparison records the broader proposed temporal wording and does not infer retroactive enforcement or adoption.
Source facts −
This policy shall apply to present and future allocations made by AFRINIC.Source facts ↗
Source facts +
This policy shall apply to past, present and future allocations made by AFRINIC.Source facts ↗
Debate timeline
Public discussion
[rpd] Re: Staff Assessment for AFPUB-2014-GEN-002-DRAFT-01
3 Discussion messages · 1 Entities
Source facts 1 ↗Source facts 2 ↗Public discussion
[rpd] AfriNIC policy AFPUB-2014-GEN-002-DRAFT-01 reject
13 Discussion messages · 9 Entities
Source facts ↗Public discussion
[rpd] Re: rpd Digest, Vol 97, Issue 17
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
RE: [rpd] Afrinic policy proposal—Afrinic Service guild lines
3 Discussion messages · 2 Entities
Source facts ↗
Entities
- Discussion messages7First activityOct 22, 2014Last activityJan 13, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies13
- Discussion messages5First activitySep 23, 2014Last activityOct 27, 2014First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies15
- Discussion messages3First activityOct 2, 2014Last activityMay 27, 2015First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies6
- H.Lu · Identity unresolvedDiscussion messages2First activityOct 22, 2014Last activityOct 26, 2014First explicit stanceOpposeLatest explicit stanceSupportStance changes1Viewpoint consistencyConsistentOther policies1
- Discussion messages2First activityOct 22, 2014Last activityOct 22, 2014First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies2
- Keshwarsingh Nadan · Identity unresolvedDiscussion messages2First activityOct 27, 2014Last activityOct 27, 2014First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyConsistentOther policies0
- gehoumi · Identity unresolvedDiscussion messages1First activityOct 24, 2014Last activityOct 24, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Vladimir Kangin · Identity unresolvedDiscussion messages1First activityOct 19, 2014Last activityOct 19, 2014First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
- Kofi ANSA AKUFO · Identity unresolvedDiscussion messages1First activityOct 27, 2014Last activityOct 27, 2014First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyConsistentOther policies3
- Victor · Identity unresolvedDiscussion messages1First activityOct 22, 2014Last activityOct 22, 2014First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Borg · Identity unresolvedDiscussion messages1First activityOct 22, 2014Last activityOct 22, 2014First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies2
- Discussion messages1First activityOct 22, 2014Last activityOct 22, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyConsistentOther policies10Freshness: Stale
Last research attempt: Oct 4, 2026
Identity verified: Oct 4, 2026
POSIX · Historical Author(s): Jordi Palet Martinez jordi.palet[at]theipv6company.com The IPv6 Company Frank Habicht geier[at]geier.ne.tz Tanzania ISP Association Mark Elkins mje[at]posix.co.za POSIX
www.afrinic.netVerified public profiles
- Discussion messages
- 1
- First activity
- Oct 22, 2014
- Last activity
- Oct 22, 2014
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Consistent
- Other policies
- 10
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Consistent
The October and December 2014 anycast contributions follow a coherent line: extend access to IPv6 and AS Numbers, then clarify the technical uses and references. The separate question about foreign companies operating in Africa does not establish a vote on out-of-region limits or a reversal of that position.
Assessment: Insufficient evidence to assess consistency · The submitted text advocates extending the existing anycast policy to IPv6 and AS Numbers. This one submission establishes that proposal, but cannot by itself establish persistence or reversal over time.
Conditions: Authorship and proposed text are distinguished from adoption or community consensus. · The stated geographic rationale concerns legitimate members supporting their networks; it is not unlimited permission for every applicant.
The proposal modifies AFPUB-2012-V4-001 to include the option to request IPv6 space and AS Numbers for anycast purposes from AFRINIC and for AFRINIC to issue these resources to the requestors.
Anycast resource assignments in the AFRINIC region
Assessment: Consistent · The proposed addition of BCP169 and subsequent support for Alan's successor-reference wording are compatible steps toward clearer technical references. The later response endorses an update rather than withdrawing the earlier anycast-use objective.
Conditions: The exact text of Alan's intervening suggestion is not reproduced in these two messages. · The expectation that the change satisfies everyone is the author's expectation, not a formal consensus decision.
These resources must be used for the sole purposes of providing anycast services or GRX (GPRS Roaming Exchanges) as recommended in BCP126 and BCP169.
Thanks Alan. I like that. Ernest - can you please update the current online wording to reflect what Alan says.
Out-Of-Region Use of AFRINIC Internet Number Resources
Assessment: Insufficient evidence to assess consistency · The question challenges a possible exclusion of foreign companies that operate in Africa. It does not supply an explicit position on the full out-of-region proposal or a second position to compare.
Conditions: A question about company origin must not be converted into support for unrestricted use outside Africa.
If a non African company moves into Africa - why would the policy not allow them IPv4 address space?
AFPUB-2012-V4-001-DRAFT-01 · Anycast resource assignments in the AFRINIC region
Assessment: Consistent · The extension submitted in October and the December reference edits share the same purpose: make IPv6 and AS Numbers available for specified anycast or GRX uses. Refining the technical references does not contradict that purpose.
Conditions: This comparison concerns the author's submitted and proposed wording, not whether either proposal was adopted.
This proposal allows an organization to receive an IPv4/IPv6 allocation or assignment and an AS Number purely for anycast or GPRS Roaming Exchange (GRX) usage.
This proposal allows an organization to receive an IPv4/IPv6 allocation or assignment and/or an AS Number purely for anycast or GPRS Roaming Exchange (GRX) usage in line with the provisions of BCP126 and BCP169.
AFPUB-2012-V4-001-DRAFT-01 · Out-Of-Region Use of AFRINIC Internet Number Resources
Assessment: Insufficient evidence to assess consistency · The anycast text discusses regional members' operations regardless of physical location, while the out-of-region question asks about foreign companies operating inside Africa. Those are different eligibility dimensions; these messages do not establish contradictory rules or a complete shared position.
Conditions: Distinguish a company's origin, membership eligibility and the physical use of its resources.
number resources allocated/assigned by AFRINIC are used by legitimate members from the service region to support their network operations, regardless of physical location.
If a non African company moves into Africa - why would the policy not allow them IPv4 address space?
- Oct 22, 2014 · Question or clarify
[rpd] AfriNIC policy AFPUB-2014-GEN-002-DRAFT-01 reject
If a non African company moves into Africa - why would the policy not allow them IPv4 address space?
Source facts ↗
Per-policy stance timelines:AFPUB-2008-GEN-001 · Unknown · No explicit position statedAFPUB-2010-V4-005 · Unknown · No explicit position statedAFPUB-2012-GEN-001 · Unknown · No explicit position statedAFPUB-2012-V4-001 · Propose alternative · Insufficient evidence to assess consistencyAFPUB-2013-GEN-001 · Unknown · No explicit position statedAFPUB-2013-V4-001 · Unknown · No explicit position statedafpub-2014-gen-002 · Unknown · Insufficient evidence to assess consistencyAFPUB-2014-GEN-003 · Support with changes · Consistentafpub-2014-gen-004 · Unknown · No explicit position statedAFPUB-2026-GEN-002-DRAFT02 · Unknown · No explicit position statedAFPUB-2026-IPv4-001-DRAFT02 · Unknown · No explicit position statedTotal policy messages: 36
- Mark Tinka · Identity unresolvedDiscussion messages1First activityOct 25, 2014Last activityOct 25, 2014First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies2
- Adam Nelson · Identity unresolvedDiscussion messages1First activityNov 7, 2014Last activityNov 7, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
Sources and coverage
Official policy sources
Public discussion archives
- afrinic-rpd
- Earliest captured
- Aug 4, 2004
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 13,116
- Known gaps
- 0
- www.afrinic.net
- afrinic-africann
- Earliest captured
- Aug 3, 2026
- Latest captured
- Oct 2, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,603
- Known gaps
- 0
- afrinic-afripv6-discuss
- Earliest captured
- Aug 17, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,538
- Known gaps
- 0
- afrinic-announce
- Earliest captured
- Aug 18, 2015
- Latest captured
- Sep 18, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,497
- Known gaps
- 0
- afrinic-community-discuss
- Earliest captured
- Sep 11, 2015
- Latest captured
- Dec 29, 2019
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,127
- Known gaps
- 0
- afrinic-dbwg
- Earliest captured
- Aug 4, 2026
- Latest captured
- Oct 6, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 946
- Known gaps
- 0
- afrinic-dnssec-ops
- Earliest captured
- Aug 18, 2015
- Latest captured
- Dec 1, 2016
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 307
- Known gaps
- 0
- afrinic-icp2-review
- Earliest captured
- Apr 10, 2025
- Latest captured
- Nov 10, 2025
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-measurement-wg
- Earliest captured
- Feb 1, 2018
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 138
- Known gaps
- 0
- afrinic-mira
- Earliest captured
- Nov 17, 2020
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-ois-wg
- Earliest captured
- Sep 9, 2021
- Latest captured
- Nov 22, 2024
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- afrinic-rpki-discuss
- Earliest captured
- Jan 15, 2016
- Latest captured
- Apr 23, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 154
- Known gaps
- 0
Coverage
Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 14, 2026
Freshness
Known gaps
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpd: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.afrinic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-africann: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-afripv6-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-announce: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-community-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dbwg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-dnssec-ops: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-measurement-wg: Source coverage is incomplete. · The source boundary has not yet been reached.
- afrinic-rpki-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
