[arin-ppml] 2016-3 Revisited

[Jason Schiller]

David,

TL;DR
The policy says "one or more transfers up to the total size of their
current ARIN IPv4 address holdings"

My read suggests you can do one or many transfers within a two year window
up to the amount approved.  There is no need to re-demonstrate utilization
within the two year window so long as total specified transfer is less than
a /16 or double your current holdings.

Can you address the question of if "demonstrated growth of IPv4 utilization
of at least half of the amount of specified transfers" is acceptable to you
as the sole anti-abuse provision, or if it is acceptable to you in addition
to the 6 month restriction.

--

An organization has a /19.
It has growing products, and wants another /19 for its 1 or 2 year need.
It wants to avail itself of the new language.
It show 80%+ utilization of its existing /19.
It then gets blanket pre-approval for one or more transfers which total to
a /19 over then next 2 years.

Then it transfers one /20, then the other..

OR

It closes the deal with Buyer A first, and transfers at ARIN using the
proposed language.
That process yields
1. pre-authorization for a /19 equalivent of specified transfers
2. approval for the /20 which is deducted from the /19 pre-athorization


Policy Text
---------------

8.5.7 Alternative Additional IPv4 Address Block Criteria
In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4
address blocks by demonstrating 80% utilization of their currently
allocated space. If they do so, they qualify to receive one or more
transfers up to the total size of their current ARIN IPv4 address holdings,
with a maximum size of /16.

An organization may only qualify under 8.5.7 once every 6 months, unless
they can also demonstrate growth of IPv4 utilization of at least half of
the amount of specified transfers since the previous transfer
pre-authorization or approval.


Some extra words in policy text for more clarity
--------------------------------------------------------------

In lieu of 8.5.5 and 8.5.6, organizations may  qualify to get a new two
year specified transfer pre-authorization under 8.5.7 once every 6 months,
unless they can also demonstrate growth of IPv4 utilization of at least
half of the amount of specified transfers since the previous transfer
pre-authorization or approval.

An organization may only qualify to get a new two year specified transfer
pre-authorization  under 8.5.7 once every 6 months, unless they can also
demonstrate growth of IPv4 utilization of at least half of the amount of
specified transfers since the previous transfer pre-authorization or
approval.



__Jason


On Fri, Feb 3, 2017 at 10:19 AM, David R Huberman <daveid at panix.com> wrote:

>
> I thought of a possible problem with the anti-abuse language -- all
> versions of it.  Let me talk it out.
>
> An organization has a /19.
> It has growing products, and wants another /19 for its 1 or 2 year need.
> It wants to avail itself of the new language.
> It is able to buy a /20 from Buyer A, and a /20 from Buyer B.
>
> It closes the deal with Buyer A first, and transfers at ARIN using the
> proposed language.
>
> How does it use any version we've discussed (Jason's various proposals,
> the current text, etc) to transfer the space it buys from Buyer B?
>
>
> (In all discussion, yes, you can always use the other sections of 8.5, but
> let's stick to the spirit of this policy language, which is meant to help
> smaller and mid-size networks double their holdings without needs testing.)
>
> _______________________________________________
> 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.
>



-- 
_______________________________________________________
Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20170203/1f1b2d79/attachment.htm>