From benno at NLnetLabs.nl Wed Oct 2 17:22:55 2013 From: benno at NLnetLabs.nl (Benno Overeinder) Date: Wed, 02 Oct 2013 17:22:55 +0200 Subject: [bcop] BCOP BoF RIPE 67 agenda, Monday 14 October Message-ID: <524C3A4F.4020708@NLnetLabs.nl> Hi, For the BCOP BoF on Monday at RIPE 67 in Athens, we have a (provisional) agenda of about one hour. Some of you already indicated that they are willing to give a short presentation on some ideas for a document, but there is still room for other enthusiast presenters to discuss a subject. Please contact us or send a mail to BCOP list. Here is the provisional agenda: - Positioning and grand perspective of local BCOP initiatives and interaction between the groups. Update of feedback on BCOP in other regions like ARIN/NANOG, LACNIC, APNIC, etc. - Brief overview of subjects that have been proposed, see http://www.internetsociety.org/deploy360/about/bcop/topics/ - Two (or more?) detailed/in-depth discussions of topics. - Discussion & closing: Who is willing to work on (part of) items, next steps, etc. Best regards, Jan and Benno -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/ From zorz at isoc.org Sat Oct 12 11:24:50 2013 From: zorz at isoc.org (Jan Zorz - ISOC) Date: Sat, 12 Oct 2013 11:24:50 +0200 Subject: [bcop] BCOP BoF in Athens Message-ID: <52591562.2040208@isoc.org> Good people on BCOP at RIPE mailing list ;) In Athens we have scheduled a BCOP BoF on monday at 18h, after the plenary part of RIPE meeting ends - this time the BoF will be "lead" by Benno Overeinder and myself. Thnx Benno for volunteering :) Benno and myself will do the lightning talk update on BCOP activities around the world on the same day at around 17h during the plenary, so be there to learn what's going on globally. You are all invited to attend the BoF, we'll discuss many interesting things and initiatives for operational documents. We identified some topics and some people already started doing some work. I'll present the beta-preview-draft of the document titled "Generic IPv6 troubleshooting procedures for helpdesks around the world", with contributors and co-authors Lee Howard, John Jason Brzozowski, David Freedman, Jason Fesler, Tim Chown, Sander Steffann, Chris Grundemann and myself. We'll also discuss the proposal from Andrei Robachevsky (ISOC) of creating a routing code of conduct, an interesting initiative to make Internet better. We might get Nick Hilliard interested to talk about BGP operational practices at IXP and so on. If anyone is interested in participating and presenting the work on the operational document that is being done - more than welcome to send an email to Benno or me. See you all on Monday afternoon in Athens, join us and bring everyone that is interested in operational practices. Cheers, Jan Zorz From ws at ripe.net Mon Oct 14 14:44:51 2013 From: ws at ripe.net (ws at ripe.net) Date: Mon, 14 Oct 2013 12:44:51 +0000 Subject: [bcop] =?utf-8?q?Presentation_Submitted_--_=5BBest_Current_Operat?= =?utf-8?q?ional_Practices_=28BCOP=29_=E2=80=93_updates_from_around_the_wo?= =?utf-8?q?rld=5D?= Message-ID: <339002f420ffd6b84223d2794a821507@ripe67.ripe.net> Dear Benno Overreinder, Jan Zorz, Thank you for uploading your presentation titled "Best Current Operational Practices (BCOP) ? updates from around the world". It is now available for viewing at: https://ripe67.ripe.net/presentations/ In order to (irreversibly!) delete the uploaded presentation, please use this link: https://ripe67.ripe.net/presentations/presentation-archive/delid/3320177476 If you have any questions, please reply to this message. RIPE 67 Meeting team From job.snijders at hibernianetworks.com Mon Oct 14 19:55:34 2013 From: job.snijders at hibernianetworks.com (Job Snijders) Date: Mon, 14 Oct 2013 20:55:34 +0300 Subject: [bcop] [Ccrsr] Some ideas on the content of the "code of conduct" (the first one - we need a better name!) Message-ID: <20131014175534.GP22067@Eleanor.local> On Tue, Oct 08, 2013 at 05:39:05PM +0200, Andrei Robachevsky wrote: > Colleagues, > > 1. basic routing hygiene & BGP security Would you consider not deaggregating your prefixes part of basic routing hygiene? I do. :-) I can understand that if a network has two different locations, with no backbone, that split up their space in two. But all to often I see networks announcing both more specific and covering aggregate, with only one endpoint, so the more specifics just waste space. > 2. anti-spoofing > 3. topology and connectivity Maybe a strong recommendation can be put in the code that a participant promises to keep peeringdb.com up2date? > 4. collaboration and coordination Here too peeringdb often plays a vital role in contacting the other party to cooperate to resolve an issue. > Any of these items? Only 4? Anything missing we'd like to include? 5. Enabling others in debugging efforts Maybe this falls under under one of the four other subjects, but I desperatly want networks to offer looking glasses from multiple points in their network, for both IPv4 and IPv6 with BGP, ping and traceroute, without a captcha, without a members login :-) > - I also got a comment regarding "Participation Requirements", > > 1. Endorsement from the management (C-level, public statement)? > 2. Demonstration of commitment through a set of measurable metrics - > what is feasible to measure? > 3. Public endorsement on the website (leave internal specifics to the > ISP and leave assessment to the operator community) > 4. Something different 1 or 3 is fine by me. I envision slapping networks with the code when they publicly endorse it but don't abide by it. One of the strongest drivers in this industry is the fear for name and shame I suppose, we all want to act like well educated boys because everything is visible. :-) Kind regards, Job -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 873 bytes Desc: not available URL: From job.snijders at hibernianetworks.com Mon Oct 14 23:43:05 2013 From: job.snijders at hibernianetworks.com (Job Snijders) Date: Tue, 15 Oct 2013 00:43:05 +0300 Subject: [bcop] [Ccrsr] Some ideas on the content of the "code of conduct" (the first one - we need a better name!) In-Reply-To: <20131014175534.GP22067@Eleanor.local> References: <20131014175534.GP22067@Eleanor.local> Message-ID: <20131014214305.GQ22067@Eleanor.local> On Mon, Oct 14, 2013 at 08:55:34PM +0300, Job Snijders wrote: > On Tue, Oct 08, 2013 at 05:39:05PM +0200, Andrei Robachevsky wrote: Whoops, this message was intended for a different mailing list. Kind regards, Job -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 873 bytes Desc: not available URL: From blake at l33.fr Wed Oct 16 11:41:17 2013 From: blake at l33.fr (Blake Willis) Date: Wed, 16 Oct 2013 11:41:17 +0200 Subject: [bcop] DNS open resolver BCP Message-ID: Greetings BCOP list, Sitting here in the DNS WG at RIPE67, it seems like a key task for the BCOP project is creating a repository (or pointers) to getting one's DNS servers properly configured & secured (the largest sources of DNS amp/reflection traffic are the networks with the least clue, & the least-deployed BCP38). There are certainly plenty of resources out there (including vendor documentation) but "google.com/search?q=DNS+open+resolver+BCP" isn't particularly conclusive. I feel the task at hand is really more of an education campaign than a technical problem... Best regards, -- Blake Willis Network Architecture Consultant & Co-Founder L33 Networks blake at l33 dot fr