<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi James,</div><div><br></div><div>Thanks you for your feedback.</div><div><br></div><div>Only replying on your second comment, <span style="background-color: rgba(255, 255, 255, 0);">the authors and </span>we (BCOP TF attendees) deliberately opted for a static extended abstract of the MANRS to be published as a RIPE document, and a living document on the MANRS website. It is of course a wish or intend to keep them consistent, but the extended abstract discuss the values and principles which should be to some extent constant. The living document on the website fills in the details, the actions, etc., that are not in the RIPE document.</div><div><br></div><div>Best regards,</div><div><br></div><div>-- Benno</div><div><br></div><div><br><div>--<div>Benno J. Overeinder</div><div>NLnet Labs</div><div><a href="https://www.nlnetlabs.nl/">https://www.nlnetlabs.nl/</a></div></div></div><div><br>Op 1 aug. 2018 om 11:38 heeft James Blessing <<a href="mailto:james.blessing@despres.co.uk">james.blessing@despres.co.uk</a>> het volgende geschreven:<br><br></div><blockquote type="cite"><div><div dir="ltr">Hi,<div><br></div><div>First of all, this is not a comment about MANRS but the published document RIPE706 and is a question of wordsmithing rather than anything else.</div><div><br></div><div>In reference to :<div><br></div><div>3.3 <span style="color:rgb(51,51,51);font-family:"Open Sans",Helvetica,Arial,sans-serif;font-size:14.3px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Network operators who agree to the Principles and implement at least one of the Actions (though not solely the Coordination Action) can become a MANRS Participant. This entitles you to use of the MANRS badge, you will be listed on the <a href="http://routingmanifesto.org">routingmanifesto.org</a> website, and you can contribute to this document and others like it.</span></span></div><div><br></div><div>As I read that clause it says to make changes to RIPE706 then you *must* first be a MANRS signee, I assume the intent was to transpose the original MANRS documents with as few changes as possible, but in doing so the reference to "this document" should have been updated to point at the original version.</div><div><br></div><div>If however, it's an intentional attempt to restrict changes to RIPE706 to a subset of the RIPE community then this is a dangerous precedent to set and we should challenge this assertion. </div><div><br></div><div>And secondly (and maybe more importantly) we now have two documents that (the original MANRS and RIPE706) that, whilst are currently in sync have no explicit method for updating and cross checking. I thought we'd all learnt the hard way that we should always have a single source of truth...</div><div><br></div><div>Thx</div><div><br></div><div>J</div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div class="gmail_signature"><br>James Blessing<br>07989 039 476</div></div></div></div> </div></blockquote></body></html>