IETF Logo Mail Archive

Re: [rtcweb] Video Codec - Possible to use.

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Fri, 19 October 2012 15:08 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 E280721F86C7 for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 08:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level:
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 S0OgNvGj1MGA for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 08:08:40 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 5766221F8685 for <rtcweb@ietf.org>; Fri, 19 Oct 2012 08:08:40 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 24DDC23F0596; Fri, 19 Oct 2012 17:08:39 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.76]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.02.0318.001; Fri, 19 Oct 2012 17:08:38 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Video Codec - Possible to use.
Thread-Index: Ac2uAdvfNfH0YMcdSYGJWOnt/4GLHP//5RsA///UtlA=
Date: Fri, 19 Oct 2012 15:08:37 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF0130AC2F@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF0130A96F@MCHP04MSX.global-ad.net> <50816228.4040605@ericsson.com>
In-Reply-To: <50816228.4040605@ericsson.com>
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: Re: [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 15:08:41 -0000

On: 19 October 2012 15:23 Stefan Hakansson LK wrote:
> On 10/19/2012 03:58 PM, Hutton, Andrew wrote:
> 
> >
> > 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?
> 
> To me this is a "must". Regardless of what codecs are made MTI now,
> they
> are likely to not be state-of-art in a few years time.

That is not really the issue. Of course the browser can add support for new codec's in years to come the question is whether the browser implementation will be able to make use of codec's provided by the underlying platform or plugin.

> 
> I had the impression this was one of the main advantages with using
> SDP:
> it offers a well established way to negotiate what codec(s) to use
> between end-points.
> 

SDP of course is flexible on this but will the browsers SDP implementation be able to handle this?


> Br,
> Stefan
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email