Re: [rtcweb] which bandwidth modifiers need to be supported?

Randell Jesup <randell-ietf@jesup.org> Thu, 09 June 2016 06:59 UTC

Return-Path: <randell-ietf@jesup.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 C550E12D12B for <rtcweb@ietfa.amsl.com>; Wed, 8 Jun 2016 23:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
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 uM875hOGeJtP for <rtcweb@ietfa.amsl.com>; Wed, 8 Jun 2016 23:59:55 -0700 (PDT)
Received: from relay.mailchannels.net (baboon.maple.relay.mailchannels.net [23.83.214.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FF1C12D125 for <rtcweb@ietf.org>; Wed, 8 Jun 2016 23:59:55 -0700 (PDT)
X-Sender-Id: wwwh|x-authuser|randell@jesup.org
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 24A9412046F for <rtcweb@ietf.org>; Thu, 9 Jun 2016 06:59:49 +0000 (UTC)
Received: from rcentral501.webserversystems.com (ip-10-213-0-221.us-west-2.compute.internal [10.213.0.221]) by relay.mailchannels.net (Postfix) with ESMTPA id 4C3021205CD for <rtcweb@ietf.org>; Thu, 9 Jun 2016 06:59:48 +0000 (UTC)
X-Sender-Id: wwwh|x-authuser|randell@jesup.org
Received: from rcentral501.webserversystems.com (rcentral501.webserversystems.com [10.25.19.46]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.6.14); Thu, 09 Jun 2016 06:59:48 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: wwwh|x-authuser|randell@jesup.org
X-MailChannels-Auth-Id: wwwh
X-MC-Loop-Signature: 1465455588504:2558196524
X-MC-Ingress-Time: 1465455588503
Received: from pool-71-162-135-19.phlapa.fios.verizon.net ([71.162.135.19]:56830 helo=[192.168.1.12]) by rcentral501.webserversystems.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <randell-ietf@jesup.org>) id 1bAtwZ-0006Bv-6p for rtcweb@ietf.org; Thu, 09 Jun 2016 02:59:55 -0400
References: <571DE213.8080306@goodadvice.pages.de> <9F33F40F6F2CD847824537F3C4E37DDF260FFABF@MCHP04MSX.global-ad.net> <4CD65A98-7FFE-4E24-A258-E022509E0A32@iii.ca>
To: rtcweb@ietf.org
From: Randell Jesup <randell-ietf@jesup.org>
Message-ID: <e87d06e6-cdb2-e9d2-9a93-8ba0095436bd@jesup.org>
Date: Thu, 9 Jun 2016 02:58:30 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <4CD65A98-7FFE-4E24-A258-E022509E0A32@iii.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
X-AuthUser: randell@jesup.org
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/C1uv2Lqkk5mEOaC9e7tEn7lSwgU>
Subject: Re: [rtcweb] which bandwidth modifiers need to be supported?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 09 Jun 2016 06:59:57 -0000

On 5/23/2016 11:42 AM, Cullen Jennings wrote:
> I’m not sure there is a requirement for a WebRTC endpoint to generate them but if there is, agree that we should say TIAS is preferred.

Agreed TIAS should be preferred (though are we actually talking generate 
or accept? - the messages below seem to slightly be in conflict.)  
Firefox Nightly just landed support for receiving b=TIAS, but not b=AS 
(at least so far).

>> On May 11, 2016, at 8:55 AM, Hutton, Andrew <andrew.hutton@unify.com> wrote:
>>
>> I was also looking at this again my assumption is that TIAS is what a WebRTC endpoint should generate TIAS as Philipp stated this is hinted at in the W3C spec but probably also should be specified in JSEP and an example in https://tools.ietf.org/html/draft-ietf-rtcweb-sdp-01#section-5.2.2 would also be useful.
>>
>> For parsing then both TIAS and AS needs to be supported this is specified in https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-14#section-5.8.
>>
>>
>>> -----Original Message-----
>>> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Philipp
>>> Hancke
>>> Sent: 25 April 2016 10:24
>>> To: rtcweb@ietf.org
>>> Subject: [rtcweb] which bandwidth modifiers need to be supported?
>>>
>>> which bandwidth modifiers for b= lines does a client need to support?
>>>
>>> Chrome currently supports b=AS, however the implementation is closer to
>>> TIAS semantically. Firefox does not implement either currently.

-- 
Randell Jesup -- rjesup a t mozilla d o t com
Please please please don't email randell-ietf@jesup.org!  Way too much spam