From info at arin.net  Fri Aug 14 11:16:12 2026
From: info at arin.net (ARIN)
Date: Fri, 14 Aug 2026 11:16:12 -0400
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
 =?utf-8?q?=E2=80=99s_Directory_Services?=
Message-ID: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>

ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services.

ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN?s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service.

This transition is an important step toward improving alignment with established IETF standards.

We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years.

------
Benefits of Transition to RDAP?

- Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.?
- Standardization and Automation: RDAP?s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.?
- Reduced Technical Overhead:?Removing old and redundant services will provide time and cost savings for ARIN.?

------
Timeline and Retirement Planning

This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently.

***
Whois-RWS?Retirement Plan and Timeline

ARIN currently offers Whois-RWS in two formats: an API and a web interface (located at https://whois.arin.net/ui/). Because the API has the same functionality between?Whois-RWS and?RDAP, ARIN proposes sunsetting the?Whois-RWS API following?a 180-day?customer outreach program.?This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy?that includes?announcements, social promotion, and other outreach.

The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users?visiting that URL.?ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience.

***
RWhois Retirement Plan and Timeline

When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead.

***
Whois (Port 43) Retirement Plan?and Timeline

ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline.

Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43).

------
After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service.

- Whois-RWS: on or after 1 July 2027
- RWhois: dependent on migration tool release date, but no sooner than 1 January 2028
- Whois (Port 43): on or after 1 January 2029

Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN?s transition to RDAP as its standard directory service.

We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently.

Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult.

This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important.

Thank you for your continued support in improving ARIN?s services.

Regards,

John Curran
President and CEO
ARIN

------
Relevant links:
- Presentation from ARIN 56: https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf
- IETF Standard for RDAP: https://www.rfc-editor.org/info/std95
- Guide to RDAP Client Implementations: https://rdap.rcode3.com/client_implementations/index.html
- ARIN RDAP Documentation: https://www.arin.net/resources/registry/whois/rdap/



From markvd at markvd.net  Fri Aug 14 14:21:15 2026
From: markvd at markvd.net (Mark Van Daele)
Date: Fri, 14 Aug 2026 13:21:15 -0500
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
 =?utf-8?q?=E2=80=99s_Directory_Services?=
In-Reply-To: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
Message-ID: <8f785ff6-9648-427c-a57a-010b2adf9173@markvd.net>

ARIN team/Community,

Thank you for the opportunity to provide input on the proposed 
retirement timelines for Whois?RWS, RWhois, and Whois Port 43. I 
appreciate ARIN?s continued efforts to modernize directory services and 
align with IETF standards.

After reviewing the consultation request, I support the retirement of 
Whois?RWS and RWhois. Both services are legacy mechanisms with limited 
adoption, redundant functionality, and meaningful operational overhead. 
Their planned deprecation makes sense especially given low usage, and 
the transition to RDAP for these two protocols is appropriate and 
beneficial.

However, I strongly recommend retaining support for Whois Port 43 going 
forward. While RDAP is unquestionably the modern standard, Port 43 
continues to serve a large and diverse operational community including:

* Users of operating system distributions that still ship Port 43 
clients by default
* Legacy automation and tooling across countless organizations
* Security operations centers
* Threat intelligence platforms
* Academic researchers
* Law enforcement

The volume and breadth of Whois Port 43 usage is significantly higher 
than any other legacy protocol. Its simplicity, ubiquity, and 
compatibility with decades of tooling make it uniquely valuable. Even 
with RDAP available, Port 43 remains deeply embedded in workflows that 
cannot be easily or quickly replaced.

For these reasons, I believe Whois Port 43 should continue to coexist 
with RDAP rather than be fully retired. Maintaining Port 43 alongside 
RDAP would preserve critical operational continuity for the broader 
Internet community while still allowing ARIN to advance RDAP as the 
preferred and modernized interface.

Thank you for considering this perspective, I appreciate ARIN?s 
engagement with the community before making major changes.

Thank You,
Mark Van Daele

