Summary

  • AFRINIC's current CPM says an implementation date should fall less than six months after the end of Last Call, unless a waiver is requested. Its current PDP explainer says less than six months after Board ratification.
  • For AFPUB-2020-GEN-006-DRAFT03, Last Call ended on 5 January 2022 and AFRINIC identified ratification on 4 February 2026. Those formulations therefore point to dates more than four years apart.
  • The proposal's official page separately says implementation will take twelve months without naming the event that starts that estimate. AFRINIC-37 records work underway and technical deployment after MyAFRINIC v2.
  • The record does not establish illegality, bad faith or the absence of a non-public waiver. It establishes that a reader cannot reconstruct the governing clock. A versioned implementation receipt would make the origin, waiver, dependency and completion state inspectable.

A duration without an origin is not a clock

Six months sounds precise. It is precise only after somebody answers “six months from what?” AFRINIC currently gives two answers on two pages that each describe the same policy-development process.

Section 3.4.5 of the current Consolidated Policy Manual says that adoption and implementation dates are announced on the Resource Policy Discussion mailing list. It then says the implementation date “should be less than six months after the end of the Last Call unless a waiver is requested.” Last Call is the origin. The waiver is the branch.

The current Policy Development page describes the final phase differently. Its diagram labels the phase “implementation ≤ 6 months after ratification.” The accompanying text says the implementation date must be less than six months after the Board ratifies a proposal, unless a waiver is requested. A later line says staff implement the proposal within six months of ratification and incorporate it into the CPM. Ratification is the origin.

This is not a debate about whether six months contains 180, 182 or 184 days. The two formulations choose different institutional events. Last Call closes community review. Ratification is a later corporate act confirming that the process was followed. When the gap between them is short, the contradiction may hide. When the gap lasts years, it decides whether a clock expired before the Board acted or began only after it acted.

The transfer policy turns the wording into four years

The Number Resources Transfer Policy supplies unusually clear dates. On the RPD archive, the co-chairs said Last Call for draft 3 would begin on 8 December 2021 and end at 23:59 UTC on 5 January 2022. Applying the CPM text mechanically points to early July 2022.

AFRINIC's ratification overview identified 4 February 2026 as the date on which draft 3 and the Abuse Contact Policy Update were ratified. Applying the current explanatory page mechanically points to early August 2026. The two origins are separated by about forty-nine months.

The ratification overview itself now illustrates another recordkeeping weakness. It remained indexed with the 4 February heading during this review, but a fresh direct request to its published URL returned HTTP 404 on 8 September. The date is not unsupported: the current proposal table marks the policy Ratified, the official proposal page does the same, AFRINIC's newsletter announced the two ratifications, and the June public-meeting minutes discuss their implementation. But a missing overview makes the chain harder to follow precisely when its date is needed to calculate the newer clock.

The point is not that one arithmetic result automatically wins. The CPM uses “should”, and it expressly permits a waiver request. The point is that AFRINIC has not given the public a joined record saying which formula it applied to this policy, whether the long interval between Last Call and ratification changed the formula, or what decision connected any waiver to a revised implementation date.

A third duration appears without a start event

The transfer proposal's own official page adds another number. It retains a staff assessment dated 28 February 2022 and an Implementation section that says: “Timeline: The proposal will take 12 months to be implemented.” That may be a workload estimate, not a procedural deadline. It may begin at ratification, at approval of a project plan, at the start of development, or at some other operational milestone. The page does not say.

The distinction matters. A forecast answers how long staff expect work to take. A rule answers when an institutional obligation should be completed. A waiver explains why the rule's ordinary path does not apply. All three can coexist, but only if the record joins them. An unanchored twelve-month forecast cannot silently replace either six-month formula, and a six-month formula cannot prove that software can be delivered safely without a dependency plan.

There is a practical reason for a longer path. The 2022 staff assessment describes substantial changes: new transfer workflows, resource tagging, ASN handling, external-RIR integration, transfer-log updates, procedural reviews and possible contractual work. It anticipated a major code review and a rewrite of the automated transfer tool. Those are not cosmetic edits.

