[arin-ppml] ARIN forcing everyone to sign the new RSA?

[Sandra Murphy]

On Oct 29, 2015, at 9:59 PM, John Curran <jcurran at arin.net> wrote:

> On Oct 29, 2015, at 6:55 PM, David Huberman <David.Huberman at microsoft.com> wrote:
>> 
>> 
> 
> David -
> 
>  ARIN issues number resources under the current version of the RSA,
>  so parties requesting new resources should expect to sign the most
>  current version.   The changes from RSA version 11 to 12 are based on
>  changes requested by the community, and I would highly recommend that
>  everyone take the opportunity to review them (even if not requesting any
>  additional resources) as the terms may be more suitable to one's needs
>  than those in your present registration services agreement.
> 

This brings to mind some text I saw on an ARIN page somewhere that explained the need to add “-Z” to organization IDs when the organization signed an LRSA: in the ARIN database, only one RSA could be associated with an organization.  So if the organization signed the LRSA (for some of their resources, by implication), a new Org-ID had to be created to tie to the new agreement.

Not precisely recalled and I can no longer find that text on the ARIN site.

Was that ever true?  Is it still true?  If an organization has signed an agreement in the past and wants new (IPv6) resources and wants to keep the existing agreement for the existing resources, will it be necessary to create a new Org-ID for those new resources because they are under a new, different agreement?

—Sandy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20151102/5ab8449a/attachment.sig>