[arin-ppml] [Revised] DRAFT POLICY ARIN-2014-9: RESOLVE CONFLICT BETWEEN RSA AND 8.2 UTILIZATION REQUIREMENTS
jeffrey.lyon at blacklotus.net
Thu Jun 26 16:25:38 EDT 2014
Notwithstanding my support for at least partially removing needs
testing, addresses obtained via M&A should certainly be
sold/transferred or returned.
On Thu, Jun 26, 2014 at 3:31 PM, Scott Leibrand <scottleibrand at gmail.com> wrote:
> On Thu, Jun 26, 2014 at 11:52 AM, Andrew Dul <andrew.dul at quark.net> wrote:
>> On 6/2/2014 10:34 AM, Heather Schiller wrote:
>> > At the PPM in April, there was support for leaving this paragraph in
>> > the NRPM, but removing the words 'aggregate' and 'return', resulting
>> > in the text below. The AC encourages feedback on this proposed change.
>> > Thanks,
>> > --Heather
>> > Draft Policy ARIN-2014-9
>> > Resolve Conflict Between RSA and 8.2 Utilization Requirements
>> > Remove the words "aggregate" and "reclaim" from 8.2, so it reads:
>> > "In the event that number resources of the combined organizations are
>> > no longer justified under ARIN policy at the time ARIN becomes aware
>> > of the transaction, through a transfer request or otherwise, ARIN will
>> > work with the resource holder(s) to return or transfer resources as
>> > needed to restore compliance via the processes outlined in current
>> > ARIN policy."
>> This new text removes the threat of reclamation from the policy manual
>> as the current RSA (section 6) prohibits ARIN from reclaiming addresses
>> for lack of use, but this rewrite does not make it clear that an
>> organization can retain their addresses for future use. This change
>> makes it clear that resources or parts of resources will not become
>> orphaned blocks due to a merger or acquisition. I believe this change
>> would promote registry accuracy as it should allow organizations to
>> update all their records to show the new holder and user of the
>> resources regardless of utilization.
>> May I suggest the following rewrite to clarify that an organization can
>> retain their addresses through a transfer.
> While that was a goal of the original proposal (which would've eliminated
> this section entirely) I did not get the sense that the community supported
> going that far. Rather, the consensus seemed to be that if an organization
> acquires addresses they don't currently need via M&A transfer, they should
> work in good faith to find a buyer for them and transfer them under 8.3 or
> 8.4. If they are unwilling to do so, they will remain in violation of this
> policy language and be unable to acquire any additional addresses, but ARIN
> will not attempt to reclaim the addresses.
>> ...ARIN will notify the resource holder(s) that they may return or
>> transfer resources as needed to restore compliance via the processes
>> outlined in current ARIN policy or retain their resources for future use
>> or later transfer/return.
> If there is community support for allowing organizations to retain unneeded
> resources obtained through M&A for future use, please speak up. I didn't
> hear much support for that position expressed at the meeting.
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
Jeffrey A. Lyon, CISSP-ISSMP
Fellow, Black Lotus Communications
mobile: (757) 304-0668 | gtalk: jeffrey.lyon at gmail.com | skype: blacklotus.net
More information about the ARIN-PPML