Summary

  • ARIN’s October roadmap keeps RWhois until a migration tool is public for 365 days, delays the Whois-RWS API until RDAP parity and documentation are ready, and adds an advanced-search beta before replacing the web interface.
  • Port 43 WHOIS has no sunset date. After 24 of 43 substantive comments opposed retirement or sought a longer transition, ARIN will monitor adoption and query traffic, then consult again against community-defined milestones.

ARIN’s August proposal named RDAP as its future standard directory service and set separate exits for three legacy protocols. Whois-RWS has both an API and a web interface, so four user-facing routes had to be handled. The plan looked like a timetable. By October, it looked more like a set of gates.

That change matters most to users of Port 43 WHOIS. The initial proposal put its retirement no earlier than 1 January 2029, after a two-year wind-down. The outcome published on 21 October names no date. ARIN will monitor RDAP adoption in commercial products and query traffic, then return to the community when milestones set by that community have been reached. The gate has replaced the calendar.

The August consultation treated the services separately. Whois-RWS has an API and a web interface; the proposal planned to retire the API after 180 days of outreach, while keeping the interface until RDAP could offer equivalent queries. RWhois would get a data-conversion tool and a 365-day countdown. Port 43, used by security teams, researchers, law enforcement and others, would get the longest window: two years, with a proposed floor of January 2029.

The October outcome keeps that service-by-service logic and makes the conditions more explicit. RWhois gets 365 days after the migration tool becomes public. The Whois-RWS API waits for ARIN to fix remaining RDAP parity issues and improve documentation and training. The web interface gets a beta RDAP advanced-search tool, which will collect more user feedback. Port 43 gets continued operation, adoption and traffic monitoring, and another consultation once community milestones are met.

At ARIN 58, the organization said Port 43 drew the sharpest pushback: 24 of 43 substantive comments opposed retirement or asked for a longer transition, according to the meeting recap. That is a real change in the plan, not a footnote to an inevitable shutdown.

RDAP has the standards case. The IETF standard gives directory data a structured, machine-readable form. That establishes the destination. The missing evidence is a public client-capability matrix and parity checklist; those records would show which legacy queries already have an RDAP route.

ARIN is right to separate the exits. A database operator can stop serving an old interface without abandoning the records and functions behind it. But the word “adoption” is not yet a test. The October roadmap does not publish a traffic threshold, a list of client capabilities that must exist, or the precise event that would trigger the next Port 43 consultation. Until that measure is public, the service has a reprieve with no visible finish line.

The practical shift is from “when does the old protocol end?” to “what must work first, and who can verify it?” For organizations that query Port 43, the answer is not to treat the old service as permanent. It is to ask ARIN for the milestone, the evidence that will satisfy it, and a transition notice that reaches users beyond ARIN’s own membership.

The directory function must outlast any one protocol. The people who depend on its output need enough time and evidence to move with it.