Re: [rtcweb] selecting codec for RTCweb?

Stephan Wenger <stewe@stewe.org> Mon, 05 September 2011 17:07 UTC

Return-Path: <stewe@stewe.org>
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 8693821F8B86 for <rtcweb@ietfa.amsl.com>; Mon, 5 Sep 2011 10:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kV3VvgSv0dK3 for <rtcweb@ietfa.amsl.com>; Mon, 5 Sep 2011 10:07:55 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by ietfa.amsl.com (Postfix) with ESMTP id AC7D721F8B85 for <rtcweb@ietf.org>; Mon, 5 Sep 2011 10:07:53 -0700 (PDT)
Received: from [192.168.1.62] (unverified [71.202.147.60]) by stewe.org (SurgeMail 3.9e) with ESMTP id 33439-1743317 for multiple; Mon, 05 Sep 2011 19:09:34 +0200
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Mon, 05 Sep 2011 10:09:23 -0700
From: Stephan Wenger <stewe@stewe.org>
To: cbran <cbran@cisco.com>, <yang.yanzi@zte.com.cn>, <rtcweb@ietf.org>, <magnus.westerlund@ericsson.com>
Message-ID: <CA8A4F2F.30765%stewe@stewe.org>
Thread-Topic: [rtcweb] selecting codec for RTCweb?
In-Reply-To: <CA86BF4B.613A%cbran@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Originating-IP: 71.202.147.60
X-Authenticated-User: stewe@stewe.org
X-ORBS-Stamp: Your IP (71.202.147.60) was found in the spamhaus database. http://www.spamhaus.net
Subject: Re: [rtcweb] selecting codec for RTCweb?
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: Mon, 05 Sep 2011 17:07:56 -0000

In this context, Alex and myself drafted and presented in Quebec
http://www.ietf.org/internet-drafts/draft-wenger-rtcweb-layered-codec-00.tx
t, which argues against mandation of codec technologies not supporting
scalability.  I have not seen any significant discussion in Quebec or on
this mailing list about codec selection, though there was some initial
noise on this topic during the BOFs.
Regards,
Stephan

On 9.2.2011 17:13 , "cbran" <cbran@cisco.com>; wrote:

>Hi YANG,
>
>On 9/2/11 2:03 AM, "yang.yanzi@zte.com.cn"; <yang.yanzi@zte.com.cn>; wrote:
>
>> 
>> Dear Magnus and All RTCweb experts,
>> 
>> Was the A/V codec selecting discussed in RTCweb WG? Do you think we
>>should
>> specify codec selecting for RTCweb in this Wroking Group?
>> 
>Cullen and I submitted this draft proposal regarding rtc-web and the A/V
>codec support.  
>
>http://tools.ietf.org/html/draft-cbran-rtcweb-codec-00
>
>I presented this at IETF 81 and will be sending out an update with
>feedback
>I have received.
>
>
>> 
>> 
>> 
>> It's greatly appreciated if you response even though it has been
>>discussed
>> before. 
>> Thanks alot. 
>> 
>> 
>> Best Regards,
>> YANG Yanzi
>> 
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb