Skip to main content

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?

14Total participants
14Discussion contributors
UnknownFormal actors
29Discussion messages
8.2Effective participants
65.5%Top-five discussion share
3People covering 50%
9People covering 80%

Policy evolution

DRAFT-03
Unknown
Source facts ↗

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.

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.

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.

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.

DRAFT-04
Withdrawn · Withdrawn
Unknown
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.

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.

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.

Debate timeline

  1. Official version

    DRAFT-03

    Source facts ↗
  2. Official version

    DRAFT-04

    Withdrawn · Withdrawn

    Source facts ↗
  3. Introduced

    Introduced

    Source facts ↗
  4. Official version

    DRAFT-01

    Source facts ↗
  5. Public discussion

    [rpd] Re: Staff Assessment for AFPUB-2014-GEN-002-DRAFT-01

    3 Discussion messages · 1 Entities

    Source facts 1 ↗Source facts 2 ↗
  6. Public discussion

    [rpd] AfriNIC policy AFPUB-2014-GEN-002-DRAFT-01 reject

    13 Discussion messages · 9 Entities

    Source facts ↗
  7. Public discussion

    [rpd] Re: rpd Digest, Vol 97, Issue 17

    2 Discussion messages · 2 Entities

    Source facts ↗
  8. Public discussion

    RE: [rpd] Afrinic policy proposal—Afrinic Service guild lines

    3 Discussion messages · 2 Entities

    Source facts ↗
  9. Official decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages7
    First activityOct 22, 2014
    Last activityJan 13, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies13
  2. Discussion messages5
    First activitySep 23, 2014
    Last activityOct 27, 2014
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies15
  3. Discussion messages3
    First activityOct 2, 2014
    Last activityMay 27, 2015
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies6
  4. H.Lu · Identity unresolved
    Discussion messages2
    First activityOct 22, 2014
    Last activityOct 26, 2014
    First explicit stanceOppose
    Latest explicit stanceSupport
    Stance changes1
    Viewpoint consistencyConsistent
    Other policies1
  5. Discussion messages2
    First activityOct 22, 2014
    Last activityOct 22, 2014
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies2
  6. Keshwarsingh Nadan · Identity unresolved
    Discussion messages2
    First activityOct 27, 2014
    Last activityOct 27, 2014
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies0
  7. gehoumi · Identity unresolved
    Discussion messages1
    First activityOct 24, 2014
    Last activityOct 24, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  8. Vladimir Kangin · Identity unresolved
    Discussion messages1
    First activityOct 19, 2014
    Last activityOct 19, 2014
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  9. Kofi ANSA AKUFO · Identity unresolved
    Discussion messages1
    First activityOct 27, 2014
    Last activityOct 27, 2014
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies3
  10. Victor · Identity unresolved
    Discussion messages1
    First activityOct 22, 2014
    Last activityOct 22, 2014
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  11. Borg · Identity unresolved
    Discussion messages1
    First activityOct 22, 2014
    Last activityOct 22, 2014
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies2
  12. Discussion messages1
    First activityOct 22, 2014
    Last activityOct 22, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies10
    Freshness: 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.net
    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.

    AFPUB-2012-V4-001-DRAFT-01

    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?

    1. 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 ↗

    Total policy messages: 36

  13. Mark Tinka · Identity unresolved
    Discussion messages1
    First activityOct 25, 2014
    Last activityOct 25, 2014
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies2
  14. Adam Nelson · Identity unresolved
    Discussion messages1
    First activityNov 7, 2014
    Last activityNov 7, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other 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

Freshness: Stale · Last refresh:

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.