[ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dez C
dez at otenet.gr
Fri May 29 10:29:56 CEST 2020
On 5/29/20 10:38 AM, Jens Link wrote: > Nick Hilliard <nick at foobar.org> writes: > >> having the meetings, for starters. > Sure. Let's talk more about deploying IPv6. Did work very well for the > last decade / years. oh, but it has. Talking about issues, creating traction, usually helps. Just check the google stats for the percentage of users accessing google via IPv6: Sep 2008: 0.04%, May 2020: 30% . Then check the stats for Greece. Greece is at almost 50% and I can tell you why: We (main ISPs+Academia) created a task force and started presenting and educating (other SPs, Enterprises etc). I bet that countries with similar percentages followed a similar path. What you're proposing is the end user's perspective and its fine. We're not just end users, we can influence things on a larger scale (sometimes, at least) cheers, Yannis > > Personally I think that one thing that might work better is to avoid IPv4 > only services when there is an alliterative service with IPv6 enabled. One > only has some little extra work, like installing a browser plugin and > watching the output. > > So do not complain that $ISP has no IPv6 choose an alliterative if you > can. If the git web service you are using does not complain and open > tickets, choose an alternative. If your CDN does not fully support IPv6 > do not complain and choose an alternative. .... > > Jens
- Previous message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
- Next message (by thread): [ipv6-wg] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]