IETF Logo Mail Archive

[rmcat] Parameters for congestion control

Varun Singh <varun@callstats.io> Mon, 13 November 2017 06:41 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 85318124B18 for <rmcat@ietfa.amsl.com>; Sun, 12 Nov 2017 22:41:45 -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 1-fxouRglR8X for <rmcat@ietfa.amsl.com>; Sun, 12 Nov 2017 22:41:43 -0800 (PST)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 6E1111200C1 for <rmcat@ietf.org>; Sun, 12 Nov 2017 22:41:43 -0800 (PST)
Received: by mail-lf0-x233.google.com with SMTP id e143so17050924lfg.12 for <rmcat@ietf.org>; Sun, 12 Nov 2017 22:41:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callstats.io; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=Xjql9L5v/qB3FyE6LgxAwTxCEuaCJjK1UNzePEXDLI4=; b=lcwVUoaNpfjODFPcH99eRuEdrAdX9FXE+U1Uyx06Sxr2nLwrGOVz58eNwUAn7hyViL OG93jB9mCnjb4wopLfRX+BMmrB3aTisCnnwcsImIDe/Mw/vvEwluLZkWqSa7krhcpvnJ w0N9RyLKNp8bCejeNKnTMWsM/472aYM4iySkE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Xjql9L5v/qB3FyE6LgxAwTxCEuaCJjK1UNzePEXDLI4=; b=HL6tzN1jLuqNPYrmlatgwB8WBEHqQL5y4hOIzRUuPH2qYs1h4ULdHpib74lwNm+YMk 8eRYRn2Qnxltr8056rLv1ZyjPlJWWqv6EYkmd0lCjiZttHACB2JG05RgB5Fl+yz4IZVb uKOPOegnH4mcLFidGjmAuq7I+Zm3iA71nOriknXl6WClyNarRLra8PhNoBPxIh6wVa1v QBlHQlIR2FCiFSjS7pAudmqJcGWVtd+zJUVs7McWQnrxzH9OnmPLtx6217SS1CTbgreP XXwFvm6lSKgZrSht4iJ7zmEN9P4W1hfmKyzDnjpsfzADtMxe9A+dNSK2WWQhuektzDHB N7Fw==
X-Gm-Message-State: AJaThX44mWg/183hxrNUT2DEbejlBmMv2M41TCYIVgByJ0i1vUKVKkzh e0B/KkYcIEXaPw2DTTpFpKERxgsC1Cua4pBL6w6g4Q==
X-Google-Smtp-Source: AGs4zMYrt1sLJEZ8w+iRFlFV26EsOTLPRG/4wTJFmE37oW4iviJlFrZmPAdCfP9ouXRBNk6zkf01wJ/b2LgU42smNbw=
X-Received: by 10.25.145.30 with SMTP id t30mr2459461lfd.247.1510555301625; Sun, 12 Nov 2017 22:41:41 -0800 (PST)
MIME-Version: 1.0
From: Varun Singh <varun@callstats.io>
Date: Mon, 13 Nov 2017 06:41:30 +0000
Message-ID: <CACHXSv7z3KSNB+4PZ9+AgrW1nzc7ZH2fbNbBDoeKVqm=SYmZuQ@mail.gmail.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Cc: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="94eb2c1cd0e62adc53055dd790a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/5319Q2q33lBQ4eTpdqWBCyFPjyw>
Subject: [rmcat] Parameters for congestion control
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 06:41:45 -0000

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/

v2.23.0 | Report a Bug | By Email