[rtcweb] which bandwidth modifiers need to be supported?

Philipp Hancke <fippo@goodadvice.pages.de> Mon, 25 April 2016 09:23 UTC

Return-Path: <fippo@goodadvice.pages.de>
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 D75E912D535 for <rtcweb@ietfa.amsl.com>; Mon, 25 Apr 2016 02:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level:
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-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 ffycjOknzy_j for <rtcweb@ietfa.amsl.com>; Mon, 25 Apr 2016 02:23:53 -0700 (PDT)
Received: from lo.psyced.org (lost.in.psyced.org [188.40.42.221]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA60B12D527 for <rtcweb@ietf.org>; Mon, 25 Apr 2016 02:23:51 -0700 (PDT)
Received: from [172.20.10.2] (2.150.17.227.tmi.telenormobil.no [2.150.17.227]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id u3P9NfbM005517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <rtcweb@ietf.org>; Mon, 25 Apr 2016 11:23:49 +0200
To: rtcweb@ietf.org
From: Philipp Hancke <fippo@goodadvice.pages.de>
Message-ID: <571DE213.8080306@goodadvice.pages.de>
Date: Mon, 25 Apr 2016 11:23:31 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/qM8jVXWl04yznb0UvutsT8Z2Ppk>
Subject: [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, 25 Apr 2016 09:23:55 -0000

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.