[address-policy-wg] 2015-01 New Policy Proposal (Alignment of Transfer Requirements for IPv4 Allocations)

On Fri, 2015-02-20 at 11:45 +0100, Erik Bais wrote:
> The reasoning for reservation of the /22's in the final /8 is for new LIR's
> and current LIR's, to be able to get into the market and do v4 to v6 CGNAT
> or something alike .. or at least get some kind of startup going on some IP
> space ...  That was the original intent .. 

So the RIPE community still agree to allowing these use cases?

  - CGNAT to v4: Limited to 335 555 customers.

Math:  /28 for infrastructure (good luck...), then using
http://www.ietf.org/proceedings/87/slides/slides-87-behave-6.pdf slide
7:
                         S * a * N
 f(P,S,a,N,R)::= P ==  ------------
                         (65536-R)
Translated to our case:  f(1008,S,25%,400,32767) =>  S == 335 555.
So apart from only being able to compete with other ISPs on CGNAT
services, they'll be strictly limited in scope to basically serve one
smaller city.

Thus, the current policy basically excludes new entrants on the market,
employing full CGNAT, to grow to 335 555 customers. 


 - Cloud service provider: Limited to a maximum of 1008 customers.

Assuming same minimalistic infrastructure of 1x /28 for infrastructure,
a CSP is limited to a maximum of 1008 customers.  And that is in the
best case that each customer only has one service instance, where each
service instance uses 1x IPv4.

Thus, the current policy basically excludes new entrants from
competition with established cloud service providers.

<snip>

> The idea to close this, is because that flipping of the /22's of the final
> /8 goes against the intent of the initial policy. 

Is the intent of the original policy is to exclude new entrants from
competing with established service providers?

Or is this exclusion from entering the market just a side-effect of
making the pool last longer by rationing address space out per legal
entity?

/M
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: </ripe/mail/archives/address-policy-wg/attachments/20150220/a43df167/attachment.sig>