From jan at go6.si Mon Oct 19 12:26:11 2015 From: jan at go6.si (Jan Zorz) Date: Mon, 19 Oct 2015 12:26:11 +0200 Subject: [bcop] Call for ideas and presentations for BCOP TF at RIPE71 Message-ID: <5624C543.6090705@go6.si> Dear BCOP community, RIPE71 is approaching rapidly and we would like to ask for some new ideas and presentations for BCOP TF meeting in Bucharest. Any volunteers that would like to start a new BCOP document? Please, respond to this list or to chairs directly. Cheers and see you all soon! Benno and Jan From job at instituut.net Thu Oct 29 17:41:12 2015 From: job at instituut.net (Job Snijders) Date: Thu, 29 Oct 2015 17:41:12 +0100 Subject: [bcop] MANRS BCOP Document Message-ID: <20151029164112.GC24841@22.rev.meerval.net> Hi all, We discussed this idea a few times before and I think agreed that it'd be a good idea to have a more precise guidance for the implementation of MANRS Actions. As I can see, it will serve at least two purposes: - Ease deployment of measures required by MANRS (we are talking here about stub networks or small providers - the majority of ASNs) - Help checking if the network setup is compliant with MANRS >From my discussions with operators at various meetings where Andrei Robachevsky presented MANRS it was also quite clear that such guidance for the MANRS "package" would be appreciated, also to be able to assess what it takes to become MANRS-compliant. So, Andrei and I took a stab at an outline of such document. It really has only a structure and is lacking content with examples, etc. at the moment. Help is needed! We put it as a Google doc, all of you should be able to edit it, so please help with some stuff. Even if it is a raw material - such input would be appreciated. The document is here: https://docs.google.com/document/d/1FQAVawGGvb-xqNLeGLk05h5nuu0FSS_9KLv6gBaWcJI/edit?usp=sharing Kind regards, Job