On 8/14/2026 10:16 AM, ARIN wrote:
> ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services.
>
> ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN?s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service.
>
> This transition is an important step toward improving alignment with established IETF standards.
>
> We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years.
>
> ------
> Benefits of Transition to RDAP?
>
> - Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.?
> - Standardization and Automation: RDAP?s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.?
> - Reduced Technical Overhead:?Removing old and redundant services will provide time and cost savings for ARIN.?
>
> ------
> Timeline and Retirement Planning
>
> This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently.
>
> ***
> Whois-RWS?Retirement Plan and Timeline
>
> ARIN currently offers Whois-RWS in two formats: an API and a web interface (located at https://whois.arin.net/ui/). Because the API has the same functionality between?Whois-RWS and?RDAP, ARIN proposes sunsetting the?Whois-RWS API following?a 180-day?customer outreach program.?This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy?that includes?announcements, social promotion, and other outreach.
>
> The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users?visiting that URL.?ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience.
>
> ***
> RWhois Retirement Plan and Timeline
>
> When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead.
>
> ***
> Whois (Port 43) Retirement Plan?and Timeline
>
> ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline.
>
> Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43).
>
> ------
> After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service.
>
> - Whois-RWS: on or after 1 July 2027
> - RWhois: dependent on migration tool release date, but no sooner than 1 January 2028
> - Whois (Port 43): on or after 1 January 2029
>
> Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN?s transition to RDAP as its standard directory service.
>
> We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently.
>
> Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult.
>
> This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important.
>
> Thank you for your continued support in improving ARIN?s services.
>
> Regards,
>
> John Curran
> President and CEO
> ARIN
>
> ------
> Relevant links:
> - Presentation from ARIN 56: https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf
> - IETF Standard for RDAP: https://www.rfc-editor.org/info/std95
> - Guide to RDAP Client Implementations: https://rdap.rcode3.com/client_implementations/index.html
> - ARIN RDAP Documentation: https://www.arin.net/resources/registry/whois/rdap/
>
>
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.

From bradan at cogspin.com  Fri Aug 14 15:41:17 2026
From: bradan at cogspin.com (Bradan Fleming)
Date: Fri, 14 Aug 2026 12:41:17 -0700
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
 =?utf-8?q?=E2=80=99s_Directory_Services?=
In-Reply-To: <8f785ff6-9648-427c-a57a-010b2adf9173@markvd.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
 <8f785ff6-9648-427c-a57a-010b2adf9173@markvd.net>
Message-ID: <f3c5a6df9095a2ae7e8973366f06859aba85bbd9.camel@cogspin.com>

+1 to this

As far as I can tell, the proposed port 43 WHOIS retirement is driven
by two main goals:

1. Reducing the cost ARIN has to pay to maintain legacy services
2. Encouraging people to adopt RDAP and stop using port 43 WHOIS in
production services by breaking their workflows

Retiring port 43 is certainly one way to accomplish that, but I think
there is a way to accomplish those goals without doing so.

- Create a lightweight service that mimics the WHOIS registry by
translating the lookups to RDAP behind the scenes and reformatting the
output.
- Use this new service to replace the (presumably costly)
infrastructure used to run the existing WHOIS services.
- Heavily ratelimit that service such that it is only useful for low-
volume users (e.g., individuals).

On a personal note, port 43 WHOIS is an adorable and historically
important protocol that holds a special place in the hearts of many. I
would hate to see it go away completely.

Regarding distributions not shipping RDAP clients, I suspect that might
change once ICANN-RDAP reaches its 1.0.0 release. (It even supports
WHOIS-style formatting!)

Best,
Bradan Fleming

