Re: [rtcweb] Video codec selection - way forward

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 18 November 2013 19:44 UTC

Return-Path: <keith.drage@alcatel-lucent.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 18A561AE1B0 for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 11:44:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 5jxs8qEmscP7 for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 11:44:20 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 44EFB1AE1AC for <rtcweb@ietf.org>; Mon, 18 Nov 2013 11:44:15 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rAIJi5Ih003934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 18 Nov 2013 13:44:07 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rAIJi4bh011093 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Nov 2013 20:44:04 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 18 Nov 2013 20:44:04 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Video codec selection - way forward
Thread-Index: AQHO4K5RagQcMG904k2Egdlu3UC4t5oq5eoAgABWmVA=
Date: Mon, 18 Nov 2013 19:44:04 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0E6F62@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <5283DFDC.4010906@ericsson.com> <528A0BD8.1070409@ericsson.com>
In-Reply-To: <528A0BD8.1070409@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [rtcweb] Video codec selection - way forward
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: Mon, 18 Nov 2013 19:44:22 -0000

While I do not think it is an alternative in itself, and therefore orthogonal to this discussion, I would like to see any draft resulting from this also containing a set of requirements leading to work that makes any hardware based codec available to the application via the browser.

I agree any APIs that already exist in this area do need more work and that work is not the work of rtcweb (and it is also not my area of expertise), but we seem to be drifting round in circles trying to deal with rights issues on downloaded codecs, and ignoring the use of codecs that may already be installed on the device for which the rights have already been paid.

Regards

Keith

> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
> Sent: 18 November 2013 12:45
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] Video codec selection - way forward
> 
> WG,
> 
> The current list of proposed alternative are the following one:
> 
>  The following alternatives has been proposed:
> 
>   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
>   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 SHOULD support both H.264 and VP8. All entities MUST
>      at least implement one of those. Entities that do not 
> support both
>      H.264 and VP8 MUST implement H.261.
> 
> The deadline to propose additional alternatives are: 27th of 
> November 2013
> 
> Cheers
> 
> Magnus
> 
> On 2013-11-13 21:23, Gonzalo Camarillo wrote:
> > Folks,
> > 
> > I hope everybody had a safe trip back home after Vancouver.
> > 
> > As you all know, we need to make progress regarding the 
> selection of 
> > the MTI video codec. The following are some of the alternatives we 
> > have on the table:
> > 
> >  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  5. All entities MUST support 
> either H.264 
> > or VP8  6. All entities MUST support H.261  7. There is no 
> MTI video 
> > codec
> > 
> > If you want the group to consider additional alternatives 
> to the ones 
> > above, please let the group know within the following *two 
> weeks*. At 
> > that point, the chairs will be listing all the received 
> alternatives 
> > and proposing a process to select one among them.
> > 
> > Please, send your proposals in an email to the list. You do 
> not need 
> > to write a draft; just send the text you would like to see in the 
> > final document regarding video codecs.
> > 
> > Thanks,
> > 
> > Gonzalo
> > Responsible AD for this WG
> > 
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> > 
> > 
> 
> 
> -- 
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>