This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 only network (not just at RIPE xx meeting)
- Previous message (by thread): [ipv6-wg] IPv6 only network (not just at RIPE xx meeting)
- Next message (by thread): [ipv6-wg] IPv6 only network (not just at RIPE xx meeting)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benedikt Stockebrand
bs at stepladder-it.com
Sun Jun 1 22:06:55 CEST 2014
Hi Geert Jan and list, Geert Jan de Groot <GeertJan.deGroot at xs4all.nl> writes: > [...] Thing is, we seem to be working on making the Internet V6-capable, > but currently V6 performance and stability is a serious issue, especially > when it comes to reporting problems. [...] the Good News[TM] here is that with an increasing number of DS-Lite deployments, these will likely put the pressure on those web sites money-wise: If the site appears sluggish or unstable to an increasing number of people who don't have proper (in the broadest possible sense and explicitly including NAT) IPv4 connectivity, the owners of those web sites will eventually notice that they have a problem. I think we are offering these people all the help they need, but until they actually want our help, that's pretty much all we can do. We can spread the word best we can, but we can't force people to listen. > So, my question to the WG: does the WG think this is a problem, Definitely, but: At the few IETF meetings I've been to before they started the sunset4 WG I've been rather frustrated by the v6ops WG being swamped with transition/somebody-save-my-IPv4 topics. We better be careful that this doesn't happen here as well. > and can we think of a way to get clueful v6 complaints to clueful > handlers, instead of being ignored / misaddressed / ...? The problem of getting first level support up and running with IPv6 is tremendous, and some people put significant effort into dealing with this. What else can we do at this point? On a more general scale: As far as I am personally concerned, rather than putting effort into convincing people who simply refuse to accept that there's something that they have to take care of, I personally rather focus my energy on those people who have realized so and come for help. That is where I can make a difference. After all, anybody in IT should have heard of IPv6 and why we need it by now; it isn't a well kept secret at all. The problem is not that people don't know, it is that people don't care. Cheers, Benedikt -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/
- Previous message (by thread): [ipv6-wg] IPv6 only network (not just at RIPE xx meeting)
- Next message (by thread): [ipv6-wg] IPv6 only network (not just at RIPE xx meeting)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]