Re: Alternative decision process in RTCWeb

Dave Crocker <dhc@dcrocker.net> Thu, 28 November 2013 14:41 UTC

Return-Path: <dhc@dcrocker.net>
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 8540F1AE125 for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2013 06:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 bcNN0ULsW63C for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2013 06:41:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5981ADFB0 for <ietf@ietf.org>; Thu, 28 Nov 2013 06:41:52 -0800 (PST)
Received: from [10.211.51.212] (rbiguest.jcresorts.com [206.170.126.120] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rASEfgFL018045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Nov 2013 06:41:46 -0800
Message-ID: <529755F6.4050404@dcrocker.net>
Date: Thu, 28 Nov 2013 06:40:54 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>, Eliot Lear <lear@cisco.com>
Subject: Re: Alternative decision process in RTCWeb
References: <52970A36.5010503@ericsson.com> <529719D7.9020109@cisco.com> <CAKHUCzxjwMXzy6=9WdRPRRCunKsLm9JFuo6JavMtEC7Tbov8TQ@mail.gmail.com>
In-Reply-To: <CAKHUCzxjwMXzy6=9WdRPRRCunKsLm9JFuo6JavMtEC7Tbov8TQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 28 Nov 2013 06:41:48 -0800 (PST)
Cc: rtcweb-chairs@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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 14:41:53 -0000

On 11/28/2013 3:18 AM, Dave Cridland wrote:
> I think that two consensus calls should be taken at this stage:

I concur with the precedence concerns that have already been raised, and 
also wonder about trying to orchestrate a sequence of consensus calls 
designed to move the group through a process that will get some folk to 
change their positions, in order to get the matter resolved.

The simplest form of such a sequence that I've heard about is to note 
the impasse, then ask whether the group does want to get the matter 
resolve.  That's likely to get a strong rough consensus yes.  Then note 
it's not going to resolve until folk change their current positions. 
The example I heard about did then produce a preferred choice.

No doubt, the current situation has folk who are more tenacious, so 
perhaps the sequence of calls needs to be a bit more elaborate.

BTW, as distasteful as it might be, is there a reason that making /both/ 
MTI would not work?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net