Re: [rtcweb] Proposed Video Selection Process

Justin Uberti <juberti@google.com> Thu, 21 November 2013 20:36 UTC

Return-Path: <juberti@google.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 43F411AE2F4 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 12:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] 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 V4vjsfr3TeaS for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 12:36:57 -0800 (PST)
Received: from mail-vb0-x22f.google.com (mail-vb0-x22f.google.com [IPv6:2607:f8b0:400c:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6C71AE2ED for <rtcweb@ietf.org>; Thu, 21 Nov 2013 12:36:56 -0800 (PST)
Received: by mail-vb0-f47.google.com with SMTP id x11so216471vbb.6 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 12:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=yd28zMIneX5j5fj06E0d5dBYXJNnnrJIomJMu6YP0YM=; b=FoBaWE/1zo0Slx6oSqW885LhMFSbTG/v6MC92/RXMI69kGkfvklyNZHANVhnNxoDrO GouVdiJ6uGDRC6fdDd8anO/fxsMqn5RKK211I6e9tn36TgSBceFTHx41EnQoEGxn2ZY+ OTNzDmoiuesJlr1fd8C1murkaLtZdxo0R3Zm93Kpmg3RQO7FFEZ+3KEQr5EL/Q/PoaRa vBLXAiLEOLH/H3nJ4gsMcB5fhuG2Zu4I7mdjqsPW6LzLkBtye6BFjwifIO9wmYK6WGP2 RbVhrq71atY/8jKtNQHJju44GEXCIrejC5T9ibFAr1YtuRP7k6OZZ31G5CCzzPsUzc42 tiQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=yd28zMIneX5j5fj06E0d5dBYXJNnnrJIomJMu6YP0YM=; b=mZ7LKX5iwouVNxhysicIUAV5HICy5GCrIK9AJmFrmAhYTZiF9lW8GAJnSVak/OBfyY OvcH9Wot1yVAbGHixifl6fVm/uYcIoYh8zTxyqM5lkEvP6UUu9DqWyWAfjB5n6flOoge X+RUe6atiaQ7wWrDiHUJyYBH3t5nnwnCBxSMHbHFndEm6YlhT/fdLAIA3qq0tdh+yf/f /Jmst9ECQJ+Z9r4xFlXw1syXVMRzY8fyQfRpFj8efSjRkkO5Qma3D6sxkwVn9HwkSDck jC/SAw2Z5m4K5dykHV7lOBJxEK7WJiBYe+wQzwHZO6idOTKORs6mvu5K4UIf0kSSZ0ty w5NA==
X-Gm-Message-State: ALoCoQk2Y8pLBXuueGR3oiN20jtBUMHT7D9do/vuBDX2DeZc2aUAqzQAJWLbVTUwrvq/We9J8hjDe/Kbpq3eX6mmt/s/DbdHtLxq0j3stHj5ZToFaadOU/x0q02IS2Lm9APXfRTSdVVQviWqLxVD534Fl+jeunsInoJtrwWoSAHvMO/C0gjW2iE1OPgguSeCZOm6iGR0UQuY
X-Received: by 10.221.51.206 with SMTP id vj14mr7563414vcb.17.1385066210007; Thu, 21 Nov 2013 12:36:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.110.101 with HTTP; Thu, 21 Nov 2013 12:36:29 -0800 (PST)
In-Reply-To: <7949EED078736C4881C92F656DC6F6C130EA8AD7E0@ausmsex00.austin.kmvtechnologies.com>
References: <528E69E2.9020208@librevideo.org> <7949EED078736C4881C92F656DC6F6C130EA8AD7E0@ausmsex00.austin.kmvtechnologies.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 21 Nov 2013 12:36:29 -0800
Message-ID: <CAOJ7v-151K2UoeMOhY-UUDzZwE=89qzbAQdrhQXYb72W+ZxQOw@mail.gmail.com>
To: Stefan Slivinski <sslivinski@lifesize.com>
Content-Type: multipart/alternative; boundary=001a11332252703f7e04ebb5db1e
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposed Video Selection Process
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, 21 Nov 2013 20:36:59 -0000

iOS doesn't expose APIs for said hardware decoding, so you're doing
software no matter what, and VP8 and H.264 are therefore on level ground.

That said, I think the general understanding here is that this is no longer
a technical decision.


On Thu, Nov 21, 2013 at 12:28 PM, Stefan Slivinski
<sslivinski@lifesize.com>wrote:

> So this is my concern.  On iOS for example it's pretty easy do decode
> large resolutions in software only using either h.264 or vp8 (and for that
> matter vp9 and h.265).  So making both h264 and vp8 decoders mandatory
> isn't a big technical problem.  The encoder however is a bigger issue.  A
> reasonably good implementation requires roughly 3x the compute to do this
> in software.  iOS however supports hardware encoding using H264 so there is
> an obvious advantage to using that specific codec on that device.  The same
> might be true for VP8 on other architectures.
>
> So requiring all webrtc implementations to support H264 and VP8 gives the
> flexibility to pick the most appropriate encoder for a given architecture.
>
>
> ----- Original Message -----
> From: Basil Mohamed Gohar [mailto:basilgohar@librevideo.org]
> Sent: Thursday, November 21, 2013 02:15 PM
> To: rtcweb@ietf.org <rtcweb@ietf.org>;
> Subject: Re: [rtcweb] Proposed Video Selection Process
>
> On 11/21/2013 03:02 PM, Stefan Slivinski wrote:
> > I in no way intended to suggest  a specific implementation of a video
> codec.  My question was around whether we are voting on requiring decoders
> (my assumption) or both encoders and decoders
>
> The discussions, up to this point, have been about choosing an MTI video
> format so that rtcweb endpoints can communicate with one-another.  I am
> not sure how this goal can be achieved without having an encoder and a
> decoder on both ends, sharing at least one common format, whether it is
> H.261, Theora, H.264, VP8, or something else.
>
> --
> Libre Video
> http://librevideo.org
> _______________________________________________
> 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
>