AFRINIC · RIR Watchdog
Amendment of Utilisation
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-2026-IPv4-002-DRAFT02
- RIR
- AFRINIC
- Official status
- Ratified
- Normalized status
- Accepted
- Introduced
- May 6, 2026
- Last source update
- Oct 10, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Technical-need waiver and documented justification · Draft 1 says the utilisation requirement is waived for listed key technical needs. Draft 2 says it may be waived for demonstrated technical purposes and expressly requires enough documentation for AFRINIC to verify the justification. It retains the ordinary 90% threshold and the first-request exception for new members. The change makes the exceptional request more evidence-dependent; it is not an automatic entitlement or proof of any granted exception.
Source facts −
The above requirement is waived for network operators requesting new IP addresses for key technical needsSource facts ↗
Source facts +
The request justification must be sufficiently documented, in such way that AFRINIC can verify the compliance with the provided justification.Source facts ↗
Allocation and assignment terminology · The first assessment asks the author to preserve reference to both allocation and assignment, rather than the first draft's phrase first allocation or request. Draft 2 uses first allocation or assignment request, and its assessment no longer proposes wording changes. This clarifies the two resource-request forms without showing that any request was approved.
Source facts −
their current resource pool – and in these cases, the request is treated as a first allocation or request.Source facts ↗
Source facts +
In such circumstances, the relevant request shall be treated as a first allocation or assignment request for the purposes of this provision.Source facts ↗
Technical versus operational constraints · Draft 2's staff interpretation explicitly excludes operational constraints as grounds for waiving the threshold. The first assessment describes technical exceptions without that express exclusion. Both assessments retain the need to identify fraudulent requests and prevent abuse, and both estimate implementation within 30 days of ratification. The exclusion is identified as staff interpretation; it should not be attributed to an identical sentence in the operative policy text.
Source facts −
However, some technical constraints deem it necessary to override this threshold requirement.Source facts ↗
Source facts +
Operational constraints shall not be considered as justification to override this threshold requirement.Source facts ↗
Draft sequence and source-date uncertainty · The first draft's history dates its initial posting to 6 May 2026, while its migrated header carries a conflicting 2020 date. Draft 2's history dates the revision to 16 June 2026 and attributes it to RPD discussion, although its header still says 6 May 2026. Follow the explicit draft sequence and retain that date disagreement. The draft-2 capture used in this comparison says Last call; neither that label nor its proposed implementation timeline proves ratification or deployment.
Source facts −
6th May 2026 Version 1: AFPUB-2026-IPv4-002-DRAFT01 Initial Draft Posted to RPDSource facts ↗
Source facts +
16th June 2026 Version 2: AFPUB-2026-IPv4-002-DRAFT02 Changes according to RPD discussionSource facts ↗
Procedural status; unchanged utilisation rules · The later page reports consensus awaiting Board ratification instead of last call. Version 2.0 and the utilisation exception wording are unchanged. The record supports advancement in procedure, not implementation or a reversal of the exception; the exact decision date is not established by these captures.
Policy ratification status · The page-level status changes from consensus awaiting Board ratification to ratified, with 25 September 2026 recorded as the AFRINIC Board ratification date. The remainder of the captured document is unchanged.
Debate timeline
Official version
2.0
Unknown · Consensus (Awaiting Ratification by Board)(Presented at AF37 24 June 2026)
Source facts ↗Official version
2.0
Accepted · RatifiedRatified by the AFRINIC Board on 25 September 2026(Presented at AF37 24 June 2026)
Source facts ↗
Entities
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies7
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,545
- 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
- 897
- 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
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.
