[arin-ppml] REVISED: Draft Policy ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy

[Steve Noble]

TL;DR I don't agree with forcing people under RSAs especially the
latest one just "because".

I've been on the other side of the "which version of the RSA"
discussion.  ARIN refuses to allow you to re-sign or sign a copy of
the RSA that applied at the time of the registration/transfer/action
unless it is the current RSA.  All ARIN really has to do is refuse to
accept the RSA.  ARIN is a monopoly, if they do not accept a document
from you, there is not much you can do.

Remember, because of ARINs own mistake (and I very much do thank John
for researching and correcting it) I was caught in a circle where I
could not update a ASN that I had the right to update, that I paid for
every year.  Had John not found the issue, there would be over 2000
other organizations caught in the same limbo.

On Mon, Dec 10, 2012 at 7:42 PM, Gary Buhrmaster
<gary.buhrmaster at gmail.com> wrote:
> On Mon, Dec 10, 2012 at 3:25 PM, Scott Leibrand <scottleibrand at gmail.com> wrote:
>> No objections here.  As far as I can tell the only substantive change (other
>> than codifying existing practice) is the requirement that "The new entity
>> must sign an RSA covering all transferred resources."  That seems like a
>> (minor) improvement in policy.
>
> Is there any concern from the community regarding the word "an" in
>
>    ... must sign *an* RSA ...
>
> While any RSA is better than none, I seem to recall a similar
> wording was interpreted by ARIN in a way that caused some
> members of the community some consternation (i.e. it allowed
> a Legacy RSA).
>
> Gary
> _______________________________________________
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.