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

Cullen Jennings <fluffy@iii.ca> Mon, 23 May 2016 16:58 UTC

Return-Path: <fluffy@iii.ca>
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 B662C12DA40 for <rtcweb@ietfa.amsl.com>; Mon, 23 May 2016 09:58:06 -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_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 HtrabjC-d1zZ for <rtcweb@ietfa.amsl.com>; Mon, 23 May 2016 09:58:05 -0700 (PDT)
Received: from smtp105.iad3a.emailsrvr.com (smtp105.iad3a.emailsrvr.com [173.203.187.105]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B64312D935 for <rtcweb@ietf.org>; Mon, 23 May 2016 09:58:02 -0700 (PDT)
Received: from smtp6.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp6.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id EC05B180362; Mon, 23 May 2016 12:57:56 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp6.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 8F0291804CD; Mon, 23 May 2016 12:57:56 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.92.108.159] (184-23-135-130.dedicated.static.sonic.net [184.23.135.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.5.4); Mon, 23 May 2016 12:57:56 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF260FFABF@MCHP04MSX.global-ad.net>
Date: Mon, 23 May 2016 08:42:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CD65A98-7FFE-4E24-A258-E022509E0A32@iii.ca>
References: <571DE213.8080306@goodadvice.pages.de> <9F33F40F6F2CD847824537F3C4E37DDF260FFABF@MCHP04MSX.global-ad.net>
To: "Hutton, Andrew" <andrew.hutton@unify.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/AhkwRcb15Goz0p1M0l-QR2oyOGU>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Mon, 23 May 2016 16:58:07 -0000

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. 

> 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. 
> 
> Regards
> Andy
> 
> 
> 
> 
>> -----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.
>> 
>> http://w3c.github.io/webrtc-pc/#widl-RTCRtpEncodingParameters-
>> maxBitrate
>> uses TIAS as a definition.
>> 
>> For parsing, supporting both is fine (for a while at least).
>> For serialization I would prefer picking one (TIAS) to having to track
>> which variant a peer supports.
>> 
>> _______________________________________________
>> 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