[arin-ppml] 2016-3 Revisited

Kevin Blumberg kevinb at thewire.ca
Fri Feb 3 10:56:11 EST 2017


I support this policy as revised.

I believe also that statistics previously showed that a large majority of requests were /16 and smaller.

Can you please confirm the following?

1) The policy would remove the requirement for documentation of future use.
2) The policy would not assist organizations that are consistently doubling more than every 6 months.
3) The policy would not assist organizations that require more than a /16.
4) The policy would allow an organization with larger holdings (ie /12) to get a /16 every 6 months.
5) The policy would not limit other transfers in section 8.5.


Kevin Blumberg

-----Original Message-----
From: ARIN-PPML [mailto:arin-ppml-bounces at arin.net] On Behalf Of David R Huberman
Sent: Friday, February 3, 2017 10:19 AM
To: arin-ppml at arin.net
Subject: Re: [arin-ppml] 2016-3 Revisited

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 
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.

More information about the ARIN-PPML mailing list