Re: [rmcat] Priority and rtcweb

Varun Singh <varun@callstats.io> Mon, 13 November 2017 20:51 UTC

Return-Path: <varun@callstats.io>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 582F9129562 for <rmcat@ietfa.amsl.com>; Mon, 13 Nov 2017 12:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=callstats.io
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 C_d_BjSMLpyD for <rmcat@ietfa.amsl.com>; Mon, 13 Nov 2017 12:51:25 -0800 (PST)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 430FC126DEE for <rmcat@ietf.org>; Mon, 13 Nov 2017 12:51:25 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id a2so19871805lfh.11 for <rmcat@ietf.org>; Mon, 13 Nov 2017 12:51:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callstats.io; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sX8D1yav/1uDvjwMMltYkN+zI8y1hPHsw7vAi0VQyO0=; b=Pf42sWvx4W1Xjmql1YHTBh2x9mh6uq1FctKDDlGkFzC5jzm/5pyFFYuOLU6Z5UqGXp 5B8R7xgPEagePegivOyE6P8em7xb6V43VYJ7oZ69Low3P50SnE5EPxaxAVTO8BM1ZnnI xeHRjnlEpsu+8xzkWtzrzOuTVqwa2OZMVb8kQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sX8D1yav/1uDvjwMMltYkN+zI8y1hPHsw7vAi0VQyO0=; b=RbY2E/MMzs+6pBtjeQ7yIEov4zQs9njFPZVwzEyJsV8N/YAlfEg2ATMGwP0jk4OsDh WxYY8wICfKMwmkgPun93hQzr40mswDx8YlyB1Cskr/pAyub+sbkqmDBdaTvWZgfXjHAe PQBDhwj7XWEz4aV+G1v8kCmFV5H8IXtcAxp0giVy3Ygp0XxDSG6zzw/I57A6TApNZUFj mxlxEJ6CI89Sg7dwHHMjL3Joa9eFBEqIXmgAjG+mqpWSAzBKcobamGwbj/wyAtNAxuV5 eklY8NiTZmbjyf1uxB2q+koz3UEonktQd8uzuJlC6w4zqD8tGqxdmAjaTPzkRJvhHkSM O2sQ==
X-Gm-Message-State: AJaThX5eBHuiocZ9upyTCjgxboKTF+LiMet6dkL/ZQuyBdF2Q+kY46B4 0yvMfh9FeRbrqhDeB+JxS1sFG7jyb246YSIEQW58aw==
X-Google-Smtp-Source: AGs4zMa/O7eGwb3v3NKXWmPlD2vuqvhhxDVX19uKJAMELhC1hO2GWaDEn5fi+YjkaWNjUfZtSlPaQ7v5o/6mhp+1vTU=
X-Received: by 10.46.76.9 with SMTP id z9mr3855612lja.105.1510606283247; Mon, 13 Nov 2017 12:51:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.167.129 with HTTP; Mon, 13 Nov 2017 12:51:02 -0800 (PST)
In-Reply-To: <B01370E2-AABE-41D4-A7A7-8A062ED3B42B@ifi.uio.no>
References: <CACHXSv7z3KSNB+4PZ9+AgrW1nzc7ZH2fbNbBDoeKVqm=SYmZuQ@mail.gmail.com> <B01370E2-AABE-41D4-A7A7-8A062ED3B42B@ifi.uio.no>
From: Varun Singh <varun@callstats.io>
Date: Mon, 13 Nov 2017 12:51:02 -0800
Message-ID: <CACHXSv7hm7d14RaCyBwyuSfAep+Znp_g0o8zJpOFnnXD+RbRHg@mail.gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Colin Perkins <csp@csperkins.org>, "W3C@CSIO" <webrtc@callstats.io>
Content-Type: multipart/alternative; boundary="f403045ea626e8a2cf055de36ea1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/XNZYuu63QLQpEfA_T49OqZBhfr0>
Subject: Re: [rmcat] Priority and rtcweb
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 20:51:27 -0000

Hi Michael,

On Mon, Nov 13, 2017 at 10:44 AM, Michael Welzl <michawe@ifi.uio.no> wrote:

> Can I hijack this thread to talk about priority?
>
>
Priority is already defined in the API document to the following levels:
high, medium, low, very-low.
These labels map to the text in the transport document

        Thus, when congestion occurs, a "high" priority flow will have the
        ability to send 8 times as much data as a "very-low" priority flow
if
        both have data to send. This prioritization is independent of the
        media type. The details of which packet to send first are
        implementation defined.

WEBRTC API:
https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcprioritytype



> There was a thread about priority in rtcweb - someone asking for a float…
> coupled-cc can easily support a float, but Harald’s transport draft doesn’t
> support it. Opinions went back and forth for a bit...
> I think we should get more WebRTC deployment and not more debate on small
> details that delays the work, so I don’t want to be a troublemaker and
> didn’t interfere with this discussion.
> But, what is the view of people in rmcat about this?
>
>
While the API does not provide a float value, nonetheless, doesn't the
WebRTC stack or framework under the JS API have all the information to
convert the set labels in to a float values after the flows are assigned
values?



> Cheers,
> Michael
>
>
> On Nov 13, 2017, at 2:41 PM, Varun Singh <varun@callstats.io> wrote:
>
> Hi,
>
> Was there a study done for the parameters needed for congestion control? I
> know we debated this at length, were there slides created by  the
> congestion control proponents, that I can reference.
>
> From the top of my head, I remember there’s
> + priority (needed by coupled congestion control)
>
> I’m asking this for w3c input. They already have max bitrate, max
> framearte, and degradation preference  degradation preference indicates
> where the bits should be allocated: in maintaining frame rates or frame
> sizes.
>
> Feedback is appreciated To make sure we didn’t miss anything.
>
> Cheers,
> Varun.
> --
> Founder, CEO, callstats.io
> http://www.callstats.io
>
> Interested in networking, media quality, and diagnostics.
> We are hiring!: www.callstats.io/jobs/
>
>
>


-- 
Founder, CEO, callstats.io
http://www.callstats.io

Interested in networking, media quality, and diagnostics.
We are hiring!: www.callstats.io/jobs/