RFC 7282 on On Consensus and Humming in the IETF

rfc-editor@rfc-editor.org Mon, 23 June 2014 20:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1621B2B1D for <ietf-announce@ietfa.amsl.com>; Mon, 23 Jun 2014 13:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.453
X-Spam-Level:
X-Spam-Status: No, score=-103.453 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MIdxSPaZigXL for <ietf-announce@ietfa.amsl.com>; Mon, 23 Jun 2014 13:48:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4E84C1A0350 for <ietf-announce@ietf.org>; Mon, 23 Jun 2014 13:48:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C239018000E; Mon, 23 Jun 2014 13:46:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7282 on On Consensus and Humming in the IETF
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140623204651.C239018000E@rfc-editor.org>
Date: Mon, 23 Jun 2014 13:46:51 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/gos-xgClFZ3Cx0nx2zhglhARSeI
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 20:48:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7282

        Title:      On Consensus and Humming in the IETF 
        Author:     P. Resnick
        Status:     Informational
        Stream:     IETF
        Date:       June 2014
        Mailbox:    presnick@qti.qualcomm.com
        Pages:      19
        Characters: 52339
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-resnick-on-consensus-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7282.txt

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.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC