This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] what does consensus mean
- Previous message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] what does consensus mean
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Mon Jan 15 12:04:41 CET 2018
> On 15 Jan 2018, at 10:21, JORDI PALET MARTINEZ via address-policy-wg <address-policy-wg at ripe.net> wrote: > > > Obviously, I don’t agree, just because for me, “consensus” is having no objections Jordi, whatever definition of consensus someone chooses is up to them. That doesn't mean it's right or the one that everybody else has to adopt. [We decide the definition of consensus by consensus. :-)] Consensus does not mean there have to be no objections. That's unanimous consensus. There's a difference. An important difference. Maybe something is getting lost in translation? ie the Spanish for "consensus" means something similar to the definition you're using. There can be consensus in RIPE (and other fora such as IETF and ICANN) even when there are objections. RFC7282 goes into this in great detail. If we relied on unanimous consensus for decisions, nothing would ever get done because anyone would have a veto that could block progress. And in a very diverse community like RIPE, it'll be impossible for everyone to agree on everything.
- Previous message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] what does consensus mean
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]