[arin-ppml] Request for Feedback: Recommended Draft Policy ARIN-2025-2 Clarify 8.5.1 Registration Services Agreement

[Mohibul Mahmud]

Hi John,

Thanks — that explanation is clear and really helpful.

My understanding is that a “current RSA” simply means the organization’s
legal status hasn’t changed since signing, regardless of which version of
the RSA they have on file.

It might be valuable to add that clarification in the NRPM or ARIN’s RSA
FAQ to reduce confusion for organizations doing transfers and avoid
unnecessary support tickets.

Also, are there any circumstances where ARIN might still ask an
organization to sign a newer RSA even without a legal status change — for
example, due to policy updates?

Best regards,
Mohibul Mahmud



On Sat, Sep 27, 2025 at 1:51 PM John Sweeting <jsweeting at arin.net> wrote:

> Hello,
>
>
>
> As far as “current RSA” goes, ARIN considers an RSA current if there is no
> change to an organization’s legal status from the time they signed the
> agreement. It does not matter what version it is. The organization,
> actually any organization, can request to sign the most recent version of
> the agreement at any time.
>
>
>
> Thanks,
>
> John S.
>
>
>
>
>
> *From: *ARIN-PPML <arin-ppml-bounces at arin.net> on behalf of Mohibul
> Mahmud <mohibul.mahmud at gmail.com>
> *Date: *Wednesday, September 24, 2025 at 8:50 PM
> *To: *Reese, Gus <gReese at cogentco.com>
> *Cc: *arin-ppml at arin.net <arin-ppml at arin.net>
> *Subject: *Re: [arin-ppml] Request for Feedback: Recommended Draft Policy
> ARIN-2025-2 Clarify 8.5.1 Registration Services Agreement
>
> Hi Gus and Kendrick,
>
>
>
> Thanks for sharing this proposed update and inviting feedback. I’m
> following the discussion and will keep an eye on how the policy evolves.
>
>
>
> It might also be helpful if ARIN could clarify what “current RSA” means in
> practice — so organizations know whether their existing agreement still
> counts.
>
>
>
> Best regards,
>
> Mohibul Mahmud
>
>
>
>
>
>
>
> On Wed, Sep 24, 2025, 8:33 p.m. Reese, Gus <gReese at cogentco.com> wrote:
>
> Hello PPML!
>
>
>
> ARIN 56 In person meeting is just a few short weeks away in my hometown of
> Arlington Texas.  Prior to the meeting I would like to solicit any feedback
> regarding Recommended Draft Policy ARIN-2025-2.
>
>
>
> Here is a refresher of the changes to the policy statement in 8.5.1:
>
>
>
> Policy statement:
>
>
>
> Remove (within the last two versions) from 8.5.1 to state: The receiving
> entity must sign an RSA covering all resources to be transferred unless
> that entity has a current RSA on file per ARIN business practices.
>
>
>
> For reference here is the existing text in the NRPM:
>
>
>
> 8.5.1. Registration Services Agreement
>
> The receiving entity must sign an RSA covering all resources to be
> transferred unless that entity has a current (within the last two versions)
> RSA on file.
>
>
>
> Feedback from the community from March 2025 and after this was presented
> at ARIN 55 was positive.
>
>
>
> As always a big thank you to the PPML community!
>
>
>
> Gus Reese & Kendrick Knowles
>
> ARIN Advisory Council
>
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20250928/897fc432/attachment.htm>