On Fri, 2026-08-14 at 13:21 -0500, Mark Van Daele via ARIN-consult
wrote:
> ARIN team/Community,
> 
> Thank you for the opportunity to provide input on the proposed 
> retirement timelines for Whois?RWS, RWhois, and Whois Port 43. I 
> appreciate ARIN?s continued efforts to modernize directory services and 
> align with IETF standards.
> 
> After reviewing the consultation request, I support the retirement of 
> Whois?RWS and RWhois. Both services are legacy mechanisms with limited 
> adoption, redundant functionality, and meaningful operational overhead. 
> Their planned deprecation makes sense especially given low usage, and 
> the transition to RDAP for these two protocols is appropriate and 
> beneficial.
> 
> However, I strongly recommend retaining support for Whois Port 43 going 
> forward. While RDAP is unquestionably the modern standard, Port 43 
> continues to serve a large and diverse operational community including:
> 
> * Users of operating system distributions that still ship Port 43 
> clients by default
> * Legacy automation and tooling across countless organizations
> * Security operations centers
> * Threat intelligence platforms
> * Academic researchers
> * Law enforcement
> 
> The volume and breadth of Whois Port 43 usage is significantly higher 
> than any other legacy protocol. Its simplicity, ubiquity, and 
> compatibility with decades of tooling make it uniquely valuable. Even 
> with RDAP available, Port 43 remains deeply embedded in workflows that 
> cannot be easily or quickly replaced.
> 
> For these reasons, I believe Whois Port 43 should continue to coexist 
> with RDAP rather than be fully retired. Maintaining Port 43 alongside 
> RDAP would preserve critical operational continuity for the broader 
> Internet community while still allowing ARIN to advance RDAP as the 
> preferred and modernized interface.
> 
> Thank you for considering this perspective, I appreciate ARIN?s 
> engagement with the community before making major changes.
> 
> Thank You,
> Mark Van Daele
> 
> On 8/14/2026 10:16 AM, ARIN wrote:
> > ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services.
> > 
> > ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN?s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service.
> > 
> > This transition is an important step toward improving alignment with established IETF standards.
> > 
> > We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years.
> > 
> > ------
> > Benefits of Transition to RDAP?
> > 
> > - Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.?
> > - Standardization and Automation: RDAP?s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.?
> > - Reduced Technical Overhead:?Removing old and redundant services will provide time and cost savings for ARIN.?
> > 
> > ------
> > Timeline and Retirement Planning
> > 
> > This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently.
> > 
> > ***
> > Whois-RWS?Retirement Plan and Timeline
> > 
> > ARIN currently offers Whois-RWS in two formats: an API and a web interface (located at https://whois.arin.net/ui/). Because the API has the same functionality between?Whois-RWS and?RDAP, ARIN proposes sunsetting the?Whois-RWS API following?a 180-day?customer outreach program.?This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy?that includes?announcements, social promotion, and other outreach.
> > 
> > The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users?visiting that URL.?ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience.
> > 
> > ***
> > RWhois Retirement Plan and Timeline
> > 
> > When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead.
> > 
> > ***
> > Whois (Port 43) Retirement Plan?and Timeline
> > 
> > ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline.
> > 
> > Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43).
> > 
> > ------
> > After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service.
> > 
> > - Whois-RWS: on or after 1 July 2027
> > - RWhois: dependent on migration tool release date, but no sooner than 1 January 2028
> > - Whois (Port 43): on or after 1 January 2029
> > 
> > Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN?s transition to RDAP as its standard directory service.
> > 
> > We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently.
> > 
> > Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult.
> > 
> > This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important.
> > 
> > Thank you for your continued support in improving ARIN?s services.
> > 
> > Regards,
> > 
> > John Curran
> > President and CEO
> > ARIN
> > 
> > ------
> > Relevant links:
> > - Presentation from ARIN 56: https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf
> > - IETF Standard for RDAP: https://www.rfc-editor.org/info/std95
> > - Guide to RDAP Client Implementations: https://rdap.rcode3.com/client_implementations/index.html
> > - ARIN RDAP Documentation: https://www.arin.net/resources/registry/whois/rdap/
> > 
> > 
> > _______________________________________________
> > ARIN-Consult
> > You are receiving this message because you are subscribed to the ARIN Consult Mailing
> > List (ARIN-consult at arin.net).
> > Unsubscribe or manage your mailing list subscription at:
> > https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> > Help Desk at info at arin.net if you experience any issues.
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.

From andy at hxr.us  Fri Aug 14 16:16:17 2026
From: andy at hxr.us (Andy Newton)
Date: Fri, 14 Aug 2026 16:16:17 -0400
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
 =?utf-8?q?=E2=80=99s_Directory_Services?=
In-Reply-To: <f3c5a6df9095a2ae7e8973366f06859aba85bbd9.camel@cogspin.com>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
 <8f785ff6-9648-427c-a57a-010b2adf9173@markvd.net>
 <f3c5a6df9095a2ae7e8973366f06859aba85bbd9.camel@cogspin.com>
Message-ID: <3ac01960-37f2-4662-9feb-1cfe666cbf8d@hxr.us>



On 8/14/26 3:41 PM, Bradan Fleming via ARIN-consult wrote:
> 
> Regarding distributions not shipping RDAP clients, I suspect that might
> change once ICANN-RDAP reaches its 1.0.0 release. (It even supports
> WHOIS-style formatting!)

Soon. Preparations are underway. The last release included support for geofeeds and the next will have support for the rpki1 extension.
It is already packaged in Homebrew and the AUR and Debian Sid.

OpenRDAP is also very widely packaged.

-andy



From bill at herrin.us  Sat Aug 15 06:12:50 2026
From: bill at herrin.us (William Herrin)
Date: Sat, 15 Aug 2026 03:12:50 -0700
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
	=?utf-8?q?=E2=80=99s_Directory_Services?=
In-Reply-To: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
Message-ID: <CAP-guGWUGpqLhW2W+p37cnogPSrjU_kUs0xCK-u2kxrErtVqkA@mail.gmail.com>

On Fri, Aug 14, 2026 at 8:16?AM ARIN <info at arin.net> wrote:
> We also expect RDAP clients to become increasingly common in OS distributions in the coming years.

Howdy,

Speaking for myself:

When you retire WHOIS, I don't want RDAP clients to be "increasinging
common" in OS distributions or available as something I can compile
for installation in /usr/local/bin. I want it to already be present as
a standard software package on my 3-year-old Linux server. And I want
it to work about as well as "whois 1.2.3.4" does now.

Debian Linux added the rdap package in release 13 on 8/9/2025. If
Debian Linux were your benchmark, that means you could reasonably
retire the whois service on or after August 9 2028. Not before.

>From what I can gather, an RDAP client is not directly available in
Red Hat RHEL 10, although if you trust and can use the SNAP ecosystem
it's available as a SNAP package. I would not consider a SNAP package
to be generally available -- I'd want to see a native RPM. My three
year clock would not start until that happens. I would probably
consider adding an official ARIN RPM repo to be reasonable -- adding
repos is a low lift and ARIN is trustworthy enough that it won't raise
a flag during my customers' security audits.

I did not find anything described as an RDAP tool in the Microsoft
Windows Store. There are multiple whois tools though I've no idea
about their efficacy.


It would not greatly offend me if at some point ARIN's whois port
started returning RDAP results in a format comparable to the RDAP
client. Asking me to move my _automation_ off of whois sooner than the
service's final retirement seems reasonable.


> ARIN understands that Whois (Port 43) carries a high volume of
> queries and will require the longest timeline to retire. We propose
> a two-year sunsetting window, during which ARIN will engage in
> active outreach to users.

For the reasons stated above, hard no on a two year retirement
timeline. Though again, it would not offend me if there was a 2-year
deprecation notice that on or about 1/1/29 the results from port 43
will continue to be provided and human readable but their format will
change without notice with no further attempt to support automation.

Except insofar as it has been integrated into the port 43 results, I
never really used rwhois or rwhois-rws. Their retirement timelines are
less concerning to me.

Regards,
Bill Herrin



-- 
For hire. https://bill.herrin.us/resume/

From patrick at klos.com  Sat Aug 15 09:59:54 2026
From: patrick at klos.com (Patrick Klos)
Date: Sat, 15 Aug 2026 09:59:54 -0400
Subject: [ARIN-consult] =?utf-8?q?Consultation_on_the_Future_of_ARIN?=
 =?utf-8?q?=E2=80=99s_Directory_Services?=
In-Reply-To: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
Message-ID: <d278058d-5713-4d3c-a4ad-cc1b26ed79f3@klos.com>

I believe the text based WHOIS service is still quite valuable and 
necessary.

It was the biggest mistake to allow ICANN to let domain owners obfuscate 
their contact information.

The domain WHOIS system was immensely useful in helping to fight spam, 
phishing, malware and other forms of Internet abuse and crime!? But when 
ICANN let anyone and everyone HIDE THEIR CONTACT INFO, the system became 
useless!!? Europe does not control us and the rest of the world.? Why 
are we letting their privacy laws change the way the rest of the world 
does WHOIS???

Since ICANN allows domain owner's to hide their contact information, why 
have a domain WHOIS system at all?!?!?

