Re: Alternative decision process in RTCWeb

Sam Hartman <hartmans-ietf@mit.edu> Thu, 28 November 2013 15:35 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA0C1AE183 for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2013 07:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
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 jAmJPUNWrqJq for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2013 07:35:13 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 608241ADBC9 for <ietf@ietf.org>; Thu, 28 Nov 2013 07:35:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id ADBCF205B7; Thu, 28 Nov 2013 10:34:30 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFSJAr_5Nbuf; Thu, 28 Nov 2013 10:34:29 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (c-50-136-31-107.hsd1.ma.comcast.net [50.136.31.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 28 Nov 2013 10:34:29 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 7EC8081946; Thu, 28 Nov 2013 10:35:09 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: Alternative decision process in RTCWeb
References: <52970A36.5010503@ericsson.com>
Date: Thu, 28 Nov 2013 10:35:09 -0500
In-Reply-To: <52970A36.5010503@ericsson.com> (Gonzalo Camarillo's message of "Thu, 28 Nov 2013 11:17:42 +0200")
Message-ID: <tsl4n6wk09e.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: IETF Discussion <ietf@ietf.org>, rtcweb-chairs@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 15:35:14 -0000

>>>>> "Gonzalo" == Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> writes:


Hi.  I've thought about the general issue of alternative decision making
a lot, and it did come up a number of times while I was an AD, although
none with such significant stakeholder interest as this.

The issue I'm most concerned about is confirming that there is rough
consensus to make a decision.  I think any variance from rough consensus
for decision making must itself meet a fairly high consensus bar.

"But we can't make a decision; we have to make a decision, so of course
we're going to do something alternative," you might say.

You don't have to make a decision though.  You can decide the IETF is
not the right forum for your decision.  You can decide not to
standardize.  You can decide to run experiments, get  data, try to
implement.  You can give up.
You can redefine the problem.  You can for example decide to have two
mandatory-to-implement options, or require receivers to implement both
and not mandate which senders must pick.

In many cases it does turn out to be easier to get consensus that a
decision must be made than it is to get consensus on a decision.
However without chairs being able to clearly show that consensus to
decide has been reached I'd expect an appeal and expect that appeal to
be successful.

Next, it's strongly desirable to get consensus on your process for
making the decision.
If you can get that, or lacking that, get consensus  on someone who will
decide the process (chairs or AD), I think you are coming along
reasonably.

Obviously concerns of fairness are important.  A process that inherently
advantaged one company or viewpoint would be suspect.

I'd personally favor coin-flips, external arbitors or similar over
voting.  We don't want to encourage voting because we could get into
situations where people block the consensus process in order to force a
vote.  Absent things like well-defined membership and procedures to
avoid one company stuffing the ballot box, going there seems
problematic.

Coin flips are nice.  They really create pressure among anyone who
actually cares about the outcome to compromise, to explore whether a
consensus can be built.  However for the frequent situations where a
decision is critical but it really doesn't matter (even if some people
think it does), they get the job done.