(Answering my own questions a little bit, even though that's a tad gauche.)

I see the ARIN website has some text I haven't seen before.  At:
https://www.arin.net/resources/agreements/index.html

. under "Registration Services Agreement", it says:

"Both existing and newly approved customers must sign and return the current 
version of the RSA for each resource request."

And thinking about it, I realize we had Version 11 for 3.5 years.  The version 
I have a copy of says April 2012.  So it's been a while. And Version 12 was 
just published this month.

So that answers most of my questions.  I'd still like clear rules for when, and 
when not, an updated RSA is required.  The RSA is still one-sided and overly 
aggressive, so it's not easy to get it signed, much less signed when it's 
already been signed.

Thanks!
David

David R Huberman
Principal, Global IP Addressing
Microsoft Corporation

From: [email protected] [mailto:[email protected]] On Behalf 
Of David Huberman
Sent: Thursday, October 29, 2015 3:49 PM
To: [email protected]
Subject: [arin-ppml] ARIN forcing everyone to sign the new RSA?

Hello,

I was very surprised to learn today that an established Org at ARIN, with an 
RSA signed in calendar year 2015, is being forced to sign a new version 12 RSA 
in order to obtain services on additional IP addresses.

ARIN: what is the justification for forcing all registrants* into Version 12? 

Also, what are the actual rules and where are they published?  Do I have to 
sign a new RSA any time I get a new AS number? What if I justify an additional 
IPv6 block? How about if I want to participate in RPKI? Or IRR? What if I clear 
the waiting list? 

Thanks,
David

David R Huberman
Principal, Global IP Addressing
Microsoft Corporation

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to