Re: RIPE our of IPv4

2019-11-30 Thread Jared Mauch
I'm still surprised that for $42/mo you can't afford IPv6. If you already have a legacy allocation most cases you can get v6 for "free". I get low budget stuff, but honestly it doesn't have to be you it could be one upstream that gives you a /48 to get you started. Sent from my iCar > On

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
On Sat, Nov 30, 2019 at 5:55 PM Valdis Klētnieks wrote: > On Sat, 30 Nov 2019 13:47:36 -0800, Matthew Kaufman said: > > > User apps prefer IPv6, Netflix stops, users complain > > And fallback to IPv4 fails to happen, why, exactly? > Because of the layer at which failure happens. You get

Re: RIPE our of IPv4

2019-11-30 Thread Brandon Martin
On 11/30/19 8:55 PM, Valdis Klētnieks wrote: >> User apps prefer IPv6, Netflix stops, users complain > And fallback to IPv4 fails to happen, why, exactly? Inability to signal application-level failure on IPv6 and that fallback to IPv4 would succeed. Netflix definitely exhibits this. I've also

Re: RIPE our of IPv4

2019-11-30 Thread Valdis Klētnieks
On Sat, 30 Nov 2019 13:47:36 -0800, Matthew Kaufman said: > User apps prefer IPv6, Netflix stops, users complain And fallback to IPv4 fails to happen, why, exactly? pgphoWWsRXmVA.pgp Description: PGP signature

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
On Sat, Nov 30, 2019 at 4:57 PM Brandon Martin wrote: > On 11/30/19 4:48 PM, Matthew Kaufman wrote: > > See previous message about legacy IPv4 holders without budget for IPv6 > blocks > > How slim are your margins to have been around long enough to have a legacy > IPv4 block but not be able to

Re: RIPE our of IPv4

2019-11-30 Thread Brandon Martin
On 11/30/19 12:18 PM, Justin Streiner wrote: > Verizon is an interesting case.  While IPv6 penetration on the wireless side > is very high, the same is not true on the Fios/DSL side.  IPv6 deployment > there is nearly nonexistent. > I've heard rumblings that some early Fios users will need to

Re: RIPE our of IPv4

2019-11-30 Thread Brandon Martin
On 11/30/19 4:48 PM, Matthew Kaufman wrote: > See previous message about legacy IPv4 holders without budget for IPv6 blocks  How slim are your margins to have been around long enough to have a legacy IPv4 block but not be able to afford the ARIN fees to get a comparable/very usable (/48 to /52

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
Sorry, thought this was the Tunnels part of the thread. Kubernetes Container networking only supported one address per pod until well *after* V6-only clusters were in alpha, so dual-stack want an option. Point is, plenty of popular server-side infrastructure was designed IPv4-first as late as

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
See previous message about legacy IPv4 holders without budget for IPv6 blocks On Sat, Nov 30, 2019 at 12:15 PM Filip Hruska wrote: > You can announce your own IPv6 subnets through TunnelBroker. > > Filip > > > On 30 November 2019 8:37:33 pm GMT+01:00, Matthew Kaufman < > matt...@matthew.at>

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
User apps prefer IPv6, Netflix stops, users complain On Sat, Nov 30, 2019 at 1:29 PM Mark Andrews wrote: > And how did that stop you deploying IPv6? It’s not like you were turning > off IPv4. > -- > Mark Andrews > > On 1 Dec 2019, at 04:03, Matthew Kaufman wrote: > >  > This is a great

Re: RIPE our of IPv4

2019-11-30 Thread Mark Andrews
And how did that stop you deploying IPv6? It’s not like you were turning off IPv4. -- Mark Andrews > On 1 Dec 2019, at 04:03, Matthew Kaufman wrote: > >  > This is a great example (but just one of many) of how server software > development works: > > IANA IPv4 runout January 2011. > >

Re: RIPE our of IPv4

2019-11-30 Thread Filip Hruska
You can announce your own IPv6 subnets through TunnelBroker. Filip On 30 November 2019 8:37:33 pm GMT+01:00, Matthew Kaufman wrote: >On Sat, Nov 30, 2019 at 9:21 AM Justin Streiner >wrote: > >> >> >> While a tunnel from HE works perfectly well, it would be nice to have >> native v6 from VZ.

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
On Sat, Nov 30, 2019 at 9:21 AM Justin Streiner wrote: > > > While a tunnel from HE works perfectly well, it would be nice to have > native v6 from VZ. > Worked perfectly well. Until Netflix blocked all known tunnel providers. Then my users demanded I turn IPv6 off... so I did. Won’t come back

Re: RIPE our of IPv4

2019-11-30 Thread Justin Streiner
On Sat, Nov 30, 2019 at 11:46 AM Ca By wrote: > > That said, google see nearly 40% of their traffic on ipv6 in the usa , > growth trend looks strong > > https://www.google.com/intl/en/ipv6/statistics.html > > And > > Comcast (71%), Charter (52%), VZ (85%), ATT (60 and 78%) , and T-Mobile >

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
This is a great example (but just one of many) of how server software development works: IANA IPv4 runout January 2011. Kubernetes initial release June 2014. Developed by Google engineers. ARIN IPv4 runout September 2015. Support for IPv6-only Kubernetes clusters alphas in 1.9, December 2017.

Re: RIPE our of IPv4

2019-11-30 Thread Matthew Kaufman
I administer two networks that use legacy IPv4 blocks (one also uses an allocation from the 44 net) Both could have IPv6 if it was free, but neither organization has the funds to waste on a paid IPv6 allocation. We should have given every legacy block matching free IPv6 space, because early

Re: RIPE our of IPv4

2019-11-30 Thread Ca By
On Sat, Nov 30, 2019 at 8:06 AM Brian Knight wrote: > > On Nov 29, 2019, at 5:28 PM, Mike Hammett wrote: > >  > "So if they do care about IPv6 connectivity, they haven’t communicated > that to us." > > Nor will they, but that doesn't mean IPv6 isn't important. > > > Personally, I don’t

Re: RIPE our of IPv4

2019-11-30 Thread Brian Knight
>> On Nov 29, 2019, at 5:28 PM, Mike Hammett wrote: >  > "So if they do care about IPv6 connectivity, they haven’t communicated that > to us." > > Nor will they, but that doesn't mean IPv6 isn't important. Personally, I don’t disagree. We engineers do what we can to support IPv6: We build