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/address-policy-wg@ripe.net/
[address-policy-wg] Consensus
- Previous message (by thread): [address-policy-wg] Complaint and future of the APWG.
- Next message (by thread): [address-policy-wg] Complaint and future of the APWG.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri Jun 12 10:24:36 CEST 2015
On 12 Jun 2015, at 09:10, h.lu at anytimechinese.com wrote: > But to my understanding how things works here, Chair can not declare consensus if there are still people disagree(and in this case, real or fake, many of them) You're wrong. The generally accepted definition of consensus is lack of sustained, reasonable objection. This does not mean everyone has to agree: that's unanimity. A consensus determination does not mean there are no objections either. Some people may well disagree with a proposal. That does not give them a veto on the proposal and their objection(s) don't necessarily block the WG from reaching consensus. I suggest you read RFC7282. Although this documents how the IETF defines consensus, much of that applies to other similar organisations and communities such as RIPE.
- Previous message (by thread): [address-policy-wg] Complaint and future of the APWG.
- Next message (by thread): [address-policy-wg] Complaint and future of the APWG.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]