[address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)

> On 14 Apr 2016, at 15:34, Aled Morris <aled.w.morris at googlemail.com> wrote:
> 
> I agree with the proposal because it makes it possible for recent entrants into the market to grow.

I strongly disagree with the proposal because it will encourage LIRs to fritter away scarce IPv4 resources which need to be conserved so there will be at least some IPv4 space available for new entrants 10? 20? 30? years from now.

LIRs who take advantage of this proposal would continue to fail to deal with the v4 run-out. That would be bad for everyone.

> Speaking on behalf of such an entity, it's difficult to grow when you're limited to your one /22 in today's market.

Tough. It’s difficult to get on a train long after it has left the station.

New entrants presumably know what the current v4 allocation policy is and should plan accordingly.

Everyone would like to grow their IPv4 networks but that just isn’t possible any more.

> We (as an industry) are not there with IPv6 for this to be the only option.

It's the only sane option. But there are others. Choose wisely.

Changing address policy to speed up depletion of the NCC's last dregs of IPv4 is not wise. Doing that just because some LIRs -- not necessarily new entrants -- can’t or won’t face up to the reality of IPv4 exhaustion is even more unwise.

This proposal, if adopted, would be also unfair on the LIRs who *already have* taken action to deal with the v4 run-out. That can’t possibly be right.

> Ring-fencing 185/8 for new LIRs is sensible, this policy is really about recycling returned addresses and solves a real problem for a lot of recent new entrants.

I’m far from convinced there is a “real problem” here. If compelling arguments can be made to define the problem and solve it, let’s hear them!

IMO this proposal is really about short-term gain for some at the expense of others, particularly tomorrow’s new LIRs.

BTW what’s to stop an unscrupulous LIR from repeatedly requesting extra /22s (or whatever) through this proposal and then selling/transferring the space without updating the database? If they tried to do this today, they could only get away with it once because they’d only get one v4 allocation.