Even ARIN isn't very strict on enforcing accurate and up to date 
information in their WHOIS record.? Amazon lists 206-555-0000 (an 
obviously invalid number) as their phone number in their WHOIS 
record(s).? I've reported this to ARIN several times, but the 
intentional error remains.

Don't tell me that the text based WHOIS service creates a greater 
"threat landscape" or "attack vector".? Text based WHOIS has been around 
for decades - by now, I'm sure it's quite hardened!? And really, tell 
me, how hard is it to continue to maintain something simple that domain 
registrars have already been doing since day 0? It's stupid to take away 
something that works and costs almost nothing to maintain.? I'm sure 
integrating text based WHOIS into the new RDAP infrastructure can't be 
too big a deal?!?

As for RDAP, adding this new much more complicated (relatively speaking) 
technology poses a much greater risk of unforeseen attack vectors.

Lastly, what good is RDAP if ICANN's WHOIS accuracy requirements are 
still being ignored??? I still can't look up actual contact information 
for domains whose server might have been compromised by scammers or 
phishers, so what am I getting from RDAP?!?!?? Let's just hope that ARIN 
doesn't follow suite in that regard?!?

_*Bottom line:? Sure, let's adopt RDAP, but there's no reason to get rid 
of text based WHOIS!*_

Patrick Klos
Klos Technologies, Inc.

On 8/14/2026 11:16 AM, ARIN wrote:
> ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services.
>
> ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN?s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service.
>
> This transition is an important step toward improving alignment with established IETF standards.
>
> We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years.
>
> ------
> Benefits of Transition to RDAP?
>
> - Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.?
> - Standardization and Automation: RDAP?s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.?
> - Reduced Technical Overhead:?Removing old and redundant services will provide time and cost savings for ARIN.?
>
> ------
> Timeline and Retirement Planning
>
> This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently.
>
> ***
> Whois-RWS?Retirement Plan and Timeline
>
> ARIN currently offers Whois-RWS in two formats: an API and a web interface (located athttps://whois.arin.net/ui/). Because the API has the same functionality between?Whois-RWS and?RDAP, ARIN proposes sunsetting the?Whois-RWS API following?a 180-day?customer outreach program.?This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy?that includes?announcements, social promotion, and other outreach.
>
> The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users?visiting that URL.?ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience.
>
> ***
> RWhois Retirement Plan and Timeline
>
> When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead.
>
> ***
> Whois (Port 43) Retirement Plan?and Timeline
>
> ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline.
>
> Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43).
>
> ------
> After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service.
>
> - Whois-RWS: on or after 1 July 2027
> - RWhois: dependent on migration tool release date, but no sooner than 1 January 2028
> - Whois (Port 43): on or after 1 January 2029
>
> Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN?s transition to RDAP as its standard directory service.
>
> We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently.
>
> Please provide comments toarin-consult at arin.net. You can subscribe to this mailing list athttps://lists.arin.net/mailman/listinfo/arin-consult.
>
> This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important.
>
> Thank you for your continued support in improving ARIN?s services.
>
> Regards,
>
> John Curran
> President and CEO
> ARIN
>
> ------
> Relevant links:
> - Presentation from ARIN 56:https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf
> - IETF Standard for RDAP:https://www.rfc-editor.org/info/std95
> - Guide to RDAP Client Implementations:https://rdap.rcode3.com/client_implementations/index.html
> - ARIN RDAP Documentation:https://www.arin.net/resources/registry/whois/rdap/
>
>
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult  Please contact the ARIN Member Services
> Help Desk atinfo at arin.net  if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20260815/c1555e20/attachment.htm>

From lav at lavender.earth  Sat Aug 15 19:59:31 2026
From: lav at lavender.earth (Lavender-Jamie)
Date: Sun, 16 Aug 2026 00:59:31 +0100
Subject: [ARIN-consult] 
 =?utf-8?q?Whois_using_these_ARIN_services=3F=3F__?=
 =?utf-8?q?=28fwd=3A__Consultation_on_the_Future_of_ARIN=E2=80=99s_Directo?=
 =?utf-8?q?ry_Services=29?=
In-Reply-To: <8132D321-98CF-4758-8D01-15139408EFE6@arin.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
 <8132D321-98CF-4758-8D01-15139408EFE6@arin.net>
