Amendment of Utilisation

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.

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.

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.

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.

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.