Skip to main content

AFRINIC · RIR Watchdog

Anycast resource assignments in the AFRINIC region

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-003
RIR
AFRINIC
Official status
Implemented
Normalized status
Accepted
Introduced
Unknown
Last source update
Oct 12, 2026
Coverage
Partial

Who actually shaped the debate?

19Total participants
19Discussion contributors
UnknownFormal actors
46Discussion messages
13.6Effective participants
50%Top-five discussion share
5People covering 50%
10People covering 80%

BTW Analysis

BTW Analysis

What changed

No policy change can be established from the supplied verified facts because the policy chronology is empty and no proposal text, amendment sequence, procedural milestone, or implementation record is provided.

What the debate was really about

The substance of the debate cannot be reconstructed. No messages, participants, stance timelines, arguments, proposals, interests, or institutional incentives are recorded in the supplied dataset.

Decision vs debate

Neither a discussion outcome nor a formal decision is established. The snapshot records zero messages, zero discussion participants, zero formal actors, zero active days, and no adoption, rejection, withdrawal, consensus, ratification, or implementation record.

Participation concentration

The zero top-message shares, HHI, effective-participant count, and core-participant counts describe an empty observed population, not broadly distributed participation. With zero messages and zero participants, concentration cannot be meaningfully assessed.

Chokepoint analysis

No procedural, institutional, or participant chokepoint can be identified because the supplied chronology and stance timelines are empty and the participation snapshot records no discussion or formal-actor activity.

Uncertainties

  • Zero values may mean that no qualifying activity occurred, that source extraction found no qualifying records, or that relevant activity occurred outside the measured dataset.
  • The concentration statistics cannot distinguish broad equality from absence of participation when both message and participant counts are zero.
  • The policy's evolution and decision outcome are unknown because no chronology, policy text, or decision record is supplied.
  • The current version-bound Doctrine authority does not establish a complete official position for this policy subject.

Policy evolution

Debate timeline

  1. Official version

    DRAFT-02

    Accepted · Implemented

    Source facts ↗
  2. Public discussion

    [rpd] New proposal - "Mandatory requirements for registering assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)

    11 Discussion messages · 9 Entities

    Source facts ↗
  3. Public discussion

    [rpd] RE: rpd Digest, Vol 96, Issue 37

    2 Discussion messages · 2 Entities

    Source facts ↗
  4. Public discussion

    [rpd] AnyCast assignments - Update

    19 Discussion messages · 11 Entities

    Source facts ↗
  5. Public discussion

    [rpd] "Anycast Assignments in the AFRINIC region" last call

    2 Discussion messages · 2 Entities

    Source facts ↗
  6. Public discussion

    [rpd] Anycast allocations and current policy

    2 Discussion messages · 2 Entities

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages5
    First activityOct 3, 2014
    Last activityDec 12, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies10
  2. Discussion messages5
    First activityMay 18, 2014
    Last activityDec 3, 2014
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies15
  3. Discussion messages5
    First activitySep 30, 2014
    Last activityDec 9, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes2
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies3
    Freshness: Stale

    Last research attempt: Oct 2, 2026

    Identity verified: Oct 2, 2026

    AfNOG · Historical
    Lead Instructor, African Network Operators Group
    www.itu.int
    AFRINIC · Historical
    serving as Special Project Manager at AfriNIC since 2006.
    www.itu.int

    Verified public profiles

    Discussion messages
    5
    First activity
    Sep 30, 2014
    Last activity
    Dec 9, 2014
    First explicit stance
    Support with changes
    Latest explicit stance
    Support with changes
    Stance changes
    2
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    3

    First explicit stance: Support with changes → Latest explicit stance: Support with changes · Stance changes: 2

    Viewpoint consistency: Insufficient evidence to assess consistency

    The four December 2014 anycast messages consistently advocate explicit best-practice references with a reasoned exception for future changes. The newly recovered July 2006 message asks about a copied regional eligibility clause in a different IPv6 PI proposal. It adds no second substantive position on that proposal and does not establish a contradiction with the later use of external best practices.

    Anycast resource assignments in the AFRINIC region

    Assessment: Consistent · The author first conditions multiple-subnet use on a BCP126 reference and proposes BCP169 for ASNs, then defends the clarity and abuse-prevention rationale and supplies replacement clauses. The clauses develop the same preference rather than withdrawing support for the mechanism.

    Conditions: This is support for the specified conditions, not an unconditional endorsement of every policy provision. · The offered wording does not establish adoption or consensus.

    As discussed at the meeting, using multiple subnets is ok as far as reference to BCP126 is in there.

    So references to best practices is good. In this case one for the v4/v6 and one for ASN

    These resources must be used for the sole purposes of providing anycast services or GRX (GPRS Roaming Exchanges) as recommended in BCP126 and BCP169 respectively.

    Anycast resource assignments in the AFRINIC region

    Assessment: Consistent · The later preference for following replacement BCPs without a new PDP extends the earlier instruction that implementers should adjust as best practices change. The author explicitly preserves an exception when there is reason to do otherwise, so this is not an unconditional transfer of all policy decisions to future BCP authors.

    Conditions: The RFC2026 passage is attributed supporting material, not a separate personal vote. · The messages do not specify who would decide that an exception is justified.

    Best practices changes over time and implementer shall adjust

    The policy should follow new BCPs( which update, replace old ones) without going through PDP unless we have reasons to do otherwise.

    Either we add the requirements in the policy or we refer to the BCP. I support the last option.

    Provider-Independent (PI) IPv6 Assignments for End-User-Organizations

    Assessment: Insufficient evidence to assess consistency · The author asks why RIPE NCC IPv4 qualification criteria appear in an AFRINIC IPv6 PI proposal. This identifies a concrete regional-applicability question; it is not a general rejection of provider-independent assignments or of every external reference. One question supplies no sequence of personal positions to compare.

    Conditions: The quoted eligibility clause belongs to the draft under discussion, not to a rule the author independently endorses. · The proposed regional-name correction in the reply is another participant's explanation.

    Can someone (jordi or others) explains to me what why should RIPE NCC actual IPV4 policy applied for AfriNIC region in the IPv6 IP assignement ?

    Provider-Independent (PI) IPv6 Assignments for End-User-Organizations · Anycast resource assignments in the AFRINIC region

    Assessment: Insufficient evidence to assess consistency · Questioning an apparently miscopied region-specific eligibility rule in 2006 and supporting explicit technical best-practice references for anycast in 2014 concern different kinds of reference. The supplied messages show no necessary contradiction, but the long gap and absence of a comparable PI position prevent a broad claim of consistent policy preferences across the two proposals.

    Conditions: A concern about which registry's rules apply cannot be generalized into opposition to all externally maintained standards. · Only the named messages and proposals are covered.

    what why should RIPE NCC actual IPV4 policy applied for AfriNIC region in the IPv6 IP assignement ?

    So references to best practices is good. In this case one for the v4/v6 and one for ASN

    unless we have reasons to do otherwise.

    1. Sep 30, 2014 · Unknown

      [rpd] New proposal - "Mandatory requirements for registering assignments and sub-allocations" (AFPUB-2014-GEN-003-DRAFT-01)

      Validated evidence is unavailable.

      Source facts ↗
    2. Dec 7, 2014 · Support with changes

      [rpd] AnyCast assignments - Update

      As discussed at the meeting, using multiple subnets is ok as far as reference to BCP126 is in there. … To add Multiple ASNs on this, i suggest, reference to BCP 169

      Source facts ↗
    3. Dec 8, 2014 · Support with changes

      [rpd] AnyCast assignments - Update

      So references to best practices is good. In this case one for the v4/v6 and one for ASN … Ressources must be used on need basis and with trust. Best practices changes over time and implementer shall adjust

      Source facts ↗
    4. Dec 8, 2014 · Propose alternative

      [rpd] AnyCast assignments - Update

      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 respectively. … These resources must be used for the sole purposes of providing anycast services or GRX (GPRS Roaming Exchanges) as recommended in BCP126 and BCP169 respectively.

      Source facts ↗
    5. Dec 9, 2014 · Support with changes

      [rpd] AnyCast assignments - Update

      The policy should follow new BCPs( which update, replace old ones) without going through PDP unless we have reasons to do otherwise. … Either we add the requirements in the policy or we refer to the BCP. I support the last option.

      Source facts ↗

    Total policy messages: 11

  4. Discussion messages4
    First activitySep 26, 2014
    Last activityFeb 8, 2015
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies13
  5. Adam Nelson · Identity unresolved
    Discussion messages4
    First activityNov 7, 2014
    Last activityFeb 8, 2015
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies4
  6. Jean Robert Hountomey · Identity unresolved
    Discussion messages3
    First activitySep 27, 2014
    Last activityOct 17, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  7. Discussion messages3
    First activitySep 26, 2014
    Last activityDec 7, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport
    Stance changes1
    Viewpoint consistencyConsistent
    Other policies8
  8. Frank Habicht · Identity unresolved
    Discussion messages3
    First activitySep 27, 2014
    Last activityDec 12, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies4
  9. Discussion messages3
    First activitySep 27, 2014
    Last activityFeb 12, 2015
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies6
  10. Badru Ntege · Identity unresolved
    Discussion messages2
    First activitySep 19, 2014
    Last activitySep 19, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  11. Discussion messages1
    First activityNov 28, 2014
    Last activityNov 28, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies10
  12. Dr Paulos Nyirenda · Identity unresolved
    Discussion messages1
    First activitySep 26, 2014
    Last activitySep 26, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  13. Unknown · Identity unresolved
    Discussion messages1
    First activityDec 12, 2014
    Last activityDec 12, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  14. David Peall · Identity unresolved
    Discussion messages1
    First activityDec 3, 2014
    Last activityDec 3, 2014
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  15. Fiona Asonga · Identity unresolved
    Discussion messages1
    First activityOct 3, 2014
    Last activityOct 3, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3
  16. Sunday Folayan · Identity unresolved
    Discussion messages1
    First activityJun 17, 2014
    Last activityJun 17, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies6
  17. Akeem MUFUTAU · Identity unresolved
    Discussion messages1
    First activitySep 27, 2014
    Last activitySep 27, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  18. Mark Tinka · Identity unresolved
    Discussion messages1
    First activityNov 4, 2014
    Last activityNov 4, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  19. Ebo Thompson · Identity unresolved
    Discussion messages1
    First activitySep 27, 2014
    Last activitySep 27, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0

Sources and coverage

Official policy sources

Public discussion archives

  • afrinic-rpd
    Earliest captured
    Aug 4, 2004
    Latest captured
    Aug 25, 2026
    Last refresh
    Oct 13, 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 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,598
    Known gaps
    0
  • afrinic-afripv6-discuss
    Earliest captured
    Aug 17, 2015
    Latest captured
    Sep 18, 2026
    Last refresh
    Oct 13, 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 13, 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 13, 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 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    941
    Known gaps
    0
  • afrinic-dnssec-ops
    Earliest captured
    Aug 18, 2015
    Latest captured
    Dec 1, 2016
    Last refresh
    Oct 13, 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 13, 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 13, 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 13, 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 13, 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 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    154
    Known gaps
    0

Coverage

Partial
Earliest captured: Aug 4, 2004
Latest captured: Oct 13, 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.