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

From: Randell Jesup <[email-masked]>
Date: Thu, 9 Jun 2016 02:58:30 -0400

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 <[email-masked]> 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:[email-masked]] On Behalf Of Philipp
>>> Hancke
>>> Sent: 25 April 2016 10:24
>>> To: [email-masked]
>>> 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 [email-masked]!  Way too much spam