[rtcweb] Video Codec - Possible to use.

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Fri, 19 October 2012 13:58 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C6421F89BC for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 06:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqYy0-Cxfqq9 for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 06:58:50 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7B321F8968 for <rtcweb@ietf.org>; Fri, 19 Oct 2012 06:58:50 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 3316D1EB8592; Fri, 19 Oct 2012 15:58:49 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.76]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.02.0318.001; Fri, 19 Oct 2012 15:58:48 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Video Codec - Possible to use.
Thread-Index: Ac2uAdvfNfH0YMcdSYGJWOnt/4GLHA==
Date: Fri, 19 Oct 2012 13:58:48 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF0130A96F@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [rtcweb] Video Codec - Possible to use.
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 19 Oct 2012 13:58:51 -0000

Hi,

The question of whether it will be possible for a webrtc application to make us of video codec's (or audio codec) which are not implemented in the browser itself has been raised before but I don't think there has been a clear answer.

Some clarity on this might help some of us to come to a conclusion on where we stand in the MTI debate.

I looked through the archives and found some statements that indicate this should be possible but I not sure we have a definitive statement on this. For example:

On 06 September 2012 00:29 Randall Gellens
> 
> One of the goals of rtcweb is to encourage greater use of native
> codecs, and greater access to such codecs by applications such as
> those running in browsers.  These are worthy goals, since native
> codecs often have better performance within the environment.
> (Examples include AMR and EVRC on handsets.)  These codecs also can
> be supported out-of-the-box, no separate downloads, no signed forms.
>

Is this really a goal we have agreement on? There does not seem to specific requirements in the requirements draft.

Also I think there are SDP implications relating to this. How would the browser and/or application be able to build the correct SDP to offer additional codecs?

Regards
Andy