Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Rough consensus
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{short description|Term used in consensus decision-making}} {{Undue weight|date=June 2023}} '''Rough consensus''' is a term used in [[consensus decision-making]] to indicate the "sense of the group" concerning a particular matter under consideration. It has been defined as the "dominant view" of a group as determined by its [[chairperson]]. The term was used by the [[Internet Engineering Task Force]] (IETF) in describing its procedures for [[working group]]s (WGs). The means to establish rough consensus was described by the IETF as follows:<ref>RFC 2418 - IETF Working Group Guidelines and Procedures. 1998</ref> <blockquote>Working groups make decisions through a "rough consensus" process. IETF consensus does not require that all participants agree although this is, of course, preferred. In general, the dominant view of the working group shall prevail. (However, "dominance" is not to be determined on the basis of volume or persistence, but rather a more general sense of agreement). Consensus can be determined by a show of hands, humming, or any other means on which the WG agrees (by rough consensus, of course). Note that 51% of the working group does not qualify as "rough consensus" and 99% is better than rough. It is up to the Chair to determine if rough consensus has been reached (IETF Working Group Guidelines and Procedures).</blockquote> The phrase is often extended into the saying "rough consensus and running code",<ref>{{cite web |title=The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force |url=https://www.ietf.org/participate/tao/ |publisher=[[Internet Engineering Task Force]] |archive-url=https://web.archive.org/web/20240524052427/https://www.ietf.org/participate/tao/ |archive-date=2024-05-24}}</ref> to make it clear that the IETF is interested in practical, working systems that can be quickly implemented. There is some debate as to whether running code leads to rough consensus or vice versa. There is also caution about whether percentages are a good measure for rough consensus. The IETF published a subsequent document pointing out that supporting percentage is less important for determining "rough consensus" than ensuring opposing views are addressed.<ref>{{Cite web|url=https://tools.ietf.org/html/rfc7282|title=RFC 7282: On Consensus and Humming in the IETF|last=Resnick|first=Pete|date=June 2014 |publisher=Internet Engineering Task Force|access-date=2016-03-17}}</ref> ==References== <references/> [[Category:Working groups]] [[Category:Consensus]] {{vocab-stub}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Cite web
(
edit
)
Template:Short description
(
edit
)
Template:Undue weight
(
edit
)
Template:Vocab-stub
(
edit
)