Colleagues, Following Job's presentation "MANRS Implementation Document" at the BCOP TF at RIPE71 last week (https://ripe71.ripe.net/programme/meeting-plan/bcop-tf/), we corralled a group of volunteers to move this project forward.
Folks that agreed to help and share their experience are: Brian J. Foust, Aaron Hughes, Will van Gulik and Aris Lambrianidis. Thank you! Of course Job and I will continue to shoulder this effort. To continue discussions and produce a draft document for wider review we created a mailinglist: https://elists.isoc.org/mailman/listinfo/manrs-bcop. Feel free to subscribe if you are interested! Otherwise - stay tuned. Regards, Job and Andrei Job Snijders wrote on 29/10/15 17:41: > 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
