[arin-ppml] transfer conditions
kkargel at polartel.com
Wed May 11 12:46:39 EDT 2011
> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of Jimmy Hess
> Sent: Tuesday, May 10, 2011 12:11 AM
> To: Matthew Kaufman
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] transfer conditions
> On Mon, May 9, 2011 at 11:50 PM, Matthew Kaufman <matthew at matthew.at>
> > On May 9, 2011, at 9:36 PM, Jimmy Hess wrote:
> >> On Mon, May 9, 2011 at 8:09 PM, Matthew Kaufman <matthew at matthew.at>
> > Note that even the "normal RSA" gets modified for certain entities, and
> the LRSA is also often "customized"
> In what way does the RSA get "modified" for certain entities?
> Do we have examples?
> I would suggest at least the requirement that the RSA used
> match a RSA published in the "Agreements" section of ARIN's website.
> Some organizations getting private RSAs of their choosing would be
> with ARIN treating all organizations that receive service impartially.
> 'Special' organizations should not have have rights, waiver of
> community developed
> policies, or other privileges granted to them by ARIN, not afforded to
> just because they are X, and "X is special".
I would tend to argue the other side of this coin. It is impossible to write a boilerplate contract for anything that will cover all situations and circumstances. Most contracts will have caveats and addenda to fine tune the contract to best serve the interests of the parties involved. NDA's that are more restrictive than standard might be one example.
I suspect that if we wrote an RSA with enough clauses to cover all possible circumstances it would require a rather large hard drive to house it and would take a team of logic PHD's to understand it.
I completely believe that ARIN staff works for the best interest of the community and with all due diligence. I fully support ARIN staff having the authority to modify an RSA to fit special circumstances.
More information about the ARIN-PPML