Re: [rtcweb] Straw Poll on Video Codec Alternatives

Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 11 January 2014 15:49 UTC

Return-Path: <derhoermi@gmx.net>
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 B7E341ADF43 for <rtcweb@ietfa.amsl.com>; Sat, 11 Jan 2014 07:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, 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 D-A9-6OmqyEJ for <rtcweb@ietfa.amsl.com>; Sat, 11 Jan 2014 07:49:12 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE6F1ADBD0 for <rtcweb@ietf.org>; Sat, 11 Jan 2014 07:49:12 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.40.188]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LoaCE-1VRKD829EY-00gaNp for <rtcweb@ietf.org>; Sat, 11 Jan 2014 16:49:01 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Ted Hardie <ted.ietf@gmail.com>
Date: Sat, 11 Jan 2014 16:49:04 +0100
Message-ID: <svn2d9lv686lit4d4mpdtfaiq7mo2fh6qs@hive.bjoern.hoehrmann.de>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:cHXeMNvpcAsIKRfhTSf/5/421uXTR2juWTXHlyGH6NMu2gGSsxS JrIavWW5QYT+VDwOoq8hkP/z6YUqQVMIuUDmKXsst1mGS55nkshIo5AurY0HO574w393RC3 gWefpnvTuCy7ay0ioVb0KDvmmwVb5H1nUWuk9k0fPtQztI2u6PcUGJDAbVbLS4/AfXwDJM0 SkL7h6PS/4YImSp7YaE3A==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Straw Poll on Video Codec Alternatives
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: Sat, 11 Jan 2014 15:49:14 -0000

* Ted Hardie wrote:
>The straw poll’s purpose is to make it clear to the WG which of the
>alternatives that are favored or disfavored and what objections you have,
>if any, against a particular alternative. ...

Here is my current thinking. Some fields intentionally left blank.

  [    NO    ]  1. All entities MUST support H.264

The current Working Group charter says "the working group will try to
avoid encumbered technologies that require royalties or other encum-
brances that would prevent such technologies from being easy to use".

It seems many potential implementers and users would be unable to ob-
tain H.264 licenses under non-discriminatory and reasonable terms for
private and commercial use. Current H.264 licensing practises are also
often unclear and are likely to put various parties at risk.

A simple example for the latter point is the distribution of recorded
WebRTC sessions on a web site that generates revenue in some form. It
is likely people are going to do that, but doing so in a legally sound
manner is often unduly burdensome under current licensing practises.

(The second paragraph can stand on its own if a "short" form is needed.)

  [          ]  2. All entities MUST support VP8

Proponents of this exclusive option have not made a convincing case.
I note in passing that `video/webm` has not been registered with IANA.

  [    NO    ]  3. All entities MUST support both H.264 and VP8
  [    NO    ]  4. Browsers MUST support both H.264 and VP8, other
                   entities MUST support at least one of H.264 and VP8
  [    NO    ]  5. All entities MUST support at least one of H.264 and
                   VP8
  [ACCEPTABLE]  6. All entities MUST support H.261

  [    NO    ]  7. There is no MTI video codec
  
This might be acceptable after properly reviewed changes to the charter.
  
  [    NO    ]  8. All entities MUST support H.261 and all entities
                   MUST support at least one of H.264 and VP8
  [ACCEPTABLE]  9. All entities MUST support Theora
  [    NO    ] 10. All entities MUST implement at least two of
                   {VP8, H.264, H.261}
  [    NO    ] 11. All entities MUST implement at least two of
                   {VP8, H.264, H.263}
  [    NO    ] 12. All entities MUST support decoding using both H.264
                   and VP8, and MUST support encoding using at least
                   one of H.264 or VP8
  [    NO    ] 13. All entities MUST support H.263
  [    NO    ] 14. All entities MUST implement at least two of
                   {VP8, H.264, Theora}
  [ACCEPTABLE] 15. All entities MUST support decoding using Theora.
  [    NO    ] 16. All entities MUST support Motion JPEG

Thanks,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/