[rtcweb] Why the Straw Poll

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 12 December 2013 01:09 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D041AD94A; Wed, 11 Dec 2013 17:09:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.502
X-Spam-Level:
X-Spam-Status: No, score=-109.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 Q9n4Wj4WOypr; Wed, 11 Dec 2013 17:09:56 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6AB1AE156; Wed, 11 Dec 2013 17:09:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2769; q=dns/txt; s=iport; t=1386810581; x=1388020181; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Pj+PtV0Et+kSwwkxFdxb+nakE/RI8g6DEGB/fqenr5c=; b=gKXOenv9cIfR6guTRveVf81Z8wXvB3bxDzOjdDytAGwVBbVzR96FkoLe +pRyFFrYCSzU7PvJI94xZAhDEg7SK3pzovYCinsLuKodLKdKdS+VGkA67 PikpEmW+/JZW1qVe0D5FVftJp+6B+NXw8pex+AyRHSl7qjm8Tj8U3M9nU E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAIULqVKtJV2b/2dsb2JhbABZgwc4U7hxToEcFnSCJQEBAQMBHVwFCwIBTjIlAgQOBQmHcwYNwi0XjiYQAgFPAgWDIYETBJNvhCWSE4MpgWgjHw
X-IronPort-AV: E=Sophos;i="4.93,875,1378857600"; d="scan'208";a="6129369"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP; 12 Dec 2013 01:09:40 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rBC19eS8014157 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Dec 2013 01:09:40 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.231]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Wed, 11 Dec 2013 19:09:39 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Thread-Topic: Why the Straw Poll
Thread-Index: AQHO9tbUki1D7g97NEKFTxdcgznMjA==
Date: Thu, 12 Dec 2013 01:09:39 +0000
Message-ID: <8ADFF7AF-FEBD-43D5-BB10-EAF53BB9F8BD@cisco.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A48441927F3A@TK5EX14MBXC295.redmond.corp.microsoft.com>
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A48441927F3A@TK5EX14MBXC295.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A4D6BC987F2B784A806459B286150036@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] Why the Straw Poll
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 01:09:59 -0000

Let me try and answer what I think is your central issue here which is: why are we spending any time on this topic. 

We have heard from a significant number of people that they think it is important for WebRTC devices and applicaitons to be able to know that video will work between devices. It was the number one requested item when speaking to the various developers with products demonstrated at WebRTC Expo and a significant issue on this email list. It is one of the several topics the chairs are driving forward. We plan to continue to do try to drive it to resolution. Note resolution includes consensus for no MTI. 

However, we perfectly well understand that you, or others, may not want to spend time on the video MTI issue. Feel free to ignore the email threads if you believe the outcome is inevitable and put your time into some of the other things we are also driving forward. 

Cullen in my co-chair role (and I'm not speaking for my co-chairs but I am pretty sure they also want to drive this issue to resolution) 


On Dec 9, 2013, at 4:32 PM, Matthew Kaufman (SKYPE) <matthew.kaufman@skype.net> wrote:

> I believe we are way off the acceptable process track here.
>  
> First, there was a discussion and a call for rough consensus at the last IETF in-person meeting. That call was not continued on the list, instead a lack of consensus was declared at the meeting.
>  
> Next, there was a proposal from the chairs to vote in a particular way, and a call for options on which to vote. It was claimed at that time that after the list was compiled, the act of taking such a vote would be taken to a consensus call. That never happened.
>  
> Instead the chairs are now conducting a “straw poll” of their own design, clearly in an effort to circumvent some very specific objections to the proposed instant-runoff vote with restricted participation. But again, instead of attempting to reach WG consensus for conducting such a poll, it has simply been foisted upon us.
>  
> I have not seen ANY replies to the message “Next Steps in Video Codec Selection Process” that indicate working group consensus of ANY KIND for conducting a poll in this format at this time or to follow the subsequent steps described in that message.
>  
> I am requesting that the chairs immediately suspend the “Straw Poll” described below until such time as there is Working Group consensus to spend the Working Group’s time and energy conducting the poll and/or to continue with the subsequent steps called out in “Next Steps in Video Codec Selection Process” at http://www.ietf.org/mail-archive/web/rtcweb/current/msg10448.html