Re: [rtcweb] Straw Poll on Video Codec Alternatives

Alexandre GOUAILLARD <agouaillard@gmail.com> Tue, 10 December 2013 09:24 UTC

Return-Path: <agouaillard@gmail.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 ADA6C1AD8D8 for <rtcweb@ietfa.amsl.com>; Tue, 10 Dec 2013 01:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 1a9lkXTxGGJJ for <rtcweb@ietfa.amsl.com>; Tue, 10 Dec 2013 01:24:18 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 167EA1AC7F3 for <rtcweb@ietf.org>; Tue, 10 Dec 2013 01:24:18 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wm4so5066026obc.28 for <rtcweb@ietf.org>; Tue, 10 Dec 2013 01:24:13 -0800 (PST)
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=VShic8/3YpwSkMOIDLSJqWuoomgUPW2GNdTn6/8iL/k=; b=DJFrBxu5LguHoadFZ9nNHIbLhYVWwJPl4jjwlNJEjwhKyikae45SAMQ9XDxh513cFP 9YFdA5fNOW3slVNTaJwu2naBQ17DVUyvuBK6drgC/RWqO4BvnlglnCzPrsvj1J0yJJAY +eIfuoqc/kMNUOOKM3jp2S2OdaJogJ+T+JUayBiAyHP0jnql8P3RlOltjcFjyXNIRSZc b6TddKC3iDz3pHrUoYmUjlnjozRdJHnC0el1qPT6Yo/lybKCdJui0AZEJ01bIk6cUgC1 x0KOYPETdLLzMDfmdO1JdNWVC8vDHI7qHcWOa8PGPxu3YNRKyzh1ucTgV6P9plp+m9lf DY/w==
MIME-Version: 1.0
X-Received: by 10.182.28.35 with SMTP id y3mr682645obg.55.1386667452922; Tue, 10 Dec 2013 01:24:12 -0800 (PST)
Received: by 10.183.6.227 with HTTP; Tue, 10 Dec 2013 01:24:12 -0800 (PST)
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
Date: Tue, 10 Dec 2013 17:24:12 +0800
Message-ID: <CAHgZEq76whTvkZ6_6xxO=5h9OCU99rLw2gjwJww7+vEbxyCfUQ@mail.gmail.com>
From: Alexandre GOUAILLARD <agouaillard@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="089e015388f6f3ff6604ed2aac59"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Cullen Jennings <fluffy@cisco.com>
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: Tue, 10 Dec 2013 09:24:22 -0000

1.a No
  .b Feeling not comfortable with h.264 situation / license / IP.
2.a Yes
3.a No
  .b In our opinion, only one MTI is needed to have interop. More than one
would not improve interop, but would increase risks and maintenance.
4.a No
  .b browser should be treated differently. It's taking the risk of
defining several class of citizens, and have to handle a definition of
"browsers" (do application which include webkit fall under this for
example.)
5.a No
  .b This does not provide a common codec for interop. between webrtc
implementations.
6.a (Barely) acceptable
  .b We are concerned that the quality achievable, and the bandwidth
requirement are barely acceptable, however, we could live with it.
7.a No
  .b We believe we need a common codec for minimal interop.
8.a No
  .b same reason as 3.b
9.a Acceptable (neutral, would prefer 2)
10.a No
    .b Same as 3.b
11.a No
    .b Same as 3.b
12.a No
    .b Same as 3.b
13.a No
    .b same as 1.b replace 264 by 263
14.a No
    .b Same as 3.b
15.a No
    .b does not solve the problem of encoding.
16.a No
   .b Same reason as 6.b, just worse.




>    1.
>
>    All entities MUST support Motion JPEG
>    1.
>
>       Are you in favor of this option [Yes/No/Acceptable]:
>       2.
>
>       Do you have any objections to this option, if so please summarize
>       them:
>
>
>
>  H.264 is a reference to the proposal in
> https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/<https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/>
>
> VP8 is a reference to the proposal in
> https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/<https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/>
>
> Theora is a reference to Xiph.org Theora Specification from March 16, 2011
> (http://www.xiph.org/theora/doc/Theora_I_spec.pdf)
>
> H.263 is a reference to profile 0 level 70 defined in annex X of ITU-T rec
> H.263 (http://www.itu.int/rec/T-REC-H.263/)
>
> H.261 is a reference to http://tools.ietf.org/html/rfc4587
>
> Motion JPEG is a reference to http://tools.ietf.org/html/rfc2435
>
>
> Thanks,
>
> The Chairs
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>