Message-ID: <7dbdee043cc8e505d9cdecda87ded3e1@lavender.earth>

On 2026-08-14 16:20, John Curran via NANOG wrote:
> NANOGers -
> 
> ARIN is undertaking a community consultation on the Future of ARIN?s
> Directory Services.  If you are interested in this topic, please see
> details below, including how to join the ARIN-consult mailing list.
> 
> Thanks!
> /John
> 
> John Curran
> President and CEO
> American Registry for Internet Numbers
> 
> Begin forwarded message:
> 
> From: ARIN <info at arin.net>
> Subject: [ARIN-consult] Consultation on the Future of ARIN?s Directory 
> Services
> Date: August 14, 2026 at 11:16:12?AM EDT
> To: <arin-consult at arin.net>
> 
> ARIN is seeking feedback from the community on a proposed road map to
> streamline and consolidate its directory services.
> 
> ARIN currently maintains four directory information protocols:
> Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple
> redundant services that provide the same information creates
> additional administrative and operational overhead to the
> organization. To reduce ARIN?s attack surface, streamline operations
> and lower future operational overhead, ARIN proposes retiring use of
> older protocols in favor of RDAP as our single, standardized directory
> service.

What excessive attack surface is there to operating whois? Yes, it is an 
additional service, but whois, in some form, has been around since 
forever and I am most certain that after so many years, there are well 
hardened whois servers available.
> 
> This transition is an important step toward improving alignment with
> established IETF standards.

Which rfc calls for the decommissioning of whois? If there is one, I 
have not heard about it yet.

> 
> We have already seen this transition in the domain industry with ICANN
> mandating the use of RDAP for directory services and dropping the
> requirement to support Whois. We also expect RDAP clients to become
> increasingly common in OS distributions in the coming years.

The reason why we have redundant services that provides the same 
information is for backwards compatibility. "[T]o become increasingly 
common in OS distributions in the coming years" does not inspire 
confidence. Right now, a whois client comes packaged and installed in 
every major distro. On a fresh install of fedora 44, I can run ``whois 
1.2.3.4`` and it would just work, contra rdap, which requires an 
additional package (perl-rdapper) to be installed. Going back a bit, 
Fedora 42 has no packaged rdap client, unless you trust copr or snap. 
Fedora 42 only came to EOL this year.

These types of breaking changes must not be made until rdap obtains the 
same level of support that whois does.

> 
> ------
> Benefits of Transition to RDAP?
> 
> - Enhanced Directory Services: Future enhancements, such as
> geolocation, will only be implemented in RDAP.?
> - Standardization and Automation: RDAP?s standardized data structure
> will improve automation for clients and provide greater flexibility in
> managing future data changes.?

Great! That's amazing! However, maintaining rdap and whois 
simultaneously are not mutually exclusive.

> - Reduced Technical Overhead:?Removing old and redundant services will
> provide time and cost savings for ARIN.?

What are the expected time and cost savings, and how do they stack up 
against the time and cost of everyone who currently uses whois to 
transition to rdap within the timeframe proposed?

