Evolving MANRS Development Process
"Learn about the collaborative approach of MANRS for routing security and the formal document process for developing and maintaining MANRS documents, enhancing transparency and credibility within the community."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Evolving MANRS: New Development Process and Document Review 1
A collaborative approach: Mutually Agreed Norms for Routing Security (MANRS, https://manrs.org/ ) An undisputed minimum security baseline the norm. Defined through MANRS Actions Demonstrated commitment by the participants Measured by the Observatory and published on https://www.manrs.org 2
The foundational pieces NetOps Program Actions CDN&Cloud Program Actions Vendor Program Actions Charter IXP Program Actions Defines roles and responsibilities of various entities in the MANRS ecosystem and the governance structure Define the baseline requirements for the participants of the program Define the baseline requirements for the participants of the program Define the baseline requirements for the participants of the program Define the baseline requirements for the participants of the program Common ROA Management Requirements and Security Standards for Operators of RPKI Services NetOps Implementation Guide IXP Implementation Guide Provides guidance on how to deploy the measures required by MANRS and is targeted at stub networks and small providers. Provides guidance on how to deploy the measures required by MANRS and is targeted at Internet eXchange Points. Provides guidance for the operators of RPKI services (ORS) 3
MANRS is maturing In developing MANRS we as a community have always strived for transparency, inclusion and consensus: working groups, task forces, community last calls To expand its impact further we need a formal process of how MANRS documents normative (e.g. MANRS Actions) and informational (e.g. MANRS Implementation Guides) are developed, adopted and maintained. Increase credibility, transparency and inclusiveness A formal documented process for developing and modifying MANRS documents MANRS Actions, MANRS Charter, etc. Introduce a formal document series Provides stable references and version control, making it easier to refer to it in external documents Participants==Community Participants==Community 4
How we develop, adopt and maintain MANRS documents: The MANRS Development Process 5
The MDP in a nutshell Approval and Approval and Publication Publication Proposal Proposal Announcement Announcement Development Development Public Comment Public Comment https://manrs.org/manrs-development-process/ 6
MANRS Actions areas for update 16% 5% NetOps Action 1 explicitly require ROV? 11% NetOps Action 4 RPKI mandatory? 68% IXP Action 1 require using auth IRRs? Ready Aspiring Lagging Lagging 0% RPKI Pick up some requirements from the MANRS+ Control Matrix? BGP session protection Peerlock More elaborate audit requirements Spoofed traffic trace-back 9
Stay tuned and participate: https://www.manrs.org FOLLOW US: /RoutingMANRS 11
