I agree in principal, but that means new entrants can't really conduct business 
because ipv6 visibility isn't to a level that your connection is actually 
useful if you were only ipv6.

I haven't been reading the entire thread but maybe for existing orgs who want 
more ipv4 they must show they are dual stacked and have their ipv6 actually 
routing and working before they get more ipv4.

Same idea as you, but from the take that the existing users who have space and 
a profitable business needs to add ipv6 before it can grow more.

Refusing ipv4 to a new entrant makes it basically impossible to start a new 
ISP/Hosting company business.  Will make existing orgs not want to roll out 
ipv6 as fast so as to somewhat block new entrants and competition.  At least 
that's how I see it.

Serge.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf 
Of Michael Richardson
Sent: Monday, November 25, 2013 9:49 AM
To: ARIN-PPML List
Subject: Re: [arin-ppml] Bootstrapping new entrants after IPv4 exhaustion


I think that we should stop trying to optimize or mitigate the IPv4 runout.
New entrants are screwed if their have a plan that requires more than an
IPv4/28 from upstream.

New entrants will need to do IPv6 from the first day, and we should make 
getting IPv6 (only) so cheap and simple that a new entrant can get PI IPv6 
space for their internal infrastructure at a point where they might not have an 
AS or any IPv4.

Let's have them think: how can I do *new innovative service* in native v6, 
rather than, "how do I doctor the paperwork convincingly enough so that I can 
get some of the last bit of IPv4"

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     [email protected]  http://www.sandelman.ca/        |   ruby on rails    [

_______________________________________________
PPML
You are receiving this message because you are subscribed to the ARIN Public 
Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to