You are here: Home > Participate > Join a Discussion > RIPE Forum
RIPE Forum v1.4.1

Best Current Operational Practices (BCOP) Task Force

Threaded
Collapse

[bcop] RIPE 706 Wording

User Image

James Blessing

2018-08-01 11:38:38 CET

Hi,

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.

In reference to :

3.3 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 routingmanifesto.org website, and you can contribute to this
document and others like it.

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.

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.

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...

Thx

J

-- 

James Blessing
07989 039 476
User Image

Benno Overeinder

2018-08-03 00:08:13 CET

Hi James,

Thanks you for your feedback.

Only replying on your second comment, the authors and 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.

Best regards,

-- Benno


--
Benno J. Overeinder
NLnet Labs
https://www.nlnetlabs.nl/

> Op 1 aug. 2018 om 11:38 heeft James Blessing <james.blessing _at_ despres.co _dot_ uk> het volgende geschreven:
> 
> Hi,
> 
> 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.
> 
> In reference to :
> 
> 3.3 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 routingmanifesto.org website, and you can contribute to this document and others like it.
> 
> 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.
> 
> 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. 
> 
> 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...
> 
> Thx
> 
> J
> 
> -- 
> 
> James Blessing
> 07989 039 476