RFC 7282: On Consensus and Humming in the IETF
In plain English — editorial summary, not part of the RFC
The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF participants and coming to (at least rough) consensus on technical matters. In particular, the IETF is supposed not to be run by a "majority rule" philosophy. This is why we engage in rituals like "humming" instead of voting. However, more and more of our actions are now indistinguishable from voting, and quite often we are letting the majority win the day without consideration of minority concerns. This document explains some features of rough consensus, what is not rough consensus, how we have gotten away from it, how we might think about it differently, and the things we can do in order to really achieve rough consensus. Note: This document is quite consciously being put forward as Informational. It does not propose to change any IETF processes and is therefore not a BCP. It is simply a collection of principles, hopefully around which the IETF can come to (at least rough) consensus.
Document record
- Document ID
- RFC7282
- Published
- June 2014
- Authors
- P. Resnick
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7221Handling of Internet-Drafts by IETF Working GroupsCurrent
April 2014
- RFC 8659DNS Certification Authority Authorization (CAA) Resource RecordCurrent
November 2019
- RFC 8874Working Group GitHub Usage GuidanceCurrent
August 2020
- RFC 5434Considerations for Having a Successful Birds-of-a-Feather (BOF) SessionCurrent
February 2009
- RFC 5317Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport ProfileCurrent
February 2009
- RFC 4832Security Threats to Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 3239Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative OperationsCurrent
February 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?