Send ARIN-PPML mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."
Today's Topics:
1. NRPM 2013.2 =?windows-874?Q?=96_New_Policies_Implemented?= (ARIN)
2. Draft policy ARIN-2013-1 Section 8.4 Inter-RIR transfers of
ASNs (Scott Leibrand)
3. Re: Draft policy ARIN-2013-1 Section 8.4 Inter-RIR transfers
of ASNs (Owen DeLong)
4. Re: Draft policy ARIN-2013-1 Section 8.4 Inter-RIR transfers
of ASNs (David Farmer)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Mar 2013 12:13:33 -0400
From: ARIN <[email protected]>
To: [email protected]
Subject: [arin-ppml] NRPM 2013.2
=?windows-874?Q?=96_New_Policies_Implemented?=
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-874; format=flowed
On 15 February 2013 the ARIN Board of Trustees adopted the following
policies:
ARIN-2012-6: Revising Section 4.4 C/I Reserved Pool Size
ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy
A new version of the ARIN Number Resource Policy Manual (NRPM) has been
published to the ARIN website. NRPM version 2013.2 is effective 20 March
2013 and supersedes the previous version. NRPM 2013.2 contains the
implementation of ARIN-2012-6 and ARIN-2012-8.
The NRPM is available at: https://www.arin.net/policy/nrpm.html
Board minutes are available at:
https://www.arin.net/about_us/bot/index.html
Draft policies and proposals are available at:
https://www.arin.net/policy/proposals/
The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
------------------------------
Message: 2
Date: Wed, 20 Mar 2013 11:33:53 -0700
From: Scott Leibrand <[email protected]>
To: ARIN-PPML List <[email protected]>
Subject: [arin-ppml] Draft policy ARIN-2013-1 Section 8.4 Inter-RIR
transfers of ASNs
Message-ID:
<CAGkMwz6CiiSJF7zL23PtTh8Mk=vSGJnbyHAX7X=jdwn-25z...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
PPML,
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).
Thanks,
Scott
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."
Rationale:
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130320/82987a1f/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 20 Mar 2013 14:37:49 -0500
From: Owen DeLong <[email protected]>
To: Scott Leibrand <[email protected]>
Cc: ARIN-PPML List <[email protected]>
Subject: Re: [arin-ppml] Draft policy ARIN-2013-1 Section 8.4
Inter-RIR transfers of ASNs
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
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.,
Owen
Sent from my iPad
On Mar 20, 2013, at 1:33 PM, Scott Leibrand <[email protected]> wrote:
> PPML,
>
> 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).
>
> Thanks,
> Scott
>
> 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."
>
> Rationale:
> 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.
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130320/d1aee11c/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 20 Mar 2013 17:19:12 -0500
From: David Farmer <[email protected]>
To: ARIN PPML <[email protected]>
Subject: Re: [arin-ppml] Draft policy ARIN-2013-1 Section 8.4
Inter-RIR transfers of ASNs
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Ok, explain to me how it huts the community if I have an extra ASN and
justified need for IP addresses and my friend has justified need for an
ASN and extra IP addresses, and we want to trade. This sound like a
match made in heaven, as contrived as it is. But, as I described it no
money changes hands and resources get used more efficiently, sounds like
good stewardship to me. But you seem to want to stand in the way of it.
Because unless the two transactions are atomic and linked the first
will go through and the second will be blocked by the language you support.
As long as justified operational need is being fulfilled, why do we the
community need to stick our nose in things. There our those that
believe maintaining justified operational need, is sticking the
community's nose to for into things already.
I support the prohibition from being the source of resources after
having and received resources (of the same type) within the last 12
months to discourage gaming the operational need requirement. But, your
operational need for one type of resources has nothing with your
operational need for other types of resources.
If someone received an IPv6 allocation, successfully deployed it, and
then was somehow able to reduce their need for IPv4; your interpretation
would prevent them from transferring their no longer needed IPv4
resources to someone else.
Owen, your wrong.
On 3/20/13 14:37 , Owen DeLong wrote:
> 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.,
>
> Owen
>
>
> Sent from my iPad
>
> On Mar 20, 2013, at 1:33 PM, Scott Leibrand <[email protected]
> <mailto:[email protected]>> wrote:
>
>> PPML,
>>
>> 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).
>>
>> Thanks,
>> Scott
>>
>> 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."
>>
>>
>> Rationale:
>>
>> 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.
>>
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected]
>> <mailto:[email protected]>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact [email protected] <mailto:[email protected]> if you experience
>> any issues.
>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>
--
================================================
David Farmer Email: [email protected]
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 1-612-626-0815
Minneapolis, MN 55414-3029 Cell: 1-612-812-9952
================================================
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 93, Issue 8
****************************************
