Skip to main content

AFRINIC · RIR Watchdog

AFPUB-2013-V4-002-DRAFT-01

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-2013-V4-002
RIR
AFRINIC
Official status
Withdrawn
Normalized status
Withdrawn
Introduced
Unknown
Last source update
Oct 1, 2026
Coverage
Partial

Who actually shaped the debate?

8Total participants
8Discussion contributors
UnknownFormal actors
12Discussion messages
7.2Effective participants
75%Top-five discussion share
3People covering 50%
6People covering 80%

BTW Analysis

BTW Analysis

What changed

No policy evolution or substantive change can be established because the verified policy chronology is empty and no initial, revised, or final policy text is supplied.

What the debate was really about

The subject of the debate cannot be determined from the verified facts. There are no recorded messages, participant stance timelines, or unresolved or minority arguments from which to identify the competing policy concerns.

Decision vs debate

Neither a discussion process nor a decision outcome is established. The dataset records zero messages, zero active days, zero discussion participants, and zero formal actors, while no verified decision record indicates whether the proposal was adopted, rejected, withdrawn, superseded, or left unresolved.

Participation concentration

The zero top-participant shares, zero HHI, zero effective-participant count, and zero core-participant counts describe an empty observed participation dataset, not broad, equal, decentralized, or unconcentrated participation. With zero messages and zero participants, there is no substantive influence distribution to assess.

Chokepoint analysis

No institutional or participant chokepoint can be identified from the supplied facts. The principal analytical chokepoint is the absence of a verified chronology, discussion records, stance timelines, formal-actor activity, and a decision record, which prevents reconstruction of policy progression, influence, or causal links between discussion and outcome.

Uncertainties

  • It is uncertain whether no public discussion occurred or whether the verified dataset captured none.
  • The temporal coverage and inclusion criteria of the participation extraction are not supplied.
  • The policy's substantive starting point, revisions, final language, and procedural milestones are unknown.
  • No verified outcome, decision-maker, rationale, date, or implementation status is supplied.
  • No causal relationship between debate, policy changes, and any decision can be evaluated.
  • The Doctrine package provides only a partial official position for this subject and cannot substitute for the missing policy-specific facts.

Policy evolution

Debate timeline

  1. Official version

    DRAFT-01

    Withdrawn · Withdrawn

    Source facts ↗
  2. Public discussion

    [AFRINIC-rpd] PDP discussions

    8 Discussion messages · 6 Entities

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages2
    First activityJun 20, 2013
    Last activityJun 21, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies10
  2. Discussion messages2
    First activityJun 3, 2013
    Last activityJun 8, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies6
  3. Discussion messages2
    First activityJun 21, 2013
    Last activityJun 26, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies13
  4. Discussion messages2
    First activityJun 21, 2013
    Last activityJun 21, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies16
  5. JP · Identity unresolved
    Discussion messages1
    First activityJun 24, 2013
    Last activityJun 24, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies6
  6. Bope Domilongo Christian · Identity unresolved
    Discussion messages1
    First activityJun 21, 2013
    Last activityJun 21, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies7
  7. Discussion messages1
    First activityJun 20, 2013
    Last activityJun 20, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies9
    Freshness: Stale

    Last research attempt: Sep 25, 2026

    Identity verified: Sep 25, 2026

    AFRINIC · Historical
    Chairs: Alan Barrett <apb at cequrux.com> S. Moonesamy <sm+afrinic at elandsys.com>
    lists.afrinic.net

    Verified public profiles

    Discussion messages
    1
    First activity
    Jun 20, 2013
    Last activity
    Jun 20, 2013
    First explicit stance
    Unknown
    Latest explicit stance
    Unknown
    Stance changes
    0
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    9

    First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0

    Viewpoint consistency: Insufficient evidence to assess consistency

    The May 2012 privacy draft and subsequent request for AFRINIC input show no substantive reversal. The August 2016 Soft Landing-bis contribution asks for analysis rather than endorsing or rejecting its limits. The two topics do not provide enough comparable positions for a broader consistency conclusion.

    Regional Internet Registry Privacy | AFPUB-2012-GEN-002-DRAFT-02

    Assessment: Consistent · Presenting a privacy draft and subsequently seeking AFRINIC's input are compatible actions. The follow-up reports an unanswered request; it does not withdraw the draft or replace its retention period.

    Conditions: The supplied May draft specifies three months; it must not be confused with a later six-month text. · The report of no reply is the author's observation at that time, not a verified general finding about AFRINIC.

    The retention period for Personal Identifiable Information is three months.

    I asked AfriNIC for input about the above ( https://lists.afrinic.net/pipermail/rpd/2012/002136.html ). There has not been any reply.

    IPv4 Soft Landing – bis (Alain Aina)

    Assessment: Insufficient evidence to assess consistency · The author waits for analysis of the proposal and distinguishes allocation justification from users' connectivity. Personal addressing preferences and comments on past strategy do not establish a vote on Soft Landing-bis or a change in such a vote.

    Conditions: The recollection of chairing an earlier soft-landing discussion is historical context, not a new position on that earlier policy.

    I was waiting to read the analysis about the proposal to find the answers to the above questions.

    Regional Internet Registry Privacy | AFPUB-2012-GEN-002-DRAFT-02 · IPv4 Soft Landing – bis (Alain Aina)

    Assessment: Insufficient evidence to assess consistency · Limiting the collection and retention of personal information and preferring an ISP-assigned public address concern different mechanisms. These messages contain no express conflict, but do not support a strong cross-policy consistency judgment.

    Conditions: A preference for public addressing does not itself endorse publishing personal information. · No complete substantive position on the Soft Landing-bis limits is stated.

    The principle of data minimization has been adopted to limit the collection and/or transfer of Personal Identifiable Information (PII) to what is directly relevant and necessary for specified, explicit and legitimate purposes.

    My preference is to have an IPv4 address assigned by my ISP.

    1. Jun 20, 2013 · Unknown

      [AFRINIC-rpd] Withdrawal of AFPUB-2013-V4-002-draft-01 proposal

      Validated evidence is unavailable.

      Source facts ↗

    Total policy messages: 103

  8. Discussion messages1
    First activityJun 24, 2013
    Last activityJun 24, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies8

Sources and coverage

Official policy sources

Public discussion archives

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

Coverage

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