Re: Dual stack IPv6 for IPv4 depletion

[Jared Mauch <jared () puck nether net>]

> On Jul 15, 2015, at 7:45 PM, Joe Maimon <jmaimon () ttec com> wrote:
>
>
>
> Doug Barton wrote:
> > On 7/15/15 10:24 AM, Joe Maimon wrote:
> > > I suspect a 16 /8 right about now would be very welcome for everybody
> > > other then the ipv6 adherents.
> >
> > Globally we were burning through about a /8 every month or two in "the
> > good old days." So in the best case scenario we'd get 32 more months of
> > easy to get IPv4, but at an overwhelming cost to re-implement every
> > network stack.
> >
> > This option was considered back in the early 2000's when I was still
> > involved in the discussion, and rejected as impractical.
>
>
> Removing experimental status does not equate with the burden of making it equivalent use to the rest of the address 
> space.
>
> How about the ARIN burn rate post IANA runout? How long does 16 /8 last then?
>
> What would be wrong with removing experimental status and allowing one of the /8 to be used for low barrier to /16 
> assignment to any party demonstrating a willingness to coax usability of the space?
>
> Yes, any such effort has to run the gauntlet of IETF/IANA/RIR policy.
>
> CGN /10 managed. This could too, if all the naysayers would just step out of the way.

This isn’t really a giant set of naysayers IMHO, but there is enough embedded logic in devices that it doesn’t make 
that much sense.

Either you can survive with some type of NAT or you can’t.  Many of my devices would not be missing capabilities if I 
had just IPv6 on them with some gateway to reach the IPv4 internet.  I could likely make a short list of the sites that 
I really need access to that are IPv4 only.  With Amazon/Walmart day, they would be well suited to have a fast IPv6 
site :)

It’s just a few operating systems that need to be changed:

windows
linux
various *bsd flavors
macos

I don’t think it’s impossible, but so many things check for  224 > A > 1 it would be a large bit of work to fix those.  
This is excluding the routing equipment.

What i’ve learned is that stuff like the netgear/linksys you have at your house spends around ~6 months in the supply 
chain before it reaches you.  these all need to be updated as well as the “big iron” stuff like cisco/juniper/arista as 
well as their embedded OS underneath, so maybe QNX or something else ‘odd’.

That effort would need to have everyone moving in the same direction now which seems unlikely.

- Jared