ARIN sets conditions for directory-service retirements after consultation

ARIN has published its directory-services consultation results, setting conditions for retiring older interfaces while returning port 43 WHOIS retirement to a future consultation. The 21 October decision matters to teams whose address-management workflows depend on registry lookups.

What changed

The revised roadmap separates four dependencies:

• RWhois: retirement will follow 365 days after a migration tool becomes available.
• Whois-RWS API: ARIN will address remaining RDAP feature gaps, documentation and training before deprecation.
• Whois-RWS web interface: a beta RDAP advanced-search tool will provide another opportunity for community feedback before replacement.
• Port 43 WHOIS: ARIN will monitor RDAP adoption in commercial products and query traffic, then consult again when the community's prerequisites are met.

These are the conditions in the published decision. The original consultation proposed calendar dates, which our September coverage correctly treated as tentative. Those proposal dates should not be presented as confirmed shutdown deadlines.

At the 23 October meeting, ARIN also explained that functional parity would not mean identical output. The ARIN 58 transcript, in its directory-services discussion, describes an advanced-search beta lasting at least six months, potentially longer. That is a planned evaluation period, not evidence that the beta has started.

Why it matters for BYOIP

Registry lookups can sit inside onboarding checks, IP address management systems and support workflows. Microsoft's Azure BYOIP documentation, for example, requires registry registration and verification of the range and its association with the customer's subscription.

For operators, the practical implication is to separate a provider's requirements from the interfaces used by their own tooling. An internal script that fails after an interface change could delay a deployment even when the prefix remains eligible for the provider's service. This announcement does not itself call for changing live route announcements.

ARIN documents RDAP as an HTTP-based protocol with structured JSON responses. A migration therefore needs checks of the information consumed by an integration, rather than only a change of URL.

What to check

1. Inventory each registry dependency by protocol, including supplier-managed tools. Avoid treating every service called “Whois” as the same interface.
2. Build a small set of representative prefix, ASN and organisation lookups. Compare required fields, references, empty results and error handling with RDAP.
3. Assign an owner to migration testing and keep a record of functional gaps. Use the forthcoming beta to test human search workflows separately from API clients.
4. Track the actual migration-tool release and subsequent notices before setting retirement dates in an internal change calendar.

Sources and further reading

The linked ARIN decision and meeting transcript distinguish the current roadmap from the original proposal. For the wider onboarding context, see our guide to registered holders, address rights and BYOIP.