Greetings Andrei and MANRS Community, To give my input on the questions you raise below, I believe for an Implementation Guide or similar (per your example) a MANRS Last Call should not be necessary. However, I don’t feel very strongly about that. On the question of handling errata, I would prefer that all be kept together. Hence, when an errata and correction applies, just put the edit (with suitable history and context) right into the document itself, not keep it separately as the IETF RFC Editor has chosen to do. Thanks, Tony From: Manrs-community <manrs-community-bounces@elists.manrs.org> on behalf of Andrei Robachevsky via Manrs-community <manrs-community@elists.manrs.org> Reply-To: Andrei Robachevsky <arobachevsky@globalcyberalliance.org> Date: Monday, February 24, 2025 at 10:18 AM To: "manrs-community@elists.manrs.org" <manrs-community@elists.manrs.org> Subject: [EXTERNAL] Re: [manrs-community] Open Call for Comments on the MANRS Development Process Dear community members, Many thanks to those who were able to join the webinar last week. If you won't be able to join, you can find the recording here: https://manrs.org/2025/02/mdp-webinars/<https://urldefense.com/v3/__https:/manrs.org/2025/02/mdp-webinars/__;!!CQl3mcHX2A!FPYHZtwFNA87VZJiOwhhCindR2808DwElgtnhyory8WG2l8py-P5F6SaCiJi43-MPwfR6WUb8VEK2WN1qtdhZiK4e-E5HjG-_AE$> During the webinar I brought up a few points regarding the MDP proposal itself that might require your consideration and comment. I am providing them here: 1. We talked about the rationale for having a separate MANRS Last Call to measure the consensus among the MANRS participants on the proposal as the final stage before its ratification. The main reason for this is that while the community Call for Comments is aimed at collecting as broad feedback as possible, the standard may have an immediate impact on the MANRS Participants, therefore, it is important to receive an explicit approval from them. The MANRS Last Call serves this purpose. But is this phase always necessary? Obviously yes, when we talk about "normative" specifications which contain requirements mandatory for the MANRS participants. But is it also needed when we work on an "informational" document, like an implementation guide? 2. Handling of errata. The proposal suggests the IESG document “IESG Processing of RFC Errata for the IETF Stream” https://datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-20210507/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-20210507/__;!!CQl3mcHX2A!FPYHZtwFNA87VZJiOwhhCindR2808DwElgtnhyory8WG2l8py-P5F6SaCiJi43-MPwfR6WUb8VEK2WN1qtdhZiK4e-E58MerQ2U$> as guidance for this. One question, though, is how we want to reflect the errata in the specification itself. In the IETF world the specification isn't corrected and one has to look at the specification and the errata next to each other to read the spec correctly. Should we do the same, or correct the reported mistakes in the specification along with keeping the errata report? Let me leave you with these two questions and ask you for your opinions on these. Thanks, Andrei On 13/02/2025 19:48, Alejandro Fernández-Cernuda via Manrs-community wrote: Dear MANRS Community: As announced earlier this week, we have set the MANRS Development Process (MDP)<https://urldefense.com/v3/__https:/manrs.org/2025/01/manrs-development-proce...> in motion. It is a very important step for the future of the initiative, so we would really like to have your feedback on it. At this moment, the initial 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. This Call for Comments ends on February 28, 2025, in just a couple of weeks from now. 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>. And please consider registering for any of the two webinars on the MDP that we are offering to the community next week, on 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...>) I will send a new reminder next week. Please do not hesitate to support our dissemination efforts by forwarding this information to your own networks. 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...>.