The June 2026 AFRINIC-37 minutes make the current dependency still clearer. Staff said Member Services was coordinating with the other RIRs to map procedures. Technical implementation would be prioritised after MyAFRINIC v2. The minutes explain that trying to implement rules on other systems could create broken business rules when a member later updated the same resources through MyAFRINIC. The portal project was expected by the end of 2026.

That is evidence of work and of a plausible sequencing constraint. It is not evidence that full implementation had already occurred. AFRINIC's PIER summary still described ASN transfers as something the ratified policy would allow “once implemented.” The current proposal table labels the transfer policy Ratified. Its remarks cell is blank, while the RPKI policy immediately below it says “Awaiting Implementation.” A blank cell is not a completion certificate, just as “once implemented” is not proof that nothing has begun.

“Implemented” needs more than one state

The public record already contains at least four distinguishable states. Procedures can be mapped with counterpart RIRs. Code can be under development or internal test. A subset of the policy can be active. The complete ratified text can be incorporated into the CPM and available through every relevant system. Calling all four “implementation” makes a date impossible to audit.

The distinction is especially important for a transfer policy. A member may need to know whether an intra-regional IPv4 transfer can be accepted, whether an ASN can move, whether an inter-RIR counterpart is ready, whether resource tags are live, and which version of the RSA or transfer agreement governs the case. A policy can have a real procedure on one path and an unfinished system dependency on another. Neither a launch announcement nor a status label should stand in for a matrix of those capabilities.

This article does not claim that AFRINIC cannot process any transfer today. The existing CPM already contains an earlier intra-regional IPv4 transfer section, and M&A practices may follow separate guidelines. Nor does it claim that “implementation underway” is empty language. The narrower finding is that the public sources do not connect current work to one controlling clock and one terminal definition.

The waiver branch is named but not observable

Both six-month formulations preserve a waiver. That is sensible. A registry should not be pushed into unsafe deployment merely to satisfy a date when governance interruption, legal restraint, interoperability or a major platform dependency makes the ordinary sequence impossible.

Yet the clause gives a reader almost none of the information needed to evaluate such a departure. It does not say, in that sentence, who requests the waiver, who decides it, what evidence is required, whether the request and decision are public, which part of implementation is covered, or what new date replaces the original expectation.

The CPM separately contains an emergency variance mechanism in section 3.6, decided by a Working Group Chair with an explanation and a minimum review period. It would be unsafe to assume that every implementation waiver is necessarily that emergency variance; the manual does not make the relationship explicit. A good receipt would identify the authority instead of making the reader infer it.

A targeted review of AFRINIC's site and RPD archive did not locate a public document that could confidently be identified as the transfer policy's implementation-waiver request and decision. That is a bounded finding. It cannot prove that no internal or unpublished waiver exists. It does show why the public cannot use the waiver branch to reconcile the clocks.

One receipt can preserve operational discretion

The repair does not require a new dashboard. A signed or versioned page for each ratified proposal would be enough if it carried the right joins.

The first block should identify the proposal ID, the hash or immutable version of the ratified text, and the PDP/CPM version that governs implementation. The second should record Last Call start and end, the ratification resolution and timestamp, the chosen clock origin, the formula and the computed ordinary target. The third should record any waiver request, requester, decision authority, rationale, scope, decision date and replacement target.

The operating block should then list dependencies and stages: procedures mapped, agreements ready, counterpart acceptance, code deployed, internal test complete, limited path active, full ratified text active, and CPM incorporation complete. Each state needs an effective date and evidence link. Corrections should preserve the prior value rather than erase it.

This receipt would not expose member cases, security controls or unreleased code. It would expose the institutional choice. AFRINIC could say openly that the Last-Call formula became impracticable after a four-year governance interruption, that the Board-ratification formula now controls, and that MyAFRINIC v2 justifies a dated waiver or revised milestone. Or it could explain a different lawful and community-consistent reading. What matters is that the answer is made once, under named authority, and remains attached to the policy.

The strongest clock is not the shortest one. It is the clock whose origin, pause, exception and finish can all be reconstructed after the people who made the decision have changed.

Sources