Summary

  • ARIN's current Number Resource Policy Manual, section 12, permits review of the current use of any resources maintained in its database. An organization must cooperate with reasonable related documentation requests. ARIN may review without establishing cause at any other time unless a full review was completed in the preceding 24 months.
  • A new resource request, reason to suspect fraudulent or policy-contrary acquisition, and reason to suspect reassignment or reallocation noncompliance are separate review triggers. The 24-month clause qualifies the no-cause route, not every review.
  • Material noncompliance can prompt a request or requirement to return resources. If the holder does not voluntarily return them, ARIN may revoke resources issued by ARIN to restore overall compliance. Section 12 also directs attention to aggregation, renumbering time and continued service while a return or revocation is pending; it gives ARIN no added power to revoke legacy address space.

The first line of section 12 is broad: ARIN may review the current use of any resources maintained in its database. The next line places a duty on the organization to cooperate with reasonable requests for related documentation. An operator may treat its assigned or allocated space as part of a long-lived network plan. The policy treats its present use as a question the registry can reopen.

The sharpest entry point is a review without cause. ARIN need not establish a reason to start one at any other time, provided a full review has not been completed in the previous twenty-four months. The word “full” matters. A casual email or a partial check does not itself satisfy the published condition. So does “completed”: the clock is tied to the end of a full review, not to the first document request. The holder should keep the conclusion notice, because section 12 requires ARIN to tell a holder when a review involving requested information has ended and what further action is required.

The two-year brake is not a general immunity period. Section 12 gives ARIN three other reasons to open the file. One is a request for new resources. Another is reason to believe resources were originally obtained fraudulently or contrary to existing policy. A third is reason to believe an organization is not following reassignment or reallocation policies. Those are listed separately from the no-cause option. A holder planning an expansion cannot assume that last year's completed audit bars scrutiny of a new request. A holder facing a documented fraud or registration concern cannot invoke the no-cause interval as a universal stop sign.

What happens after review deserves more attention than the opening letter. Where ARIN finds material noncompliance with current policy, it may ask or require the organization to return enough resources to come into, or reasonably close to, compliance. The policy gives ARIN staff room for reasonable judgment about how much noncompliance remains. They must consider utilization, available address pool and other facts, avoiding a forced return that would prompt an immediate new request or unnecessary route de-aggregation. The rule prefers whole-block returns; a partial return should leave one aggregate block.

Those provisions recognize that a bad cut through an address plan can create a routing cost.

The escalation is explicit. If the organization does not voluntarily return resources as requested, ARIN may revoke resources that ARIN issued as needed to restore overall compliance, applying the same guidelines. That is an institutional power over the registered holder's ability to keep operating with an address block, not simply a request to correct an inaccurate WHOIS field. Yet the policy sets operational limits around the process. Except for fraud or policy violation, a holder receives at least six months to effect a return. ARIN negotiates a longer period if it believes the organization is working in good faith and has a valid need for renumbering time. Service continues while return or revocation is pending, with maintenance fees calculated as if the action were complete.

Legacy resources sit at an important boundary. Section 12 says it creates no additional authority for ARIN to revoke legacy address space. The utilization of legacy resources may still be considered when ARIN assesses overall compliance. Those statements work together: a legacy block can enter the calculation without becoming newly revocable under this section. An inventory that combines ARIN-issued and legacy resources without recording their origin obscures both exposure and the scope of ARIN's remedy.

The manual also bars premature failure findings for policies that allow a future compliance period. If a rule gives the holder a specified interval to assign prefixes or reach a usage target, section 12 says noncompliance cannot be measured until that interval has passed. A review may open earlier, but an unfinished allowance cannot be declared a missed deadline. The timing of the underlying policy matters as much as the date of the review.

The current rule has a history. ARIN's 2007 resource-review proposal archive shows the community's attempt to put a process around an expansive review power. The live manual is the operative text. It preserves no-cause review, attaches the twenty-four-month full-review condition, requires a conclusion notice after requested documentation and sets rules for returns and revocation. That is not an absence of process. It is a process whose first move can still arrive without a stated reason.

The official records reviewed here do not identify a specific recent organization subjected to a no-cause review, a block returned under section 12 or a revocation decision. A dated ARIN review notice and outcome would show how the rule operates in a case. The published text already tells boards where the exposure begins: in the registry's authority to revisit utilization and in the distinction between a narrow pause on unprompted review and the other paths into the file.