Re: [rtcweb] Making both VP8 and H264 MTI

cowwoc <cowwoc@bbs.darktech.org> Tue, 05 November 2013 18:07 UTC

Return-Path: <cowwoc@bbs.darktech.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F7C21E809D for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 10:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.545
X-Spam-Level:
X-Spam-Status: No, score=-4.545 tagged_above=-999 required=5 tests=[AWL=-0.946, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1hXVYJibejG9 for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 10:06:52 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by ietfa.amsl.com (Postfix) with ESMTP id C99CC21E80EB for <rtcweb@ietf.org>; Tue, 5 Nov 2013 10:06:34 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id qd12so15437500ieb.5 for <rtcweb@ietf.org>; Tue, 05 Nov 2013 10:06:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8+k5IvjN8ZuPmY2olnUXkzZDUHC1ZicIcSVoLHtUVqk=; b=mHDk0VY6AjPLtOEEK/LSPADnLtSANw/W1IZsRxEh2f3XbjNIYfmPGT3qP9HVJCoDPs drEXH/bIvtiDKIU26pMZ/epPVdoKGS2gBEOX7EMaZVJ2pvsxRmVmT/DKEzpyxsLman/r bVcu30OIsRR7kytmNHv0mt1gU3rRPkEYOmLqIp6Cf1yIOfUYUzrZTDjLyyO7zJjTPMOS rixe9hjHuxdBkLNrqHppN09WpHDMTLv3E49L7MMB1bmht0YMn5PKmlSacS4BnqossPjX eOpcqKWe2HDmaSquN9IVQPw3HglzbVGBTJVf3WyvN3jIKF75nDERBvUBLfODVtfDc1pX OXSw==
X-Gm-Message-State: ALoCoQnwFhQpCVTmNwbqgJR2zsbmxHW6MxYkh3PwSfcNTe7d3OMPKDUZoEWmmgrvApJU/9C+bwpf
X-Received: by 10.43.60.139 with SMTP id ws11mr14023775icb.12.1383674782691; Tue, 05 Nov 2013 10:06:22 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id ka5sm9585364igb.2.2013.11.05.10.06.21 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Nov 2013 10:06:21 -0800 (PST)
Message-ID: <5279339B.9040506@bbs.darktech.org>
Date: Tue, 05 Nov 2013 13:06:19 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CE9E91B2.1BEAA%mzanaty@cisco.com> <8EB7C7F2-105D-4CFB-AC06-F8BB331A4736@cisco.com>
In-Reply-To: <8EB7C7F2-105D-4CFB-AC06-F8BB331A4736@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Making both VP8 and H264 MTI
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 05 Nov 2013 18:07:05 -0000
X-List-Received-Date: Tue, 05 Nov 2013 18:07:05 -0000

Cullen,

     In light of the fact that vendors are highly polarized on this 
topic, I'd like to suggest the following voting order:

1. Should *both* H.264 and VP8 be MTI?

If there is a consensus for yes, stop here.

2a. Should *only* H.264 be MTI? or,
2b. Should *only* VP8 be MTI?

If there is a consensus for either one, stop here.

3a. Should *only* H.261 be MTI? or,
3b. Should no codec be MTI? (this implies transcoding)

     Given the final choice (H.261 or no MTI) I suspect many vendors 
would choose H.261 and upgrade to H.264/VP8 at runtime. No one really 
wants to go back to the days of transcoding.

Gili

On 05/11/2013 12:44 PM, Cullen Jennings (fluffy) wrote:
> Right now there is no proposal on the table for the MTI to be both VP8 and H.264 and the deadline was back in October so it's not a topic the chairs feel ready to discuss in the thursday meeting.
>
> I will note that in the past when this idea was discussed, the people who were concerned about IPR for either codec pointed out that this could only increased, not decreased, the IPR concerns.
>
> The chairs are more concerned about neither choice being acceptable. If we found out that both are acceptable, that will be a good situation and we will find a reasonable way to proceed from there that is acceptable to the WG. Alternative process is the last resort. From a chair point of view, it really better if people actually honestly answer the question in a consensus call instead gaming the system.
>
> Cullen - Just one of the chairs and I hope my co-chairs add more but they are both in meetings right now
>
>
> On Nov 5, 2013, at 9:27 AM, "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
>   wrote:
>
>> This is an important point the chairs must clarify. If there is strong
>> support for both questions, will the chair interpret that as support for 2
>> MTIs, or declare no consensus, forcing us into alternative processes? I
>> support both as MTI. But if raising my hand twice increases the likelihood
>> of an alternative process, I will only support one (despite objecting to
>> being forced to support only one).
>>
>> Mo
>>
>>
>> On 11/5/13, 9:46 AM, Martin Thomson <martin.thomson@gmail.com> wrote:
>>
>> On 5 November 2013 06:18, Hutton, Andrew <andrew.hutton@unify.com> wrote:
>>> How would we conclude that the community would like both to be made MTI?
>>
>> If I were to pretend that I am a process wonk, I might say something
>> like: if the objections to both questions are weak AND if the
>> objectors are unable to find reasons that pass muster.
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb