Skip to main content

AFRINIC · RIR Watchdog

Redefine “core DNS service provider” | AFPUB-2012-V4-002-DRAFT-02

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-2012-V4-002
RIR
AFRINIC
Official status
Withdrawn by Author
Normalized status
Withdrawn
Introduced
Sep 18, 2012
Last source update
Oct 1, 2026
Coverage
Partial

Who actually shaped the debate?

2Total participants
1Discussion contributors
1Formal actors
1Discussion messages
1Effective participants
100%Top-five discussion share
1People covering 50%
1People covering 80%

BTW Analysis

BTW Analysis

What changed

Frank Habicht's retained DRAFT-02 proposed expanding the IPv4 provider-independent eligibility definition from ICANN-sanctioned root operators to organisations in the AFRINIC service region providing DNS for any TLD. It allowed up to two assignments for a TLD service and retained support for root-server infrastructure. This was proposed eligibility, not a demonstrated allocation or an adopted entitlement.

What the debate was really about

The recovered November 27 comment challenged treating every TLD as critical and suggested separating that question from provider-independent address space. The disagreement concerns which operational function justifies privileged access to addresses; it is not a recorded rejection of all TLD allocations.

Arguments that prevailed

  • No argument can be identified as prevailing from the available discussion. The recorded procedural outcome was withdrawal.

Arguments that did not prevail

  • The proposed expansion did not advance through this proposal. The record does not show whether the suggestion to separate the issues was accepted elsewhere.

Decision vs debate

AFRINIC's retained history reports no consensus at the November 28, 2012 meeting and withdrawal by the author on November 29. The comment preceded both. The record does not establish that this commenter caused either outcome, and withdrawal is not adoption or a board rejection.

Participation concentration

Only one discussion message is currently recovered. Its 100% message share describes this incomplete sample, not control of the wider debate. The separately listed author must not be counted as a second observed speaker.

Chokepoint analysis

The proposed definition connected an institutional category to access to independent IPv4 addresses. Expanding it could broaden eligibility, while the regional condition and two-assignment limit would remain boundaries. The archive alone cannot establish how AFRINIC exercised allocation discretion or whether an applicant was denied resources.

Uncertainties

  • The first draft, full meeting discussion and author's withdrawal explanation are not present in the reviewed material.
  • The recovered commenter remains an unresolved discussion identity. Neither personal motives nor a wider consensus can be inferred.

Policy evolution

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    DRAFT-02

    Withdrawn · Withdrawn by Author

    Source facts ↗
  3. Official decision

    withdrawn

    withdrawn

    Source facts ↗

Entities

Freshness: Stale
  1. SM · Identity unresolved
    Discussion messages1
    First activityNov 27, 2012
    Last activityNov 27, 2012
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies7
  2. Frank Habicht · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    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 10, 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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,518
    Known gaps
    0
  • afrinic-afripv6-discuss
    Earliest captured
    Aug 17, 2015
    Latest captured
    Sep 18, 2026
    Last refresh
    Oct 9, 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 9, 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 9, 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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    868
    Known gaps
    0
  • afrinic-dnssec-ops
    Earliest captured
    Aug 18, 2015
    Latest captured
    Dec 1, 2016
    Last refresh
    Oct 9, 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 9, 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 9, 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 9, 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 9, 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 9, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    154
    Known gaps
    0

Coverage

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