Re: [rtcweb] VP8 vs H.264 - the core issue

Ted Hardie <ted.ietf@gmail.com> Thu, 24 October 2013 14:30 UTC

Return-Path: <ted.ietf@gmail.com>
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 CE73811E831E for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 07:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 R6A1uV8bRoxV for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 07:30:14 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E583711E818A for <rtcweb@ietf.org>; Thu, 24 Oct 2013 07:30:02 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so3944116iec.20 for <rtcweb@ietf.org>; Thu, 24 Oct 2013 07:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BC+fZamLnqb/g+XlqqJyD3/kciQ4rlAb+JMHRqp6ZM0=; b=YItYiF++uPafADttny8fPVgQQ2MPkl0bIdZG1Ch2ckPC4hyodNvqtJt44vZUB8LUTX dnlHGbqj/GjtBCaTECQkV7i+dUAB669hU+MZTiB96fyTf8a0Lugg0TPf5YuNGpARYVQg BRyfBL8OZ8s+2vcE17YlwGvdvsWxm1FCgxnF7qaPfN7Zm8DI+LyhJsT4CLN5ootFqcTZ XG+0mVAlKj1YF2YEFWPVPustZkG2myra1zXDWWtEDd3VsGoW6qCN0JwL4ZqU1CopmBa4 IuvDg+guAMjEucgt1YkEBx44DJ4gbTVTXSFUe5B+ZgUmPDs4NMXHBO4xTghJT5hqteQQ kngw==
MIME-Version: 1.0
X-Received: by 10.42.18.136 with SMTP id x8mr1787264ica.11.1382625002383; Thu, 24 Oct 2013 07:30:02 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Thu, 24 Oct 2013 07:30:02 -0700 (PDT)
In-Reply-To: <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se>
References: <52681A96.2020904@alvestrand.no> <526826AF.5030308@librevideo.org> <52690090.2050609@alvestrand.no> <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se>
Date: Thu, 24 Oct 2013 07:30:02 -0700
Message-ID: <CA+9kkMAYuBH9VA=QhkLfe5gCJvwS24HgnVuyomAidUAfu6=f2A@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Bo Burman <bo.burman@ericsson.com>
Content-Type: multipart/alternative; boundary="20cf303f69101ff40d04e97d78c7"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
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: Thu, 24 Oct 2013 14:30:15 -0000

On Thu, Oct 24, 2013 at 6:26 AM, Bo Burman <bo.burman@ericsson.com> wrote:

>  1) We do agree that H.264 Constrained Baseline and VP8 are comparable in
> terms of video quality. But do not forget that Constrained Baseline's twin
> sister H.264 Constrained High outperforms VP8 by a huge margin. This is
> also relevant.****
>
> ** **
>
>
Hi Bo,

I note that one of the recent editorial updates you made to the draft is
this:

 H.264 Constrained High Profile Level 1.3, logically extended to
      support 720p resolution at 30 Hz framerate is RECOMMENDED.


that is, you added the word "logically".  Is "logically extended" a term of
art here, or do you simply mean you think it makes sense to extend the

support to Constrained High Profile Level 1.3?

I also note that the discussion here is about a Mandatory to Implement codec
(that is, something at a MUST level that avoids negotiation failure).  Your
document appears to assign that to Constrained Baseline Profile Level 1.2.

The discussion of Constrained High seems to me about an optimization and
is at most an aside, and not part of the core issue to be decided.
If you have changed your view and  believe that Constrained High Profile
Level 1.3 should be mandatory to implement, then it would be useful to say
so more forcefully than above. If you have not, then I believe it is not,
strictly speaking, relevant.


My personal view,

regards,

Ted Hardie