> 
> ------
> Timeline and Retirement Planning
> 
> This consultation seeks community input for the proposed retirement
> timelines below. We are keenly interested in receiving specific input
> on any barriers and/or obstacles these changes may create for
> customers, as well as steps ARIN can take to ensure a smooth
> transition. Note that the retirement plans for each impacted directory
> service will be completed independently, though in some cases work may
> be conducted concurrently.
> 
> ***
> Whois-RWS?Retirement Plan and Timeline
> 
> ARIN currently offers Whois-RWS in two formats: an API and a web
> interface (located at https://whois.arin.net/ui/). Because the API has
> the same functionality between?Whois-RWS and?RDAP, ARIN proposes
> sunsetting the?Whois-RWS API following?a 180-day?customer outreach
> program.?This will include updating the Whois-RWS payloads to include
> a notification to users, as well as a robust communication
> strategy?that includes?announcements, social promotion, and other
> outreach.
> 
> The Whois-RWS web interface will remain available until work is
> completed to ensure parity, providing equivalent query capabilities to
> RDAP. The changeover from Whois-RWS to RDAP will be transparent to end
> users?visiting that URL.?ARIN will inform the community a minimum of
> 30 days before the retirement of the Whois-RWS web interface, noting
> the switch to RDAP will not change the end user experience.
> 
> ***
> RWhois Retirement Plan and Timeline
> 
> When RWhois server use is retired, we will provide organizations with
> a recommendation for an open-source RDAP server implementation. To
> help ease the transition and migration of data, ARIN plans to provide
> a conversion tool for populating that recommended RDAP server with
> existing RWhois data. When the tool is publicly available, ARIN
> proposes a 365-day sunsetting timeline for RWhois. This will allow for
> robust communication and direct outreach to organizations who use
> RWhois and plan to either convert to the RDAP client or discontinue
> their use of local clients and report their reassignment information
> directly to ARIN instead.
> 
> ***
> Whois (Port 43) Retirement Plan?and Timeline
> 
> ARIN understands that Whois (Port 43) carries a high volume of queries
> and will require the longest timeline to retire. We propose a two-year
> sunsetting window, during which ARIN will engage in active outreach to
> users. This will include updates to Whois (Port 43) results during the
> sunsetting period that will contain information about the retirement
> deadline.
> 
> Because Whois (Port 43) has been the historically preferred method of
> querying Internet number resource registration data, it remains
> heavily used by cybersecurity professionals, researchers, law
> enforcement, and many other types of organizations. ARIN will seek to
> engage beyond our community to raise awareness of the planned
> retirement date for Whois (Port 43).
> 
> ------
> After the retirement of the directory service protocols described
> above and listed below, ARIN will only support RDAP as our single,
> standardized directory service.
> 
> - Whois-RWS: on or after 1 July 2027
> - RWhois: dependent on migration tool release date, but no sooner than
> 1 January 2028
> - Whois (Port 43): on or after 1 January 2029
> 
> Throughout the sunsetting process for all services, ARIN will engage
> with our community to ensure customers and users are well-informed
> about the retirement of the described services and ARIN?s transition
> to RDAP as its standard directory service.

With all due respect, ARIN is an internet registry. ARIN is not some 
tech company that must be at the forefront of innovation, moving fast 
and breaking things.
> 
> We look forward to your feedback on the proposed timelines for
> retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you
> consider each service independently, with the understanding that each
> of these services may impact your organization differently.

Hard no on two years for Whois as there is insufficient Rdap support at 
this time.

No comment on Whois-RWS and RWhois.

> 
> Please provide comments to arin-consult at arin.net. You can subscribe to
> this mailing list at
> https://lists.arin.net/mailman/listinfo/arin-consult.
> 
> This consultation will remain open until 5:00 PM ET on 14 September
> 2026. ARIN seeks clear direction through community input, so your
> feedback is important.
> 
> Thank you for your continued support in improving ARIN?s services.
> 
> Regards,
> 
> John Curran
> President and CEO
> ARIN
> 
> ------
> Relevant links:
> - Presentation from ARIN 56:
> https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf
> - IETF Standard for RDAP: https://www.rfc-editor.org/info/std95
> - Guide to RDAP Client Implementations:
> https://rdap.rcode3.com/client_implementations/index.html
> - ARIN RDAP Documentation: 
> https://www.arin.net/resources/registry/whois/rdap/
> _______________________________________________
> ARIN-Consult
> _______________________________________________
> NANOG mailing list
> https://lists.nanog.org/archives/list/nanog at lists.nanog.org/message/VPMTFPBUX5YC6NLFMFNTWFZCDZF5X47O/

From Miles.McCredie at midco.com  Sun Aug 16 12:12:44 2026
From: Miles.McCredie at midco.com (Miles McCredie)
Date: Sun, 16 Aug 2026 16:12:44 +0000
Subject: [ARIN-consult] 
 =?utf-8?q?=5BEXTERNAL=5D_-__Consultation_on_the_F?=
 =?utf-8?q?uture_of_ARIN=E2=80=99s_Directory_Services?=
In-Reply-To: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
References: <B2B1F04F-4BFD-4AAE-92B6-F224CB2D80CE@arin.net>
 <2eb1185c-da57-49c1-9307-39d169cb262b.4ed73c0e-3647-455d-a83f-39a249afb096.5cd9f219-56f7-4646-8a92-0d421ee9ef04@emailsignatures365.codetwo.com>
Message-ID: <CH3PR17MB636207906B7097EA5D463AD59BD82@CH3PR17MB6362.namprd17.prod.outlook.com>

In line with comments others have made about the availability of RDAP clients -

Ubuntu 24.04

 *
Released Apr-2024
 *
Standard security maintenance until May-2029
 *
No packaged RDAP client

Ubuntu 26.04

 *
Released  Apr-2026
 *
openRDAP 0.9.1 package available

Would it be possible to provide some statistics about the various services?
Particular statistics that I'm interested in:

 *
Peak hourly queries to each of the services for the last month
 *
Average hourly queries to each of the services for the last month
 *
Number of whois queries referred  to non-ARIN servers over the last month.

I think that making whois.arin.net a CNAME for search.arin.net would be reasonably safe six months after notification.  My assumption is that these services are used interactively.

How feasible would it be to maintain a whois server that proxies queries to RDAP for several years?
Adding a notification suggesting moving to RDAP to the footer in the output might be a good idea.
It might be worthwhile adding a pointer to this consultation in the short term.

Moving to RDAP will be beneficial overall but I'm concerned that the timelines below are too aggressive.

Good discussion topic for the Miami meeting.




[http://images.midcocomm.com/ES_MidcoLogo.png]

Miles McCredie
Principal Network Engineer II Core IP

Office: 6052755192
Miles.McCredie at midco.com

Midco.com

Let's go beyond.




________________________________
From: ARIN-consult <arin-consult-bounces at arin.net> on behalf of ARIN <info at arin.net>
Sent: Friday, August 14, 2026 10:16 AM
To: arin-consult at arin.net <arin-consult at arin.net>
Subject: [EXTERNAL] - [ARIN-consult] Consultation on the Future of ARIN?s Directory Services

CAUTION: This email originated from outside of MIDCO.
Do not click links or open attachments unless you recognize the sender and know the content is safe.

ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services.

ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN?s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service.

This transition is an important step toward improving alignment with established IETF standards.

We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years.

------
Benefits of Transition to RDAP?

- Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.?
- Standardization and Automation: RDAP?s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.?
- Reduced Technical Overhead:?Removing old and redundant services will provide time and cost savings for ARIN.?

------
Timeline and Retirement Planning

This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently.

***
Whois-RWS?Retirement Plan and Timeline

ARIN currently offers Whois-RWS in two formats: an API and a web interface (located at https://whois.arin.net/ui/)<https://whois.arin.net/ui/>. Because the API has the same functionality between?Whois-RWS and?RDAP, ARIN proposes sunsetting the?Whois-RWS API following?a 180-day?customer outreach program.?This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy?that includes?announcements, social promotion, and other outreach.

The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users?visiting that URL.?ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience.

***
RWhois Retirement Plan and Timeline

When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead.

***
Whois (Port 43) Retirement Plan?and Timeline

ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline.

Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43).

------
After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service.

- Whois-RWS: on or after 1 July 2027
- RWhois: dependent on migration tool release date, but no sooner than 1 January 2028
- Whois (Port 43): on or after 1 January 2029

Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN?s transition to RDAP as its standard directory service.

We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently.

Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult<https://lists.arin.net/mailman/listinfo/arin-consult>.

This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important.

Thank you for your continued support in improving ARIN?s services.

Regards,

John Curran
President and CEO
ARIN

------
Relevant links:
- Presentation from ARIN 56: https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf<https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directoryservices.pdf>
- IETF Standard for RDAP: https://www.rfc-editor.org/info/std95<https://www.rfc-editor.org/info/std95>
- Guide to RDAP Client Implementations: https://rdap.rcode3.com/client_implementations/index.html<https://rdap.rcode3.com/client_implementations/index.html>
- ARIN RDAP Documentation: https://www.arin.net/resources/registry/whois/rdap/<https://www.arin.net/resources/registry/whois/rdap/>


_______________________________________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN Consult Mailing
List (ARIN-consult at arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-consult<https://lists.arin.net/mailman/listinfo/arin-consult> Please contact the ARIN Member Services
Help Desk at info at arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20260816/de2a21b6/attachment-0001.htm>

