IETF Logo Mail Archive

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

Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Fri, 19 October 2012 14:22 UTC

Return-Path: <stefan.lk.hakansson@ericsson.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 AE02721F86E5 for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 07:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 TZH45uLLJ-vr for <rtcweb@ietfa.amsl.com>; Fri, 19 Oct 2012 07:22:36 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id EEEB421F85A4 for <rtcweb@ietf.org>; Fri, 19 Oct 2012 07:22:35 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-0c-5081622a2653
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 7A.59.11467.A2261805; Fri, 19 Oct 2012 16:22:34 +0200 (CEST)
Received: from [150.132.142.225] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Fri, 19 Oct 2012 16:22:34 +0200
Message-ID: <50816228.4040605@ericsson.com>
Date: Fri, 19 Oct 2012 16:22:32 +0200
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <9F33F40F6F2CD847824537F3C4E37DDF0130A96F@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF0130A96F@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNJMWRmVeSWpSXmKPExsUyM+Jvra5WUmOAQd9hSYu1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8aFzKVvBLJaKnq2TWBoYFzN3MXJySAiYSGz+fIcNwhaTuHBv PZDNxSEkcIpR4tzOQ8wQzlpGiZ71zWAdvALaEsd//QfrYBFQlbh7+AQLiM0mYCOxtnsKE4gt KhAmsXznZiaIekGJkzOfgNWICAhLbH3VCxYXBtp8tXkqK4gtJOAn8eDgXjCbU8Bf4vPnHjCb WcBW4sKc6ywQtrzE9rdzmCHqdSXevb7HOoFRYBaSFbOQtMxC0rKAkXkVo3BuYmZOermhXmpR ZnJxcX6eXnHqJkZgAB7c8lt3B+OpcyKHGKU5WJTEebmS9vsLCaQnlqRmp6YWpBbFF5XmpBYf YmTi4JRqYOyZn5C7sqm061n2nKBXaeJFczd7LJ3kbfxQ5JWN2YnDuzVczVR+PtC89/gbk8/N ghN1d8rbbCQKzGSjnsceERD9mSxgYPfy32keiyjZw1EV9r/WZX0R6xRs0s+9pLPhSHGPuOFa p5k/xav2nrpd9GT6dBGhk0HRzWYMkcxam60+7LSuZZuwW4mlOCPRUIu5qDgRAK3+EaoOAgAA
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 14:22:36 -0000

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.

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.

Br,
Stefan

v2.23.0 | Report a Bug | By Email