Skip to main content

AFRINIC · RIR Watchdog

AFPUB-2017-GEN-002-DRAFT03

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-2017-GEN-002
RIR
AFRINIC
Official status
Unknown
Normalized status
Unknown
Introduced
Apr 5, 2018
Last source update
Oct 6, 2026
Coverage
Partial

Who actually shaped the debate?

1Total participants
UnknownDiscussion contributors
1Formal actors
UnknownDiscussion messages
UnknownEffective participants
UnknownTop-five discussion share
UnknownPeople covering 50%
UnknownPeople covering 80%

BTW Analysis

BTW Analysis

What changed

No policy change can be identified from the supplied verified facts. The chronology is empty, and no proposal versions, amendments, status changes, or stance transitions are recorded.

What the debate was really about

The substantive subject of the debate cannot be determined because no discussion messages, arguments, participants, or stance timelines are present in the verified record.

Decision vs debate

Neither a discussion process nor a formal decision is observable in the supplied record. Zero messages and discussion participants indicate no captured discussion, while zero formal actors and the absence of an outcome record mean that adoption, rejection, withdrawal, expiration, or supersession cannot be established.

Participation concentration

The snapshot records zero messages, zero participants, zero active days, and no one-time or repeat contributors. Consequently, the zero top-participant shares, HHI, effective-participant count, and core counts describe an empty dataset and do not demonstrate equal, broad, decentralized, or inclusive participation.

Chokepoint analysis

No procedural or actor-based chokepoint can be identified. The record supplies neither participants nor formal actors, and it omits the applicable decision body, procedure, threshold, and outcome. Any claim that a particular actor or stage controlled the process would therefore be unsupported.

Uncertainties

  • It is uncertain whether no debate occurred, whether debate occurred but was not captured, or whether relevant material falls outside the supplied source revision.
  • The policy chronology, proposal revisions, discussion record, participant identities, stance histories, formal decision actors, decision procedure, and outcome record are missing.
  • The zero concentration metrics are consistent with an empty dataset but cannot establish how participation would have been distributed in a complete record.
  • The Doctrine package provides an interpretive lens but does not establish a complete official position and cannot supply the missing facts or determine the policy outcome.

Policy evolution

DRAFT-05
Unknown · Archived
Jun 10, 2019
Source facts ↗

Working-group governance moves into a separate document · The comparison spans Draft 1 to Draft 5, rather than consecutive drafts. Draft 1 specifies a chair and vice-chair, elections, responsibilities, removal, resignation and posting restrictions in the same proposal. Draft 5 refers working-group guidelines and procedures to a separate PDP document and uses plural chairs; its history records a return to two chairs. The omitted details must not be treated as abolished everywhere.

Anonymous initiation and chair-as-editor provision is omitted · Draft 1 lets initiators remain anonymous and assigns the chair responsibility for acting as editor or finding a volunteer. Draft 5 omits that mechanism; its history attributes removal of anonymity and the chair-as-editor option to Draft 4. This is a change between the retained texts, not a claim that it first appeared in Draft 5.

Adoption period changes from a maximum to a minimum · Draft 1 caps the adoption phase at two weeks. Draft 5 requires a call for adoption of at least two weeks, after which the chairs consider the views expressed and announce discussion or rejection. The old-version column embedded in Draft 5 still contains the former maximum; the main proposed text and new-version column use the minimum.

Meeting support leads into the concluding phase · Draft 5 expressly presents the proposal at the next public policy meeting after review and asks whether it has enough support to enter the concluding phase. Major objections raised in that phase must be addressed before consensus is determined. Draft 1 describes rough consensus at the end of review, before last call. Both retain later feedback and the possibility of returning to discussion.

Last call must start within two weeks after the meeting · Draft 5 requires the chairs to initiate last call as soon as possible and no later than two weeks after the public policy meeting. Draft 1 starts last call after a review-phase consensus determination without that express post-meeting deadline. Both retain a last-call period of at least two weeks.

Ratification review includes process flaws and organisational harm · Draft 5 requires a comprehensive submission report and proposes ratification unless the board identifies a materially flawed process or consensus declaration, or harm to the organisation in its fiduciary role. It requires remand with reasons or specific advice. Draft 1 chiefly directs the board to check that the process was followed. This compares proposed board duties, not a legal ruling.

Mandatory pre-adoption board consultation is removed · Draft 1 requires the board to allow at least two weeks of working-group review before its emergency policy action. Draft 5 omits that additional consultation period and refers an adopted emergency policy to the following public policy meeting under the bylaws. The older staff assessment criticises the restriction; that criticism and the later proposed text are separate evidence.

An implementation deadline is restored · Draft 5 adds publication of the implementation date and a target of less than six months after board ratification unless a waiver is requested. Draft 1 lacks an implementation timetable, a gap explicitly identified by its staff assessment. The new clock starts at ratification, not at last-call consensus.

Appeals cover adoption decisions and gain a reporting deadline · Draft 5 expressly includes adoption-phase decisions in appeals. It dates the two-week filing window from announced chair actions or decisions on the list or at a meeting, adds a maximum four-week committee report period unless waived, and states that the committee decision is final. Draft 1 uses public knowledge of the decision and has no report deadline or explicit finality clause.

Capture dates do not establish consecutive legislative steps · Draft 1 has a 2018 submission header but a revision history dating the first posting to April 2017. Draft 5 has a 10 June 2019 submission header and a history entry dated 9 June. Its embedded comparison table contrasts Drafts 4 and 5, whereas this retained request compares Drafts 1 and 5. The differences cannot all be attributed to the final revision alone.

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Unknown · Archived

    Source facts ↗
  3. Official version

    DRAFT-01

    Unknown · Archived

    Source facts ↗
  4. Official version

    DRAFT-05

    Unknown · Archived

    Source facts ↗

Entities

Freshness: Stale
  1. Refer to Proposal Tab · 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 11, 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 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,555
    Known gaps
    0
  • afrinic-afripv6-discuss
    Earliest captured
    Aug 17, 2015
    Latest captured
    Sep 18, 2026
    Last refresh
    Oct 11, 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 11, 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 11, 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 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    904
    Known gaps
    0
  • afrinic-dnssec-ops
    Earliest captured
    Aug 18, 2015
    Latest captured
    Dec 1, 2016
    Last refresh
    Oct 11, 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 11, 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 11, 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 11, 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 11, 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 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    154
    Known gaps
    0

Coverage

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