Re: [rtcweb] Stephan Wenger's choices

cowwoc <cowwoc@bbs.darktech.org> Mon, 30 December 2013 18:04 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 C11AE1AE2CA for <rtcweb@ietfa.amsl.com>; Mon, 30 Dec 2013 10:04:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Qy3QdZa1kmO9 for <rtcweb@ietfa.amsl.com>; Mon, 30 Dec 2013 10:04:46 -0800 (PST)
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by ietfa.amsl.com (Postfix) with ESMTP id 9004F1AE29F for <rtcweb@ietf.org>; Mon, 30 Dec 2013 10:04:46 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so12341092iej.12 for <rtcweb@ietf.org>; Mon, 30 Dec 2013 10:04:40 -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=rqVzjUcjwFCa+rvBRpjFT5iIdb1PnXohWTB87JHXHes=; b=GoWHT/5tl9R19XQyRptNOT2hHD599Msh4ij9D8iVF8d9WJ3zYdJeJSF80YH/5sgacv X6QmAiG2N8lXE9npZwsiGXTVWppaZoe+i0O7Wc7hXx8xBz4a1Y1z0xKuGOypykcBSzGi pf0yeIUegyVQqFSK+2uQH6jSsPzewL9obFUieN2ycyWSiy8ARAtD3s8u+f30bcO4J0Cs sZlAagqiD/R4khtEW9BVd0wxap1JIwyHJLA3QURfkLo0AiFY6yQd0oiEF1uaV5VaCXpP B727w7szoXWeBHlo5i3w/WlBf/rasAgJGzMWaeWSmQg4uGew06zliONCzu3WGO1cJbex QO+g==
X-Gm-Message-State: ALoCoQkOoVcbhNvRcKrUTXFwO/juf35gEAq96g4kBSu1yLvDPfdb8a7Qrd6FOfDIc79nG1hkXdgb
X-Received: by 10.50.136.201 with SMTP id qc9mr57712260igb.11.1388426680498; Mon, 30 Dec 2013 10:04:40 -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 d18sm46184701igz.0.2013.12.30.10.04.39 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 30 Dec 2013 10:04:39 -0800 (PST)
Message-ID: <52C1B591.2010504@bbs.darktech.org>
Date: Mon, 30 Dec 2013 13:04:01 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <52BF037D.4050706@googlemail.com> <CEE4479F.3E568%stewe@stewe.org> <20131228183148.GI3245@audi.shelbyville.oz> <CABcZeBOMEE9nOMzR2AisGQDTByrjsNms6qS4+DQvjUMUYyHCjw@mail.gmail.com> <20131228212423.GJ3245@audi.shelbyville.oz> <CABcZeBNwMPjGFZV08DV8ZFrJg0N+Lr8zD=CwUY2qxrCqw8MWdA@mail.gmail.com> <20131228230333.GK3245@audi.shelbyville.oz> <CABcZeBPBXT-4UqYyTVNjGBL5wo-n0qisMC2bj+=E115YQ8m8aQ@mail.gmail.com>
In-Reply-To: <CABcZeBPBXT-4UqYyTVNjGBL5wo-n0qisMC2bj+=E115YQ8m8aQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Stephan Wenger's choices
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: Mon, 30 Dec 2013 18:04:47 -0000

On 28/12/2013 6:17 PM, Eric Rescorla wrote:
>> We can joke about absurdities, but I'm completely serious about the real
>> benefits that a low-complexity, tiny-footprint, completely accessible
>> codec would have as the MTI.
> Yes, I realize you're serious. But it turns out that there is a difference
> between seriously believing something and actually convincing
> people.
>
> So far you have yet to convince me, at least, that it's better
> for users to have an MTI bad codec on every device than to have
> an MTI good codec on most devices and no video on really low-end
> devices.
Eric,

Here is what I don't get: On the one hand we're being told that we 
should choose H.264 as MTI because it's supported by most legacy or 
resource-constrained/mobile devices; on the other hand, the majority of 
those same devices don't support H.264 encoding in hardware (and never 
will). It just so happens that we can deploy WebRTC on legacy devices 
using an older codec, such as H.261, but that's being rejected as too old.

I'm hearing contradictory messages here. What is our top priority? 
Supporting legacy devices, or video quality? Because it doesn't seem 
like you can have both.

What am I missing here?

Gili