[arin-ppml] Draft policy ARIN-2013-1 Section 8.4 Inter-RIR transfers of ASNs
owen at delong.com
Wed Mar 20 15:37:49 EDT 2013
I will point out that that there is still ongoing discussion about the "of the same resource" clause.
Personally, I favor restricting transfers based on having received any resource rather than having to track them separately.,
Sent from my iPad
On Mar 20, 2013, at 1:33 PM, Scott Leibrand <scottleibrand at gmail.com> wrote:
> At our last meeting, the ARIN AC accepted ARIN-prop-183 Section 8.4 Transfer enhancement as a draft policy. It has been given Draft Policy number ARIN-2013-1, and retitled as "Section 8.4 Inter-RIR transfers of ASNs". The revision currently under discussion is below.
> If you haven't expressed an opinion yet, or if you have any updated feedback based on the updated text, please speak up. A version of this policy will be up for discussion in Barbados, either as a Draft policy or a Recommended Draft Policy (depending on the outcome of tomorrow's AC meeting).
> Policy Proposal Name: Section 8.4 Inter-RIR transfers of ASNs
> Proposal Originator: Martin Hannigan
> Proposal Version: 1.2
> Date: 19 Mar 2013
> Proposal type: MODIFY
> Policy term: PERMANENT
> Policy statement:
> Modify the following text in Section 8.4
> Add "or ASNs to be transferred, as" to the first bullet point under Conditions on source of the transfer, so that it reads:
> "The source entity must be the current rights holder of the IPv4 address resources or ASNs to be transferred, as recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources."
> Change "IPv4 number resources" to "IPv4 number resources or ASNs", so that the fourth bullet point reads:
> "Source entities within the ARIN region must not have received a transfer, allocation, or assignment of that same resource type (IPv4 number resource or ASN) from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include M&A transfers."
> We already allow transfer of ASNs within the ARIN region. The change will accomplish two things. First there is inconsistent language in 8.4 eg "IPv4 Address" v. "IPv4 Number Resource(s)" and second, it will allow the transfer of ASNs between RIRs through 8.4 and using the standards we have already established for IPv4 transfers. For many of the same reasons that we allow transfer of IP addresses, we should allow transfers of ASNs and to help insure that idle resources are both recovered and utilized efficiently and where needed, and to allow the registry to be updated to reflect who is actually using which ASNs.
> Version 1.1 changes the title, clarifies the resulting policy language slightly, and explicitly includes the resulting policy language in the policy statement.
> Version 1.2 clarifies that the 12-month restriction on having received a transfer, allocation, or assignment applies separately to IPv4 number resources and ASNs.
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML