From zorz at isoc.org Mon Sep 2 10:33:43 2013 From: zorz at isoc.org (Jan Zorz - ISOC) Date: Mon, 2 Sep 2013 10:33:43 +0200 Subject: [bcop] BCOP BoF at RIPE67 in Athens Message-ID: <52244D67.10305@isoc.org> Dear BCOP "crowd" :) We got the BCOP BoF accepted for RIPE67 in Athens, with a note that we would like to have it on Monday after the "BCOP updates" lightning talk, where I'll do a short update on the BCOP activities around the world and some identified topics that came out of discussion on this mailing list (and also some others). I would like to announce with great pleasure, that Benno Overeinder from NLNET Labs volunteered and made a step forward to help with BCOP activity in RIPE community - so he'll do the ligtning talk with me and co-run the BCOP BoF in Athens. We have a small web page with some information about BCOPs around the world: http://www.internetsociety.org/deploy360/about/bcop/ ...and a list of some identified topics: http://www.internetsociety.org/deploy360/about/bcop/topics/ Now we need to start drafting some of this documents. Pick the topic and draft a "table of content", send it to the list and ask for co-authors. Anyone? I'll start the draft titled "Basic IPv6 troubleshooting for helpdesks around the world" document, that would bring the ISPs a simple template with some generic information that their helpdesk should know about when they put IPv6 in production. Document should be really just a start with "add-your-own-specifics" in mind. I think this should remove the next speedbump in IPv6 deployment, I have the same feeling like I had when I started a document, that later became RIPE-501 and RIPE-554. Would anyone like to help me with this? I would also like to suggest that we have some short presentations of ideas of BCOP documents in Athens - but we need to start doing something prior to that - and we have less than 2 months to do something. Cheers, Jan Zorz From mayan at bupt.edu.cn Tue Sep 3 04:54:38 2013 From: mayan at bupt.edu.cn (MA Yan) Date: Tue, 3 Sep 2013 10:54:38 +0800 (CST) Subject: [bcop] =?gbk?q?BCOP_BoF_at_RIPE67_in_Athens?= Message-ID: <20130903025438.3CE8B340313@mx5.bupt.edu.cn> An HTML attachment was scrubbed... URL: From zorz at isoc.org Mon Sep 9 10:56:57 2013 From: zorz at isoc.org (Jan Zorz - ISOC) Date: Mon, 9 Sep 2013 10:56:57 +0200 Subject: [bcop] Suggestions for top-10 IPv6 issues that trigger residential users to call helpdesk Message-ID: <522D8D59.4030401@isoc.org> 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 From mayan at bupt.edu.cn Mon Sep 9 21:43:54 2013 From: mayan at bupt.edu.cn (=?gbk?B?wu3Rzw==?=) Date: Mon, 09 Sep 2013 21:43:54 +0800(CST) Subject: [bcop] =?gbk?q?Suggestions_for_top-10_IPv6_issues_that_trigger_re?= =?gbk?q?sidentialusers_to_call_helpdesk?= Message-ID: <20130909134354.45FF019F383@mx1.bupt.edu.cn> An HTML attachment was scrubbed... URL: From zorz at isoc.org Tue Sep 10 09:28:23 2013 From: zorz at isoc.org (Jan Zorz - ISOC) Date: Tue, 10 Sep 2013 09:28:23 +0200 Subject: [bcop] Suggestions for top-10 IPv6 issues that trigger residentialusers to call helpdesk In-Reply-To: <20130909134354.45FF019F383@mx1.bupt.edu.cn> References: <20130909134354.45FF019F383@mx1.bupt.edu.cn> Message-ID: <522ECA17.8040601@isoc.org> On 9/9/13 3:43 PM, ?? wrote: > Agree on these issues as listed below? with added a few, including > security concern, DHCP, ... : > > - Addressing issues( DHCP issue may belong to this) > - 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? > - Security issue > - less supporting software/solutions, like accounting/management/trouble > shooting softwares... Thank you very much for your suggestions. What we need is to break down this areas and find actual cases and situations for each bullet above. like: "users host configures IPv6 address from RA sent from router, but there is no further IPv6 connectivity between CPE and ISP" - and the procedure how to detect that and how to fix that or: "I can get to Facebook, Google, YouTube, Wikipedia, (list other dual-stack sites) but not Amazon, eBay (other IPv4-only sites)." Troubleshooting: Try www.test-ipv6.com, what do you see there (and move forward through procedure flowchart) The main goal of the document is to push/move forward the IPv6 implementation towards end-users and this inability for technical folk to deliver a simple IPv6 description/script/information to helpdesk manager is creating psychological impediment to move things forward. For example - a fire-alarm procedures. We don't have to know how fire works, what the temperatures are, how fire extinguisher works, how the dust that comes out of it affects the flame and so on and so on... We need simple instructions "in case of fire or visible flame, go down the stairs, find red cylindrical thing on the wall, read instructions how to use it and point towards fire. If fire don't go away, call fire brigade at number XXX (second level support)" No RA,DHCPv6,PD,etc... just simple clear instructions how to determine if the problem is because of IPv6 issue, locate the issue (for example go to test-ipv6.com, what do you see... ah, in this case do [that]...) and move forward through the procedure. Cheers, Jan ---- "Engineering is always positive in results..." N. Tesla From zorz at isoc.org Wed Sep 11 09:55:20 2013 From: zorz at isoc.org (Jan Zorz - ISOC) Date: Wed, 11 Sep 2013 09:55:20 +0200 Subject: [bcop] BCOP BoF at RIPE67 in Athens In-Reply-To: <20130903025438.3CE8B340313@mx5.bupt.edu.cn> References: <20130903025438.3CE8B340313@mx5.bupt.edu.cn> Message-ID: <523021E8.2010601@isoc.org> On 9/3/13 4:54 AM, MA Yan wrote: > Yes, it is good to know that the BCOP BoF be accepted. > > I would like to work with you all on this. > We have IPv6 deployed in our network, though there is some dedicated > helpdesk work related with IPv6, butnot much yet. Hi, Thank you for your kind offer. Yes, we need suggestions and ideas on real situations and IPv6 issues that would make user call the helpdesk. Could you send some examples that you encountered at your helpdesk? Cheers, Jan -- Jan Zorz Internet Society mailto: http://www.internetsociety.org/deploy360/ -- "Engineering is always positive in results..." N. Tesla