icon-1-darkicon-1-darkicon-1-lighticon-2-darkicon-2-lighticon-3-darkicon-3-lighticon-4-darkicon-4-lighticon-5-darkicon-5-lighticon-6-darkicon-6-lighticon-7-darkicon-7-lighticon-8-darkicon-8-lighticon-9-darkISOC-IconISOC-IconISOC-IconShapeISOC-IconISOC-IconISOC-IconPage 1icon-comma-darkicon-comma-lightFill 1ISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconShapeISOC-IconISOC-IconISOC-IconBLOCKSISOC-IconISOC-IconISOC-IconISOC-IconLISTISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconLEFTISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconShapeDOWN ARROWSEARCHISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-Icon-Dark-RGBISOC-Society-logo
Donate
Discussing MANRS at RIPE 72 Next Week Thumbnail
‹ Back
Improving Technical Security 20 May 2016

Discussing MANRS at RIPE 72 Next Week

Andrei Robachevsky
By Andrei RobachevskySenior Director, Technology Programmes

Some time ago, a group of MANRS participants agreed that it’d be a good idea to have more precise guidance for the implementation of MANRS Actions. Having such a document could serve at least two purposes:

  • Ease deployment of measures required by MANRS (stub networks or small providers – the majority of ASNs)
  • Help check if the network setup is compliant with MANRS

Job Snijders presented this idea and an outline of the MANRS BCOP document at RIPE71 in November 2015. The idea was supported by several network operators and experts who joined the team to develop such guidance. Since then the team has done some heavy lifting as it appeared even the implementation of basic routing security practices cannot be accomplished by a single line in a config file!

We plan to present this work at the RIPE BCOP TF on May 23 during the RIPE meeting. If you are planning to attend RIPE72, please join the discussion.

This is a work in progress, but you can find the current version of the document here:

https://docs.google.com/document/d/1fQxknkC3_ggdNnPF3NfaWFpmc4ajTonVQIiD9DYBhlg/edit?usp=sharing

We welcome your review and contributions. We expect that shaping up of the document will continue in the RIPE BCOP TF.

[Editor’s Note: This post was originally published on the Routing Resilience Manifesto blog at https://www.routingmanifesto.org/2016/05/discussing-manrs-at-ripe-72-next-week/.]

‹ Back

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

Related articles

Paving the Way Forward for MANRS
Paving the Way Forward for MANRS
Improving Technical Security18 February 2016

Paving the Way Forward for MANRS

How do you get a community effort off the ground and make it a success? How do we even define...

MANRS BCOP published
Deploy3604 April 2017

MANRS BCOP published

The Internet Society's Mutually Assured Norms for Routing Security (MANRS) initiative recently published a Best Current Operational Practices (BCOP) document to provide...

MANRS BCOP published as RIPE document
MANRS BCOP published as RIPE document
Mutually Agreed Norms for Routing Security (MANRS)13 June 2018

MANRS BCOP published as RIPE document

The MANRS initiative's set of Best Current Operational Practices has received recognition from the RIPE community by being published as...

Join the conversation with Internet Society members around the world