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/bcop@ripe.net/
[bcop] Suggestions for top-10 IPv6 issues that trigger residential users to call helpdesk
- Previous message (by thread): [bcop] BCOP BoF at RIPE67 in Athens
- Next message (by thread): [bcop] Suggestions for top-10 IPv6 issues that trigger residentialusers to call helpdesk
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz - ISOC
zorz at isoc.org
Mon Sep 9 10:56:57 CEST 2013
Dear BCOP group ;) I'm trying to put together a list of (at least) top-10 problems/situations/issues on IPv6 that annoys the end user to the point that he calls operators helpdesk and claims that "internet is not working". What are possible issues, that a guy at helpdesk will encounter and the IPv6 could be the cause? What can go wrong? The areas that I identified are: - Addressing issues - DNS issues - Firewall issues - Tunneling issues - Transition mechanisms issues - Happy eyeballs issues - Why avoiding at all cost saying “if you have issues just disable IPv6” Any suggestions and ideas in building top-10 or top-15 most common issues would be greatly appreciated. As this document is aiming to document the best current operational practice for the operator, I'll also ask for suggestions the IPv6 working group (if the chairs will permit me to do so) and maybe gain some more interested experts to join our (for now) small group. Cheers, Jan
- Previous message (by thread): [bcop] BCOP BoF at RIPE67 in Athens
- Next message (by thread): [bcop] Suggestions for top-10 IPv6 issues that trigger residentialusers to call helpdesk
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]