Greetings Georgios and MANRS Community, Thank you for asking the clarifying questions. To your question 1 below (MANRS compared with IETF), I would say that the origin of MANRS was from the Operational community to find consensus for a collection of practices which, *particularly taken together*, would improve the overall profile of security for Internet routing. While IETF standards may be something that a particular vendor or software implementation might be compared against, MANRS is more a guidance that Operators could ask of each other. On point 2 below regarding consensus, I appreciate the reference document that you shared, and I believe it does a good job of describing the objectives. Thank you, Tony From: Manrs-community <manrs-community-bounces@elists.manrs.org> on behalf of Georgios Karagiannis via Manrs-community <manrs-community@elists.manrs.org> Reply-To: Georgios Karagiannis <georgios.karagiannis@huawei.com> Date: Monday, February 24, 2025 at 2:32 PM To: "manrs-community@elists.manrs.org" <manrs-community@elists.manrs.org> Subject: [EXTERNAL] [manrs-community] Comments - RE: Open Call for Comments on the MANRS Development Process Hi MANRS Community and MANRS Steering Committee, Please note that I have reviewed the MANRS Development Process (MDP) proposal, see: https://manrs.org/proposals/21421/<https://urldefense.com/v3/__https:/manrs.org/proposals/21421/__;!!CQl3mcHX2A!H7-AwN7bQUbj-EWjjxt0XAzsrykAsJHNnLYOReupHvKUw6QGxrBFSAfFBVqr8lUTIfsPwsueVnUEFP6m5TIe3QGZsZaUu7-s--NV$> I have two key comments on this proposal: 1. What is the difference between a MANRS standard and an IETF standard specification? It will be useful to provide a clearer definition for what a MANRS standard is and in particular, what is difference between a MANRS standard and an IETF routing security standard specification? 1. How can consensus on MANRS decisions can be measured? Is this similar to the IETF “rough” consensus definition, or? It will be useful to provide a clearer definition to what is meant by consensus. Is this similar to the IETF “rough” consensus definition, or? For example, see the IETF RFC 7282 “On Consensus and Humming in the IETF”, see: https://www.rfc-editor.org/rfc/rfc7282.txt<https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc7282.txt__;!!CQl3mcHX2A!H7-AwN7bQUbj-EWjjxt0XAzsrykAsJHNnLYOReupHvKUw6QGxrBFSAfFBVqr8lUTIfsPwsueVnUEFP6m5TIe3QGZsZaUu5JKDhV6$> Best regards, Georgios From: Manrs-community [mailto:manrs-community-bounces@elists.manrs.org] On Behalf Of Alejandro Fernández-Cernuda via Manrs-community Sent: Monday, February 10, 2025 15:54 To: manrs-community@elists.manrs.org Subject: [manrs-community] Open Call for Comments on the MANRS Development Process Dear MANRS Community: As some of you will know, the MANRS initiative has set a standardization process in motion, called the MANRS Development Process (MDP). You can have a detailed description of what we are planning to do in the following post from Tony Tauber, Chairman of the MANRS Steering Committee: https://manrs.org/2025/01/manrs-development-process/<https://urldefense.com/v3/__https:/manrs.org/2025/01/manrs-development-process/__;!!CQl3mcHX2A!H7-AwN7bQUbj-EWjjxt0XAzsrykAsJHNnLYOReupHvKUw6QGxrBFSAfFBVqr8lUTIfsPwsueVnUEFP6m5TIe3QGZsZaUu-oT7NIB$> The proposal has already been reviewed by both the MANRS Secretariat and the MANRS Steering Committee and it is now open for comments from the MANRS Community. The Call for Comments ends on February 28, 2025. Everybody is welcome to submit their feedback and discuss the proposal on the manrs-community mailing list. If you are not subscribed to the mailing list please send a request to contact@manrs.org<mailto:contact@manrs.org>. In order to raise awareness, facilitate the discussion, and answer any possible questions about the MDP that the community might have, we are organizing a double webinar next February 19. You can find the details below: · Webinar on the MANRS Development Process, Session East: February 19, 9:00 – 10:00 UTC (link to register<https://urldefense.com/v3/__https:/us06web.zoom.us/meeting/register/Y-B4YhiN...>) · Webinar on the MANRS Development Process, Session West: February 19, 21:00 – 22:00 UTC (link to register<https://urldefense.com/v3/__https:/us06web.zoom.us/meeting/register/ZJ19skUy...>) We are looking forward to seeing you there. Thanks for your continued support, • • • • Alejandro Fernández-Cernuda Díaz Director of Engagement, Internet Integrity Program Global Cyber Alliance afcernuda@globalcyberalliance.org<mailto:afcernuda@globalcyberalliance.org> +32 28823050 GCA Brussels Rond Point Schuman 6 1040 Brussels Belgium [Image removed by sender. GCA Website]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA Twitter]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA Facebook]<https://urldefense.com/v3/__https:/www.facebook.com/GlobalCyberAlliance/__;!...> [Image removed by sender. GCA LinkedIn]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA YouTube]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA GitHub]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA Email Signup]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA Instagram]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> [Image removed by sender. GCA Forums]<https://urldefense.com/v3/__https:/csvv404.na1.hs-sales-engage.com/Ctc/WZ*23...> GCA takes your privacy seriously. To review our privacy policy, please click here<https://urldefense.com/v3/__https:/www.globalcyberalliance.org/privacy-polic...>.