Re: [rtcweb] Video codec selection: Dropping options

cowwoc <cowwoc@bbs.darktech.org> Thu, 28 November 2013 17:57 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 F18B71ADED5 for <rtcweb@ietfa.amsl.com>; Thu, 28 Nov 2013 09:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 LSzehWklpiZx for <rtcweb@ietfa.amsl.com>; Thu, 28 Nov 2013 09:57:12 -0800 (PST)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by ietfa.amsl.com (Postfix) with ESMTP id B56F31ACCE6 for <rtcweb@ietf.org>; Thu, 28 Nov 2013 09:57:12 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id lx4so14645131iec.37 for <rtcweb@ietf.org>; Thu, 28 Nov 2013 09:57:11 -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; bh=zsmEO0OtXeZqwVdnXR6UgUmmpvgpRqF0VGOAJZtcbwA=; b=EJR3R5MidJBhA/T34aPE/O/7aneUoyP0jDVWbooGGBWIF/OaRJ2pxlUHz3QpLM9GGZ Cr7sacHaEwan/AWlhHkMgKOpcIw0YLzFLOJ5dl5MChnELc9G8GbiN6DH7gVZ7sG/nnSv lOw9LHkiYehjWXj4wk1/q3p+Qsi2OHRXxn/RhsO7SKh7l+0zIRyd6pQ8g1GJwGMuYDDh VbP+6vAEFlsCHOnWZsgmQDotgIdjYIdHrNLPohC7rWoxoAxmCcesUlj35M7Lm0tRvMqg COe6p0Qqbkbh7gNSlTRRpyM+8kisqP3QS5wdSP3O4AXtbOLo7tiB9ASYyfjgORMjMePr 7c6A==
X-Gm-Message-State: ALoCoQlfUWRpviDViJYbNLLEKb/IUTm2PLoe2VJ1hPpDGJphRw9IZCq5r5V5Vd40PlePrQ+nLpRR
X-Received: by 10.50.234.162 with SMTP id uf2mr2996033igc.48.1385661431827; Thu, 28 Nov 2013 09:57:11 -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 v9sm36607919igh.7.2013.11.28.09.57.10 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Nov 2013 09:57:11 -0800 (PST)
Message-ID: <529783C8.7090806@bbs.darktech.org>
Date: Thu, 28 Nov 2013 12:56:24 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <E44893DD4E290745BB608EB23FDDB7620A13AE73@008-AM1MPN1-041.mgdnok.nokia.com> <CAGgHUiQLXSzU+AvCcvDa383DA=OGd9-NTedfFOAVGt+OmyKwwg@mail.gmail.com>
In-Reply-To: <CAGgHUiQLXSzU+AvCcvDa383DA=OGd9-NTedfFOAVGt+OmyKwwg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070309070809070308090607"
Subject: Re: [rtcweb] Video codec selection: Dropping options
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, 28 Nov 2013 17:57:15 -0000

On 28/11/2013 5:20 AM, Leon Geyser wrote:
> I am a bit confused about option 15. How does that one work?
> Let's say I have a two sides: H.264 encoding/decoding + Theora decoder 
> and the other side has VP8 encoding/decoding + Theora decoder. How do 
> they communicate?

Any option that mandates one or more decoders implies "and MUST support 
encoding of one of the aforementioned formats".

Gili

>
>
> On 28 November 2013 10:22, <Markus.Isomaki@nokia.com 
> <mailto:Markus.Isomaki@nokia.com>> wrote:
>
>     Hi,
>
>     I'm not much in favor of the voting, but if we do it:
>
>     Based on the consensus call we already held in Vancouver, I would
>     propose to drop from the list in [1] any options that make
>     exclusively VP8 mandatory to implement or exclusively H.264
>     mandatory to implement. I think we have already established that
>     much, and including those options in any vote seems wrong.
>
>     In practice I'm talking about these four options:
>     1. All entities MUST support H.264
>     2. All entities MUST support VP8
>     3. All entities MUST support both H.264 and VP8
>     4. Browsers MUST support both H.264 and VP8, other entities MUST
>     support at least one of H.264 and VP8
>
>     What the WG should focus on is to see if there is a consensus on
>     any of the so called "fallback" options vs. no MTI. I think these
>     are all valid as such as a "fallback":
>
>     5. All entities MUST support at least one of H.264 and VP8
>     6. All entities MUST support H.261
>     7. There is no MTI video codec
>     8. 5+6, i.e. All entities MUST support H.261 and all entities MUST
>     support at least one of H.264 and VP8
>     9. All entities MUST support Theora
>     10. All entities MUST implement at least two of {VP8, H.264, H.261}
>     11. All entities MUST implement at least two of {VP8, H.264, H.263}
>     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
>     13. All entities MUST support H.263
>     14. All entities MUST implement at least two of {VP8, H.264 CBP,
>     Theora}
>     15. All entities MUST support decoding using Theora.
>
>     I think it would be problematic even if one of options 1-4 came
>     out as a winner from a voting procedure, since it would force a
>     large part of the community to implement something they have valid
>     reasons to avoid. Some of the options 5-15 may have issues as
>     well, but at least a consensus call among them would still be in
>     order, since we haven't really had it so far. And presumably the
>     issues and polarization are "smaller" than with the VP8 vs. H.264
>     argument.
>
>     Regards,
>             Markus
>
>     [1] http://trac.tools.ietf.org/wg/rtcweb/trac/wiki/WikiStart
>
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb