• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
MANRS

MANRS

Mutually Agreed Norms for Routing Security

  • Home
  • About
    • History
    • Partners
    • Testimonials
    • Governance
      • Steering Committee
      • Advisory Group
        • Description and Role
        • Members
      • Community Charter
    • Contact Us
  • Programs
    • Network Operators
      • Network Operators Program and Actions
      • Implementation Guide
      • Participants
      • Join
    • IXPs
      • IXP Program and Actions
      • Participants
      • Join
    • CDN and Cloud Providers
      • CDN and Cloud Providers Program and Actions
      • Participants
      • Join
    • Equipment Vendors
      • Equipment Vendor Program and Actions
      • Participants
      • Join
  • MANRS Ambassadors
  • Resources
    • Training
      • Workshops
      • Tutorials
    • Promote MANRS
    • How-to Videos
    • Events
  • Observatory
  • Blog
  • Join

MANRS Implementation Guide Published as RIPE 706

June 13, 2018 by Megan Kruse 3 Comments

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

MANRS helps network operators around the world improve the security and resilience of the global routing system through four actions that include filtering, anti-spoofing, coordination and support for global validation. It currently involves over 85 organisations encompassing nearly 200 Autonomous Systems around the world, including some of the largest ISPs.

The MANRS BCOP offers guidance on how to practically implement each of the MANRS actions, based on the operational experiences of numerous network operators around the world. It’s a must read for those working with the global routing system, as routing security is a shared responsibility and needs commitment to good practices from all its participants.

The RIPE documents are developed and approved by the RIPE community, having been published since 1989. They include technical and operational recommendations, as well as policy, procedural and organisational documents. The publication of RIPE-706 represents community recognition of the MANRS principles and the importance of a commitment to routing security.

The MANRS initiative would like to thank David Freedman, Brian Foust, Barry Greene, Ben Maddison, Andrei Robachevsky, Job Snijders and Sander Steffann who were the primary authors of the document, but also all those who provided comment and feedback, and those who translated it into other languages.

If you’re interested in signing-up to MANRS, join here.

Category iconMANRS Publications,  News and Announcements

Reader Interactions

Comments

  1. Sylvain BAYA says

    June 19, 2018 at 8:20 am

    Hi Andrei,
    That’s a good achivement. which honor your team’s effort and commitment.
    Now that you have this document, accepted as a BCOP, in the RIPE community, I see two actions needed ahead for the #MANRS continuing progression.
    My Suggestions :
    * Create a MailingList to discuss/share, at-large, MANRS related issues and progress { I have read, somewhere in the website, that there is a mailing list. But, until now, I don’t know were it is :-/ } ;
    * Launch a #DeployAthon : #MANRSathon maybe 🙂 … The guys from the AFRINIC Capacity Development Team have done it for IPv6 Deployment, during #AIS2018;
    * …

    Regards,
    –sb.

    Reply
    • Andrei Robachevsky says

      June 19, 2018 at 1:12 pm

      Hi Sylvain,

      Thank you for the kind words.

      There is a mailinglist, although it is only available to the participants of the initiative. There are public fora for the discussion of broader routing security issues, such as RIPE’s routing WG, or NANOG. If there is an opportunity to report on MANRS and its progress, MANRS participants are encouraged to present this.

      Regarding the #MANRSathon – I’d like to explore this idea. If you could share your thoughts, please write to manrs at isoc.org.

      Thank you for your interest,

      Regards,

      Andrei

      Reply
      • Sylvain BAYA says

        June 20, 2018 at 6:42 am

        Alright Andrei,

        Regards,
        –sb.

        Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Recent Posts

  • You’ve Got Mail—MANRS Conformance Reports and Incident Reporting
  • Majority of Announced IPv6 Address Space Now Secured by ROAs
  • RFC 7911 – What happens when routers do not speak the same language
  • The US FCC Asked About Routing Security. Here’s what MANRS Participants Had to Say.
  • Announcing 2022 MANRS Fellows
MANRS logo
Join MANRS
  • Sharing Our Content
  • Terms of Use
  • Privacy Policy
  • Contact
Follow us: Follow MANRS on Twitter Follow MANRS on Facebook Follow MANRS on LinkedIn Follow MANRS on YouTube

MANRS Document © 2016–2022