Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Tore Anderson
* Sander Steffann > > We just need Google to announce that IPv6 enabled sites will get a > > slight bonus in search rankings. And just like that, there will > > suddenly be a business reason to implement IPv6. > > I already discussed that with them a long time ago, but they weren't > convinced

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Randy Bush
>> the more interesting question to me is: what can we, ops and ietf, do >> to make it operationally and financially easier for providers and >> enterprises to go to ipv6 instead of ipv4 nat? carrot not stick. > > The problem is, the only way to make it easier for providers and > enterprises to s

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread George Metz
On Mon, Jan 4, 2016 at 9:37 PM, Randy Bush wrote: > the more interesting question to me is: what can we, ops and ietf, do > to make it operationally and financially easier for providers and > enterprises to go to ipv6 instead of ipv4 nat? carrot not stick. > > randy > The problem is, the only w

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Randy Bush
> The Netflix idea is putting pressure on eyeball networks. The google > search rank idea is to put pressure on content providers. and how does the internet benefit by putting pressure on providers? i see how the folk who produce glossy paper for a living, or those who charge for renting 128 bit

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Baldur Norddahl
On 5 January 2016 at 02:53, Owen DeLong wrote: > The same is likely true of the Google search ranking idea, no? > The Netflix idea is putting pressure on eyeball networks. The google search rank idea is to put pressure on content providers. You have been arguing that the content providers are th

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Valdis . Kletnieks
On Mon, 04 Jan 2016 16:42:45 -0800, Owen DeLong said: > Another alternative discussed, but Netflix seems so far to be unconvinced: > > If you come via IPv6, you get all the content. > > If you come from IPv4, And Netflix convinces Sony to ship an IPv6-capable OS update for the PS3 and PS4, how, e

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Jan 4, 2016, at 17:01 , Ricky Beam wrote: > > On Mon, 04 Jan 2016 19:42:45 -0500, Owen DeLong wrote: >> If you come from IPv4, in the first week that new content is posted, instead >> of the new content, you get a video explaining the need to get a better >> internet connection and that

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Damian Menscher
On Mon, Jan 4, 2016 at 2:48 PM, wrote: > On Mon, 04 Jan 2016 17:23:20 -0500, Christopher Morrow said: > > https://developers.google.com/speed/public-dns/faq?hl=en > > > > there I asked jeeves for ya! > > > > So in how many of the 196 or so extant countries does 8.8.8.8 resolve > to > > > a host w

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Justin M. Streiner
On Mon, 4 Jan 2016, Ca By wrote: Just a reminder, that 10% is a global number. The number in the USA is 25% today in general, is 37% for mobile devices. Furthermore, forecasting is a dark art that frequently simply extends the past onto the future. It does not account for purposeful engineeri

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Ricky Beam
On Mon, 04 Jan 2016 19:42:45 -0500, Owen DeLong wrote: If you come from IPv4, in the first week that new content is posted, instead of the new content, you get a video explaining the need to get a better internet connection and that the content you want will be available to the legacy inter

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Jan 4, 2016, at 16:37 , Sander Steffann wrote: > > Hi, > >> We just need Google to announce that IPv6 enabled sites will get a slight >> bonus in search rankings. And just like that, there will suddenly be a >> business reason to implement IPv6. > > I already discussed that with them a lo

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Sander Steffann
Hi, > We just need Google to announce that IPv6 enabled sites will get a slight > bonus in search rankings. And just like that, there will suddenly be a > business reason to implement IPv6. I already discussed that with them a long time ago, but they weren't convinced. Maybe now is the time to d

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Jan 4, 2016, at 16:21 , Damian Menscher wrote: > > On Mon, Jan 4, 2016 at 3:55 PM, Owen DeLong > wrote: > domain.name results are 82 (16.4%) up from 69 (13.8%). > www.domain.name

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Damian Menscher via NANOG
On Mon, Jan 4, 2016 at 3:55 PM, Owen DeLong wrote: > domain.name results are 82 (16.4%) up from 69 (13.8%). > www.domain.name results are 101 (20.2%) up from > 81 (16.2%) As a professional pessimist, I can't help but note that of the 111 sites responding over IPv6 (I'm

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Valdis . Kletnieks
On Mon, 04 Jan 2016 15:35:05 -0800, Owen DeLong said: > You do realize that the query source address is not 8.8.8.8 when it goes to > the > authoritative server, right? As I said: > So in how many of the 196 or so extant countries does 8.8.8.8 resolve to > a host which, when it sends a query up

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
It’s always fun when I open my mouth in public only to turn it into a learning experience. TL;DR version: Several enhancements to the script and to my PERL library to improve the accuracy were made. The now more accurate results aren’t very different. Details below: As a result of comments rec

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Mon, 04 Jan 2016 14:17:56 -0800, Owen DeLong said: >> Further, 8.8.8.8 actually fully supports EDNS0 Client Subnet capability, so >> if the geo-IP balancer in question wants, they can eliminate the failure mode >> you are describing in that case. > > Which only helps for people using 8.8.8.8.

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Jan 4, 2016, at 14:09 , valdis.kletni...@vt.edu wrote: > > On Mon, 04 Jan 2016 13:52:46 -0800, Damian Menscher said: > >> While I agree with your general sentiment about 3xx responses (often used >> to redirect example.com to www.example.com) I think your concerns about >> 8.8.8.8 are over-

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Baldur Norddahl
We just need Google to announce that IPv6 enabled sites will get a slight bonus in search rankings. And just like that, there will suddenly be a business reason to implement IPv6. Regards, Baldur

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Valdis . Kletnieks
On Mon, 04 Jan 2016 17:23:20 -0500, Christopher Morrow said: > https://developers.google.com/speed/public-dns/faq?hl=en > > there I asked jeeves for ya! > > So in how many of the 196 or so extant countries does 8.8.8.8 resolve to > > a host which, when it sends a query up the chain, appears to be

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Christopher Morrow
https://developers.google.com/speed/public-dns/faq?hl=en there I asked jeeves for ya! On Mon, Jan 4, 2016 at 5:09 PM, wrote: > On Mon, 04 Jan 2016 13:52:46 -0800, Damian Menscher said: > >> While I agree with your general sentiment about 3xx responses (often used >> to redirect example.com to w

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> On Jan 4, 2016, at 13:21 , valdis.kletni...@vt.edu wrote: > > On Mon, 04 Jan 2016 11:59:40 -0800, Owen DeLong said: > >> These numbers might be slightly pessimistic because 3XX series responses are >> not counted as good. > > They may be a *lot* more than slightly pessimistic - consider the c

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Valdis . Kletnieks
On Mon, 04 Jan 2016 13:52:46 -0800, Damian Menscher said: > While I agree with your general sentiment about 3xx responses (often used > to redirect example.com to www.example.com) I think your concerns about > 8.8.8.8 are over-stated. 8.8.8.8 is deployed in many locations, which > gives DNS-based

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Damian Menscher via NANOG
On Mon, Jan 4, 2016 at 1:21 PM, wrote: > On Mon, 04 Jan 2016 11:59:40 -0800, Owen DeLong said: > > > These numbers might be slightly pessimistic because 3XX series responses > are > > not counted as good. > > They may be a *lot* more than slightly pessimistic - consider the case of > any site tha

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Valdis . Kletnieks
On Mon, 04 Jan 2016 11:59:40 -0800, Owen DeLong said: > These numbers might be slightly pessimistic because 3XX series responses are > not counted as good. They may be a *lot* more than slightly pessimistic - consider the case of any site that uses 3xx replies to redirect to a geo-IP based server

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Ricky Beam
On Mon, 04 Jan 2016 11:21:14 -0500, Jon Lewis wrote: Just a reminder, that 10% is a global number. And it's not "native". A great many (myself included) have IPv6 *by choice* through various tunnels. And AT&T (Uverse) isn't "native" either -- it's a 6rd tunnel their gateways have been prog

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Owen DeLong
> > > Add to that the fact that as we run closer to (or further into?) run-out, at > some point there's likely to be a rapid acceleration in v6 provisioning as > networks finally realize that they can't reasonably get any more v4 space or > their end-user customers finally begin to demand v6.

Re: Netflix stuffing data on pipe

2016-01-04 Thread Owen DeLong
The most obvious things would be to make feedback faster… Implement congestion controls further up stream with reduced buffering throughout the network, selective technologies like WRED, etc. As RS said, sure, but all come at a cost either in performance, equipment, support, or some combination

Re: VPLS Providers

2016-01-04 Thread Christopher Morrow
On Mon, Jan 4, 2016 at 4:19 AM, Mark Tinka wrote: > Almost every time a customer has asked me for VPLS (or EVPN), they've > been just fine with l3vpn as a suggested alternative. > > Other customers are all about doing their own routing... there are complications with an L3 vpn solution that L2/vp

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Neil Harris
On 04/01/16 16:09, Ca By wrote: On Mon, Jan 4, 2016 at 3:26 AM, Neil Harris wrote: On 02/01/16 15:35, Tomas Podermanski wrote: Hi, according to Google's statistics (https://www.google.com/intl/en/ipv6/statistics.html) on 31st December 2015 the IPv6 penetration reached 10% for the very

RE: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Jacques Latour
Great news and even more impressive is that Canada is the fastest adopter with ~8% IPv6 penetration, growing from almost 0.5% to 8% in 3 months!!!. See http://stats.labs.apnic.net/ipv6/CA Telus is making a big difference in Canada as the IPv6 adoption leader @ ~45% IPv6 adoption.http://sta

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Jared Mauch
> On Jan 4, 2016, at 11:09 AM, Ca By wrote: > >> On Mon, Jan 4, 2016 at 3:26 AM, Neil Harris wrote: >> >>> On 02/01/16 15:35, Tomas Podermanski wrote: >>> >>> Hi, >>> >>> according to Google's statistics >>> (https://www.google.com/intl/en/ipv6/statistics.html) on 31st December >>> 2015

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Jon Lewis
On Mon, 4 Jan 2016, Ca By wrote: Given the recent doubling growth, and assuming this trend is following a logistic function, then, rounding the numbers a bit for neatness, I get: Jan 2016: 10% Jan 2017: 20% Jan 2018: 33% Jan 2019: 50% Jan 2020: 67% Jan 2021: 80% Jan 2022: 90% with IPv4 traffic

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Ca By
On Mon, Jan 4, 2016 at 3:26 AM, Neil Harris wrote: > On 02/01/16 15:35, Tomas Podermanski wrote: > >> Hi, >> >> according to Google's statistics >> (https://www.google.com/intl/en/ipv6/statistics.html) on 31st December >> 2015 the IPv6 penetration reached 10% for the very first time. Just a

