[arin-ppml] LRSA requirement for resources being transferred (Was: ARIN-prop-136 Services Opt-out Allowed for Unaffiliated Address Blocks

Owen DeLong owen at delong.com
Fri Feb 25 13:12:37 EST 2011

On Feb 25, 2011, at 9:46 AM, Matthew Kaufman wrote:

> On 2/24/2011 10:35 PM, Bill Woodcock wrote:
>> Hash: SHA1
>> On Feb 24, 2011, at 9:19 PM, Matthew Kaufman wrote:
>>> So the issue is that if ARIN believes that legacy non-LRSA resources are not transferable and yet the transferer and the transferee believe they are, we have a problem.
>> Then there's no problem, because there's no resource that's not transferrable.
> I meant to say "if ARIN believes that legacy non-LRSA resources are not transferable *to another party who hasn't signed the RSA*, and yet the trasferer and the transferee believe they are"
In such case, the transferor and transferee are both mistaken.

>> Qualifications attach to the recipient of a resource, not to the donor or the resource itself.
> And how would you go about enforcing that in the case where, because of ARIN policy, neither party bothers to notify ARIN?
Once ARIN becomes aware that the resources are no longer being utilized by the
resource holder of record, they can be considered abandoned and made available
for registration to an RSA-contracted recipient. Beyond that, there is no real need
for enforcement, per se.


More information about the ARIN-PPML mailing list