Re: [rtcweb] Proposed Video Selection Process

<Markus.Isomaki@nokia.com> Thu, 21 November 2013 21:43 UTC

Return-Path: <Markus.Isomaki@nokia.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 CCF671AE389 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 13:43:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.725
X-Spam-Level:
X-Spam-Status: No, score=-4.725 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 GsEJnWVGm9yH for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 13:43:55 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id DF33E1AE37E for <rtcweb@ietf.org>; Thu, 21 Nov 2013 13:43:54 -0800 (PST)
Received: from smtp.mgd.nokia.com ([65.54.30.50]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id rALLXmmi001075 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 21 Nov 2013 23:33:49 +0200
Received: from 008-AM1MPN1-041.mgdnok.nokia.com ([169.254.1.35]) by 008-AM1MMR2-016.mgdnok.nokia.com ([65.54.30.50]) with mapi id 14.03.0136.001; Thu, 21 Nov 2013 21:33:48 +0000
From: <Markus.Isomaki@nokia.com>
To: <ekr@rtfm.com>
Thread-Topic: [rtcweb] Proposed Video Selection Process
Thread-Index: AQHO5tnkMqQSi3Uo8kudbR+N6LyUKZov+9iAgAACNgCAAAr/gIAABK+AgAAYwYCAAAHxAIAAAPyAgAAGL4CAAAVsrQ==
Date: Thu, 21 Nov 2013 21:33:47 +0000
Message-ID: <2CA8952C-9AD0-49F0-A8E9-160099D09DC9@nokia.com>
References: <528E39F4.4010706@ericsson.com> <CAEqTk6RrHSzgJ9QA_spJQWN+6SaRWwwq6H4cwBxNbTHXnHmhYA@mail.gmail.com> <8647A71C-CDCF-4897-96D6-4CD1C6566BE6@cisco.com> <CAOJ7v-1kdXreZbF0Q7=DinObV5=eWcdfFuwrJ13BQ0Hk=Fec-Q@mail.gmail.com> <528E5B47.70702@nostrum.com> <20131121204147.GV3245@audi.shelbyville.oz> <528E71AC.4040202@librevideo.org> <CABkgnnUKPMTpMqX6G5=kDQomG9wgqZeTomOnjGecTFZ7T3GjfQ@mail.gmail.com>, <CABcZeBO+cd46EOXCCO+qh5OtYWZz6Fam9O0RhY=vHVGUCMfhdA@mail.gmail.com>
In-Reply-To: <CABcZeBO+cd46EOXCCO+qh5OtYWZz6Fam9O0RhY=vHVGUCMfhdA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_2CA8952C9AD049F0A8E9160099D09DC9nokiacom_"
MIME-Version: 1.0
X-Nokia-AV: Clean
Cc: 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 21:43:57 -0000

Would the implement any two of {VP8, H.264 CBP, H.261} option solve your problem?

+1 for Ron's reasoning.

Markus

Sent from my iPad

On Nov 21, 2013, at 23:15, "ext Eric Rescorla" <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote:

Agreed.

To take a not-so-random example, given that Firefox will soon
support both H.264 and VP8, what additional implementations
will it be able to talk to if it does H.261?

-Ekr




On Thu, Nov 21, 2013 at 12:52 PM, Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com>> wrote:
On 21 November 2013 12:48, Basil Mohamed Gohar
<basilgohar@librevideo.org<mailto:basilgohar@librevideo.org>> wrote:
> Has anyone actually objected to H.261 being the one MTI codec [...] ?

More than one person has already.

And I find the argument raised quite compelling.  It's hard to justify
spending valuable time and resources on implementing something that
crappy.
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb