[arin-ppml] "Leasing" of space via non-connectivity providers (was: Re: And so it ends... )
On Thu, Feb 03, 2011 at 03:04:36PM -0800, Owen DeLong wrote:
> > 2. Address leasing is not allowed. Must get your addresses from a
> > primary or at least major bandwidth provider. Addresses found to be
> > leased or provided in with a paper-tiger transit arrangement are
> > subject to reclamation by ARIN.
> > Cons: Unenforceable.
> Not entirely true.
> It may be difficult to enforce, but, it is not unenforceable.
For all practical purposes, it is unenforceable. ARIN cannot make a
meaningful distinction between "you buy a T1 and you get a /X" and
"you buy a GRE tunnel and you get a /X".
More to the point, I don't want ARIN to waste time trying to do so. IMO
ARIN should be working to ensure two things:
1. that the barriers to v6 adoption are as low as we can make them, and
2. that the database be as accurate as we can make it.
The market will handle the rest, including the issue of putting unused IPv4
addresses to use. To borrow a phrase from Randy, I don't want a bunch of
ametuer regulators attempting to decide what constitutes "connectivity".
> If that's the best you can do in the con column for this idea, I think
> keeping things this way is vastly superior to your proposed option 1.
Option #1 is reality, today, and let's not pretend otherwise.
> > 3. Any multihomed registrant using an ARIN AS number and SWIPed for at
> > least one year with a /24 or larger is entitled to convert the
> > registration to an ARIN direct assignment upon filing the proper
> > paperwork. Refusing SWIP or assigning addresses out of region is
> > grounds for reclamation.
> I have to admit this third option is interesting and has some appeal.
Agreed, although I would remove the threat of reclamation because I don't
think this is something ARIN needs to regulate. The commercial agreements
between the parties should spell out the expected behavior, including
whether or not the addresses may be transferred to the lessee, and under
Let's do what we can to make sure that the database is accurate, and focus
our efforts on v6 going forward.