Summary

  • ARIN told its 22 October meeting that some organizations receiving IPv4 addresses through transfers had not known they must wait 12 months before acting as a source for another transfer.
  • The clock sits in the source provisions of NRPM 8.3 and 8.4. Staff asked whether to repeat it in the recipient provisions and whether an early attempt should prompt a resource review.

The next outgoing deal can fail the calendar test before anyone examines the addresses being sent. ARIN’s rule asks whether the organization received IPv4 space within the previous year. That is why the ARIN 58 Policy Implementation and Experience Report matters: staff says some recipients did not know about the wait before trying to become a source themselves. Registration Services alerts them during the incoming transfer, yet the public manual asks a new holder to read the rules for its future role to find the clock.

Section 8.3 of the current NRPM governs specified transfers inside the ARIN region. Its source clause says an organization generally must not have received a transfer, allocation or assignment from ARIN in the preceding 12 months before transferring out. It has stated exceptions, including M&A transfers under 8.2 and a possible renumbering waiver. Section 8.4 places an analogous condition on an in-region source in an inter-RIR transfer, with its own common-control and 8.2 exceptions. The recipient paragraphs tell incoming holders about qualification and current policy; they do not spell out the future source clock.

The test attaches to the organization, rather than merely to the newly received addresses. A network that takes in one block and later wants to transfer an older one faces the source clock too, subject to the section’s exceptions. That turns a seemingly small placement error into a question for anyone sequencing address transactions: the second deal may have to wait for the first deal’s anniversary. ARIN publishes no count of surprised recipients or blocked deals. Its Day 1 recap confirms the issue reached the meeting floor.

Sweeting’s report asks two separate questions. Should the warning appear where recipients read? And should ARIN initiate a review under NRPM 12 when a recent recipient tries to start a source transfer? The first would change notice. The second would change the response to a failed attempt. ARIN has posed them to the community; its published manual still contains the existing text.