Summary

  • AFRINIC's published Contractual Obligations Check applies to Hostmaster, database and Internet Routing Registry queues. A request must come from a registered contact, the member must be in good standing and AFRINIC must hold a signed Registration Service Agreement.
  • If a check fails, AFRINIC says it denies support or number-resource requests, allows a reasonable period of about ten working days, closes a still-unresolved ticket and requires a fresh one after correction. The reviewed pages publish no severity class, clock definition or interim route for an urgent, reversible registry correction.

The gate has a legitimate job

The easy criticism would be that a registry should answer every message immediately. That would be wrong. A change to a resource record, reverse delegation or routing-policy object can affect parties beyond the sender. AFRINIC needs evidence that a requester speaks for the organisation recorded in its system. It also needs a current contractual counterparty and a workable rule for members that owe fees already due.

The Contractual Obligations Check makes those controls visible. It names three ticket queues: Hostmaster, afrinic-dbm and the Internet Routing Registry. It then names three tests. The ticket must originate from a registered contact; the Resource Member's account must be in good standing; and AFRINIC must have a signed RSA on file.

Each test addresses a different failure mode. Contact authority reduces the chance that a former employee, vendor or stranger changes an organisation's records. Good standing connects shared registry services to the financing obligation accepted by members. The signed RSA supplies the legal and administrative identity behind the service. These are not ceremonial boxes. Removing them would substitute speed for custody.

The contact rule is also more workable than a bare rejection. AFRINIC says a delegated person can proceed if an authorised contact resubmits the request or introduces that person. If all registered contacts have left, the page describes a recovery route using organisation letterhead, a senior signatory such as a CEO or CTO, and a company stamp. The signed-RSA guidance likewise says a requester should receive a notice and remediation details when AFRINIC cannot find the agreement in its internal member file.

Three queues meet one stop rule

The weakness is not the existence of the gate. It is the public description of what happens next. AFRINIC's non-compliance page says all support and/or IP-resource requests are denied until the relevant accounts comply with every section of the check. It allows a “reasonable” period of approximately ten working days. If the condition persists, the ticket is closed. After curing it, the requester must submit a fresh application or ticket.

That sequence is clear as debt or document administration. It is incomplete as queue control. A request for an additional allocation can wait without changing an existing public record. A correction to a contact, a reverse delegation or an IRR object may have a different operational clock. AFRINIC's IRR guide explains that networks publish routing policy for other operators to use. That fact does not mean a delayed ticket changes a route, still less that an outage has occurred. It does mean the queue deserves a declared way to distinguish ordinary work from a correction whose cost rises with time.

The public language does not make that distinction. It publishes no severity bands, no safe interim action and no rule for preserving a ticket's original place once the member supplies the missing evidence. “About ten working days” also leaves several small but consequential questions unanswered: which event starts the clock, which holidays apply, whether the clock pauses while AFRINIC reviews a submission, and which time zone controls the deadline.

Verification can itself require support

The circle is most visible in the membership-verification guide. AFRINIC says inaccurate registered contacts and organisation details breach the RSA and that support will not be provided until the situation is rectified. Yet some corrections are not wholly self-service. AFRINIC says only staff can change an organisation name or its general and billing addresses, and asks for documentary evidence such as a recent utility bill for an address change.

There is a recovery path: contact Member Services, provide the required records and clear the inconsistency. But the public pages do not join the verification request and the blocked operational ticket into one traceable case. A member can therefore face two pieces of work with different identifiers: cure the account first, then open the substantive ticket again.

The Member Guidebook shows why contact roles matter. Administrative, technical and billing contacts do different work; a technical contact may manage resources, assignments and reverse delegations. A generic “registered contact” status is therefore not the whole authorisation question. The useful record is who was authorised for this action, what was missing, when the cure arrived and whether the original operational risk survived the wait.

Good standing needs the same precision. AFRINIC's definition says a member must have completed the necessary formalities, remain current and owe no unsettled debt already due; an invoice not yet due does not disqualify the account. The CoC page adds calendar detail for current-year balances. That is a legitimate eligibility rule. It becomes more auditable when the ticket records the balance date used for the decision rather than leaving the member to reconstruct it later.

The evidence stops before an incident

Nothing in the reviewed record identifies a member whose ticket was wrongly denied. It shows no route leak, resource withdrawal, outage, missed deadline or arbitrary decision. It also cannot prove that AFRINIC staff lack an internal escalation procedure. The narrower finding is sufficient: the public rule that members can inspect does not describe risk triage, clock semantics, interim handling or a joined disposition record.

The distinction matters. An institution should not be accused on the strength of an empty field. But operators should not have to infer a critical control from private practice either. A published procedure earns confidence by explaining not only why it can stop work, but how it keeps the stop proportionate to the risk.

Sources

The analysis uses AFRINIC's CoC overview, non-compliance sequence, signed-RSA check, membership-verification guide, Member Guidebook, IRR guide and good-standing definition. The pages establish the published mechanism and its limits; they do not establish a particular incident.