My opinion is: Legacy holders can keep what they have until doomsday, and where these holders decide to transfer in any way method shape or form, they are subject to RSA. I feel that it does not seem fair on the part of the rest of the community that legacy holders legitimize (not sure that's the correct word) their holding with the use of a special instrument (LRSA) and at the same time retain the ability to profit from that which is technically not property/....I suspect they were given these resources in the spirit of R&D at the time.<div>
<br></div><div>rd<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br>
On Mon, May 9, 2011 at 9:20 PM, Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<br>
> RSA, I could support it. I do not support granting LRSA to transfer<br>
> recipients. The LRSA provides special benefits that are intended to<br>
<br>
I agree. The LRSA is an agreement between ARIN and a legacy resource holder.<br>
A transfer recipient is not a legacy resource holder; a transfer<br>
recipient is a new<br>
resource holder.<br>
<br>
Also, there is no reason ARIN should adopt a more lax policy in anticipation<br>
that a resource holder will ignore their obligations in attempting to make<br>
'undocumented' transfers not allowed by policy.<br>
<br>
Legitimizing non-needs-based transfers would encourage them.<br>
It is questionable whether black market transfers would even be<br>
attempted, otherwise, by any legacy holders with significant number<br>
resources assigned to their network.<br>
<br>
> Owen<br>
--<br>
-JH<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 9 May 2011 23:36:56 -0500<br>
From: Jimmy Hess <<a href="mailto:mysidia@gmail.com">mysidia@gmail.com</a>><br>
To: Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>><br>
Cc: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] transfer conditions<br>
Message-ID: <<a href="mailto:BANLkTimdMWZFSCmUH6fWLgcKcsUJCrdoDA@mail.gmail.com">BANLkTimdMWZFSCmUH6fWLgcKcsUJCrdoDA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Mon, May 9, 2011 at 8:09 PM, Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>> wrote:<br>
> On May 9, 2011, at 3:49 PM, Ted Mittelstaedt wrote:<br>
> All of the versions of the LRSA, and all of the modifications of "The RSA" are "an RSA"<br>
>> I wouldn't like it, but obviously ARIN does not like forcing the recieving party to sign an RSA,<br>
> No, they're fine with "an RSA", just not "The RSA and Only The RSA"<br>
> Matthew Kaufman<br>
<br>
When I say and see "RSA" in the 8.3 transfer policy; I take that to mean<br>
the unmodified, standard RSA signed for new allocations by ARIN.<br>
And "LRSA" to be the special modified RSA for legacy holders.<br>
<br>
Do you suggest ARIN staff have taken a liberty to not implement it in<br>
that manner?<br>
<br>
I expect transfer recipients to be required to sign the RSA equivalent to<br>
the standard RSA signed by receivers of new allocations.<br>
<br>
That is, a RSA that does not provide the transfer recipient any benefits,<br>
more rights, provide any fewer restrictions on the transfer recipient, than<br>
the new allocation RSA, and does not restrict ARIN or cause ARIN to surrender<br>
any rights not surrendered when the allocation recipient enteres into<br>
a standard RSA.<br>
<br>
--<br>
-JH<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 9 May 2011 21:39:30 -0700<br>
From: Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>><br>
To: Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>><br>
Cc: Warren Johnson <<a href="mailto:warren@wholesaleinternet.net">warren@wholesaleinternet.net</a>>, <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] ARIN-prop-146 Clarify Justified Need for<br>
Transfers<br>
Message-ID: <<a href="mailto:A9D651E2-9377-434F-93D1-133E5F1CC5EE@matthew.at">A9D651E2-9377-434F-93D1-133E5F1CC5EE@matthew.at</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
On May 9, 2011, at 7:09 PM, Owen DeLong wrote:<br>
<br>
> Actually, not so much... The resulting organization would still be subject<br>
> to a section 12 audit and appropriate reclamation of the unused space.<br>
><br>
<br>
Given that no section 12 audit resulted in a significant return from the HP + DEC/Compaq merger, I will simply assume that you're just wrong about this.<br>
<br>
Matthew Kaufman<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 9 May 2011 21:50:23 -0700<br>
From: Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>><br>
To: Jimmy Hess <<a href="mailto:mysidia@gmail.com">mysidia@gmail.com</a>><br>
Cc: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] transfer conditions<br>
Message-ID: <<a href="mailto:1B32A1B5-0FFC-4C58-93F3-9C984E42F5AB@matthew.at">1B32A1B5-0FFC-4C58-93F3-9C984E42F5AB@matthew.at</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
On May 9, 2011, at 9:36 PM, Jimmy Hess wrote:<br>
<br>
> On Mon, May 9, 2011 at 8:09 PM, Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>> wrote:<br>
>> On May 9, 2011, at 3:49 PM, Ted Mittelstaedt wrote:<br>
>> All of the versions of the LRSA, and all of the modifications of "The RSA" are "an RSA"<br>
>>> I wouldn't like it, but obviously ARIN does not like forcing the recieving party to sign an RSA,<br>
>> No, they're fine with "an RSA", just not "The RSA and Only The RSA"<br>
>> Matthew Kaufman<br>
><br>
> When I say and see "RSA" in the 8.3 transfer policy; I take that to mean<br>
> the unmodified, standard RSA signed for new allocations by ARIN.<br>
> And "LRSA" to be the special modified RSA for legacy holders.<br>
<br>
Well, since "RSA" is not currently defined in the NRPM anywhere, it could mean anything they want, I suppose.<br>
<br>
Note that even the "normal RSA" gets modified for certain entities, and the LRSA is also often "customized"<br>
<br>
><br>
> Do you suggest ARIN staff have taken a liberty to not implement it in<br>
> that manner?<br>
><br>
<br>
That is the only way that the public statements made regarding the Nortel/Microsoft transfer make any sense. There's evidence that "a LRSA" was signed and evidence that "policy 8.3 was followed".<br>
<br>
> I expect transfer recipients to be required to sign the RSA equivalent to<br>
> the standard RSA signed by receivers of new allocations.<br>
><br>
<br>
Well, that isn't what has happened, at least once. I have a policy proposal that clarifies what might happen... please comment on it (I'm guessing you would NOT support it, given your position about which RSA should be required)<br>
<br>
Matthew Kaufman<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 10 May 2011 00:10:30 -0500<br>
From: Jimmy Hess <<a href="mailto:mysidia@gmail.com">mysidia@gmail.com</a>><br>
To: Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>><br>
Cc: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] transfer conditions<br>
Message-ID: <BANLkTi=6k_Xkoh-OqpR=<a href="mailto:jhiZ3hOz%2BqEqpw@mail.gmail.com">jhiZ3hOz+qEqpw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Mon, May 9, 2011 at 11:50 PM, Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>> wrote:<br>
> On May 9, 2011, at 9:36 PM, Jimmy Hess wrote:<br>
>> On Mon, May 9, 2011 at 8:09 PM, Matthew Kaufman <<a href="mailto:matthew@matthew.at">matthew@matthew.at</a>> wrote:<br>
<br>
> Note that even the "normal RSA" gets modified for certain entities, and the LRSA is also often "customized"<br>
><br>
In what way does the RSA get "modified" for certain entities?<br>
Do we have examples?<br>
<br>
I would suggest at least the requirement that the RSA used<br>
match a RSA published in the "Agreements" section of ARIN's website.<br>
<br>
Some organizations getting private RSAs of their choosing would be inconsistent<br>
with ARIN treating all organizations that receive service impartially.<br>
<br>
'Special' organizations should not have have rights, waiver of<br>
community developed<br>
policies, or other privileges granted to them by ARIN, not afforded to others,<br>
just because they are X, and "X is special".<br>
<br>
--<br>
-JH<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
End of ARIN-PPML Digest, Vol 71, Issue 104<br>
******************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br><img src="http://api.ning.com/files/60Dc*7fMSnOD5inYWvnElhieb2y*e2O798iHVa48vgYOJUmz33g1MSmWAGQs0M2C7g4LXqAu0KvJ0c99k3kSouZfig33AnNo/emaillogo.jpg" height="61" width="58"><br>
<div>Rudi Daniel<div><i><a href="http://www.facebook.com/pages/Kingstown-Saint-Vincent-and-the-Grenadines/DanielCharles/153611257984774" target="_blank">danielcharles consulting</a><br></i><b><span style="font-size:large"><font color="#006600"><a href="http://www.facebook.com/pages/Kingstown-Saint-Vincent-and-the-Grenadines/DanielCharles/153611257984774" target="_blank">1-784 498 8277</a></font></span></b></div>
<div><font color="#006600"><span style="font-size:large"><b><br></b></span></font><div><span style="font-size:large"><br></span></div></div></div><br>
</div>