About "consensus" and "voting"...
Hi Suresh, Gert, All, "member organizations represented by" -- this only happens at the RIPE NCC GM, twice a year. The PDP doesn't happen at the RIPE NCC GM, afaik, whether we like it or not. When polarisation is obvious, "consensus" is impossible and everything tend to remain as is... Cheers, Carlos On Sat, 9 May 2020, Suresh Ramasubramanian wrote:
In a case where the community is polarised to this extent it would be better to break with procedure and call a vote for once. With member organizations represented by their abuse team heads, rather than IP / routing people, so that the organisation?s stance on this is clear.
From: Gert Doering <gert@space.net> Date: Saturday, 9 May 2020 at 3:57 PM To: Suresh Ramasubramanian <ops.lists@gmail.com> Cc: Randy Bush <randy@psg.com>, Nick Hilliard <nick@foobar.org>, anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net> Subject: Re: [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Hi,
On Sat, May 09, 2020 at 01:12:32AM +0000, Suresh Ramasubramanian wrote:
Has this even been put to a vote or is it the same group of extremely vocal RIPE regulars against it and the same group of extremely vocal security types for it? Rough consensus has its limitations in such cases.
There is no voting.
It's either "there is sufficient support and counterarguments have been adequately addressed" or "no consensus, rewrite or withdraw".
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
I am aware of this and aware that calling for a vote on any such matter would be a significant departure from procedure. Having one might at least lay this discussion to rest once and for all. I’ve seen variants of it for several years now. From: Carlos Friaças <cfriacas@fccn.pt> Date: Saturday, 9 May 2020 at 6:10 PM To: Suresh Ramasubramanian <ops.lists@gmail.com> Cc: Gert Doering <gert@space.net>, anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net> Subject: About "consensus" and "voting"... Hi Suresh, Gert, All, "member organizations represented by" -- this only happens at the RIPE NCC GM, twice a year. The PDP doesn't happen at the RIPE NCC GM, afaik, whether we like it or not. When polarisation is obvious, "consensus" is impossible and everything tend to remain as is... Cheers, Carlos On Sat, 9 May 2020, Suresh Ramasubramanian wrote:
In a case where the community is polarised to this extent it would be better to break with procedure and call a vote for once. With member organizations represented by their abuse team heads, rather than IP / routing people, so that the organisation?s stance on this is clear.
From: Gert Doering <gert@space.net> Date: Saturday, 9 May 2020 at 3:57 PM To: Suresh Ramasubramanian <ops.lists@gmail.com> Cc: Randy Bush <randy@psg.com>, Nick Hilliard <nick@foobar.org>, anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net> Subject: Re: [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Hi,
On Sat, May 09, 2020 at 01:12:32AM +0000, Suresh Ramasubramanian wrote:
Has this even been put to a vote or is it the same group of extremely vocal RIPE regulars against it and the same group of extremely vocal security types for it? Rough consensus has its limitations in such cases.
There is no voting.
It's either "there is sufficient support and counterarguments have been adequately addressed" or "no consensus, rewrite or withdraw".
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Suresh Ramasubramanian wrote on 09/05/2020 15:23:
Having one might at least lay this discussion to rest once and for all. I’ve seen variants of it for several years now.
But imagine if someone contacted a bunch of their colleagues and said: "look, there's this policy proposal going on in RIPE AAWG and it would be really great if you could just join up on the mailing list and add in a +1, thanks!" Therein lies the problem - or at least one of the problems - with voting: it's wide open to manipulation. There is another way of looking at this stalemate though: there's a policy development process and it produces outcomes. The outcomes may not be what some individuals on the WG want, but they are clear outcomes all the same. In the sense that you're concerned that there's stalemate regarding some of these proposals, there isn't according to the PDP: no consensus is a legitimate and clear outcome, and when there is no consensus, the policy does not proceed. So the issue is more: why are newer versions of this policy proposal returning repeatedly, and are they dealing adequately with the things that are blocking consensus? It's surprising to see a third iteration of this policy proposal - the first two versions didn't look like they were going anywhere. But resubmitting new versions is an issue between the WG chairs and the proposer. Nick
Hi, On Sat, 9 May 2020, Nick Hilliard wrote:
Suresh Ramasubramanian wrote on 09/05/2020 15:23:
Having one might at least lay this discussion to rest once and for all. I?ve seen variants of it for several years now.
But imagine if someone contacted a bunch of their colleagues and said: "look, there's this policy proposal going on in RIPE AAWG and it would be really great if you could just join up on the mailing list and add in a +1, thanks!"
Therein lies the problem - or at least one of the problems - with voting: it's wide open to manipulation.
Same goes for "it takes only 2 or 3 voices to break consensus". Even if arguments are somewhat "creative"...
There is another way of looking at this stalemate though: there's a policy development process and it produces outcomes. The outcomes may not be what some individuals on the WG want, but they are clear outcomes all the same.
In the sense that you're concerned that there's stalemate regarding some of these proposals, there isn't according to the PDP: no consensus is a legitimate and clear outcome, and when there is no consensus, the policy does not proceed.
The *proposal* does not proceed... the policy can already be in place, but remains unchanged.
So the issue is more: why are newer versions of this policy proposal returning repeatedly, and are they dealing adequately with the things that are blocking consensus?
It may, for those trying to accomodate "creative" arguments. For those which may be impacted by rules changing, certainly they won't see it as "adequate".
It's surprising to see a third iteration of this policy proposal - the first two versions didn't look like they were going anywhere. But resubmitting new versions is an issue between the WG chairs and the proposer.
That's the PDP. You can also try to change it, to prevent 3rd, 4th, 5th, 6th, 7th, and so on versions, but i suspect consensus might not be easy to achieve :-) Regards, Carlos
Nick
Hi Carlos, Carlos Friaças wrote on 09/05/2020 22:25:
On Sat, 9 May 2020, Nick Hilliard wrote:
Suresh Ramasubramanian wrote on 09/05/2020 15:23:
Having one might at least lay this discussion to rest once and for all. I?ve seen variants of it for several years now.
But imagine if someone contacted a bunch of their colleagues and said: "look, there's this policy proposal going on in RIPE AAWG and it would be really great if you could just join up on the mailing list and add in a +1, thanks!"
Therein lies the problem - or at least one of the problems - with voting: it's wide open to manipulation.
Same goes for "it takes only 2 or 3 voices to break consensus".
Even if arguments are somewhat "creative"...
no, and in fact this is the point of consensus. It depends on informed judgement and assessment, not a handful of dissenting voices, or people shouting, or votes or anything else. It's worth reading RFC 7282. There is a lot of wisdom in that document.
In the sense that you're concerned that there's stalemate regarding some of these proposals, there isn't according to the PDP: no consensus is a legitimate and clear outcome, and when there is no consensus, the policy does not proceed.
The *proposal* does not proceed... the policy can already be in place, but remains unchanged.
The existing reached consensus despite a number of dissenting voices :-) Personally, I think the policy does more harm than good, but it is what it is. I'm not going to put in a proposal to remove it because that probably wouldn't reach consensus and it would end up wasting working group time. Nick
Hi Nick, all, In many situations "rough consensus" was reached after many versions. Sometimes is a matter of finding the right balance, "the point in the middle" I was referring before. Even if it takes 10 versions instead of just 2. The issue is for the chairs, not an easy task, in the way to determine if objections are valid. Objections aren't just a matter of "taste", which is not valid, as very well described in RFC7282. Regards, Jordi @jordipalet El 9/5/20 23:36, "anti-abuse-wg en nombre de Nick Hilliard" <anti-abuse-wg-bounces@ripe.net en nombre de nick@foobar.org> escribió: Hi Carlos, Carlos Friaças wrote on 09/05/2020 22:25: > On Sat, 9 May 2020, Nick Hilliard wrote: >> Suresh Ramasubramanian wrote on 09/05/2020 15:23: >>> Having one might at least lay this discussion to rest once and for >>> all. I?ve seen variants of it for several years now. >> >> But imagine if someone contacted a bunch of their colleagues and said: >> "look, there's this policy proposal going on in RIPE AAWG and it would >> be really great if you could just join up on the mailing list and add >> in a +1, thanks!" >> >> Therein lies the problem - or at least one of the problems - with >> voting: it's wide open to manipulation. > > Same goes for "it takes only 2 or 3 voices to break consensus". > > Even if arguments are somewhat "creative"... no, and in fact this is the point of consensus. It depends on informed judgement and assessment, not a handful of dissenting voices, or people shouting, or votes or anything else. It's worth reading RFC 7282. There is a lot of wisdom in that document. >> In the sense that you're concerned that there's stalemate regarding >> some of these proposals, there isn't according to the PDP: no >> consensus is a legitimate and clear outcome, and when there is no >> consensus, the policy does not proceed. > > The *proposal* does not proceed... the policy can already be in place, > but remains unchanged. The existing reached consensus despite a number of dissenting voices :-) Personally, I think the policy does more harm than good, but it is what it is. I'm not going to put in a proposal to remove it because that probably wouldn't reach consensus and it would end up wasting working group time. Nick ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
I don’t need to imagine it. I have seen it happen more than once and chalked it up to just how some communities work. The number of other wg chairs and various other ripe regulars that suddenly found themselves in the aawg room, probably for the first time for most of them, during an AOB session introduced agenda item to boot Richard Cox from his co chair role was one such example. --srs ________________________________ From: Nick Hilliard <nick@foobar.org> Sent: Sunday, May 10, 2020 12:09:08 AM To: Suresh Ramasubramanian <ops.lists@gmail.com> Cc: anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net> Subject: Re: [anti-abuse-wg] About "consensus" and "voting"... Suresh Ramasubramanian wrote on 09/05/2020 15:23:
Having one might at least lay this discussion to rest once and for all. I’ve seen variants of it for several years now.
But imagine if someone contacted a bunch of their colleagues and said: "look, there's this policy proposal going on in RIPE AAWG and it would be really great if you could just join up on the mailing list and add in a +1, thanks!" Therein lies the problem - or at least one of the problems - with voting: it's wide open to manipulation. There is another way of looking at this stalemate though: there's a policy development process and it produces outcomes. The outcomes may not be what some individuals on the WG want, but they are clear outcomes all the same. In the sense that you're concerned that there's stalemate regarding some of these proposals, there isn't according to the PDP: no consensus is a legitimate and clear outcome, and when there is no consensus, the policy does not proceed. So the issue is more: why are newer versions of this policy proposal returning repeatedly, and are they dealing adequately with the things that are blocking consensus? It's surprising to see a third iteration of this policy proposal - the first two versions didn't look like they were going anywhere. But resubmitting new versions is an issue between the WG chairs and the proposer. Nick
participants (4)
-
Carlos Friaças
-
JORDI PALET MARTINEZ
-
Nick Hilliard
-
Suresh Ramasubramanian