[arin-ppml] ARIN-prop-175 Delete Section 8.2

[David Farmer]

Harrison,

I see one problem, 8.3 explicitly does not include IPv6 transfers. The 
current policy also doesn't include ASNs either, but when ARIN-2012-3 is 
implemented, no later than July 31 according to the web site, that 
shouldn't be a problem.  However, the proposal that initiated 
ARIN-2012-3 included IPv6 and there was significant opposition to 
including IPv6 in 8.3 transfers.  So without some additional 
modification of 8.3 this policy would have the effect on eliminating 
IPv6 transfers completely.

Also, ARIN-2011-1 and ARIN-2012-1 should be implemented in a similar 
time frame as ARIN-2012-3 including interRIR transfers and significant 
changes to 8.3 and the creation of 8.4.

A couple suggestion first, rather than renumber 8.3 to 8.2 could I 
suggest you just delete 8.2 and we can put "[Section Number Retired]" in 
its place.  Please consider if the changes to section 8.3 and the 
addition of 8.4 with the pending implementation of the policies above 
change your assessment of the situation.

While I think you have a valid point, but I'm not sure liberalizing 
transfers for IPv6 will be a idea that gets consensus.  Are there 
changes to 8.2 that would clarify when it should be used verses 8.3 that 
could accomplish the stated goal?

On 6/20/12 08:12 CDT, ARIN wrote:

> ARIN-prop-175 Delete Section 8.2
>
> Proposal Originator: Harrison Grundy
>
> Proposal Version: 1
>
> Date: 20 June 2012
>
> Proposal Type: Modify
>
> Policy Term: Permanent
>
> Policy Statement:
>
> Delete section 8.2, and renumber section 8.3 to 8.2,
>
> Add language to the new Section 8.2 (Transfers to Specified Recipients):
>
> "ARIN will provisionally update the registry to reflect the transfer
> request initiated by the resource holder pending ARIN's approval or
> rejection of the transfer. If the transfer is rejected, ARIN will update
> the registry to reflect the original resource holder."
>
> Rationale:
>
> Transfers due to mergers and acquisitions should follow the same process
> as any directed transfer. Current language in the NRPM is silent on the
> status of those resources as it relates to RSAs, while requiring that
> the number resources of the merged organisations comply with ARIN's
> policies. This situation is needlessly confusing, and serves only to
> create a legal grey area for these resources.
>
> There is also no clear delineation on when an entity may elect to
> perform an 8.2 transfer over an 8.3 transfer, beyond the requirement
> that "the new entity has acquired assets that used the transferred
> resources from the current registrant". Purchasing a single router from
> an entity should not magically transform what is otherwise a transfer to
> a specified recipient into a special transfer that does not carry the
> requirements of an 8.3 transfer. The text of 8.2 would also appear to
> preclude transferring resources that are not currently in use.
>
> This policy proposal serves to homogenise transfer requirements so that
> there is one simple method of transfer, regardless of the business
> circumstances surrounding that transaction.
>
> By immediately updating the registry upon receiving a request,
> renumbering pain as part of M&A transactions will only occur where the
> resources will not be used for their already approved purpose.
>
> Timetable for implementation: Immediate
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota	
2218 University Ave SE	    Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================