Recommended RIR governance draft puts registry continuity in focus

A recommended third version of the Regional Internet Registry governance document was published on 1 September 2026. The proposal matters to address holders because it concerns the institutions providing registration and related services on which portable IP space depends. ARIN's announcement presents it as a recommended draft with further steps, not an already implemented change to resource-holder rules.

What changed

The ASO Address Council, also serving as the NRO Number Council, completed its recommended text. The package includes the draft, a comparison with the previous version and an explanation of changes; the NRO Executive Council is to provide updates on the next steps.

The version 3 document addresses recognition, ongoing operation and possible derecognition of regional registries. It includes audit and compliance processes and temporary arrangements intended to maintain registry services during emergencies.

Its definition of registry services extends beyond issuing addresses to registration, directory information and related technical services. The draft is therefore relevant to continuing use of existing resources as well as new allocations. These provisions should be read as proposed governance arrangements while adoption and implementation remain pending.

Why it matters for BYOIP

For operators, the useful lens is dependency management. Moving a prefix between providers involves more than a BGP announcement: teams also depend on the administrative records and authorization processes surrounding that prefix. Our guide to IP address holders and rights explains those relationships.

Our analysis is that registry continuity deserves a place in infrastructure planning, even when no immediate configuration change follows a governance announcement. The practical response is to know who holds the resources, who can administer them, and which provider workflows rely on registry information.

This is not a reason to change ROAs, move registrations or assume that a particular registry will lose recognition. The document is useful for tracking how the registry system proposes to handle exceptional conditions, rather than predicting that those conditions will occur.

What to check

• Keep the registered-holder details and authorized operational contacts for your prefixes documented and current.
• Identify registry-dependent steps in onboarding, renewals, transfers and incident response. Assign an internal owner to each dependency.
• Track official adoption and implementation notices before treating proposed procedures as active requirements.
• If a provider cites this draft as the reason for a new mandatory action, ask for the adopted rule, applicable date and registry notice supporting that action.

Sources and further reading

ARIN's announcement establishes the publication milestone and process status. The NRO text is the primary reference for the proposed provisions. Both should be revisited before reporting a later adoption or implementation event.