- BCOP - mailman.ripe.net

Suggestions for top-10 IPv6 issues that trigger residential users to call helpdesk
by Jan Zorz - ISOC 09 Sep '13

09 Sep '13

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

1 0

BCOP BoF at RIPE67 in Athens
by Jan Zorz - ISOC 02 Sep '13

02 Sep '13

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

1 0

First email to BCOP discussion list...
by Jan Zorz - ISOC 24 Jul '13

24 Jul '13

Hi all, Finally we have a mailing list (thnx to staff @RIPE-NCC) that we identified as one of the first next steps at BOF in Dublin RIPE meeting. Please send emails to: bcop(a)ripe.net This is the place, where we can discuss how to move forward with the Best Current Operational Practices work, how to maybe move it forward towards more official status, who is willing to participate and start the documents - but first of all - we agreed that we need to identify the topics of discussion. First few that I heard were: - source addr antispoofing operational practices - peering good practices - how to implement IPv6 at ISP (different network types and flavors) - DNSsec how-to and practices ... I would like to invite all to send suggestions so we can identify the topics - and then we can see later where we can start some effort and form a groups that would start producing a documentation. Thank you all for participating at BOF, we are aiming for another BOF in Athens (this time with beer and chips in the room, as the BOF should be :) ) Cheers, Jan Zorz

4 6

Some ideas
by Nash, Steve 05 Jul '13

05 Jul '13

As a very early starting point, having scanned the ietf BCPs, I table the following. I believe we need to consider both what the requirements should be, and also what incentives there might be for compliance. I suggest the emphasis should be on satisfying the world at large that the Internet community encourages its members to behave responsibly. A secondary objective might be education for new operators. ========================================== RIPE Implementation Requirements 1. INHIBIT ADDRESS SPOOFING 1.1 BCP 38 (rfc 2827) with BCP 84 (rfc 3704) Ingress Filtering Implemented at every access router and switch as appropriate for: 1. Single host 2. Non-Transit subnet 3. Registered sub-network transit (tell ISP of additional address spaces) 4. Open Transit (restrict to BGP?) 5...... 1.2 Install RIPE supplied anti-spoofing probe at 10% of access PoPs 1.3 [Consider] TCP/UDP/SCTP.... port filtering Accept DNS replies (src port 53) only from customers requesting DNS support. Block dest port 53 toward non-hosting clients. 2. POLICIES FOR PEERING Register External Routing Policy in RIPE Db. Ask Peers to comply with this doc (? Inter-RIR ?) ? Apply route filtering At IX ask Peers to maintain AS-MAC mapping, in order to facilitate back-tracking 3. DNS POLICIES ?rfc 2870 (BCP 40) ?rfc 2219 BCP 17 ?rfc 2182 BCP 16 4. POLICIES FOR EMAIL ?rfc 2505 (BCP 30) Steve Nash 17 June 2013 steve.nash(a)theiet.org ================================

2 1