Re: Netflix stuffing data on pipe

2016-01-04 Thread Rob Seastrom
I haven't done packet dumps to verify the behavior (too busy catching up on holiday email) but I can't help but wonder if IW10 (on by default in FreeBSD 10 which I believe might be what Netflix has underneath) is causing this problem, and that maybe a more gentle CWND ramp-up (or otherwise tweak

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread Neil Harris
On 02/01/16 15:35, Tomas Podermanski wrote: Hi, according to Google's statistics (https://www.google.com/intl/en/ipv6/statistics.html) on 31st December 2015 the IPv6 penetration reached 10% for the very first time. Just a little reminder. On 20th Nov 2012 the number was 1%. In December we a

Re: Another Big day for IPv6 - 10% native penetration

2016-01-04 Thread A . L . M . Buxey
Hi, > I'm wondering when we reach another significant milestone - 50% :-) half of us will celebrate, the other half will cry ;-) alan

Re: VPLS Providers

2016-01-04 Thread Mark Tinka
On 1/Jan/16 17:19, Nick Hilliard wrote: > > If you're talking a requirement for connecting geographically separated > locations, there are sound technical reasons for avoiding vpls like the > plague. Unless there are overriding technical reasons why it wouldn't > work, l3vpn will almost always

Re: Netflix stuffing data on pipe

2016-01-04 Thread Pete Mundy
Very succiently put, Owen! I concur. Is anything the ISP could avoid to alleviate this occurrence, or is it entirely a 'server-side' issue to resolve? Pete > On 4/01/2016, at 8:42 pm, Owen DeLong wrote: > > As I understand it, the problem being discussed is an oscillation that is > creat