
From nobody Wed Jul  1 03:10:16 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7361ACD0C for <rmcat@ietfa.amsl.com>; Wed,  1 Jul 2015 03:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 slORr112p97u for <rmcat@ietfa.amsl.com>; Wed,  1 Jul 2015 03:10:13 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 831861B2C0B for <rmcat@ietf.org>; Wed,  1 Jul 2015 03:10:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 031F6D930E; Wed,  1 Jul 2015 12:10:11 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3fbLr6SCmywU; Wed,  1 Jul 2015 12:10:10 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id C8461D930D; Wed,  1 Jul 2015 12:10:10 +0200 (MEST)
Message-ID: <5593BC82.9040303@tik.ee.ethz.ch>
Date: Wed, 01 Jul 2015 12:10:10 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "rmcat@ietf.org" <rmcat@ietf.org>,  Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/PUFRZ_M8cpUe36opcUDtYp4IktU>
Subject: [rmcat] draft meeting agenda
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 01 Jul 2015 10:10:15 -0000

Hi all,

I've just uploaded a first draft meeting agenda. I'm still waiting for feedback 
from some people, so there might still be changes. Anyway, please check what's 
on the agenda for now to make sure I didn't miss anything or got something wrong:

https://www.ietf.org/proceedings/93/agenda/agenda-93-rmcat

Mirja


From nobody Wed Jul  1 08:47:50 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A49611A90BC; Wed,  1 Jul 2015 08:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 nSUDxu_yNhQn; Wed,  1 Jul 2015 08:47:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83E4C1A90A2; Wed,  1 Jul 2015 08:47:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150701154746.25096.73757.idtracker@ietfa.amsl.com>
Date: Wed, 01 Jul 2015 08:47:46 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/2n27MWZ9bT0n4Pe47IjnOFerI0g>
Cc: rmcat@ietf.org
Subject: [rmcat] I-D Action: draft-ietf-rmcat-sbd-01.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 01 Jul 2015 15:47:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the RTP Media Congestion Avoidance Techniques Working Group of the IETF.

        Title           : Shared Bottleneck Detection for Coupled Congestion Control for RTP Media.
        Authors         : David Hayes
                          Simone Ferlin
                          Michael Welzl
	Filename        : draft-ietf-rmcat-sbd-01.txt
	Pages           : 20
	Date            : 2015-07-01

Abstract:
   This document describes a mechanism to detect whether end-to-end data
   flows share a common bottleneck.  It relies on summary statistics
   that are calculated by a data receiver based on continuous
   measurements and regularly fed to a grouping algorithm that runs
   wherever the knowledge is needed.  This mechanism complements the
   coupled congestion control mechanism in draft-welzl-rmcat-coupled-cc.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rmcat-sbd-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rmcat-sbd-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jul  1 11:27:21 2015
Return-Path: <davihay@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122C21AC3BB for <rmcat@ietfa.amsl.com>; Wed,  1 Jul 2015 11:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 o7KTBYUWgrPw for <rmcat@ietfa.amsl.com>; Wed,  1 Jul 2015 11:27:18 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 289FF1ACDC1 for <rmcat@ietf.org>; Wed,  1 Jul 2015 11:27:17 -0700 (PDT)
Received: from mail-mx6.uio.no ([129.240.10.40]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <davihay@ifi.uio.no>) id 1ZAMj5-0007cy-KW; Wed, 01 Jul 2015 20:27:15 +0200
Received: from 40.84-48-123.nextgentel.com ([84.48.123.40] helo=[192.168.0.5]) by mail-mx6.uio.no with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) user davihay@ifi.uio.no (Exim 4.80.1) (envelope-from <davihay@ifi.uio.no>) id 1ZAMj4-0001zU-WA; Wed, 01 Jul 2015 20:27:15 +0200
Date: Wed, 01 Jul 2015 20:27:13 +0200
From: David Hayes <davihay@ifi.uio.no>
To: rmcat WG <rmcat@ietf.org>
Message-Id: <1435775233.12351.5@smtp.uio.no>
X-Mailer: geary/0.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 3 msgs/h 1 sum rcpts/h 4 sum msgs/h 1 total rcpts 272 max rcpts/h 10 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 78EB2B24E14191F6F99A4FA4FFB4469C175EE9EB
X-UiO-SPAM-Test: UIO-GREYLIST remote_host: 84.48.123.40 spam_score: -49 maxlevel 80 minaction 1 bait 0 mail/h: 1 total 96 max/h 5 blacklist 0 greylist 1 ratelimit 0
X-UiOonly: EDB26E2D06D89EAEC02873F78D3525BA38805C8B
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/hgfmYlhy1_CwJdIwJMBi_UaGT6o>
Cc: Simone Ferlin-Oliveira <ferlin@simula.no>, Michael Welzl <michawe@ifi.uio.no>
Subject: [rmcat] Fwd:  I-D Action: draft-ietf-rmcat-sbd-01.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 01 Jul 2015 18:27:20 -0000

Dear Group,

We have submitted a new revision of the draft. Work has continued 
improving the overall robustness of the mechanism.
Key improvements in the draft include:
	1. Moving the unbiased skew estimate section to replace the original 
skew estimate,
	2. Introduction of a more robust variability estimator,
	3. Revision of the clock skew section with a place holder for the 
moment
	   (though we will show some results in Prague), and
	4. A description of key parameters and how they influence the 
mechanism.

Feedback hoped for :)

Kind regards,

David

---------- Forwarded message ----------

 From: internet-drafts@ietf.org
Subject: [rmcat] I-D Action: draft-ietf-rmcat-sbd-01.txt
Date: Wed, 1 Jul 2015 17:47:46 +0200
To: i-d-announce@ietf.org
Cc: rmcat@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
 This draft is a work item of the RTP Media Congestion Avoidance 
Techniques Working Group of the IETF.

        Title           : Shared Bottleneck Detection for Coupled 
Congestion Control for RTP Media.
        Authors         : David Hayes
                          Simone Ferlin
                          Michael Welzl
	Filename        : draft-ietf-rmcat-sbd-01.txt
	Pages           : 20
	Date            : 2015-07-01

Abstract:
   This document describes a mechanism to detect whether end-to-end data
   flows share a common bottleneck.  It relies on summary statistics
   that are calculated by a data receiver based on continuous
   measurements and regularly fed to a grouping algorithm that runs
   wherever the knowledge is needed.  This mechanism complements the
   coupled congestion control mechanism in draft-welzl-rmcat-coupled-cc.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rmcat-sbd-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rmcat-sbd-01


Please note that it may take a couple of minutes from the time of 
submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/




From nobody Sun Jul  5 08:49:13 2015
Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97B5E1A92FF for <rmcat@ietfa.amsl.com>; Sun,  5 Jul 2015 08:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 IxbfIMQACLqX for <rmcat@ietfa.amsl.com>; Sun,  5 Jul 2015 08:49:11 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE501A92AD for <rmcat@ietf.org>; Sun,  5 Jul 2015 08:49:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1994; q=dns/txt; s=iport; t=1436111351; x=1437320951; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=x0NwEe+vSgGK32IH213r1tYfiGkyrYHCj9cIWbnEX8w=; b=R0GeLdkY4YoRilL2CpXoxup25r06TK0PTcr9yLH+IbPjfJjuJx8xrzGZ AtTofPJfVYWWjRq9ecpwhgTiLXhkmTtYIiac5EOek3RTxt4T2QEHbNT6H ktWWjbtuD+4qeVhHFWUyLEFILUxRbuG07ACp8VgfuC0YcO0ARBK2JQ8r2 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CxAwCEUZlV/5FdJa1cgxJUYAa9QQmBcIV1AoEaOBQBAQEBAQEBgQqEJAEBBDo9AhACAQg2EDIbAQYDAgQOBYgvDccTAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tLhQYHhCsFjBmHfAGEYYcGgTpEg1GPKoNdJoN7bwGBRoEEAQEB
X-IronPort-AV: E=Sophos;i="5.15,410,1432598400"; d="scan'208";a="165561775"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-7.cisco.com with ESMTP; 05 Jul 2015 15:49:10 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t65FnADA025294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rmcat@ietf.org>; Sun, 5 Jul 2015 15:49:10 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.112]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Sun, 5 Jul 2015 10:49:10 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: rmcat WG <rmcat@ietf.org>
Thread-Topic: New Version Notification for draft-fu-rmcat-wifi-test-case-00.txt
Thread-Index: AQHQtsC6t0/vgZD/+0y+P6+Ub4FV+J3NBsAA
Date: Sun, 5 Jul 2015 15:49:09 +0000
Message-ID: <D1BEBB23.22602%xiaoqzhu@cisco.com>
References: <20150705012002.19096.46475.idtracker@ietfa.amsl.com>
In-Reply-To: <20150705012002.19096.46475.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.89.1.19]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <091D9A17416DAB4DA32748B5E8BC63E4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/MhoaDYHX2roGFM_VNFSW7ztPycg>
Cc: "Jeromy Fu \(jianfu\)" <jianfu@cisco.com>, "Michael Ramalho \(mramalho\)" <mramalho@cisco.com>, "Dan Tan \(dtan2\)" <dtan2@cisco.com>
Subject: [rmcat] FW: New Version Notification for draft-fu-rmcat-wifi-test-case-00.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 05 Jul 2015 15:49:12 -0000

Hi,=20

We have put together a straw-man version of a draft on Wi-Fi test cases,
up for discussions and feedback in the upcoming RMCAT WG meeting in
Prague.=20

Your comments and inputs are welcome.

Thanks,
Xiaoqing


On 7/4/15, 8:20 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-fu-rmcat-wifi-test-case-00.txt
>has been successfully submitted by Xiaoqing Zhu and posted to the
>IETF repository.
>
>Name:		draft-fu-rmcat-wifi-test-case
>Revision:	00
>Title:		Evaluation Test Cases for Interactive Real-Time Media over Wi-Fi
>Networks
>Document date:	2015-07-03
>Group:		Individual Submission
>Pages:		24
>URL:           =20
>https://www.ietf.org/internet-drafts/draft-fu-rmcat-wifi-test-case-00.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-fu-rmcat-wifi-test-case/
>Htmlized:      =20
>https://tools.ietf.org/html/draft-fu-rmcat-wifi-test-case-00
>
>
>Abstract:
>   Wireless network is becoming the dominiant mode of Internet access
>   nowadays.  According to statisics gathered by Cisco regarding usage
>   of interactive real-time interactive media (e.g., video conferencing
>   calls) across different types of clients, 76.12% of the calls are
>   over Wi-Fi networks, 23.84% are over cellular, and only 0.04% are
>   over Ethernet.  [Editor's note: need some clarification/reference
>   regarding source of this data].  It is therefore important to
>   evaluate candidate congestion control schemes designed for real-time
>   interactive media over test cases that include Wi-Fi access links.
>   This draft serves such a purpose, and is complementary to
>   [I-D.ietf-rmcat-eval-test] and
>   [I-D.draft-sarker-rmcat-cellular-eval-test-cases]
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Mon Jul  6 05:02:12 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27A621ACE3E; Mon,  6 Jul 2015 05:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 OS7UuxmIphdX; Mon,  6 Jul 2015 05:02:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4441ACDDD; Mon,  6 Jul 2015 05:02:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150706120207.18080.31912.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jul 2015 05:02:07 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/IG0jqC01BngtzK8o49On5MFSyXE>
Cc: rmcat@ietf.org
Subject: [rmcat] I-D Action: draft-ietf-rmcat-scream-cc-01.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jul 2015 12:02:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the RTP Media Congestion Avoidance Techniques Working Group of the IETF.

        Title           : Self-Clocked Rate Adaptation for Multimedia
        Authors         : Ingemar Johansson
                          Zaheduzzaman Sarker
	Filename        : draft-ietf-rmcat-scream-cc-01.txt
	Pages           : 32
	Date            : 2015-07-06

Abstract:
   This memo describes a rate adaptation algorithm for conversational
   video services.  The solution conforms to the packet conservation
   principle and uses a hybrid loss and delay based congestion control
   algorithm.  The algorithm is evaluated over both simulated Internet
   bottleneck scenarios as well as in a LTE (Long Term Evolution) system
   simulator and is shown to achieve both low latency and high video
   throughput in these scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rmcat-scream-cc/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rmcat-scream-cc-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jul  6 05:06:42 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C0D1ACE50 for <rmcat@ietfa.amsl.com>; Mon,  6 Jul 2015 05:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 3oz9lz1mbhU8 for <rmcat@ietfa.amsl.com>; Mon,  6 Jul 2015 05:06:39 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 324E61ACE46 for <rmcat@ietf.org>; Mon,  6 Jul 2015 05:06:39 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-0e-559a6f4d834a
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 32.44.12828.D4F6A955; Mon,  6 Jul 2015 14:06:37 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.44]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0210.002; Mon, 6 Jul 2015 14:06:36 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: I-D Action: draft-ietf-rmcat-scream-cc-01.txt
Thread-Index: AQHQt+OiFu1fWtCZ9UCQrxw2Bizcpp3OV+fw
Date: Mon, 6 Jul 2015 12:06:36 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129911D3@ESESSMB307.ericsson.se>
References: <20150706120207.18080.31912.idtracker@ietfa.amsl.com>
In-Reply-To: <20150706120207.18080.31912.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+Jvja5v/qxQg1v/VSxW3/zA5sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujNeNGgWzhCredfWxNjAe4uti5OSQEDCR+Na+ixnCFpO4cG89 WxcjF4eQwFFGiSsNnawQziJGiV2H/wJlODjYBGwkHi/2A2kQEVCV2NL/hw3EFhawkvg3fz0j RNxaYsf/N1C2kcSOaxPBbBYBFYklj7cygdi8Ar4Sbxc3sYPYQgKOEq/3LQKLcwo4Scy/th3s IEagg76fWgMWZxYQl7j1ZD4TxKECEkv2nIc6WlTi5eN/rBC2osTV6cuh6nUkFuz+xAZha0ss W/iaGWKvoMTJmU9YJjCKzkIydhaSlllIWmYhaVnAyLKKUbQ4tbg4N93IWC+1KDO5uDg/Ty8v tWQTIzAiDm75rbuDcfVrx0OMAhyMSjy8D1bMDBViTSwrrsw9xCjNwaIkzjtjc16okEB6Yklq dmpqQWpRfFFpTmrxIUYmDk6pBkZNdZdZS4+G/rdsq2ISe/mz4Py/I5e+HBB88VOIaZnNaZms 2lWLrWMfmoQ25SVM1fxx05n54Ya595krOGRYeHQdxdcKvPlad5pBp2Pl8VPqMw5/eKY5ce3c 20V6szyiYs2zT4flqXt4b2rLb3gn+u90v2ViXaXmt/P9Qr/mnbvBZTBz6knWvP9KLMUZiYZa zEXFiQCpZtIhaQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/7ILNzhIJjPD2DDKfxD9gJaGYDJc>
Subject: Re: [rmcat] I-D Action: draft-ietf-rmcat-scream-cc-01.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jul 2015 12:06:41 -0000

Hi all,

Minor updates on SCReAM draft. Added an "Implementation Status" section acc=
ording to RFC 6982.

BR

Zahed and Ingemar.

> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: den 6 juli 2015 14:02
> To: i-d-announce@ietf.org
> Cc: rmcat@ietf.org
> Subject: I-D Action: draft-ietf-rmcat-scream-cc-01.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the RTP Media Congestion Avoidance Techniqu=
es
> Working Group of the IETF.
>=20
>         Title           : Self-Clocked Rate Adaptation for Multimedia
>         Authors         : Ingemar Johansson
>                           Zaheduzzaman Sarker
> 	Filename        : draft-ietf-rmcat-scream-cc-01.txt
> 	Pages           : 32
> 	Date            : 2015-07-06
>=20
> Abstract:
>    This memo describes a rate adaptation algorithm for conversational
>    video services.  The solution conforms to the packet conservation
>    principle and uses a hybrid loss and delay based congestion control
>    algorithm.  The algorithm is evaluated over both simulated Internet
>    bottleneck scenarios as well as in a LTE (Long Term Evolution) system
>    simulator and is shown to achieve both low latency and high video
>    throughput in these scenarios.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rmcat-scream-cc/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rmcat-scream-cc-01
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Mon Jul  6 14:00:43 2015
Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049461A893F for <rmcat@ietfa.amsl.com>; Mon,  6 Jul 2015 14:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 BhDtal1d2E1l for <rmcat@ietfa.amsl.com>; Mon,  6 Jul 2015 14:00:40 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72ADF1B321B for <rmcat@ietf.org>; Mon,  6 Jul 2015 14:00:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2163; q=dns/txt; s=iport; t=1436216440; x=1437426040; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=oxrGvFZGs6OH7H37K7e2M88esQPy9R5ZEoBAcbX876E=; b=gvdLUHjJuE7gH3OgV6flT+vGfWduuDZ+303UwNajYv0OnuCi7Jh6KXRI nMg3lrtaj81cH7VzFrogfQwDIVT+0rXdu28QAhpbg+f5mDWQDSmG6FC74 aL/gqylPwoON9ZAWVTbc1r/vJ7iWaRYMJ396eiWcO8/81NZ1rm50olOPH E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+AwB065pV/5pdJa1cgxJUYAa9VwmBcIV1AoE7OBQBAQEBAQEBgQqEJAEBBA5XEgIQAgEIRjIbAQYDAgQOBYguDctVAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tLhQYHhCsFjBk4h0QBhGGHBoE6RINRkwcmg3tvgUeBBAEBAQ
X-IronPort-AV: E=Sophos;i="5.15,417,1432598400"; d="scan'208";a="165718585"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-2.cisco.com with ESMTP; 06 Jul 2015 21:00:39 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t66L0cUX017170 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Jul 2015 21:00:38 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.136]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0195.001; Mon, 6 Jul 2015 16:00:38 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: rmcat WG <rmcat@ietf.org>
Thread-Topic: New Version Notification for draft-zhu-rmcat-video-traffic-source-02.txt
Thread-Index: AQHQuAzBIwf7d1b71kaGg1ZnKJlkbp3O7YIA
Date: Mon, 6 Jul 2015 21:00:37 +0000
Message-ID: <D1C01DDC.22657%xiaoqzhu@cisco.com>
References: <20150706165646.10418.3364.idtracker@ietfa.amsl.com>
In-Reply-To: <20150706165646.10418.3364.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.152.13.87]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C63811594FC374419EDCC3763032F8EE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/S7XJnCB_mvXlZtw8WCMtJLhXuK8>
Cc: "Sergio Mena de la Cruz \(semena\)" <semena@cisco.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: [rmcat] FW: New Version Notification for draft-zhu-rmcat-video-traffic-source-02.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jul 2015 21:00:42 -0000

Hi,=20

This is an updated version of the draft, with changes mainly in sections
4, 6, and 7. We=B9ve also added a section (8) on Implementation Status as w=
e
intend to share via open source our code for the trace-driven model (still
pending internal approval).

Thanks,
Xiaoqing


On 7/6/15, 11:56 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-zhu-rmcat-video-traffic-source-02.txt
>has been successfully submitted by Xiaoqing Zhu and posted to the
>IETF repository.
>
>Name:		draft-zhu-rmcat-video-traffic-source
>Revision:	02
>Title:		Modeling Video Traffic Sources for RMCAT Evaluations
>Document date:	2015-07-03
>Group:		Individual Submission
>Pages:		15
>URL:           =20
>https://www.ietf.org/internet-drafts/draft-zhu-rmcat-video-traffic-source-
>02.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-zhu-rmcat-video-traffic-source/
>Htmlized:      =20
>https://tools.ietf.org/html/draft-zhu-rmcat-video-traffic-source-02
>Diff:          =20
>https://www.ietf.org/rfcdiff?url2=3Ddraft-zhu-rmcat-video-traffic-source-0=
2
>
>Abstract:
>   This document describes two reference video traffic source models for
>   evaluating RMCAT candidate algorithms.  The first model statistically
>   characterizes the behavior of a live video encoder in response to
>   changing requests on target video rate.  The second model is trace-
>   driven, and emulates the encoder output by scaling the pre-encoded
>   video frame sizes from a widely used video test sequence.  Both
>   models are designed to strike a balance between simplicity,
>   repeatability, and authenticity in modeling the interactions between
>   a video traffic source and the congestion control module.
>
>                 =20
>       =20
>One of the co-authors was omitted by the automatic meta data extraction
>process. Therefore need to fill in author info manually.
>
>Thanks.=20
>=20
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Tue Jul  7 10:54:25 2015
Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 581511ACF17 for <rmcat@ietfa.amsl.com>; Tue,  7 Jul 2015 10:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ffNt7hxml0tl for <rmcat@ietfa.amsl.com>; Tue,  7 Jul 2015 10:54:23 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1BAD1ACF0A for <rmcat@ietf.org>; Tue,  7 Jul 2015 10:54:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1725; q=dns/txt; s=iport; t=1436291664; x=1437501264; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Xvle2FrhcHsTv5nEBcPLXMg/3pBG66/aiWgP21lJ9AU=; b=fF7uS4qxPEiAsynkCftE6NJju7JM3Cs933FB0iyPPQFxAVchnp3h9NZv cZVnpxhIAg/gykFEPeJ5urxmieR9gDQKDzMqtZD+XNreVbsd8JV3oPlzF p04AhH0F61kLhryTt3TwvkoL5hhq2pBtM6r0tS0YfDKz/BzwnoQJiTIsY E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BuAwBkEZxV/5pdJa1bgxJUYAa9ZgmBcYV1AoFbOBQBAQEBAQEBgQqEJAEBBDo9AhACAQg2EDIbAQYDAgQOBYguDcw9AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tLhQYHhCsFjByHfAGEYYcHgTpFg1KTCSaDe28BgUaBBAEBAQ
X-IronPort-AV: E=Sophos;i="5.15,425,1432598400"; d="scan'208";a="13382961"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 07 Jul 2015 17:54:23 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t67HsMr4000335 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rmcat@ietf.org>; Tue, 7 Jul 2015 17:54:22 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.136]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Tue, 7 Jul 2015 12:54:21 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: rmcat WG <rmcat@ietf.org>
Thread-Topic: New Version Notification for draft-fu-rmcat-wifi-test-case-01.txt
Thread-Index: AQHQuEDJ8QvuNL0ypE6rKs5H4yQmWp3QS2OA
Date: Tue, 7 Jul 2015 17:54:21 +0000
Message-ID: <D1C17C39.22A70%xiaoqzhu@cisco.com>
References: <20150706230913.20855.582.idtracker@ietfa.amsl.com>
In-Reply-To: <20150706230913.20855.582.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.152.13.144]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26BE0E2CC8A8904682953B590CC6EB0F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/DzNWuCW_SnzTx6gg86k_jDOx-8c>
Cc: "Jeromy Fu \(jianfu\)" <jianfu@cisco.com>, "Michael Ramalho \(mramalho\)" <mramalho@cisco.com>, "Dan Tan \(dtan2\)" <dtan2@cisco.com>
Subject: [rmcat] FW: New Version Notification for draft-fu-rmcat-wifi-test-case-01.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Jul 2015 17:54:24 -0000

Hi,

Here is an updated version with some further minor revisions.

Thanks,
Xiaoqing
=20

On 7/6/15, 6:09 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-fu-rmcat-wifi-test-case-01.txt
>has been successfully submitted by Xiaoqing Zhu and posted to the
>IETF repository.
>
>Name:		draft-fu-rmcat-wifi-test-case
>Revision:	01
>Title:		Evaluation Test Cases for Interactive Real-Time Media over Wi-Fi
>Networks
>Document date:	2015-07-06
>Group:		Individual Submission
>Pages:		24
>URL:           =20
>https://www.ietf.org/internet-drafts/draft-fu-rmcat-wifi-test-case-01.txt
>Status:        =20
>https://datatracker.ietf.org/doc/draft-fu-rmcat-wifi-test-case/
>Htmlized:      =20
>https://tools.ietf.org/html/draft-fu-rmcat-wifi-test-case-01
>Diff:          =20
>https://www.ietf.org/rfcdiff?url2=3Ddraft-fu-rmcat-wifi-test-case-01
>
>Abstract:
>   An increasing proportion of multimedia communication applications,
>   including real-time interactive voice and video, are transported over
>   Wi-Fi networks (i.e., wireless local area networks following IEEE
>   802.11 standards) today.  It is therefore important to evaluate
>   candidate congestion control schemes designed in the RMCAT Working
>   Group over test cases that include Wi-Fi access links.  This draft
>   serves such a purpose, and is complementary to
>   [I-D.ietf-rmcat-eval-test] and
>   [I-D.draft-sarker-rmcat-cellular-eval-test-cases]
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Wed Jul  8 10:53:24 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E62A51A1BDA for <rmcat@ietfa.amsl.com>; Wed,  8 Jul 2015 10:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.21
X-Spam-Level: 
X-Spam-Status: No, score=-3.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ymFn_t9RCsg0 for <rmcat@ietfa.amsl.com>; Wed,  8 Jul 2015 10:53:20 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 504D51A1BD2 for <rmcat@ietf.org>; Wed,  8 Jul 2015 10:53:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 9A71ED930E; Wed,  8 Jul 2015 19:53:18 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id v8ajYuyvSM56; Wed,  8 Jul 2015 19:53:18 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 47EF9D9302; Wed,  8 Jul 2015 19:53:18 +0200 (MEST)
Message-ID: <559D638D.1040307@tik.ee.ethz.ch>
Date: Wed, 08 Jul 2015 19:53:17 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>,  "Michael Ramalho (mramalho)" <mramalho@cisco.com>, "Sergio Mena de la Cruz (semena)" <semena@cisco.com>,  charles.ganzhorn@gmail.com, paulej@packetizer.com,  stefano.daronco@epfl.ch, "rmcat@ietf.org" <rmcat@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/LRuwjxf1QlzQOwNBwkV-_BcBfjM>
Subject: [rmcat] Review of draft-ietf-rmcat-nada-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 08 Jul 2015 17:53:24 -0000

Hi Xiaoqing, hi all,

this is a review as an individual contributor and not as a wg chair.

I think the document is well written but I had some problem to easily follow 
some of the details. I think this could be easily improved a lot by renaming 
(nearly all) variables; I'll give further suggestions on this below. My main 
problem, however, was on understanding the formula(s) in section 5.1.2. This is 
partly because of the excessive use of variables with not super helpful names, 
but mostly because there is no reasoning giving why the formula looks the way it 
looks! As not currently done in the draft, could you maybe explain on the 
mailing list now, how you came up with this formula? What are the different 
components good for? How did you decided to add all these calculations?

Further there are some parts where a more detailed description is needed (see 
also further comments below). This document should allow people to re-implement 
NADA without knowing your code. I think there are a number of details missing in 
the description and other parts are not specified well enough as probably 
considered as implementation-specific details. However, I think there are things 
that actually will influence NADA performance if implemented differently and 
should therefore be further specified as well (at least one default approach), 
e.g. the filtering of delay values.

See more detailed comment in the order of the document structure below:

1) This is a rather general comment on the first paragraph in the introduction 
and may apply to other schemes as well: You mention challenges here. However, 
you don't refer to the rmcat requirements doc. Maybe you should refer this 
somewhere and potentially even discuss if and how the requirements have been 
address, or at least how the challenges you mention here are reflected in the 
requirements doc.

2) I would recommend to rename section 2 to 'Overview' instead of 'System Model' 
because that is what is actually is; it gives a summary description of what NADA 
is doing. As this text already introduced a number of variables, I would highly 
recommend to have Figure 1 already here because I needed to look at the Figure 
(knowing that there is one) to actually understand the text. Further I don't 
think the first point mentioning the source media stream is needed as this is 
also not shown in the figure.

3) Further I would recommend one new, own section that lists all variables and 
parameters! That would help really a lot!
Please also note that there is a difference between variables and parameters. 
Parameters are things that have a predefined value that you set once, while 
variables change over time. Usually parameter are noted in all upper case 
letters. In your currently description, parameters and variables look the same 
which makes things super difficult to read. E.g. d_th is a parameter and should 
be D_TH, or even better DELAY_THRES. And that's the second recommendation: I 
would recommend use longer, more descriptive names in many case because it helps 
the reader to follow. Further if you are going to have an own variables and 
parameter section, please indicate all default values for parameters.

4) On section 4.1
- t_r,n is hard to read, use t_{r,n} or t_r_n or even better ts_rec_n
- I'd also recommend to following variable names:
   z_n -> owd_n
   d_n -> qdelay_n
   d_f -> delay_base or owd_base
   d_hat_n -> qdelay_n_filter (or what does 'hat' stand for? or don't use 
d_hat_n at all and just have one more formula: d_n >- filter(d_n)...
- Please describe the estimation of the base delay in more detail because I 
think that's a case where there can be an influence on performance. E.g. in 
LEDBAT the minimum of 1-minutes minutes of the last 10 minutes is used.
- Did you also try a 2-point minimum filter? That's even easier and I'd assume 
that would be sufficient in most cases? Or what's the reason for the 5-point 
median filter?
- Do the clocks have to be synchronized for this approach? Please discuss this 
somewhere!

5) On section 4.2
- This section introduces a parameter without naming it (500ms). This is 
actually the same 500ms as introduces as delta in equation (2), right? Further I 
don' think 500ms is a good recommendation here. This value MUST be larger than 
one RTT and therefore there is a dependency on the RTT. Therefore for my point 
of view the recommendation should be something like 3*RTT and not a fixed value.
- Please specify more concretely the exponential smoothing filter that is used. 
Especially which weight is used!?!

6) I've detected a number of case, where the documents basically says something 
like 'further work is need here'. I would find it very helpful (also as a chair) 
to list all these issues in a open issues section. There are three issues I've 
found so far in section 4.2, 4.7 and 5.1:
   - Alternative approach to calculate the loss ratio (as e.g. TFRC)
   - OWD vs. RTT
   - Choice of start value
+ of course all discussion on parameters (which would include the question if a 
certain value is a MUST e.g. because of fairness reason, or if there is range to 
choose from)

7) Section 4.3
- I think this section should be a subsection of 4.1 because it's 'just' further 
steps to get the delay estimate.
- The formula was super hard to parse for me because there usually should be a 
large bracket. Maybe make it like this (as a graphic):

                      /  (d_hat_n),                  if d_hat_n < d_th;
                      |
                      |       (d_max - d_hat_n)^4
         d_tilde_n = <   d_th --------------------,  if  d_th<d_hat_n<d_max;
                      |         (d_max - d_th)^4
                      |
                      \   0,                         if d_hat_n > d_max.

- Parameters: d_max -> DELAY_MAX
               d_th -> DELAY_THRES

8) On section 4.4
- Why is this done on receiver side? Isn't there already some loss feedback in 
RTCP that could be used on sender side instead of sending a new report?
- Does the values of d_M=200ms and d_L=1s assume that the loss and marking 
probabilities are configured differently at the network node; lower marking 
threshold? Don't those values strongly depend on the configuration in the 
network node? Is it important that all competing NADA flows use the same value 
(for fairness)?
- I'm wondering if you really need to aggregated congestion anymore as you 
already have the scheme in section 4.3...? Wouldn't it be sufficient to use the 
estimated delay if there is no loss and use the other signals differently. E.g. 
if there is loss, halve as traditional cc would do?
- I think tuning these value is also an open issue and an important one!

9) Section 4.6
- Can't this part be done at the sender as well and then you don't have to 
transmit x_n'?
- Why do you need a feedback interval of 100ms if you only update any 
information every every 500ms?
- And if 250ms is sufficient, why do you use 100ms?

10) I'd recommend to move section 4.7 into an own section (7) at the end of the 
doc because it is not part of the algorithm description but 'only' some discussion.

11) "The sender initializes the reference rate R_n as R-min by default, or to
a value specified by the upper-layer application."
-> I think this is a big open issue. I don't think the application should 
specify this value because it could be misused, but the initial rate must fit to 
the initial coding I guess. So 10 packet/RTT might be to low...? Which rate are 
you using currently?

12) Section 5.1 say "if the reported queuing delay is close to zero". What does 
'close to zero' mean? Do you have another threshold here? How did you implement 
this? Please give a more detailed description here!

13) Section 5.1.1:
- "A typical value of T_th is 50ms." Does all NADA flows need to have the same 
value to be fair? Than this is a MUST value!
- "The rate R_n is updated as follows:" This does not specify when the rate is 
updated. On arrival of each report?
- This implements a multiplicative increase therefore I would denote the 
equation the following way:
   R_n = R_r + alpha * R_r
   I would also call the increase factor alpha as this is usually used in 
congestion control.
- I'm not sure if it is right that the increase rate should the large the 
smaller the base delay is. I'd say it should be the other was around. Please 
provide some reasoning here! Further is delta actually needed here? Or please 
explain further what the target ACK interval actually is!
- gamma_0 is also a confusing naming, should be gamma_max or alpha_max as 
suggested above.

14) Section 5.1.2:
- As I said, I've been starring at this for at least 15 minutes and could not 
figure out why you came up with this. This is my main issue. Please explain!
- Isn't delta_s the same than delta? Why don't you use the same parameter name? 
Again, should be DELTA or DELTA_REPORT.

15) Section 5.2 could be moved into section 2 because it again does not describe 
the algorithm.

16) The equation given in section 5.3 is really complicated where you actually 
just want to have the current number of bytes in the buffer. I think this is 
over-specified and would not need a formula. Further the use of the word size is 
confusing. A buffer size for me is the maximum amount of bytes a buffer could 
hold. I think you mean the current buffer occupancy (in bytes)...?

17) Please give values for beta_v and beta_s (as used in your implementation). 
Further I'm not sure if it is a good idea to adjust both R_v and R_n at once. 
Wouldn't it be sufficient to only adjust R_v?

18) One last comment on PCN (see last paragraph section 6): PCN was designed for 
admission control in one DiffServ domain and not the Internet, therefore this is 
not applicable here!

As a general recommendation (what I learn from my own work on congestion 
control), simplification is always a goal even if performance might be slightly 
worse: a simpler algorithm is easier to understand and therefore easier to 
evaluate, and people will be more likely to use it and make less implementation 
errors. So maybe at this stage you might want think about where you potentially 
could simplify NADA. Because I think up to now you only added stuff to make it 
work, but maybe there is now also something that could be removed instead...? 
Not sure if that's possible, just an idea...

Find other nits/proposals below:

s/The RTP sender also generates RTP timestamp in outgoing packets./The RTP 
sender also provides an RTP timestamp within each outgoing packets./

s/it is discounted following a non-linear curve/it is scaled down following a 
non-linear curve/

s/see Sec. 6.1.1 Accelerated ramp-up/see Sec. 5.1.1 Accelerated ramp-up/

s/R-min/R_min/

s/its rate increase after at least one round-trip time/its rate increase after 
at minimum one round-trip time/

s/ the rate increase multiplier should decrease with the delay  in the feedback 
control loop,/ the rate increase multiplier should smaller the larger the base 
delay in the feedback control loop is,/


Mirja


From nobody Fri Jul 10 05:06:21 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA0681A87BB for <rmcat@ietfa.amsl.com>; Fri, 10 Jul 2015 05:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.91
X-Spam-Level: 
X-Spam-Status: No, score=-5.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Qru-9Wdoj9LA for <rmcat@ietfa.amsl.com>; Fri, 10 Jul 2015 05:06:15 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EABC41A87EB for <rmcat@ietf.org>; Fri, 10 Jul 2015 05:06:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 879D0D9305; Fri, 10 Jul 2015 14:06:13 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eWl97fZxLS2x; Fri, 10 Jul 2015 14:06:13 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 42787D9302; Fri, 10 Jul 2015 14:06:13 +0200 (MEST)
Message-ID: <559FB533.5090105@tik.ee.ethz.ch>
Date: Fri, 10 Jul 2015 14:06:11 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>,  Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/dS5L9rILn18lbTLFypH3f2xmmXQ>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 10 Jul 2015 12:06:19 -0000

Hi Zahed, hi Ingemar,

please find my review as an individual contributor below.

First of all I have a few general question on the algorithm(s):

1) When calculating cwnd you on the one hand calculate scl_i to basically 
quickly speed up to the previous maximum value cwnd_i and on the other hand try 
to maintain a low delay target. Aren't these two conflicting goals? Without 
having looked at your experimentation results now, I'd expect that you even when 
you are alone on the link induce more than owd_target delay (actually depending 
on the maximum buffer size as reflected by cwnd_i), and when competing with 
other traffic, you'd still cannot reach an equal sharing but will always get a 
lower share. Which is probably okay; however the part that maybe worries my a 
little is that the achieved delay and/or achieved sharing probably depends on 
the configured maximum buffer size (which might be large)...? Can you comment on 
this or provide more detail results on this?

2) I would have expected that the video rate controller takes cwnd or the actual 
sending window as an input parameter. However, your approach seems to have two 
more or less independent control loops for the sending rate and the coding rate. 
That seems quite weird to me (however the reasoning behind the design of the 
video coder is also not really clear to me; see below for further comments on 
this). I'd be worried that if those two loops are rather independent that they 
could actually make conflicting decision, e.g. video controller increases the 
rate and congestion controller decreases the rate. Also wouldn't it be useful to 
use the cwnd as an input parameter? Please comment!


And two more high-level/general comments on (the structure of) the document:

1) I think the algorithm is now well understandable with the code and respective 
explanation (expect the end of section 4.1.3 needs more explanation as just 
mentioned above). I would still like to propose some restructuring. I think the 
readability can be much improved by some rather simple restructuring using a 
model similar as in the LEDBAT draft: First give a high level summarize of all 
steps that have to be performed ("For each ACK/report the state on the delay and 
delay trend will be updated. If a loss is detected the congestion window cwnd 
will be decreased strongly, otherwise there are two operation mode: fast 
increase and regular operation. In fast increase the goal is to reach a previous 
target value quickly applying an multiplicative increase scheme, while otherwise 
a delay traget should be maintained..."). Then give all the pseudo code 
structured into functions and finally explain each function block in detail in 
an own paragraph. I already have a good idea how this would look like and if you 
want to we can sit down at the meeting and do this together.

2) Having reviewed NADA and Scream now basically in one go, I think the used 
framework is very similar. If you look at your Figure 1 and the Figure 1 in the 
NADA draft, I think I'm now basically able to do a 1:1 mapping. However, I think 
in your picture it is wrong to have multiple video coder/rate controller/queues 
shown because that indicates that there is only one transmission scheduler and 
congestion controller for all transmissions, which is not the case. If you 
remove that part, there is only one difference left between the two images and 
that is that there is an input from the congestion control to the video rate 
controller in NADA which you don't have (also see comment 2 above). Other than 
that the mapping would be the following way:

NADA
---
Reference Rate Calculator    -> Network congestion control
Video Target Rate Calculator -> Rate Control
Sending Rate Calculator      -> Transmission scheduler
Encoder                      -> Video Encoder
Rate Shaping Buffer          -> Queue RTP packets

I think it would be super helpful to use a common terminology here for everybody 
to better understand similarities and differences. I guess the same is true for 
variable and parameter names if there things that are actually the same. Note 
that you in some case already use the same names (I didn't check however if the 
things that have the same name actually are the same things...)

3) I think it is great to have a section to list all parameters and values. 
Thanks! However I do have to say I find tables here not the right choice because 
it just stretches the information over more pages than needed and therefore 
makes it actually harder to find the right bit. Further there are a few 
variables that are actually parameters and listed wrongly. Two examples I've 
found are: mss and min_cwnd (should be MSS and MIN_CWND which you even write 
this way sometimes). Further for variables I would not indicate the initial 
values here. I'd propose to have a init function instead in the later 
description where one can see all initial value at once (like in the LEDBAT 
draft). Further please review if all variables are actually needed. If there are 
only temporal and not variables that actually hold state in the pseudo code, I 
don't think they need t be listed here.


Further comments following the structure of the document:

Section 1: I've also made this comment regarding the NADA doc: I guess every 
algorithm doc should refer the requirements doc and to some extend discuss if 
and how these requirements have been addressed...

Section 1.1: not sure why this section is there; don't see a need to have this 
information in this document because it doesn't help me understand the algorithm 
any better.

Section 3:
- s/follows packet conservation principles/follows the packet conservation 
principle/
- I think think FACK is not the right reference for the packet conservation 
priniple, should be  "Congestion Avoidance and Control" by Van Jacobsen and 
Michael J. Karels, SIGCOM'88 (see reference Jac88 of FACK paper).
- s/The packet conservation principle is realized by/In Scream, the packet 
conservation principle is realized by/ -> otherwise it sounds like it's always 
realized this way, which is not true.
- Maybe give already a super brief description of what LEDBAT is doing:
   s/in a way similar to LEDBAT [RFC6817]./in a way similar to LEDBAT [RFC6817] 
by maintaining a given target delay./
- This text further say "a few steps to take to make the concept work with 
conversational media". Maybe already name these steps very briefly here: e.g. 
taking the delay trend into account and the previous maximum rate to compete 
with other non-delay based traffic...

Section 3.1
- You say there are similarities with newcwv but then never mention this again. 
Can you explain what the similarities are? I've just reviewed newcwv and this is 
absolutely not clear to me...
- Fast start: May I propose to name this Fast Increase instead (and also always 
write this with upper letters). Actually that's the same name I used for TCP 
SIAD where I also have this mechanism that is kind of similar to Slow Start but 
can be resumed later as well. I propose this change (not just because I want my 
name to be used ;-) but) because having 'start' in the name is confusing to my 
if you not only use this mechanism to actually start or re-start a transmission.
- Also maybe be slightly more concrete here (on a high level) about what fast 
start is doing: e.g "implements and multiplicative increase to quickly reach the 
maximum capacity where the increase factor is scaled based on a previous maximum 
rate (expect at transmission start). Fast start is resumed during a transmission 
if the delay trend goes below a certain threshold." Btw. I would also appreciate 
to introduce a parameter for this threshold and not only say "less than 0.2 for 
1.0 seconds or more" (see later in section 4.1.2.1).
- s/with FTP traffic/with bulk traffic/

Section 3.2.
- This section says packet pacing is used, however I don't think this is further 
mention in the rest of the text... please add something on this... or there 
might be a confusion between me and you what pacing means (see below).

Section 3.3.
- Maybe already include the relevant part of figure 1 here because a figure 
really helps. Or include the whole figure 1 in section 3 and structure the 
overview based on this image.

Section 4.1
- I guess you can remove the reference to I-D.ietf-rmcat-app-interaction because 
we are working on this draft anymore. However, it was anyway not clear what 
exactly you are referencing it for. From my point of view explaining the 
relationship to other docs (of the same wg) is often done best in the intro.
- On Figure 1: As said above I find it confusing that there are multiple video 
streams here because that indicates that there is only one congestion controller 
and one transmission scheduler for all transmissions. For the same reason I 
actually find the name transmission scheduler confusion because a scheduler 
would actually be the one who decides which packet to put on the link at which 
time (which often is done on the nic). However your transmission scheduler is 
'only' calculating the sending window, therefore I call it something like 
sending rate controller...

Section 4.1.2.1
- At the beginning of this section you define some terminology. Maybe put this 
in the terminology section instead?
- I've also asked this question for NADA: Don't you need synchronized clocks at 
the sender and receiver. Please further discuss this!
- Please also give more details how loss detection is done. I guess that's 
simply indicated in an RTCP report..? Please say which information are exactly used.
- Please give also some kind of pseudo code on how bytes_newly_acked is updated. 
That simply helps people to implement things correctly.
- As said above I would structure the pseudo code in functions where one 
function would be an init function here. That also helps to avoid implementation 
errors.
- Please give more details how the function R() is implemented.
- Why is scl_i called this way? What does the i stand for? Maybe take a slightly 
longer more meaningful name like scale_increase. This helps the reader to 
immediately understand what this is later used for!
- Why is scl_i limited to 0.2? Should this also a parameter?
- Please give some reasoning why scl_i is calculated this way! Is this similar 
to Cubic? If so please refer!
- I believe the calculation of off_target is only needed if not in fast start. 
If so please move it!
- cwnd_i is initialized to 1. That seems really weird to me. Does this work well 
for fast start at a beginning of a transmission? I guess the intention is to 
make fast start behave like slow start at the beginning of a connection. In this 
case scl_i should be 1. Why don't you just set scl_i to 1 if cwnd_i has not been 
set yet...?
- gain calculation: owd_trend is always a value between 0 and 1, therefore it 
can not be negative, therefore the max() in the gain calculation can be removed:
gain = GAIN*(1.0 + (1.0 - owd_trend/ 0.2))
- Where is this 0.2 in this gain calculation again coming from. Is there a good 
reasoning for this value? Should this be again a parameter? Is this the same 
parameter than the previous 0.2?
- I'd move the discussion what the difference to LEDBAT is into section 3.1 
because these point are very general and therefore no algorithm details are 
needed to be known and you mention those difference there already without saying 
what they actually are.
- However, you say you don't use ALLOWED_INCREASE but isn't 
MAX_BYTES_IN_FLIGHT_HEAD_ROOM effective the same...?
- The part on flow compensation is rather unclear! Suddenly you have two new 
parameters owd_norm_mean_sh and owd_norm_var: how are they calculated? When are 
they updated? I think there is something missing somewhere. Further where does 
this formula come from? I guess there is some previous working that proposed 
this approach? Can you give a reference and further explain why this approach is 
taken?

Section 4.1.2.2
- I'd move the initial part here with the two bullet points into section 3.2 
because this is rather some high level info.
- I don't think I would call the proposed approach pacing. Pacing is for me that 
if you can send you multiple packet at once (because the send/congestion window 
is large enough) that you spread the sending times of each packet over the time 
interval until the next ACK/update is expected.
- Further the calculation seems rather complicated. Is this really needed? Can 
you further explain in the doc in which case this approach helps which problem 
and why?!

Section 4.1.3
- Why is the estimation interval 200ms (shouldn't this be a parameter as well?) 
but the RATE_ADJUSTMENT_INTERVAL 100ms? If you only estimate every 200ms there 
will be no new information after 100ms to adjust something...?
- s/ if the congestion control is if fast start or not./ if the congestion 
control is in fast start or not./
- In general, as mention above, there is more explanation needed on the single 
steps of the video rate controller, especially on
   - What is RMAP_UP_TIME actually good for? Why is this 10s?
   - Please explain further why increment is calculated the way it is calculated!
   - Shouldn't the target_bitrate be only increased in steps that the encoder 
can handle?
   - Please you further explain the last part on rate_rtp_limit!!!

Section 4.2
- Here the table is good because there are less values and it actually provides 
a nice overview!

Section 5.
- This needs to go in an own draft at some point. Please also compare 
similarities with the information needed by NADA and GCC!

Section 7
- Actually a conclusion is not needed for an IETF Internet draft...

Section 8
- regarding the clock drift compensation, please see the appendix of the LEDBAT 
RFC. If you've implemented basically the same thing as described there, it 
probably enough to refer to that.

Mirja


From nobody Fri Jul 10 08:59:16 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321611B29E0 for <rmcat@ietfa.amsl.com>; Fri, 10 Jul 2015 08:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9h_BalSDfuNS for <rmcat@ietfa.amsl.com>; Fri, 10 Jul 2015 08:59:12 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E2C11B2CA2 for <rmcat@ietf.org>; Fri, 10 Jul 2015 08:59:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 8722DD9307; Fri, 10 Jul 2015 17:59:10 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2GC6og2WK7xc; Fri, 10 Jul 2015 17:59:10 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 4B2D1D9302; Fri, 10 Jul 2015 17:59:10 +0200 (MEST)
Message-ID: <559FEBCC.3060604@tik.ee.ethz.ch>
Date: Fri, 10 Jul 2015 17:59:08 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Stefan Holmer <holmer@google.com>, gaetano.carlucci@poliba.it,  Luca De Cicco <l.decicco@poliba.it>, Saverio Mascolo <mascolo@poliba.it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/MhnZa8CM7yh_rO2V7SgvOkmoirg>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>
Subject: [rmcat] Brief review of draft-alvestrand-rmcat-congestion-03
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 10 Jul 2015 15:59:15 -0000

Hi Stefan, hi all,

I've had a quick review of draft-alvestrand-rmcat-congestion-03 as an individual 
contributor (not as chairs). I have a couple of high level comments and a few 
more detail once.

In general I, now after just reading NADA and Scream, found it slightly hard to 
read your draft because you are often use a different terminology and different 
variable names. Especially for the arrival model I wonder if you make things 
more complicated than they are. If I get you right, you effectively also just 
want to estimate the queuing delay which is your case however is denoted w(i). 
While the other approaches simply compare the sender and receiver timestamps 
(which requires synchronized clocks or at least additional mechanism to 
compensate for not-synchronized clocks), you look at the inter-arrival times at 
the sender and the receiver and basically estimate the difference between the 
sending rate and receiving rate and therefore... the queue... What I don't 
really understand it why to you need to look at groups of packets?

Further you are using a Kalman filter. That's seem also complicated. Other 
schemes use much simpler filters (like the min of the last few values or a mean) 
and achieve acceptable estimates as well. I can only say this again: simplicity 
is also an important goal when designing a successful mechanism.

As just mention I'd really would like to see more meaningful variable names. 
That really helps the reader. Examples are:
- gamma_1(i) -> effectively this your delay target, often called target_delay; 
don't think you need denote this as a function by writing (i) because it's 
simply a variable in our implementation, right?
- A_hat -> this reflects the target sending rate where the other rmcat proposal 
usually maintain a congestion window for, called cwnd. Btw. how do you maintain 
the send-out process? Is this ack-clocked/report-clocked? In this case it would 
make sense to maintain a window in bytes. Or is it timer-based where you 
calculate the next send-out time based on the rate? Anyway I'd rather like to 
see a longer more meaningful name like target-rate or output_rate (not sure you 
really need the _hat because effectively all your variables are _hat).
- R_hat(i) -> for window based schemes this information is kept as flight_size 
(number of bytes in flight)

There is one sentence that really confuses me (detailed comment). In 4.4 you say
"On every update the delay-based estimate of the available bandwidth
    is increased, either multiplicatively or additively, depending on its
    current state."
Here you mean A_hat(i), right? Because I would call this the target rate, while 
R_hat(i) would be an delay-based estimate...?

A few more detailed questions regarding the calculation of R_hat(i). Is that 
done at receiver-side? Why are you using a window between 0.5 and 1 sec? 
Shouldn't that depend on the RTT and at best be one RTT? Can you maybe give 
pseudo code for basically the second paragraph on page 11?

In general I think it would helpful to not only provide mathematical formulas 
but also some pseudo code that is closer to the implementation (in a couple of 
cases).

Next and final point is on number, there are a couple of numbers where it is not 
clear where they came from and why they have been chosen. I guess most of these 
numbers should be parameter that could be tested in different scenarios. These are:
- update interval for R_hat(i): 0.5-1s (see above)
- 8% increase factor -> really no idea with this has been chosen; actually seems 
rather low to me...
- 100ms add-on to RTT for the response time -> really don't understand why you 
don't simply take the RTT; however this should at least not be a fixed value 
from my point of view (but a factor...?)
- maximum increase rate of 0.5 packets per response time (TCP RENO should 
actually increase by 1 packet/RTT which is now fixed in the Linux kernel, I think)
- upper limit of 1.5*R_hat(i) for A_hat(i)...?
- alpha [0.8, 0.95] where 0.86 is recommended...??? Reno uses 0.5, Cubic should 
use 0.7. Where does this recommendation comes from? Btw. the decrease factor is 
usually called beta while the increase factor/rate is called alpha in AIMD/MIMD 
systems.
- And the number that worries me most is the loss level threshold for the 
loss-based controller... 2% and 10% ???? That's a lot! TFRC is not comparable in 
this case because you are only looking at the loss rate since the last report 
while TFRC looks at an average over a slightly longer time scale. With 
loss-based congestion control you have this probing behavior where there are no 
losses for a couple of RTTs (depending on the size of the congestion window/link 
speed) and then there are a couple of losses within one window. This should give 
you a relative low average loss rate (much belower than 10% and usually even 
below 1%) and the congestion control should reduce its sending rate immediately 
as soon as one loss is detected! If you now induce a loss rate of 2-10% this 
should starve all other competing flows! I'd say, for stability reasons you need 
to decrease as soon as there is loss detected. As you already apply this 
multiplicative decrease rule (A_hat(i) = alpha * R_hat(i) ) for delay, I really 
don't see why you are not using the same rule for loss...? I've quickly looked 
at your evaluation results and sees that GCC is able to co-exists with TCP. 
However I'd assume that in this case still only the delay-based controller 
controls the rate and the loss-based controller doesn't kick in at all. Can you 
confirm/check this?

Now looking at the results, I'd like to request three more things (Thanks!):
- Can you run one more simulation with more than one TCP flow?
- What happen if the TCP stops after a while? Does the target delay value gamma 
actually go down again? Can you plot gamma as well in this sceanrio?
- And can you show the plots on slide 33 (multiple GCC flows) for more than 120s 
because the flows seem to de-converge again.

Thanks for all the work though!

Mirja





From nobody Mon Jul 13 07:28:03 2015
Return-Path: <holmer@google.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B721B2B29 for <rmcat@ietfa.amsl.com>; Mon, 13 Jul 2015 07:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.612
X-Spam-Level: **
X-Spam-Status: No, score=2.612 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, GB_SUMOF=1, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Fl2EtETqse-5 for <rmcat@ietfa.amsl.com>; Mon, 13 Jul 2015 07:27:57 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (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 6AC9D1ACEB0 for <rmcat@ietf.org>; Mon, 13 Jul 2015 07:27:57 -0700 (PDT)
Received: by ietj16 with SMTP id j16so62905867iet.0 for <rmcat@ietf.org>; Mon, 13 Jul 2015 07:27:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=+wSLHLtP3XOmjbOqZU1vNBCV9p/zW6ns/1xfBRqDeBc=; b=UHYwuiFhO7bNvCW9xAkPgD6MLfXpyJ71skH83XR8c6Z6sdf92Hd1C9TpwaNNlGKGj+ w6YgVrbd4F/DLbYyQFC9e2Tk6FRMO3nvTpWOdbnazr+ypRghgaviWkdhKt87pVBt3VPJ +Fcf/s6dSn2IiZSPkWm6Yl8NdfNSkM0f7ANC50TtK9HWZ8Ol8iHuh5mATbnnEUimngDG vSq1WKCEh5pU4b2aLOchIvvIdC6Mh6dnSJfmshku1JBalE97qUZXMazDh7zCtNQmcP1k QbDfWDS0cM01IyCxfYnhfMO+QnxCaqEJooLD1Cx6eBavs0tQ80R8uJbVkNCMT9N/3l36 +sjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=+wSLHLtP3XOmjbOqZU1vNBCV9p/zW6ns/1xfBRqDeBc=; b=NOVMeqFt/aIOQGOPG6yPT3olEENRguegqtgdXMYSXwx5i1ISfF+mQqVx4LF5DiHCHz K72hooufryB0oLI+m34bWseb4O4zg47A3b0EGe5h85oyhPzb2P5x2VdPuVY5scDRWBfX wcPv+cD8gZNBg62byUpz17k0XX0EDoIdDPfc/AJxVEjTQKgbQOx9vTbT7aCFEdoHI9G6 kh7+G2QN0Nkhz22oJi06LZRzxjG33GKMgJyfM0SXzUuEUw0qhfVJkQYr85+rffz+ttTJ 1fyiD/5IwvnZmLWejnt/W63IQZHPj4010Ju7RnDxPhMWQT9Nj6btaIz6QEIVrOh764eK oapA==
X-Gm-Message-State: ALoCoQl1zK1cdWKQhNcWiBMUSi4DDXnmvn5K6HuCHRMdmhpdjsWrHkHuAAsQmWAwPfC7MkKNnHug
X-Received: by 10.50.43.226 with SMTP id z2mr13186579igl.65.1436797676138; Mon, 13 Jul 2015 07:27:56 -0700 (PDT)
MIME-Version: 1.0
References: <559FEBCC.3060604@tik.ee.ethz.ch>
In-Reply-To: <559FEBCC.3060604@tik.ee.ethz.ch>
From: Stefan Holmer <holmer@google.com>
Date: Mon, 13 Jul 2015 14:27:46 +0000
Message-ID: <CAEdus3+49dP4F_fzDp089w3+tsm0RJ_MM1n_r0L0Oa2ezBTycg@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  gaetano.carlucci@poliba.it, Luca De Cicco <l.decicco@poliba.it>,  Saverio Mascolo <mascolo@poliba.it>
Content-Type: multipart/alternative; boundary=047d7bfea0f419debf051ac2877c
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/0J3L4_VIoGUiDwTki_I_7Jjk1LA>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Brief review of draft-alvestrand-rmcat-congestion-03
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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 Jul 2015 14:28:01 -0000

--047d7bfea0f419debf051ac2877c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mirja,

Thanks a lot for this detailed review. I have added some comments inline,
but we will definitely take this input for the next revision.

/Stefan

On Fri, Jul 10, 2015 at 5:59 PM Mirja K=C3=BChlewind <
mirja.kuehlewind@tik.ee.ethz.ch> wrote:

> Hi Stefan, hi all,
>
> I've had a quick review of draft-alvestrand-rmcat-congestion-03 as an
> individual
> contributor (not as chairs). I have a couple of high level comments and a
> few
> more detail once.
>
> In general I, now after just reading NADA and Scream, found it slightly
> hard to
> read your draft because you are often use a different terminology and
> different
> variable names. Especially for the arrival model I wonder if you make
> things
> more complicated than they are. If I get you right, you effectively also
> just
> want to estimate the queuing delay which is your case however is denoted
> w(i).
> While the other approaches simply compare the sender and receiver
> timestamps
> (which requires synchronized clocks or at least additional mechanism to
> compensate for not-synchronized clocks), you look at the inter-arrival
> times at
> the sender and the receiver and basically estimate the difference between
> the
> sending rate and receiving rate and therefore... the queue... What I don'=
t
> really understand it why to you need to look at groups of packets?
>

Right, we are looking at queuing delay as well. The main difference is that
in GCC we are looking at queuing delay variations, while NADA and Scream
are both looking at estimated queuing delay. Our signal is therefore both
positive and negative, and can be expected to be zero mean if the queue is
"stable".

To some degree the groups of packets comes from that the algorithm was
initially designed to use RTP timestamps and look at inter-departure and
inter-arrival times of video frames. We generalized this by instead looking
at packets which were sent at roughly the same time (5 ms window).

In the same way we also group packets by arrival-time under the assumption
that packets received close together in time don't add much more value
about the delay variation. This is something we decided to do to better
handle burstiness that we have been observing on wireless networks, where
packets can be held up on the network for hundreds of milliseconds and then
be delivered back to back. The filter typically won't handle those big
spikes if we process one packet at a time, but if we wait a bit and process
a group of packets, we will see that we recover from the spike immediately
and that it wasn't caused by us sending too much.

I hope this makes it more clear. Do you think it would be good to discuss
this in more detail in the draft?


>
> Further you are using a Kalman filter. That's seem also complicated. Othe=
r
> schemes use much simpler filters (like the min of the last few values or =
a
> mean)
> and achieve acceptable estimates as well. I can only say this again:
> simplicity
> is also an important goal when designing a successful mechanism.
>

I agree that the model we currently are proposing can be simplified. Back
when this algorithm was based on video frames, there was a need to reduce
the effect of large frames causing delay spikes simply beacuse they were
large. Now that we are typically using pacing to limit this effect, there
isn't much to be gained from this complicated filter.

However, I do believe it can be useful to filter more aggressively if the
delay varies a lot (a lot of jitter), and less if it's a clean signal. For
instance by choosing alpha in avg_delay_variation =3D alpha*packet_delay +
(1-alpha)*avg_delay_variation.

I haven't tried a min filter, but from the top of my head I can't see why
it would have any obvious benefits?

Anyway, I agree it makes sense to look at how to simplify this.


>
> As just mention I'd really would like to see more meaningful variable
> names.
> That really helps the reader. Examples are:
> - gamma_1(i) -> effectively this your delay target, often called
> target_delay;
>

I guess it could be seen as a target, but in that case a delay variation
target. However, we are comparing both to positive gamma_1 and negative
gamma_1, which makes it a bit strange to see it as a target, in my opinion.
Our goal is really to be inside the range [-gamma_1, gamma_1]. Maybe
calling it threshold instead?


> don't think you need denote this as a function by writing (i) because it'=
s
> simply a variable in our implementation, right?
>

That's true. If that's the way drafts are typically written I wouldn't mind
changing style. :)


> - A_hat -> this reflects the target sending rate where the other rmcat
> proposal
> usually maintain a congestion window for, called cwnd. Btw. how do you
> maintain
> the send-out process?


Up to this point we haven't specified the send-out process, but we also
suggest using a pacer similarly to other drafts. It wasn't entirely clear
to me that this was supposed to be part of the proposals, but we can work
on getting that specified as well in a future revision.

Our algorithm computes a target rate for the encoder, and the pacer also
has the target rate as input.


> Is this ack-clocked/report-clocked? In this case it would
> make sense to maintain a window in bytes. Or is it timer-based where you
> calculate the next send-out time based on the rate? Anyway I'd rather lik=
e
> to
> see a longer more meaningful name like target-rate or output_rate (not
> sure you
> really need the _hat because effectively all your variables are _hat).
>

Sure, target_rate sounds like a good name to me.


> - R_hat(i) -> for window based schemes this information is kept as
> flight_size
> (number of bytes in flight)
>

That is the same thing only if your window based scheme is ack-clocked,
right? If not you may have increasingly more packets in flight without
knowing if packets are coming in at the other end. Anyway, I think we can
call this throughput or something?


>
> There is one sentence that really confuses me (detailed comment). In 4.4
> you say
> "On every update the delay-based estimate of the available bandwidth
>     is increased, either multiplicatively or additively, depending on its
>     current state."
> Here you mean A_hat(i), right? Because I would call this the target rate,
> while
> R_hat(i) would be an delay-based estimate...?
>

Yes, A_hat(i) is what we refer to. This will be a lot more clear if we do
the renaming we have been talking about above.


>
> A few more detailed questions regarding the calculation of R_hat(i). Is
> that
> done at receiver-side?


Depends on where the delay-based controller is implemented. If you have per
packet acks it can easily be implemented at the sender, which is what we
suggest. If you are using REMB instead it's better implemented at the
receiver. In the final version we will probably only have one recommended
way of implementing this.


> Why are you using a window between 0.5 and 1 sec?

Shouldn't that depend on the RTT and at best be one RTT?


Maybe. That would allow us to quickly decrease to the right bitrate if we
detect congestion. However, if there's a lot of jitter unrelated to
congestion, we may back down too far. Taking the average over a larger
interval may help avoid reducing the target_rate too much, at the expense
of sometimes not reducing enough. Do you agree?


> Can you maybe give
> pseudo code for basically the second paragraph on page 11?
>

Yes, that seems like a good thing to provide.


>
> In general I think it would helpful to not only provide mathematical
> formulas
> but also some pseudo code that is closer to the implementation (in a
> couple of
> cases).
>
> Next and final point is on number, there are a couple of numbers where it
> is not
> clear where they came from and why they have been chosen. I guess most of
> these
> numbers should be parameter that could be tested in different scenarios.
> These are:
> - update interval for R_hat(i): 0.5-1s (see above)
> - 8% increase factor -> really no idea with this has been chosen; actuall=
y
> seems
> rather low to me...
>

It has been fairly arbitrarily chosen, mostly to avoid being too aggressive
especially since we can get into the multiplicative increase mode at any
point in time (not only during initial ramp-up). We may want to consider
making this larger as we start to converge on the other pieces of the
algorithm.


> - 100ms add-on to RTT for the response time -> really don't understand wh=
y
> you
> don't simply take the RTT; however this should at least not be a fixed
> value
> from my point of view (but a factor...?)
>

I see it like this; the time it takes for the detector to find out if a
rate increase caused congestion, is the sum of the time it takes for the
sender to send at the new rate, the time it takes those packets to start
arriving at the receiver, the time it takes for the receiver to send
feedback back to the sender, and the time it takes for the sender to filter
the delay signal and detect the congestion.

In the current draft we split this into two components, RTT for the time it
takes for packets to go to the receiver and back and 100 ms for the time it
takes for the detector to filter/detect a change in delay variations and
for the codec to actually provide the requested bitrate.

Does that make sense?


> - maximum increase rate of 0.5 packets per response time (TCP RENO should
> actually increase by 1 packet/RTT which is now fixed in the Linux kernel,
> I think)
>

Right. We wanted to be a bit more cautious as we don't want to cause too
much jitter. This can also be tuned as we start to converge on other parts,
but how aggressive we can be here depends a bit on how the filter and
detection is tuned, and so on.


> - upper limit of 1.5*R_hat(i) for A_hat(i)...?
>

We have to allow our target_bitrate to be larger than what the encoder is
producing (or in this case what the current throughput is). The encoder may
produce too little, and this shouldn't have a substantial impact on the
performance. That's why we have this relaxation. At the same time, we don't
want the target_bitrate to become too much larger than what we are actually
sending, as we don't know if it would be possible to send that much safely.


> - alpha [0.8, 0.95] where 0.86 is recommended...??? Reno uses 0.5, Cubic
> should
> use 0.7. Where does this recommendation comes from?


It has been picked in a similar way as the additive increase and
multiplicative increase parameters. Basically manually tuned to get the
behavior we wanted.


> Btw. the decrease factor is
> usually called beta while the increase factor/rate is called alpha in
> AIMD/MIMD
> systems.
>

Good point.


> - And the number that worries me most is the loss level threshold for the
> loss-based controller... 2% and 10% ???? That's a lot! TFRC is not
> comparable in
> this case because you are only looking at the loss rate since the last
> report
> while TFRC looks at an average over a slightly longer time scale. With
> loss-based congestion control you have this probing behavior where there
> are no
> losses for a couple of RTTs (depending on the size of the congestion
> window/link
> speed) and then there are a couple of losses within one window. This
> should give
> you a relative low average loss rate (much belower than 10% and usually
> even
> below 1%) and the congestion control should reduce its sending rate
> immediately
> as soon as one loss is detected! If you now induce a loss rate of 2-10%
> this
> should starve all other competing flows! I'd say, for stability reasons
> you need
> to decrease as soon as there is loss detected. As you already apply this
> multiplicative decrease rule (A_hat(i) =3D alpha * R_hat(i) ) for delay, =
I
> really
> don't see why you are not using the same rule for loss...?


I agree about all of this, and that is why we mention this under Further
work. We want to combine the control of both delay and loss in a better
way, and make it a loss less tolerant to packet loss.


> I've quickly looked
> at your evaluation results and sees that GCC is able to co-exists with TC=
P.
> However I'd assume that in this case still only the delay-based controlle=
r
> controls the rate and the loss-based controller doesn't kick in at all.
> Can you
> confirm/check this?
>

I can confirm this, which is the main reason for reworking the loss-based
controller. Actually if we tune the K_u and K_d parameters a bit
differently, we can make the algorithm starve TCP flows, which of course
shouldn't be possible.


>
> Now looking at the results, I'd like to request three more things
> (Thanks!):
>

No problem, we'll get back to you with these plots. At the moment we're
working on getting all the evaluation test cases committed to our code
base. Once that is done this should be quickly done.


> - Can you run one more simulation with more than one TCP flow?

- What happen if the TCP stops after a while? Does the target delay value
> gamma
> actually go down again? Can you plot gamma as well in this sceanrio?
>

It does, we'll provide some plots.


> - And can you show the plots on slide 33 (multiple GCC flows) for more
> than 120s
> because the flows seem to de-converge again.
>

Right, that is not the case, but I can see how you may get that impression.
:)


>
> Thanks for all the work though!
>
> Mirja
>
>
>
>
>

--047d7bfea0f419debf051ac2877c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Mirja,<div><br></div><div>Thanks a lot for this detaile=
d review. I have added some comments inline, but we will definitely take th=
is input for the next revision.</div><div><br></div><div>/Stefan<br><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Jul 10, 2015 at 5:59 PM Mi=
rja K=C3=BChlewind &lt;<a href=3D"mailto:mirja.kuehlewind@tik.ee.ethz.ch">m=
irja.kuehlewind@tik.ee.ethz.ch</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Hi Stefan, hi all,<br>
<br>
I&#39;ve had a quick review of draft-alvestrand-rmcat-congestion-03 as an i=
ndividual<br>
contributor (not as chairs). I have a couple of high level comments and a f=
ew<br>
more detail once.<br>
<br>
In general I, now after just reading NADA and Scream, found it slightly har=
d to<br>
read your draft because you are often use a different terminology and diffe=
rent<br>
variable names. Especially for the arrival model I wonder if you make thing=
s<br>
more complicated than they are. If I get you right, you effectively also ju=
st<br>
want to estimate the queuing delay which is your case however is denoted w(=
i).<br>
While the other approaches simply compare the sender and receiver timestamp=
s<br>
(which requires synchronized clocks or at least additional mechanism to<br>
compensate for not-synchronized clocks), you look at the inter-arrival time=
s at<br>
the sender and the receiver and basically estimate the difference between t=
he<br>
sending rate and receiving rate and therefore... the queue... What I don&#3=
9;t<br>
really understand it why to you need to look at groups of packets?<br></blo=
ckquote><div><br></div><div>Right, we are looking at queuing delay as well.=
 The main difference is that in GCC we are looking at queuing delay variati=
ons, while NADA and Scream are both looking at estimated queuing delay. Our=
 signal is therefore both positive and negative, and can be expected to be =
zero mean if the queue is &quot;stable&quot;.</div><div><br></div><div>To s=
ome degree the groups of packets comes from that the algorithm was initiall=
y designed to use RTP timestamps and look at inter-departure and inter-arri=
val times of video frames. We generalized this by instead looking at packet=
s which were sent at roughly the same time (5 ms window).</div><div><br></d=
iv><div>In the same way we also group packets by arrival-time under the ass=
umption that packets received close together in time don&#39;t add much mor=
e value about the delay variation. This is something we decided to do to be=
tter handle burstiness that we have been observing on wireless networks, wh=
ere packets can be held up on the network for hundreds of milliseconds and =
then be delivered back to back. The filter typically won&#39;t handle those=
 big spikes if we process one packet at a time, but if we wait a bit and pr=
ocess a group of packets, we will see that we recover from the spike immedi=
ately and that it wasn&#39;t caused by us sending too much.</div><div><br><=
/div><div>I hope this makes it more clear. Do you think it would be good to=
 discuss this in more detail in the draft?</div><div>=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<br>
Further you are using a Kalman filter. That&#39;s seem also complicated. Ot=
her<br>
schemes use much simpler filters (like the min of the last few values or a =
mean)<br>
and achieve acceptable estimates as well. I can only say this again: simpli=
city<br>
is also an important goal when designing a successful mechanism.<br></block=
quote><div><br></div><div>I agree that the model we currently are proposing=
 can be simplified. Back when this algorithm was based on video frames, the=
re was a need to reduce the effect of large frames causing delay spikes sim=
ply beacuse they were large. Now that we are typically using pacing to limi=
t this effect, there isn&#39;t much to be gained from this complicated filt=
er.</div><div><br></div><div>However, I do believe it can be useful to filt=
er more aggressively if the delay varies a lot (a lot of jitter), and less =
if it&#39;s a clean signal. For instance by choosing alpha in avg_delay_var=
iation =3D alpha*packet_delay=C2=A0+ (1-alpha)*avg_delay_variation.</div><d=
iv><br></div><div>I haven&#39;t tried a min filter, but from the top of my =
head I can&#39;t see why it would have any obvious benefits?</div><div><br>=
</div><div>Anyway, I agree it makes sense to look at how to simplify this.<=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
As just mention I&#39;d really would like to see more meaningful variable n=
ames.<br>
That really helps the reader. Examples are:<br>
- gamma_1(i) -&gt; effectively this your delay target, often called target_=
delay;<br></blockquote><div><br></div><div>I guess it could be seen as a ta=
rget, but in that case a delay variation target. However, we are comparing =
both to positive gamma_1 and negative gamma_1, which makes it a bit strange=
 to see it as a target, in my opinion. Our goal is really to be inside the =
range [-gamma_1, gamma_1]. Maybe calling it threshold instead?</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
don&#39;t think you need denote this as a function by writing (i) because i=
t&#39;s<br>
simply a variable in our implementation, right?<br></blockquote><div><br></=
div><div>That&#39;s true. If that&#39;s the way drafts are typically writte=
n I wouldn&#39;t mind changing style. :)</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
- A_hat -&gt; this reflects the target sending rate where the other rmcat p=
roposal<br>
usually maintain a congestion window for, called cwnd. Btw. how do you main=
tain<br>
the send-out process?</blockquote><div><br></div><div>Up to this point we h=
aven&#39;t specified the send-out process, but we also suggest using a pace=
r similarly to other drafts. It wasn&#39;t entirely clear to me that this w=
as supposed to be part of the proposals, but we can work on getting that sp=
ecified as well in a future revision.</div><div><br></div><div>Our algorith=
m computes a target rate for the encoder, and the pacer also has the target=
 rate as input.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Is th=
is ack-clocked/report-clocked? In this case it would<br>
make sense to maintain a window in bytes. Or is it timer-based where you<br=
>
calculate the next send-out time based on the rate? Anyway I&#39;d rather l=
ike to<br>
see a longer more meaningful name like target-rate or output_rate (not sure=
 you<br>
really need the _hat because effectively all your variables are _hat).<br><=
/blockquote><div><br></div><div>Sure, target_rate sounds like a good name t=
o me.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- R_hat(i) -&gt; for window based schemes this information is kept as fligh=
t_size<br>
(number of bytes in flight)<br></blockquote><div><br></div><div>That is the=
 same thing only if your window based scheme is ack-clocked, right? If not =
you may have increasingly more packets in flight without knowing if packets=
 are coming in at the other end. Anyway, I think we can call this throughpu=
t or something?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There is one sentence that really confuses me (detailed comment). In 4.4 yo=
u say<br>
&quot;On every update the delay-based estimate of the available bandwidth<b=
r>
=C2=A0 =C2=A0 is increased, either multiplicatively or additively, dependin=
g on its<br>
=C2=A0 =C2=A0 current state.&quot;<br>
Here you mean A_hat(i), right? Because I would call this the target rate, w=
hile<br>
R_hat(i) would be an delay-based estimate...?<br></blockquote><div><br></di=
v><div>Yes, A_hat(i) is what we refer to. This will be a lot more clear if =
we do the renaming we have been talking about above.</div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
A few more detailed questions regarding the calculation of R_hat(i). Is tha=
t<br>
done at receiver-side?</blockquote><div><br></div><div>Depends on where the=
 delay-based controller is implemented. If you have per packet acks it can =
easily be implemented at the sender, which is what we suggest. If you are u=
sing REMB instead it&#39;s better implemented at the receiver. In the final=
 version we will probably only have one recommended way of implementing thi=
s.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why are you using a=
 window between 0.5 and 1 sec?</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Shouldn&#39;t that depend on the RTT and at best be one RTT?</blockquote><d=
iv><br></div><div>Maybe. That would allow us to quickly decrease to the rig=
ht bitrate if we detect congestion. However, if there&#39;s a lot of jitter=
 unrelated to congestion, we may back down too far. Taking the average over=
 a larger interval may help avoid reducing the target_rate too much, at the=
 expense of sometimes not reducing enough. Do you agree?</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"> Can you maybe give<br>
pseudo code for basically the second paragraph on page 11?<br></blockquote>=
<div><br></div><div>Yes, that seems like a good thing to provide.</div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
In general I think it would helpful to not only provide mathematical formul=
as<br>
but also some pseudo code that is closer to the implementation (in a couple=
 of<br>
cases).<br>
<br>
Next and final point is on number, there are a couple of numbers where it i=
s not<br>
clear where they came from and why they have been chosen. I guess most of t=
hese<br>
numbers should be parameter that could be tested in different scenarios. Th=
ese are:<br>
- update interval for R_hat(i): 0.5-1s (see above)<br>
- 8% increase factor -&gt; really no idea with this has been chosen; actual=
ly seems<br>
rather low to me...<br></blockquote><div><br></div><div>It has been fairly =
arbitrarily chosen, mostly to avoid being too aggressive especially since w=
e can get into the multiplicative increase mode at any point in time (not o=
nly during initial ramp-up). We may want to consider making this larger as =
we start to converge on the other pieces of the algorithm.</div><div>=C2=A0=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
- 100ms add-on to RTT for the response time -&gt; really don&#39;t understa=
nd why you<br>
don&#39;t simply take the RTT; however this should at least not be a fixed =
value<br>
from my point of view (but a factor...?)<br></blockquote><div><br></div><di=
v>I see it like this; the time it takes for the detector to find out if a r=
ate increase caused congestion, is the sum of the time it takes for the sen=
der to send at the new rate, the time it takes those packets to start arriv=
ing at the receiver, the time it takes for the receiver to send feedback ba=
ck to the sender, and the time it takes for the sender to filter the delay =
signal and detect the congestion.</div><div><br></div><div>In the current d=
raft we split this into two components, RTT for the time it takes for packe=
ts to go to the receiver and back and 100 ms for the time it takes for the =
detector to filter/detect a change in delay variations and for the codec to=
 actually provide the requested bitrate.</div><div><br></div><div>Does that=
 make sense?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- maximum increase rate of 0.5 packets per response time (TCP RENO should<b=
r>
actually increase by 1 packet/RTT which is now fixed in the Linux kernel, I=
 think)<br></blockquote><div><br></div><div>Right. We wanted to be a bit mo=
re cautious as we don&#39;t want to cause too much jitter. This can also be=
 tuned as we start to converge on other parts, but how aggressive we can be=
 here depends a bit on how the filter and detection is tuned, and so on.</d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- upper limit of 1.5*R_hat(i) for A_hat(i)...?<br></blockquote><div><br></d=
iv><div>We have to allow our target_bitrate to be larger than what the enco=
der is producing (or in this case what the current throughput is). The enco=
der may produce too little, and this shouldn&#39;t have a substantial impac=
t on the performance. That&#39;s why we have this relaxation. At the same t=
ime, we don&#39;t want the target_bitrate to become too much larger than wh=
at we are actually sending, as we don&#39;t know if it would be possible to=
 send that much safely.</div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
- alpha [0.8, 0.95] where 0.86 is recommended...??? Reno uses 0.5, Cubic sh=
ould<br>
use 0.7. Where does this recommendation comes from?</blockquote><div><br></=
div><div>It has been picked in a similar way as the additive increase and m=
ultiplicative increase parameters. Basically manually tuned to get the beha=
vior we wanted.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
 Btw. the decrease factor is<br>
usually called beta while the increase factor/rate is called alpha in AIMD/=
MIMD<br>
systems.<br></blockquote><div><br></div><div>Good point.</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
- And the number that worries me most is the loss level threshold for the<b=
r>
loss-based controller... 2% and 10% ???? That&#39;s a lot! TFRC is not comp=
arable in<br>
this case because you are only looking at the loss rate since the last repo=
rt<br>
while TFRC looks at an average over a slightly longer time scale. With<br>
loss-based congestion control you have this probing behavior where there ar=
e no<br>
losses for a couple of RTTs (depending on the size of the congestion window=
/link<br>
speed) and then there are a couple of losses within one window. This should=
 give<br>
you a relative low average loss rate (much belower than 10% and usually eve=
n<br>
below 1%) and the congestion control should reduce its sending rate immedia=
tely<br>
as soon as one loss is detected! If you now induce a loss rate of 2-10% thi=
s<br>
should starve all other competing flows! I&#39;d say, for stability reasons=
 you need<br>
to decrease as soon as there is loss detected. As you already apply this<br=
>
multiplicative decrease rule (A_hat(i) =3D alpha * R_hat(i) ) for delay, I =
really<br>
don&#39;t see why you are not using the same rule for loss...?</blockquote>=
<div><br></div><div>I agree about all of this, and that is why we mention t=
his under Further work. We want to combine the control of both delay and lo=
ss in a better way, and make it a loss less tolerant to packet loss.</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"> I&#39;ve quickly looked<br>
at your evaluation results and sees that GCC is able to co-exists with TCP.=
<br>
However I&#39;d assume that in this case still only the delay-based control=
ler<br>
controls the rate and the loss-based controller doesn&#39;t kick in at all.=
 Can you<br>
confirm/check this?<br></blockquote><div><br></div><div>I can confirm this,=
 which is the main reason for reworking the loss-based controller. Actually=
 if we tune the K_u and K_d parameters a bit differently, we can make the a=
lgorithm starve TCP flows, which of course shouldn&#39;t be possible.</div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Now looking at the results, I&#39;d like to request three more things (Than=
ks!):<br></blockquote><div><br></div><div>No problem, we&#39;ll get back to=
 you with these plots. At the moment we&#39;re working on getting all the e=
valuation test cases committed to our code base. Once that is done this sho=
uld be quickly done.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
- Can you run one more simulation with more than one TCP flow?</blockquote>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
- What happen if the TCP stops after a while? Does the target delay value g=
amma<br>
actually go down again? Can you plot gamma as well in this sceanrio?<br></b=
lockquote><div><br></div><div>It does, we&#39;ll provide some plots.</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
- And can you show the plots on slide 33 (multiple GCC flows) for more than=
 120s<br>
because the flows seem to de-converge again.<br></blockquote><div><br></div=
><div>Right, that is not the case, but I can see how you may get that impre=
ssion. :)</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks for all the work though!<br>
<br>
Mirja<br>
<br>
<br>
<br>
<br>
</blockquote></div></div></div>

--047d7bfea0f419debf051ac2877c--


From nobody Mon Jul 13 13:19:13 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387501A887A for <rmcat@ietfa.amsl.com>; Mon, 13 Jul 2015 13:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qWUMR4LS-tpz for <rmcat@ietfa.amsl.com>; Mon, 13 Jul 2015 13:19:08 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6D91A886B for <rmcat@ietf.org>; Mon, 13 Jul 2015 13:19:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 748FED9304; Mon, 13 Jul 2015 22:19:06 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 92HKTvVioUnr; Mon, 13 Jul 2015 22:19:06 +0200 (MEST)
Received: from [192.168.178.33] (x4d02d263.dyn.telefonica.de [77.2.210.99]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 715D6D9303; Mon, 13 Jul 2015 22:19:05 +0200 (MEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <CAEdus3+49dP4F_fzDp089w3+tsm0RJ_MM1n_r0L0Oa2ezBTycg@mail.gmail.com>
Date: Mon, 13 Jul 2015 22:19:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B0524F2-98F1-42DA-BCFB-583C03FD2B8D@tik.ee.ethz.ch>
References: <559FEBCC.3060604@tik.ee.ethz.ch> <CAEdus3+49dP4F_fzDp089w3+tsm0RJ_MM1n_r0L0Oa2ezBTycg@mail.gmail.com>
To: Stefan Holmer <holmer@google.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/sj2ctvO-AIpAsYAWvad3RtyV0po>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, Saverio Mascolo <mascolo@poliba.it>, Luca De Cicco <l.decicco@poliba.it>, gaetano.carlucci@poliba.it
Subject: Re: [rmcat] Brief review of draft-alvestrand-rmcat-congestion-03
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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 Jul 2015 20:19:12 -0000

Hi Stefan,

see some comments/answer below. (Don=E2=80=99t know why my mail program =
was not able distinguish my original mail from you reply anymore but I =
hope that=E2=80=99s still readable).

Mirja

>=20
> In general I, now after just reading NADA and Scream, found it =
slightly hard to
> read your draft because you are often use a different terminology and =
different
> variable names. Especially for the arrival model I wonder if you make =
things
> more complicated than they are. If I get you right, you effectively =
also just
> want to estimate the queuing delay which is your case however is =
denoted w(i).
> While the other approaches simply compare the sender and receiver =
timestamps
> (which requires synchronized clocks or at least additional mechanism =
to
> compensate for not-synchronized clocks), you look at the inter-arrival =
times at
> the sender and the receiver and basically estimate the difference =
between the
> sending rate and receiving rate and therefore... the queue... What I =
don't
> really understand it why to you need to look at groups of packets?
>=20
> Right, we are looking at queuing delay as well. The main difference is =
that in GCC we are looking at queuing delay variations, while NADA and =
Scream are both looking at estimated queuing delay. Our signal is =
therefore both positive and negative, and can be expected to be zero =
mean if the queue is "stable=E2=80=9C.

Just FYI, Scream is looking to some extend at the, in this case called, =
trend of the queuing delay as well, see section 4.1.2.1. which can also =
be positive or negative. Would really be nice to better understand =
similarities and differences between the proposals.

>=20
> To some degree the groups of packets comes from that the algorithm was =
initially designed to use RTP timestamps and look at inter-departure and =
inter-arrival times of video frames. We generalized this by instead =
looking at packets which were sent at roughly the same time (5 ms =
window).
>=20
> In the same way we also group packets by arrival-time under the =
assumption that packets received close together in time don't add much =
more value about the delay variation. This is something we decided to do =
to better handle burstiness that we have been observing on wireless =
networks, where packets can be held up on the network for hundreds of =
milliseconds and then be delivered back to back. The filter typically =
won't handle those big spikes if we process one packet at a time, but if =
we wait a bit and process a group of packets, we will see that we =
recover from the spike immediately and that it wasn't caused by us =
sending too much.
>=20
> I hope this makes it more clear. Do you think it would be good to =
discuss this in more detail in the draft?

Yes, some more discussion would definitely be useful here. Especially =
making it more clear that this is an optimization for wireless networks =
would actually help. Maybe, at least for presentation purposes, you =
could also try to describe a basic algorithm which is as simple as =
possible to still work well and e.g. describe this part as an (optional) =
add-on=E2=80=A6 not sure that makes sense=E2=80=A6

> =20
>=20
> Further you are using a Kalman filter. That's seem also complicated. =
Other
> schemes use much simpler filters (like the min of the last few values =
or a mean)
> and achieve acceptable estimates as well. I can only say this again: =
simplicity
> is also an important goal when designing a successful mechanism.
>=20
> I agree that the model we currently are proposing can be simplified. =
Back when this algorithm was based on video frames, there was a need to =
reduce the effect of large frames causing delay spikes simply beacuse =
they were large. Now that we are typically using pacing to limit this =
effect, there isn't much to be gained from this complicated filter.
>=20
> However, I do believe it can be useful to filter more aggressively if =
the delay varies a lot (a lot of jitter), and less if it's a clean =
signal. For instance by choosing alpha in avg_delay_variation =3D =
alpha*packet_delay + (1-alpha)*avg_delay_variation.
>=20
> I haven't tried a min filter, but from the top of my head I can't see =
why it would have any obvious benefits?

The only benefit would be simplicity. Maybe take the same approach here =
than just proposed above. Just say in the =E2=80=9Abase algorithm=E2=80=98=
 that there needs to be a filter and then discuss later in an own =
section that you propose a Kalman filter. Just a thought...

>=20
> Anyway, I agree it makes sense to look at how to simplify this.
> =20
>=20
> As just mention I'd really would like to see more meaningful variable =
names.
> That really helps the reader. Examples are:
> - gamma_1(i) -> effectively this your delay target, often called =
target_delay;
>=20
> I guess it could be seen as a target, but in that case a delay =
variation target. However, we are comparing both to positive gamma_1 and =
negative gamma_1, which makes it a bit strange to see it as a target, in =
my opinion. Our goal is really to be inside the range [-gamma_1, =
gamma_1]. Maybe calling it threshold instead?

yes, maybe call it delay_var_thres =E2=80=A6?

> =20
> don't think you need denote this as a function by writing (i) because =
it's
> simply a variable in our implementation, right?
>=20
> That's true. If that's the way drafts are typically written I wouldn't =
mind changing style. :)
> =20
> - A_hat -> this reflects the target sending rate where the other rmcat =
proposal
> usually maintain a congestion window for, called cwnd. Btw. how do you =
maintain
> the send-out process?
>=20
> Up to this point we haven't specified the send-out process, but we =
also suggest using a pacer similarly to other drafts. It wasn't entirely =
clear to me that this was supposed to be part of the proposals, but we =
can work on getting that specified as well in a future revision
>=20
> Our algorithm computes a target rate for the encoder, and the pacer =
also has the target rate as input.

actually the pacing is e.g. in scream in the appendix. However, the =
interface to the video coder should probably be part of the draft (for =
now). The other schemes basically have a different rate as input for the =
encoder than the actual sending rate. If that=E2=80=99s the same in your =
case, I guess that=E2=80=99s okay as well.

> =20
> Is this ack-clocked/report-clocked? In this case it would
> make sense to maintain a window in bytes. Or is it timer-based where =
you
> calculate the next send-out time based on the rate? Anyway I'd rather =
like to
> see a longer more meaningful name like target-rate or output_rate (not =
sure you
> really need the _hat because effectively all your variables are _hat).
>=20
> Sure, target_rate sounds like a good name to me.
> =20
> - R_hat(i) -> for window based schemes this information is kept as =
flight_size
> (number of bytes in flight)
>=20
> That is the same thing only if your window based scheme is =
ack-clocked, right? If not you may have increasingly more packets in =
flight without knowing if packets are coming in at the other end. =
Anyway, I think we can call this throughput or something?

No, only difference is flight size is a value in bytes while you are =
looking at a rate. The difference between packets in flight and actual =
packet as the receiver is e.g. called pipe_ack in =
draft-ietf-tcpm-newcwv.

> =20
>=20
> There is one sentence that really confuses me (detailed comment). In =
4.4 you say
> "On every update the delay-based estimate of the available bandwidth
>     is increased, either multiplicatively or additively, depending on =
its
>     current state."
> Here you mean A_hat(i), right? Because I would call this the target =
rate, while
> R_hat(i) would be an delay-based estimate...?
>=20
> Yes, A_hat(i) is what we refer to. This will be a lot more clear if we =
do the renaming we have been talking about above.
> =20
>=20
> A few more detailed questions regarding the calculation of R_hat(i). =
Is that
> done at receiver-side?
>=20
> Depends on where the delay-based controller is implemented. If you =
have per packet acks it can easily be implemented at the sender, which =
is what we suggest. If you are using REMB instead it's better =
implemented at the receiver. In the final version we will probably only =
have one recommended way of implementing this.
> =20
> Why are you using a window between 0.5 and 1 sec?
> Shouldn't that depend on the RTT and at best be one RTT?
>=20
> Maybe. That would allow us to quickly decrease to the right bitrate if =
we detect congestion. However, if there's a lot of jitter unrelated to =
congestion, we may back down too far. Taking the average over a larger =
interval may help avoid reducing the target_rate too much, at the =
expense of sometimes not reducing enough. Do you agree?

Okay. Not sure I agree but that=E2=80=99s maybe something to test. In =
any case this should not be a fixed value but something like 3*RTT.

> =20
> Can you maybe give
> pseudo code for basically the second paragraph on page 11?
>=20
> Yes, that seems like a good thing to provide.
> =20
>=20
> In general I think it would helpful to not only provide mathematical =
formulas
> but also some pseudo code that is closer to the implementation (in a =
couple of
> cases).
>=20
> Next and final point is on number, there are a couple of numbers where =
it is not
> clear where they came from and why they have been chosen. I guess most =
of these
> numbers should be parameter that could be tested in different =
scenarios. These are:
> - update interval for R_hat(i): 0.5-1s (see above)
> - 8% increase factor -> really no idea with this has been chosen; =
actually seems
> rather low to me...
>=20
> It has been fairly arbitrarily chosen, mostly to avoid being too =
aggressive especially since we can get into the multiplicative increase =
mode at any point in time (not only during initial ramp-up). We may want =
to consider making this larger as we start to converge on the other =
pieces of the algorithm.

Probably also worth some experimentation.

> =20
> - 100ms add-on to RTT for the response time -> really don't understand =
why you
> don't simply take the RTT; however this should at least not be a fixed =
value
> from my point of view (but a factor...?)
>=20
> I see it like this; the time it takes for the detector to find out if =
a rate increase caused congestion, is the sum of the time it takes for =
the sender to send at the new rate, the time it takes those packets to =
start arriving at the receiver, the time it takes for the receiver to =
send feedback back to the sender, and the time it takes for the sender =
to filter the delay signal and detect the congestion.
>=20
> In the current draft we split this into two components, RTT for the =
time it takes for packets to go to the receiver and back and 100 ms for =
the time it takes for the detector to filter/detect a change in delay =
variations and for the codec to actually provide the requested bitrate.
>=20
> Does that make sense?

Ah okay. That makes more sense.

> =20
> - maximum increase rate of 0.5 packets per response time (TCP RENO =
should
> actually increase by 1 packet/RTT which is now fixed in the Linux =
kernel, I think)
>=20
> Right. We wanted to be a bit more cautious as we don't want to cause =
too much jitter. This can also be tuned as we start to converge on other =
parts, but how aggressive we can be here depends a bit on how the filter =
and detection is tuned, and so on.

Maybe worth trying also a maximum increase rate of 1 packet per RTT.

> =20
> - upper limit of 1.5*R_hat(i) for A_hat(i)...?
>=20
> We have to allow our target_bitrate to be larger than what the encoder =
is producing (or in this case what the current throughput is). The =
encoder may produce too little, and this shouldn't have a substantial =
impact on the performance. That's why we have this relaxation. At the =
same time, we don't want the target_bitrate to become too much larger =
than what we are actually sending, as we don't know if it would be =
possible to send that much safely.

I understand why you have a limit, the question was only why is the =
limit 1.5*R. But I guess that the one value/parameter that seems to make =
most sense to me and doesn=E2=80=99t need to much further explanation.

> =20
> - alpha [0.8, 0.95] where 0.86 is recommended...??? Reno uses 0.5, =
Cubic should
> use 0.7. Where does this recommendation comes from?
>=20
> It has been picked in a similar way as the additive increase and =
multiplicative increase parameters. Basically manually tuned to get the =
behavior we wanted.=20

Okay. So probably also depends strongly on the other parameters, e.g. if =
you use a higher maximum increase rate, you might also use a stronger =
decrease=E2=80=A6 maybe put slightly more explanation in the draft.

> =20
> Btw. the decrease factor is
> usually called beta while the increase factor/rate is called alpha in =
AIMD/MIMD
> systems.
>=20
> Good point.
> =20
> - And the number that worries me most is the loss level threshold for =
the
> loss-based controller... 2% and 10% ???? That's a lot! TFRC is not =
comparable in
> this case because you are only looking at the loss rate since the last =
report
> while TFRC looks at an average over a slightly longer time scale. With
> loss-based congestion control you have this probing behavior where =
there are no
> losses for a couple of RTTs (depending on the size of the congestion =
window/link
> speed) and then there are a couple of losses within one window. This =
should give
> you a relative low average loss rate (much belower than 10% and =
usually even
> below 1%) and the congestion control should reduce its sending rate =
immediately
> as soon as one loss is detected! If you now induce a loss rate of =
2-10% this
> should starve all other competing flows! I'd say, for stability =
reasons you need
> to decrease as soon as there is loss detected. As you already apply =
this
> multiplicative decrease rule (A_hat(i) =3D alpha * R_hat(i) ) for =
delay, I really
> don't see why you are not using the same rule for loss...?
>=20
> I agree about all of this, and that is why we mention this under =
Further work. We want to combine the control of both delay and loss in a =
better way, and make it a loss less tolerant to packet loss.

Good!

> =20
> I've quickly looked
> at your evaluation results and sees that GCC is able to co-exists with =
TCP.
> However I'd assume that in this case still only the delay-based =
controller
> controls the rate and the loss-based controller doesn't kick in at =
all. Can you
> confirm/check this?
>=20
> I can confirm this, which is the main reason for reworking the =
loss-based controller. Actually if we tune the K_u and K_d parameters a =
bit differently, we can make the algorithm starve TCP flows, which of =
course shouldn't be possible.
> =20
>=20
> Now looking at the results, I'd like to request three more things =
(Thanks!):
>=20
> No problem, we'll get back to you with these plots. At the moment =
we're working on getting all the evaluation test cases committed to our =
code base. Once that is done this should be quickly done.
> =20
> - Can you run one more simulation with more than one TCP flow?
> - What happen if the TCP stops after a while? Does the target delay =
value gamma
> actually go down again? Can you plot gamma as well in this sceanrio?
>=20
> It does, we'll provide some plots.
> =20
> - And can you show the plots on slide 33 (multiple GCC flows) for more =
than 120s
> because the flows seem to de-converge again.
>=20
> Right, that is not the case, but I can see how you may get that =
impression. :)

Great! See you at the interim!


> =20
>=20
> Thanks for all the work though!
>=20
> Mirja
>=20
>=20
>=20
>=20


From nobody Tue Jul 14 00:24:55 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1DD1A8F33 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 00:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.901
X-Spam-Level: 
X-Spam-Status: No, score=-5.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 kh8-SShSfdAd for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 00:24:49 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0382F1A8BC5 for <rmcat@ietf.org>; Tue, 14 Jul 2015 00:24:47 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-c2-55a4b93d227d
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 43.03.12828.D39B4A55; Tue, 14 Jul 2015 09:24:46 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.120]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0210.002; Tue, 14 Jul 2015 09:24:45 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
Thread-Topic: Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow
Date: Tue, 14 Jul 2015 07:24:45 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch>
In-Reply-To: <559FB533.5090105@tik.ee.ethz.ch>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+Jvja7dziWhBnfP8Vgcap3JYrFh9RQW i9U3P7A5MHssWfKTyePQ8yCPYx++sgUwR3HZpKTmZJalFunbJXBltC5YwFzw5zJjxYelXA2M R84xdjFyckgImEh8fj+PHcIWk7hwbz1bFyMXh5DAUUaJ44vnsEM4Sxglbi2fygJSxSZgI7Hy 0Hegbg4OEQEvic+fAkFqmAVOMUqs797NAhIXBpr68bkgSLmIgKnE19OdLBC2kcT3u7eZQGwW AVWJudMvgB3BK+ArcaP7OFhcSEBX4mnzJVYQm1NAT+LU9elgNYwCshL3v98Dm8MsIC5x68l8 JoijBSSW7DnPDGGLSrx8/I8VwlaSaFzyhBXkHGYBTYn1u/QhWhUlpnQ/ZIdYKyhxcuYTlgmM YrOQTJ2F0DELSccsJB0LGFlWMYoWpxYX56YbGeulFmUmFxfn5+nlpZZsYgTG08Etv3V3MK5+ 7XiIUYCDUYmHVyF3SagQa2JZcWXuIUZpDhYlcd4Zm/NChQTSE0tSs1NTC1KL4otKc1KLDzEy cXBKNTCa2Dwz1LzfYbo6vk9VJfTYfObC1bMFKtt32b99G+g+XS+IZ4f/wykqJm7XFthuT7jl pSsouzThCd8krn19zvFGNUdK5X66PTyp9ljBzmSiT6CMxoR3de9LYg5UMRx6YHPykN31euu/ vcVvxeJtj/BMNnq3JeXQC6cE37K/q/5EZfJ3eEts9lZiKc5INNRiLipOBADTqnq3iAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/MvYQop3uEiEaIjSyxryoZ1obEdg>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 07:24:53 -0000

SGkgTWlyamEgYW5kIHRoYW5rcyBmb3IgeW91ciBjb21tZW50cywgYW5zd2VycyBpbmxpbmUgbWFy
a2VkIHdpdGggW0lKXQ0KDQpSZWdhcmRzDQovSW5nZW1hcg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IE1pcmphIEvDvGhsZXdpbmQgW21haWx0bzptaXJqYS5rdWVobGV3
aW5kQHRpay5lZS5ldGh6LmNoXQ0KPiBTZW50OiBkZW4gMTAganVsaSAyMDE1IDE0OjA2DQo+IFRv
OiBaYWhlZHV6emFtYW4gU2Fya2VyOyBJbmdlbWFyIEpvaGFuc3NvbiBTDQo+IENjOiBLYXJlbiBF
LiBFLiBOaWVsc2VuOyBybWNhdEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZXZpZXcgb2YgZHJhZnQt
aWV0Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gDQo+IEhpIFphaGVkLCBoaSBJbmdlbWFyLA0KPiAN
Cj4gcGxlYXNlIGZpbmQgbXkgcmV2aWV3IGFzIGFuIGluZGl2aWR1YWwgY29udHJpYnV0b3IgYmVs
b3cuDQo+IA0KPiBGaXJzdCBvZiBhbGwgSSBoYXZlIGEgZmV3IGdlbmVyYWwgcXVlc3Rpb24gb24g
dGhlIGFsZ29yaXRobShzKToNCj4gDQo+IDEpIFdoZW4gY2FsY3VsYXRpbmcgY3duZCB5b3Ugb24g
dGhlIG9uZSBoYW5kIGNhbGN1bGF0ZSBzY2xfaSB0byBiYXNpY2FsbHkNCj4gcXVpY2tseSBzcGVl
ZCB1cCB0byB0aGUgcHJldmlvdXMgbWF4aW11bSB2YWx1ZSBjd25kX2kgYW5kIG9uIHRoZSBvdGhl
cg0KPiBoYW5kIHRyeSB0byBtYWludGFpbiBhIGxvdyBkZWxheSB0YXJnZXQuIEFyZW4ndCB0aGVz
ZSB0d28gY29uZmxpY3RpbmcgZ29hbHM/DQo+IFdpdGhvdXQgaGF2aW5nIGxvb2tlZCBhdCB5b3Vy
IGV4cGVyaW1lbnRhdGlvbiByZXN1bHRzIG5vdywgSSdkIGV4cGVjdCB0aGF0DQo+IHlvdSBldmVu
IHdoZW4geW91IGFyZSBhbG9uZSBvbiB0aGUgbGluayBpbmR1Y2UgbW9yZSB0aGFuIG93ZF90YXJn
ZXQgZGVsYXkNCj4gKGFjdHVhbGx5IGRlcGVuZGluZyBvbiB0aGUgbWF4aW11bSBidWZmZXIgc2l6
ZSBhcyByZWZsZWN0ZWQgYnkgY3duZF9pKSwgYW5kDQo+IHdoZW4gY29tcGV0aW5nIHdpdGggb3Ro
ZXIgdHJhZmZpYywgeW91J2Qgc3RpbGwgY2Fubm90IHJlYWNoIGFuIGVxdWFsIHNoYXJpbmcNCj4g
YnV0IHdpbGwgYWx3YXlzIGdldCBhIGxvd2VyIHNoYXJlLiBXaGljaCBpcyBwcm9iYWJseSBva2F5
OyBob3dldmVyIHRoZSBwYXJ0DQo+IHRoYXQgbWF5YmUgd29ycmllcyBteSBhIGxpdHRsZSBpcyB0
aGF0IHRoZSBhY2hpZXZlZCBkZWxheSBhbmQvb3IgYWNoaWV2ZWQNCj4gc2hhcmluZyBwcm9iYWJs
eSBkZXBlbmRzIG9uIHRoZSBjb25maWd1cmVkIG1heGltdW0gYnVmZmVyIHNpemUgKHdoaWNoDQo+
IG1pZ2h0IGJlIGxhcmdlKS4uLj8gQ2FuIHlvdSBjb21tZW50IG9uIHRoaXMgb3IgcHJvdmlkZSBt
b3JlIGRldGFpbCByZXN1bHRzDQo+IG9uIHRoaXM/DQpbSUpdIEFjdHVhbGx5IHRoZSBwdXJwb3Nl
IG9mIGN3bmRfaSBhbmQgc2NsX2kgaXMgdG8gc2xvdyBkb3duIHRoZSBpbmNyZWFzZSBvbiBjd25k
IGFuZCB0YXJnZXQgYml0cmF0ZSB3aGVuIGNsb3NlIHRvIHRoZSBsYXN0IGtub3duIG1heCB2YWx1
ZS4gVGhpcyBnaXZlcyBhIGNoYW5jZSBmb3IgdGhlIGFsZ29yaXRobSB0byBhdm9pZCBhIHRvbyBs
YXJnZSBkZWxheSBzcGlrZSB3aGVuIHRoZSBwYXRoIGNhcGFjaXR5IG9mIGEgZml4ZWQgQlcgbGlu
ayBpcyByZWFjaGVkLCBhdCB0aGUgc2FtZSB0aW1lIGl0IGdpdmVzIGEgYmV0dGVyIG9wcG9ydHVu
aXR5IHRvIGdyYWIgZnJlZSBiYW5kd2lkdGggcmVhc29uYWJseSBmYXN0Lg0KSXQgbWF5IGJlIGFu
IG9wdGlvbiB0byBiYXNlIHRoZSB2aWRlbyB0YXJnZXQgcmF0ZSBvbiBzb21ldGhpbmcgbGlrZSB0
aGUgc2VuZCB3aW5kb3csIG5vdCBzdXJlIHdoYXQgaXQgd291bGQgbGlrZSwgeW91IHByb2JhYmx5
IG5lZWQgdG8gZG8gc29tZXRoaW5nIGxpa2UgY3duZC9ydHQuIExpa2UgaXQgaXMgbm93IHRoZXJl
IGFyZSBhY3R1YWxseSB0d28gY29udHJvbCBsb29wcyBhcyB5b3UgY29ycmVjdGx5IG9ic2VydmUu
IEN1cnJlbnRseSBJIGRvbid0IHNlZSBhIHdheSBhcm91bmQgdGhpcyBhcyB0aGUgdmlkZW8gY29k
ZXIgY2FuIGZsdWN0dWF0ZSBxdWl0ZSBhIGxvdCBhcm91bmQgdGhlIHRhcmdldCBiaXRyYXRlLiBJ
biB0aGUgbG9uZyBydW4gaXQgaXMgcGVyaGFwcyBwb3NzaWJsZSAoYW5kIGRlc2lyYWJsZSkgdG8g
bWFrZSBpdCBvbmUgY29udHJvbCBsb29wLCBub3Qgc3VyZSB0aGF0IGl0IHdpbGwgaGFwcGVucy4g
QW5vdGhlciB0aGluZyB0aGF0IHNwZWFrcyBpbiBmYXZvciBvZiB0d28gY29udHJvbCBsb29wcyBp
cyB0aGF0IFNDUmVBTSBjYW4gY29uZ2VzdGlvbiBjb250cm9sIG11bHRpcGxlIHN0cmVhbXMsIGZv
ciBpbnN0YW5jZSB2aWRlbyBhbmQgYXVkaW8uIFRoaXMgY2FuIGJlIGV4cGVyaW1lbnRlZCB3aXRo
IGluIHRoZSBDKysgY29kZS4NCj4gDQo+IDIpIEkgd291bGQgaGF2ZSBleHBlY3RlZCB0aGF0IHRo
ZSB2aWRlbyByYXRlIGNvbnRyb2xsZXIgdGFrZXMgY3duZCBvciB0aGUNCj4gYWN0dWFsIHNlbmRp
bmcgd2luZG93IGFzIGFuIGlucHV0IHBhcmFtZXRlci4gSG93ZXZlciwgeW91ciBhcHByb2FjaA0K
PiBzZWVtcyB0byBoYXZlIHR3byBtb3JlIG9yIGxlc3MgaW5kZXBlbmRlbnQgY29udHJvbCBsb29w
cyBmb3IgdGhlIHNlbmRpbmcNCj4gcmF0ZSBhbmQgdGhlIGNvZGluZyByYXRlLg0KPiBUaGF0IHNl
ZW1zIHF1aXRlIHdlaXJkIHRvIG1lIChob3dldmVyIHRoZSByZWFzb25pbmcgYmVoaW5kIHRoZSBk
ZXNpZ24gb2YNCj4gdGhlIHZpZGVvIGNvZGVyIGlzIGFsc28gbm90IHJlYWxseSBjbGVhciB0byBt
ZTsgc2VlIGJlbG93IGZvciBmdXJ0aGVyDQo+IGNvbW1lbnRzIG9uIHRoaXMpLiBJJ2QgYmUgd29y
cmllZCB0aGF0IGlmIHRob3NlIHR3byBsb29wcyBhcmUgcmF0aGVyDQo+IGluZGVwZW5kZW50IHRo
YXQgdGhleSBjb3VsZCBhY3R1YWxseSBtYWtlIGNvbmZsaWN0aW5nIGRlY2lzaW9uLCBlLmcuIHZp
ZGVvDQo+IGNvbnRyb2xsZXIgaW5jcmVhc2VzIHRoZSByYXRlIGFuZCBjb25nZXN0aW9uIGNvbnRy
b2xsZXIgZGVjcmVhc2VzIHRoZSByYXRlLg0KPiBBbHNvIHdvdWxkbid0IGl0IGJlIHVzZWZ1bCB0
byB1c2UgdGhlIGN3bmQgYXMgYW4gaW5wdXQgcGFyYW1ldGVyPyBQbGVhc2UNCj4gY29tbWVudCEN
Cj4gDQo+IA0KPiBBbmQgdHdvIG1vcmUgaGlnaC1sZXZlbC9nZW5lcmFsIGNvbW1lbnRzIG9uICh0
aGUgc3RydWN0dXJlIG9mKSB0aGUNCj4gZG9jdW1lbnQ6DQo+IA0KPiAxKSBJIHRoaW5rIHRoZSBh
bGdvcml0aG0gaXMgbm93IHdlbGwgdW5kZXJzdGFuZGFibGUgd2l0aCB0aGUgY29kZSBhbmQNCj4g
cmVzcGVjdGl2ZSBleHBsYW5hdGlvbiAoZXhwZWN0IHRoZSBlbmQgb2Ygc2VjdGlvbiA0LjEuMyBu
ZWVkcyBtb3JlDQo+IGV4cGxhbmF0aW9uIGFzIGp1c3QgbWVudGlvbmVkIGFib3ZlKS4gSSB3b3Vs
ZCBzdGlsbCBsaWtlIHRvIHByb3Bvc2Ugc29tZQ0KPiByZXN0cnVjdHVyaW5nLiBJIHRoaW5rIHRo
ZSByZWFkYWJpbGl0eSBjYW4gYmUgbXVjaCBpbXByb3ZlZCBieSBzb21lIHJhdGhlcg0KPiBzaW1w
bGUgcmVzdHJ1Y3R1cmluZyB1c2luZyBhIG1vZGVsIHNpbWlsYXIgYXMgaW4gdGhlIExFREJBVCBk
cmFmdDogRmlyc3QgZ2l2ZSBhDQo+IGhpZ2ggbGV2ZWwgc3VtbWFyaXplIG9mIGFsbCBzdGVwcyB0
aGF0IGhhdmUgdG8gYmUgcGVyZm9ybWVkICgiRm9yIGVhY2gNCj4gQUNLL3JlcG9ydCB0aGUgc3Rh
dGUgb24gdGhlIGRlbGF5IGFuZCBkZWxheSB0cmVuZCB3aWxsIGJlIHVwZGF0ZWQuIElmIGEgbG9z
cyBpcw0KPiBkZXRlY3RlZCB0aGUgY29uZ2VzdGlvbiB3aW5kb3cgY3duZCB3aWxsIGJlIGRlY3Jl
YXNlZCBzdHJvbmdseSwgb3RoZXJ3aXNlDQo+IHRoZXJlIGFyZSB0d28gb3BlcmF0aW9uIG1vZGU6
IGZhc3QgaW5jcmVhc2UgYW5kIHJlZ3VsYXIgb3BlcmF0aW9uLiBJbiBmYXN0DQo+IGluY3JlYXNl
IHRoZSBnb2FsIGlzIHRvIHJlYWNoIGEgcHJldmlvdXMgdGFyZ2V0IHZhbHVlIHF1aWNrbHkgYXBw
bHlpbmcgYW4NCj4gbXVsdGlwbGljYXRpdmUgaW5jcmVhc2Ugc2NoZW1lLCB3aGlsZSBvdGhlcndp
c2UgYSBkZWxheSB0cmFnZXQgc2hvdWxkIGJlDQo+IG1haW50YWluZWQuLi4iKS4gVGhlbiBnaXZl
IGFsbCB0aGUgcHNldWRvIGNvZGUgc3RydWN0dXJlZCBpbnRvIGZ1bmN0aW9ucyBhbmQNCj4gZmlu
YWxseSBleHBsYWluIGVhY2ggZnVuY3Rpb24gYmxvY2sgaW4gZGV0YWlsIGluIGFuIG93biBwYXJh
Z3JhcGguIEkgYWxyZWFkeQ0KPiBoYXZlIGEgZ29vZCBpZGVhIGhvdyB0aGlzIHdvdWxkIGxvb2sg
bGlrZSBhbmQgaWYgeW91IHdhbnQgdG8gd2UgY2FuIHNpdCBkb3duDQo+IGF0IHRoZSBtZWV0aW5n
IGFuZCBkbyB0aGlzIHRvZ2V0aGVyLg0KW0lKXSBJJ2QgbGlrZSB0byBoYXZlIHNvbWUga2luZCBv
ZiBzaXQgdG9nZXRoZXIsIHVuZm9ydHVuYXRlbHkgSSBjYW5ub3QgYXR0ZW5kIHRoZSBJRVRGIHRo
aXMgdGltZSwgcGVyaGFwcyBzb21lIHJlbW90ZSBhcHBlYXIuaW4gc2Vzc2lvbiBvciB0aGUgbGlr
ZSBjYW4gYmUgYXJyYW5nZWQgaW4gQXVndXN0Lg0KDQo+IA0KPiAyKSBIYXZpbmcgcmV2aWV3ZWQg
TkFEQSBhbmQgU2NyZWFtIG5vdyBiYXNpY2FsbHkgaW4gb25lIGdvLCBJIHRoaW5rIHRoZQ0KPiB1
c2VkIGZyYW1ld29yayBpcyB2ZXJ5IHNpbWlsYXIuIElmIHlvdSBsb29rIGF0IHlvdXIgRmlndXJl
IDEgYW5kIHRoZSBGaWd1cmUgMSBpbg0KPiB0aGUgTkFEQSBkcmFmdCwgSSB0aGluayBJJ20gbm93
IGJhc2ljYWxseSBhYmxlIHRvIGRvIGEgMToxIG1hcHBpbmcuIEhvd2V2ZXIsIEkNCj4gdGhpbmsg
aW4geW91ciBwaWN0dXJlIGl0IGlzIHdyb25nIHRvIGhhdmUgbXVsdGlwbGUgdmlkZW8gY29kZXIv
cmF0ZQ0KPiBjb250cm9sbGVyL3F1ZXVlcyBzaG93biBiZWNhdXNlIHRoYXQgaW5kaWNhdGVzIHRo
YXQgdGhlcmUgaXMgb25seSBvbmUNCj4gdHJhbnNtaXNzaW9uIHNjaGVkdWxlciBhbmQgY29uZ2Vz
dGlvbiBjb250cm9sbGVyIGZvciBhbGwgdHJhbnNtaXNzaW9ucywgd2hpY2gNCj4gaXMgbm90IHRo
ZSBjYXNlLiBJZiB5b3UgcmVtb3ZlIHRoYXQgcGFydCwgdGhlcmUgaXMgb25seSBvbmUgZGlmZmVy
ZW5jZSBsZWZ0DQo+IGJldHdlZW4gdGhlIHR3byBpbWFnZXMgYW5kIHRoYXQgaXMgdGhhdCB0aGVy
ZSBpcyBhbiBpbnB1dCBmcm9tIHRoZQ0KPiBjb25nZXN0aW9uIGNvbnRyb2wgdG8gdGhlIHZpZGVv
IHJhdGUgY29udHJvbGxlciBpbiBOQURBIHdoaWNoIHlvdSBkb24ndCBoYXZlDQo+IChhbHNvIHNl
ZSBjb21tZW50IDIgYWJvdmUpLiANCltJSl0gV2UgY2FuIHByb2JhYmx5IHJlbW92ZSB0aGUgZXhh
bXBsZSB3aXRoIG11bHRpcGxlIHZpZGVvcyBpZiBpdCBtYWtlcyB0aGluZ3MgbW9yZSBzaW1wbGUs
IGJ1dCBmYWN0IG9mIHRoZSBtYXR0ZXIgaXMgdGhhdCBTQ1JlQU0gY2FuIGhhbmRsZSBtdWx0aXBs
ZSBzb3VyY2VzLg0KDQoNCk90aGVyIHRoYW4gdGhhdCB0aGUgbWFwcGluZyB3b3VsZCBiZSB0aGUN
Cj4gZm9sbG93aW5nIHdheToNCj4gDQo+IE5BREENCj4gLS0tDQo+IFJlZmVyZW5jZSBSYXRlIENh
bGN1bGF0b3IgICAgLT4gTmV0d29yayBjb25nZXN0aW9uIGNvbnRyb2wNCj4gVmlkZW8gVGFyZ2V0
IFJhdGUgQ2FsY3VsYXRvciAtPiBSYXRlIENvbnRyb2wNCj4gU2VuZGluZyBSYXRlIENhbGN1bGF0
b3IgICAgICAtPiBUcmFuc21pc3Npb24gc2NoZWR1bGVyDQo+IEVuY29kZXIgICAgICAgICAgICAg
ICAgICAgICAgLT4gVmlkZW8gRW5jb2Rlcg0KPiBSYXRlIFNoYXBpbmcgQnVmZmVyICAgICAgICAg
IC0+IFF1ZXVlIFJUUCBwYWNrZXRzDQo+IA0KPiBJIHRoaW5rIGl0IHdvdWxkIGJlIHN1cGVyIGhl
bHBmdWwgdG8gdXNlIGEgY29tbW9uIHRlcm1pbm9sb2d5IGhlcmUgZm9yDQo+IGV2ZXJ5Ym9keSB0
byBiZXR0ZXIgdW5kZXJzdGFuZCBzaW1pbGFyaXRpZXMgYW5kIGRpZmZlcmVuY2VzLiANCltJSl0g
QWdyZWUsIGlmIHdlIGNhbiBjb21lIHVwIHdpdGggc29tZSBjb21tb24gdGVybXMsIHNvIG11Y2gg
dGhlIGJldHRlcg0KDQo+SSBndWVzcyB0aGUNCj4gc2FtZSBpcyB0cnVlIGZvciB2YXJpYWJsZSBh
bmQgcGFyYW1ldGVyIG5hbWVzIGlmIHRoZXJlIHRoaW5ncyB0aGF0IGFyZQ0KPiBhY3R1YWxseSB0
aGUgc2FtZS4gTm90ZSB0aGF0IHlvdSBpbiBzb21lIGNhc2UgYWxyZWFkeSB1c2UgdGhlIHNhbWUg
bmFtZXMgKEkNCj4gZGlkbid0IGNoZWNrIGhvd2V2ZXIgaWYgdGhlIHRoaW5ncyB0aGF0IGhhdmUg
dGhlIHNhbWUgbmFtZSBhY3R1YWxseSBhcmUgdGhlDQo+IHNhbWUgdGhpbmdzLi4uKQ0KPiANCj4g
MykgSSB0aGluayBpdCBpcyBncmVhdCB0byBoYXZlIGEgc2VjdGlvbiB0byBsaXN0IGFsbCBwYXJh
bWV0ZXJzIGFuZCB2YWx1ZXMuDQo+IFRoYW5rcyEgSG93ZXZlciBJIGRvIGhhdmUgdG8gc2F5IEkg
ZmluZCB0YWJsZXMgaGVyZSBub3QgdGhlIHJpZ2h0IGNob2ljZQ0KPiBiZWNhdXNlIGl0IGp1c3Qg
c3RyZXRjaGVzIHRoZSBpbmZvcm1hdGlvbiBvdmVyIG1vcmUgcGFnZXMgdGhhbiBuZWVkZWQgYW5k
DQo+IHRoZXJlZm9yZSBtYWtlcyBpdCBhY3R1YWxseSBoYXJkZXIgdG8gZmluZCB0aGUgcmlnaHQg
Yml0LiBGdXJ0aGVyIHRoZXJlIGFyZSBhDQo+IGZldyB2YXJpYWJsZXMgdGhhdCBhcmUgYWN0dWFs
bHkgcGFyYW1ldGVycyBhbmQgbGlzdGVkIHdyb25nbHkuIFR3byBleGFtcGxlcw0KPiBJJ3ZlIGZv
dW5kIGFyZTogbXNzIGFuZCBtaW5fY3duZCAoc2hvdWxkIGJlIE1TUyBhbmQgTUlOX0NXTkQgd2hp
Y2gNCj4geW91IGV2ZW4gd3JpdGUgdGhpcyB3YXkgc29tZXRpbWVzKS4NCltJSl0gSSBoYXZlIHRv
IGJsYW1lIHRoZSB1c2Ugb2YgdGFibGVzIG9uICBteSBtZWRpb2NyZSBYTUwgc2tpbGxzLCBpcyBh
IGxpc3QgYmV0dGVyID8uIFdpbGwgY29ycmVjdCB0aGUgTVNTIGFuZCBNSU5fQ1dORCBlcnJvciwg
dGhhbmtzDQoNCj4gRnVydGhlciBmb3IgdmFyaWFibGVzIEkgd291bGQgbm90DQo+IGluZGljYXRl
IHRoZSBpbml0aWFsIHZhbHVlcyBoZXJlLiBJJ2QgcHJvcG9zZSB0byBoYXZlIGEgaW5pdCBmdW5j
dGlvbiBpbnN0ZWFkIGluDQo+IHRoZSBsYXRlciBkZXNjcmlwdGlvbiB3aGVyZSBvbmUgY2FuIHNl
ZSBhbGwgaW5pdGlhbCB2YWx1ZSBhdCBvbmNlIChsaWtlIGluIHRoZQ0KPiBMRURCQVQgZHJhZnQp
LiBGdXJ0aGVyIHBsZWFzZSByZXZpZXcgaWYgYWxsIHZhcmlhYmxlcyBhcmUgYWN0dWFsbHkgbmVl
ZGVkLiBJZg0KPiB0aGVyZSBhcmUgb25seSB0ZW1wb3JhbCBhbmQgbm90IHZhcmlhYmxlcyB0aGF0
IGFjdHVhbGx5IGhvbGQgc3RhdGUgaW4gdGhlDQo+IHBzZXVkbyBjb2RlLCBJIGRvbid0IHRoaW5r
IHRoZXkgbmVlZCB0IGJlIGxpc3RlZCBoZXJlLg0KW0lKXSBPSywgc291bmRzIGdvb2QuDQoNCj4g
DQo+IA0KPiBGdXJ0aGVyIGNvbW1lbnRzIGZvbGxvd2luZyB0aGUgc3RydWN0dXJlIG9mIHRoZSBk
b2N1bWVudDoNCj4gDQo+IFNlY3Rpb24gMTogSSd2ZSBhbHNvIG1hZGUgdGhpcyBjb21tZW50IHJl
Z2FyZGluZyB0aGUgTkFEQSBkb2M6IEkgZ3Vlc3MNCj4gZXZlcnkgYWxnb3JpdGhtIGRvYyBzaG91
bGQgcmVmZXIgdGhlIHJlcXVpcmVtZW50cyBkb2MgYW5kIHRvIHNvbWUgZXh0ZW5kDQo+IGRpc2N1
c3MgaWYgYW5kIGhvdyB0aGVzZSByZXF1aXJlbWVudHMgaGF2ZSBiZWVuIGFkZHJlc3NlZC4uLg0K
PiANCj4gU2VjdGlvbiAxLjE6IG5vdCBzdXJlIHdoeSB0aGlzIHNlY3Rpb24gaXMgdGhlcmU7IGRv
bid0IHNlZSBhIG5lZWQgdG8gaGF2ZSB0aGlzDQo+IGluZm9ybWF0aW9uIGluIHRoaXMgZG9jdW1l
bnQgYmVjYXVzZSBpdCBkb2Vzbid0IGhlbHAgbWUgdW5kZXJzdGFuZCB0aGUNCj4gYWxnb3JpdGht
IGFueSBiZXR0ZXIuDQo+IA0KPiBTZWN0aW9uIDM6DQo+IC0gcy9mb2xsb3dzIHBhY2tldCBjb25z
ZXJ2YXRpb24gcHJpbmNpcGxlcy9mb2xsb3dzIHRoZSBwYWNrZXQgY29uc2VydmF0aW9uDQo+IHBy
aW5jaXBsZS8NCj4gLSBJIHRoaW5rIHRoaW5rIEZBQ0sgaXMgbm90IHRoZSByaWdodCByZWZlcmVu
Y2UgZm9yIHRoZSBwYWNrZXQgY29uc2VydmF0aW9uDQo+IHByaW5pcGxlLCBzaG91bGQgYmUgICJD
b25nZXN0aW9uIEF2b2lkYW5jZSBhbmQgQ29udHJvbCIgYnkgVmFuIEphY29ic2VuDQo+IGFuZCBN
aWNoYWVsIEouIEthcmVscywgU0lHQ09NJzg4IChzZWUgcmVmZXJlbmNlIEphYzg4IG9mIEZBQ0sg
cGFwZXIpLg0KPiAtIHMvVGhlIHBhY2tldCBjb25zZXJ2YXRpb24gcHJpbmNpcGxlIGlzIHJlYWxp
emVkIGJ5L0luIFNjcmVhbSwgdGhlIHBhY2tldA0KPiBjb25zZXJ2YXRpb24gcHJpbmNpcGxlIGlz
IHJlYWxpemVkIGJ5LyAtPiBvdGhlcndpc2UgaXQgc291bmRzIGxpa2UgaXQncyBhbHdheXMNCj4g
cmVhbGl6ZWQgdGhpcyB3YXksIHdoaWNoIGlzIG5vdCB0cnVlLg0KW0lKXSBPSw0KDQo+IC0gTWF5
YmUgZ2l2ZSBhbHJlYWR5IGEgc3VwZXIgYnJpZWYgZGVzY3JpcHRpb24gb2Ygd2hhdCBMRURCQVQg
aXMgZG9pbmc6DQo+ICAgIHMvaW4gYSB3YXkgc2ltaWxhciB0byBMRURCQVQgW1JGQzY4MTddLi9p
biBhIHdheSBzaW1pbGFyIHRvIExFREJBVA0KPiBbUkZDNjgxN10gYnkgbWFpbnRhaW5pbmcgYSBn
aXZlbiB0YXJnZXQgZGVsYXkuLw0KPiAtIFRoaXMgdGV4dCBmdXJ0aGVyIHNheSAiYSBmZXcgc3Rl
cHMgdG8gdGFrZSB0byBtYWtlIHRoZSBjb25jZXB0IHdvcmsgd2l0aA0KPiBjb252ZXJzYXRpb25h
bCBtZWRpYSIuIE1heWJlIGFscmVhZHkgbmFtZSB0aGVzZSBzdGVwcyB2ZXJ5IGJyaWVmbHkgaGVy
ZToNCj4gZS5nLg0KPiB0YWtpbmcgdGhlIGRlbGF5IHRyZW5kIGludG8gYWNjb3VudCBhbmQgdGhl
IHByZXZpb3VzIG1heGltdW0gcmF0ZSB0bw0KPiBjb21wZXRlIHdpdGggb3RoZXIgbm9uLWRlbGF5
IGJhc2VkIHRyYWZmaWMuLi4NCltJSl0gT0sNCj4gDQo+IFNlY3Rpb24gMy4xDQo+IC0gWW91IHNh
eSB0aGVyZSBhcmUgc2ltaWxhcml0aWVzIHdpdGggbmV3Y3d2IGJ1dCB0aGVuIG5ldmVyIG1lbnRp
b24gdGhpcw0KPiBhZ2Fpbi4NCj4gQ2FuIHlvdSBleHBsYWluIHdoYXQgdGhlIHNpbWlsYXJpdGll
cyBhcmU/IEkndmUganVzdCByZXZpZXdlZCBuZXdjd3YgYW5kIHRoaXMNCj4gaXMgYWJzb2x1dGVs
eSBub3QgY2xlYXIgdG8gbWUuLi4NCltJSl0gT0ssIHdpbGwgbmVlZCB0byBjbGFyaWZ5IHRoaXMu
DQoNCj4gLSBGYXN0IHN0YXJ0OiBNYXkgSSBwcm9wb3NlIHRvIG5hbWUgdGhpcyBGYXN0IEluY3Jl
YXNlIGluc3RlYWQgKGFuZCBhbHNvDQo+IGFsd2F5cyB3cml0ZSB0aGlzIHdpdGggdXBwZXIgbGV0
dGVycykuIEFjdHVhbGx5IHRoYXQncyB0aGUgc2FtZSBuYW1lIEkgdXNlZCBmb3INCj4gVENQIFNJ
QUQgd2hlcmUgSSBhbHNvIGhhdmUgdGhpcyBtZWNoYW5pc20gdGhhdCBpcyBraW5kIG9mIHNpbWls
YXIgdG8gU2xvdyBTdGFydA0KPiBidXQgY2FuIGJlIHJlc3VtZWQgbGF0ZXIgYXMgd2VsbC4gSSBw
cm9wb3NlIHRoaXMgY2hhbmdlIChub3QganVzdCBiZWNhdXNlIEkNCj4gd2FudCBteSBuYW1lIHRv
IGJlIHVzZWQgOy0pIGJ1dCkgYmVjYXVzZSBoYXZpbmcgJ3N0YXJ0JyBpbiB0aGUgbmFtZSBpcw0K
PiBjb25mdXNpbmcgdG8gbXkgaWYgeW91IG5vdCBvbmx5IHVzZSB0aGlzIG1lY2hhbmlzbSB0byBh
Y3R1YWxseSBzdGFydCBvciByZS0NCj4gc3RhcnQgYSB0cmFuc21pc3Npb24uDQo+IC0gQWxzbyBt
YXliZSBiZSBzbGlnaHRseSBtb3JlIGNvbmNyZXRlIGhlcmUgKG9uIGEgaGlnaCBsZXZlbCkgYWJv
dXQgd2hhdCBmYXN0DQo+IHN0YXJ0IGlzIGRvaW5nOiBlLmcgImltcGxlbWVudHMgYW5kIG11bHRp
cGxpY2F0aXZlIGluY3JlYXNlIHRvIHF1aWNrbHkgcmVhY2gNCj4gdGhlIG1heGltdW0gY2FwYWNp
dHkgd2hlcmUgdGhlIGluY3JlYXNlIGZhY3RvciBpcyBzY2FsZWQgYmFzZWQgb24gYQ0KPiBwcmV2
aW91cyBtYXhpbXVtIHJhdGUgKGV4cGVjdCBhdCB0cmFuc21pc3Npb24gc3RhcnQpLiBGYXN0IHN0
YXJ0IGlzIHJlc3VtZWQNCj4gZHVyaW5nIGEgdHJhbnNtaXNzaW9uIGlmIHRoZSBkZWxheSB0cmVu
ZCBnb2VzIGJlbG93IGEgY2VydGFpbiB0aHJlc2hvbGQuIiBCdHcuDQo+IEkgd291bGQgYWxzbyBh
cHByZWNpYXRlIHRvIGludHJvZHVjZSBhIHBhcmFtZXRlciBmb3IgdGhpcyB0aHJlc2hvbGQgYW5k
IG5vdA0KPiBvbmx5IHNheSAibGVzcyB0aGFuIDAuMiBmb3INCj4gMS4wIHNlY29uZHMgb3IgbW9y
ZSIgKHNlZSBsYXRlciBpbiBzZWN0aW9uIDQuMS4yLjEpLg0KPiAtIHMvd2l0aCBGVFAgdHJhZmZp
Yy93aXRoIGJ1bGsgdHJhZmZpYy8NCltJSl0gT0sgOi0pICwgRmFzdCBJbmNyZWFzZSBpdCBpcyAh
LCBuZXZlciBmZWx0IGNvbWZvcnRhYmxlIHdpdGggdGhlICJmYXN0IHN0YXJ0IiB0ZXJtLiBEbyB5
b3UgaGF2ZSBhIHJlZmVyZW5jZSB0byB5b3VyIFRDUCBTSUFEIHdvcmsuIFdvdWxkIGJlIG5pY2Ug
dG8gc2VlIGl0IGFzIEkgYW0gbG9va2luZyBhdCB3YXlzIHRvIHJlY292ZXIgZnJvbSBmYWlsZWQg
VENQIEN1YmljIEh5U3RhcnRzIChyZWxhdGVkIHRvIGlzc3VlcyB3ZSBzZWUgd2l0aCBIeVN0YXJ0
IGFuZCBMVEUgYWNjZXNzKQ0KDQo+IA0KPiBTZWN0aW9uIDMuMi4NCj4gLSBUaGlzIHNlY3Rpb24g
c2F5cyBwYWNrZXQgcGFjaW5nIGlzIHVzZWQsIGhvd2V2ZXIgSSBkb24ndCB0aGluayB0aGlzIGlz
IGZ1cnRoZXINCj4gbWVudGlvbiBpbiB0aGUgcmVzdCBvZiB0aGUgdGV4dC4uLiBwbGVhc2UgYWRk
IHNvbWV0aGluZyBvbiB0aGlzLi4uIG9yIHRoZXJlDQo+IG1pZ2h0IGJlIGEgY29uZnVzaW9uIGJl
dHdlZW4gbWUgYW5kIHlvdSB3aGF0IHBhY2luZyBtZWFucyAoc2VlIGJlbG93KS4NCltJSl0gUGFj
a2V0IHBhY2luZyB3YXMgYnJva2VuIG91dCB0byB0aGUgYXBwZW5kaXggc2VjdGlvbiBBLjEsIHRo
ZSByZWFzb24gd2FzIHRoYXQgaXQgZGlkIG5vdCBzZWVtIHRvIGZpdCB3aXRoIHRoZSBlYXJsaWVy
IGNvbnNlbnN1cyB0aGF0IHRoZSBjb25nZXN0aW9uIGNvbnRyb2wgc2hvdWxkIGNvbXB1dGUgYSBz
ZW5kIHdpbmRvdy4gQnV0IEkgZ3Vlc3MgdGhlIHBhY2tldCBwYWNpbmcgc2VjdGlvbiBjYW4gYmUg
bW92ZWQgdG8gYW4gZWFybGllciBzZWN0aW9uDQoNCj4gDQo+IFNlY3Rpb24gMy4zLg0KPiAtIE1h
eWJlIGFscmVhZHkgaW5jbHVkZSB0aGUgcmVsZXZhbnQgcGFydCBvZiBmaWd1cmUgMSBoZXJlIGJl
Y2F1c2UgYSBmaWd1cmUNCj4gcmVhbGx5IGhlbHBzLiBPciBpbmNsdWRlIHRoZSB3aG9sZSBmaWd1
cmUgMSBpbiBzZWN0aW9uIDMgYW5kIHN0cnVjdHVyZSB0aGUNCj4gb3ZlcnZpZXcgYmFzZWQgb24g
dGhpcyBpbWFnZS4NCj4gDQo+IFNlY3Rpb24gNC4xDQo+IC0gSSBndWVzcyB5b3UgY2FuIHJlbW92
ZSB0aGUgcmVmZXJlbmNlIHRvIEktRC5pZXRmLXJtY2F0LWFwcC1pbnRlcmFjdGlvbg0KPiBiZWNh
dXNlIHdlIGFyZSB3b3JraW5nIG9uIHRoaXMgZHJhZnQgYW55bW9yZS4gSG93ZXZlciwgaXQgd2Fz
IGFueXdheSBub3QNCj4gY2xlYXIgd2hhdCBleGFjdGx5IHlvdSBhcmUgcmVmZXJlbmNpbmcgaXQg
Zm9yLiBGcm9tIG15IHBvaW50IG9mIHZpZXcNCj4gZXhwbGFpbmluZyB0aGUgcmVsYXRpb25zaGlw
IHRvIG90aGVyIGRvY3MgKG9mIHRoZSBzYW1lIHdnKSBpcyBvZnRlbiBkb25lIGJlc3QNCj4gaW4g
dGhlIGludHJvLg0KW0lKXSBQZXJoYXBzIFphaGVkIGNhbiBleHBsYWluIHRoZSByZWYgdG8gdGhl
IGFwcCBpbnRlcmNhdGlvbiBhcyBJIGhhdmUgbm90IGJlZW4gaW52b2x2ZWQgaW4gdGhhdCB3b3Jr
DQoNCj4gLSBPbiBGaWd1cmUgMTogQXMgc2FpZCBhYm92ZSBJIGZpbmQgaXQgY29uZnVzaW5nIHRo
YXQgdGhlcmUgYXJlIG11bHRpcGxlIHZpZGVvDQo+IHN0cmVhbXMgaGVyZSBiZWNhdXNlIHRoYXQg
aW5kaWNhdGVzIHRoYXQgdGhlcmUgaXMgb25seSBvbmUgY29uZ2VzdGlvbg0KPiBjb250cm9sbGVy
IGFuZCBvbmUgdHJhbnNtaXNzaW9uIHNjaGVkdWxlciBmb3IgYWxsIHRyYW5zbWlzc2lvbnMuIEZv
ciB0aGUgc2FtZQ0KPiByZWFzb24gSSBhY3R1YWxseSBmaW5kIHRoZSBuYW1lIHRyYW5zbWlzc2lv
biBzY2hlZHVsZXIgY29uZnVzaW9uIGJlY2F1c2UgYQ0KPiBzY2hlZHVsZXIgd291bGQgYWN0dWFs
bHkgYmUgdGhlIG9uZSB3aG8gZGVjaWRlcyB3aGljaCBwYWNrZXQgdG8gcHV0IG9uIHRoZQ0KPiBs
aW5rIGF0IHdoaWNoIHRpbWUgKHdoaWNoIG9mdGVuIGlzIGRvbmUgb24gdGhlIG5pYykuIEhvd2V2
ZXIgeW91cg0KPiB0cmFuc21pc3Npb24gc2NoZWR1bGVyIGlzICdvbmx5JyBjYWxjdWxhdGluZyB0
aGUgc2VuZGluZyB3aW5kb3csIHRoZXJlZm9yZSBJDQo+IGNhbGwgaXQgc29tZXRoaW5nIGxpa2Ug
c2VuZGluZyByYXRlIGNvbnRyb2xsZXIuLi4NCltJSl0gQ291bGQgYmUgT2sgdG8gcmVuYW1lIGl0
IHRvIHNlbmRpbmcgcmF0ZSBjb250cm9sbGVyLCBJIGRvbid0IGhhdmUgYW55IHN0cm9uZyBvcGlu
aW9uLiBOb3RlIHRoYXQgU0NSZUFNIGNhbiBpbiBmYWN0IGNvbmdlc3Rpb24gY29udHJvbCBtb3Jl
IHRoYW4gb25lIHN0cmVhbSwgdGhpcyBpcyBzaW1pbGFyIHRvIGhvdyBTQ1RQIGFuZCBRVUlDIHdv
cmtzLiAgIA0KDQo+IA0KPiBTZWN0aW9uIDQuMS4yLjENCj4gLSBBdCB0aGUgYmVnaW5uaW5nIG9m
IHRoaXMgc2VjdGlvbiB5b3UgZGVmaW5lIHNvbWUgdGVybWlub2xvZ3kuIE1heWJlIHB1dA0KPiB0
aGlzIGluIHRoZSB0ZXJtaW5vbG9neSBzZWN0aW9uIGluc3RlYWQ/DQo+IC0gSSd2ZSBhbHNvIGFz
a2VkIHRoaXMgcXVlc3Rpb24gZm9yIE5BREE6IERvbid0IHlvdSBuZWVkIHN5bmNocm9uaXplZCBj
bG9ja3MNCj4gYXQgdGhlIHNlbmRlciBhbmQgcmVjZWl2ZXIuIFBsZWFzZSBmdXJ0aGVyIGRpc2N1
c3MgdGhpcyENCltJSl0gTm8uIFN5bmNocm9uaXplZCBjbG9ja3MgYXJlIG5vdCBuZWVkZWQsIEkg
YW0gYSBiaXQgaGVzaXRhbnQgYWJvdXQgdGhlIGltcGFjdCBvZiBjbG9jayBza2V3LiBUaGUgInJl
YWwiIGNvZGUgcmVzZXRzIHRoZSBiYXNlIGRlbGF5IGhpc3RvcnkgaXQgdGhlIE9XRCB0YWtlcyBv
biBpbnJlYXNvbmFibGUgdmFsdWVzLCB0aGlzIGlzIG5vdCBtZW50aW9uZWQgaW4gdGhlIGRyYWZ0
IGhvd2V2ZXIuIFdpbGwgZml4IHRoaXMNCg0KPiAtIFBsZWFzZSBhbHNvIGdpdmUgbW9yZSBkZXRh
aWxzIGhvdyBsb3NzIGRldGVjdGlvbiBpcyBkb25lLiBJIGd1ZXNzIHRoYXQncw0KPiBzaW1wbHkg
aW5kaWNhdGVkIGluIGFuIFJUQ1AgcmVwb3J0Li4/IFBsZWFzZSBzYXkgd2hpY2ggaW5mb3JtYXRp
b24gYXJlIGV4YWN0bHkNCj4gdXNlZC4NCltJSl0gVGhlIG5fbG9zcyBjb3VudGVyIGlzIGNoZWNr
ZWQsIGlmIGl0IGhhcyBpbmNyZW1lbnRlZCBieSBvbmUgb3IgbW9yZSBzdGVwcyBpbiBhbiBSVFQg
aXQgaXMgY29uc2lkZXJlZCBhIGxvc3MgZXZlbnQuIFdpbGwgY2xhcmlmeSB0aGlzDQoNCj4gLSBQ
bGVhc2UgZ2l2ZSBhbHNvIHNvbWUga2luZCBvZiBwc2V1ZG8gY29kZSBvbiBob3cgYnl0ZXNfbmV3
bHlfYWNrZWQgaXMNCj4gdXBkYXRlZC4NCltJSl0gT0sNCg0KPiBUaGF0IHNpbXBseSBoZWxwcyBw
ZW9wbGUgdG8gaW1wbGVtZW50IHRoaW5ncyBjb3JyZWN0bHkuDQo+IC0gQXMgc2FpZCBhYm92ZSBJ
IHdvdWxkIHN0cnVjdHVyZSB0aGUgcHNldWRvIGNvZGUgaW4gZnVuY3Rpb25zIHdoZXJlIG9uZQ0K
PiBmdW5jdGlvbiB3b3VsZCBiZSBhbiBpbml0IGZ1bmN0aW9uIGhlcmUuIFRoYXQgYWxzbyBoZWxw
cyB0byBhdm9pZA0KPiBpbXBsZW1lbnRhdGlvbiBlcnJvcnMuDQpbSUpdIEl0IGlzIGNoYWxsZW5n
aW5nIHRvIHdyaXRlIGFuIGF1dG9jb3JyZWxhdGlvbiBmdW5jdGlvbiBpbiBBU0NJSSBhcnQgYnV0
IEkgZ2l2ZSBpdCBhKG5vdGhlcikgdHJ5IDotKQ0KDQo+IC0gUGxlYXNlIGdpdmUgbW9yZSBkZXRh
aWxzIGhvdyB0aGUgZnVuY3Rpb24gUigpIGlzIGltcGxlbWVudGVkLg0KPiAtIFdoeSBpcyBzY2xf
aSBjYWxsZWQgdGhpcyB3YXk/IFdoYXQgZG9lcyB0aGUgaSBzdGFuZCBmb3I/IE1heWJlIHRha2Ug
YSBzbGlnaHRseQ0KPiBsb25nZXIgbW9yZSBtZWFuaW5nZnVsIG5hbWUgbGlrZSBzY2FsZV9pbmNy
ZWFzZS4gVGhpcyBoZWxwcyB0aGUgcmVhZGVyIHRvDQo+IGltbWVkaWF0ZWx5IHVuZGVyc3RhbmQg
d2hhdCB0aGlzIGlzIGxhdGVyIHVzZWQgZm9yIQ0KPiAtIFdoeSBpcyBzY2xfaSBsaW1pdGVkIHRv
IDAuMj8gU2hvdWxkIHRoaXMgYWxzbyBhIHBhcmFtZXRlcj8NCltJSl0gR29vZCBxdWVzdGlvbiAs
IHdvdWxkIHByb2JhYmx5IGJlIGJldHRlciB0byBqdXN0IHVzZSBzY2wgb3IgdG1wIGluc3RlYWQu
IA0KMC4yIGlzIHRoZXJlIHRvIGF2b2lkIHRoYXQgdGhlIGNvbmdlc3Rpb24gd2luZG93IGdyb3d0
aCBpcyBpcyBzZXQgdG8gemVyby4NCg0KPiAtIFBsZWFzZSBnaXZlIHNvbWUgcmVhc29uaW5nIHdo
eSBzY2xfaSBpcyBjYWxjdWxhdGVkIHRoaXMgd2F5ISBJcyB0aGlzIHNpbWlsYXIgdG8NCj4gQ3Vi
aWM/IElmIHNvIHBsZWFzZSByZWZlciENCltJSl0gWWVzLCBpdCBpcyB2ZXJ5IHNpbWlsYXIgdG8g
Q3ViaWMsIHBlcmhhcHMgSSBoYXZlIG9ubHkgcmVmZXJyZWQgdG8gdGhpcyBpbiBlbWFpbHMsIHdp
bGwgY2xhcmlmeSB0aGlzDQoNCj4gLSBJIGJlbGlldmUgdGhlIGNhbGN1bGF0aW9uIG9mIG9mZl90
YXJnZXQgaXMgb25seSBuZWVkZWQgaWYgbm90IGluIGZhc3Qgc3RhcnQuDQo+IElmIHNvIHBsZWFz
ZSBtb3ZlIGl0IQ0KW0lKXSBPSw0KDQo+IC0gY3duZF9pIGlzIGluaXRpYWxpemVkIHRvIDEuIFRo
YXQgc2VlbXMgcmVhbGx5IHdlaXJkIHRvIG1lLiBEb2VzIHRoaXMgd29yayB3ZWxsDQo+IGZvciBm
YXN0IHN0YXJ0IGF0IGEgYmVnaW5uaW5nIG9mIGEgdHJhbnNtaXNzaW9uPyBJIGd1ZXNzIHRoZSBp
bnRlbnRpb24gaXMgdG8gbWFrZQ0KPiBmYXN0IHN0YXJ0IGJlaGF2ZSBsaWtlIHNsb3cgc3RhcnQg
YXQgdGhlIGJlZ2lubmluZyBvZiBhIGNvbm5lY3Rpb24uIEluIHRoaXMgY2FzZQ0KPiBzY2xfaSBz
aG91bGQgYmUgMS4gV2h5IGRvbid0IHlvdSBqdXN0IHNldCBzY2xfaSB0byAxIGlmIGN3bmRfaSBo
YXMgbm90IGJlZW4gc2V0DQo+IHlldC4uLj8NCltJSl0gWWVzLCB5b3UgYXJlIHJpZ2h0LCAgY291
bGQgYmUgYW4gYWx0ZXJuYXRpdmUsDQoNCj4gLSBnYWluIGNhbGN1bGF0aW9uOiBvd2RfdHJlbmQg
aXMgYWx3YXlzIGEgdmFsdWUgYmV0d2VlbiAwIGFuZCAxLCB0aGVyZWZvcmUgaXQNCj4gY2FuIG5v
dCBiZSBuZWdhdGl2ZSwgdGhlcmVmb3JlIHRoZSBtYXgoKSBpbiB0aGUgZ2FpbiBjYWxjdWxhdGlv
biBjYW4gYmUNCj4gcmVtb3ZlZDoNCltJSl0gT0sNCg0KPiBnYWluID0gR0FJTiooMS4wICsgKDEu
MCAtIG93ZF90cmVuZC8gMC4yKSkNCj4gLSBXaGVyZSBpcyB0aGlzIDAuMiBpbiB0aGlzIGdhaW4g
Y2FsY3VsYXRpb24gYWdhaW4gY29taW5nIGZyb20uIElzIHRoZXJlIGEgZ29vZA0KPiByZWFzb25p
bmcgZm9yIHRoaXMgdmFsdWU/IFNob3VsZCB0aGlzIGJlIGFnYWluIGEgcGFyYW1ldGVyPyBJcyB0
aGlzIHRoZSBzYW1lDQo+IHBhcmFtZXRlciB0aGFuIHRoZSBwcmV2aW91cyAwLjI/DQpbSUpdIFRo
ZSAwLjIgdmFsdWVzIChubyByZWxhdGlvbiBiZXR3ZWVuIHRoZSB0d28gMC4yIHZhbHVlcyBhY3R1
YWxseSkgYXJlIHRoZSByZXN1bHRzIG9mIGV4cGVyaW1lbnRhdGlvbi4gVGhleSBhcmUgbm90IHRo
YXQgY3JpdGljYWwgaG93ZXZlciwgY291bGQgaGF2ZSBiZWVuIG90aGVyIHZhbHVlcyBsaWtlIDAu
My4gQ291bGQgYmUgZ29vZCB0byBoYXZlIHRoZW0gYXMgcGFyYW1ldGVycyAoYWN0dWFsbHkgSSBn
b3QgdGhlIHNhbWUgcmVtYXJrIGZyb20gRGFuaWVsIExpbmRzdHLDtm0gd2hvIGhlbHBlZCBtZSB0
byBnZXQgU0NSZUFNIGludG8gT3BlbldlYlJUQyA6LSkgLiAgDQoNCj4gLSBJJ2QgbW92ZSB0aGUg
ZGlzY3Vzc2lvbiB3aGF0IHRoZSBkaWZmZXJlbmNlIHRvIExFREJBVCBpcyBpbnRvIHNlY3Rpb24g
My4xDQo+IGJlY2F1c2UgdGhlc2UgcG9pbnQgYXJlIHZlcnkgZ2VuZXJhbCBhbmQgdGhlcmVmb3Jl
IG5vIGFsZ29yaXRobSBkZXRhaWxzIGFyZQ0KPiBuZWVkZWQgdG8gYmUga25vd24gYW5kIHlvdSBt
ZW50aW9uIHRob3NlIGRpZmZlcmVuY2UgdGhlcmUgYWxyZWFkeQ0KPiB3aXRob3V0IHNheWluZyB3
aGF0IHRoZXkgYWN0dWFsbHkgYXJlLg0KPiAtIEhvd2V2ZXIsIHlvdSBzYXkgeW91IGRvbid0IHVz
ZSBBTExPV0VEX0lOQ1JFQVNFIGJ1dCBpc24ndA0KPiBNQVhfQllURVNfSU5fRkxJR0hUX0hFQURf
Uk9PTSBlZmZlY3RpdmUgdGhlIHNhbWUuLi4/DQpbSUpdIEhtbSwgd2lsbCBoYXZlIHRvIGxvb2sg
aW50byB0aGlzLi4gbmVlZCB0byBjb21lIGJhY2sNCg0KPiAtIFRoZSBwYXJ0IG9uIGZsb3cgY29t
cGVuc2F0aW9uIGlzIHJhdGhlciB1bmNsZWFyISBTdWRkZW5seSB5b3UgaGF2ZSB0d28NCj4gbmV3
IHBhcmFtZXRlcnMgb3dkX25vcm1fbWVhbl9zaCBhbmQgb3dkX25vcm1fdmFyOiBob3cgYXJlIHRo
ZXkNCj4gY2FsY3VsYXRlZD8gV2hlbiBhcmUgdGhleSB1cGRhdGVkPyBJIHRoaW5rIHRoZXJlIGlz
IHNvbWV0aGluZyBtaXNzaW5nDQo+IHNvbWV3aGVyZS4gRnVydGhlciB3aGVyZSBkb2VzIHRoaXMg
Zm9ybXVsYSBjb21lIGZyb20/IEkgZ3Vlc3MgdGhlcmUgaXMNCj4gc29tZSBwcmV2aW91cyB3b3Jr
aW5nIHRoYXQgcHJvcG9zZWQgdGhpcyBhcHByb2FjaD8gQ2FuIHlvdSBnaXZlIGENCj4gcmVmZXJl
bmNlIGFuZCBmdXJ0aGVyIGV4cGxhaW4gd2h5IHRoaXMgYXBwcm9hY2ggaXMgdGFrZW4/DQpbSUpd
IFlvdSBiZWF0IG1lIHRvIHRoZSBwdW5jaCBoZXJlLiBUaGlzIGlzIGluc3BpcmVkIGJ5IHRoZSB3
b3JrIG9uIHNoYXJlZCBib3R0bGVuZWNrIGRldGVjdGlvbiBpbiBSTUNBVC4gIEkgaW1wbGVtZW50
ZWQgdGhlIHZhcmlhbmNlIGFuZCBza2V3IGVzdGltYXRlcyBhbiBvYnNlcnZlZCB0aGF0IHRoZXkg
YWN0dWFsbHkgaW5kaWNhdGUgcXVpdGUgd2VsbCB3aGVuIGNvbXBldGluZyBmbG93cyBlbnRlciBh
bmQgc3RpbGwgdGhlIHJpc2sgaXMgcXVpdGUgc21hbGwgdGhhdCBpdCBjYXVzZXMgc2VsZi1pbmZs
aWN0ZWQgY29uZ2VzdGlvbi4gDQoNCj4gDQo+IFNlY3Rpb24gNC4xLjIuMg0KPiAtIEknZCBtb3Zl
IHRoZSBpbml0aWFsIHBhcnQgaGVyZSB3aXRoIHRoZSB0d28gYnVsbGV0IHBvaW50cyBpbnRvIHNl
Y3Rpb24gMy4yDQo+IGJlY2F1c2UgdGhpcyBpcyByYXRoZXIgc29tZSBoaWdoIGxldmVsIGluZm8u
DQo+IC0gSSBkb24ndCB0aGluayBJIHdvdWxkIGNhbGwgdGhlIHByb3Bvc2VkIGFwcHJvYWNoIHBh
Y2luZy4gUGFjaW5nIGlzIGZvciBtZSB0aGF0DQo+IGlmIHlvdSBjYW4gc2VuZCB5b3UgbXVsdGlw
bGUgcGFja2V0IGF0IG9uY2UgKGJlY2F1c2UgdGhlIHNlbmQvY29uZ2VzdGlvbg0KPiB3aW5kb3cg
aXMgbGFyZ2UgZW5vdWdoKSB0aGF0IHlvdSBzcHJlYWQgdGhlIHNlbmRpbmcgdGltZXMgb2YgZWFj
aCBwYWNrZXQNCj4gb3ZlciB0aGUgdGltZSBpbnRlcnZhbCB1bnRpbCB0aGUgbmV4dCBBQ0svdXBk
YXRlIGlzIGV4cGVjdGVkLg0KW0lKXSBUaGF0IGlzIGFjdHVhbGx5IHdoYXQgdGhlIHBhY2luZyBm
dW5jdGlvbiBkb2VzIGluIHRoZSBjb2RlLCBwZXJoYXBzIEkgbmVlZCB0byB3b3JrIHRoZSB0ZXh0
IGhlcmUsDQo+IC0gRnVydGhlciB0aGUgY2FsY3VsYXRpb24gc2VlbXMgcmF0aGVyIGNvbXBsaWNh
dGVkLiBJcyB0aGlzIHJlYWxseSBuZWVkZWQ/IENhbg0KPiB5b3UgZnVydGhlciBleHBsYWluIGlu
IHRoZSBkb2MgaW4gd2hpY2ggY2FzZSB0aGlzIGFwcHJvYWNoIGhlbHBzIHdoaWNoDQo+IHByb2Js
ZW0gYW5kIHdoeT8hDQpbSUpdIE9LICwgd2lsbCBjbGFyaWZ5DQo+IA0KPiBTZWN0aW9uIDQuMS4z
DQo+IC0gV2h5IGlzIHRoZSBlc3RpbWF0aW9uIGludGVydmFsIDIwMG1zIChzaG91bGRuJ3QgdGhp
cyBiZSBhIHBhcmFtZXRlciBhcw0KPiB3ZWxsPykgYnV0IHRoZSBSQVRFX0FESlVTVE1FTlRfSU5U
RVJWQUwgMTAwbXM/IElmIHlvdSBvbmx5IGVzdGltYXRlDQo+IGV2ZXJ5IDIwMG1zIHRoZXJlIHdp
bGwgYmUgbm8gbmV3IGluZm9ybWF0aW9uIGFmdGVyIDEwMG1zIHRvIGFkanVzdA0KPiBzb21ldGhp
bmcuLi4/DQpbSUpdIFByb2JhYmx5IGEgbWlzdGFrZSwgc2hvdWxkIGJlIDIwMG1zLCBhY2NvcmRp
bmcgdG8gdGhlIGltcGxlbWVudGF0aW9uDQoNCj4gLSBzLyBpZiB0aGUgY29uZ2VzdGlvbiBjb250
cm9sIGlzIGlmIGZhc3Qgc3RhcnQgb3Igbm90Li8gaWYgdGhlIGNvbmdlc3Rpb24gY29udHJvbCBp
cw0KPiBpbiBmYXN0IHN0YXJ0IG9yIG5vdC4vDQo+IC0gSW4gZ2VuZXJhbCwgYXMgbWVudGlvbiBh
Ym92ZSwgdGhlcmUgaXMgbW9yZSBleHBsYW5hdGlvbiBuZWVkZWQgb24gdGhlDQo+IHNpbmdsZSBz
dGVwcyBvZiB0aGUgdmlkZW8gcmF0ZSBjb250cm9sbGVyLCBlc3BlY2lhbGx5IG9uDQo+ICAgIC0g
V2hhdCBpcyBSTUFQX1VQX1RJTUUgYWN0dWFsbHkgZ29vZCBmb3I/IFdoeSBpcyB0aGlzIDEwcz8N
CltJSl0gVGhpcyBpcyBhY3R1YWxseSBhIG1pc3Rha2UsIGl0IGlzIHJlcGxhY2VkIGJ5IGEgUkFN
UF9VUF9TUEVFRCBwYXJhbWV0ZXIgdGhhdCBpbmRpY2F0ZXMgDQp0aGUgbWF4IGluY3JlYXNlIG9m
IHRoZSB0YXJnZXQgcmF0ZSBpbiBbYnBzL3NdDQoNCj4gICAgLSBQbGVhc2UgZXhwbGFpbiBmdXJ0
aGVyIHdoeSBpbmNyZW1lbnQgaXMgY2FsY3VsYXRlZCB0aGUgd2F5IGl0IGlzIGNhbGN1bGF0ZWQh
DQpbSUpdIFdpbGwgYWRkIGFuIGV4cGxhbmF0aW9uDQoNCj4gICAgLSBTaG91bGRuJ3QgdGhlIHRh
cmdldF9iaXRyYXRlIGJlIG9ubHkgaW5jcmVhc2VkIGluIHN0ZXBzIHRoYXQgdGhlIGVuY29kZXIN
Cj4gY2FuIGhhbmRsZT8NCltJSl0gVGhlcmUgYXJlIG5vIGFjdHVhbCBzdGVwcyB0aGF0IHRoZSBl
bmNvZGVyIGNhbiBoYW5kbGUuIE9uZSB0eXBpY2FsbHkganVzdCBzZXQgYSB0YXJnZXQgcmF0ZSBh
bmQgdGhlIHJhdGUgY29udHJvbCBsb29wIGluIHRoZSB2aWRlbyBlbmNvZGVyIHRyaWVzIHRvIGFk
YXB0IHRvIGl0Lg0KDQo+ICAgIC0gUGxlYXNlIHlvdSBmdXJ0aGVyIGV4cGxhaW4gdGhlIGxhc3Qg
cGFydCBvbiByYXRlX3J0cF9saW1pdCEhIQ0KW0lKXSBZZXMsIHRoaXMgcGFydCBwcm9iYWJseSBu
ZWVkcyBhIGJldHRlciBleHBsYW5hdGlvbiwgaXQgd2FzIGFkZGVkIHF1aXRlIHJlY2VudGx5IGFz
IGEgcmVtZWR5IHRvIHNvbWUgcmVhbC1saWZlIGlzc3VlcyB3aXRoIHZpZGVvIGNvZGluZy4NCg0K
PiANCj4gU2VjdGlvbiA0LjINCj4gLSBIZXJlIHRoZSB0YWJsZSBpcyBnb29kIGJlY2F1c2UgdGhl
cmUgYXJlIGxlc3MgdmFsdWVzIGFuZCBpdCBhY3R1YWxseSBwcm92aWRlcw0KPiBhIG5pY2Ugb3Zl
cnZpZXchDQpbSUpdIE9LLCBnb29kICENCg0KPiANCj4gU2VjdGlvbiA1Lg0KPiAtIFRoaXMgbmVl
ZHMgdG8gZ28gaW4gYW4gb3duIGRyYWZ0IGF0IHNvbWUgcG9pbnQuIFBsZWFzZSBhbHNvIGNvbXBh
cmUNCj4gc2ltaWxhcml0aWVzIHdpdGggdGhlIGluZm9ybWF0aW9uIG5lZWRlZCBieSBOQURBIGFu
ZCBHQ0MhDQpbSUpdIE9LDQoNCj4gDQo+IFNlY3Rpb24gNw0KPiAtIEFjdHVhbGx5IGEgY29uY2x1
c2lvbiBpcyBub3QgbmVlZGVkIGZvciBhbiBJRVRGIEludGVybmV0IGRyYWZ0Li4uDQpbSUpdIE9L
LCBncmVhdCENCg0KPiANCj4gU2VjdGlvbiA4DQo+IC0gcmVnYXJkaW5nIHRoZSBjbG9jayBkcmlm
dCBjb21wZW5zYXRpb24sIHBsZWFzZSBzZWUgdGhlIGFwcGVuZGl4IG9mIHRoZQ0KPiBMRURCQVQg
UkZDLiBJZiB5b3UndmUgaW1wbGVtZW50ZWQgYmFzaWNhbGx5IHRoZSBzYW1lIHRoaW5nIGFzIGRl
c2NyaWJlZA0KPiB0aGVyZSwgaXQgcHJvYmFibHkgZW5vdWdoIHRvIHJlZmVyIHRvIHRoYXQuDQpb
SUpdIE5vIGNsb2NrIGRyaWZ0IGNvbXBlbnNhdGlvbiBpbXBsZW1lbnRlZCB5ZXQuIFdpbGwgaGF2
ZSBhIGxvb2sgaW50byB0aGUgTEVEQkFUIFJGQy4NCg0KPiANCj4gTWlyamENCg0K


From nobody Tue Jul 14 01:51:36 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C011A90B6 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 01:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 39bbFi8qtMh4 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 01:51:33 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BE011A90D4 for <rmcat@ietf.org>; Tue, 14 Jul 2015 01:51:31 -0700 (PDT)
X-AuditID: c1b4fb3a-f79356d000006281-b6-55a4cd91b426
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id ED.CA.25217.19DC4A55; Tue, 14 Jul 2015 10:51:29 +0200 (CEST)
Received: from [150.132.141.43] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.210.2; Tue, 14 Jul 2015 10:51:29 +0200
Message-ID: <55A4CD90.4020905@ericsson.com>
Date: Tue, 14 Jul 2015 10:51:28 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Organization: Ericsson AB
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBLMWRmVeSWpSXmKPExsUyM+Jvje7Es0tCDdpua1kcap3JYrFh9RQW i9U3P7A5MHssWfKTyePQ8yCPYx++sgUwR3HZpKTmZJalFunbJXBlbFnVwViwU67i4eWbLA2M qyS6GDk5JARMJG7sPsoKYYtJXLi3nq2LkYtDSOAoo0TH6v0sIAkhgTWMEssP8oPYvALaEo8a +9hBbBYBVYnta7qZuxg5ONgEbCQeL/YDCfMLSEpsaNjNDGKLCkRJTH28jgWiVVDi5MwnLCDz RQRaGCW2TmwASzALREhcuvaGDWSOMNBB7Xt1IdbmS9y/dQWshFPAT+LWxhZmiHILiZnzzzNC 2PISzVtng50gJKAr0fUybgKj0Cwk22Yh6ZiFpGMBI/MqRtHi1OLi3HQjI73Uoszk4uL8PL28 1JJNjMCgPrjlt9UOxoPPHQ8xCnAwKvHwKuQuCRViTSwrrsw9xCjNwaIkzjtjc16okEB6Yklq dmpqQWpRfFFpTmrxIUYmDk6pBsaGtE8cZj7WVUpNLNOTuhjijnedvTn36n1lvw02n1y2z81W 3BJR2rZiYf9px0OS3T0JNnvY9P5/f/xydfNhhb6VJft9593WKDC4WNo96SDzbokF1T8/uv+r enb17quwOHbJsLsBb6MrNE5KdRuks3X+OG8UHLh71erXgQuv5CxlPPRI+G6Of4kSS3FGoqEW c1FxIgBMdNwbSwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/3DpKuygVVtwJUGCZOahc9Pcc60s>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 08:51:35 -0000

On 2015-07-14 09:24, Ingemar Johansson S wrote:
> Hi Mirja and thanks for your comments, answers inline marked with [IJ]
>

>> And two more high-level/general comments on (the structure of) the
>> document:
>>
>> 1) I think the algorithm is now well understandable with the code and
>> respective explanation (expect the end of section 4.1.3 needs more
>> explanation as just mentioned above). I would still like to propose some
>> restructuring. I think the readability can be much improved by some rather
>> simple restructuring using a model similar as in the LEDBAT draft: First give a
>> high level summarize of all steps that have to be performed ("For each
>> ACK/report the state on the delay and delay trend will be updated. If a loss is
>> detected the congestion window cwnd will be decreased strongly, otherwise
>> there are two operation mode: fast increase and regular operation. In fast
>> increase the goal is to reach a previous target value quickly applying an
>> multiplicative increase scheme, while otherwise a delay traget should be
>> maintained..."). Then give all the pseudo code structured into functions and
>> finally explain each function block in detail in an own paragraph. I already
>> have a good idea how this would look like and if you want to we can sit down
>> at the meeting and do this together.
> [IJ] I'd like to have some kind of sit together, unfortunately I cannot attend the IETF this time, perhaps some remote appear.in session or the like can be arranged in August.
As I will be attending Prague we can sit together and if remote 
participant can join perhaps Ingemar can also join. We can at least 
start the process. And thanks for the this.

>>
>> 2) Having reviewed NADA and Scream now basically in one go, I think the
>> used framework is very similar. If you look at your Figure 1 and the Figure 1 in
>> the NADA draft, I think I'm now basically able to do a 1:1 mapping. However, I
>> think in your picture it is wrong to have multiple video coder/rate
>> controller/queues shown because that indicates that there is only one
>> transmission scheduler and congestion controller for all transmissions, which
>> is not the case. If you remove that part, there is only one difference left
>> between the two images and that is that there is an input from the
>> congestion control to the video rate controller in NADA which you don't have
>> (also see comment 2 above).
> [IJ] We can probably remove the example with multiple videos if it makes things more simple, but fact of the matter is that SCReAM can handle multiple sources.
>
>
> Other than that the mapping would be the
>> following way:
>>
>> NADA
>> ---
>> Reference Rate Calculator    -> Network congestion control
>> Video Target Rate Calculator -> Rate Control
>> Sending Rate Calculator      -> Transmission scheduler
>> Encoder                      -> Video Encoder
>> Rate Shaping Buffer          -> Queue RTP packets
>>
>> I think it would be super helpful to use a common terminology here for
>> everybody to better understand similarities and differences.
> [IJ] Agree, if we can come up with some common terms, so much the better
>
This (and the previous comment from Mirja and Ingemar on similarity 
between NADA and SCReAM) tell that common terminologies should be used 
in the different candidate drafts for ease of understanding if the terms 
are meaning the same things. We had a plan to have a framework document 
in RMCAT. Will that help?

-- 
Zahed

==================================================
ANM ZAHEDUZZAMAN SARKER


Ericsson AB
Services, Media and Network Features
LaboratoriegrÃ¤nd 11
97128 LuleÃ¥, Sweden
Phone +46 10 717 37 43
Fax +46 920 996 21
SMS/MMS +46 76 115 37 43
zaheduzzaman.sarker@ericsson.com
www.ericsson.com

==================================================


From nobody Tue Jul 14 05:08:03 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A421F1AC3ED for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 05:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.079
X-Spam-Level: 
X-Spam-Status: No, score=-1.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 v3hwGmhtcKXb for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 05:07:59 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::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 E56291AC3EA for <rmcat@ietf.org>; Tue, 14 Jul 2015 05:07:58 -0700 (PDT)
Received: by igvi1 with SMTP id i1so52500431igv.1 for <rmcat@ietf.org>; Tue, 14 Jul 2015 05:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Qj07yQc1FUOMxvHJ8rtdol3/KVK/2oxqzAldE7XDHdA=; b=jz1/KlopbZ9lDLusXYoz6Fr3QNq6YUhq/vwuCm2ewrZ8k9iDykZhr3RKhAlJ8xNOko HdTvaBbdvQFEQ6yrOTMDpIiOr/sa1cMmyLLKix+PVX9UNMo3/OKOXdDZ4qhF4laagHJr Hh8FDhMuotCNn/QFqvVkCtX8JQ6RGGA7I+9l4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Qj07yQc1FUOMxvHJ8rtdol3/KVK/2oxqzAldE7XDHdA=; b=QsJqgZCeYNMpYPtoyujAqpC8PixWsfBZx75Y6JfFHhRUhpN8z83TJn3PryA661bpPc BF2OpOar+9eBwR/LlRk2Bg76juo1RawHtVeK3jz9V/DWvdwU6wVOt+pyvVDFkLpRW8KB nhjZwywH7rFFSCbZ/X2bHxvA2N4hvwTHZHS8CNzDUU3Xyzmy2+QB0OmEvoYydncaSEiO 9jFFaWgkzeD0wdNMrPvLGcbtwl+ml+NCACUZEIMTMqZIJcAX26pEP/bsYEJ+vUiB5HTA WV6iriYTxGejirrA3Ll2yO93OPBqe80GNNnxBMZqc/dkGsKCR+UZrw2lsZdovbIGwqkF NQwQ==
X-Gm-Message-State: ALoCoQmPHH4OmUkohRCCss5tyBcoD1nUV20E9l6poA1fR+fydjYW8VbWhuxOeFcbvCMzgRX+7QCVhjEc1Q04oeI0tcMHoKJE3xi9VihxKarcXDLWvXntWAU=
X-Received: by 10.107.33.65 with SMTP id h62mr30382058ioh.11.1436875678338; Tue, 14 Jul 2015 05:07:58 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>
In-Reply-To: <55A4CD90.4020905@ericsson.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGmc/6jnjaBhqE3gdH9BjSKecACAIU9jZWAhk0bc+czbKj8A==
Date: Tue, 14 Jul 2015 14:07:56 +0200
Message-ID: <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>,  Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,  =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/Qhv_2NGmpTJ7UIyN57NbLUX71E4>
Cc: rmcat@ietf.org
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 12:08:01 -0000

HI,

>> Other than that the mapping would be the
>>> following way:
>>>
>>> NADA
>>> ---
>>> Reference Rate Calculator    -> Network congestion control
>>> Video Target Rate Calculator -> Rate Control
>>> Sending Rate Calculator      -> Transmission scheduler
>>> Encoder                      -> Video Encoder
>>> Rate Shaping Buffer          -> Queue RTP packets
>>>
>>> I think it would be super helpful to use a common terminology here
>>> for everybody to better understand similarities and differences.
>> [IJ] Agree, if we can come up with some common terms, so much the
>> better
>>
>This (and the previous comment from Mirja and Ingemar on similarity
>between NADA and SCReAM) tell that common terminologies should be used
>in the different candidate drafts for ease of understanding if the terms
>are
>meaning the same things. We had a plan to have a framework document in
>RMCAT. Will that help?
>
[Karen ] Yes I think that can be a good idea, but I am not sure that the
above mapping of terms is right  - or is it  ?.
I very likely can be mistaken, but with screams multiple stream view then I
have thought that the following was the case:

Scream Transmission scheduler is in fact a true transmission scheduler as i=
t
takes packets from the multiple RTP queues and schedule the packets
(following whatever multiple-stream scheduling policy/stream priority
relevant)
for consummation of the global sending rate/the congestion window calculate=
d
and thus transmit the packets on the UDP socket (after which they eventuall=
y
will
go to the NIC for transmission). I further had assumed that pacing
(vis-=C3=A0-vis cwnv) in this design is implemented as part of the transmis=
sion
scheduler and not as part of the RTP queue logic.
This model at least corresponds to SCTP's model for scheduling of the
multiple streams for consummation of CWND and transmission.

BR, Karen

>--
>Zahed
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>ANM ZAHEDUZZAMAN SARKER
>
>
>Ericsson AB
>Services, Media and Network Features
>Laboratoriegr=C3=A4nd 11
>97128 Lule=C3=A5, Sweden
>Phone +46 10 717 37 43
>Fax +46 920 996 21
>SMS/MMS +46 76 115 37 43
>zaheduzzaman.sarker@ericsson.com
>www.ericsson.com
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D


From nobody Tue Jul 14 06:57:40 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E27F31ACD55 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 06:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aON3tLH_cvlf for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 06:57:35 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391C11ACD53 for <rmcat@ietf.org>; Tue, 14 Jul 2015 06:57:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id A403CD930C; Tue, 14 Jul 2015 15:57:33 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 010ambLExxu9; Tue, 14 Jul 2015 15:57:33 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 45F8AD930B; Tue, 14 Jul 2015 15:57:33 +0200 (MEST)
Message-ID: <55A5154C.40402@tik.ee.ethz.ch>
Date: Tue, 14 Jul 2015 15:57:32 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>,  Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com>
In-Reply-To: <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/YqoQ7mt2SDWFo9siTGT-o0N_Mj8>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 13:57:38 -0000

Hi Karen, hi all,

see below.

On 14.07.2015 14:07, Karen Elisabeth Egede Nielsen wrote:
> HI,
>
>>> Other than that the mapping would be the
>>>> following way:
>>>>
>>>> NADA
>>>> ---
>>>> Reference Rate Calculator    -> Network congestion control
>>>> Video Target Rate Calculator -> Rate Control
>>>> Sending Rate Calculator      -> Transmission scheduler
>>>> Encoder                      -> Video Encoder
>>>> Rate Shaping Buffer          -> Queue RTP packets
>>>>
>>>> I think it would be super helpful to use a common terminology here
>>>> for everybody to better understand similarities and differences.
>>> [IJ] Agree, if we can come up with some common terms, so much the
>>> better
>>>
>> This (and the previous comment from Mirja and Ingemar on similarity
>> between NADA and SCReAM) tell that common terminologies should be used
>> in the different candidate drafts for ease of understanding if the terms
>> are
>> meaning the same things. We had a plan to have a framework document in
>> RMCAT. Will that help?
>>
> [Karen ] Yes I think that can be a good idea, but I am not sure that the
> above mapping of terms is right  - or is it  ?.
> I very likely can be mistaken, but with screams multiple stream view then I
> have thought that the following was the case:
>
> Scream Transmission scheduler is in fact a true transmission scheduler as it
> takes packets from the multiple RTP queues and schedule the packets
> (following whatever multiple-stream scheduling policy/stream priority
> relevant)
> for consummation of the global sending rate/the congestion window calculated
> and thus transmit the packets on the UDP socket (after which they eventually
> will
> go to the NIC for transmission). I further had assumed that pacing
> (vis-Ã -vis cwnv) in this design is implemented as part of the transmission
> scheduler and not as part of the RTP queue logic.
> This model at least corresponds to SCTP's model for scheduling of the
> multiple streams for consummation of CWND and transmission.

If I have red the current draft correctly, everything you've described here was 
moved to the appendix and all that is left in the main part is the calculation 
of the actual sending rate. In this case it would map (to NADA). Probably you 
want one image in the main part that is similar to the image in NADA and then 
have another image in the appendix where you show multiple sources and an 
actually transmission scheduler.

Mirja


>
> BR, Karen
>
>> --
>> Zahed
>>
>> ==================================================
>> ANM ZAHEDUZZAMAN SARKER
>>
>>
>> Ericsson AB
>> Services, Media and Network Features
>> LaboratoriegrÃ¤nd 11
>> 97128 LuleÃ¥, Sweden
>> Phone +46 10 717 37 43
>> Fax +46 920 996 21
>> SMS/MMS +46 76 115 37 43
>> zaheduzzaman.sarker@ericsson.com
>> www.ericsson.com
>>
>> ==================================================


From nobody Tue Jul 14 07:18:08 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 637F41ACDB3 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.079
X-Spam-Level: 
X-Spam-Status: No, score=-1.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 1O4pD5CRyZrT for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:18:05 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (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 571301ACDA5 for <rmcat@ietf.org>; Tue, 14 Jul 2015 07:18:05 -0700 (PDT)
Received: by iecuq6 with SMTP id uq6so12199392iec.2 for <rmcat@ietf.org>; Tue, 14 Jul 2015 07:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Ybs5H/vHAy/vbovgZQ1FNnPunQAWcC4kpLLjTxzovs4=; b=rJpsNWat0XRk9vkbuEgvUaECbTU1+NHnDFGPzwa56Lg7p8fjPwNEPMqOEeUQ6uPs+I MCIaU9b/5gAPKNwYtzIVObwUgTnOuDuT2V/u1J084QQpvvXZ9TLmBg3mxdBd4wnlYpuT bTDtGgxbZB72cBxago/5NPtrD5BQVLMaIgsgU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Ybs5H/vHAy/vbovgZQ1FNnPunQAWcC4kpLLjTxzovs4=; b=GmM8BBbDnBHl9/GVEM+hkc8pLz9p9fgE60FO+FQ9+lXLFM7jCym8NvsM/NwTD8zY6N yL+ibYKZh4f6LPaDumuWHYjMNHBpMslBrt+AA9L0jCssXVDpJpw1OZIIOrIRiejPXr2R RAqP9ZLFbssSkfMd1alS6M/XzKT0Zn03TUfv5buq7QVRzc3e+CwslxVeuzNy077Fdy4w p5Vj9tBqNax3dEvJbkQsriO7/PlYchPi4aodUQkYLCfTkFCrmhjjXr9qRPeQH4ZR6EuW 34Q9rbI86evwKdZ4fQN6QY74Py0Pi8YXp5mFOY+GvK0jo8W2mYIkDIgghloW0RXj6GWm tbjA==
X-Gm-Message-State: ALoCoQnkug+fSQz1L2E1dImFSZYO3Nim6ny2MZj+Nq/PMg0+cCqTMNPJiPjvhZ+DEO3DSIB005m5tiYKeVk4qD16fwPCJbhLzlp8EGRZW0MzWKx3lwaCWMg=
X-Received: by 10.50.64.244 with SMTP id r20mr19799017igs.33.1436883484598; Tue, 14 Jul 2015 07:18:04 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <55A5154C.40402@tik.ee.ethz.ch>
In-Reply-To: <55A5154C.40402@tik.ee.ethz.ch>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGmc/6jnjaBhqE3gdH9BjSKecACAIU9jZWAhk0bc8BHrz2aAEqugbVnLuMIQA=
Date: Tue, 14 Jul 2015 16:18:03 +0200
Message-ID: <b89b8ae12b3f759de433e382cd7e7114@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>,  Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/9Z9Aem1Ktr7hL0QvXnTgL8RJnQE>
Cc: rmcat@ietf.org
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 14:18:07 -0000

HI,
>>>
>> [Karen ] Yes I think that can be a good idea, but I am not sure that
>> the above mapping of terms is right  - or is it  ?.
>> I very likely can be mistaken, but with screams multiple stream view
>> then I have thought that the following was the case:
>>
>> Scream Transmission scheduler is in fact a true transmission scheduler
>> as it takes packets from the multiple RTP queues and schedule the
>> packets (following whatever multiple-stream scheduling policy/stream
>> priority
>> relevant)
>> for consummation of the global sending rate/the congestion window
>> calculated and thus transmit the packets on the UDP socket (after
>> which they eventually will go to the NIC for transmission). I further
>> had assumed that pacing (vis-=C3=A0-vis cwnv) in this design is implemen=
ted
>> as part of the transmission scheduler and not as part of the RTP queue
>> logic.
>> This model at least corresponds to SCTP's model for scheduling of the
>> multiple streams for consummation of CWND and transmission.
>
>If I have red the current draft correctly, everything you've described her=
e
>was
>moved to the appendix and all that is left in the main part is the
>calculation of
>the actual sending rate. In this case it would map (to NADA). Probably you
>want one image in the main part that is similar to the image in NADA and
>then
>have another image in the appendix where you show multiple sources and an
>actually transmission scheduler.
>
[Karen ] Yes - I see your point. One note though is that in a multi-stream
model then pacing
logically is instantiated by the multi-stream transmission scheduler which
consumes the packets from the RTP queues
and not logically instantiated in the individual RTP queue objects.
I think that it is important that the terminology (and the definition of th=
e
objects within the framework one can say)
accommodates for a both a single RTP stream and a multi-stream solution - O=
r
?

BR, Karen

>Mirja
>
>
>>
>> BR, Karen
>>
>>> --
>>> Zahed
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>>> ANM ZAHEDUZZAMAN SARKER
>>>
>>>
>>> Ericsson AB
>>> Services, Media and Network Features
>>> Laboratoriegr=C3=A4nd 11
>>> 97128 Lule=C3=A5, Sweden
>>> Phone +46 10 717 37 43
>>> Fax +46 920 996 21
>>> SMS/MMS +46 76 115 37 43
>>> zaheduzzaman.sarker@ericsson.com
>>> www.ericsson.com
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D


From nobody Tue Jul 14 07:24:21 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F811ACDD2 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, J_CHICKENPOX_17=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_47=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Cd30Y6XXLH6d for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:24:15 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A265D1ACCF5 for <rmcat@ietf.org>; Tue, 14 Jul 2015 07:24:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 561CFD9307; Tue, 14 Jul 2015 16:24:13 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id I1KywPyf8QiV; Tue, 14 Jul 2015 16:24:13 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 11788D9305; Tue, 14 Jul 2015 16:24:13 +0200 (MEST)
Message-ID: <55A51B8C.6090303@tik.ee.ethz.ch>
Date: Tue, 14 Jul 2015 16:24:12 +0200
From: =?windows-1252?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Ingemar Johansson <info@ijdata.com>, rmcat@ietf.org,  mirja.kuehlewind@tik.ee.ethz.ch, karen.nielsen@tieto.com,  zaheduzzaman.sarker@ericsson.com, ingemar.s.johansson@ericsson.com
References: <mailman.0.1436549867.21676.rmcat@ietf.org> <55A0124D.9010907@ijdata.com>
In-Reply-To: <55A0124D.9010907@ijdata.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/be03n39gheCVfCSdxRkzKx_dwCc>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 14:24:20 -0000

Hi Ingemar,

see some comments below (I thought I've answered you yesterday already but now 
just realized that I didn't... ).

Mirja

On 10.07.2015 20:43, Ingemar Johansson wrote:
> Hi Mirja and thanks for the comments, answers to at least a few of the comments inline marked [IJ].
> Use my private email temporarly during the summer as I don't expect to pick up my working machine
> on a regular basis and this is anyway a public conversation
>
> /Ingemar
>
>
>     Hi Zahed, hi Ingemar,
>
>     please find my review as an individual contributor below.
>
>     First of all I have a few general question on the algorithm(s):
>
>     1) When calculating cwnd you on the one hand calculate scl_i to
>     basicallyquickly speed up to the previous maximum value cwnd_i and on the
>     other hand tryto maintain a low delay target. Aren't these two conflicting
>     goals? Withouthaving looked at your experimentation results now, I'd expect
>     that you even whenyou are alone on the link induce more than owd_target
>     delay (actually dependingon the maximum buffer size as reflected by cwnd_i),
>     and when competing withother traffic, you'd still cannot reach an equal
>     sharing but will always get alower share. Which is probably okay; however
>     the part that maybe worries my alittle is that the achieved delay and/or
>     achieved sharing probably depends onthe configured maximum buffer size
>     (which might be large)...? Can you comment onthis or provide more detail
>     results on this?2) I would have expected that the video rate controller
>     takes cwnd or the actualsending window as an input parameter. However, your
>     approach seems to have twomore or less independent control loops for the
>     sending rate and the coding rate.That seems quite weird to me (however the
>     reasoning behind the design of thevideo coder is also not really clear to
>     me; see below for further comments onthis). I'd be worried that if those two
>     loops are rather independent that theycould actually make conflicting
>     decision, e.g. video controller increases therate and congestion controller
>     decreases the rate. Also wouldn't it be useful touse the cwnd as an input
>     parameter? Please comment!
>
> [IJ] Actually the purpose of cwnd_i and scl_i is to slow down the increase on
> cwnd and target bitrate when close to the last known max value. This gives a
> chance for the algorithm to avoid a too large delay spike when the path capacity
> of a fixed BW link is reached, at the same time it gives a better opportunity to
> grab free bandwidth reasonably fast.

I understood this but this also means that you are fast(er) when your are far 
away from the target bit rate. So it's both.


> It may be an option to base the video target rate on something like the send
> window, not sure what it would like, you probably need to do something like
> cwnd/rtt. Like it is now there are actually two control loops as you correctly
> observe. Currently I don't see a way around this as the video coder can
> fluctuate quite a lot around the target bitrate. In the long run it is perhaps
> possible (and desirable) to make it one control loop, not sure that it will
> happens. Another thing that speaks in favor of two control loops is that SCReAM
> can congestion control multiple streams, for instance video and audio. This can
> be experimented with in the C++ code.

I didn't say it has to be one control loop but I was wondering if it makes sense 
to two completely independent control loop. I'd have expected that the video 
rate control loop takes the target sending rate as in input parameter.

>
>     And two more high-level/general comments on (the structure of) the document:
>
>     1) I think the algorithm is now well understandable with the code and
>     respectiveexplanation (expect the end of section 4.1.3 needs more
>     explanation as justmentioned above). I would still like to propose some
>     restructuring. I think thereadability can be much improved by some rather
>     simple restructuring using amodel similar as in the LEDBAT draft: First give
>     a high level summarize of allsteps that have to be performed ("For each
>     ACK/report the state on the delay anddelay trend will be updated. If a loss
>     is detected the congestion window cwndwill be decreased strongly, otherwise
>     there are two operation mode: fastincrease and regular operation. In fast
>     increase the goal is to reach a previoustarget value quickly applying an
>     multiplicative increase scheme, while otherwisea delay traget should be
>     maintained..."). Then give all the pseudo codestructured into functions and
>     finally explain each function block in detail inan own paragraph. I already
>     have a good idea how this would look like and if youwant to we can sit down
>     at the meeting and do this together.2) Having reviewed NADA and Scream now
>     basically in one go, I think the usedframework is very similar. If you look
>     at your Figure 1 and the Figure 1 in theNADA draft, I think I'm now
>     basically able to do a 1:1 mapping. However, I thinkin your picture it is
>     wrong to have multiple video coder/rate controller/queuesshown because that
>     indicates that there is only one transmission scheduler andcongestion
>     controller for all transmissions, which is not the case.
>
> [IJ] I'd like to have some kind of sit together, urfortunately I cannot attend
> the IETF this time, perhaps some remote appear.in session or the like can be
> arranged in August.
> We can probably remove the example with multiple videos if it makes things more
> simple, but fact of the matter is that SCReAM can handle multiple sources.
>
>     If youremove that part, there is only one difference left between the two
>     images andthat is that there is an input from the congestion control to the
>     video ratecontroller in NADA which you don't have (also see comment 2
>     above). Other thanthat the mapping would be the following way:
>
>     NADA
>     ---
>     Reference Rate Calculator    -> Network congestion control
>     Video Target Rate Calculator -> Rate Control
>     Sending Rate Calculator      -> Transmission scheduler
>     Encoder                      -> Video Encoder
>     Rate Shaping Buffer          -> Queue RTP packets
>
>     I think it would be super helpful to use a common terminology here for
>     everybodyto better understand similarities and differences.
>
> [IJ] Agree, if we can come up with some common terms, so much the better.
>
>     I guess the same is true forvariable and parameter names if there things
>     that are actually the same. Notethat you in some case already use the same
>     names (I didn't check however if thethings that have the same name actually
>     are the same things...)3) I think it is great to have a section to list all
>     parameters and values.Thanks! However I do have to say I find tables here
>     not the right choice becauseit just stretches the information over more
>     pages than needed and thereforemakes it actually harder to find the right
>     bit. Further there are a fewvariables that are actually parameters and
>     listed wrongly. Two examples I'vefound are: mss and min_cwnd (should be MSS
>     and MIN_CWND which you even writethis way sometimes).
>
> [IJ] I have to blame the use of tables on  my mediocre XML skills, is a list
> better. Will connect the MSS and MIN_CWND error, thansk

Yes, I guess a simple list with the variables names and some explanation would 
do it.
And finding a nice formating in the RFC style is often hard...

>
>     Further for variables I would not indicate the initialvalues here. I'd
>     propose to have a init function instead in the laterdescription where one
>     can see all initial value at once (like in the LEDBATdraft). Further please
>     review if all variables are actually needed. If there areonly temporal and
>     not variables that actually hold state in the pseudo code, Idon't think they
>     need t be listed here.
>
> [IJ] OK, sounds good.
>
>     Further comments following the structure of the document:
>
>     Section 1: I've also made this comment regarding the NADA doc: I guess
>     everyalgorithm doc should refer the requirements doc and to some extend
>     discuss ifand how these requirements have been addressed...Section 1.1: not
>     sure why this section is there; don't see a need to have thisinformation in
>     this document because it doesn't help me understand the algorithmany better.
>
>     Section 3:
>
>     - s/follows packet conservation principles/follows the packet
>     conservationprinciple/- I think think FACK is not the right reference for
>     the packet conservationpriniple, should be "Congestion Avoidance and
>     Control" by Van Jacobsen andMichael J. Karels, SIGCOM'88 (see reference
>     Jac88 of FACK paper).- s/The packet conservation principle is realized by/In
>     Scream, the packetconservation principle is realized by/ -> otherwise it
>     sounds like it's alwaysrealized this way, which is not true.
>
> [IJ] OK
>
>     - Maybe give already a super brief description of what LEDBAT is doing:
>
>     s/in a way similar to LEDBAT [RFC6817]./in a way similar to LEDBAT
>     [RFC6817]by maintaining a given target delay./- This text further say "a few
>     steps to take to make the concept work withconversational media". Maybe
>     already name these steps very briefly here: e.g.taking the delay trend into
>     account and the previous maximum rate to competewith other non-delay based
>     traffic...
>
> [IJ] OK
>
>     Section 3.1
>
>     - You say there are similarities with newcwv but then never mention this
>     again.Can you explain what the similarities are? I've just reviewed newcwv
>     and this isabsolutely not clear to me...- Fast start: May I propose to name
>     this Fast Increase instead (and also alwayswrite this with upper letters).
>     Actually that's the same name I used for TCPSIAD where I also have this
>     mechanism that is kind of similar to Slow Start butcan be resumed later as
>     well. I propose this change (not just because I want myname to be used ;-)
>     but) because having 'start' in the name is confusing to myif you not only
>     use this mechanism to actually start or re-start a transmission.- Also maybe
>     be slightly more concrete here (on a high level) about what faststart is
>     doing: e.g "implements and multiplicative increase to quickly reach
>     themaximum capacity where the increase factor is scaled based on a previous
>     maximumrate (expect at transmission start). Fast start is resumed during a
>     transmissionif the delay trend goes below a certain threshold." Btw. I would
>     also appreciateto introduce a parameter for this threshold and not only say
>     "less than 0.2 for1.0 seconds or more" (see later in section 4.1.2.1).
>
>     - s/with FTP traffic/with bulk traffic/
>
> [IJ] OK :-) , Fast Increase it is !, never felt comfortable with the "fast
> start" term. Do you have a reference to your TCP SIAD work. Would be nice to see
> it as I am looking at ways to recover from failed TCP Cubic HyStarts (related to
> issues we see with HyStart and LTE access)

I gave a presentation on this at the ICCRG meeting in Honolulu:

http://www.ietf.org/proceedings/91/slides/slides-91-iccrg-5.pdf

>
>       Section 3.2.
>
>     - This section says packet pacing is used, however I don't think this is
>     furthermention in the rest of the text... please add something on this... or
>     theremight be a confusion between me and you what pacing means (see below).
>
> [IJ] Packet pacing was broken out to the appendix section A.1, the reason was
> that it did not seem to fit with the earlier concensus that the congetsion
> control should compute a send window.

That actually seems to make sense. I think it's good to have this in the 
appendix for now (sorry I didn't really review the appendix), however, we might 
want to discuss this again at some point. I will try to remember this.

>
>     Section 3.3.
>
>     - Maybe already include the relevant part of figure 1 here because a
>     figurereally helps. Or include the whole figure 1 in section 3 and structure
>     theoverview based on this image.
>
> [IJ] OK, will give it a try
>
>     Section 4.1
>
>     - I guess you can remove the reference to I-D.ietf-rmcat-app-interaction
>     becausewe are working on this draft anymore. However, it was anyway not
>     clear whatexactly you are referencing it for. From my point of view
>     explaining therelationship to other docs (of the same wg) is often done best
>     in the intro.- On Figure 1: As said above I find it confusing that there are
>     multiple videostreams here because that indicates that there is only one
>     congestion controllerand one transmission scheduler for all transmissions.
>     For the same reason Iactually find the name transmission scheduler confusion
>     because a schedulerwould actually be the one who decides which packet to put
>     on the link at whichtime (which often is done on the nic). However your
>     transmission scheduler is'only' calculating the sending window, therefore I
>     call it something likesending rate controller...
>
> [IJ] Perhaps Zahed can explain the ref to the app intercation as I have not been
> involved in that work
>
>     Section 4.1.2.1
>
>     - At the beginning of this section you define some terminology. Maybe put
>     thisin the terminology section instead?- I've also asked this question for
>     NADA: Don't you need synchronized clocks atthe sender and receiver.
>
> [IJ] No. Synchronized clocks are not needed, I am a bit hesitant about the
> impact of clock skew. The "real" code resets the base delay history it the OWD
> takes on inreasonable values, this is not mentioned in the draft however. Will
> fix this

Okay. But then you need to remember the initial value of the first timestamps of 
the sender and the receiver and always compensate the difference. I think this 
should be described somewhere; probably also in the appendix.

>
>     Please further discuss this!- Please also give more details how loss
>     detection is done. I guess that'ssimply indicated in an RTCP report..?
>     Please say which information are exactly used.-
>
> [IJ] The n_loss counter is checked, if it has incremented by one or more steps
> in an RTT it is considered a loss event. Will clarify this
>
>     Please give also some kind of pseudo code on how bytes_newly_acked is
>     updated.That simply helps people to implement things correctly.- As said
>     above I would structure the pseudo code in functions where onefunction would
>     be an init function here. That also helps to avoid implementationerrors.
>
> [IJ] OK
>
>     - Please give more details how the function R() is implemented.
>
> [IJ] It is challenging to write an autocorrelation function in ASCII art but I
> give it a(nother) try :-)
>
>
>
>     - Why is scl_i called this way? What does the i stand for? Maybe take a
>     slightlylonger more meaningful name like scale_increase. This helps the
>     reader toimmediately understand what this is later used for!
>
>     - Why is scl_i limited to 0.2? Should this also a parameter?
>
> [IJ] Good question , would probably be better to just use scl or tmp instead.
> 0.2 is there to avoid that the congestion window growth is is set to zero.

It's clear that the cwnd should not be 0 but why is 0.2 the right value for the 
minimum scaling? Why not 0.1 or 0.3?

>
>     - Please give some reasoning why scl_i is calculated this way! Is this
>     similarto Cubic? If so please refer!-
>
> [IJ] Yes, it is very similar to Cubic, perhaps I have only referred to this in
> emails, will clarify tthis
>
>     I believe the calculation of off_target is only needed if not in fast
>     start.If so please move it!-
>
> [IJ] OK
>
>     cwnd_i is initialized to 1. That seems really weird to me.
>     Does this work wellfor fast start at a beginning of a transmission? I guess
>     the intention is tomake fast start behave like slow start at the beginning
>     of a connection. In thiscase scl_i should be 1. Why don't you just set scl_i
>     to 1 if cwnd_i has not beenset yet...?-
>
> [IJ] Yes, you are right,  could be an alternative,
>
>     gain calculation: owd_trend is always a value between 0 and 1, therefore
>     itcan not be negative, therefore the max() in the gain calculation can be
>     removed:
>
> [IJ] OK
>
>     gain = GAIN*(1.0 + (1.0 - owd_trend/ 0.2))
>
>     - Where is this 0.2 in this gain calculation again coming from. Is there a
>     goodreasoning for this value? Should this be again a parameter? Is this the
>     sameparameter than the previous 0.2?-
>
> [IJ] The 0.2 values (no relation between the to 0.2 values actually) are the
> results of experimentation. They are not that critical however, could have been
> other values like 0.3. Could be good to have them as parameters (actually I got
> the same remark from Daniel Lindström who helped me to get SCReAM into
> OpenWebRTC :-) .

Okay! I think if a parameter was found from experimentation, it should be 
mentioned and it should be explained what the effect will be if this value is 
changed nevertheless.

>
>     I'd move the discussion what the difference to LEDBAT is into section
>     3.1because these point are very general and therefore no algorithm details
>     areneeded to be known and you mention those difference there already without
>     sayingwhat they actually are.- However, you say you don't use
>     ALLOWED_INCREASE but isn'tMAX_BYTES_IN_FLIGHT_HEAD_ROOM effective the same...?-
>
> [IJ] Hmm, will have to look into this..
>
>     The part on flow compensation is rather unclear! Suddenly you have two
>     newparameters owd_norm_mean_sh and owd_norm_var: how are they calculated?
>     When arethey updated? I think there is something missing somewhere. Further
>     where doesthis formula come from? I guess there is some previous working
>     that proposedthis approach? Can you give a reference and further explain why
>     this approach istaken?
>
> [IJ] You beat me to the punch here. This is inspired by the work on shared
> bottleneck detection in RMCAT.  I implemented the variance and skew estimates an
> observed that

...?

>
>     Section 4.1.2.2
>
>     - I'd move the initial part here with the two bullet points into section
>     3.2because this is rather some high level info.- I don't think I would call
>     the proposed approach pacing. Pacing is for me thatif you can send you
>     multiple packet at once (because the send/congestion windowis large enough)
>     that you spread the sending times of each packet over the timeinterval until
>     the next ACK/update is expected.- Further the calculation seems rather
>     complicated. Is this really needed? Canyou further explain in the doc in
>     which case this approach helps which problemand why?!
>
>     Section 4.1.3
>
>     - Why is the estimation interval 200ms (shouldn't this be a parameter as
>     well?)but the RATE_ADJUSTMENT_INTERVAL 100ms? If you only estimate every
>     200ms therewill be no new information after 100ms to adjust something...?-
>     s/ if the congestion control is if fast start or not./ if the
>     congestioncontrol is in fast start or not./- In general, as mention above,
>     there is more explanation needed on the singlesteps of the video rate
>     controller, especially on
>
> [IJ] Probably a mistake, should be 200ms, according to the implementation
>
>        - What is RMAP_UP_TIME actually good for? Why is this 10s?
>
> [IJ] This is actually a mistake, it is replaced by a RAMP_UP_SPEED parameter that indicates
> the max increase of the target rate.
>
>       - Please explain further why increment is calculated the way it is calculated!
>
> [IJ] Will add an explanation
>
>     - Shouldn't the target_bitrate be only increased in steps that the
>     encodercan handle?
>
> [IJ] There are no actual steps that the encoder can handle. One typically just
> set a target rate and the rate control loop in the video encoder tries to adapt
> to it.
>
>        - Please you further explain the last part on rate_rtp_limit!!!
>
> [IJ] Yes, this part probably needs a better explanation, it was added quite
> recently as a remedy to some real-life issues with video coding.
>
>       Section 4.2
>
>     - Here the table is good because there are less values and it actually
>     providesa nice overview!
>
> [IJ] OK
>
>     Section 5.
>
>     - This needs to go in an own draft at some point. Please also
>     comparesimilarities with the information needed by NADA and GCC!
>
> [IJ] Yes,
>
>     Section 7
>     - Actually a conclusion is not needed for an IETF Internet draft...
>
> [IJ] OK, great
>
>       Section 8
>
>     - regarding the clock drift compensation, please see the appendix of the
>     LEDBATRFC. If you've implemented basically the same thing as described
>     there, itprobably enough to refer to that.
>
>     Mirja
>
> [IJ] No clock drift compensation implemented yet. Will have a look into the
> LEDBAT RFC.
>
>
>
>


From nobody Tue Jul 14 07:59:49 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 082BD1ACE8C for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 JxwMoqtWbdT3 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 07:59:45 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E57E1ACE8B for <rmcat@ietf.org>; Tue, 14 Jul 2015 07:59:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 174F4D9307; Tue, 14 Jul 2015 16:59:44 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fSSkNLZfFoZe; Tue, 14 Jul 2015 16:59:43 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id B883BD9305; Tue, 14 Jul 2015 16:59:43 +0200 (MEST)
Message-ID: <55A523DF.5060203@tik.ee.ethz.ch>
Date: Tue, 14 Jul 2015 16:59:43 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>
In-Reply-To: <55A4CD90.4020905@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/UpFBZ1IUDcjVocAtdp2SCyf5_cw>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 14:59:48 -0000

Hi Zahed,

see below.

On 14.07.2015 10:51, Zaheduzzaman Sarker wrote:
>
>
> On 2015-07-14 09:24, Ingemar Johansson S wrote:
>> Hi Mirja and thanks for your comments, answers inline marked with [IJ]
>>
>
>>> And two more high-level/general comments on (the structure of) the
>>> document:
>>>
>>> 1) I think the algorithm is now well understandable with the code and
>>> respective explanation (expect the end of section 4.1.3 needs more
>>> explanation as just mentioned above). I would still like to propose some
>>> restructuring. I think the readability can be much improved by some rather
>>> simple restructuring using a model similar as in the LEDBAT draft: First give a
>>> high level summarize of all steps that have to be performed ("For each
>>> ACK/report the state on the delay and delay trend will be updated. If a loss is
>>> detected the congestion window cwnd will be decreased strongly, otherwise
>>> there are two operation mode: fast increase and regular operation. In fast
>>> increase the goal is to reach a previous target value quickly applying an
>>> multiplicative increase scheme, while otherwise a delay traget should be
>>> maintained..."). Then give all the pseudo code structured into functions and
>>> finally explain each function block in detail in an own paragraph. I already
>>> have a good idea how this would look like and if you want to we can sit down
>>> at the meeting and do this together.
>> [IJ] I'd like to have some kind of sit together, unfortunately I cannot attend the IETF this time, perhaps some remote appear.in session or the like can be arranged in August.
> As I will be attending Prague we can sit together and if remote
> participant can join perhaps Ingemar can also join. We can at least
> start the process. And thanks for the this.

Okay, I think I'll have some time on Tuesday. Let's discuss Sunday, when we are 
going to work on this!

>
>>>
>>> 2) Having reviewed NADA and Scream now basically in one go, I think the
>>> used framework is very similar. If you look at your Figure 1 and the Figure 1 in
>>> the NADA draft, I think I'm now basically able to do a 1:1 mapping. However, I
>>> think in your picture it is wrong to have multiple video coder/rate
>>> controller/queues shown because that indicates that there is only one
>>> transmission scheduler and congestion controller for all transmissions, which
>>> is not the case. If you remove that part, there is only one difference left
>>> between the two images and that is that there is an input from the
>>> congestion control to the video rate controller in NADA which you don't have
>>> (also see comment 2 above).
>> [IJ] We can probably remove the example with multiple videos if it makes things more simple, but fact of the matter is that SCReAM can handle multiple sources.
>>
>>
>> Other than that the mapping would be the
>>> following way:
>>>
>>> NADA
>>> ---
>>> Reference Rate Calculator    -> Network congestion control
>>> Video Target Rate Calculator -> Rate Control
>>> Sending Rate Calculator      -> Transmission scheduler
>>> Encoder                      -> Video Encoder
>>> Rate Shaping Buffer          -> Queue RTP packets
>>>
>>> I think it would be super helpful to use a common terminology here for
>>> everybody to better understand similarities and differences.
>> [IJ] Agree, if we can come up with some common terms, so much the better
>>
> This (and the previous comment from Mirja and Ingemar on similarity
> between NADA and SCReAM) tell that common terminologies should be used
> in the different candidate drafts for ease of understanding if the terms
> are meaning the same things. We had a plan to have a framework document
> in RMCAT. Will that help?


For me personally it would be more important to have the same terminology and 
also the same variable names if things are really exactly the same thing in the 
drafts, than having a framework document. Also, if the drafts 'speak the same 
language', it should be easy to write a framework document.

As a chair I'd actually like to publish the current proposal as experimental 
RFCs as stand-alone documents. While if we end up to actually publish more than 
one scheme as standard track, I think it would be useful to have one framework 
document where we describe all similarities and potentially also discuss when to 
use which scheme... but that's for the working group to decide later on.

Mirja


>


From nobody Tue Jul 14 09:38:55 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89021A879D for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 09:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 0NvPJ__SB8zZ for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 09:38:53 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BA471A877E for <rmcat@ietf.org>; Tue, 14 Jul 2015 09:38:52 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-38-55a53b1aa6bd
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 4C.59.29223.A1B35A55; Tue, 14 Jul 2015 18:38:50 +0200 (CEST)
Received: from [153.88.230.52] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.210.2; Tue, 14 Jul 2015 18:38:49 +0200
Message-ID: <55A53B19.5050000@ericsson.com>
Date: Tue, 14 Jul 2015 18:38:49 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Organization: Ericsson AB
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <55A523DF.5060203@tik.ee.ethz.ch>
In-Reply-To: <55A523DF.5060203@tik.ee.ethz.ch>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUyM+Jvja6U9dJQg6k3NSwOtc5ksdiwegqL xeqbH9gcmD2WLPnJ5HHoeZDHsQ9f2QKYo7hsUlJzMstSi/TtErgyvlyfxFywUafi668ZzA2M O5S7GDk5JARMJNYd7GOCsMUkLtxbz9bFyMUhJHCUUeLlmf+MEM5qRonzexYzdzFycPAKaEu0 Xo0EaWARUJW4driPESTMJmAj8XixH0iYX0BSYkPDbmYQW1QgSmLq43UsIDavgKDEyZlPwGwR AS+JD1NWgo1nFpjBKHH6zicmkDnCQAe179WFWLuRUWLSoedgx3EK6Emc6j/GBmIzC1hIzJx/ nhHClpdo3job7DQhAV2JrpdxExiFZiFZNwtJxywkHQsYmVcxihanFiflphsZ6aUWZSYXF+fn 6eWllmxiBIb1wS2/DXYwvnzueIhRgINRiYdXIXdJqBBrYllxZe4hRmkOFiVx3hmb80KFBNIT S1KzU1MLUovii0pzUosPMTJxcEo1MKYuebfC7bj31afGk3in8W/54zfnUMnp+Q1LVnkVRe9Y xb3ikbHkrwyBbSZTX6y/KDc/2vFiQpJb4aKNrxpETxZcmZOz51Sc9lVLjwVPHQMmJ2cz/HpW wh9eF7TNKe+4Z9apVispGbfKn0tXP6/6ePOp2P0DifwtXoclin9JNJ09eviMyURvvpdKLMUZ iYZazEXFiQA6OB6tTAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/2KB20h6n0AhteGvaM8_EatpfrU8>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 16:38:54 -0000

On 2015-07-14 16:59, Mirja KÃ¼hlewind wrote:
> Hi Zahed,
>
> see below.
>
> On 14.07.2015 10:51, Zaheduzzaman Sarker wrote:
>>
>>
>> On 2015-07-14 09:24, Ingemar Johansson S wrote:
>>> Hi Mirja and thanks for your comments, answers inline marked with [IJ]
>>>
>>
>>>> And two more high-level/general comments on (the structure of) the
>>>> document:
>>>>
>>>> 1) I think the algorithm is now well understandable with the code and
>>>> respective explanation (expect the end of section 4.1.3 needs more
>>>> explanation as just mentioned above). I would still like to propose
>>>> some
>>>> restructuring. I think the readability can be much improved by some
>>>> rather
>>>> simple restructuring using a model similar as in the LEDBAT draft:
>>>> First give a
>>>> high level summarize of all steps that have to be performed ("For each
>>>> ACK/report the state on the delay and delay trend will be updated.
>>>> If a loss is
>>>> detected the congestion window cwnd will be decreased strongly,
>>>> otherwise
>>>> there are two operation mode: fast increase and regular operation.
>>>> In fast
>>>> increase the goal is to reach a previous target value quickly
>>>> applying an
>>>> multiplicative increase scheme, while otherwise a delay traget
>>>> should be
>>>> maintained..."). Then give all the pseudo code structured into
>>>> functions and
>>>> finally explain each function block in detail in an own paragraph. I
>>>> already
>>>> have a good idea how this would look like and if you want to we can
>>>> sit down
>>>> at the meeting and do this together.
>>> [IJ] I'd like to have some kind of sit together, unfortunately I
>>> cannot attend the IETF this time, perhaps some remote appear.in
>>> session or the like can be arranged in August.
>> As I will be attending Prague we can sit together and if remote
>> participant can join perhaps Ingemar can also join. We can at least
>> start the process. And thanks for the this.
>
> Okay, I think I'll have some time on Tuesday. Let's discuss Sunday, when
> we are going to work on this!
Ok.
>
>>
>>>>
>>>> 2) Having reviewed NADA and Scream now basically in one go, I think the
>>>> used framework is very similar. If you look at your Figure 1 and the
>>>> Figure 1 in
>>>> the NADA draft, I think I'm now basically able to do a 1:1 mapping.
>>>> However, I
>>>> think in your picture it is wrong to have multiple video coder/rate
>>>> controller/queues shown because that indicates that there is only one
>>>> transmission scheduler and congestion controller for all
>>>> transmissions, which
>>>> is not the case. If you remove that part, there is only one
>>>> difference left
>>>> between the two images and that is that there is an input from the
>>>> congestion control to the video rate controller in NADA which you
>>>> don't have
>>>> (also see comment 2 above).
>>> [IJ] We can probably remove the example with multiple videos if it
>>> makes things more simple, but fact of the matter is that SCReAM can
>>> handle multiple sources.
>>>
>>>
>>> Other than that the mapping would be the
>>>> following way:
>>>>
>>>> NADA
>>>> ---
>>>> Reference Rate Calculator    -> Network congestion control
>>>> Video Target Rate Calculator -> Rate Control
>>>> Sending Rate Calculator      -> Transmission scheduler
>>>> Encoder                      -> Video Encoder
>>>> Rate Shaping Buffer          -> Queue RTP packets
>>>>
>>>> I think it would be super helpful to use a common terminology here for
>>>> everybody to better understand similarities and differences.
>>> [IJ] Agree, if we can come up with some common terms, so much the better
>>>
>> This (and the previous comment from Mirja and Ingemar on similarity
>> between NADA and SCReAM) tell that common terminologies should be used
>> in the different candidate drafts for ease of understanding if the terms
>> are meaning the same things. We had a plan to have a framework document
>> in RMCAT. Will that help?
>
>
> For me personally it would be more important to have the same
> terminology and also the same variable names if things are really
> exactly the same thing in the drafts, than having a framework document.
> Also, if the drafts 'speak the same language', it should be easy to
> write a framework document.
My point of bringing the framework document is to have a place to
discuss what are the correct/appropriate terminologies to use. I believe 
everyone is comfortable with their own terminologies thus discussions 
are required to change some of them to
streamline the docs . Personally, I dont have issues with changing
the terminologies as long as we agree on the definitions.

>
> As a chair I'd actually like to publish the current proposal as
> experimental RFCs as stand-alone documents. While if we end up to
> actually publish more than one scheme as standard track, I think it
> would be useful to have one framework document where we describe all
> similarities and potentially also discuss when to use which scheme...
> but that's for the working group to decide later on.
>
I agree with this view. Perhaps we can use the wiki to be a place
where we define the terminologies and then if required we can have them 
in a framework document.

BR
-- 
Zahed

==================================================
ANM ZAHEDUZZAMAN SARKER


Ericsson AB
Services, Media and Network Features
LaboratoriegrÃ¤nd 11
97128 LuleÃ¥, Sweden
Phone +46 10 717 37 43
Fax +46 920 996 21
SMS/MMS +46 76 115 37 43
zaheduzzaman.sarker@ericsson.com
www.ericsson.com

==================================================


From nobody Tue Jul 14 12:35:02 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED5C1ACE48 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 12:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.101
X-Spam-Level: 
X-Spam-Status: No, score=-4.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, J_CHICKENPOX_17=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_47=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 bX4GHyY1GRRD for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 12:34:57 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A8161B2B2D for <rmcat@ietf.org>; Tue, 14 Jul 2015 12:34:56 -0700 (PDT)
X-AuditID: c1b4fb25-f79046d000007f53-c9-55a5645e2ca4
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 2C.3F.32595.E5465A55; Tue, 14 Jul 2015 21:34:54 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.120]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0210.002; Tue, 14 Jul 2015 21:34:53 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "rmcat@ietf.org" <rmcat@ietf.org>, "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Thread-Topic: Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQu0BNUvgGEfog+E+ekiHUB7EKeJ3a6XoAgABzrPA=
Date: Tue, 14 Jul 2015 19:34:53 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B3B1E8@ESESSMB205.ericsson.se>
References: <mailman.0.1436549867.21676.rmcat@ietf.org> <55A0124D.9010907@ijdata.com> <55A51B8C.6090303@tik.ee.ethz.ch>
In-Reply-To: <55A51B8C.6090303@tik.ee.ethz.ch>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM+JvjW5cytJQg79rRSwOtc5ksdiwegqL xeqbH9gcmD2WLPnJ5HHoeZDHsQ9f2QKYo7hsUlJzMstSi/TtErgy+o8fZSpYeIyxYvFJnQbG 61MYuxg5OSQETCRW318AZYtJXLi3nq2LkYtDSOAoo8S+OY+ZQBJCAksYJXqWa4HYbAI2EisP fWcEKRIRuMUo8WTRHnaQBLOAlcSX43+Zuxg5OISBpn58LggSFhEwlfh6upMFwraSeHLrPpjN IqAq8fbzb2YQm1fAV6L59AGoXZUSK+5uZgQZwymgJ3HlXTVImFFAVuL+93ssEJvEJW49mc8E cbOAxJI955khbFGJl4//sULYShJrD2+HqteTuDF1ChuErS2xbOFrqLWCEidnPmGZwCg2C8nY WUhaZiFpmYWkZQEjyypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwIg6uOW36g7Gy28cDzEK cDAq8fAq5C4JFWJNLCuuzD3EKM3BoiTOO2NzXqiQQHpiSWp2ampBalF8UWlOavEhRiYOTqkG RldH/yUdd9efnDvnM7/A9/PdBifDfNweCZvW3p94aLbq7mWb8p2uBp3ZkcfNxPLI5om4xNpM YKQ9SLu3R9vaRfyRhGWms+TCpWqftld0XC//apSbsn/aGYXaJD+vn+u03offuOx1Vr9F79d9 iS/7rLd+LHCp1l7U2tmxrtT2a5XZo1OhGwJYlFiKMxINtZiLihMBU+19d4kCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/roDsvl6DSmd5NBfo554bFlyqn70>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 19:35:02 -0000

Hi
A few answers below

/Ingemar=20

> -----Original Message-----
> From: Mirja K=FChlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
> Sent: den 14 juli 2015 16:24
> To: Ingemar Johansson; rmcat@ietf.org; mirja.kuehlewind@tik.ee.ethz.ch;
> Karen E. E. Nielsen; Zaheduzzaman Sarker; Ingemar Johansson S
> Subject: Re: Review of draft-ietf-rmcat-scream-cc-01
>=20
> Hi Ingemar,
>=20
> see some comments below (I thought I've answered you yesterday already
> but now just realized that I didn't... ).
>=20
> Mirja
>=20
> On 10.07.2015 20:43, Ingemar Johansson wrote:
> > Hi Mirja and thanks for the comments, answers to at least a few of the
> comments inline marked [IJ].
> > Use my private email temporarly during the summer as I don't expect to
> > pick up my working machine on a regular basis and this is anyway a
> > public conversation
> >
> > /Ingemar
> >
> >
> >     Hi Zahed, hi Ingemar,
> >
> >     please find my review as an individual contributor below.
> >
> >     First of all I have a few general question on the algorithm(s):
> >
> >     1) When calculating cwnd you on the one hand calculate scl_i to
> >     basicallyquickly speed up to the previous maximum value cwnd_i and =
on
> the
> >     other hand tryto maintain a low delay target. Aren't these two conf=
licting
> >     goals? Withouthaving looked at your experimentation results now, I'=
d
> expect
> >     that you even whenyou are alone on the link induce more than
> owd_target
> >     delay (actually dependingon the maximum buffer size as reflected by
> cwnd_i),
> >     and when competing withother traffic, you'd still cannot reach an e=
qual
> >     sharing but will always get alower share. Which is probably okay;
> however
> >     the part that maybe worries my alittle is that the achieved delay a=
nd/or
> >     achieved sharing probably depends onthe configured maximum buffer
> size
> >     (which might be large)...? Can you comment onthis or provide more
> detail
> >     results on this?2) I would have expected that the video rate contro=
ller
> >     takes cwnd or the actualsending window as an input parameter.
> However, your
> >     approach seems to have twomore or less independent control loops fo=
r
> the
> >     sending rate and the coding rate.That seems quite weird to me (howe=
ver
> the
> >     reasoning behind the design of thevideo coder is also not really cl=
ear to
> >     me; see below for further comments onthis). I'd be worried that if =
those
> two
> >     loops are rather independent that theycould actually make conflicti=
ng
> >     decision, e.g. video controller increases therate and congestion co=
ntroller
> >     decreases the rate. Also wouldn't it be useful touse the cwnd as an=
 input
> >     parameter? Please comment!
> >
> > [IJ] Actually the purpose of cwnd_i and scl_i is to slow down the
> > increase on cwnd and target bitrate when close to the last known max
> > value. This gives a chance for the algorithm to avoid a too large
> > delay spike when the path capacity of a fixed BW link is reached, at
> > the same time it gives a better opportunity to grab free bandwidth
> reasonably fast.
>=20
> I understood this but this also means that you are fast(er) when your are=
 far
> away from the target bit rate. So it's both.
[IJ] Yes, you are right. Similar to Cubic it speeds up the growth beyond th=
e inflection point.


>=20
>=20
> > It may be an option to base the video target rate on something like the
> send
> > window, not sure what it would like, you probably need to do something
> like
> > cwnd/rtt. Like it is now there are actually two control loops as you co=
rrectly
> > observe. Currently I don't see a way around this as the video coder can
> > fluctuate quite a lot around the target bitrate. In the long run it is =
perhaps
> > possible (and desirable) to make it one control loop, not sure that it =
will
> > happens. Another thing that speaks in favor of two control loops is tha=
t
> SCReAM
> > can congestion control multiple streams, for instance video and audio. =
This
> can
> > be experimented with in the C++ code.
>=20
> I didn't say it has to be one control loop but I was wondering if it make=
s sense
> to two completely independent control loop. I'd have expected that the
> video
> rate control loop takes the target sending rate as in input parameter.
[IJ] Could be, I recall that I tried out things like these in the past, nee=
d to look in old code and refresh my memory. My conclusion so far is that t=
he video coder needs to be a bit opportunistic and try to push a (tiny) bit=
 more into the transmission scheduler  than what is actually possible to pu=
sh through the network. This occasionally builds a small RTP queue as the a=
ck clocking prevents too much data in flught. Without that slight overalloc=
ation the network congestion controller will have too little data to send a=
nd eventually this leads to a higher sensitivity to other competing flows a=
nd also problems to grab free capacity.

>=20
> >
> >     And two more high-level/general comments on (the structure of) the
> document:
> >
> >     1) I think the algorithm is now well understandable with the code a=
nd
> >     respectiveexplanation (expect the end of section 4.1.3 needs more
> >     explanation as justmentioned above). I would still like to propose =
some
> >     restructuring. I think thereadability can be much improved by some
> rather
> >     simple restructuring using amodel similar as in the LEDBAT draft: F=
irst give
> >     a high level summarize of allsteps that have to be performed ("For =
each
> >     ACK/report the state on the delay anddelay trend will be updated. I=
f a
> loss
> >     is detected the congestion window cwndwill be decreased strongly,
> otherwise
> >     there are two operation mode: fastincrease and regular operation. I=
n fast
> >     increase the goal is to reach a previoustarget value quickly applyi=
ng an
> >     multiplicative increase scheme, while otherwisea delay traget shoul=
d be
> >     maintained..."). Then give all the pseudo codestructured into funct=
ions
> and
> >     finally explain each function block in detail inan own paragraph. I=
 already
> >     have a good idea how this would look like and if youwant to we can =
sit
> down
> >     at the meeting and do this together.2) Having reviewed NADA and
> Scream now
> >     basically in one go, I think the usedframework is very similar. If =
you look
> >     at your Figure 1 and the Figure 1 in theNADA draft, I think I'm now
> >     basically able to do a 1:1 mapping. However, I thinkin your picture=
 it is
> >     wrong to have multiple video coder/rate controller/queuesshown
> because that
> >     indicates that there is only one transmission scheduler andcongesti=
on
> >     controller for all transmissions, which is not the case.
> >
> > [IJ] I'd like to have some kind of sit together, urfortunately I cannot=
 attend
> > the IETF this time, perhaps some remote appear.in session or the like c=
an
> be
> > arranged in August.
> > We can probably remove the example with multiple videos if it makes
> things more
> > simple, but fact of the matter is that SCReAM can handle multiple sourc=
es.
> >
> >     If youremove that part, there is only one difference left between t=
he
> two
> >     images andthat is that there is an input from the congestion contro=
l to
> the
> >     video ratecontroller in NADA which you don't have (also see comment=
 2
> >     above). Other thanthat the mapping would be the following way:
> >
> >     NADA
> >     ---
> >     Reference Rate Calculator    -> Network congestion control
> >     Video Target Rate Calculator -> Rate Control
> >     Sending Rate Calculator      -> Transmission scheduler
> >     Encoder                      -> Video Encoder
> >     Rate Shaping Buffer          -> Queue RTP packets
> >
> >     I think it would be super helpful to use a common terminology here =
for
> >     everybodyto better understand similarities and differences.
> >
> > [IJ] Agree, if we can come up with some common terms, so much the
> better.
> >
> >     I guess the same is true forvariable and parameter names if there t=
hings
> >     that are actually the same. Notethat you in some case already use t=
he
> same
> >     names (I didn't check however if thethings that have the same name
> actually
> >     are the same things...)3) I think it is great to have a section to =
list all
> >     parameters and values.Thanks! However I do have to say I find table=
s
> here
> >     not the right choice becauseit just stretches the information over =
more
> >     pages than needed and thereforemakes it actually harder to find the
> right
> >     bit. Further there are a fewvariables that are actually parameters =
and
> >     listed wrongly. Two examples I'vefound are: mss and min_cwnd (shoul=
d
> be MSS
> >     and MIN_CWND which you even writethis way sometimes).
> >
> > [IJ] I have to blame the use of tables on  my mediocre XML skills, is a=
 list
> > better. Will connect the MSS and MIN_CWND error, thansk
>=20
> Yes, I guess a simple list with the variables names and some explanation
> would
> do it.
> And finding a nice formating in the RFC style is often hard...
>=20
> >
> >     Further for variables I would not indicate the initialvalues here. =
I'd
> >     propose to have a init function instead in the laterdescription whe=
re one
> >     can see all initial value at once (like in the LEDBATdraft). Furthe=
r please
> >     review if all variables are actually needed. If there areonly tempo=
ral and
> >     not variables that actually hold state in the pseudo code, Idon't t=
hink they
> >     need t be listed here.
> >
> > [IJ] OK, sounds good.
> >
> >     Further comments following the structure of the document:
> >
> >     Section 1: I've also made this comment regarding the NADA doc: I gu=
ess
> >     everyalgorithm doc should refer the requirements doc and to some
> extend
> >     discuss ifand how these requirements have been addressed...Section
> 1.1: not
> >     sure why this section is there; don't see a need to have thisinform=
ation in
> >     this document because it doesn't help me understand the algorithman=
y
> better.
> >
> >     Section 3:
> >
> >     - s/follows packet conservation principles/follows the packet
> >     conservationprinciple/- I think think FACK is not the right referen=
ce for
> >     the packet conservationpriniple, should be "Congestion Avoidance an=
d
> >     Control" by Van Jacobsen andMichael J. Karels, SIGCOM'88 (see
> reference
> >     Jac88 of FACK paper).- s/The packet conservation principle is reali=
zed
> by/In
> >     Scream, the packetconservation principle is realized by/ -> otherwi=
se it
> >     sounds like it's alwaysrealized this way, which is not true.
> >
> > [IJ] OK
> >
> >     - Maybe give already a super brief description of what LEDBAT is do=
ing:
> >
> >     s/in a way similar to LEDBAT [RFC6817]./in a way similar to LEDBAT
> >     [RFC6817]by maintaining a given target delay./- This text further s=
ay "a
> few
> >     steps to take to make the concept work withconversational media".
> Maybe
> >     already name these steps very briefly here: e.g.taking the delay tr=
end
> into
> >     account and the previous maximum rate to competewith other non-
> delay based
> >     traffic...
> >
> > [IJ] OK
> >
> >     Section 3.1
> >
> >     - You say there are similarities with newcwv but then never mention=
 this
> >     again.Can you explain what the similarities are? I've just reviewed
> newcwv
> >     and this isabsolutely not clear to me...- Fast start: May I propose=
 to name
> >     this Fast Increase instead (and also alwayswrite this with upper le=
tters).
> >     Actually that's the same name I used for TCPSIAD where I also have =
this
> >     mechanism that is kind of similar to Slow Start butcan be resumed l=
ater as
> >     well. I propose this change (not just because I want myname to be u=
sed
> ;-)
> >     but) because having 'start' in the name is confusing to myif you no=
t only
> >     use this mechanism to actually start or re-start a transmission.- A=
lso
> maybe
> >     be slightly more concrete here (on a high level) about what faststa=
rt is
> >     doing: e.g "implements and multiplicative increase to quickly reach
> >     themaximum capacity where the increase factor is scaled based on a
> previous
> >     maximumrate (expect at transmission start). Fast start is resumed d=
uring
> a
> >     transmissionif the delay trend goes below a certain threshold." Btw=
. I
> would
> >     also appreciateto introduce a parameter for this threshold and not =
only
> say
> >     "less than 0.2 for1.0 seconds or more" (see later in section 4.1.2.=
1).
> >
> >     - s/with FTP traffic/with bulk traffic/
> >
> > [IJ] OK :-) , Fast Increase it is !, never felt comfortable with the "f=
ast
> > start" term. Do you have a reference to your TCP SIAD work. Would be ni=
ce
> to see
> > it as I am looking at ways to recover from failed TCP Cubic HyStarts (r=
elated
> to
> > issues we see with HyStart and LTE access)
>=20
> I gave a presentation on this at the ICCRG meeting in Honolulu:
>=20
> http://www.ietf.org/proceedings/91/slides/slides-91-iccrg-5.pdf
[IJ] Thanks, seems like this one fell below my radar coverage, it has its d=
ownsides not being able to participate at the meetings ...


>=20
> >
> >       Section 3.2.
> >
> >     - This section says packet pacing is used, however I don't think th=
is is
> >     furthermention in the rest of the text... please add something on t=
his...
> or
> >     theremight be a confusion between me and you what pacing means (see
> below).
> >
> > [IJ] Packet pacing was broken out to the appendix section A.1, the reas=
on
> was
> > that it did not seem to fit with the earlier concensus that the congets=
ion
> > control should compute a send window.
>=20
> That actually seems to make sense. I think it's good to have this in the
> appendix for now (sorry I didn't really review the appendix), however, we
> might
> want to discuss this again at some point. I will try to remember this.
>=20
> >
> >     Section 3.3.
> >
> >     - Maybe already include the relevant part of figure 1 here because =
a
> >     figurereally helps. Or include the whole figure 1 in section 3 and =
structure
> >     theoverview based on this image.
> >
> > [IJ] OK, will give it a try
> >
> >     Section 4.1
> >
> >     - I guess you can remove the reference to I-D.ietf-rmcat-app-intera=
ction
> >     becausewe are working on this draft anymore. However, it was anyway
> not
> >     clear whatexactly you are referencing it for. From my point of view
> >     explaining therelationship to other docs (of the same wg) is often =
done
> best
> >     in the intro.- On Figure 1: As said above I find it confusing that =
there are
> >     multiple videostreams here because that indicates that there is onl=
y one
> >     congestion controllerand one transmission scheduler for all
> transmissions.
> >     For the same reason Iactually find the name transmission scheduler
> confusion
> >     because a schedulerwould actually be the one who decides which pack=
et
> to put
> >     on the link at whichtime (which often is done on the nic). However =
your
> >     transmission scheduler is'only' calculating the sending window, the=
refore
> I
> >     call it something likesending rate controller...
> >
> > [IJ] Perhaps Zahed can explain the ref to the app intercation as I have=
 not
> been
> > involved in that work
> >
> >     Section 4.1.2.1
> >
> >     - At the beginning of this section you define some terminology. May=
be
> put
> >     thisin the terminology section instead?- I've also asked this quest=
ion for
> >     NADA: Don't you need synchronized clocks atthe sender and receiver.
> >
> > [IJ] No. Synchronized clocks are not needed, I am a bit hesitant about =
the
> > impact of clock skew. The "real" code resets the base delay history it =
the
> OWD
> > takes on inreasonable values, this is not mentioned in the draft howeve=
r.
> Will
> > fix this
>=20
> Okay. But then you need to remember the initial value of the first
> timestamps of
> the sender and the receiver and always compensate the difference. I think
> this
> should be described somewhere; probably also in the appendix.
>=20
> >
> >     Please further discuss this!- Please also give more details how los=
s
> >     detection is done. I guess that'ssimply indicated in an RTCP report=
..?
> >     Please say which information are exactly used.-
> >
> > [IJ] The n_loss counter is checked, if it has incremented by one or mor=
e
> steps
> > in an RTT it is considered a loss event. Will clarify this
> >
> >     Please give also some kind of pseudo code on how bytes_newly_acked =
is
> >     updated.That simply helps people to implement things correctly.- As=
 said
> >     above I would structure the pseudo code in functions where onefunct=
ion
> would
> >     be an init function here. That also helps to avoid implementationer=
rors.
> >
> > [IJ] OK
> >
> >     - Please give more details how the function R() is implemented.
> >
> > [IJ] It is challenging to write an autocorrelation function in ASCII ar=
t but I
> > give it a(nother) try :-)
> >
> >
> >
> >     - Why is scl_i called this way? What does the i stand for? Maybe ta=
ke a
> >     slightlylonger more meaningful name like scale_increase. This helps=
 the
> >     reader toimmediately understand what this is later used for!
> >
> >     - Why is scl_i limited to 0.2? Should this also a parameter?
> >
> > [IJ] Good question , would probably be better to just use scl or tmp
> instead.
> > 0.2 is there to avoid that the congestion window growth is is set to ze=
ro.
>=20
> It's clear that the cwnd should not be 0 but why is 0.2 the right value f=
or the
> minimum scaling? Why not 0.1 or 0.3?
[IJ] You are right, others may come up with another value. One may actually=
 consider to flip the whole thing and use the time since "congestion epoch"=
 like it is done with Cubic. One would likely get the same look and feel an=
d this may be easier to explain in a draft text due to the similarities wit=
h Cubic ?=20

>=20
> >
> >     - Please give some reasoning why scl_i is calculated this way! Is t=
his
> >     similarto Cubic? If so please refer!-
> >
> > [IJ] Yes, it is very similar to Cubic, perhaps I have only referred to =
this in
> > emails, will clarify tthis
> >
> >     I believe the calculation of off_target is only needed if not in fa=
st
> >     start.If so please move it!-
> >
> > [IJ] OK
> >
> >     cwnd_i is initialized to 1. That seems really weird to me.
> >     Does this work wellfor fast start at a beginning of a transmission?=
 I guess
> >     the intention is tomake fast start behave like slow start at the be=
ginning
> >     of a connection. In thiscase scl_i should be 1. Why don't you just =
set scl_i
> >     to 1 if cwnd_i has not beenset yet...?-
> >
> > [IJ] Yes, you are right,  could be an alternative,
> >
> >     gain calculation: owd_trend is always a value between 0 and 1, ther=
efore
> >     itcan not be negative, therefore the max() in the gain calculation =
can be
> >     removed:
> >
> > [IJ] OK
> >
> >     gain =3D GAIN*(1.0 + (1.0 - owd_trend/ 0.2))
> >
> >     - Where is this 0.2 in this gain calculation again coming from. Is =
there a
> >     goodreasoning for this value? Should this be again a parameter? Is =
this
> the
> >     sameparameter than the previous 0.2?-
> >
> > [IJ] The 0.2 values (no relation between the to 0.2 values actually) ar=
e the
> > results of experimentation. They are not that critical however, could h=
ave
> been
> > other values like 0.3. Could be good to have them as parameters (actual=
ly I
> got
> > the same remark from Daniel Lindstr=F6m who helped me to get SCReAM
> into
> > OpenWebRTC :-) .
>=20
> Okay! I think if a parameter was found from experimentation, it should be
> mentioned and it should be explained what the effect will be if this valu=
e is
> changed nevertheless.
[IJ] OK

>=20
> >
> >     I'd move the discussion what the difference to LEDBAT is into secti=
on
> >     3.1because these point are very general and therefore no algorithm
> details
> >     areneeded to be known and you mention those difference there alread=
y
> without
> >     sayingwhat they actually are.- However, you say you don't use
> >     ALLOWED_INCREASE but isn'tMAX_BYTES_IN_FLIGHT_HEAD_ROOM
> effective the same...?-
> >
> > [IJ] Hmm, will have to look into this..
> >
> >     The part on flow compensation is rather unclear! Suddenly you have =
two
> >     newparameters owd_norm_mean_sh and owd_norm_var: how are they
> calculated?
> >     When arethey updated? I think there is something missing somewhere.
> Further
> >     where doesthis formula come from? I guess there is some previous
> working
> >     that proposedthis approach? Can you give a reference and further
> explain why
> >     this approach istaken?
> >
> > [IJ] You beat me to the punch here. This is inspired by the work on sha=
red
> > bottleneck detection in RMCAT.  I implemented the variance and skew
> estimates an
> > observed that
>=20
> ...?
[IJ] Was too fast with the send button, sorry. Corrected answer is " This i=
s inspired by the work on shared bottleneck detection in RMCAT.  I implemen=
ted the variance and skew estimates an observed that they actually indicate=
 quite well when competing flows enter and still the risk is quite small th=
at it causes self-inflicted congestion. " . I can show a few examples later=
 on to visualize this.

>=20
> >
> >     Section 4.1.2.2
> >
> >     - I'd move the initial part here with the two bullet points into se=
ction
> >     3.2because this is rather some high level info.- I don't think I wo=
uld call
> >     the proposed approach pacing. Pacing is for me thatif you can send =
you
> >     multiple packet at once (because the send/congestion windowis large
> enough)
> >     that you spread the sending times of each packet over the timeinter=
val
> until
> >     the next ACK/update is expected.- Further the calculation seems rat=
her
> >     complicated. Is this really needed? Canyou further explain in the d=
oc in
> >     which case this approach helps which problemand why?!
> >
> >     Section 4.1.3
> >
> >     - Why is the estimation interval 200ms (shouldn't this be a paramet=
er as
> >     well?)but the RATE_ADJUSTMENT_INTERVAL 100ms? If you only
> estimate every
> >     200ms therewill be no new information after 100ms to adjust
> something...?-
> >     s/ if the congestion control is if fast start or not./ if the
> >     congestioncontrol is in fast start or not./- In general, as mention=
 above,
> >     there is more explanation needed on the singlesteps of the video ra=
te
> >     controller, especially on
> >
> > [IJ] Probably a mistake, should be 200ms, according to the implementati=
on
> >
> >        - What is RMAP_UP_TIME actually good for? Why is this 10s?
> >
> > [IJ] This is actually a mistake, it is replaced by a RAMP_UP_SPEED
> parameter that indicates
> > the max increase of the target rate.
> >
> >       - Please explain further why increment is calculated the way it i=
s
> calculated!
> >
> > [IJ] Will add an explanation
> >
> >     - Shouldn't the target_bitrate be only increased in steps that the
> >     encodercan handle?
> >
> > [IJ] There are no actual steps that the encoder can handle. One typical=
ly
> just
> > set a target rate and the rate control loop in the video encoder tries =
to
> adapt
> > to it.
> >
> >        - Please you further explain the last part on rate_rtp_limit!!!
> >
> > [IJ] Yes, this part probably needs a better explanation, it was added q=
uite
> > recently as a remedy to some real-life issues with video coding.
> >
> >       Section 4.2
> >
> >     - Here the table is good because there are less values and it actua=
lly
> >     providesa nice overview!
> >
> > [IJ] OK
> >
> >     Section 5.
> >
> >     - This needs to go in an own draft at some point. Please also
> >     comparesimilarities with the information needed by NADA and GCC!
> >
> > [IJ] Yes,
> >
> >     Section 7
> >     - Actually a conclusion is not needed for an IETF Internet draft...
> >
> > [IJ] OK, great
> >
> >       Section 8
> >
> >     - regarding the clock drift compensation, please see the appendix o=
f the
> >     LEDBATRFC. If you've implemented basically the same thing as descri=
bed
> >     there, itprobably enough to refer to that.
> >
> >     Mirja
> >
> > [IJ] No clock drift compensation implemented yet. Will have a look into=
 the
> > LEDBAT RFC.
> >
> >
> >
> >


From nobody Tue Jul 14 13:15:47 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4121B2C47 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 13:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 il4MoymmIR17 for <rmcat@ietfa.amsl.com>; Tue, 14 Jul 2015 13:15:44 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC51F1B2AD7 for <rmcat@ietf.org>; Tue, 14 Jul 2015 13:15:33 -0700 (PDT)
X-AuditID: c1b4fb3a-f79356d000006281-b5-55a56de349ae
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 3F.88.25217.3ED65A55; Tue, 14 Jul 2015 22:15:31 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.120]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0210.002; Tue, 14 Jul 2015 22:15:31 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>
Thread-Topic: Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcEC
Date: Tue, 14 Jul 2015 20:15:30 +0000
Message-ID: <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>, <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com>
In-Reply-To: <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+Jvje7j3KWhBo9OGlgcap3JYrFh9RQW i9U3P7A5MHssWfKTyePQ8yCPYx++sgUwR3HZpKTmZJalFunbJXBlLD3RylgwS7Li//IjjA2M V0W6GDk5JARMJPbd72SCsMUkLtxbz9bFyMUhJHCUUeLilUWsIAkhgSWMEifX1oLYbAI2EisP fWcEsUUEjCXWNXwGq2EWWM4osW+/KogtDDT0w/zfbBA1phJfT3eyQNhuEudnPgSrZxFQlXi7 bg0ziM0LFP/86y8j3OKbbzeAXcQpYCcxZwbEEYwCshL3v99jgVgmLvF57gOoqwUkluw5zwxh i0q8fPwP6iA9iRtTp7BB2NoSyxa+hlomKHFy5hOWCYyis5CMmoWkZRaSlllIWhYwsqxiFC1O LS7OTTcy0kstykwuLs7P08tLLdnECIydg1t+W+1gPPjc8RCjAAejEg+vQu6SUCHWxLLiytxD jNIcLErivDM254UKCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYIxd8YiHP+dGw6ObziuSOEoc r4nXrykpvPZnQf1CHbXNl7h9fvz6wzvxxDP7g41p08UE7Y8UyHo80HxeYaDA6DdFqbClRveW RmbONXONsC9//Gq8tzIwP5lwwIa7QX3qAruioqmC/RqFb7srr4nPsKpjuvdf/VXNjkfzYp6c 3hd/s0z/h/QZMSWW4oxEQy3mouJEAA5Xby9+AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/_Wy9YynMvdEgjQED72Xm1uJuFnA>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Jul 2015 20:15:46 -0000

Hi Karen
Your interpretation of the SCReAM multistream handling and transmission sch=
eduling is correct. And as such it resembles SCTP (with NDATA) or QUIC (wit=
h the addition of support for unreliable delivery) very much

Ingemar

Sent from Moxier Mail
(http://www.moxier.com)


----- Ursprungligt meddelande -----
Fr=E5n: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Till: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Ingemar Johan=
sson S <ingemar.s.johansson@ericsson.com>, Mirja K=FChlewind <mirja.kuehlew=
ind@tik.ee.ethz.ch>
Kopia: "rmcat@ietf.org" <rmcat@ietf.org>
Skickat: 2015-07-14 14:08
=C4mne: RE: Review of draft-ietf-rmcat-scream-cc-01



HI,

>> Other than that the mapping would be the
>>> following way:
>>>
>>> NADA
>>> ---
>>> Reference Rate Calculator    -> Network congestion control
>>> Video Target Rate Calculator -> Rate Control
>>> Sending Rate Calculator      -> Transmission scheduler
>>> Encoder                      -> Video Encoder
>>> Rate Shaping Buffer          -> Queue RTP packets
>>>
>>> I think it would be super helpful to use a common terminology here
>>> for everybody to better understand similarities and differences.
>> [IJ] Agree, if we can come up with some common terms, so much the
>> better
>>
>This (and the previous comment from Mirja and Ingemar on similarity
>between NADA and SCReAM) tell that common terminologies should be used
>in the different candidate drafts for ease of understanding if the terms
>are
>meaning the same things. We had a plan to have a framework document in
>RMCAT. Will that help?
>
[Karen ] Yes I think that can be a good idea, but I am not sure that the
above mapping of terms is right  - or is it  ?.
I very likely can be mistaken, but with screams multiple stream view then I
have thought that the following was the case:

Scream Transmission scheduler is in fact a true transmission scheduler as i=
t
takes packets from the multiple RTP queues and schedule the packets
(following whatever multiple-stream scheduling policy/stream priority
relevant)
for consummation of the global sending rate/the congestion window calculate=
d
and thus transmit the packets on the UDP socket (after which they eventuall=
y
will
go to the NIC for transmission). I further had assumed that pacing
(vis-=E0-vis cwnv) in this design is implemented as part of the transmissio=
n
scheduler and not as part of the RTP queue logic.
This model at least corresponds to SCTP's model for scheduling of the
multiple streams for consummation of CWND and transmission.

BR, Karen

>--
>Zahed
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>ANM ZAHEDUZZAMAN SARKER
>
>
>Ericsson AB
>Services, Media and Network Features
>Laboratoriegr=E4nd 11
>97128 Lule=E5, Sweden
>Phone +46 10 717 37 43
>Fax +46 920 996 21
>SMS/MMS +46 76 115 37 43
>zaheduzzaman.sarker@ericsson.com
>www.ericsson.com
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D


From nobody Thu Jul 16 05:21:43 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C23541A897B for <rmcat@ietfa.amsl.com>; Thu, 16 Jul 2015 05:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Z26xXLf7zcz7 for <rmcat@ietfa.amsl.com>; Thu, 16 Jul 2015 05:21:41 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E975E1A8977 for <rmcat@ietf.org>; Thu, 16 Jul 2015 05:21:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 102FDD931B; Thu, 16 Jul 2015 14:21:39 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id sesYYylYoPEz; Thu, 16 Jul 2015 14:21:38 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id D6FDCD9319; Thu, 16 Jul 2015 14:21:38 +0200 (MEST)
Message-ID: <55A7A1D2.6070600@tik.ee.ethz.ch>
Date: Thu, 16 Jul 2015 14:21:38 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "rmcat@ietf.org" <rmcat@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/fGQTmuJ8dfyqgi0W4FsZTDX_ADI>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] Please send slides! For both interim and regular meeting!
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 16 Jul 2015 12:21:42 -0000

Hi all,

please send your slides for the INTERIM until tomorrow night

	Friday, July 17, 6pm

and please send your slides for the regular meeting until

	Saturday, July 18, 6pm!

This includes slides we've requested to be included into the chairs' status 
update (Zahed/Varun)!

Thanks!
See you soon!

Karen & Mirja



From nobody Fri Jul 17 08:23:15 2015
Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D21D1A88B9 for <rmcat@ietfa.amsl.com>; Fri, 17 Jul 2015 08:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.312
X-Spam-Level: 
X-Spam-Status: No, score=-14.312 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 c4V-r7JbT88j for <rmcat@ietfa.amsl.com>; Fri, 17 Jul 2015 08:23:10 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AF141A8886 for <rmcat@ietf.org>; Fri, 17 Jul 2015 08:23:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18411; q=dns/txt; s=iport; t=1437146590; x=1438356190; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ePARRxo80GqLGywW73binbTT1Y5zXlBdsz1Xa793JP0=; b=I3kQBo2ztgvuLzaNp8N5g0FAB4cZmYesKlhW263CdDfCz9pzUJN7Rk54 iSJXKQgtM3PDy9McvqyxZHv5VCvcLCwYe7xtHHmD8LEEvcUVyuW58CmUg y3nYnfwXo5ChYMFjG0FAfi5zxHfrJfMUSPs3ibqFdQPxoNnTgyQLCABqr Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQBQDyHKlV/40NJK1agxOBPQbDTwKBRjwQAQEBAQEBAYEKhCQBAQQnRwYVAgEIRjIlAgQBEogu0G4BAQEBBgEBAQEBHYpKgQKEUzqEKwEEhwkFhSmBJoZvAYdOhFCBQ4QZgxCIAIQ2g2EmggoDHIFTbwGBAwQ/gQQBAQE
X-IronPort-AV: E=Sophos;i="5.15,497,1432598400"; d="scan'208";a="12618450"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-4.cisco.com with ESMTP; 17 Jul 2015 15:23:08 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t6HFN8IE013452 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Jul 2015 15:23:08 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.72]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Fri, 17 Jul 2015 10:23:08 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: =?Windows-1252?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "Michael Ramalho (mramalho)" <mramalho@cisco.com>, "Sergio Mena de la Cruz (semena)" <semena@cisco.com>, "charles.ganzhorn@gmail.com" <charles.ganzhorn@gmail.com>, "paulej@packetizer.com" <paulej@packetizer.com>, "stefano.daronco@epfl.ch" <stefano.daronco@epfl.ch>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: Review of draft-ietf-rmcat-nada-00
Thread-Index: AQHQuab7EWE9mEHX5UqrjpQRYL2f2Z3f1acA
Date: Fri, 17 Jul 2015 15:23:07 +0000
Message-ID: <D1CE7C81.234B4%xiaoqzhu@cisco.com>
References: <559D638D.1040307@tik.ee.ethz.ch>
In-Reply-To: <559D638D.1040307@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.89.5.63]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5746B8E24C86494E99333351DD97B7AC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/TGxvY1uc8fNrZRdALO4dWubtawc>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-nada-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 17 Jul 2015 15:23:14 -0000

Hi Mirja,=20

Thanks much for your detailed review on the draft. Your input is very
helpful.=20

Some high-level changes we plan to make on the draft after reading through
your comments:
- will make some structural changes to separate out the core congestion
control algorithm (e.g., accelerated ramp-up, gradual update) from
descriptions on recommended implementations (e.g., rate shaping buffer);
- will group mention of all open issues into one section instead of
spreading them across different parts of the draft;
- will add a table on list of parameters and default values (similar to
Fig. 2 in the updated video-traffic-source draft)
- regarding formulas in sec. 5.1.2: it was derived out of a
network-utility-maximization framework and we weren=B9t sure how much of th=
e
intermediate math should show up in the draft, since this is not a
research paper. Maybe I can add some citations to the theoretical
background of this work for folks who are potentially interested. Also, we
attempted to give some intuitive explanations on that in our previous
presentations. Maybe I can fold some of the text into the draft too.

Some more responses below inline (marked by [XZ]).

Best,
Xiaoqing

On 7/8/15, 12:53 PM, "Mirja K=FChlewind" <mirja.kuehlewind@tik.ee.ethz.ch>
wrote:

>Hi Xiaoqing, hi all,
>
>this is a review as an individual contributor and not as a wg chair.
>
>I think the document is well written but I had some problem to easily
>follow=20
>some of the details. I think this could be easily improved a lot by
>renaming=20
>(nearly all) variables; I'll give further suggestions on this below. My
>main=20
>problem, however, was on understanding the formula(s) in section 5.1.2.
>This is=20
>partly because of the excessive use of variables with not super helpful
>names,=20
>but mostly because there is no reasoning giving why the formula looks the
>way it=20
>looks! As not currently done in the draft, could you maybe explain on the
>mailing list now, how you came up with this formula? What are the
>different=20
>components good for? How did you decided to add all these calculations?
>
>Further there are some parts where a more detailed description is needed
>(see=20
>also further comments below). This document should allow people to
>re-implement=20
>NADA without knowing your code. I think there are a number of details
>missing in=20
>the description and other parts are not specified well enough as probably
>considered as implementation-specific details. However, I think there are
>things=20
>that actually will influence NADA performance if implemented differently
>and=20
>should therefore be further specified as well (at least one default
>approach),=20
>e.g. the filtering of delay values.


[XZ] Yes, we learned about the need for further clarification of
implementation details after exchanging notes with Google colleagues for
their implementation of NADA. I was hoping to learn from their experience
during the Prague meeting, before coming back to revise the draft.
=20
>
>See more detailed comment in the order of the document structure below:
>
>1) This is a rather general comment on the first paragraph in the
>introduction=20
>and may apply to other schemes as well: You mention challenges here.
>However,=20
>you don't refer to the rmcat requirements doc. Maybe you should refer
>this=20
>somewhere and potentially even discuss if and how the requirements have
>been=20
>address, or at least how the challenges you mention here are reflected in
>the=20
>requirements doc.

[XZ]  Will refer to the requirement doc. Good suggestion.


>
>2) I would recommend to rename section 2 to 'Overview' instead of 'System
>Model'=20
>because that is what is actually is; it gives a summary description of
>what NADA=20
>is doing. As this text already introduced a number of variables, I would
>highly=20
>recommend to have Figure 1 already here because I needed to look at the
>Figure=20
>(knowing that there is one) to actually understand the text. Further I
>don't=20
>think the first point mentioning the source media stream is needed as
>this is=20
>also not shown in the figure.

[XZ] Will do.=20

>
>3) Further I would recommend one new, own section that lists all
>variables and=20
>parameters! That would help really a lot!
>Please also note that there is a difference between variables and
>parameters.=20
>Parameters are things that have a predefined value that you set once,
>while=20
>variables change over time. Usually parameter are noted in all upper case
>letters. In your currently description, parameters and variables look the
>same=20
>which makes things super difficult to read. E.g. d_th is a parameter and
>should=20
>be D_TH, or even better DELAY_THRES. And that's the second
>recommendation: I=20
>would recommend use longer, more descriptive names in many case because
>it helps=20
>the reader to follow. Further if you are going to have an own variables
>and=20
>parameter section, please indicate all default values for parameters.


[XZ]  Will add a section on notations.  I=B9m not so sure about denoting
parameters in all upper case and denoting variables in lower case: is that
a convention of IETF drafts? If so will be happy to follow suit.


>
>4) On section 4.1
>- t_r,n is hard to read, use t_{r,n} or t_r_n or even better ts_rec_n
>- I'd also recommend to following variable names:
>   z_n -> owd_n
>   d_n -> qdelay_n
>   d_f -> delay_base or owd_base
>   d_hat_n -> qdelay_n_filter (or what does 'hat' stand for? or don't use
>d_hat_n at all and just have one more formula: d_n >- filter(d_n)...
>- Please describe the estimation of the base delay in more detail because
>I=20
>think that's a case where there can be an influence on performance. E.g.
>in=20
>LEDBAT the minimum of 1-minutes minutes of the last 10 minutes is used.
>- Did you also try a 2-point minimum filter? That's even easier and I'd
>assume=20
>that would be sufficient in most cases? Or what's the reason for the
>5-point=20
>median filter?

[XZ] will describe in further detail on how to estimate base delay, etc.
Have not tried With 2-point minimum filter. Will look into that. The
reason for the 5-pt median filter is that it worked well for outlier
rejection without adding excessive delay.


>- Do the clocks have to be synchronized for this approach? Please discuss
>this=20
>somewhere!

[XZ] Sec. 4.7 covers some of that. Since we use relative OWD, difference
between sender/receiver clocks is cancelled out. However, drift between
the two clocks over time may still affect performance, so we need some
external mechanism to help bound clock drifts.

>
>5) On section 4.2
>- This section introduces a parameter without naming it (500ms). This is
>actually the same 500ms as introduces as delta in equation (2), right?
>Further I=20
>don' think 500ms is a good recommendation here. This value MUST be larger
>than=20
>one RTT and therefore there is a dependency on the RTT. Therefore for my
>point=20
>of view the recommendation should be something like 3*RTT and not a fixed
>value.
>- Please specify more concretely the exponential smoothing filter that is
>used.=20
>Especially which weight is used!?!

[XZ] The time window for packet loss ratio estimation (currently at 500ms)
is independent from the interval where derivative of queuing delay is
calculated.  Why MUST this interval be greater than RTT? Don=B9t yet see th=
e
reasoning ...

[XZ] In general we=B9ll describe more clearly how packet loss ratio should
be estimated.=20


>
>6) I've detected a number of case, where the documents basically says
>something=20
>like 'further work is need here'. I would find it very helpful (also as a
>chair)=20
>to list all these issues in a open issues section. There are three issues
>I've=20
>found so far in section 4.2, 4.7 and 5.1:
>   - Alternative approach to calculate the loss ratio (as e.g. TFRC)
>   - OWD vs. RTT
>   - Choice of start value
>+ of course all discussion on parameters (which would include the
>question if a=20
>certain value is a MUST e.g. because of fairness reason, or if there is
>range to=20
>choose from)

[XZ] Will group all discussion on open issues into one section.

>
>7) Section 4.3
>- I think this section should be a subsection of 4.1 because it's 'just'
>further=20
>steps to get the delay estimate.
>- The formula was super hard to parse for me because there usually should
>be a=20
>large bracket. Maybe make it like this (as a graphic):
>
>                      /  (d_hat_n),                  if d_hat_n < d_th;
>                      |
>                      |       (d_max - d_hat_n)^4
>         d_tilde_n =3D <   d_th --------------------,  if
>d_th<d_hat_n<d_max;
>                      |         (d_max - d_th)^4
>                      |
>                      \   0,                         if d_hat_n > d_max.
>
>- Parameters: d_max -> DELAY_MAX
>               d_th -> DELAY_THRES


[XZ]  I would like to clarify that non-linear warping of delay is not part
of delay estimation, but rather a mechanism for making the RMCAT flow more
robust against competing loss-based flow.  Also this step occurs after
estimation of loss (invoking of delay warping may also depend on detection
of loss, we are still exploring that variant). So keeping it separate will
be more clear.=20

[XZ] Will work to make the equations/parameters/variables more readily
accessible.=20


>
>8) On section 4.4
>- Why is this done on receiver side? Isn't there already some loss
>feedback in=20
>RTCP that could be used on sender side instead of sending a new report?

[XZ] in fact some of the operations can be moved to sender instead of
receiver side. At this stage we don=B9t have a strong preference. I can
mention in the draft the possibility of moving some operations to the
sender instead. =20


>- Does the values of d_M=3D200ms and d_L=3D1s assume that the loss and
>marking=20
>probabilities are configured differently at the network node; lower
>marking=20
>threshold? Don't those values strongly depend on the configuration in the
>network node? Is it important that all competing NADA flows use the same
>value=20
>(for fairness)?


[XZ] The value of d_L and d_M does not depend on configurations at the
network node, but does assume that ECN markings, when available, will show
up first before losses. For fairness, yes, all NADA flows need to go with
the same penalty values.



>- I'm wondering if you really need to aggregated congestion anymore as
>you=20
>already have the scheme in section 4.3...? Wouldn't it be sufficient to
>use the=20
>estimated delay if there is no loss and use the other signals
>differently. E.g.=20
>if there is loss, halve as traditional cc would do?
>- I think tuning these value is also an open issue and an important one!


[XZ]  Yes, we do need the aggregation so that the algorithm will
seamlessly switch to reacting to loss-based congestion when competing
against loss-based flows that drive the queue to full.

>
>9) Section 4.6
>- Can't this part be done at the sender as well and then you don't have
>to=20
>transmit x_n'?
>- Why do you need a feedback interval of 100ms if you only update any
>information every every 500ms?
>- And if 250ms is sufficient, why do you use 100ms?

[XZ] To clarify information is updated on an ongoing basis, just that they
are smoothed out over the past observation window. Will clarify that in
future draft. More frequent feedback gives the sender an opportunity to
react fast in face of sudden congestion.  It=B9s a trade-off between
feedback overhead vs. feedback control loop responsiveness.


>
>10) I'd recommend to move section 4.7 into an own section (7) at the end
>of the=20
>doc because it is not part of the algorithm description but 'only' some
>discussion.

[XZ] Good point. Will merge that to the section on open issues.

>
>11) "The sender initializes the reference rate R_n as R-min by default,
>or to
>a value specified by the upper-layer application."
>-> I think this is a big open issue. I don't think the application should
>specify this value because it could be misused, but the initial rate must
>fit to=20
>the initial coding I guess. So 10 packet/RTT might be to low...? Which
>rate are=20
>you using currently?


[XZ] The sender initializes the reference rate as R_min.  Discussion on
whether the sender can start at an arbitrarily specified rate by the
application belongs to the API/framework document, I think.


>
>12) Section 5.1 say "if the reported queuing delay is close to zero".
>What does=20
>'close to zero' mean? Do you have another threshold here? How did you
>implement=20
>this? Please give a more detailed description here!

[XZ]  Good catch. We can report on the threshold we use in considering
queuing delay as =B3close to zero=B2.


>
>13) Section 5.1.1:
>- "A typical value of T_th is 50ms." Does all NADA flows need to have the
>same=20
>value to be fair? Than this is a MUST value!
>- "The rate R_n is updated as follows:" This does not specify when the
>rate is=20
>updated. On arrival of each report?
>- This implements a multiplicative increase therefore I would denote the
>equation the following way:
>   R_n =3D R_r + alpha * R_r
>   I would also call the increase factor alpha as this is usually used in
>congestion control.
>- I'm not sure if it is right that the increase rate should the large the
>smaller the base delay is. I'd say it should be the other was around.
>Please=20
>provide some reasoning here! Further is delta actually needed here? Or
>please=20
>explain further what the target ACK interval actually is!
>- gamma_0 is also a confusing naming, should be gamma_max or alpha_max as
>suggested above.

[XZ]  All rates are updated upon arrival of feedback report.  Thanks for
catching this and will clarify in draft.  I think we already used alpha
for the exponential smoothing parameter.  Will reconsider all notation
choices.=20

[XZ]  We explained how the increase ratio was derived in our previous
presentation. Again, I need some guidance on how much of that derivation
should show up in the draft=8A
=20

>
>14) Section 5.1.2:
>- As I said, I've been starring at this for at least 15 minutes and could
>not=20
>figure out why you came up with this. This is my main issue. Please
>explain!
>- Isn't delta_s the same than delta? Why don't you use the same parameter
>name?=20
>Again, should be DELTA or DELTA_REPORT.
>
>15) Section 5.2 could be moved into section 2 because it again does not
>describe=20
>the algorithm.

[XZ] Good suggestion. Will do.

>
>16) The equation given in section 5.3 is really complicated where you
>actually=20
>just want to have the current number of bytes in the buffer. I think this
>is=20
>over-specified and would not need a formula. Further the use of the word
>size is=20
>confusing. A buffer size for me is the maximum amount of bytes a buffer
>could=20
>hold. I think you mean the current buffer occupancy (in bytes)...?

[XZ] I think we can remove this one, since it=B9s more of a description of
how the rate shaping buffer evolves than what the algorithm does.  Your
suggestion of describing in text sounds good.

>
>17) Please give values for beta_v and beta_s (as used in your
>implementation).=20
>Further I'm not sure if it is a good idea to adjust both R_v and R_n at
>once.=20
>Wouldn't it be sufficient to only adjust R_v?

[XZ] Will add all default values of parameters to the table in the new
draft.=20

[XZ] We do want to adjust both the outgoing rate to the network (R_s) and
the target rate for the encoder rate control (R_v) since it helps to drain
the local rate shaping buffer faster if the encoder reacts slowly.
 =20
>
>18) One last comment on PCN (see last paragraph section 6): PCN was
>designed for=20
>admission control in one DiffServ domain and not the Internet, therefore
>this is=20
>not applicable here!


[XZ] You are right that we did not use the term PCN in its original
intended context.  Instead we were really talking about an advanced
virtue-queu-based marking scheme that leveraged  the marking capability of
PCN. I=B9ll change the wording here to make it less confusion.

=20
>
>As a general recommendation (what I learn from my own work on congestion
>control), simplification is always a goal even if performance might be
>slightly=20
>worse: a simpler algorithm is easier to understand and therefore easier
>to=20
>evaluate, and people will be more likely to use it and make less
>implementation=20
>errors. So maybe at this stage you might want think about where you
>potentially=20
>could simplify NADA. Because I think up to now you only added stuff to
>make it=20
>work, but maybe there is now also something that could be removed
>instead...?=20
>Not sure if that's possible, just an idea...

[XZ]  I too prefer simplicity whenever possible. The proposed NADA
algorithm is actually simpler than it appears to be from the current
draft. Some additional complexity was added to accommodate loss-based
competing flows. I hope after separating the core congestion control
algorithm from detailed implementation recommendations, this will become
more clear.=20

>
>Find other nits/proposals below:
>
>s/The RTP sender also generates RTP timestamp in outgoing packets./The
>RTP=20
>sender also provides an RTP timestamp within each outgoing packets./
>
>s/it is discounted following a non-linear curve/it is scaled down
>following a=20
>non-linear curve/
>
>s/see Sec. 6.1.1 Accelerated ramp-up/see Sec. 5.1.1 Accelerated ramp-up/
>
>s/R-min/R_min/
>
>s/its rate increase after at least one round-trip time/its rate increase
>after=20
>at minimum one round-trip time/
>
>s/ the rate increase multiplier should decrease with the delay  in the
>feedback=20
>control loop,/ the rate increase multiplier should smaller the larger the
>base=20
>delay in the feedback control loop is,/
>

[XZ] Will keep these in mind for the next revision.  Thanks again for all
detailed comments and suggestions!

>
>Mirja
>


From nobody Sat Jul 18 01:04:45 2015
Return-Path: <harald@alvestrand.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A131ACEDA for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 01:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LZ1YiMnlLzte for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 01:04:41 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 501201ACEDC for <rmcat@ietf.org>; Sat, 18 Jul 2015 01:04:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 810CF7C0E3D for <rmcat@ietf.org>; Sat, 18 Jul 2015 10:04:40 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhU1uLn2hD-2 for <rmcat@ietf.org>; Sat, 18 Jul 2015 10:04:39 +0200 (CEST)
Received: from [IPv6:2001:67c:370:136:e190:20fd:9b5e:945d] (unknown [IPv6:2001:67c:370:136:e190:20fd:9b5e:945d]) by mork.alvestrand.no (Postfix) with ESMTPSA id 4D0EF7C0B00 for <rmcat@ietf.org>; Sat, 18 Jul 2015 10:04:39 +0200 (CEST)
Message-ID: <55AA0896.6060108@alvestrand.no>
Date: Sat, 18 Jul 2015 10:04:38 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: rmcat@ietf.org
References: <mailman.0.1436549867.21676.rmcat@ietf.org> <55A0124D.9010907@ijdata.com> <55A51B8C.6090303@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3B1E8@ESESSMB205.ericsson.se>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B3B1E8@ESESSMB205.ericsson.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/AKvVCjn80eI2ETC_d3UW8cY_5PE>
Subject: [rmcat] Data available for probing bandwidth (Re: Review of draft-ietf-rmcat-scream-cc-01)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 18 Jul 2015 08:04:43 -0000

Picking up on a sub-point in the scream review thread....

On 07/14/2015 09:34 PM, Ingemar Johansson S wrote:
>> I didn't say it has to be one control loop but I was wondering if it makes sense
>> > to two completely independent control loop. I'd have expected that the
>> > video
>> > rate control loop takes the target sending rate as in input parameter.
> [IJ] Could be, I recall that I tried out things like these in the past, need to look in old code and refresh my memory. My conclusion so far is that the video coder needs to be a bit opportunistic and try to push a (tiny) bit more into the transmission scheduler  than what is actually possible to push through the network. This occasionally builds a small RTP queue as the ack clocking prevents too much data in flught. Without that slight overallocation the network congestion controller will have too little data to send and eventually this leads to a higher sensitivity to other competing flows and also problems to grab free capacity.
>
I remember that we've also seen the problem that in order to "find"
extra capacity, one needs to have extra data to send.

In some Google experiments, we've tried with extra padding; in some QUIC
experiments, I know they've considered using extra FEC frames (if
sending "too much" causes loss, we will then have the data even if a
"base" data frame was lost).

We might want to break this out as a separate topic - "what do we send
in order to probe for whether there's more bandwidth available".


-- 
Surveillance is pervasive. Go Dark.


From nobody Sat Jul 18 07:04:39 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A031B2CBB for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 07:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.521
X-Spam-Level: 
X-Spam-Status: No, score=0.521 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 O8bpktUteTnN for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 07:04:36 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 2A3801B2CB9 for <rmcat@ietf.org>; Sat, 18 Jul 2015 07:04:36 -0700 (PDT)
Received: by igbij6 with SMTP id ij6so55364660igb.1 for <rmcat@ietf.org>; Sat, 18 Jul 2015 07:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=klUvJ0hi7TA4q0sd5+NlJg7FLtrD/e2Cs+90ONtikZE=; b=ifp6fH+HaZJ0oF2AmdJCEWqU0wi//KitsG9xjgWlgao/OMn2kwApH/6YcoK5/Cgd88 TSlJMElZvXWbzuxEQM257CCLTyvGl0Yk3zsaqTCfYJx/sOtC1qKvvFsidEGoMQWWziGI Y2a6i1X92VCJKuSktj4K7ulK4RM1zUnuK7IS0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=klUvJ0hi7TA4q0sd5+NlJg7FLtrD/e2Cs+90ONtikZE=; b=DGlGZm77uQmeCgcetNvpHl+h33pmJsJPNurQlOy5rmGkMxGWVXK9qejOn6WzJEnKAE QTZ3cNTJcA/31K2KdUMaCeW6nG8kBnZPve5B/tTerlGFfhyTNO8TYeYqMGcv9qV2176n Hk/U7Z40aC9GevWrA6HHFRhIDCMhRPt9tsE4XOBzsahGngBd7kyow/JFzAGAv/fJWzCm 9d8X8EktYE7zAruB2tnC3nszTkY5Hvw2Mia6dmaXYQfOShkaPgNfIzvxnAU0rjAxqb0v iDXUikWduiXTornHXiqJfpKIuYyfiXUIuxt5SYLpB3A/LTNBBLmIx/ee2jE0jyhF7GdK EBKw==
X-Gm-Message-State: ALoCoQni1dyrwPxYIxa13PVnsHvvPkMuDgq7IcCTaGkzxCru0RR0i40nzNeZOyGYdiQVFx8uH2KReca/GKmGeEBCuzI3Ti4XjtBKdXCE03jACLxTgDtUMwg=
X-Received: by 10.107.156.203 with SMTP id f194mr23534443ioe.164.1437228275598;  Sat, 18 Jul 2015 07:04:35 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdDBYqzp8LtqL1GsSvyOBquFN26zaw==
Date: Sat, 18 Jul 2015 16:04:34 +0200
Message-ID: <183677ac742f85e9a60b42bc12bdcaad@mail.gmail.com>
To: rmcat@ietf.org
Content-Type: multipart/alternative; boundary=001a1140cd00d42539051b26c8cf
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/qOcmEoqUqmDW2sf7R_okD4iqwy8>
Subject: [rmcat] RMCAT INTERIM Room change to BERLIN/BRUSSELS
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 18 Jul 2015 14:04:37 -0000

--001a1140cd00d42539051b26c8cf
Content-Type: text/plain; charset=UTF-8

HI wg,



The Interim meeting Sunday morning 09:00-13:00 HAS BEEN MOVED to room
Berlin/Brussels.



We should have MEETECHO working there for remote participation.



BR, Karen

--001a1140cd00d42539051b26c8cf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div =
class=3D"WordSection1"><p class=3D"MsoNormal"><span lang=3D"DA">HI wg,</spa=
n></p><p class=3D"MsoNormal"><span lang=3D"DA">=C2=A0</span></p><p class=3D=
"MsoNormal">The Interim meeting Sunday morning 09:00-13:00 HAS BEEN MOVED t=
o room Berlin/Brussels.</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"Mso=
Normal">We should have MEETECHO working there for remote participation.</p>=
<p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">BR, Karen</p><p cla=
ss=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal"><b><span style=3D"font-si=
ze:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">=
=C2=A0</span></b></p></div></body></html>

--001a1140cd00d42539051b26c8cf--


From nobody Sat Jul 18 23:09:12 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 093271A007C for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 23:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.52
X-Spam-Level: 
X-Spam-Status: No, score=0.52 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 CWK5U9Bc2S_w for <rmcat@ietfa.amsl.com>; Sat, 18 Jul 2015 23:09:08 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 92CFD1A0058 for <rmcat@ietf.org>; Sat, 18 Jul 2015 23:09:08 -0700 (PDT)
Received: by igbpg9 with SMTP id pg9so19306267igb.0 for <rmcat@ietf.org>; Sat, 18 Jul 2015 23:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=/zedflE5I3MhMvh4fjAPYfBnefKTPH7sfkK8RqDTErc=; b=Vt6pWiTnonugt0PaEUxDNGapZfcA6P13uSsPHZD/T7nP8qNcPNOL0T8VWiEQED7Tt8 ETVMPiChzWh7lsrEh8oP+eXV9aw4kZUuzyzCegijBpyyATcBC16RzIdapNTud3JxmuLJ +y9d6Ziabssxbd577xOiKfIIRPb4l+OTP+MIk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=/zedflE5I3MhMvh4fjAPYfBnefKTPH7sfkK8RqDTErc=; b=IrJ7HbyEX0BCMqzIX09wQ7Dy9VHuCxvSrbaCE9T/OB0ntajWAjBV6/jcLphAdJ0P0e Ocv4LpzIu9Udwkp477kKJnBe4WaZgfymZ7ZXhxYI5GWO/liPejdclSnA+DSfdvn1BajV hgb5qu/faHgIyXvI+CFMEUlxqOrw3ITCOZ/IyrkT+xYHlef2gNFD26erTQ5gSq5GSdVd d3xKYojNZDNFq519w8Pm5m/j4h1cRDiF4Kb+0K0IX2A82r+l4u/+f33y7KAK+Rs4H053 kSavF2hR9dDouJAelDEWZPOXLAtvgVpJG3STgyVka7gcvAOr04x37MexxFPnviZ/WyoD lwZw==
X-Gm-Message-State: ALoCoQnBHonGqq0KFRL3TAGmHUfRmC/4+bujNw7HYpyIiNV9lgnHR/qB93ZJG0j24rtPRPEcJD0YOsMBNvgij2ow0g2avnR4Of+/ePJtgKvoNAw4D4IrCWA=
X-Received: by 10.107.136.160 with SMTP id s32mr28184704ioi.174.1437286147929;  Sat, 18 Jul 2015 23:09:07 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>, <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com>
In-Reply-To: <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGmc/6jnjaBhqE3gdH9BjSKecACAIU9jZWAhk0bc8BHrz2aAKIK+jXnLftacA=
Date: Sun, 19 Jul 2015 08:09:04 +0200
Message-ID: <456f0d239cbead1c87a3d639688f7495@mail.gmail.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/p7RE7z6IP7BONr7JcX8QcQtimuc>
Cc: rmcat@ietf.org, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 06:09:11 -0000

HI Ingemar, Zahed

Reading the coupled congestion control draft and the app-interactions
draft I have come to wonder a
bit about the multi-stream capabilities of scream - or  the in-build
coupled congestion control of  scream, one can say.

The coupled congestion control of welzl-rmcat-couple-cc allows for
priority to be given to different flows managed by
one couple congestion control context (i.e. the flow identified as sharing
the same bottle neck) - and the app-interactions draft asks for the same
possibility
to be provided. The scream coupled cc also allow for such prioritization
to be done in that such can be achieved by scheduling priorities in
between
the multiple RTP streams that one CC context serves (here scream model is
the same model as sctp multi-stream cc follows).
HOWEVER what the  scream model does not directly allow for - as  far as I
can see - is prioritized coupling in between multiple RTP flows that do
not use the same UDP socket/connection tuple -- And then I start wonder if
the stream model is the right one.

Possibly one can see the scream model as introducing one more level in the
coupled cc model - i.e., prioritized coupling in between the flows using
the same UDP socket/UDP tuple is done by means of scream transmission
scheduling priorities and then coupled congestion control following the
welzl model on top of this, when more "advanced" coupling or SBD detection
is desired or relevant in between flows sharing the same bottleneck, but
not using the same UDP socket/UDP tuple.

I suppose that it should be up to implementations how they want to
implement coupled cc and if they want a leveled approach as the one just
described or a more "direct" approach where each RTP flows is handled
individually from a CC perspective and the coupled via coupled cc (wezlz).

On the other hand the one should understand what would be the motivation
for a leveled approach would be - also because it seems to give a more
complex model  - Is it so that such is motivated by - for example: ?

* It is more efficient (overhead or protocol, state, whatever) to manage
CC on "one" multi-stream RTP basis when such is possible -  as scream does
? and therefore the leveled approach has advantages from a general
perspective or possibly it is advantageous in the particular situations
where the default (build-in) shared bottle-neck detection of scream is the
only one relevant ?

I hope that this was somewhat understandable...

Thanks
BR, Karen


>-----Original Message-----
>From: Ingemar Johansson S [mailto:ingemar.s.johansson@ericsson.com]
>Sent: Tuesday, July 14, 2015 10:16 PM
>To: Karen E. E. Nielsen
>Cc: Mirja K=C3=BChlewind; Zaheduzzaman Sarker; rmcat@ietf.org
>Subject: SV: Review of draft-ietf-rmcat-scream-cc-01
>
>Hi Karen
>Your interpretation of the SCReAM multistream handling and transmission
>scheduling is correct. And as such it resembles SCTP (with NDATA) or QUIC
>(with the addition of support for unreliable delivery) very much
>
>Ingemar
>
>Sent from Moxier Mail
>(http://www.moxier.com)
>
>
>----- Ursprungligt meddelande -----
>Fr=C3=A5n: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
>Till: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Ingemar
>Johansson S <ingemar.s.johansson@ericsson.com>, Mirja K=C3=BChlewind
><mirja.kuehlewind@tik.ee.ethz.ch>
>Kopia: "rmcat@ietf.org" <rmcat@ietf.org>
>Skickat: 2015-07-14 14:08
>=C3=84mne: RE: Review of draft-ietf-rmcat-scream-cc-01
>
>
>
>HI,
>
>>> Other than that the mapping would be the
>>>> following way:
>>>>
>>>> NADA
>>>> ---
>>>> Reference Rate Calculator    -> Network congestion control
>>>> Video Target Rate Calculator -> Rate Control
>>>> Sending Rate Calculator      -> Transmission scheduler
>>>> Encoder                      -> Video Encoder
>>>> Rate Shaping Buffer          -> Queue RTP packets
>>>>
>>>> I think it would be super helpful to use a common terminology here
>>>> for everybody to better understand similarities and differences.
>>> [IJ] Agree, if we can come up with some common terms, so much the
>>> better
>>>
>>This (and the previous comment from Mirja and Ingemar on similarity
>>between NADA and SCReAM) tell that common terminologies should be
>used
>>in the different candidate drafts for ease of understanding if the
>>terms are meaning the same things. We had a plan to have a framework
>>document in RMCAT. Will that help?
>>
>[Karen ] Yes I think that can be a good idea, but I am not sure that the
above
>mapping of terms is right  - or is it  ?.
>I very likely can be mistaken, but with screams multiple stream view then
I
>have thought that the following was the case:
>
>Scream Transmission scheduler is in fact a true transmission scheduler as
it
>takes packets from the multiple RTP queues and schedule the packets
>(following whatever multiple-stream scheduling policy/stream priority
>relevant)
>for consummation of the global sending rate/the congestion window
>calculated and thus transmit the packets on the UDP socket (after which
they
>eventually will go to the NIC for transmission). I further had assumed
that
>pacing (vis-=C3=A0-vis cwnv) in this design is implemented as part of the
>transmission scheduler and not as part of the RTP queue logic.
>This model at least corresponds to SCTP's model for scheduling of the
multiple
>streams for consummation of CWND and transmission.
>
>BR, Karen
>
>>--
>>Zahed
>>
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>>ANM ZAHEDUZZAMAN SARKER
>>
>>
>>Ericsson AB
>>Services, Media and Network Features
>>Laboratoriegr=C3=A4nd 11
>>97128 Lule=C3=A5, Sweden
>>Phone +46 10 717 37 43
>>Fax +46 920 996 21
>>SMS/MMS +46 76 115 37 43
>>zaheduzzaman.sarker@ericsson.com
>>www.ericsson.com
>>
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D


From nobody Sun Jul 19 02:44:38 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C22151AC3E6 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 02:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LajuRM2lBzMV for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 02:44:35 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFCFD1AC3D5 for <rmcat@ietf.org>; Sun, 19 Jul 2015 02:44:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 92B06D930A for <rmcat@ietf.org>; Sun, 19 Jul 2015 11:44:33 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id r9oBLARyllbC for <rmcat@ietf.org>; Sun, 19 Jul 2015 11:44:33 +0200 (MEST)
Received: from dhcp-9b54.meeting.ietf.org (dhcp-9b54.meeting.ietf.org [31.133.155.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 5215AD9304 for <rmcat@ietf.org>; Sun, 19 Jul 2015 11:44:33 +0200 (MEST)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <8BD87958-FABC-4C15-A2D3-2F7CA33D487B@tik.ee.ethz.ch>
Date: Sun, 19 Jul 2015 11:44:33 +0200
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/NP6Pr5UQxEONQs7h0CBrwcNEyfk>
Subject: [rmcat] Slides of interim are here
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 09:44:36 -0000

http://www.ietf.org/proceedings/interim/2015/07/19/rmcat/proceedings.html


From nobody Sun Jul 19 06:25:29 2015
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 180521ACEDA for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 06:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 QBIAq8nygAEA for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 06:25:26 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (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 E9A311ACED3 for <rmcat@ietf.org>; Sun, 19 Jul 2015 06:25:25 -0700 (PDT)
Received: by laem6 with SMTP id m6so83630051lae.0 for <rmcat@ietf.org>; Sun, 19 Jul 2015 06:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=PrbireDuVN/R4fq62q2ALwzHCWuS1iuuKK7cfiE3RSA=; b=lOUHyJSkUFHGq1O9JclkbJx08ZqQkQMDzW2Y6KpitnB1dooFCrSKOOMBUTvUJsuE6c yvMbVd75EMEIHKmJzhMJE584Y3WGvLf9QHwPSMBDzWgKlcyIiCk9oV7QlNGETQpc36cK gLHS2kvyXxFHWzEiAMQEwtGAzQuFExinHJ8w5YREl4jW7AHBKVbUMgobYqXGxC1F8r04 80st/eUOK/6kQ9IdNNA3pwPVgtj04Wnekm/3zlAQl5zacKvQH9TkypCODz42Yyz26eEE oMX7eXcqVXyVK9JpxXNndmXF8l/dyjhzb7f9q9cnrATz3pLKqgzdsWdI4aU+9ohvzZ/r febw==
X-Received: by 10.152.203.233 with SMTP id kt9mr20440491lac.99.1437312324386;  Sun, 19 Jul 2015 06:25:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.211.132 with HTTP; Sun, 19 Jul 2015 06:25:05 -0700 (PDT)
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Sun, 19 Jul 2015 15:25:05 +0200
Message-ID: <CAEbPqrxXUpb+51O4V9vL5XiLmLV99XK9bFZfqbbcFwMh93VUHA@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/WKySq4vPpgT8U2qvVOBfx-vFzaQ>
Cc: rmcat WG <rmcat@ietf.org>
Subject: Re: [rmcat] Data available for probing bandwidth (Re: Review of draft-ietf-rmcat-scream-cc-01)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 13:25:28 -0000

On Sat, Jul 18, 2015 at 10:04 AM, Harald Alvestrand
<harald@alvestrand.no> wrote:
>
> Picking up on a sub-point in the scream review thread....
>
> On 07/14/2015 09:34 PM, Ingemar Johansson S wrote:
>>> I didn't say it has to be one control loop but I was wondering if it ma=
kes sense
>>> > to two completely independent control loop. I'd have expected that th=
e
>>> > video
>>> > rate control loop takes the target sending rate as in input parameter=
.
>> [IJ] Could be, I recall that I tried out things like these in the past, =
need to look in old code and refresh my memory. My conclusion so far is tha=
t the video coder needs to be a bit opportunistic and try to push a (tiny) =
bit more into the transmission scheduler  than what is actually possible to=
 push through the network. This occasionally builds a small RTP queue as th=
e ack clocking prevents too much data in flught. Without that slight overal=
location the network congestion controller will have too little data to sen=
d and eventually this leads to a higher sensitivity to other competing flow=
s and also problems to grab free capacity.
>>
> I remember that we've also seen the problem that in order to "find"
> extra capacity, one needs to have extra data to send.
>
> In some Google experiments, we've tried with extra padding; in some QUIC
> experiments, I know they've considered using extra FEC frames (if
> sending "too much" causes loss, we will then have the data even if a
> "base" data frame was lost).

The following is mostly anecdotal: After the QUIC presentation in
Vanouver, November 2013, we went back and confirmed our results from
adaptive FEC.


Recently, Google announced Quick UDP Internet Connections (QUIC) [52]
to replace TLS and TCP from HTTP/2.0, it provides multiplexed in-order
reliable stream transport over UDP. Similar to FBRA, it trades
bandwidth for decrease in latency. QUIC too keeps a running-XOR of
some packets and sends at least 1 FEC packet for every 20 packets.
Their initial experiments show that retransmissions are reduced from
18% to 10% and the FEC produced at most 5% overhead [53].

The full paper at: http://www.netlab.tkk.fi/~varun/nagy2014mmsys.pdf

>
> We might want to break this out as a separate topic - "what do we send
> in order to probe for whether there's more bandwidth available".

This is a good discussion topic, and perhaps others have brought this
up at earlier presentations of adaptive-fec. For example, sending
duplicate redundant packets, or spreading (piggybacking) a large
I-frame across several other frames.

Alternatively, I remember this being also discussed at the netvc BoF,
more in comparison to Opus which uses inband-fec, i.e., the codec
produces 1 FEC packet for every fixed number of RTP packets. And if a
feature like the one in opus would appear in netvc's codec.

Cheers,
Varun




>
>
> --
> Surveillance is pervasive. Go Dark.
>



--=20
http://www.callstats.io


From nobody Sun Jul 19 07:54:35 2015
Return-Path: <gaetano.carlucci@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE221AD352 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 07:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 AHSnt2uAOeBa for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 07:54:31 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (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 27B161AD338 for <rmcat@ietf.org>; Sun, 19 Jul 2015 07:54:31 -0700 (PDT)
Received: by lbbqi7 with SMTP id qi7so2357494lbb.3 for <rmcat@ietf.org>; Sun, 19 Jul 2015 07:54:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Qx+2xQrZ0VjHZGCZKIQ3ykZ2fbWHZNzNXKp4ajl9L4M=; b=GBtyHp6AJ2GieW6nO136tCdEsnEvP5w9fP8dt2ZNgBI0ASdPnnVjOnhEpOeo814Hf+ kk/iHoKyspV0Vgu51wcoEKsxmNVCxP5f1Amg/tKPZd75S9BIl0fJ6Hu2nC+gs83PeHqA yLNzPOs91PKsHhRDDwTsW/n63AFEwU5NP4QcjypzMuBn/DDSQewyW92kwmWMHMEfi7F8 WMU7qPbXMbHhvFva2Vdzgj9NsESMtIb4zFmb2XB9yXqndCXgeW3X9AXgs1nGIF5DfDnf a5h9eUqFbZDaLN2LhRqIs4RyVfvltsXoHMrKBApgKUjd6GXCGcvvfPFnynbca3PRjfWv I8hA==
MIME-Version: 1.0
X-Received: by 10.152.36.102 with SMTP id p6mr23446203laj.19.1437317669550; Sun, 19 Jul 2015 07:54:29 -0700 (PDT)
Received: by 10.25.214.226 with HTTP; Sun, 19 Jul 2015 07:54:29 -0700 (PDT)
Received: by 10.25.214.226 with HTTP; Sun, 19 Jul 2015 07:54:29 -0700 (PDT)
In-Reply-To: <CAAic+YAzHzeQ9HR+X0EjpYSV6PcCPQpuW90-AqM9pppihAL=tA@mail.gmail.com>
References: <CAEbPqrxXUpb+51O4V9vL5XiLmLV99XK9bFZfqbbcFwMh93VUHA@mail.gmail.com> <CAAic+YAzHzeQ9HR+X0EjpYSV6PcCPQpuW90-AqM9pppihAL=tA@mail.gmail.com>
Date: Sun, 19 Jul 2015 16:54:29 +0200
Message-ID: <CAAic+YCJkOJu9odHSag7hscp6r9teaXK2ZUdV5KUAqRZtoch8Q@mail.gmail.com>
From: Gaetano Carlucci <gaetano.carlucci@gmail.com>
To: Varun Singh <vsingh.ietf@gmail.com>, rmcat@ietf.org
Content-Type: multipart/alternative; boundary=089e0158b7a41f803c051b3b99fd
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/Wr-E0VN3Q47kxucChj7H9bsY1Ag>
Subject: Re: [rmcat] Data available for probing bandwidth (Re: Review of draft-ietf-rmcat-scream-cc-01)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 14:54:34 -0000

--089e0158b7a41f803c051b3b99fd
Content-Type: text/plain; charset=UTF-8

Hi,

we have started a preliminary investigation of QUIC here
http://c3lab.poliba.it/images/3/3b/QUIC_SAC15.pdf.

In version 21 FEC is disabled by default.
When it is tured on it sends roughy one FEC packet every two data packets.

cheers,
gaetano.
Il 19/Lug/2015 15:25, "Varun Singh" <vsingh.ietf@gmail.com> ha scritto:

On Sat, Jul 18, 2015 at 10:04 AM, Harald Alvestrand
<harald@alvestrand.no> wrote:
>
> Picking up on a sub-point in the scream review thread....
>
> On 07/14/2015 09:34 PM, Ingemar Johansson S wrote:
>>> I didn't say it has to be one control loop but I was wondering if it
makes sense
>>> > to two completely independent control loop. I'd have expected that the
>>> > video
>>> > rate control loop takes the target sending rate as in input parameter.
>> [IJ] Could be, I recall that I tried out things like these in the past,
need to look in old code and refresh my memory. My conclusion so far is
that the video coder needs to be a bit opportunistic and try to push a
(tiny) bit more into the transmission scheduler  than what is actually
possible to push through the network. This occasionally builds a small RTP
queue as the ack clocking prevents too much data in flught. Without that
slight overallocation the network congestion controller will have too
little data to send and eventually this leads to a higher sensitivity to
other competing flows and also problems to grab free capacity.
>>
> I remember that we've also seen the problem that in order to "find"
> extra capacity, one needs to have extra data to send.
>
> In some Google experiments, we've tried with extra padding; in some QUIC
> experiments, I know they've considered using extra FEC frames (if
> sending "too much" causes loss, we will then have the data even if a
> "base" data frame was lost).

The following is mostly anecdotal: After the QUIC presentation in
Vanouver, November 2013, we went back and confirmed our results from
adaptive FEC.


Recently, Google announced Quick UDP Internet Connections (QUIC) [52]
to replace TLS and TCP from HTTP/2.0, it provides multiplexed in-order
reliable stream transport over UDP. Similar to FBRA, it trades
bandwidth for decrease in latency. QUIC too keeps a running-XOR of
some packets and sends at least 1 FEC packet for every 20 packets.
Their initial experiments show that retransmissions are reduced from
18% to 10% and the FEC produced at most 5% overhead [53].

The full paper at: http://www.netlab.tkk.fi/~varun/nagy2014mmsys.pdf

>
> We might want to break this out as a separate topic - "what do we send
> in order to probe for whether there's more bandwidth available".

This is a good discussion topic, and perhaps others have brought this
up at earlier presentations of adaptive-fec. For example, sending
duplicate redundant packets, or spreading (piggybacking) a large
I-frame across several other frames.

Alternatively, I remember this being also discussed at the netvc BoF,
more in comparison to Opus which uses inband-fec, i.e., the codec
produces 1 FEC packet for every fixed number of RTP packets. And if a
feature like the one in opus would appear in netvc's codec.

Cheers,
Varun




>
>
> --
> Surveillance is pervasive. Go Dark.
>



--
http://www.callstats.io

--089e0158b7a41f803c051b3b99fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi,</p>
<p dir=3D"ltr">we have started a preliminary investigation of QUIC here <a =
href=3D"http://c3lab.poliba.it/images/3/3b/QUIC_SAC15.pdf">http://c3lab.pol=
iba.it/images/3/3b/QUIC_SAC15.pdf</a>.</p>
<p dir=3D"ltr">In version 21 FEC is disabled by default. <br>
When it is tured on it sends roughy one FEC packet every two data packets.<=
/p>
<p dir=3D"ltr">cheers,<br>
gaetano.</p>
<div class=3D"gmail_quote">Il 19/Lug/2015 15:25, &quot;Varun Singh&quot; &l=
t;<a href=3D"mailto:vsingh.ietf@gmail.com">vsingh.ietf@gmail.com</a>&gt; ha=
 scritto:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"qu=
oted-text">On Sat, Jul 18, 2015 at 10:04 AM, Harald Alvestrand<br>
&lt;<a href=3D"mailto:harald@alvestrand.no">harald@alvestrand.no</a>&gt; wr=
ote:<br>
&gt;<br>
&gt; Picking up on a sub-point in the scream review thread....<br>
&gt;<br>
&gt; On 07/14/2015 09:34 PM, Ingemar Johansson S wrote:<br>
&gt;&gt;&gt; I didn&#39;t say it has to be one control loop but I was wonde=
ring if it makes sense<br>
&gt;&gt;&gt; &gt; to two completely independent control loop. I&#39;d have =
expected that the<br>
&gt;&gt;&gt; &gt; video<br>
&gt;&gt;&gt; &gt; rate control loop takes the target sending rate as in inp=
ut parameter.<br>
&gt;&gt; [IJ] Could be, I recall that I tried out things like these in the =
past, need to look in old code and refresh my memory. My conclusion so far =
is that the video coder needs to be a bit opportunistic and try to push a (=
tiny) bit more into the transmission scheduler=C2=A0 than what is actually =
possible to push through the network. This occasionally builds a small RTP =
queue as the ack clocking prevents too much data in flught. Without that sl=
ight overallocation the network congestion controller will have too little =
data to send and eventually this leads to a higher sensitivity to other com=
peting flows and also problems to grab free capacity.<br>
&gt;&gt;<br>
&gt; I remember that we&#39;ve also seen the problem that in order to &quot=
;find&quot;<br>
&gt; extra capacity, one needs to have extra data to send.<br>
&gt;<br>
&gt; In some Google experiments, we&#39;ve tried with extra padding; in som=
e QUIC<br>
&gt; experiments, I know they&#39;ve considered using extra FEC frames (if<=
br>
&gt; sending &quot;too much&quot; causes loss, we will then have the data e=
ven if a<br>
&gt; &quot;base&quot; data frame was lost).<br>
<br>
</div>The following is mostly anecdotal: After the QUIC presentation in<br>
Vanouver, November 2013, we went back and confirmed our results from<br>
adaptive FEC.<br>
<br>
<br>
Recently, Google announced Quick UDP Internet Connections (QUIC) [52]<br>
to replace TLS and TCP from HTTP/2.0, it provides multiplexed in-order<br>
reliable stream transport over UDP. Similar to FBRA, it trades<br>
bandwidth for decrease in latency. QUIC too keeps a running-XOR of<br>
some packets and sends at least 1 FEC packet for every 20 packets.<br>
Their initial experiments show that retransmissions are reduced from<br>
18% to 10% and the FEC produced at most 5% overhead [53].<br>
<br>
The full paper at: <a href=3D"http://www.netlab.tkk.fi/~varun/nagy2014mmsys=
.pdf" rel=3D"noreferrer" target=3D"_blank">http://www.netlab.tkk.fi/~varun/=
nagy2014mmsys.pdf</a><br>
<div class=3D"quoted-text"><br>
&gt;<br>
&gt; We might want to break this out as a separate topic - &quot;what do we=
 send<br>
&gt; in order to probe for whether there&#39;s more bandwidth available&quo=
t;.<br>
<br>
</div>This is a good discussion topic, and perhaps others have brought this=
<br>
up at earlier presentations of adaptive-fec. For example, sending<br>
duplicate redundant packets, or spreading (piggybacking) a large<br>
I-frame across several other frames.<br>
<br>
Alternatively, I remember this being also discussed at the netvc BoF,<br>
more in comparison to Opus which uses inband-fec, i.e., the codec<br>
produces 1 FEC packet for every fixed number of RTP packets. And if a<br>
feature like the one in opus would appear in netvc&#39;s codec.<br>
<br>
Cheers,<br>
Varun<br>
<div class=3D"quoted-text"><br>
<br>
<br>
<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Surveillance is pervasive. Go Dark.<br>
&gt;<br>
<br>
<br>
<br>
--<br>
</div><a href=3D"http://www.callstats.io" rel=3D"noreferrer" target=3D"_bla=
nk">http://www.callstats.io</a><br>
<br>
</blockquote></div>

--089e0158b7a41f803c051b3b99fd--


From nobody Sun Jul 19 11:04:33 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 773531B2B11 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 11:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level: 
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 hHkD23mQwnqQ for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 11:04:28 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 7A45B1B2B0C for <rmcat@ietf.org>; Sun, 19 Jul 2015 11:04:27 -0700 (PDT)
Received: by iggf3 with SMTP id f3so67843681igg.1 for <rmcat@ietf.org>; Sun, 19 Jul 2015 11:04:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=22B/bPMRszEGgJw6MkBLf/2URrJDn+aNv+ZzHFQ5Z4E=; b=xiS+R3QY1DLS9TFuvH6n6tUoq1/n1l4yht+mWdOOJ0sGeWRc9pW9YgW1PgbQn7bJnn 4qw4eff15PvaqagW+awBXhuSNg43+luWTCjN+8X5H6lx1GhLkfyHJXgremVx/GnIz50G 5A8OD6pL2rAgSgkMzFU7W6WV2BBiJDtWq8EuU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=22B/bPMRszEGgJw6MkBLf/2URrJDn+aNv+ZzHFQ5Z4E=; b=Mz4/Cp7qy8S6KDCYXW8eYeQfkRl2SN42Q25HoZmJnWjh4W4zqLuqJZcembyOmp2Jgg wi3X0umPhOnQp6M+ZKEmG26fnZfzPTXQdLh0PteYCiZUMAeC0nWE4NZeKmdmPOOEs2qo e9RjKFNlL0T0SpnRr/O7KPP9vEzm3Qg0OYzrP3Smlu5K2lkSxZ9mAlswYYdT4e8wUJud iUN8SBG1Lh3gtAyBIpyz+XIyfVoaTisC3l0+t2wWBVN62Jv3lo4EXVmkWMExC/qzOk9W eMxl5Gs7Yq27oDstKv9gStABdX5mPpuLk6vQ6dd+qKALbPZjJ7h8v4t6mYEbrIwjOJ4K r+pg==
X-Gm-Message-State: ALoCoQk/wG9LOhkvi3umPQywKVOmGaDn8H91D879/fVOzmsGAzgiSrj4Rt0Ma74QPjFHZ9qzl6HKMAnT9JfJJHZVnJDrtAagw+gVSrr0cSSkNJ7Kch05XNY=
X-Received: by 10.107.136.160 with SMTP id s32mr30878106ioi.174.1437329066996;  Sun, 19 Jul 2015 11:04:26 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdDCTVLB4Wf4ApIxSkG9SB86EGEyuA==
Date: Sun, 19 Jul 2015 20:04:25 +0200
Message-ID: <adf483811175cd873364d6447c504066@mail.gmail.com>
To: rmcat@ietf.org, "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary=001a113ecffe76d4e6051b3e4033
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/vQ5dKp9KY9dwPH3mfOLsC8QfE-o>
Subject: [rmcat] Comments on draft-zanaty-rmcat-cc-codec-interactions-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 18:04:31 -0000

--001a113ecffe76d4e6051b3e4033
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mo,



For what it is worth then please accept the following comments to the draft=
.



General:



I think that the document now only includes the CC-Codec interactions. I
think this complies with what we intended in the wg.



I think that we should divide into MANDATORY and OPTIONAL sections, so that
the

minimal set of features that

a codec developer have to rely on from the CC, and interact with, is
absolutely clear.



Right now the document includes more interactions that what the present
RMCAT CC proposals provides.

Indeed it seems that they only provides the very basic one (and with couple
CC one more).

I think that further work shall narrow down the CC-codec interactions that
we want to have in the document.

While it has value during the progress of the RMCAT CC definition work, to
describe codec-cc  interactions,

that we from a theoretical perspective identify as something that could
make sense for an RMCAT CC to provide, but which are not provided by any

solution (yet?),  then I am not sure that it makes sense to have  these
interactions in there in the end.



Perhaps a  solution could be to put the interaction features, which are not
supported by any of the CC proposals into the appendix and

here describe why one have ended up not supporting each.

I indeed suppose that there will be good reason for  why one can have or
will have to live without.



I think that the introduction is a little too heavy and detailed in content=
.

E.g., I don=E2=80=99t think that the doc necessarily needs to motivate why =
RMCAT CC
is needed nor

does it need to describe what present application do instead of using RMCAT
CC (I think).

Also section 3 and section 4 are a little to detailed to my taste. But on
the other hand, then as long as

no framework document exists, then some context should be given.



Detailed comments:



Abstract:



Suggest to rephrase:



and the components dedicated to congestion control functions --> and the
RMCAT congestion control layer



I assume that FEC is the reason why you use the formulation



the application components that relate
   to congestion control, specifically the media codec control layer,



instead of simply:



the media codec control layer



Section 1:



I am not sure if we really need the historical perspective on CC
implemented (or not) in RTP media applications in this document.

I think that the text is good, but I think that it belongs rather in the
requirements doc or in a framework doc.

I think that one could jump right into the paragraph under the bulleted
list in section 1 or even right into the paragraph starting with .



The RMCAT requirements..





Second last paragraph of Section 1:

In order to meet these requirements, interactions are necessary
   between the application's congestion controller, the RTP layer, media
   codecs, other components, and the underlying UDP/IP network stack.
   This memo attempts to present a conceptual model of the various
   interfaces based on a simplified application decomposition.  This
   memo discusses interactions between the congestion control and codec
   control layer in a typical RTP Application.



I suggest to rephrase to (something like):



In order to meet these requirements, interactions are necessary
   between the application's congestion controller and other
   application components, like the media codecs layer and the
   RTP layer. This memo describes the interactions between the
   RMCAT congestion control layer and the codec
   control layer in a interactive real time media RTP application.

Section 3:



Suggest to rephrase:



understanding and discussion of where congestion
   control functions operate, and how they interface with the other
   components.

to



understanding and discussion of where congestion
   control functions operate, and how they interface with the codec control
layer.





Bullet 2 on Config seems to be too detailed for the purpose of this
document. I suggest to keep only the text until  =E2=80=9CFor example ..



Bullet 4: I suggest to eliminate the text from  =E2=80=9Csuch as REMB
[I-D.alvestrand-rmcat-remb] ..=E2=80=9D and onwards in this bullet.



Bullet 6: Shared state : I don=E2=80=99t think this detail is needed here. =
It is ?
If so then I think that it should just be part of bullet 5 on congestion
control.



Section 5:



The section starts with saying =E2=80=9Cthe necessary..=E2=80=9D. but it se=
ems to describe
both necessary and optional interactions. IF we end up describing optional
interactions then I think we should have two subsections here =E2=80=93 one=
 for the
=E2=80=9Cnecessary=E2=80=9D ones and, one section for the optional ones.



Section 5.2:



Right now what we have here is the priorities in coupled congestion.
Correct ? If so I think that this could be made more concrete.



Section 5.3, 5.4, 5.5, 5.6, 5.8, 5.9:



No RMCAT CC solution seems to support this at present.  Should it be here ?



5.6 has the heading Forward Error Correction, but truly speaks about
sensitivity to loss patterns. Shouldn=E2=80=99t this be the tittle ? (if ke=
pt).



Section 5.7:



This may be provided by the RMCAT CC (judging from the present discussions
in the wg). Should as the other paragraph say

more exactly what the interaction consists of (CC-FEC/encoder).



BR, Karen

--001a113ecffe76d4e6051b3e4033
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1972514046;
	mso-list-type:hybrid;
	mso-list-template-ids:-1834349748 -1201531504 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style></head><body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div =
class=3D"WordSection1"><p class=3D"MsoNormal">Hi Mo,</p><p class=3D"MsoNorm=
al">=C2=A0</p><p class=3D"MsoNormal">For what it is worth then please accep=
t the following comments to the draft.</p><p class=3D"MsoNormal">=C2=A0</p>=
<p class=3D"MsoNormal">General:</p><p class=3D"MsoNormal">=C2=A0</p><p clas=
s=3D"MsoNormal">I think that the document now only includes the CC-Codec in=
teractions. I think this complies with what we intended in the wg.</p><p cl=
ass=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">I think that we should d=
ivide into MANDATORY and OPTIONAL sections, so that the </p><p class=3D"Mso=
Normal">minimal set of features that </p><p class=3D"MsoNormal">a codec dev=
eloper have to rely on from the CC, and interact with, is absolutely clear.=
</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Right now the d=
ocument includes more interactions that what the present RMCAT CC proposals=
 provides.</p><p class=3D"MsoNormal">Indeed it seems that they only provide=
s the very basic one (and with couple CC one more).</p><p class=3D"MsoNorma=
l">I think that further work shall narrow down the CC-codec interactions th=
at we want to have in the document.</p><p class=3D"MsoNormal">While it has =
value during the progress of the RMCAT CC definition work, to describe code=
c-cc =C2=A0interactions,</p><p class=3D"MsoNormal">that we from a theoretic=
al perspective identify as something that could make sense for an RMCAT CC =
to provide, but which are not provided by any</p><p class=3D"MsoNormal">sol=
ution (yet?), =C2=A0then I am not sure that it makes sense to have =C2=A0th=
ese interactions in there in the end.</p><p class=3D"MsoNormal">=C2=A0</p><=
p class=3D"MsoNormal">Perhaps a =C2=A0solution could be to put the interact=
ion features, which are not supported by any of the CC proposals into the a=
ppendix and</p><p class=3D"MsoNormal">here describe why one have ended up n=
ot supporting each. </p><p class=3D"MsoNormal">I indeed suppose that there =
will be good reason for=C2=A0 why one can have or will have to live without=
. </p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">I think that =
the introduction is a little too heavy and detailed in content.</p><p class=
=3D"MsoNormal">E.g., I don=E2=80=99t think that the doc necessarily needs t=
o motivate why RMCAT CC is needed nor</p><p class=3D"MsoNormal">does it nee=
d to describe what present application do instead of using RMCAT CC (I thin=
k).</p><p class=3D"MsoNormal">Also section 3 and section 4 are a little to =
detailed to my taste. But on the other hand, then as long as</p><p class=3D=
"MsoNormal">no framework document exists, then some context should be given=
.</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Detailed comme=
nts:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Abstract:</=
p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Suggest to rephra=
se:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoPlainText"><span sty=
le=3D"font-family:&quot;Courier New&quot;">and the components dedicated to =
congestion control functions --&gt; and the RMCAT congestion control layer<=
/span></p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">I assume =
that FEC is the reason why you use the formulation </p><p class=3D"MsoNorma=
l">=C2=A0</p><p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Cou=
rier New&quot;">the application components that relate<br>=C2=A0=C2=A0 to c=
ongestion control, specifically the media codec control layer,</span></p><p=
 class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">instead of simply:</p=
><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal"><span style=3D"fon=
t-size:10.5pt;font-family:&quot;Courier New&quot;">the media codec control =
layer</span></p><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font=
-family:&quot;Courier New&quot;">=C2=A0</span></p><p class=3D"MsoNormal">Se=
ction 1:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">I am no=
t sure if we really need the historical perspective on CC implemented (or n=
ot) in RTP media applications in this document.</p><p class=3D"MsoNormal">I=
 think that the text is good, but I think that it belongs rather in the req=
uirements doc or in a framework doc.</p><p class=3D"MsoNormal">I think that=
 one could jump right into the paragraph under the bulleted list in section=
 1 or even right into the paragraph starting with . =C2=A0</p><p class=3D"M=
soNormal">=C2=A0</p><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;=
font-family:&quot;Courier New&quot;">The RMCAT requirements..</span></p><p =
class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Couri=
er New&quot;">=C2=A0</span></p><p class=3D"MsoNormal"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;">=C2=A0</span></p><p class=
=3D"MsoNormal">Second last paragraph of Section 1:</p><p class=3D"MsoPlainT=
ext" style=3D"margin-bottom:12.0pt"><span style=3D"font-family:&quot;Courie=
r New&quot;">In order to meet these requirements, interactions are necessar=
y<br>=C2=A0=C2=A0 between the application&#39;s congestion controller, the =
RTP layer, media<br>=C2=A0=C2=A0 codecs, other components, and the underlyi=
ng UDP/IP network stack.<br>=C2=A0=C2=A0 This memo attempts to present a co=
nceptual model of the various<br>=C2=A0=C2=A0 interfaces based on a simplif=
ied application decomposition.=C2=A0 This<br>=C2=A0=C2=A0 memo discusses in=
teractions between the congestion control and codec<br>=C2=A0=C2=A0 control=
 layer in a typical RTP Application.</span></p><p class=3D"MsoNormal">=C2=
=A0</p><p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;color:#222222=
;background:white">I suggest to rephrase to (something like):</span></p><p =
class=3D"MsoNormal"><span style=3D"font-size:11.5pt;color:#222222;backgroun=
d:white">=C2=A0</span></p><p class=3D"MsoPlainText" style=3D"margin-bottom:=
12.0pt"><span style=3D"font-family:&quot;Courier New&quot;">In order to mee=
t these requirements, interactions are necessary<br>=C2=A0=C2=A0 between th=
e application&#39;s congestion controller and other <br>=C2=A0=C2=A0=C2=A0a=
pplication components, like the media codecs layer and the <br>=C2=A0=C2=A0=
=C2=A0RTP layer. This memo describes the interactions between the <br>=C2=
=A0=C2=A0=C2=A0RMCAT congestion control layer and the codec<br>=C2=A0=C2=A0=
 control layer in a interactive real time media RTP application.</span></p>=
<p class=3D"MsoNormal">Section 3:</p><p class=3D"MsoNormal">=C2=A0</p><p cl=
ass=3D"MsoNormal">Suggest to rephrase:</p><p class=3D"MsoNormal">=C2=A0</p>=
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">understanding and discussion of where congestion<br>=C2=A0=C2=A0 control=
 functions operate, and how they interface with the other<br>=C2=A0=C2=A0 c=
omponents.</span></p><p class=3D"MsoPlainText"><span style=3D"font-family:&=
quot;Courier New&quot;">to</span></p><p class=3D"MsoPlainText"><span style=
=3D"font-family:&quot;Courier New&quot;">=C2=A0</span></p><p class=3D"MsoPl=
ainText"><span style=3D"font-family:&quot;Courier New&quot;">understanding =
and discussion of where congestion<br>=C2=A0=C2=A0 control functions operat=
e, and how they interface with the codec control layer.</span></p><p class=
=3D"MsoPlainText">=C2=A0</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"Ms=
oNormal">Bullet 2 on Config seems to be too detailed for the purpose of thi=
s document. I suggest to keep only the text until =C2=A0=E2=80=9CFor exampl=
e .. </p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Bullet 4: =
I suggest to eliminate the text from =C2=A0=E2=80=9C<span style=3D"font-siz=
e:10.5pt;font-family:&quot;Courier New&quot;">such as REMB [I-D.alvestrand-=
rmcat-remb] ..=E2=80=9D </span>and onwards in this bullet.</p><p class=3D"M=
soNormal">=C2=A0</p><p class=3D"MsoNormal">Bullet 6: Shared state : I don=
=E2=80=99t think this detail is needed here. It is ? If so then I think tha=
t it should just be part of bullet 5 on congestion control.</p><p class=3D"=
MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Section 5:</p><p class=3D"MsoNo=
rmal">=C2=A0</p><p class=3D"MsoNormal">The section starts with saying =E2=
=80=9Cthe necessary..=E2=80=9D. but it seems to describe both necessary and=
 optional interactions. IF we end up describing optional interactions then =
I think we should have two subsections here =E2=80=93 one for the =E2=80=9C=
necessary=E2=80=9D ones and, one section for the optional ones.</p><p class=
=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Section 5.2:</p><p class=3D=
"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">Right now what we have here is=
 the priorities in coupled congestion. Correct ? If so I think that this co=
uld be made more concrete.</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"=
MsoNormal">Section 5.3, 5.4, 5.5, 5.6, 5.8, 5.9:</p><p class=3D"MsoNormal">=
=C2=A0</p><p class=3D"MsoNormal">No RMCAT CC solution seems to support this=
 at present.=C2=A0 Should it be here ?</p><p class=3D"MsoNormal">=C2=A0</p>=
<p class=3D"MsoNormal">5.6 has the heading Forward Error Correction, but tr=
uly speaks about sensitivity to loss patterns. Shouldn=E2=80=99t this be th=
e tittle ? (if kept).</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNo=
rmal">Section 5.7:</p><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNorma=
l">This may be provided by the RMCAT CC (judging from the present discussio=
ns in the wg). Should as the other paragraph say </p><p class=3D"MsoNormal"=
>more exactly what the interaction consists of (CC-FEC/encoder).</p><p clas=
s=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal">BR, Karen </p><p class=3D"=
MsoNormal">=C2=A0</p></div></body></html>

--001a113ecffe76d4e6051b3e4033--


From nobody Sun Jul 19 12:44:07 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845AB1B2BED for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 12:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 I4NxjbHQskvd for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 12:44:04 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AE951B2BEB for <rmcat@ietf.org>; Sun, 19 Jul 2015 12:44:04 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-51-55abfe02bdaf
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C1.10.29223.20EFBA55; Sun, 19 Jul 2015 21:44:02 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.7]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0210.002; Sun, 19 Jul 2015 21:44:01 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: Video sequences for emulation tests
Thread-Index: AdDCA1w2Kk90mXvXQlq2XhRN8ptByA==
Date: Sun, 19 Jul 2015 19:44:01 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5ESESSMB307erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+JvjS7Tv9WhBi++yVqsvvmBzYHRY8mS n0wBjFFcNimpOZllqUX6dglcGT8XHGAtuKde0TPrJ3MD4w+lLkZODgkBE4nt66YxQ9hiEhfu rWfrYuTiEBI4yihxbMsOZghnEaPE/dbvrF2MHBxsAjYSjxf7gTSICKhKbOn/wwZiCwvoSPw8 uJcdIm4osef8bSYIW0/i0NnVYDYLUP319jVgNbwCvhJnX30GsxmBFn8/tQashllAXOLWk/lM EAcJSCzZcx7qOFGJl4//sULYShJrD29ngajPl9hzYw7UTEGJkzOfsExgFJqFZNQsJGWzkJRB xPUkbkydwgZha0ssW/iaGcLWlZjx7xALsvgCRvZVjKLFqcVJuelGRnqpRZnJxcX5eXp5qSWb GIExcXDLb4MdjC+fOx5iFOBgVOLhXcCyOlSINbGsuDL3EKM0B4uSOO+MzXmhQgLpiSWp2amp BalF8UWlOanFhxiZODilGhhrZa7t4Oa9v7dfmlX2Fb8sv+ptu+cZDhoejlKrX0hLCnIYNZhc KfPvUAorag7vuGz+a09GR/C8HdveF+4tT7S/0bErdWqZdc7CtxNsyyt5Puro7xaYxKaZ46h3 nFcvYQtT6r5TjPM+CU5cmvUtT0x7l48561rhlJ8Jz1euKAxmceo9qH5SU4mlOCPRUIu5qDgR ADaW0vtqAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/5xJKslu7MdyfbNLz4sq5WcS3kUM>
Subject: [rmcat] Video sequences for emulation tests
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 19:44:06 -0000

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5ESESSMB307erics_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

As RMCAT congestion control algorithms are getting implemented, we will see=
 more test results where real video encoder will be used.
We have seen results for GCC in the emulated network where a video sequence=
 has been used. The evaluation results of SCReAM implementation we will als=
o use some video sequences.

The eval-test (https://tools.ietf.org/html/draft-ietf-rmcat-eval-test-01) d=
raft points to sources of the video sequences to use in the tests but does =
not pick any particular one(s). However, as the contents of the video seque=
nces have impact on the encoder output, I believe it will be better if we c=
an agree on the video sequences to use in the tests. This will make the res=
ults more comparable.

Any comments on that?

BR

Zahed

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ANM ZAHEDUZZAMAN SARKER
Senior Researcher
Services, Media and Network Features

Ericsson
Laboratoriegr=E4nd 11
97128 Lule=E5, Sweden
Phone +46 10 717 37 43
Mobile +46 76 115 37 43
Office +46 76 115 37 43
Fax +46 920 996 21
zaheduzzaman.sarker@ericsson.com
www.ericsson.com<http://www.ericsson.com>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D




--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5ESESSMB307erics_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi,</div>
<div>&nbsp;</div>
<div>As RMCAT congestion control algorithms are getting implemented, we wil=
l see more test results where real video encoder will be used.</div>
<div>We have seen results for GCC in the emulated network where a video seq=
uence has been used. The evaluation results of SCReAM implementation we wil=
l also use some video sequences.</div>
<div>&nbsp;</div>
<div>The eval-test (<a href=3D"https://tools.ietf.org/html/draft-ietf-rmcat=
-eval-test-01">https://tools.ietf.org/html/draft-ietf-rmcat-eval-test-01</a=
>) draft points to sources of the video sequences to use in the tests but d=
oes not pick any particular one(s).
However, as the contents of the video sequences have impact on the encoder =
output, I believe it will be better if we can agree on the video sequences =
to use in the tests. This will make the results more comparable.</div>
<div>&nbsp;</div>
<div>Any comments on that?</div>
<div>&nbsp;</div>
<div>BR</div>
<div>&nbsp;</div>
<div>Zahed&nbsp; </div>
<div>&nbsp;</div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt;"><b>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D</b></span></font></div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt;"><b>ANM ZAHEDUZZAMAN SARKER
<br>

</b>Senior Researcher <br>

Services, Media and Network Features</span></font></div>
<div><font color=3D"#333333"><br>

<font face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt;"><b>Ericsson=
<br>

</b></span></font><font face=3D"Arial" size=3D"2"><span style=3D"font-size:=
10pt;">Laboratoriegr=E4nd 11<br>

97128 Lule=E5, Sweden<br>

Phone &#43;46 10 717 37 43<br>

Mobile &#43;46 76 115 37 43<br>

Office &#43;46 76 115 37 43<br>

Fax &#43;46 920 996 21<br>

zaheduzzaman.sarker@ericsson.com<br>

</span></font><a href=3D"http://www.ericsson.com"><font face=3D"Arial" size=
=3D"2" color=3D"blue"><span style=3D"font-size:10pt;"><u>www.ericsson.com</=
u></span></font></a></font></div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt;">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D</span></font></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5ESESSMB307erics_--


From nobody Sun Jul 19 14:01:12 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D348D1B2C58 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 J5wafQHiUKH1 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:01:10 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BE71B2C42 for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:01:09 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-59-55ac1013b4be
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 4E.ED.12828.3101CA55; Sun, 19 Jul 2015 23:01:07 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.7]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0210.002; Sun, 19 Jul 2015 23:01:07 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Thread-Topic: Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjS/PwJG37fj0CVghb7vFBOk53adLiAgAA5wQCAABVdAIAAiDoAgAbvKgCAAQ6iQA==
Date: Sun, 19 Jul 2015 21:01:06 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>, <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com>
In-Reply-To: <456f0d239cbead1c87a3d639688f7495@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyM+Jvja6wwJpQg2U/5SwOtc5ksdiwegqL xeqbH9gcmD2WLPnJ5HHoeZDHsQ9f2QKYo7hsUlJzMstSi/TtErgyWps/MBdc063o3PGQsYHx gE4XIyeHhICJxLpvJ5kgbDGJC/fWs3UxcnEICRxllHiz5wwThLOIUeLRydMsXYwcHGwCNhKP F/uBmCICuRJfl3CC9DIL5EtsnNkCViEMNPPjc0GQsIiAqcTX050sENVhEqcv64OEWQRUJVom nmIEsXkFfCU2f21nhli0jUni1YW7bCAJTgE7iT1X9zOD2IxAp30/tYYJYpW4xK0n86FOFpBY suc8M4QtKvHy8T9WCFtJYtHtz0wge5kFNCXW79KHaFWUmNL9kB1ir6DEyZlPWCYwis1CMnUW QscsJB2zkHQsYGRZxShanFpcnJtuZKyXWpSZXFycn6eXl1qyiREYSQe3/Nbdwbj6teMhRgEO RiUe3gUsq0OFWBPLiitzDzFKc7AoifPO2JwXKiSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGx 0CVib19wl/GhvvWcu7Nqai8fF2WoFL7L+JuF0SCqOnrHhdrpbNYPjt/85m7zf8qblpcBSdyb 06ff2vKWSV0sSqf7+96C2pcmrtq2eV6nAt8dSjlxrOmD0q1XMzbmZCVc+2lv7xN1ep+tquzZ E4mzt0jM+FfycFbkO88PDfFc8/c7Ml/SOiygxFKckWioxVxUnAgA2Y4Rz4UCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/4LKSHo4BGYeO2wIjI6P3-lDUwmA>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:01:12 -0000

SGkgS2FyZW4sDQoNClBsZWFzZSBzZWUgaW5saW5lLg0KDQpCUg0KDQpaYWhlZA0KDQo+IA0KPiBS
ZWFkaW5nIHRoZSBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBkcmFmdCBhbmQgdGhlIGFwcC1p
bnRlcmFjdGlvbnMgZHJhZnQgSQ0KPiBoYXZlIGNvbWUgdG8gd29uZGVyIGEgYml0IGFib3V0IHRo
ZSBtdWx0aS1zdHJlYW0gY2FwYWJpbGl0aWVzIG9mIHNjcmVhbSAtIG9yDQo+IHRoZSBpbi1idWls
ZCBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBvZiAgc2NyZWFtLCBvbmUgY2FuIHNheS4NCj4g
DQo+IFRoZSBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBvZiB3ZWx6bC1ybWNhdC1jb3VwbGUt
Y2MgYWxsb3dzIGZvciBwcmlvcml0eSB0bw0KPiBiZSBnaXZlbiB0byBkaWZmZXJlbnQgZmxvd3Mg
bWFuYWdlZCBieSBvbmUgY291cGxlIGNvbmdlc3Rpb24gY29udHJvbCBjb250ZXh0DQo+IChpLmUu
IHRoZSBmbG93IGlkZW50aWZpZWQgYXMgc2hhcmluZyB0aGUgc2FtZSBib3R0bGUgbmVjaykgLSBh
bmQgdGhlIGFwcC0NCj4gaW50ZXJhY3Rpb25zIGRyYWZ0IGFza3MgZm9yIHRoZSBzYW1lIHBvc3Np
YmlsaXR5IHRvIGJlIHByb3ZpZGVkLiBUaGUgc2NyZWFtDQo+IGNvdXBsZWQgY2MgYWxzbyBhbGxv
dyBmb3Igc3VjaCBwcmlvcml0aXphdGlvbiB0byBiZSBkb25lIGluIHRoYXQgc3VjaCBjYW4gYmUN
Cj4gYWNoaWV2ZWQgYnkgc2NoZWR1bGluZyBwcmlvcml0aWVzIGluIGJldHdlZW4gdGhlIG11bHRp
cGxlIFJUUCBzdHJlYW1zIHRoYXQgb25lDQo+IENDIGNvbnRleHQgc2VydmVzIChoZXJlIHNjcmVh
bSBtb2RlbCBpcyB0aGUgc2FtZSBtb2RlbCBhcyBzY3RwIG11bHRpLXN0cmVhbQ0KPiBjYyBmb2xs
b3dzKS4NCj4gSE9XRVZFUiB3aGF0IHRoZSAgc2NyZWFtIG1vZGVsIGRvZXMgbm90IGRpcmVjdGx5
IGFsbG93IGZvciAtIGFzICBmYXIgYXMgSSBjYW4NCj4gc2VlIC0gaXMgcHJpb3JpdGl6ZWQgY291
cGxpbmcgaW4gYmV0d2VlbiBtdWx0aXBsZSBSVFAgZmxvd3MgdGhhdCBkbyBub3QgdXNlIHRoZQ0K
PiBzYW1lIFVEUCBzb2NrZXQvY29ubmVjdGlvbiB0dXBsZSAtLSBBbmQgdGhlbiBJIHN0YXJ0IHdv
bmRlciBpZiB0aGUgc3RyZWFtDQo+IG1vZGVsIGlzIHRoZSByaWdodCBvbmUuDQpbWmFoZWR1enph
bWFuIFNhcmtlcl0gSSBiZWxpZXZlIHlvdXIgaW50ZXJwcmV0YXRpb24gb2YgYSBzY3JlYW0gY29u
dHJvbGxlciBjb250cm9sbGluZyBtdWx0aXBsZSBSVFAgZmxvd3Mgb25seSB3aXRoIHNhbWUgIlVE
UCBzb2NrZXQvY29ubmVjdGlvbiB0dXBsZSIgaXMgY29taW5nIGZyb20gYSBwcmV2aW91cyByZXBs
eSB3aGVyZSBpdCB3YXMgc2FpZCB0aGUgY29udHJvbGxlciBjb250cm9scyBmbG93cyBvbmx5IHRv
d2FyZHMgc2FtZSBkZXN0aW5hdGlvbi4gSSB0aGluayB0aGUgY29ycmVjdCB0aGluZyB0byBzYXkg
aXMsIHRoZSBSVFAgcGFja2V0IHBhc3NpbmcgdGhyb3VnaCB0aGUgYSBzY3JlYW0gdHJhbnNtaXNz
aW9uIHNjaGVkdWxlciBtb3JlIG9mIGxlc3Mgc2hvd2luZyBzYW1lIGNoYXJhY3RlcmlzdGljcywg
bGlrZSBzaGFyaW5nIHNhbWUgYm90dGxlbmVjay4gSGVuY2UgaWYgdGhlcmUgaXMgYSBzeXN0ZW0g
bGlrZSBTQkQgYWxyZWFkeSBhbGxvd3MgbXVsdGlwbGUgUlRQIGZsb3dzIHdpdGggZGlmZmVyZW50
IGRlc3RpbmF0aW9uIHRvIGJlIGlkZW50aWZpZWQgYXMgc2hhcmluZyB0aGUgc2FtZSBib3R0bGVu
ZWNrIHRoZW4gcHJpb3JpdGl6YXRpb25zIGNhbiBiZSBhcHBsaWVkIHRvIGFsbCB0aG9zZSBmbG93
cyBieSBzYW1lIHRyYW5zbWlzc2lvbiBzY2hlZHVsZXIuDQpJbiB0aGUgaW1wbGVtZW50YXRpb24g
b2Ygc2NyZWFtIHRoZXJlIGlzIGEgbWV0aG9kIHRvIHJlZ2lzdGVyIGEgUlRQIGZsb3cgdG8gYSBz
Y3JlYW0gY29udHJvbGxlciB3aGljaCB3aWxsIGJlIGNvbmdlc3Rpb24gY29udHJvbGxlZCBieSB0
aGUgdGhhdCBwYXJ0aWN1bGFyIHNjcmVhbSBjb250cm9sbGVyICh0aGUgdHJhbnNtaXNzaW9uIHNj
aGVkdWxlciByZXNpZGVzIGluIHRoZSBzY3JlYW0gY29udHJvbCkuIFRoaXMgYWxzbyBtZWFucyB0
aGUgc2NyZWFtIGNvbnRyb2xsZXIgaGFzIHRvIGdldCB0aGUgaW5mb3JtYXRpb24gZnJvbSB0aGUg
UlRDUCBmZWVkYmFja3MgZm9yIHRoZSByZXNwZWN0aXZlIHJlZ2lzdGVyZWQgZmxvd3MuDQpIZW5j
ZSwgeW91ciBpbnRlcnByZXRhdGlvbiBvZiAiIHRoZSBzY3JlYW0gbW9kZWwgZG9lcyBub3QgZGly
ZWN0bHkgYWxsb3cgZm9yIHByaW9yaXRpemVkIGNvdXBsaW5nIGluIGJldHdlZW4gbXVsdGlwbGUg
UlRQIGZsb3dzIHRoYXQgZG8gbm90IHVzZSB0aGUgc2FtZSBVRFAgc29ja2V0L2Nvbm5lY3Rpb24g
dHVwbGUgIiBpcyBub3QgY29tcGxldGVseSB0cnVlLg0KDQo+IFBvc3NpYmx5IG9uZSBjYW4gc2Vl
IHRoZSBzY3JlYW0gbW9kZWwgYXMgaW50cm9kdWNpbmcgb25lIG1vcmUgbGV2ZWwgaW4gdGhlDQo+
IGNvdXBsZWQgY2MgbW9kZWwgLSBpLmUuLCBwcmlvcml0aXplZCBjb3VwbGluZyBpbiBiZXR3ZWVu
IHRoZSBmbG93cyB1c2luZyB0aGUNCj4gc2FtZSBVRFAgc29ja2V0L1VEUCB0dXBsZSBpcyBkb25l
IGJ5IG1lYW5zIG9mIHNjcmVhbSB0cmFuc21pc3Npb24NCj4gc2NoZWR1bGluZyBwcmlvcml0aWVz
IGFuZCB0aGVuIGNvdXBsZWQgY29uZ2VzdGlvbiBjb250cm9sIGZvbGxvd2luZyB0aGUgd2VsemwN
Cj4gbW9kZWwgb24gdG9wIG9mIHRoaXMsIHdoZW4gbW9yZSAiYWR2YW5jZWQiIGNvdXBsaW5nIG9y
IFNCRCBkZXRlY3Rpb24gaXMNCj4gZGVzaXJlZCBvciByZWxldmFudCBpbiBiZXR3ZWVuIGZsb3dz
IHNoYXJpbmcgdGhlIHNhbWUgYm90dGxlbmVjaywgYnV0IG5vdCB1c2luZw0KPiB0aGUgc2FtZSBV
RFAgc29ja2V0L1VEUCB0dXBsZS4NCltaYWhlZHV6emFtYW4gU2Fya2VyXSBTQ1JlQU0gbW9kZWwg
ZG9lcyBub3Qgc2ltcGx5IGFzc3VtZXMgdGhlIGV4aXN0ZW5jZSBvZiBjb3VwbGVkLWNjIGJ5IGRl
ZmF1bHQuIEFzIFNDUmVBTSBhbHJlYWR5IHVzZXMgYSB0cmFuc21pc3Npb24gc2NoZWR1bGVyIGl0
IGlzIGVhc3kgdG8gaW1wbGVtZW50ICJwcmlvcml0aXphdGlvbiBjb3VwbGluZyIgdGhlcmUuIA0K
PiANCj4gSSBzdXBwb3NlIHRoYXQgaXQgc2hvdWxkIGJlIHVwIHRvIGltcGxlbWVudGF0aW9ucyBo
b3cgdGhleSB3YW50IHRvIGltcGxlbWVudA0KPiBjb3VwbGVkIGNjIGFuZCBpZiB0aGV5IHdhbnQg
YSBsZXZlbGVkIGFwcHJvYWNoIGFzIHRoZSBvbmUganVzdCBkZXNjcmliZWQgb3IgYQ0KPiBtb3Jl
ICJkaXJlY3QiIGFwcHJvYWNoIHdoZXJlIGVhY2ggUlRQIGZsb3dzIGlzIGhhbmRsZWQgaW5kaXZp
ZHVhbGx5IGZyb20gYSBDQw0KPiBwZXJzcGVjdGl2ZSBhbmQgdGhlIGNvdXBsZWQgdmlhIGNvdXBs
ZWQgY2MgKHdlemx6KS4NCltaYWhlZHV6emFtYW4gU2Fya2VyXSBJIGJlbGlldmUgZm9yIGltcGxl
bWVudGVycyBkbyBoYXZlIGEgY2hvaWNlLiBIb3dldmVyLCBpZiB0aGV5IGRlY2lkZWQgdG8gaW1w
bGVtZW50IFNDUmVBTSB0aGV5IGhhdmUgYW4gZWFzeSBhbHRlcm5hdGl2ZSBmb3IgY291cGxlZC1j
YyBhcyBNaWNoYWVsIFcgaGltc2VsZiBzYXlzLg0KPiANCj4gT24gdGhlIG90aGVyIGhhbmQgdGhl
IG9uZSBzaG91bGQgdW5kZXJzdGFuZCB3aGF0IHdvdWxkIGJlIHRoZSBtb3RpdmF0aW9uIGZvcg0K
PiBhIGxldmVsZWQgYXBwcm9hY2ggd291bGQgYmUgLSBhbHNvIGJlY2F1c2UgaXQgc2VlbXMgdG8g
Z2l2ZSBhIG1vcmUgY29tcGxleA0KPiBtb2RlbCAgLSBJcyBpdCBzbyB0aGF0IHN1Y2ggaXMgbW90
aXZhdGVkIGJ5IC0gZm9yIGV4YW1wbGU6ID8NCj4gDQo+ICogSXQgaXMgbW9yZSBlZmZpY2llbnQg
KG92ZXJoZWFkIG9yIHByb3RvY29sLCBzdGF0ZSwgd2hhdGV2ZXIpIHRvIG1hbmFnZSBDQyBvbg0K
PiAib25lIiBtdWx0aS1zdHJlYW0gUlRQIGJhc2lzIHdoZW4gc3VjaCBpcyBwb3NzaWJsZSAtICBh
cyBzY3JlYW0gZG9lcyA/IGFuZA0KPiB0aGVyZWZvcmUgdGhlIGxldmVsZWQgYXBwcm9hY2ggaGFz
IGFkdmFudGFnZXMgZnJvbSBhIGdlbmVyYWwgcGVyc3BlY3RpdmUgb3INCj4gcG9zc2libHkgaXQg
aXMgYWR2YW50YWdlb3VzIGluIHRoZSBwYXJ0aWN1bGFyIHNpdHVhdGlvbnMgd2hlcmUgdGhlIGRl
ZmF1bHQgKGJ1aWxkLQ0KPiBpbikgc2hhcmVkIGJvdHRsZS1uZWNrIGRldGVjdGlvbiBvZiBzY3Jl
YW0gaXMgdGhlIG9ubHkgb25lIHJlbGV2YW50ID8NCj4gDQpbWmFoZWR1enphbWFuIFNhcmtlcl0g
SSBiZWxpZXZlIEkgaGF2ZSBhbHJlYWR5IGFuc3dlcmVkIHRob3NlIHF1ZXN0aW9ucy4NCg0K


From nobody Sun Jul 19 14:08:08 2015
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA611B2CC0 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 MhZs1iS7vwp1 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:08:05 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (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 671911B2CBB for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:08:05 -0700 (PDT)
Received: by lahe2 with SMTP id e2so24530240lah.1 for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MeUkZnyEQfDPK7P80vSW7cqk/+v3A0x1IQeP40ZNgmw=; b=Y1igR+1MzQktTJF+S5+zsMh31dL71hPCzbi5YemK+0m85p8HiIq85oSOSHDDkVWWRo 2Hoo0+JRdnGwyLO+ffjZrOx71B4+eMxLw+7J7zZODulOaTp4nHXhnqMrZz3JnxWbjWtF BGC8F3epcC8yh27vB2WKPwpDJu3ayZKiFKdQPoMfq/9RBMoQ8Prx1f/9QD6FX82fR9N0 SQtBM047i4TO7T4ZgHmqb6u69/U0PRCnmq3R5n2Cr9HRnzZskRMxpAXOQcAUGfdo8Tx9 24E1HZKbfOzEtQXabs20bA9C5O+ixcdDnwlk8JjDKKF/HUienPvuJcc6tsAT0RVGcyce cvqg==
MIME-Version: 1.0
X-Received: by 10.112.50.177 with SMTP id d17mr400551lbo.18.1437340083908; Sun, 19 Jul 2015 14:08:03 -0700 (PDT)
Received: by 10.112.211.132 with HTTP; Sun, 19 Jul 2015 14:08:03 -0700 (PDT)
Received: by 10.112.211.132 with HTTP; Sun, 19 Jul 2015 14:08:03 -0700 (PDT)
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se>
References: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se>
Date: Sun, 19 Jul 2015 23:08:03 +0200
Message-ID: <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com>
From: Varun Singh <vsingh.ietf@gmail.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11336e5a1f7665051b40d130
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/z9eAXq_3iIwQoXc6yGn51tOcwKE>
Cc: rmcat WG <rmcat@ietf.org>
Subject: Re: [rmcat] Video sequences for emulation tests
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:08:07 -0000

--001a11336e5a1f7665051b40d130
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi zahed,

We didn't explicitly say which videos, but the feast points to a URL with
sequences. These sequences were shared by Stephan Wenger a few IETF
meetings ago. IIRC, Foreman was used before that.  And the complete list is
at the url.

Cheers

[HEVC-seq] HEVC, , "Test Sequences", http://
<http://www.netlab.tkk.fi/~varun/test_sequences/>www.netlab.tkk.fi
<http://www.netlab.tkk.fi/~varun/test_sequences/>/~varun/test_sequences/
<http://www.netlab.tkk.fi/~varun/test_sequences/>
On Jul 19, 2015 9:44 PM, "Zaheduzzaman Sarker" <
zaheduzzaman.sarker@ericsson.com> wrote:

>  Hi,
>
> As RMCAT congestion control algorithms are getting implemented, we will
> see more test results where real video encoder will be used.
> We have seen results for GCC in the emulated network where a video
> sequence has been used. The evaluation results of SCReAM implementation w=
e
> will also use some video sequences.
>
> The eval-test (https://tools.ietf.org/html/draft-ietf-rmcat-eval-test-01)
> draft points to sources of the video sequences to use in the tests but do=
es
> not pick any particular one(s). However, as the contents of the video
> sequences have impact on the encoder output, I believe it will be better =
if
> we can agree on the video sequences to use in the tests. This will make t=
he
> results more comparable.
>
> Any comments on that?
>
> BR
>
> Zahed
>
>
> *=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D*
>
> *ANM ZAHEDUZZAMAN SARKER *Senior Researcher
> Services, Media and Network Features
>
>
> *Ericsson *Laboratoriegr=C3=A4nd 11
> 97128 Lule=C3=A5, Sweden
> Phone +46 10 717 37 43
> Mobile +46 76 115 37 43
> Office +46 76 115 37 43
> Fax +46 920 996 21
> zaheduzzaman.sarker@ericsson.com
> *www.ericsson.com* <http://www.ericsson.com>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
>
>
>

--001a11336e5a1f7665051b40d130
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi zahed,</p>
<p dir=3D"ltr">We didn&#39;t explicitly say which videos, but the feast poi=
nts to a URL with sequences. These sequences were shared by Stephan Wenger =
a few IETF meetings ago. IIRC, Foreman was used before that.=C2=A0 And the =
complete list is at the url. </p>
<p dir=3D"ltr">Cheers<br></p>
<p dir=3D"ltr">[HEVC-seq] HEVC, , &quot;Test Sequences&quot;, <a href=3D"ht=
tp://www.netlab.tkk.fi/~varun/test_sequences/">http://</a><a href=3D"http:/=
/www.netlab.tkk.fi/~varun/test_sequences/">www.netlab.tkk.fi</a><a href=3D"=
http://www.netlab.tkk.fi/~varun/test_sequences/">/~varun/test_sequences/</a=
></p>
<div class=3D"gmail_quote">On Jul 19, 2015 9:44 PM, &quot;Zaheduzzaman Sark=
er&quot; &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com">zaheduzzam=
an.sarker@ericsson.com</a>&gt; wrote:<br type=3D"attribution"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">






<div>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt">
<div>Hi,</div>
<div>=C2=A0</div>
<div>As RMCAT congestion control algorithms are getting implemented, we wil=
l see more test results where real video encoder will be used.</div>
<div>We have seen results for GCC in the emulated network where a video seq=
uence has been used. The evaluation results of SCReAM implementation we wil=
l also use some video sequences.</div>
<div>=C2=A0</div>
<div>The eval-test (<a href=3D"https://tools.ietf.org/html/draft-ietf-rmcat=
-eval-test-01" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-rmc=
at-eval-test-01</a>) draft points to sources of the video sequences to use =
in the tests but does not pick any particular one(s).
However, as the contents of the video sequences have impact on the encoder =
output, I believe it will be better if we can agree on the video sequences =
to use in the tests. This will make the results more comparable.</div>
<div>=C2=A0</div>
<div>Any comments on that?</div>
<div>=C2=A0</div>
<div>BR</div>
<div>=C2=A0</div>
<div>Zahed=C2=A0 </div>
<div>=C2=A0</div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt"><b>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D</b></span></font></div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt"><b>ANM ZAHEDUZZAMAN SARKER
<br>

</b>Senior Researcher <br>

Services, Media and Network Features</span></font></div>
<div><font color=3D"#333333"><br>

<font face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt"><b>Ericsson<=
br>

</b></span></font><font face=3D"Arial" size=3D"2"><span style=3D"font-size:=
10pt">Laboratoriegr=C3=A4nd 11<br>

97128 Lule=C3=A5, Sweden<br>

Phone <a href=3D"tel:%2B46%2010%20717%2037%2043" value=3D"+46107173743" tar=
get=3D"_blank">+46 10 717 37 43</a><br>

Mobile <a href=3D"tel:%2B46%2076%20115%2037%2043" value=3D"+46761153743" ta=
rget=3D"_blank">+46 76 115 37 43</a><br>

Office <a href=3D"tel:%2B46%2076%20115%2037%2043" value=3D"+46761153743" ta=
rget=3D"_blank">+46 76 115 37 43</a><br>

Fax <a href=3D"tel:%2B46%20920%20996%2021" value=3D"+4692099621" target=3D"=
_blank">+46 920 996 21</a><br>

<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com" target=3D"_blank">zahed=
uzzaman.sarker@ericsson.com</a><br>

</span></font><a href=3D"http://www.ericsson.com" target=3D"_blank"><font f=
ace=3D"Arial" size=3D"2" color=3D"blue"><span style=3D"font-size:10pt"><u>w=
ww.ericsson.com</u></span></font></a></font></div>
<div><font face=3D"Arial" size=3D"2" color=3D"#333333"><span style=3D"font-=
size:10pt">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D</span></font></div>
<div>=C2=A0</div>
<div>=C2=A0</div>
<div>=C2=A0</div>
</span></font>
</div>

</blockquote></div>

--001a11336e5a1f7665051b40d130--


From nobody Sun Jul 19 14:11:44 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9986B1B2CD4 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4h5TZKXKdJ23 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:11:41 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA5591A898B for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:11:40 -0700 (PDT)
Received: from mail-mx4.uio.no ([129.240.10.45]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZGvs2-0001LR-Ua; Sun, 19 Jul 2015 23:11:38 +0200
Received: from [130.129.233.50] by mail-mx4.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1ZGvs2-0005Z0-GD; Sun, 19 Jul 2015 23:11:38 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se>
Date: Sun, 19 Jul 2015 23:11:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FBB57EE-E11A-4AB9-8CF8-4AD206C3E001@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
X-Mailer: Apple Mail (2.2070.6)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 5 msgs/h 1 sum rcpts/h 9 sum msgs/h 4 total rcpts 31158 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 41D4490A01271D130C346BB55509E2E97AB268E9
X-UiO-SPAM-Test: remote_host: 130.129.233.50 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 9 max/h 4 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/IDXloORWuY75ga-HmjWUjVXtOo4>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:11:42 -0000

Hi,

snip:


>> I suppose that it should be up to implementations how they want to =
implement
>> coupled cc and if they want a leveled approach as the one just =
described or a
>> more "direct" approach where each RTP flows is handled individually =
from a CC
>> perspective and the coupled via coupled cc (wezlz).
> [Zaheduzzaman Sarker] I believe for implementers do have a choice. =
However, if they decided to implement SCReAM they have an easy =
alternative for coupled-cc as Michael W himself says.

I don't think I said that (actually I'm not sure I even understand this =
sentence). What did you mean I said?

Cheers,
Michael


From nobody Sun Jul 19 14:28:54 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70E61B2D7D for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 qdLlvuz-gYLW for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:28:51 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33E7F1B2D7A for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:28:51 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-42-55ac1691d343
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id EB.1F.12828.1961CA55; Sun, 19 Jul 2015 23:28:49 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.7]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0210.002; Sun, 19 Jul 2015 23:28:49 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjS/PwJG37fj0CVghb7vFBOk53adLiAgAA5wQCAABVdAIAAiDoAgAbvKgCAAQ6iQP//7YqAgAAlaUA=
Date: Sun, 19 Jul 2015 21:28:47 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFD9@ESESSMB307.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <3FBB57EE-E11A-4AB9-8CF8-4AD206C3E001@ifi.uio.no>
In-Reply-To: <3FBB57EE-E11A-4AB9-8CF8-4AD206C3E001@ifi.uio.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGfG3Rnei2JpQg96/chaHWmeyWPw4u5PV YsPqKSwWq29+YHNg8Viy5CeTx+rVD5k9Dj0P8jj24StbAEsUl01Kak5mWWqRvl0CV8a6K1+Z C35zVixYtZW9gfEjexcjJ4eEgInEuW2trBC2mMSFe+vZuhi5OIQEjjJK7Js+gxXCWcQo0bhv PVMXIwcHm4CNxOPFfiANIgJqEieWrwZrYBa4wShxaWkvC0hCGKim/U0/K0SRrcTJP8uZIOwk if9Le8A2swioShx4OxGshlfAV2LblI3MEMu2MEs82zqDDSTBKWAncW3xIjCbEei876fWgA1i FhCXuPVkPhPE2QISS/acZ4awRSVePv4H9Y6SxKLbn6Hq9SRuTJ3CBmFrSyxb+JoZYrGgxMmZ T1gmMIrNQjJ2FpKWWUhaZiFpWcDIsopRtDi1uDg33chYL7UoM7m4OD9PLy+1ZBMjMNIObvmt u4Nx9WvHQ4wCHIxKPLwLWFaHCrEmlhVX5h5ilOZgURLnnbE5L1RIID2xJDU7NbUgtSi+qDQn tfgQIxMHp1QDY7tHrrSp4705d16sm7/I/1vc48mCUQWT3nWk1b9YI/1Cc/4Ojdm3Cu+fqfV9 f8mvLkEhQvIYd3Fr/Hwh87p5WlebX+msrbzwhcvKyb/T4P+ngkZJK9eKPKEKnpOFz87tWfHh rf7kvmfvj/82MZ41XTx6XfoHoTnbA5YvzP/+/ugVDrGW6KNbpiixFGckGmoxFxUnAgAptQi9 lQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/myJu-2toDAusfsfZ3VHYX9HsVWA>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:28:52 -0000

Hi Michael,

If my memory supports me then I remember you saying prioritization can be e=
asily applied with schedulers at some points in your presentation at RMCAT =
previous IETF meetings.

But if you think you haven't then please accept my apologies.

BR

Zahed

> -----Original Message-----
> From: Michael Welzl [mailto:michawe@ifi.uio.no]
> Sent: den 19 juli 2015 23:12
> To: Zaheduzzaman Sarker
> Cc: Karen E. E. Nielsen; Ingemar Johansson S; rmcat@ietf.org; Mirja K=FCh=
lewind
> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>=20
> Hi,
>=20
> snip:
>=20
>=20
> >> I suppose that it should be up to implementations how they want to
> >> implement coupled cc and if they want a leveled approach as the one
> >> just described or a more "direct" approach where each RTP flows is
> >> handled individually from a CC perspective and the coupled via coupled=
 cc
> (wezlz).
> > [Zaheduzzaman Sarker] I believe for implementers do have a choice.
> However, if they decided to implement SCReAM they have an easy alternativ=
e
> for coupled-cc as Michael W himself says.
>=20
> I don't think I said that (actually I'm not sure I even understand this s=
entence).
> What did you mean I said?
>=20
> Cheers,
> Michael


From nobody Sun Jul 19 14:31:55 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 284041B2D7E for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 OW8iBp_7ROfE for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:31:51 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 981321B2D80 for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:31:50 -0700 (PDT)
X-AuditID: c1b4fb3a-f79356d000006281-a6-55ac1744c66b
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 8A.BD.25217.4471CA55; Sun, 19 Jul 2015 23:31:48 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.7]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0210.002; Sun, 19 Jul 2015 23:31:48 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Varun Singh <vsingh.ietf@gmail.com>
Thread-Topic: [rmcat] Video sequences for emulation tests
Thread-Index: AdDCA1w2Kk90mXvXQlq2XhRN8ptByAAUuAuAAATr6kA=
Date: Sun, 19 Jul 2015 21:31:48 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se>
References: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se> <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com>
In-Reply-To: <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEFESESSMB307erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3RtdFfE2owdMWG4vVNz+wWext8ndg 8tg56y67x5IlP5kCmKK4bFJSczLLUov07RK4MvY/ns1asKqbseJfu1ID45l2xi5GTg4JAROJ TTNXskDYYhIX7q1nA7GFBI4ySjSf1+9i5AKyFzFKfL+wjrWLkYODTcBG4vFiPxBTREBd4uAN H5ByZgFZietvd4K1CgtYSGxuWsAEYosIWEpMvneAEcK2kph9+jdYDYuAqsSBOV/A4rwCvhKL dh9jglg1hVFixuKtzCAJToFAiZubp7CC2IxAt30/tYYJYpm4xK0n85kgbhaQWLLnPDOELSrx 8vE/VghbSWLR7c9Q9fkSnTdeQC0TlDg58wnLBEbRWUhGzUJSNgtJ2SygN5kFNCXW79KHKFGU mNL9kB3C1pBonTOXHVl8ASP7KkbR4tTi4tx0IyO91KLM5OLi/Dy9vNSSTYzAWDu45bfVDsaD zx0PMQpwMCrx8C5gWR0qxJpYVlyZe4hRmoNFSZx3xua8UCGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2M4dPv5xR9s7j49AT35KSiiabrwzOuaGw7sMKrwkJH/t012/IQ4dk5ObJvWSdGLN7n dmjhDXFNzoMm3/XbL+9OsD/+UuxUS/2ZHc/3zFTgtJdKjmXOZP1b+c/nVqrwUm29TRf732fv X2BfLWzBefn/09dpL6Tc9y9/usP082TpkOcn2+X77oleU2Ipzkg01GIuKk4EAH+/XjGWAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/PT3Tb8x1Etk4kc_IIqQmHfzpyIs>
Cc: rmcat WG <rmcat@ietf.org>
Subject: Re: [rmcat] Video sequences for emulation tests
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:31:53 -0000

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEFESESSMB307erics_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVmFydW4sDQoNClllcywgd2UgaGF2ZW7igJl0IGV4cGxpY2l0bHkgc2FpZCB3aGljaCB2aWRl
b3MuIEJ1dCBub3cgSSB0aGluayBpdCB3b3VsZCBiZSBnb29kIHRvIHBpY2sgdXAgY291cGxlIG9m
IHRoZW0gaWYgbm90IG9uZS4NCg0KQlINCg0KWmFoZWQNCg0KRnJvbTogVmFydW4gU2luZ2ggW21h
aWx0bzp2c2luZ2guaWV0ZkBnbWFpbC5jb21dDQpTZW50OiBkZW4gMTkganVsaSAyMDE1IDIzOjA4
DQpUbzogWmFoZWR1enphbWFuIFNhcmtlcg0KQ2M6IHJtY2F0IFdHDQpTdWJqZWN0OiBSZTogW3Jt
Y2F0XSBWaWRlbyBzZXF1ZW5jZXMgZm9yIGVtdWxhdGlvbiB0ZXN0cw0KDQoNCkhpIHphaGVkLA0K
DQpXZSBkaWRuJ3QgZXhwbGljaXRseSBzYXkgd2hpY2ggdmlkZW9zLCBidXQgdGhlIGZlYXN0IHBv
aW50cyB0byBhIFVSTCB3aXRoIHNlcXVlbmNlcy4gVGhlc2Ugc2VxdWVuY2VzIHdlcmUgc2hhcmVk
IGJ5IFN0ZXBoYW4gV2VuZ2VyIGEgZmV3IElFVEYgbWVldGluZ3MgYWdvLiBJSVJDLCBGb3JlbWFu
IHdhcyB1c2VkIGJlZm9yZSB0aGF0LiAgQW5kIHRoZSBjb21wbGV0ZSBsaXN0IGlzIGF0IHRoZSB1
cmwuDQoNCkNoZWVycw0KDQpbSEVWQy1zZXFdIEhFVkMsICwgIlRlc3QgU2VxdWVuY2VzIiwgaHR0
cDovLzxodHRwOi8vd3d3Lm5ldGxhYi50a2suZmkvfnZhcnVuL3Rlc3Rfc2VxdWVuY2VzLz53d3cu
bmV0bGFiLnRray5maTxodHRwOi8vd3d3Lm5ldGxhYi50a2suZmkvfnZhcnVuL3Rlc3Rfc2VxdWVu
Y2VzLz4vfnZhcnVuL3Rlc3Rfc2VxdWVuY2VzLzxodHRwOi8vd3d3Lm5ldGxhYi50a2suZmkvfnZh
cnVuL3Rlc3Rfc2VxdWVuY2VzLz4NCk9uIEp1bCAxOSwgMjAxNSA5OjQ0IFBNLCAiWmFoZWR1enph
bWFuIFNhcmtlciIgPHphaGVkdXp6YW1hbi5zYXJrZXJAZXJpY3Nzb24uY29tPG1haWx0bzp6YWhl
ZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGksDQoNCkFzIFJNQ0FUIGNv
bmdlc3Rpb24gY29udHJvbCBhbGdvcml0aG1zIGFyZSBnZXR0aW5nIGltcGxlbWVudGVkLCB3ZSB3
aWxsIHNlZSBtb3JlIHRlc3QgcmVzdWx0cyB3aGVyZSByZWFsIHZpZGVvIGVuY29kZXIgd2lsbCBi
ZSB1c2VkLg0KV2UgaGF2ZSBzZWVuIHJlc3VsdHMgZm9yIEdDQyBpbiB0aGUgZW11bGF0ZWQgbmV0
d29yayB3aGVyZSBhIHZpZGVvIHNlcXVlbmNlIGhhcyBiZWVuIHVzZWQuIFRoZSBldmFsdWF0aW9u
IHJlc3VsdHMgb2YgU0NSZUFNIGltcGxlbWVudGF0aW9uIHdlIHdpbGwgYWxzbyB1c2Ugc29tZSB2
aWRlbyBzZXF1ZW5jZXMuDQoNClRoZSBldmFsLXRlc3QgKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLXJtY2F0LWV2YWwtdGVzdC0wMSkgZHJhZnQgcG9pbnRzIHRvIHNvdXJj
ZXMgb2YgdGhlIHZpZGVvIHNlcXVlbmNlcyB0byB1c2UgaW4gdGhlIHRlc3RzIGJ1dCBkb2VzIG5v
dCBwaWNrIGFueSBwYXJ0aWN1bGFyIG9uZShzKS4gSG93ZXZlciwgYXMgdGhlIGNvbnRlbnRzIG9m
IHRoZSB2aWRlbyBzZXF1ZW5jZXMgaGF2ZSBpbXBhY3Qgb24gdGhlIGVuY29kZXIgb3V0cHV0LCBJ
IGJlbGlldmUgaXQgd2lsbCBiZSBiZXR0ZXIgaWYgd2UgY2FuIGFncmVlIG9uIHRoZSB2aWRlbyBz
ZXF1ZW5jZXMgdG8gdXNlIGluIHRoZSB0ZXN0cy4gVGhpcyB3aWxsIG1ha2UgdGhlIHJlc3VsdHMg
bW9yZSBjb21wYXJhYmxlLg0KDQpBbnkgY29tbWVudHMgb24gdGhhdD8NCg0KQlINCg0KWmFoZWQN
Cg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PQ0KQU5NIFpBSEVEVVpaQU1BTiBTQVJLRVINClNlbmlv
ciBSZXNlYXJjaGVyDQpTZXJ2aWNlcywgTWVkaWEgYW5kIE5ldHdvcmsgRmVhdHVyZXMNCg0KRXJp
Y3Nzb24NCkxhYm9yYXRvcmllZ3LDpG5kIDExDQo5NzEyOCBMdWxlw6UsIFN3ZWRlbg0KUGhvbmUg
KzQ2IDEwIDcxNyAzNyA0Mzx0ZWw6JTJCNDYlMjAxMCUyMDcxNyUyMDM3JTIwNDM+DQpNb2JpbGUg
KzQ2IDc2IDExNSAzNyA0Mzx0ZWw6JTJCNDYlMjA3NiUyMDExNSUyMDM3JTIwNDM+DQpPZmZpY2Ug
KzQ2IDc2IDExNSAzNyA0Mzx0ZWw6JTJCNDYlMjA3NiUyMDExNSUyMDM3JTIwNDM+DQpGYXggKzQ2
IDkyMCA5OTYgMjE8dGVsOiUyQjQ2JTIwOTIwJTIwOTk2JTIwMjE+DQp6YWhlZHV6emFtYW4uc2Fy
a2VyQGVyaWNzc29uLmNvbTxtYWlsdG86emFoZWR1enphbWFuLnNhcmtlckBlcmljc3Nvbi5jb20+
DQp3d3cuZXJpY3Nzb24uY29tPGh0dHA6Ly93d3cuZXJpY3Nzb24uY29tPg0KPT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PQ0KDQoNCg0K

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEFESESSMB307erics_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
VnJpbmRhOw0KCXBhbm9zZS0xOjIgMTEgNSAyIDQgMiA0IDIgMiAzO30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6VnJpbmRhOw0KCXBhbm9zZS0xOjIgMTEgNSAyIDQgMiA0IDIgMiAzO30NCkBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIg
NCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToy
IDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBO
ZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
cA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJ
bWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4t
bGVmdDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJv
bWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNv
bmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6
IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0aW9u
MQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQg
NzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBWYXJ1biw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlllcywg
d2UgaGF2ZW7igJl0IGV4cGxpY2l0bHkgc2FpZCB3aGljaCB2aWRlb3MuIEJ1dCBub3cgSSB0aGlu
ayBpdCB3b3VsZCBiZSBnb29kIHRvIHBpY2sgdXAgY291cGxlIG9mIHRoZW0gaWYgbm90IG9uZS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPkJSPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5aYWhlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0K
PGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAx
LjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPiBWYXJ1biBTaW5naCBbbWFpbHRvOnZzaW5naC5pZXRmQGdtYWlsLmNv
bV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBkZW4gMTkganVsaSAyMDE1IDIzOjA4PGJyPg0KPGI+VG86
PC9iPiBaYWhlZHV6emFtYW4gU2Fya2VyPGJyPg0KPGI+Q2M6PC9iPiBybWNhdCBXRzxicj4NCjxi
PlN1YmplY3Q6PC9iPiBSZTogW3JtY2F0XSBWaWRlbyBzZXF1ZW5jZXMgZm9yIGVtdWxhdGlvbiB0
ZXN0czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwPkhpIHphaGVkLDxvOnA+PC9vOnA+PC9w
Pg0KPHA+V2UgZGlkbid0IGV4cGxpY2l0bHkgc2F5IHdoaWNoIHZpZGVvcywgYnV0IHRoZSBmZWFz
dCBwb2ludHMgdG8gYSBVUkwgd2l0aCBzZXF1ZW5jZXMuIFRoZXNlIHNlcXVlbmNlcyB3ZXJlIHNo
YXJlZCBieSBTdGVwaGFuIFdlbmdlciBhIGZldyBJRVRGIG1lZXRpbmdzIGFnby4gSUlSQywgRm9y
ZW1hbiB3YXMgdXNlZCBiZWZvcmUgdGhhdC4mbmJzcDsgQW5kIHRoZSBjb21wbGV0ZSBsaXN0IGlz
IGF0IHRoZSB1cmwuDQo8bzpwPjwvbzpwPjwvcD4NCjxwPkNoZWVyczxvOnA+PC9vOnA+PC9wPg0K
PHA+W0hFVkMtc2VxXSBIRVZDLCAsICZxdW90O1Rlc3QgU2VxdWVuY2VzJnF1b3Q7LCA8YSBocmVm
PSJodHRwOi8vd3d3Lm5ldGxhYi50a2suZmkvfnZhcnVuL3Rlc3Rfc2VxdWVuY2VzLyI+DQpodHRw
Oi8vPC9hPjxhIGhyZWY9Imh0dHA6Ly93d3cubmV0bGFiLnRray5maS9+dmFydW4vdGVzdF9zZXF1
ZW5jZXMvIj53d3cubmV0bGFiLnRray5maTwvYT48YSBocmVmPSJodHRwOi8vd3d3Lm5ldGxhYi50
a2suZmkvfnZhcnVuL3Rlc3Rfc2VxdWVuY2VzLyI+L352YXJ1bi90ZXN0X3NlcXVlbmNlcy88L2E+
PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gSnVsIDE5LCAy
MDE1IDk6NDQgUE0sICZxdW90O1phaGVkdXp6YW1hbiBTYXJrZXImcXVvdDsgJmx0OzxhIGhyZWY9
Im1haWx0bzp6YWhlZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbSI+emFoZWR1enphbWFuLnNh
cmtlckBlcmljc3Nvbi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5I
aSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+QXMgUk1DQVQgY29uZ2VzdGlvbiBjb250cm9sIGFsZ29yaXRobXMgYXJl
IGdldHRpbmcgaW1wbGVtZW50ZWQsIHdlIHdpbGwgc2VlIG1vcmUgdGVzdCByZXN1bHRzIHdoZXJl
IHJlYWwgdmlkZW8gZW5jb2RlciB3aWxsIGJlIHVzZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5XZSBoYXZlIHNlZW4gcmVzdWx0cyBmb3IgR0NDIGluIHRoZSBlbXVsYXRlZCBuZXR3
b3JrIHdoZXJlIGEgdmlkZW8gc2VxdWVuY2UgaGFzIGJlZW4gdXNlZC4gVGhlIGV2YWx1YXRpb24g
cmVzdWx0cyBvZiBTQ1JlQU0gaW1wbGVtZW50YXRpb24gd2Ugd2lsbCBhbHNvIHVzZSBzb21lIHZp
ZGVvIHNlcXVlbmNlcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGhlIGV2YWwtdGVzdCAoPGEgaHJlZj0iaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcm1jYXQtZXZhbC10ZXN0LTAxIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcm1jYXQt
ZXZhbC10ZXN0LTAxPC9hPikgZHJhZnQgcG9pbnRzDQogdG8gc291cmNlcyBvZiB0aGUgdmlkZW8g
c2VxdWVuY2VzIHRvIHVzZSBpbiB0aGUgdGVzdHMgYnV0IGRvZXMgbm90IHBpY2sgYW55IHBhcnRp
Y3VsYXIgb25lKHMpLiBIb3dldmVyLCBhcyB0aGUgY29udGVudHMgb2YgdGhlIHZpZGVvIHNlcXVl
bmNlcyBoYXZlIGltcGFjdCBvbiB0aGUgZW5jb2RlciBvdXRwdXQsIEkgYmVsaWV2ZSBpdCB3aWxs
IGJlIGJldHRlciBpZiB3ZSBjYW4gYWdyZWUgb24gdGhlIHZpZGVvIHNlcXVlbmNlcyB0byB1c2Ug
aW4gdGhlDQogdGVzdHMuIFRoaXMgd2lsbCBtYWtlIHRoZSByZXN1bHRzIG1vcmUgY29tcGFyYWJs
ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+QW55IGNvbW1lbnRzIG9uIHRoYXQ/PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkJSPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPlphaGVkJm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNw
OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzMzMzMzMyI+PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PTwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMzMzMzMzMiPkFOTSBaQUhFRFVaWkFN
QU4gU0FSS0VSDQo8YnI+DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzMzMzMzMyI+U2VuaW9yIFJlc2VhcmNoZXINCjxicj4NClNlcnZpY2VzLCBNZWRpYSBhbmQg
TmV0d29yayBGZWF0dXJlczwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzMzMzIj48YnI+DQo8L3NwYW4+PGI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzMzMzIj5Fcmljc3Nvbjxicj4NCjwv
c3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzMzMzIj5MYWJvcmF0
b3JpZWdyw6RuZCAxMTxicj4NCjk3MTI4IEx1bGXDpSwgU3dlZGVuPGJyPg0KUGhvbmUgPGEgaHJl
Zj0idGVsOiUyQjQ2JTIwMTAlMjA3MTclMjAzNyUyMDQzIiB0YXJnZXQ9Il9ibGFuayI+JiM0Mzs0
NiAxMCA3MTcgMzcgNDM8L2E+PGJyPg0KTW9iaWxlIDxhIGhyZWY9InRlbDolMkI0NiUyMDc2JTIw
MTE1JTIwMzclMjA0MyIgdGFyZ2V0PSJfYmxhbmsiPiYjNDM7NDYgNzYgMTE1IDM3IDQzPC9hPjxi
cj4NCk9mZmljZSA8YSBocmVmPSJ0ZWw6JTJCNDYlMjA3NiUyMDExNSUyMDM3JTIwNDMiIHRhcmdl
dD0iX2JsYW5rIj4mIzQzOzQ2IDc2IDExNSAzNyA0MzwvYT48YnI+DQpGYXggPGEgaHJlZj0idGVs
OiUyQjQ2JTIwOTIwJTIwOTk2JTIwMjEiIHRhcmdldD0iX2JsYW5rIj4mIzQzOzQ2IDkyMCA5OTYg
MjE8L2E+PGJyPg0KPGEgaHJlZj0ibWFpbHRvOnphaGVkdXp6YW1hbi5zYXJrZXJAZXJpY3Nzb24u
Y29tIiB0YXJnZXQ9Il9ibGFuayI+emFoZWR1enphbWFuLnNhcmtlckBlcmljc3Nvbi5jb208L2E+
PGJyPg0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzMzMzIj48
YSBocmVmPSJodHRwOi8vd3d3LmVyaWNzc29uLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPnd3dy5lcmljc3Nvbi5jb208L3NwYW4+PC9hPjwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzMzMzMzMyI+PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEFESESSMB307erics_--


From nobody Sun Jul 19 14:56:25 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970F81B2D91 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fO8PkrIjarn4 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 14:56:22 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0251A90F4 for <rmcat@ietf.org>; Sun, 19 Jul 2015 14:56:21 -0700 (PDT)
Received: from mail-mx6.uio.no ([129.240.10.40]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZGwZH-0003GO-B9; Sun, 19 Jul 2015 23:56:19 +0200
Received: from [130.129.233.50] by mail-mx6.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZGwZG-0000vc-ON; Sun, 19 Jul 2015 23:56:19 +0200
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFD9@ESESSMB307.ericsson.se>
Date: Sun, 19 Jul 2015 23:56:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3FE580B-640D-4D42-A173-2D14FAFE7E63@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <3FBB57EE-E11A-4AB9-8CF8-4AD206C3E001@ifi.uio.no> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFD9@ESESSMB307.ericsson.se>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
X-Mailer: Apple Mail (2.2070.6)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 12 msgs/h 3 sum rcpts/h 16 sum msgs/h 6 total rcpts 31165 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: F59F8ADFC46615B9022BFC0185E7445E34235E27
X-UiO-SPAM-Test: remote_host: 130.129.233.50 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 11 max/h 4 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/JAJr_yyqrCBdKekzWA3BzGcrTro>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 21:56:23 -0000

> On 19. jul. 2015, at 23.28, Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com> wrote:
>=20
>=20
> Hi Michael,
>=20
> If my memory supports me then I remember you saying prioritization can =
be easily applied with schedulers at some points in your presentation at =
RMCAT previous IETF meetings.
>=20
> But if you think you haven't then please accept my apologies.

Nono, I just didn't understand the sentence as you phrased it. Yes, I =
did say that. We also mention scheduling as another way to do it in the =
coupled-cc draft.
I think scheduling is fine if all trafic is multiplexed on the same =
5-tuple and you therefore know it will always share the same bottleneck.

Our coupled-cc mechanism was made to make the code easier. This applies =
when you have situations with a shared bottleneck detection algorithm as =
input, to decide whether you're coupling or not. This is a dynamic =
decision, requiring the ability to turn the coupling on and off.

E.g., quickly going from:  one congestion controller, 3 flows are =
scheduled onto it   to: 3 congestion controllers, one per flow  ...
and back...
...is probably not an easy matter to implement. Turning our coupled-cc =
mechanism on and off is very easy.

But since this is all on one host only, I don't think we should strictly =
enforce any certain behavior.

Cheers,
Michael


From nobody Sun Jul 19 15:38:05 2015
Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46D171B2DE1 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 evmY77SWD6rS for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:38:02 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D157C1B2DE0 for <rmcat@ietf.org>; Sun, 19 Jul 2015 15:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16125; q=dns/txt; s=iport; t=1437345481; x=1438555081; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=kA8w7TLEfW9I1Eer2dQOg8HfWZrwsCZB3QPX3FB9GwE=; b=dDbvrzF8eDl25aEnlsqNDC7YaW6rI0duD71h1mle8U2rdzjZs/OKI8xM 0vexeB4HjDmQjNwImQdIeg/ceG96/vVe1h4GrVT3KGy5PKGUFtufeZR3B 2dWyOmL1UR6fk4nHnVIWj+AcTEKUMT9DDOizamZhEWKsHZR34G7VFNJJ3 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CFBQC6JaxV/4MNJK1cFoIwTVRpBoUmuDeFdwKBHTsRAQEBAQEBAYEKhCMBAQEELRwwDgICAQgRAwEBASgHFgUGERQJCAEBBAENBYgZAxINvlkNhS4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXBItIgk2CKA0EBgEJhCIFlFIBhG6FSoFokV+HKCaCDRyBU2+BR4EEAQEB
X-IronPort-AV: E=Sophos; i="5.15,504,1432598400"; d="scan'208,217"; a="11170533"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-8.cisco.com with ESMTP; 19 Jul 2015 22:38:00 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t6JMc08c030718 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jul 2015 22:38:00 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.72]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Sun, 19 Jul 2015 17:38:00 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Varun Singh <vsingh.ietf@gmail.com>
Thread-Topic: [rmcat] Video sequences for emulation tests
Thread-Index: AdDCA1w2Kk90mXvXQlq2XhRN8ptByAAjYyOAAADUWAAABoCbgA==
Date: Sun, 19 Jul 2015 22:38:00 +0000
Message-ID: <D1D1F2FE.2405F%xiaoqzhu@cisco.com>
References: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se> <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se>
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.2.150604
x-originating-ip: [10.61.106.66]
Content-Type: multipart/alternative; boundary="_000_D1D1F2FE2405Fxiaoqzhuciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/9m14XszmQewX5SHJb4u3mqZVk-E>
Cc: rmcat WG <rmcat@ietf.org>
Subject: Re: [rmcat] Video sequences for emulation tests
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 22:38:04 -0000

--_000_D1D1F2FE2405Fxiaoqzhuciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Agree that will be nice for folks to use the same set of video sequences fo=
r testing.  We have not yet tested with the sources shared by Stephan Wenge=
r.  Will weigh in on this topic after we look into that.

BTW, from the link foreman15_4000.yuv has a size of 0 =85

Thanks,
Xiaoqing

From: rmcat <rmcat-bounces@ietf.org<mailto:rmcat-bounces@ietf.org>> on beha=
lf of Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com<mailto:zaheduzz=
aman.sarker@ericsson.com>>
Date: Sunday, July 19, 2015 at 4:31 PM
To: Varun Singh <vsingh.ietf@gmail.com<mailto:vsingh.ietf@gmail.com>>
Cc: rmcat WG <rmcat@ietf.org<mailto:rmcat@ietf.org>>
Subject: Re: [rmcat] Video sequences for emulation tests

Hi Varun,

Yes, we haven=92t explicitly said which videos. But now I think it would be=
 good to pick up couple of them if not one.

BR

Zahed

From: Varun Singh [mailto:vsingh.ietf@gmail.com]
Sent: den 19 juli 2015 23:08
To: Zaheduzzaman Sarker
Cc: rmcat WG
Subject: Re: [rmcat] Video sequences for emulation tests


Hi zahed,

We didn't explicitly say which videos, but the feast points to a URL with s=
equences. These sequences were shared by Stephan Wenger a few IETF meetings=
 ago. IIRC, Foreman was used before that.  And the complete list is at the =
url.

Cheers

[HEVC-seq] HEVC, , "Test Sequences", http://<http://www.netlab.tkk.fi/~varu=
n/test_sequences/>www.netlab.tkk.fi<http://www.netlab.tkk.fi/~varun/test_se=
quences/>/~varun/test_sequences/<http://www.netlab.tkk.fi/~varun/test_seque=
nces/>
On Jul 19, 2015 9:44 PM, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsso=
n.com<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
Hi,

As RMCAT congestion control algorithms are getting implemented, we will see=
 more test results where real video encoder will be used.
We have seen results for GCC in the emulated network where a video sequence=
 has been used. The evaluation results of SCReAM implementation we will als=
o use some video sequences.

The eval-test (https://tools.ietf.org/html/draft-ietf-rmcat-eval-test-01) d=
raft points to sources of the video sequences to use in the tests but does =
not pick any particular one(s). However, as the contents of the video seque=
nces have impact on the encoder output, I believe it will be better if we c=
an agree on the video sequences to use in the tests. This will make the res=
ults more comparable.

Any comments on that?

BR

Zahed

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ANM ZAHEDUZZAMAN SARKER
Senior Researcher
Services, Media and Network Features

Ericsson
Laboratoriegr=E4nd 11
97128 Lule=E5, Sweden
Phone +46 10 717 37 43<tel:%2B46%2010%20717%2037%2043>
Mobile +46 76 115 37 43<tel:%2B46%2076%20115%2037%2043>
Office +46 76 115 37 43<tel:%2B46%2076%20115%2037%2043>
Fax +46 920 996 21<tel:%2B46%20920%20996%2021>
zaheduzzaman.sarker@ericsson.com<mailto:zaheduzzaman.sarker@ericsson.com>
www.ericsson.com<http://www.ericsson.com>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D




--_000_D1D1F2FE2405Fxiaoqzhuciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3C369C1FA8B7634BA8F983E48CA9729D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Agree that will be nice for folks to use the same set of video sequenc=
es for testing. &nbsp;We have not yet tested with the sources shared by Ste=
phan Wenger. &nbsp;Will weigh in on this topic after we look into that.&nbs=
p;</div>
<div><br>
</div>
<div>BTW, from the link&nbsp;foreman15_4000.yuv has a size of 0 =85</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Xiaoqing</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>rmcat &lt;<a href=3D"mailto:r=
mcat-bounces@ietf.org">rmcat-bounces@ietf.org</a>&gt; on behalf of Zaheduzz=
aman Sarker &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com">zaheduz=
zaman.sarker@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Sunday, July 19, 2015 at 4:31=
 PM<br>
<span style=3D"font-weight:bold">To: </span>Varun Singh &lt;<a href=3D"mail=
to:vsingh.ietf@gmail.com">vsingh.ietf@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>rmcat WG &lt;<a href=3D"mailto:=
rmcat@ietf.org">rmcat@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [rmcat] Video sequence=
s for emulation tests<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Vrinda;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Vrinda;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Hi Varun,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Yes, we haven=92t explicitly said w=
hich videos. But now I think it would be good to pick up couple of them if =
not one.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">BR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Zahed<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> Varun Singh [<a href=3D"mailto:vsingh.ietf@gmail.c=
om">mailto:vsingh.ietf@gmail.com</a>]
<br>
<b>Sent:</b> den 19 juli 2015 23:08<br>
<b>To:</b> Zaheduzzaman Sarker<br>
<b>Cc:</b> rmcat WG<br>
<b>Subject:</b> Re: [rmcat] Video sequences for emulation tests<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Hi zahed,<o:p></o:p></p>
<p>We didn't explicitly say which videos, but the feast points to a URL wit=
h sequences. These sequences were shared by Stephan Wenger a few IETF meeti=
ngs ago. IIRC, Foreman was used before that.&nbsp; And the complete list is=
 at the url.
<o:p></o:p></p>
<p>Cheers<o:p></o:p></p>
<p>[HEVC-seq] HEVC, , &quot;Test Sequences&quot;, <a href=3D"http://www.net=
lab.tkk.fi/~varun/test_sequences/">
http://</a><a href=3D"http://www.netlab.tkk.fi/~varun/test_sequences/">www.=
netlab.tkk.fi</a><a href=3D"http://www.netlab.tkk.fi/~varun/test_sequences/=
">/~varun/test_sequences/</a><o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Jul 19, 2015 9:44 PM, &quot;Zaheduzzaman Sarker&q=
uot; &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com">zaheduzzaman.s=
arker@ericsson.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">Hi,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">As RMCAT congestion control algorithms are getting implement=
ed, we will see more test results where real video encoder will be used.<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">We have seen results for GCC in the emulated network where a=
 video sequence has been used. The evaluation results of SCReAM implementat=
ion we will also use some video sequences.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">The eval-test (<a href=3D"https://tools.ietf.org/html/draft-=
ietf-rmcat-eval-test-01" target=3D"_blank">https://tools.ietf.org/html/draf=
t-ietf-rmcat-eval-test-01</a>) draft points
 to sources of the video sequences to use in the tests but does not pick an=
y particular one(s). However, as the contents of the video sequences have i=
mpact on the encoder output, I believe it will be better if we can agree on=
 the video sequences to use in the
 tests. This will make the results more comparable.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">Any comments on that?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">BR<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">Zahed&nbsp;
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: rgb(51, 51, 51);">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span></b><span styl=
e=3D"font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Aria=
l, sans-serif; color: rgb(51, 51, 51);">ANM ZAHEDUZZAMAN SARKER
<br>
</span></b><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; =
color: rgb(51, 51, 51);">Senior Researcher
<br>
Services, Media and Network Features</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(51, 51, 51);"><br>
</span><b><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; c=
olor: rgb(51, 51, 51);">Ericsson<br>
</span></b><span style=3D"font-size: 10pt; font-family: Arial, sans-serif; =
color: rgb(51, 51, 51);">Laboratoriegr=E4nd 11<br>
97128 Lule=E5, Sweden<br>
Phone <a href=3D"tel:%2B46%2010%20717%2037%2043" target=3D"_blank">&#43;46 =
10 717 37 43</a><br>
Mobile <a href=3D"tel:%2B46%2076%20115%2037%2043" target=3D"_blank">&#43;46=
 76 115 37 43</a><br>
Office <a href=3D"tel:%2B46%2076%20115%2037%2043" target=3D"_blank">&#43;46=
 76 115 37 43</a><br>
Fax <a href=3D"tel:%2B46%20920%20996%2021" target=3D"_blank">&#43;46 920 99=
6 21</a><br>
<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com" target=3D"_blank">zahed=
uzzaman.sarker@ericsson.com</a><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#333333"><a href=3D"http://www.ericsson.com" targe=
t=3D"_blank"><span style=3D"font-size: 10pt; font-family: Arial, sans-serif=
;">www.ericsson.com</span></a></span><span style=3D"font-size: 11pt; font-f=
amily: Calibri, sans-serif;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Arial, =
sans-serif; color: rgb(51, 51, 51);">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span><span style=3D"fo=
nt-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D1D1F2FE2405Fxiaoqzhuciscocom_--


From nobody Sun Jul 19 15:43:44 2015
Return-Path: <mzanaty@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DCA1B2DF4 for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 jQOBgyl6fqUq for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:43:40 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F8C1B2DF2 for <rmcat@ietf.org>; Sun, 19 Jul 2015 15:43:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15220; q=dns/txt; s=iport; t=1437345820; x=1438555420; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=erhMVLPZpoJ60DW1U1K2vdT7eUcAfWRh8CcIKIB3Ris=; b=Zjsbl86nOwvHFYPrdTcdqttDTzGC76PGckuAxDZ2pBWYW4CWChDIrTj4 h5tOpopPQOoYLkDb6euk6Sx/8ySGlV2+n9UV3yDTK9cwZGfpjApq1pUUE 4I8kISq63iHXnOpx36Wg/d8b27EqDlU2kDFSwkXNX6a1S+WQlIN3i46Iu o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CGBQCPJ6xV/4gNJK1cFoIwTVRphSy4N4V3AoEdPBABAQEBAQEBgQqEIwEBAQQtHDAOAgIBCBEEAQEoBxYFBhEUCQgBAQQOBYgZAxINvl8NhS4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXBItIgk2CNQQGAQmDDoEUBZRSAYRuhUqBaJFfhygmgg0cgVNvgksBAQE
X-IronPort-AV: E=Sophos; i="5.15,504,1432598400"; d="scan'208,217"; a="16816098"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-3.cisco.com with ESMTP; 19 Jul 2015 22:43:38 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t6JMhc1X027641 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jul 2015 22:43:38 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.42]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Sun, 19 Jul 2015 17:43:38 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Thread-Topic: [rmcat] Video sequences for emulation tests
Thread-Index: AdDCA1w2Kk90mXvXQlq2XhRN8ptByAAjYyOAAADUWAD//8A/cw==
Date: Sun, 19 Jul 2015 22:43:37 +0000
Message-ID: <C489F1D8-E66C-4EC2-AA18-C4B0DDF3A0F6@cisco.com>
References: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se> <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com>, <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se>
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C489F1D8E66C4EC2AA18C4B0DDF3A0F6ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/w54jzObA7xeGgiResTJu7iWV-_8>
Cc: rmcat WG <rmcat@ietf.org>, Varun Singh <vsingh.ietf@gmail.com>
Subject: Re: [rmcat] Video sequences for emulation tests
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 22:43:42 -0000

--_000_C489F1D8E66C4EC2AA18C4B0DDF3A0F6ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

The encoder and its configuration, particularly rate control settings, usua=
lly impacts output bitrate even more than the selection of raw sequences. S=
o if we are moving towards guidelines for how CC candidates should test rea=
l video, some specific encoder and configuration should be specified in add=
ition to specific raw sequences.

Cheers,
Mo



On Jul 19, 2015, at 11:31 PM, Zaheduzzaman Sarker <zaheduzzaman.sarker@eric=
sson.com<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:

Hi Varun,

Yes, we haven=92t explicitly said which videos. But now I think it would be=
 good to pick up couple of them if not one.

BR

Zahed

From: Varun Singh [mailto:vsingh.ietf@gmail.com]
Sent: den 19 juli 2015 23:08
To: Zaheduzzaman Sarker
Cc: rmcat WG
Subject: Re: [rmcat] Video sequences for emulation tests


Hi zahed,

We didn't explicitly say which videos, but the feast points to a URL with s=
equences. These sequences were shared by Stephan Wenger a few IETF meetings=
 ago. IIRC, Foreman was used before that.  And the complete list is at the =
url.

Cheers

[HEVC-seq] HEVC, , "Test Sequences", http://<http://www.netlab.tkk.fi/~varu=
n/test_sequences/>www.netlab.tkk.fi<http://www.netlab.tkk.fi/~varun/test_se=
quences/>/~varun/test_sequences/<http://www.netlab.tkk.fi/~varun/test_seque=
nces/>
On Jul 19, 2015 9:44 PM, "Zaheduzzaman Sarker" <zaheduzzaman.sarker@ericsso=
n.com<mailto:zaheduzzaman.sarker@ericsson.com>> wrote:
Hi,

As RMCAT congestion control algorithms are getting implemented, we will see=
 more test results where real video encoder will be used.
We have seen results for GCC in the emulated network where a video sequence=
 has been used. The evaluation results of SCReAM implementation we will als=
o use some video sequences.

The eval-test (https://tools.ietf.org/html/draft-ietf-rmcat-eval-test-01) d=
raft points to sources of the video sequences to use in the tests but does =
not pick any particular one(s). However, as the contents of the video seque=
nces have impact on the encoder output, I believe it will be better if we c=
an agree on the video sequences to use in the tests. This will make the res=
ults more comparable.

Any comments on that?

BR

Zahed

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ANM ZAHEDUZZAMAN SARKER
Senior Researcher
Services, Media and Network Features

Ericsson
Laboratoriegr=E4nd 11
97128 Lule=E5, Sweden
Phone +46 10 717 37 43<tel:%2B46%2010%20717%2037%2043>
Mobile +46 76 115 37 43<tel:%2B46%2076%20115%2037%2043>
Office +46 76 115 37 43<tel:%2B46%2076%20115%2037%2043>
Fax +46 920 996 21<tel:%2B46%20920%20996%2021>
zaheduzzaman.sarker@ericsson.com<mailto:zaheduzzaman.sarker@ericsson.com>
www.ericsson.com<http://www.ericsson.com>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D




--_000_C489F1D8E66C4EC2AA18C4B0DDF3A0F6ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>The encoder and its configuration, particularly rate control settings,=
 usually impacts output bitrate even more than the selection of raw sequenc=
es. So if we are moving towards guidelines for how CC candidates should tes=
t real video, some specific encoder
 and configuration should be specified in addition to specific raw sequence=
s.&nbsp;</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Mo<br>
<br>
<br>
</div>
<div><br>
On Jul 19, 2015, at 11:31 PM, Zaheduzzaman Sarker &lt;<a href=3D"mailto:zah=
eduzzaman.sarker@ericsson.com">zaheduzzaman.sarker@ericsson.com</a>&gt; wro=
te:<br>
<br>
</div>
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Vrinda;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Vrinda;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Varun,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yes, we haven=92t explici=
tly said which videos. But now I think it would be good to pick up couple o=
f them if not one.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">BR<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Zahed<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Varun Si=
ngh [<a href=3D"mailto:vsingh.ietf@gmail.com">mailto:vsingh.ietf@gmail.com<=
/a>]
<br>
<b>Sent:</b> den 19 juli 2015 23:08<br>
<b>To:</b> Zaheduzzaman Sarker<br>
<b>Cc:</b> rmcat WG<br>
<b>Subject:</b> Re: [rmcat] Video sequences for emulation tests<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Hi zahed,<o:p></o:p></p>
<p>We didn't explicitly say which videos, but the feast points to a URL wit=
h sequences. These sequences were shared by Stephan Wenger a few IETF meeti=
ngs ago. IIRC, Foreman was used before that.&nbsp; And the complete list is=
 at the url.
<o:p></o:p></p>
<p>Cheers<o:p></o:p></p>
<p>[HEVC-seq] HEVC, , &quot;Test Sequences&quot;, <a href=3D"http://www.net=
lab.tkk.fi/~varun/test_sequences/">
http://</a><a href=3D"http://www.netlab.tkk.fi/~varun/test_sequences/">www.=
netlab.tkk.fi</a><a href=3D"http://www.netlab.tkk.fi/~varun/test_sequences/=
">/~varun/test_sequences/</a><o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Jul 19, 2015 9:44 PM, &quot;Zaheduzzaman Sarker&q=
uot; &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com">zaheduzzaman.s=
arker@ericsson.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Hi,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">As RMCAT congestion control algorithms =
are getting implemented, we will see more test results where real video enc=
oder will be used.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">We have seen results for GCC in the emu=
lated network where a video sequence has been used. The evaluation results =
of SCReAM implementation we will also use some video sequences.<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">The eval-test (<a href=3D"https://tools=
.ietf.org/html/draft-ietf-rmcat-eval-test-01" target=3D"_blank">https://too=
ls.ietf.org/html/draft-ietf-rmcat-eval-test-01</a>) draft points
 to sources of the video sequences to use in the tests but does not pick an=
y particular one(s). However, as the contents of the video sequences have i=
mpact on the encoder output, I believe it will be better if we can agree on=
 the video sequences to use in the
 tests. This will make the results more comparable.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Any comments on that?<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">BR<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Zahed&nbsp;
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#333333">=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span></b><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#333333">ANM ZAHEDUZZAMAN SARKER
<br>
</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&q=
uot;sans-serif&quot;;color:#333333">Senior Researcher
<br>
Services, Media and Network Features</span><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#333333"><br>
</span><b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&qu=
ot;sans-serif&quot;;color:#333333">Ericsson<br>
</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&q=
uot;sans-serif&quot;;color:#333333">Laboratoriegr=E4nd 11<br>
97128 Lule=E5, Sweden<br>
Phone <a href=3D"tel:%2B46%2010%20717%2037%2043" target=3D"_blank">&#43;46 =
10 717 37 43</a><br>
Mobile <a href=3D"tel:%2B46%2076%20115%2037%2043" target=3D"_blank">&#43;46=
 76 115 37 43</a><br>
Office <a href=3D"tel:%2B46%2076%20115%2037%2043" target=3D"_blank">&#43;46=
 76 115 37 43</a><br>
Fax <a href=3D"tel:%2B46%20920%20996%2021" target=3D"_blank">&#43;46 920 99=
6 21</a><br>
<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com" target=3D"_blank">zahed=
uzzaman.sarker@ericsson.com</a><br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#333333"><a href=3D"http://www.ericsson.com" targe=
t=3D"_blank"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;">www.ericsson.com</span></a></span><span style=3D"fo=
nt-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#333333">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_C489F1D8E66C4EC2AA18C4B0DDF3A0F6ciscocom_--


From nobody Sun Jul 19 15:59:08 2015
Return-Path: <mzanaty@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF121B2E3C for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 uc6LK9UJJ1TP for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 15:59:04 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E4C1B2E1D for <rmcat@ietf.org>; Sun, 19 Jul 2015 15:58:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21263; q=dns/txt; s=iport; t=1437346728; x=1438556328; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ncd5kQFbNKUvK0usofRbG3XkoO/POr31fctpu+2yBnc=; b=XUxJpgxoU21r1R7kB6EtmAjDdJhWVbXEmJy+x4Mrv5kypeKkuiOj9siJ nr+DYt1b0fQD/vRHIKCUbBvuj0GqSiF8K7MV/pYspvJC2J78oTJXpt8L3 awIX+l38hTbgDlhorWRshU9Z+KYY7Jd+lOnf6+L63WN5Q2WyOr3WyFQMO 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BtAwAEK6xV/5ldJa1SCoJGTYE9u2UJh2wCgR44FAEBAQEBAQGBCoQkAQEEJ1IQAgEIPwcyFBEBAQQOBRuIE8QTAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tMhCldB4MXgRQFlFIBh06EUoFDhBqLEYQ4g2Emg3xvgksBAQE
X-IronPort-AV: E=Sophos; i="5.15,505,1432598400"; d="scan'208,217"; a="11177202"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 19 Jul 2015 22:58:47 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t6JMwldu005278 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jul 2015 22:58:47 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.42]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Sun, 19 Jul 2015 17:58:47 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Thread-Topic: Comments on draft-zanaty-rmcat-cc-codec-interactions-00
Thread-Index: AdDCTVLB4Wf4ApIxSkG9SB86EGEyuAAKSUqT
Date: Sun, 19 Jul 2015 22:58:46 +0000
Message-ID: <06C761C3-30D0-4D53-90B6-5935D1E70F05@cisco.com>
References: <adf483811175cd873364d6447c504066@mail.gmail.com>
In-Reply-To: <adf483811175cd873364d6447c504066@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_06C761C330D04D5390B65935D1E70F05ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/We_3LTsyzHQl11pPoWf0zVN2WyU>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Comments on draft-zanaty-rmcat-cc-codec-interactions-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Jul 2015 22:59:07 -0000

--_000_06C761C330D04D5390B65935D1E70F05ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Karen,

Thanks for the review and comments.

Your first point is the most important to set the direction of this draft. =
This will be highlighted in the status slide (of the chairs update). So far=
, nearly all discussion about interactions in CC drafts and list threads is=
 focused on Allowed Rate, with little or no discussion about the other inte=
ractions listed. I'm happy to remove the others, or mark them optional, or =
move them to an appendix, if the CC authors can confirm they don't intend a=
ny such interactions as they progress.

The rest of your edits and points look good. We will update the draft to in=
corporate them.

Cheers,
Mo

On Jul 19, 2015, at 8:04 PM, Karen Elisabeth Egede Nielsen <karen.nielsen@t=
ieto.com<mailto:karen.nielsen@tieto.com>> wrote:

Hi Mo,

For what it is worth then please accept the following comments to the draft=
.

General:

I think that the document now only includes the CC-Codec interactions. I th=
ink this complies with what we intended in the wg.

I think that we should divide into MANDATORY and OPTIONAL sections, so that=
 the
minimal set of features that
a codec developer have to rely on from the CC, and interact with, is absolu=
tely clear.

Right now the document includes more interactions that what the present RMC=
AT CC proposals provides.
Indeed it seems that they only provides the very basic one (and with couple=
 CC one more).
I think that further work shall narrow down the CC-codec interactions that =
we want to have in the document.
While it has value during the progress of the RMCAT CC definition work, to =
describe codec-cc  interactions,
that we from a theoretical perspective identify as something that could mak=
e sense for an RMCAT CC to provide, but which are not provided by any
solution (yet?),  then I am not sure that it makes sense to have  these int=
eractions in there in the end.

Perhaps a  solution could be to put the interaction features, which are not=
 supported by any of the CC proposals into the appendix and
here describe why one have ended up not supporting each.
I indeed suppose that there will be good reason for  why one can have or wi=
ll have to live without.

I think that the introduction is a little too heavy and detailed in content=
.
E.g., I don=92t think that the doc necessarily needs to motivate why RMCAT =
CC is needed nor
does it need to describe what present application do instead of using RMCAT=
 CC (I think).
Also section 3 and section 4 are a little to detailed to my taste. But on t=
he other hand, then as long as
no framework document exists, then some context should be given.

Detailed comments:

Abstract:

Suggest to rephrase:


and the components dedicated to congestion control functions --> and the RM=
CAT congestion control layer

I assume that FEC is the reason why you use the formulation


the application components that relate
   to congestion control, specifically the media codec control layer,

instead of simply:

the media codec control layer

Section 1:

I am not sure if we really need the historical perspective on CC implemente=
d (or not) in RTP media applications in this document.
I think that the text is good, but I think that it belongs rather in the re=
quirements doc or in a framework doc.
I think that one could jump right into the paragraph under the bulleted lis=
t in section 1 or even right into the paragraph starting with .

The RMCAT requirements..


Second last paragraph of Section 1:

In order to meet these requirements, interactions are necessary
   between the application's congestion controller, the RTP layer, media
   codecs, other components, and the underlying UDP/IP network stack.
   This memo attempts to present a conceptual model of the various
   interfaces based on a simplified application decomposition.  This
   memo discusses interactions between the congestion control and codec
   control layer in a typical RTP Application.

I suggest to rephrase to (something like):


In order to meet these requirements, interactions are necessary
   between the application's congestion controller and other
   application components, like the media codecs layer and the
   RTP layer. This memo describes the interactions between the
   RMCAT congestion control layer and the codec
   control layer in a interactive real time media RTP application.
Section 3:

Suggest to rephrase:


understanding and discussion of where congestion
   control functions operate, and how they interface with the other
   components.

to



understanding and discussion of where congestion
   control functions operate, and how they interface with the codec control=
 layer.



Bullet 2 on Config seems to be too detailed for the purpose of this documen=
t. I suggest to keep only the text until  =93For example ..

Bullet 4: I suggest to eliminate the text from  =93such as REMB [I-D.alvest=
rand-rmcat-remb] ..=94 and onwards in this bullet.

Bullet 6: Shared state : I don=92t think this detail is needed here. It is =
? If so then I think that it should just be part of bullet 5 on congestion =
control.

Section 5:

The section starts with saying =93the necessary..=94. but it seems to descr=
ibe both necessary and optional interactions. IF we end up describing optio=
nal interactions then I think we should have two subsections here =96 one f=
or the =93necessary=94 ones and, one section for the optional ones.

Section 5.2:

Right now what we have here is the priorities in coupled congestion. Correc=
t ? If so I think that this could be made more concrete.

Section 5.3, 5.4, 5.5, 5.6, 5.8, 5.9:

No RMCAT CC solution seems to support this at present.  Should it be here ?

5.6 has the heading Forward Error Correction, but truly speaks about sensit=
ivity to loss patterns. Shouldn=92t this be the tittle ? (if kept).

Section 5.7:

This may be provided by the RMCAT CC (judging from the present discussions =
in the wg). Should as the other paragraph say
more exactly what the interaction consists of (CC-FEC/encoder).

BR, Karen


--_000_06C761C330D04D5390B65935D1E70F05ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Hi Karen,</div>
<div><br>
</div>
<div>Thanks for the review and comments.</div>
<div><br>
</div>
<div>Your first point is the most important to set the direction of this dr=
aft. This will be highlighted in the status slide (of the chairs update). S=
o far, nearly all discussion about interactions in CC drafts and list threa=
ds is focused on Allowed Rate, with
 little or no discussion about the other interactions listed. I'm happy to =
remove the others, or mark them optional, or move them to an appendix, if t=
he CC authors can confirm they don't intend any such interactions as they p=
rogress.&nbsp;<br>
<br>
The rest of your edits and points look good. We will update the draft to in=
corporate them.&nbsp;</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Mo</div>
<div><br>
On Jul 19, 2015, at 8:04 PM, Karen Elisabeth Egede Nielsen &lt;<a href=3D"m=
ailto:karen.nielsen@tieto.com">karen.nielsen@tieto.com</a>&gt; wrote:<br>
<br>
</div>
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1972514046;
	mso-list-type:hybrid;
	mso-list-template-ids:-1834349748 -1201531504 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style>
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Mo,</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">For what it is worth then please accept the followin=
g comments to the draft.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">General:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I think that the document now only includes the CC-C=
odec interactions. I think this complies with what we intended in the wg.</=
p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I think that we should divide into MANDATORY and OPT=
IONAL sections, so that the
</p>
<p class=3D"MsoNormal">minimal set of features that </p>
<p class=3D"MsoNormal">a codec developer have to rely on from the CC, and i=
nteract with, is absolutely clear.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Right now the document includes more interactions th=
at what the present RMCAT CC proposals provides.</p>
<p class=3D"MsoNormal">Indeed it seems that they only provides the very bas=
ic one (and with couple CC one more).</p>
<p class=3D"MsoNormal">I think that further work shall narrow down the CC-c=
odec interactions that we want to have in the document.</p>
<p class=3D"MsoNormal">While it has value during the progress of the RMCAT =
CC definition work, to describe codec-cc &nbsp;interactions,</p>
<p class=3D"MsoNormal">that we from a theoretical perspective identify as s=
omething that could make sense for an RMCAT CC to provide, but which are no=
t provided by any</p>
<p class=3D"MsoNormal">solution (yet?), &nbsp;then I am not sure that it ma=
kes sense to have &nbsp;these interactions in there in the end.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Perhaps a &nbsp;solution could be to put the interac=
tion features, which are not supported by any of the CC proposals into the =
appendix and</p>
<p class=3D"MsoNormal">here describe why one have ended up not supporting e=
ach. </p>
<p class=3D"MsoNormal">I indeed suppose that there will be good reason for&=
nbsp; why one can have or will have to live without.
</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I think that the introduction is a little too heavy =
and detailed in content.</p>
<p class=3D"MsoNormal">E.g., I don=92t think that the doc necessarily needs=
 to motivate why RMCAT CC is needed nor</p>
<p class=3D"MsoNormal">does it need to describe what present application do=
 instead of using RMCAT CC (I think).</p>
<p class=3D"MsoNormal">Also section 3 and section 4 are a little to detaile=
d to my taste. But on the other hand, then as long as</p>
<p class=3D"MsoNormal">no framework document exists, then some context shou=
ld be given.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Detailed comments:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Abstract:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Suggest to rephrase:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">and the components dedicated to congestion control functions --&gt; and =
the RMCAT congestion control layer</span></p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I assume that FEC is the reason why you use the form=
ulation </p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">the application components that relate<br>
&nbsp;&nbsp; to congestion control, specifically the media codec control la=
yer,</span></p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">instead of simply:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;">the media codec control layer</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal">Section 1:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I am not sure if we really need the historical persp=
ective on CC implemented (or not) in RTP media applications in this documen=
t.</p>
<p class=3D"MsoNormal">I think that the text is good, but I think that it b=
elongs rather in the requirements doc or in a framework doc.</p>
<p class=3D"MsoNormal">I think that one could jump right into the paragraph=
 under the bulleted list in section 1 or even right into the paragraph star=
ting with . &nbsp;</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;">The RMCAT requirements..</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal">Second last paragraph of Section 1:</p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:12.0pt"><span style=3D"fon=
t-family:&quot;Courier New&quot;">In order to meet these requirements, inte=
ractions are necessary<br>
&nbsp;&nbsp; between the application's congestion controller, the RTP layer=
, media<br>
&nbsp;&nbsp; codecs, other components, and the underlying UDP/IP network st=
ack.<br>
&nbsp;&nbsp; This memo attempts to present a conceptual model of the variou=
s<br>
&nbsp;&nbsp; interfaces based on a simplified application decomposition.&nb=
sp; This<br>
&nbsp;&nbsp; memo discusses interactions between the congestion control and=
 codec<br>
&nbsp;&nbsp; control layer in a typical RTP Application.</span></p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;color:#222222;backgr=
ound:white">I suggest to rephrase to (something like):</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.5pt;color:#222222;backgr=
ound:white">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:12.0pt"><span style=3D"fon=
t-family:&quot;Courier New&quot;">In order to meet these requirements, inte=
ractions are necessary<br>
&nbsp;&nbsp; between the application's congestion controller and other <br>
&nbsp;&nbsp;&nbsp;application components, like the media codecs layer and t=
he <br>
&nbsp;&nbsp;&nbsp;RTP layer. This memo describes the interactions between t=
he <br>
&nbsp;&nbsp;&nbsp;RMCAT congestion control layer and the codec<br>
&nbsp;&nbsp; control layer in a interactive real time media RTP application=
.</span></p>
<p class=3D"MsoNormal">Section 3:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Suggest to rephrase:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">understanding and discussion of where congestion<br>
&nbsp;&nbsp; control functions operate, and how they interface with the oth=
er<br>
&nbsp;&nbsp; components.</span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">to</span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span style=3D"font-family:&quot;Courier New&quot=
;">understanding and discussion of where congestion<br>
&nbsp;&nbsp; control functions operate, and how they interface with the cod=
ec control layer.</span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Bullet 2 on Config seems to be too detailed for the =
purpose of this document. I suggest to keep only the text until &nbsp;=93Fo=
r example ..
</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Bullet 4: I suggest to eliminate the text from &nbsp=
;=93<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;">su=
ch as REMB [I-D.alvestrand-rmcat-remb] ..=94
</span>and onwards in this bullet.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Bullet 6: Shared state : I don=92t think this detail=
 is needed here. It is ? If so then I think that it should just be part of =
bullet 5 on congestion control.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Section 5:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">The section starts with saying =93the necessary..=94=
. but it seems to describe both necessary and optional interactions. IF we =
end up describing optional interactions then I think we should have two sub=
sections here =96 one for the =93necessary=94
 ones and, one section for the optional ones.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Section 5.2:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Right now what we have here is the priorities in cou=
pled congestion. Correct ? If so I think that this could be made more concr=
ete.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Section 5.3, 5.4, 5.5, 5.6, 5.8, 5.9:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">No RMCAT CC solution seems to support this at presen=
t.&nbsp; Should it be here ?</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">5.6 has the heading Forward Error Correction, but tr=
uly speaks about sensitivity to loss patterns. Shouldn=92t this be the titt=
le ? (if kept).</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Section 5.7:</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">This may be provided by the RMCAT CC (judging from t=
he present discussions in the wg). Should as the other paragraph say
</p>
<p class=3D"MsoNormal">more exactly what the interaction consists of (CC-FE=
C/encoder).</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">BR, Karen </p>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</body>
</html>

--_000_06C761C330D04D5390B65935D1E70F05ciscocom_--


From nobody Sun Jul 19 22:32:06 2015
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9482E1B2FBE for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 22:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 50uZK_4SmaGl for <rmcat@ietfa.amsl.com>; Sun, 19 Jul 2015 22:32:03 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 56BDA1B2FBC for <rmcat@ietf.org>; Sun, 19 Jul 2015 22:32:03 -0700 (PDT)
Received: by igbij6 with SMTP id ij6so74666639igb.1 for <rmcat@ietf.org>; Sun, 19 Jul 2015 22:32:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=JENxm0f+KuYqKMlnaE8E+AJvDCSQQ88euz255b5BnTU=; b=zIwY1zeib2mrH7A0bhAoveJ1kKJkUQEQ+itGqsU9HVzycWGUUUw/cWboDu/eu+Vztn fFz2lRBcK2pupD+DcFHiG+P3XvuEMrQ3QEFKp0B0Oi7leE4Ck3iDTNso/aPlJIs06D1A x17Tq0Rrn1Ix1a4S28VSKvE745UnDNUJM/Eoc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=JENxm0f+KuYqKMlnaE8E+AJvDCSQQ88euz255b5BnTU=; b=K4HHqSvrp73nDHU8pXIrm//PfEVeezXsRmP+VrONUeVZtRVql9dKCrlFjvGcYG2gjc LxwViMageI0WAI3q1EhhPYTaP+9KHdyoobGjCqjqeoHQy4vTEd5X7wmKhDweoPt12J+i wrtPNC2ETbo/FnqggL9AtiOcJAxnCyFV6DTzR4gYkCfvWKMNiham6Qcx4J09+n6EAvDQ uE8muZBSOUFypCshq4VxKVFvJ6fMAYsuki61xcP1oNIUUeXLCpbeQUogmxOpRSLEnO5H nzqg6ByhTFuHlNuR2kO6QYAaJJ2g8lM4CbAWpXmO61zYSE68rmhjkQ+X7Ja1pJq+bmaA yUyg==
X-Gm-Message-State: ALoCoQl55QTd0hPnx3A+UzWX57GFa5ihRA8+OHLnJVb/9HwtiOydWB3hwW4B5FOD1xEBlheIopCyLBfm91dKocvvBhvjUw1JM4OQPN9CEbTmkznVMdFtWfA=
X-Received: by 10.107.167.2 with SMTP id q2mr36942320ioe.109.1437370322852; Sun, 19 Jul 2015 22:32:02 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>, <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se>
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGmc/6jnjaBhqE3gdH9BjSKecACAIU9jZWAhk0bc8BHrz2aAKIK+jXANzjCGUCD65y+5yiFxow
Date: Mon, 20 Jul 2015 07:32:02 +0200
Message-ID: <07529396e89526f834a8816d1d2502c7@mail.gmail.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>,  Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/8yBmkpx0_gCO0VEbpUHqnESDEkw>
Cc: rmcat@ietf.org, =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 20 Jul 2015 05:32:05 -0000

HI,

Yes - there is the possibility to implement coupled congestion control with
scheduling priorities,
There is no doubt about that :-), Indeed SCTP does it and scream does it.
But it is not so well-described in the
scream draft how exactly the prioritization works and which means an
application has to define different priorities.
(For information then for SCTP a number of different scheduling
possibilities is described in
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)

Then for RMCAT coupled congestion control  we have the Wezlz, Safiqul
proposal where the coupled is done
in-between per flow-CC contexts by prioritization on manipulation of the
cwnd.
And the we also have, a not so detailed proposal/description, on how the
same can be achieved via scheduling (scream).
It should be ok to allow for different ways to implement coupling, but we
should then eventually have one document that describes both
solutions. Shouldn't we ?

BR, Karen



>-----Original Message-----
>From: Zaheduzzaman Sarker [mailto:zaheduzzaman.sarker@ericsson.com]
>Sent: Sunday, July 19, 2015 11:01 PM
>To: Karen E. E. Nielsen; Ingemar Johansson S
>Cc: Mirja K=C3=BChlewind; rmcat@ietf.org
>Subject: RE: Review of draft-ietf-rmcat-scream-cc-01
>
>Hi Karen,
>
>Please see inline.
>
>BR
>
>Zahed
>
>>
>> Reading the coupled congestion control draft and the app-interactions
>> draft I have come to wonder a bit about the multi-stream capabilities
>> of scream - or the in-build coupled congestion control of  scream, one
>> can
>say.
>>
>> The coupled congestion control of welzl-rmcat-couple-cc allows for
>> priority to be given to different flows managed by one couple
>> congestion control context (i.e. the flow identified as sharing the
>> same bottle neck) - and the app- interactions draft asks for the same
>> possibility to be provided. The scream coupled cc also allow for such
>> prioritization to be done in that such can be achieved by scheduling
>> priorities in between the multiple RTP streams that one CC context
>> serves (here scream model is the same model as sctp multi-stream cc
>follows).
>> HOWEVER what the  scream model does not directly allow for - as  far
>> as I can see - is prioritized coupling in between multiple RTP flows
>> that do not use the same UDP socket/connection tuple -- And then I
>> start wonder if the stream model is the right one.
>[Zaheduzzaman Sarker] I believe your interpretation of a scream controller
>controlling multiple RTP flows only with same "UDP socket/connection tuple=
"
>is coming from a previous reply where it was said the controller controls
>flows
>only towards same destination. I think the correct thing to say is, the RT=
P
>packet passing through the a scream transmission scheduler more of less
>showing same characteristics, like sharing same bottleneck. Hence if there
>is a
>system like SBD already allows multiple RTP flows with different
>destination to
>be identified as sharing the same bottleneck then prioritizations can be
>applied to all those flows by same transmission scheduler.
>In the implementation of scream there is a method to register a RTP flow t=
o
>a
>scream controller which will be congestion controlled by the that
>particular
>scream controller (the transmission scheduler resides in the scream
>control).
>This also means the scream controller has to get the information from the
>RTCP feedbacks for the respective registered flows.
>Hence, your interpretation of " the scream model does not directly allow
>for
>prioritized coupling in between multiple RTP flows that do not use the sam=
e
>UDP socket/connection tuple " is not completely true.
>
>> Possibly one can see the scream model as introducing one more level in
>> the coupled cc model - i.e., prioritized coupling in between the flows
>> using the same UDP socket/UDP tuple is done by means of scream
>> transmission scheduling priorities and then coupled congestion control
>> following the welzl model on top of this, when more "advanced"
>> coupling or SBD detection is desired or relevant in between flows
>> sharing the same bottleneck, but not using the same UDP socket/UDP tuple=
.
>[Zaheduzzaman Sarker] SCReAM model does not simply assumes the
>existence of coupled-cc by default. As SCReAM already uses a transmission
>scheduler it is easy to implement "prioritization coupling" there.
>>
>> I suppose that it should be up to implementations how they want to
>> implement coupled cc and if they want a leveled approach as the one
>> just described or a more "direct" approach where each RTP flows is
>> handled individually from a CC perspective and the coupled via coupled c=
c
>(wezlz).
>[Zaheduzzaman Sarker] I believe for implementers do have a choice.
>However, if they decided to implement SCReAM they have an easy
>alternative for coupled-cc as Michael W himself says.
>>
>> On the other hand the one should understand what would be the
>> motivation for a leveled approach would be - also because it seems to
>> give a more complex model  - Is it so that such is motivated by - for
>> example:
>?
>>
>> * It is more efficient (overhead or protocol, state, whatever) to
>> manage CC on "one" multi-stream RTP basis when such is possible -  as
>> scream does ? and therefore the leveled approach has advantages from a
>> general perspective or possibly it is advantageous in the particular
>> situations where the default (build-
>> in) shared bottle-neck detection of scream is the only one relevant ?
>>
>[Zaheduzzaman Sarker] I believe I have already answered those questions.


From nobody Mon Jul 20 00:49:37 2015
Return-Path: <zaheduzzaman.sarker@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C22F81A01A9 for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 00:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 LaXh5XfrWZxC for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 00:49:33 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F38641A0158 for <rmcat@ietf.org>; Mon, 20 Jul 2015 00:49:32 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-f2-55aca80adab8
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id BD.17.12828.A08ACA55; Mon, 20 Jul 2015 09:49:30 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.7]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0210.002; Mon, 20 Jul 2015 09:49:30 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Thread-Topic: Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjS/PwJG37fj0CVghb7vFBOk53adLiAgAA5wQCAABVdAIAAiDoAgAbvKgCAAQ6iQIAAeVoAgAA6p9A=
Date: Mon, 20 Jul 2015 07:49:29 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129AD5BB@ESESSMB307.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com>, <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com>
In-Reply-To: <07529396e89526f834a8816d1d2502c7@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsUyM+JvjS7XijWhBjN2WVkcap3JYrFh9RQW i9U3P7A5MHssWfKTyePQ8yCPYx++sgUwR3HZpKTmZJalFunbJXBl/DxwlLmgz6Ni//eVjA2M C9y6GDk5JARMJF7/mcQOYYtJXLi3nq2LkYtDSOAoo8SJv4cYIZxFjBKHLz5l7WLk4GATsJF4 vNgPxBQRyJX4uoQTpJdZIF9i48wWFpCwMNDMj88FQcIiAqYSX093skDYSRK/J91iA7FZBFQl vr25CraWV8BXYsHHw1Br1zFLbN7YDdbAKWAnMXXFWlYQmxHotu+n1jBB7BKXuPVkPhPEzQIS S/acZ4awRSVePv7HCmErSaw9vB3sHmYBTYn1u/QhWhUlpnQ/hNorKHFy5hOWCYxis5BMnYXQ MQtJxywkHQsYWVYxihanFhfnphsZ66UWZSYXF+fn6eWllmxiBMbSwS2/dXcwrn7teIhRgINR iYf3geyaUCHWxLLiytxDjNIcLErivDM254UKCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYFzu GDq14VJXwMtUpo6g2zfzKzb8Cd8j8Xtz741kq3cXhKe8LYw5s7iY+VZVYuXO9QJhUlsf3hM7 b2t1nvFHvc/Eh60fnD2C5gjuWmz8saVH6LRt9bK1tct25uwN97hkvdZzLW8oS4XXhqRJ8x1M dU/FbY+JOG909Uzp0flLT+1Zq9+lvc7+wxIlluKMREMt5qLiRADtuAI9hgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/u7IL1LgEk_q0-lbO9rqZ8a1OP5c>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 20 Jul 2015 07:49:35 -0000

SGksDQoNCkl0IHdhcy9pcyBub3Qgb3VyIHByaW1lIGludGVudGlvbiB0byBnbyB0aHJvdWdoIGRp
ZmZlcmVudCAgc2NoZWR1bGluZyBjYW4gYmUgdXNlZC4gV2UgZGVzY3JpYmVkIGEgc2ltcGxlIHdh
eSBvZiBkb2luZyBwcmlvcml0aXphdGlvbiBpbiB0aGUgc2NoZWR1bGVyLg0KDQpSZWdhcmRpbmcg
bW92aW5nIGludG8gYSBjb21tb24gZHJhZnQgd2l0aCBvdGhlciBzb2x1dGlvbnMsIEkgZG9u4oCZ
dCBoYXZlIGFueSBzdHJvbmcgb3BpbmlvbiBhYm91dCBpdCBidXQgc2VlbXMgbGlrZSBhIHJlYXNv
bmFibGUgdGhpbmcgdG8gZG8gaWYgUk1DQVQgaXMgZ29pbmcgdG8gcHJvZHVjZSBhIHNpbmdsZSBk
b2N1bWVudCBkZXNjcmliaW5nIGFsdGVybmF0aXZlcy4gVGhlIHN0cmVhbSBwcmlvcml0aXphdGlv
biBpcyBhbHJlYWR5IG1lbnRpb25lZCBhcyBhbiAiYWRkaXRpb25hbCBmZWF0dXJlIiBzbyBzZXBh
cmF0aW5nIHRoYXQgZnJvbSBTQ1JlQU0gZHJhZnQgYW5kIGp1c3QgcG9pbnRpbmcgdG8gdGhhdCB0
aGUgb3RoZXIgZG9jIHNob3VsZCBub3QgYmUgYW4gaXNzdWUuDQoNCkJSDQoNClphaGVkDQoNCj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogS2FyZW4gRWxpc2FiZXRoIEVnZWRl
IE5pZWxzZW4gW21haWx0bzprYXJlbi5uaWVsc2VuQHRpZXRvLmNvbV0NCj4gU2VudDogZGVuIDIw
IGp1bGkgMjAxNSAwNzozMg0KPiBUbzogWmFoZWR1enphbWFuIFNhcmtlcjsgSW5nZW1hciBKb2hh
bnNzb24gUw0KPiBDYzogTWlyamEgS8O8aGxld2luZDsgcm1jYXRAaWV0Zi5vcmcNCj4gU3ViamVj
dDogUkU6IFJldmlldyBvZiBkcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMQ0KPiANCj4gSEks
DQo+IA0KPiBZZXMgLSB0aGVyZSBpcyB0aGUgcG9zc2liaWxpdHkgdG8gaW1wbGVtZW50IGNvdXBs
ZWQgY29uZ2VzdGlvbiBjb250cm9sIHdpdGgNCj4gc2NoZWR1bGluZyBwcmlvcml0aWVzLCBUaGVy
ZSBpcyBubyBkb3VidCBhYm91dCB0aGF0IDotKSwgSW5kZWVkIFNDVFAgZG9lcyBpdCBhbmQNCj4g
c2NyZWFtIGRvZXMgaXQuDQo+IEJ1dCBpdCBpcyBub3Qgc28gd2VsbC1kZXNjcmliZWQgaW4gdGhl
DQo+IHNjcmVhbSBkcmFmdCBob3cgZXhhY3RseSB0aGUgcHJpb3JpdGl6YXRpb24gd29ya3MgYW5k
IHdoaWNoIG1lYW5zIGFuDQo+IGFwcGxpY2F0aW9uIGhhcyB0byBkZWZpbmUgZGlmZmVyZW50IHBy
aW9yaXRpZXMuDQo+IChGb3IgaW5mb3JtYXRpb24gdGhlbiBmb3IgU0NUUCBhIG51bWJlciBvZiBk
aWZmZXJlbnQgc2NoZWR1bGluZyBwb3NzaWJpbGl0aWVzIGlzDQo+IGRlc2NyaWJlZCBpbg0KPiBo
dHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtdHN2d2ctc2N0cC1uZGF0
YS8uKQ0KPiANCj4gVGhlbiBmb3IgUk1DQVQgY291cGxlZCBjb25nZXN0aW9uIGNvbnRyb2wgIHdl
IGhhdmUgdGhlIFdlemx6LCBTYWZpcXVsDQo+IHByb3Bvc2FsIHdoZXJlIHRoZSBjb3VwbGVkIGlz
IGRvbmUgaW4tYmV0d2VlbiBwZXIgZmxvdy1DQyBjb250ZXh0cyBieQ0KPiBwcmlvcml0aXphdGlv
biBvbiBtYW5pcHVsYXRpb24gb2YgdGhlIGN3bmQuDQo+IEFuZCB0aGUgd2UgYWxzbyBoYXZlLCBh
IG5vdCBzbyBkZXRhaWxlZCBwcm9wb3NhbC9kZXNjcmlwdGlvbiwgb24gaG93IHRoZSBzYW1lDQo+
IGNhbiBiZSBhY2hpZXZlZCB2aWEgc2NoZWR1bGluZyAoc2NyZWFtKS4NCj4gSXQgc2hvdWxkIGJl
IG9rIHRvIGFsbG93IGZvciBkaWZmZXJlbnQgd2F5cyB0byBpbXBsZW1lbnQgY291cGxpbmcsIGJ1
dCB3ZSBzaG91bGQNCj4gdGhlbiBldmVudHVhbGx5IGhhdmUgb25lIGRvY3VtZW50IHRoYXQgZGVz
Y3JpYmVzIGJvdGggc29sdXRpb25zLiBTaG91bGRuJ3Qgd2UNCj4gPw0KPiANCj4gQlIsIEthcmVu
DQo+IA0KPiANCj4gDQo+ID4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+RnJvbTogWmFo
ZWR1enphbWFuIFNhcmtlciBbbWFpbHRvOnphaGVkdXp6YW1hbi5zYXJrZXJAZXJpY3Nzb24uY29t
XQ0KPiA+U2VudDogU3VuZGF5LCBKdWx5IDE5LCAyMDE1IDExOjAxIFBNDQo+ID5UbzogS2FyZW4g
RS4gRS4gTmllbHNlbjsgSW5nZW1hciBKb2hhbnNzb24gUw0KPiA+Q2M6IE1pcmphIEvDvGhsZXdp
bmQ7IHJtY2F0QGlldGYub3JnDQo+ID5TdWJqZWN0OiBSRTogUmV2aWV3IG9mIGRyYWZ0LWlldGYt
cm1jYXQtc2NyZWFtLWNjLTAxDQo+ID4NCj4gPkhpIEthcmVuLA0KPiA+DQo+ID5QbGVhc2Ugc2Vl
IGlubGluZS4NCj4gPg0KPiA+QlINCj4gPg0KPiA+WmFoZWQNCj4gPg0KPiA+Pg0KPiA+PiBSZWFk
aW5nIHRoZSBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBkcmFmdCBhbmQgdGhlIGFwcC1pbnRl
cmFjdGlvbnMNCj4gPj4gZHJhZnQgSSBoYXZlIGNvbWUgdG8gd29uZGVyIGEgYml0IGFib3V0IHRo
ZSBtdWx0aS1zdHJlYW0gY2FwYWJpbGl0aWVzDQo+ID4+IG9mIHNjcmVhbSAtIG9yIHRoZSBpbi1i
dWlsZCBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBvZiAgc2NyZWFtLA0KPiA+PiBvbmUgY2Fu
DQo+ID5zYXkuDQo+ID4+DQo+ID4+IFRoZSBjb3VwbGVkIGNvbmdlc3Rpb24gY29udHJvbCBvZiB3
ZWx6bC1ybWNhdC1jb3VwbGUtY2MgYWxsb3dzIGZvcg0KPiA+PiBwcmlvcml0eSB0byBiZSBnaXZl
biB0byBkaWZmZXJlbnQgZmxvd3MgbWFuYWdlZCBieSBvbmUgY291cGxlDQo+ID4+IGNvbmdlc3Rp
b24gY29udHJvbCBjb250ZXh0IChpLmUuIHRoZSBmbG93IGlkZW50aWZpZWQgYXMgc2hhcmluZyB0
aGUNCj4gPj4gc2FtZSBib3R0bGUgbmVjaykgLSBhbmQgdGhlIGFwcC0gaW50ZXJhY3Rpb25zIGRy
YWZ0IGFza3MgZm9yIHRoZSBzYW1lDQo+ID4+IHBvc3NpYmlsaXR5IHRvIGJlIHByb3ZpZGVkLiBU
aGUgc2NyZWFtIGNvdXBsZWQgY2MgYWxzbyBhbGxvdyBmb3Igc3VjaA0KPiA+PiBwcmlvcml0aXph
dGlvbiB0byBiZSBkb25lIGluIHRoYXQgc3VjaCBjYW4gYmUgYWNoaWV2ZWQgYnkgc2NoZWR1bGlu
Zw0KPiA+PiBwcmlvcml0aWVzIGluIGJldHdlZW4gdGhlIG11bHRpcGxlIFJUUCBzdHJlYW1zIHRo
YXQgb25lIENDIGNvbnRleHQNCj4gPj4gc2VydmVzIChoZXJlIHNjcmVhbSBtb2RlbCBpcyB0aGUg
c2FtZSBtb2RlbCBhcyBzY3RwIG11bHRpLXN0cmVhbSBjYw0KPiA+Zm9sbG93cykuDQo+ID4+IEhP
V0VWRVIgd2hhdCB0aGUgIHNjcmVhbSBtb2RlbCBkb2VzIG5vdCBkaXJlY3RseSBhbGxvdyBmb3Ig
LSBhcyAgZmFyDQo+ID4+IGFzIEkgY2FuIHNlZSAtIGlzIHByaW9yaXRpemVkIGNvdXBsaW5nIGlu
IGJldHdlZW4gbXVsdGlwbGUgUlRQIGZsb3dzDQo+ID4+IHRoYXQgZG8gbm90IHVzZSB0aGUgc2Ft
ZSBVRFAgc29ja2V0L2Nvbm5lY3Rpb24gdHVwbGUgLS0gQW5kIHRoZW4gSQ0KPiA+PiBzdGFydCB3
b25kZXIgaWYgdGhlIHN0cmVhbSBtb2RlbCBpcyB0aGUgcmlnaHQgb25lLg0KPiA+W1phaGVkdXp6
YW1hbiBTYXJrZXJdIEkgYmVsaWV2ZSB5b3VyIGludGVycHJldGF0aW9uIG9mIGEgc2NyZWFtDQo+
ID5jb250cm9sbGVyIGNvbnRyb2xsaW5nIG11bHRpcGxlIFJUUCBmbG93cyBvbmx5IHdpdGggc2Ft
ZSAiVURQDQo+IHNvY2tldC9jb25uZWN0aW9uIHR1cGxlIg0KPiA+aXMgY29taW5nIGZyb20gYSBw
cmV2aW91cyByZXBseSB3aGVyZSBpdCB3YXMgc2FpZCB0aGUgY29udHJvbGxlcg0KPiA+Y29udHJv
bHMgZmxvd3Mgb25seSB0b3dhcmRzIHNhbWUgZGVzdGluYXRpb24uIEkgdGhpbmsgdGhlIGNvcnJl
Y3QgdGhpbmcNCj4gPnRvIHNheSBpcywgdGhlIFJUUCBwYWNrZXQgcGFzc2luZyB0aHJvdWdoIHRo
ZSBhIHNjcmVhbSB0cmFuc21pc3Npb24NCj4gPnNjaGVkdWxlciBtb3JlIG9mIGxlc3Mgc2hvd2lu
ZyBzYW1lIGNoYXJhY3RlcmlzdGljcywgbGlrZSBzaGFyaW5nIHNhbWUNCj4gPmJvdHRsZW5lY2su
IEhlbmNlIGlmIHRoZXJlIGlzIGEgc3lzdGVtIGxpa2UgU0JEIGFscmVhZHkgYWxsb3dzIG11bHRp
cGxlDQo+ID5SVFAgZmxvd3Mgd2l0aCBkaWZmZXJlbnQgZGVzdGluYXRpb24gdG8gYmUgaWRlbnRp
ZmllZCBhcyBzaGFyaW5nIHRoZQ0KPiA+c2FtZSBib3R0bGVuZWNrIHRoZW4gcHJpb3JpdGl6YXRp
b25zIGNhbiBiZSBhcHBsaWVkIHRvIGFsbCB0aG9zZSBmbG93cw0KPiA+Ynkgc2FtZSB0cmFuc21p
c3Npb24gc2NoZWR1bGVyLg0KPiA+SW4gdGhlIGltcGxlbWVudGF0aW9uIG9mIHNjcmVhbSB0aGVy
ZSBpcyBhIG1ldGhvZCB0byByZWdpc3RlciBhIFJUUA0KPiA+ZmxvdyB0byBhIHNjcmVhbSBjb250
cm9sbGVyIHdoaWNoIHdpbGwgYmUgY29uZ2VzdGlvbiBjb250cm9sbGVkIGJ5IHRoZQ0KPiA+dGhh
dCBwYXJ0aWN1bGFyIHNjcmVhbSBjb250cm9sbGVyICh0aGUgdHJhbnNtaXNzaW9uIHNjaGVkdWxl
ciByZXNpZGVzDQo+ID5pbiB0aGUgc2NyZWFtIGNvbnRyb2wpLg0KPiA+VGhpcyBhbHNvIG1lYW5z
IHRoZSBzY3JlYW0gY29udHJvbGxlciBoYXMgdG8gZ2V0IHRoZSBpbmZvcm1hdGlvbiBmcm9tDQo+
ID50aGUgUlRDUCBmZWVkYmFja3MgZm9yIHRoZSByZXNwZWN0aXZlIHJlZ2lzdGVyZWQgZmxvd3Mu
DQo+ID5IZW5jZSwgeW91ciBpbnRlcnByZXRhdGlvbiBvZiAiIHRoZSBzY3JlYW0gbW9kZWwgZG9l
cyBub3QgZGlyZWN0bHkNCj4gPmFsbG93IGZvciBwcmlvcml0aXplZCBjb3VwbGluZyBpbiBiZXR3
ZWVuIG11bHRpcGxlIFJUUCBmbG93cyB0aGF0IGRvDQo+ID5ub3QgdXNlIHRoZSBzYW1lIFVEUCBz
b2NrZXQvY29ubmVjdGlvbiB0dXBsZSAiIGlzIG5vdCBjb21wbGV0ZWx5IHRydWUuDQo+ID4NCj4g
Pj4gUG9zc2libHkgb25lIGNhbiBzZWUgdGhlIHNjcmVhbSBtb2RlbCBhcyBpbnRyb2R1Y2luZyBv
bmUgbW9yZSBsZXZlbA0KPiA+PiBpbiB0aGUgY291cGxlZCBjYyBtb2RlbCAtIGkuZS4sIHByaW9y
aXRpemVkIGNvdXBsaW5nIGluIGJldHdlZW4gdGhlDQo+ID4+IGZsb3dzIHVzaW5nIHRoZSBzYW1l
IFVEUCBzb2NrZXQvVURQIHR1cGxlIGlzIGRvbmUgYnkgbWVhbnMgb2Ygc2NyZWFtDQo+ID4+IHRy
YW5zbWlzc2lvbiBzY2hlZHVsaW5nIHByaW9yaXRpZXMgYW5kIHRoZW4gY291cGxlZCBjb25nZXN0
aW9uDQo+ID4+IGNvbnRyb2wgZm9sbG93aW5nIHRoZSB3ZWx6bCBtb2RlbCBvbiB0b3Agb2YgdGhp
cywgd2hlbiBtb3JlICJhZHZhbmNlZCINCj4gPj4gY291cGxpbmcgb3IgU0JEIGRldGVjdGlvbiBp
cyBkZXNpcmVkIG9yIHJlbGV2YW50IGluIGJldHdlZW4gZmxvd3MNCj4gPj4gc2hhcmluZyB0aGUg
c2FtZSBib3R0bGVuZWNrLCBidXQgbm90IHVzaW5nIHRoZSBzYW1lIFVEUCBzb2NrZXQvVURQIHR1
cGxlLg0KPiA+W1phaGVkdXp6YW1hbiBTYXJrZXJdIFNDUmVBTSBtb2RlbCBkb2VzIG5vdCBzaW1w
bHkgYXNzdW1lcyB0aGUNCj4gPmV4aXN0ZW5jZSBvZiBjb3VwbGVkLWNjIGJ5IGRlZmF1bHQuIEFz
IFNDUmVBTSBhbHJlYWR5IHVzZXMgYQ0KPiA+dHJhbnNtaXNzaW9uIHNjaGVkdWxlciBpdCBpcyBl
YXN5IHRvIGltcGxlbWVudCAicHJpb3JpdGl6YXRpb24gY291cGxpbmciIHRoZXJlLg0KPiA+Pg0K
PiA+PiBJIHN1cHBvc2UgdGhhdCBpdCBzaG91bGQgYmUgdXAgdG8gaW1wbGVtZW50YXRpb25zIGhv
dyB0aGV5IHdhbnQgdG8NCj4gPj4gaW1wbGVtZW50IGNvdXBsZWQgY2MgYW5kIGlmIHRoZXkgd2Fu
dCBhIGxldmVsZWQgYXBwcm9hY2ggYXMgdGhlIG9uZQ0KPiA+PiBqdXN0IGRlc2NyaWJlZCBvciBh
IG1vcmUgImRpcmVjdCIgYXBwcm9hY2ggd2hlcmUgZWFjaCBSVFAgZmxvd3MgaXMNCj4gPj4gaGFu
ZGxlZCBpbmRpdmlkdWFsbHkgZnJvbSBhIENDIHBlcnNwZWN0aXZlIGFuZCB0aGUgY291cGxlZCB2
aWENCj4gPj4gY291cGxlZCBjYw0KPiA+KHdlemx6KS4NCj4gPltaYWhlZHV6emFtYW4gU2Fya2Vy
XSBJIGJlbGlldmUgZm9yIGltcGxlbWVudGVycyBkbyBoYXZlIGEgY2hvaWNlLg0KPiA+SG93ZXZl
ciwgaWYgdGhleSBkZWNpZGVkIHRvIGltcGxlbWVudCBTQ1JlQU0gdGhleSBoYXZlIGFuIGVhc3kN
Cj4gPmFsdGVybmF0aXZlIGZvciBjb3VwbGVkLWNjIGFzIE1pY2hhZWwgVyBoaW1zZWxmIHNheXMu
DQo+ID4+DQo+ID4+IE9uIHRoZSBvdGhlciBoYW5kIHRoZSBvbmUgc2hvdWxkIHVuZGVyc3RhbmQg
d2hhdCB3b3VsZCBiZSB0aGUNCj4gPj4gbW90aXZhdGlvbiBmb3IgYSBsZXZlbGVkIGFwcHJvYWNo
IHdvdWxkIGJlIC0gYWxzbyBiZWNhdXNlIGl0IHNlZW1zIHRvDQo+ID4+IGdpdmUgYSBtb3JlIGNv
bXBsZXggbW9kZWwgIC0gSXMgaXQgc28gdGhhdCBzdWNoIGlzIG1vdGl2YXRlZCBieSAtIGZvcg0K
PiA+PiBleGFtcGxlOg0KPiA+Pw0KPiA+Pg0KPiA+PiAqIEl0IGlzIG1vcmUgZWZmaWNpZW50IChv
dmVyaGVhZCBvciBwcm90b2NvbCwgc3RhdGUsIHdoYXRldmVyKSB0bw0KPiA+PiBtYW5hZ2UgQ0Mg
b24gIm9uZSIgbXVsdGktc3RyZWFtIFJUUCBiYXNpcyB3aGVuIHN1Y2ggaXMgcG9zc2libGUgLSAg
YXMNCj4gPj4gc2NyZWFtIGRvZXMgPyBhbmQgdGhlcmVmb3JlIHRoZSBsZXZlbGVkIGFwcHJvYWNo
IGhhcyBhZHZhbnRhZ2VzIGZyb20NCj4gPj4gYSBnZW5lcmFsIHBlcnNwZWN0aXZlIG9yIHBvc3Np
Ymx5IGl0IGlzIGFkdmFudGFnZW91cyBpbiB0aGUNCj4gPj4gcGFydGljdWxhciBzaXR1YXRpb25z
IHdoZXJlIHRoZSBkZWZhdWx0IChidWlsZC0NCj4gPj4gaW4pIHNoYXJlZCBib3R0bGUtbmVjayBk
ZXRlY3Rpb24gb2Ygc2NyZWFtIGlzIHRoZSBvbmx5IG9uZSByZWxldmFudCA/DQo+ID4+DQo+ID5b
WmFoZWR1enphbWFuIFNhcmtlcl0gSSBiZWxpZXZlIEkgaGF2ZSBhbHJlYWR5IGFuc3dlcmVkIHRo
b3NlIHF1ZXN0aW9ucy4NCg==


From nobody Mon Jul 20 01:03:09 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23EF1A01FC for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 01:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 cx3tALFMXeTS for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 01:03:03 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EA4E1A0158 for <rmcat@ietf.org>; Mon, 20 Jul 2015 01:03:03 -0700 (PDT)
Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZH62P-0000wn-Mo; Mon, 20 Jul 2015 10:03:01 +0200
Received: from dhcp-9ad4.meeting.ietf.org ([31.133.154.212]) by mail-mx3.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1ZH62P-00047v-6A; Mon, 20 Jul 2015 10:03:01 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <07529396e89526f834a8816d1d2502c7@mail.gmail.com>
Date: Mon, 20 Jul 2015 10:02:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2070.6)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 5 msgs/h 1 sum rcpts/h 7 sum msgs/h 2 total rcpts 31176 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 868A91A6C6A23E5140E743AFE6EE28CBAC65AE98
X-UiO-SPAM-Test: remote_host: 31.133.154.212 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 3 max/h 2 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/zI8T1yfIhQ1xCwXaF4lc0C8ceSM>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, rmcat@ietf.org, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 20 Jul 2015 08:03:07 -0000

> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> HI,
>=20
> Yes - there is the possibility to implement coupled congestion control =
with
> scheduling priorities,
> There is no doubt about that :-), Indeed SCTP does it and scream does =
it.
> But it is not so well-described in the
> scream draft how exactly the prioritization works and which means an
> application has to define different priorities.
> (For information then for SCTP a number of different scheduling
> possibilities is described in
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>=20
> Then for RMCAT coupled congestion control  we have the Wezlz, Safiqul
> proposal where the coupled is done
> in-between per flow-CC contexts by prioritization on manipulation of =
the
> cwnd.
> And the we also have, a not so detailed proposal/description, on how =
the
> same can be achieved via scheduling (scream).
> It should be ok to allow for different ways to implement coupling, but =
we
> should then eventually have one document that describes both
> solutions. Shouldn't we ?

I think so. There is already (short, because it's so simple) text about =
scheduling in coupled-cc and we can extend that and make it stand out =
more clearly (now it's in the intro I think).

Cheers,
Michael


From nobody Mon Jul 20 04:32:08 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A111A1ADB for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 04:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.705
X-Spam-Level: 
X-Spam-Status: No, score=-2.705 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 GwdIwD636gSQ for <rmcat@ietfa.amsl.com>; Mon, 20 Jul 2015 04:32:03 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 65F031A1A90 for <rmcat@ietf.org>; Mon, 20 Jul 2015 04:32:03 -0700 (PDT)
Received: from dhcp-9873.meeting.ietf.org (dhcp-9873.meeting.ietf.org [31.133.152.115]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 19AD71B00118 for <rmcat@ietf.org>; Mon, 20 Jul 2015 12:31:57 +0100 (BST)
Message-ID: <55ACDC2F.9030600@erg.abdn.ac.uk>
Date: Mon, 20 Jul 2015 13:31:59 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: rmcat@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/rGIw43sFRtnNc1hKkZ405utBV-o>
Subject: [rmcat] RMCAT - RAW NOTES
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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, 20 Jul 2015 11:32:06 -0000

Here are raw notes from the meeting today (as best I can) - Chairs 
please can you tidy and merge any other notes,

Gorry

---

RMCAT at IETF-93 (Prague)
Chairs: Mirja Kuehlewind & Karen Nielson
Monday, July 20, Morning Session I 0900-1130
Room Name: Congress Hall II

Agenda and Note Well was presented.

WG Status
Chairs

Evaluation Criteria (authors)
- Feedback appreciated
- Requirements will be removed from this document.
Mirja: There is also a TCP model from Mozilla for traffic with document 
size.
Mirja: There is also a video model draft that could be referenced.
Zahed Sarker: The test draft describes the video sequence, you need to 
separate hard and soft content that are to be used for evaluation. Where 
does this fit?
Karen: This is evaluation criteria. The question is whether this should 
be a separate draft because of the size?
-: What do we do with video sequences?
-: We could define a few video sources, and refer to the other draft for 
traces. Maybe pick slow and high motion cases?
-: I support choosing a few sequences. We could also use a synthetic codec.
Karen: Suggest text on these topics, and we can discuss on the list.
Zahed: I think we can also explore screen casting. Screen casting of 
video is hard.
Francesco: We can build a list of frame sizes output, and agree a codec.
Chairs: Please discuss in the video source model presentation.

Evaluation Tests
Karen: Document should be stable (please comment now), but will be kept 
open until we can finalise, and we can also explore whether the wireless 
test cases will be added or separate.
Zahed: One thing is when you change the bandwidth, you can use UDP 
background traffic to synthesise capacity changes. ... traffic bursts 
induce congestion.
Mirja (at Mic): Changing the capacity of the link is different, because 
the UDP traffic can be dropped in congestion.
Chairs: Authors will update the draft.

Scream
Zahed: Code is now available. The draft is expected to be finished in 
August.

Volunteers to review the next version:
?
Stefan Holmer
Mo Zanty
Varun Singh

FEC
Varun Singh
Mo Zanty: I think the FEC work should be generic, most codecs are 
already doing this.
-: Agree
Chairs: We need some evaluation of this. Can you do this anytime some?
We’ll work on this.
Xiaoqin Zhu: I am not following this draft in detail, but plan to look 
at this.
Stefan: We do use FEC. No current plans for this approach, but that can 
change.
Mirja: There is a use of probing for higher capacity using FEC.
Chairs: Please send inputs via the list.

Interactions with RTP and Codecs
Mo Zanty: There will be series of 3 drafts that will exist.
Colin Perkins: I think it is important this draft talks about these 
things, I think the draft is useful as it stands.
Karen: There are about 7 different interactions that are possible. Some 
are used in RMCAT. We should try to understand why not all are supported 
by RMCAT, can we understand which have been considered?
Colin Perkins: I think there are things here that may be useful if other 
approaches are being considered. At the moment everyone appears to be 
taking the same approach. I think it depends on the types of CC being used.
Karen: If the things are beyond the scope of the current WG, then we 
could perhaps put these in an appendix.
Colin: We should not take this out, we could highlight this.
Mo: We can make this document says more clearly which ones are mandatory 
for RMCAT.
Varun Singh: We seem to have started evaluation, this had implications 
in VP8. The impact on H.264 may be different, it could be too early to 
know which are needed. There could be feedback to netvc.
Xiaoqin Zhu: There is the allowed rate, and there other interactions, 
and some we have not explored.
Ahed: What is the plan in RMCAT? How do I test?
Mirja: The test cases do not use a real encoder, there could be a 
synthetic codec used to work with encoder people.
Stefan: We can’t assume that a codec has knobs, apart from requesting a 
keyframe; or setting a new bit rate target.
Chairs: There seems to be a way forward. The scope was not to cut-out 
options, but to label these. We propose to adopt the draft as a basis 
for a WG draft. Should the WG adopt this document?
[Hum for adoption; No Hum against]
Chairs: The chairs will confirm this adoption on the list.

Chairs: We would like to seem common terminology between candidates 
(this could be a separate document). We would like to see all candidates 
individually specify all the things needed to implement.
Gorry Fairhurst: It may be useful to write a terminology ID, even if 
this is not published, just to agree common text.
Mo: I think the framework will be needed to compare.
Harald A: If we want common terminology that we have to agree this.
Mo & Zahed: I could edit.
Xiaoqin Zhu: -
Michael Ramahlo: We need to pin down the framework and terminology.
Gorry: I suggest the WG tries to start with a short I-D that may not 
even be adopted (or published), but then could allow the text to be 
copied into the draft.
Chairs: Please propose some common terminology.

Wireless Test Case
Coupled congestion control with RTP
Safiqul Islam
draft-welzl-rmcat-coupled-cc-05 (milestone group-cc)
Zahed: I like the use of the test case. Did all the streams have the 
same priority?
Safiqul: They did have the same priority. We can provide priority 
results at the next IETF.
Zahed: It would be nice to look at mismatches in the encoding rate and 
give insight on what happens when the codec does not behave (exceeds 
what is asked for).
Michael Welzl: Encoder not using the rate is the start/stop test case. 
If we need another test case, then please ask.
Zahed; I am suggesting not to use the CBR traffic for evaluation.
Chairs: Please discuss the test cases.

Chairs: Is this ready for adoption?
Zahed: I am unsure about prioritisation status.
Karen (at Mic): If we adopt this draft then we adopt this solution, but 
not the scheduling approach.
Michael: The scheduling part is something that could be described, we 
can describe the pros and cons in the next document.
Karen: Are you saying your solution would have the same behaviour if you 
do scheduling.
Zahed: Why is there one flow stated?
Michael: This is not quite the same.
Chairs: Is there an option to move the scheduling to an appendix?
Zahed: We do not seem to have 2 competing ideas. If someone uses SCREAM 
they may already have this. Is there a question about whether we use one 
solution or another?
Mirja: I think this is not super useful.
Karen: The specification between streams seems to change the way.
Mirja: I think this is just two different ways.
Karen: I think you get a different behaviour when you use the two 
approaches. Priorities can be different,
Mirja: This could go into the interface draft.
Karen: I think we have just one method, if we come up with a different 
approach then we will see the interface.
Gorry: I do not know what the chairs are adopting. Has the WG agreed 
there is one approach and that we will put scheduling out of scope for 
this document, and then make other adoption calls for other drafts with 
other approaches?
Mirja: This is what we discussed with the authors. The WG chairs made a 
decision after the last meeting to ask to adopt this.
Xiaoqin Zhu: How easy is it to extend the approach?
Zahed: Are we saying this is a proposal to just specify this for NADA?
Michael: This is for NADA - it says this in the abstract.
Mirja: We think we should adopt this just for NADA.
Zahed: What about other approaches?
Karen: I think SCREAM needs to also be described and allow the document 
to either be updated or to a separate draft. There may also be two 
different mechanisms that can be described in two separate drafts.
Michael Ramahlo: I see it is in scope for the milestone. If we need to 
make a call today for acceptance, so we do not end up with a separate 
document for each of the candidates (N-squared documents]. Is the call 
just to adopt a solution for NADA?
Mirja: I think we start with NADA.
Karen: I think we can try to make new additions to the document for 
other schemes and see if this works.
Chairs: I would like to see the adoption call for this draft as a basis 
for a WG version with the scheduling moved to the appendix. We suggest 
we adopt this.
[Hums for some; Hums against few].
Chairs: Did we hear hums against?
[No Hum]

Update on GCC
Stefan Holmer
draft-alvestrand-rmcat-congestion-03 (milestone cc-cand)

Chairs: We saw promising results yesterday that suggest this is ready.
-: I was not there. What was discussed yesterday?
Mirja: They compared GCC with NADA. I think this is a reasonable way to 
move forward.
Chairs: The Chairs would like to know if this should be adopted.
[Hums for few; Hums against none].

Update on NADA
Xiaoqing Zhu
draft-ietf-rmcat-nada-00 (milestone cc-cand)

Xiaoqing Zhu: We’d be interested in implementation feedback from people 
reading the draft.
Chairs: Please send comments to the list and update the draft.
Chairs: Who is willing to review?
Stefan Holmer
Zahed Sarker
Anurag Bhargava

WiFi test cases
Xiaoqing Zhu
draft-fu-rmcat-wifi-test-case-01 (milestone eval-criteria)

Chairs: Please send comments to the mailing list.
Xiaoqing Zhu: Can we ask if this can become a working group item, that 
can be merged with the cellular case?
Zahed: It would be nice try some alternatives, and find out a little 
more. I’d be interested in what the WG thinks.
Mirja: I think this text belongs in the WG document.
Zahed: I would like to know if this is ready to merge.
Varun: I can see why it may be merged. I think the ones we saw yesterday 
were good.
Michael Ramahlo: I see differences in the way these operate. I would 
like to know what the WG thinks.
Mirja: Do you want to merge all of this into the document?
Varun: The ones that are tested make sense.
Zahed: We can merge, but I have not tried these things, so I do not know 
what you want me to do.
Chairs: Please go ahead and merge this.

Modeling Video Traffic Sources for RMCAT Evaluations
Sergio Mena de la Cruz
draft-zhu-rmcat-video-traffic-source-02 (milestone eval-criteria)

Mirja: No time for comments.
Chairs: How many people have read the draft?
[4 people had read the draft]
Chairs: Please read the document and discuss on the mailing list.

Shared Bottleneck Detection for Coupled Congestion Control for RTP Media
David Hayes
draft-ietf-rmcat-sbd-00 (milestone group-cc)

Matt Mathis: There is work in IPPM that talked about this?
Brian Tramell (as IPPM Chair): We should send a note to the list saying 
this isn’t useful for this use case. It would be interesting to know if 
the IPPM metrics match those from this draft.
Matt: Yes I see this as a lightweight approach and you may like to 
quantify the differences.
Chairs: What are the next steps?
David: We are going to revise.

----


Note:


From nobody Wed Jul 22 02:06:54 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 101511ACEDB for <rmcat@ietfa.amsl.com>; Wed, 22 Jul 2015 02:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 rxgu94B8GDEa for <rmcat@ietfa.amsl.com>; Wed, 22 Jul 2015 02:06:51 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A4BD1AD082 for <rmcat@ietf.org>; Wed, 22 Jul 2015 02:06:50 -0700 (PDT)
X-AuditID: c1b4fb2d-f79176d00000321c-2d-55af5d28d89c
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 78.1B.12828.82D5FA55; Wed, 22 Jul 2015 11:06:48 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0210.002; Wed, 22 Jul 2015 11:06:47 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: Michael Welzl <michawe@ifi.uio.no>, "Karen E. E. Nielsen" <karen.nielsen@tieto.com>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwA==
Date: Wed, 22 Jul 2015 09:06:47 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no>
In-Reply-To: <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3Rlcjdn2owfk9khaHWmeyWPw4u5PV YsPqKSwWq29+YHNg8Viy5CeTx+rVD5k9Dj0P8jj24StbAEsUl01Kak5mWWqRvl0CV8bbc/NZ CyYqVbQ1P2dpYLwk3cXIySEhYCKx+MpCVghbTOLCvfVsXYxcHEICRxkl9ryexgzhLGaUuNP/ hR2kik3ARmLloe+MILaIQKTEt7OrWUGKmAUeMkr8+TWZBSQhDFTU/qafFaLIVuLkn+VMEHaW xIG+M2BxFgFViWe3zoPV8wr4SnyYuQlq2wtmiUsPbrCBJDgF7CSWTl0EtplRQFbi/vd7YA3M AuISt57MZ4K4W0BiyZ7zzBC2qMTLx/+g/lGSWHt4O1S9nsSNqVPYIGxtiWULXzNDLBaUODnz CcsERrFZSMbOQtIyC0nLLCQtCxhZVjGKFqcWF+emGxnrpRZlJhcX5+fp5aWWbGIExtrBLb91 dzCufu14iFGAg1GJh1fh57pQIdbEsuLK3EOM0hwsSuK8MzbnhQoJpCeWpGanphakFsUXleak Fh9iZOLglGpgnL3ollea3nXZP+IbourWfb51NsNumkOAdBa7o9TyJvOijkD38ywZJy5pcGn+ ktUJnHkscKrBsvWfvT813tl+M7w38LR6oGm6h0aFUZee69Kq30HVNQKHLy3dFTNl+n6X67/c evcXzOl2dEnb8fafu4XRgdVpJdr3eSaI/59XUhD+7Q/Dl9/5SizFGYmGWsxFxYkAPs2dPJYC AAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/gy4QzwekcAggGQC8FfUEeLDUEYk>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 22 Jul 2015 09:06:53 -0000

Hi

Still waiting for the summer to show up so I'll try to chime in while this =
subject is at least luke-warm. I may be slow with follow up on this, sorry =
for that in advance.

Stream prio in SCReAM is outlined in section A.2 in the draft (https://tool=
s.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28 ). In its function it=
 resembles fq-codel quite a lot in the sense that streams that do not get s=
cheduled at a given scheduling instant gets a credit that is used to increa=
se the chance of being scheduled at the next scheduling instant. A configur=
able scheduling priority determines how much credit  that is given. Looking=
 in the https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf draft=
 I would say that this resembles the "Weighted Fair Queueing Scheduler"  th=
e most. Some additional means are needed to make this work well in reality =
though (see below).=20

The benefit with doing scheduling priority and a common congestion control =
is an increased probability that the path capacity is fully utilized, if a =
stream becomes idle (for instance no or little activity in one video source=
) , more resources are allocated to the other sources. And this is achieved=
 with no or very little additional delay buildup on the sender side.
Another benefit with stream prioritization is that it is easier to make one=
 congestion control behave well (low delay /packet loss) esp. on a wireless=
 link. We have simulation results that supports this statement albeit in th=
e different context (QUIC congestion control evolution).
The stream prioritization and one congestion control of course require that=
 all the streams share the same bottleneck characteristics

With that said, the biggest challenge I have seen this far is the large var=
iability of esp. video sources. Sit still in front of the camera and the ou=
tput rate becomes very low regardless the target rate, move yourself closer=
 to the camera and bang!!.. you get 2Mbps video rate all of a sudden. This =
variability causes issues with stream prioritization in the sense that less=
 variable streams may be pushed back. Additional code is therefore added in=
 SCReAM to correct this anomaly and ensure a (weighted) fair distribution  =
over a longer time scale. Still as mentioned in the SCReAM draft, this need=
s to be tried out some more. I have sofar only simulated video sources with=
 variability to see that the current implementation is reasonably robust.
The bottom line here is that, while scheduling of streams with static prope=
rties may be considered simple, real video may be a taller order.=20

/Ingemar




> -----Original Message-----
> From: Michael Welzl [mailto:michawe@ifi.uio.no]
> Sent: den 20 juli 2015 10:03
> To: Karen E. E. Nielsen
> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org; Mirja
> K=FChlewind
> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>=20
>=20
> > On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
> <karen.nielsen@tieto.com> wrote:
> >
> > HI,
> >
> > Yes - there is the possibility to implement coupled congestion control
> > with scheduling priorities, There is no doubt about that :-), Indeed
> > SCTP does it and scream does it.
> > But it is not so well-described in the scream draft how exactly the
> > prioritization works and which means an application has to define
> > different priorities.
> > (For information then for SCTP a number of different scheduling
> > possibilities is described in
> > http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
> >
> > Then for RMCAT coupled congestion control  we have the Wezlz, Safiqul
> > proposal where the coupled is done in-between per flow-CC contexts by
> > prioritization on manipulation of the cwnd.
> > And the we also have, a not so detailed proposal/description, on how
> > the same can be achieved via scheduling (scream).
> > It should be ok to allow for different ways to implement coupling, but
> > we should then eventually have one document that describes both
> > solutions. Shouldn't we ?
>=20
> I think so. There is already (short, because it's so simple) text about
> scheduling in coupled-cc and we can extend that and make it stand out mor=
e
> clearly (now it's in the intro I think).
>=20
> Cheers,
> Michael


From nobody Wed Jul 22 02:16:30 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E08A1ACEDF for <rmcat@ietfa.amsl.com>; Wed, 22 Jul 2015 02:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7LDfxuP-Bqig for <rmcat@ietfa.amsl.com>; Wed, 22 Jul 2015 02:16:26 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C6C71A2182 for <rmcat@ietf.org>; Wed, 22 Jul 2015 02:16:25 -0700 (PDT)
Received: from mail-mx6.uio.no ([129.240.10.40]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZHq8U-0000Ak-TI; Wed, 22 Jul 2015 11:16:22 +0200
Received: from dhcp-8973.meeting.ietf.org ([31.133.137.115]) by mail-mx6.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZHq8T-00019V-R8; Wed, 22 Jul 2015 11:16:22 +0200
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se>
Mime-Version: 1.0 (1.0)
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no>
X-Mailer: iPhone Mail (11D201)
From: Michael Welzl <michawe@ifi.uio.no>
Date: Wed, 22 Jul 2015 11:16:21 +0200
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 6 msgs/h 2 sum rcpts/h 11 sum msgs/h 6 total rcpts 31358 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, MIME_QP_LONG_LINE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 8D986D32D6D94A7434B828D3EAE4A98F6BC9813E
X-UiO-SPAM-Test: remote_host: 31.133.137.115 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 3 max/h 2 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/GzA5S3pJSuZkyScKObue-dJnV2s>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 22 Jul 2015 09:16:29 -0000

understood; i think these details are beyond the scope of our coupling draft=
 which focuses on a different method.

cheers
michael

Sent from my iPhone

> On 22. juli 2015, at 11:06, Ingemar Johansson S <ingemar.s.johansson@erics=
son.com> wrote:
>=20
> Hi
>=20
> Still waiting for the summer to show up so I'll try to chime in while this=
 subject is at least luke-warm. I may be slow with follow up on this, sorry f=
or that in advance.
>=20
> Stream prio in SCReAM is outlined in section A.2 in the draft (https://too=
ls.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28 ). In its function it=
 resembles fq-codel quite a lot in the sense that streams that do not get sc=
heduled at a given scheduling instant gets a credit that is used to increase=
 the chance of being scheduled at the next scheduling instant. A configurabl=
e scheduling priority determines how much credit  that is given. Looking in t=
he https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf draft I wou=
ld say that this resembles the "Weighted Fair Queueing Scheduler"  the most.=
 Some additional means are needed to make this work well in reality though (=
see below).=20
>=20
> The benefit with doing scheduling priority and a common congestion control=
 is an increased probability that the path capacity is fully utilized, if a s=
tream becomes idle (for instance no or little activity in one video source) ,=
 more resources are allocated to the other sources. And this is achieved wit=
h no or very little additional delay buildup on the sender side.
> Another benefit with stream prioritization is that it is easier to make on=
e congestion control behave well (low delay /packet loss) esp. on a wireless=
 link. We have simulation results that supports this statement albeit in the=
 different context (QUIC congestion control evolution).
> The stream prioritization and one congestion control of course require tha=
t all the streams share the same bottleneck characteristics
>=20
> With that said, the biggest challenge I have seen this far is the large va=
riability of esp. video sources. Sit still in front of the camera and the ou=
tput rate becomes very low regardless the target rate, move yourself closer t=
o the camera and bang!!.. you get 2Mbps video rate all of a sudden. This var=
iability causes issues with stream prioritization in the sense that less var=
iable streams may be pushed back. Additional code is therefore added in SCRe=
AM to correct this anomaly and ensure a (weighted) fair distribution  over a=
 longer time scale. Still as mentioned in the SCReAM draft, this needs to be=
 tried out some more. I have sofar only simulated video sources with variabi=
lity to see that the current implementation is reasonably robust.
> The bottom line here is that, while scheduling of streams with static prop=
erties may be considered simple, real video may be a taller order.=20
>=20
> /Ingemar
>=20
>=20
>=20
>=20
>> -----Original Message-----
>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>> Sent: den 20 juli 2015 10:03
>> To: Karen E. E. Nielsen
>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org; Mirja
>> K=C3=BChlewind
>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>=20
>>=20
>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
>>> <karen.nielsen@tieto.com> wrote:
>>>=20
>>> HI,
>>>=20
>>> Yes - there is the possibility to implement coupled congestion control
>>> with scheduling priorities, There is no doubt about that :-), Indeed
>>> SCTP does it and scream does it.
>>> But it is not so well-described in the scream draft how exactly the
>>> prioritization works and which means an application has to define
>>> different priorities.
>>> (For information then for SCTP a number of different scheduling
>>> possibilities is described in
>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>>>=20
>>> Then for RMCAT coupled congestion control  we have the Wezlz, Safiqul
>>> proposal where the coupled is done in-between per flow-CC contexts by
>>> prioritization on manipulation of the cwnd.
>>> And the we also have, a not so detailed proposal/description, on how
>>> the same can be achieved via scheduling (scream).
>>> It should be ok to allow for different ways to implement coupling, but
>>> we should then eventually have one document that describes both
>>> solutions. Shouldn't we ?
>>=20
>> I think so. There is already (short, because it's so simple) text about
>> scheduling in coupled-cc and we can extend that and make it stand out mor=
e
>> clearly (now it's in the intro I think).
>>=20
>> Cheers,
>> Michael
>=20


From nobody Thu Jul 23 04:43:16 2015
Return-Path: <davihay@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 552371AC42D; Thu, 23 Jul 2015 04:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 M2XMClbelEgB; Thu, 23 Jul 2015 04:43:09 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E63F1AC41F; Thu, 23 Jul 2015 04:43:09 -0700 (PDT)
Received: from mail-mx2.uio.no ([129.240.10.30]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <davihay@ifi.uio.no>) id 1ZIEu3-00061d-Nc; Thu, 23 Jul 2015 13:43:07 +0200
Received: from dhcp-9b81.meeting.ietf.org ([31.133.155.129] helo=[192.168.42.61]) by mail-mx2.uio.no with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) user davihay@ifi.uio.no (Exim 4.80) (envelope-from <davihay@ifi.uio.no>) id 1ZIEu3-0002sY-1z; Thu, 23 Jul 2015 13:43:07 +0200
Date: Thu, 23 Jul 2015 13:43:05 +0200
From: David Hayes <davihay@ifi.uio.no>
To: ippm@ietf.org, "rmcat@ietf.org" <rmcat@ietf.org>
Message-Id: <1437651785.12450.1@smtp.uio.no>
X-Mailer: geary/0.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 3 msgs/h 2 sum rcpts/h 4 sum msgs/h 3 total rcpts 323 max rcpts/h 10 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 903739DBCBB60E372AD7797656F287A25944C5D5
X-UiO-SPAM-Test: remote_host: 31.133.155.129 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 5 max/h 2 blacklist 0 greylist 0 ratelimit 0
X-UiOonly: C12D9D6F1E6C8B7FE975C0870078FE8A4A1AFADE
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/y0195k0yWivwb_LKFy3wLr1TCUg>
Subject: [rmcat] Fwd: [ippm] RMCAT SBD
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Jul 2015 11:43:12 -0000

Hi

I neglected to put the RMCAT list in the original mail. When 
responding, please send to both lists.

Thanks!

David

---------- Forwarded message ----------

 From: David Hayes <davihay@ifi.uio.no>
Subject: [ippm] RMCAT SBD
Date: Wed, 22 Jul 2015 17:19:04 +0200
To: ippm@ietf.org

Hi!

When I presented an update of this work on Shared Bottleneck Detection
(SBD) in the RMCAT meeting a few days ago it was suggested that I send
a note to the ippm group due to the delay metrics the mechanism uses.

The slides for the recent update can be found here:
http://www.ietf.org/proceedings/93/slides/slides-93-rmcat-5.pdf

The draft can be found here:
https://tools.ietf.org/html/draft-ietf-rmcat-sbd-01

The item that prompted this suggestion was the use of a metric
based on Mean Absolute Deviation (MAD).


Some notes on the context of this work:

The mechanism uses summary type statistics describing the shape of
flow OWDs in order to distinguish between flows sharing or not sharing
a common bottleneck. It is designed to be light weight and store a
minimum of state, with potential for having a future OS kernel
implementation (though this is not a requirement or need in the RMCAT
context where it will be in the browser).

MAD (modified to enable 'on the fly' calculation without
storing OWD measurements) is used as a variability measure. It is being
put forward as a more robust measure (for SBD purposes) than the
earlier measure based on a type of PDV measure (max-mean per period T).

The purpose of these measures is for grouping flows not for measuring
performance, however, the use of these metrics may be of interest to
the group. The work may also benefit from the expertise in the ippm
community.

Kind regards,

David

PS

If you are wondering about the examples at the end of the slides
that have significant clock skew and some graph based clustering, these
are work in progress and the mechanisms that facilitates these have not
yet been annunciated in the draft.



-- 

-------------------------
David Hayes
davihay@ifi.uio.no
Department of Informatics
University of Oslo

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm



From nobody Fri Jul 24 01:42:26 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B801A1A2E for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 01:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 r7o175glRd5K for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 01:42:22 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E491A1A9D for <rmcat@ietf.org>; Fri, 24 Jul 2015 01:42:20 -0700 (PDT)
X-AuditID: c1b4fb25-f79046d000007f53-b2-55b1fa6bfe30
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 72.CC.32595.B6AF1B55; Fri, 24 Jul 2015 10:42:19 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0210.002; Fri, 24 Jul 2015 10:42:18 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiA=
Date: Fri, 24 Jul 2015 08:42:17 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no>
In-Reply-To: <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyM+JvjW72r42hBueuClkcap3JYvHj7E5W iw2rp7BYrL75gc2BxWPJkp9MHqtXP2T2OPQ8yOPYh69sASxRXDYpqTmZZalF+nYJXBnH375l KrhiXvFo63X2BsY5Zl2MnBwSAiYSE16uYoWwxSQu3FvP1sXIxSEkcJRR4uPiN4wQzmJGicmb p7CAVLEJ2EisPPSdEcQWEVCTOLF8NVgHs8AtRokzT6+DFQkDFbW/6WeFKLKVOPlnOROEXSZx 6exeIJuDg0VAVWLRIm8Qk1fAV+LSTjGIXQ9YJM4tOwA2hlPATmLRxfnsIDajgKzE/e/3wOLM AuISt57MZ4K4WkBiyZ7zzBC2qMTLx/+gvlGSWHt4OwvIfGYBTYn1u/QhWhUlpnQ/BBvJKyAo cXLmE5YJjGKzkEydhdAxC0nHLCQdCxhZVjGKFqcWJ+WmGxnrpRZlJhcX5+fp5aWWbGIExtjB Lb9VdzBefuN4iFGAg1GJh1dhzsZQIdbEsuLK3EOM0hwsSuK8MzbnhQoJpCeWpGanphakFsUX leakFh9iZOLglGpg5DzBrnb6R25upO1Lq5SpBXr3WOQv7u+7meq11V6jlftIovqHtoYX1sUu GgJ9BcVfP235orP/eqN1/QSP5WmPq1U+9WmGP00/rmbF/ernbr6ENx26ZU6+8dNM0/hMUtb1 RDk3Tf7epfHf/W/m76O7jL9LvGI1EPpYzjXT4uq6movlr2I26MgrsRRnJBpqMRcVJwIAv91G TZICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/aKniuW_QqcYPKF-3rLSx1cTRsdI>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Jul 2015 08:42:24 -0000

SGkNCg0KTm90IHN1cmUgSSBnZXQgaXQuIA0KRG8geW91IG1lYW4gdGhhdCBjb3VwbGluZyBhbGdv
IGlzIGltbXVuZSB0byB2aWRlbyBjb2RlciBvdXRwdXQgcmF0ZSB2YXJpYXRpb24gPw0KDQovSW5n
ZW1hcg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE1pY2hhZWwgV2Vs
emwgW21haWx0bzptaWNoYXdlQGlmaS51aW8ubm9dDQo+IFNlbnQ6IGRlbiAyMiBqdWxpIDIwMTUg
MTE6MTYNCj4gVG86IEluZ2VtYXIgSm9oYW5zc29uIFMNCj4gQ2M6IEthcmVuIEUuIEUuIE5pZWxz
ZW47IFphaGVkdXp6YW1hbiBTYXJrZXI7IHJtY2F0QGlldGYub3JnOyBNaXJqYQ0KPiBLw7xobGV3
aW5kDQo+IFN1YmplY3Q6IFJlOiBbcm1jYXRdIFJldmlldyBvZiBkcmFmdC1pZXRmLXJtY2F0LXNj
cmVhbS1jYy0wMQ0KPiANCj4gdW5kZXJzdG9vZDsgaSB0aGluayB0aGVzZSBkZXRhaWxzIGFyZSBi
ZXlvbmQgdGhlIHNjb3BlIG9mIG91ciBjb3VwbGluZyBkcmFmdA0KPiB3aGljaCBmb2N1c2VzIG9u
IGEgZGlmZmVyZW50IG1ldGhvZC4NCj4gDQo+IGNoZWVycw0KPiBtaWNoYWVsDQo+IA0KPiBTZW50
IGZyb20gbXkgaVBob25lDQo+IA0KPiA+IE9uIDIyLiBqdWxpIDIwMTUsIGF0IDExOjA2LCBJbmdl
bWFyIEpvaGFuc3NvbiBTDQo+IDxpbmdlbWFyLnMuam9oYW5zc29uQGVyaWNzc29uLmNvbT4gd3Jv
dGU6DQo+ID4NCj4gPiBIaQ0KPiA+DQo+ID4gU3RpbGwgd2FpdGluZyBmb3IgdGhlIHN1bW1lciB0
byBzaG93IHVwIHNvIEknbGwgdHJ5IHRvIGNoaW1lIGluIHdoaWxlIHRoaXMNCj4gc3ViamVjdCBp
cyBhdCBsZWFzdCBsdWtlLXdhcm0uIEkgbWF5IGJlIHNsb3cgd2l0aCBmb2xsb3cgdXAgb24gdGhp
cywgc29ycnkgZm9yDQo+IHRoYXQgaW4gYWR2YW5jZS4NCj4gPg0KPiA+IFN0cmVhbSBwcmlvIGlu
IFNDUmVBTSBpcyBvdXRsaW5lZCBpbiBzZWN0aW9uIEEuMiBpbiB0aGUgZHJhZnQNCj4gKGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMSNwYWdl
LTI4ICkuIEluIGl0cw0KPiBmdW5jdGlvbiBpdCByZXNlbWJsZXMgZnEtY29kZWwgcXVpdGUgYSBs
b3QgaW4gdGhlIHNlbnNlIHRoYXQgc3RyZWFtcyB0aGF0IGRvDQo+IG5vdCBnZXQgc2NoZWR1bGVk
IGF0IGEgZ2l2ZW4gc2NoZWR1bGluZyBpbnN0YW50IGdldHMgYSBjcmVkaXQgdGhhdCBpcyB1c2Vk
IHRvDQo+IGluY3JlYXNlIHRoZSBjaGFuY2Ugb2YgYmVpbmcgc2NoZWR1bGVkIGF0IHRoZSBuZXh0
IHNjaGVkdWxpbmcgaW5zdGFudC4gQQ0KPiBjb25maWd1cmFibGUgc2NoZWR1bGluZyBwcmlvcml0
eSBkZXRlcm1pbmVzIGhvdyBtdWNoIGNyZWRpdCAgdGhhdCBpcyBnaXZlbi4NCj4gTG9va2luZyBp
biB0aGUgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9wZGYvZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLW5k
YXRhLTA0LnBkZg0KPiBkcmFmdCBJIHdvdWxkIHNheSB0aGF0IHRoaXMgcmVzZW1ibGVzIHRoZSAi
V2VpZ2h0ZWQgRmFpciBRdWV1ZWluZw0KPiBTY2hlZHVsZXIiICB0aGUgbW9zdC4gU29tZSBhZGRp
dGlvbmFsIG1lYW5zIGFyZSBuZWVkZWQgdG8gbWFrZSB0aGlzIHdvcmsNCj4gd2VsbCBpbiByZWFs
aXR5IHRob3VnaCAoc2VlIGJlbG93KS4NCj4gPg0KPiA+IFRoZSBiZW5lZml0IHdpdGggZG9pbmcg
c2NoZWR1bGluZyBwcmlvcml0eSBhbmQgYSBjb21tb24gY29uZ2VzdGlvbg0KPiBjb250cm9sIGlz
IGFuIGluY3JlYXNlZCBwcm9iYWJpbGl0eSB0aGF0IHRoZSBwYXRoIGNhcGFjaXR5IGlzIGZ1bGx5
IHV0aWxpemVkLCBpZiBhDQo+IHN0cmVhbSBiZWNvbWVzIGlkbGUgKGZvciBpbnN0YW5jZSBubyBv
ciBsaXR0bGUgYWN0aXZpdHkgaW4gb25lIHZpZGVvIHNvdXJjZSkgLA0KPiBtb3JlIHJlc291cmNl
cyBhcmUgYWxsb2NhdGVkIHRvIHRoZSBvdGhlciBzb3VyY2VzLiBBbmQgdGhpcyBpcyBhY2hpZXZl
ZCB3aXRoDQo+IG5vIG9yIHZlcnkgbGl0dGxlIGFkZGl0aW9uYWwgZGVsYXkgYnVpbGR1cCBvbiB0
aGUgc2VuZGVyIHNpZGUuDQo+ID4gQW5vdGhlciBiZW5lZml0IHdpdGggc3RyZWFtIHByaW9yaXRp
emF0aW9uIGlzIHRoYXQgaXQgaXMgZWFzaWVyIHRvIG1ha2Ugb25lDQo+IGNvbmdlc3Rpb24gY29u
dHJvbCBiZWhhdmUgd2VsbCAobG93IGRlbGF5IC9wYWNrZXQgbG9zcykgZXNwLiBvbiBhIHdpcmVs
ZXNzDQo+IGxpbmsuIFdlIGhhdmUgc2ltdWxhdGlvbiByZXN1bHRzIHRoYXQgc3VwcG9ydHMgdGhp
cyBzdGF0ZW1lbnQgYWxiZWl0IGluIHRoZQ0KPiBkaWZmZXJlbnQgY29udGV4dCAoUVVJQyBjb25n
ZXN0aW9uIGNvbnRyb2wgZXZvbHV0aW9uKS4NCj4gPiBUaGUgc3RyZWFtIHByaW9yaXRpemF0aW9u
IGFuZCBvbmUgY29uZ2VzdGlvbiBjb250cm9sIG9mIGNvdXJzZSByZXF1aXJlDQo+ID4gdGhhdCBh
bGwgdGhlIHN0cmVhbXMgc2hhcmUgdGhlIHNhbWUgYm90dGxlbmVjayBjaGFyYWN0ZXJpc3RpY3MN
Cj4gPg0KPiA+IFdpdGggdGhhdCBzYWlkLCB0aGUgYmlnZ2VzdCBjaGFsbGVuZ2UgSSBoYXZlIHNl
ZW4gdGhpcyBmYXIgaXMgdGhlIGxhcmdlDQo+IHZhcmlhYmlsaXR5IG9mIGVzcC4gdmlkZW8gc291
cmNlcy4gU2l0IHN0aWxsIGluIGZyb250IG9mIHRoZSBjYW1lcmEgYW5kIHRoZSBvdXRwdXQNCj4g
cmF0ZSBiZWNvbWVzIHZlcnkgbG93IHJlZ2FyZGxlc3MgdGhlIHRhcmdldCByYXRlLCBtb3ZlIHlv
dXJzZWxmIGNsb3NlciB0bw0KPiB0aGUgY2FtZXJhIGFuZCBiYW5nISEuLiB5b3UgZ2V0IDJNYnBz
IHZpZGVvIHJhdGUgYWxsIG9mIGEgc3VkZGVuLiBUaGlzDQo+IHZhcmlhYmlsaXR5IGNhdXNlcyBp
c3N1ZXMgd2l0aCBzdHJlYW0gcHJpb3JpdGl6YXRpb24gaW4gdGhlIHNlbnNlIHRoYXQgbGVzcw0K
PiB2YXJpYWJsZSBzdHJlYW1zIG1heSBiZSBwdXNoZWQgYmFjay4gQWRkaXRpb25hbCBjb2RlIGlz
IHRoZXJlZm9yZSBhZGRlZCBpbg0KPiBTQ1JlQU0gdG8gY29ycmVjdCB0aGlzIGFub21hbHkgYW5k
IGVuc3VyZSBhICh3ZWlnaHRlZCkgZmFpciBkaXN0cmlidXRpb24NCj4gb3ZlciBhIGxvbmdlciB0
aW1lIHNjYWxlLiBTdGlsbCBhcyBtZW50aW9uZWQgaW4gdGhlIFNDUmVBTSBkcmFmdCwgdGhpcyBu
ZWVkcw0KPiB0byBiZSB0cmllZCBvdXQgc29tZSBtb3JlLiBJIGhhdmUgc29mYXIgb25seSBzaW11
bGF0ZWQgdmlkZW8gc291cmNlcyB3aXRoDQo+IHZhcmlhYmlsaXR5IHRvIHNlZSB0aGF0IHRoZSBj
dXJyZW50IGltcGxlbWVudGF0aW9uIGlzIHJlYXNvbmFibHkgcm9idXN0Lg0KPiA+IFRoZSBib3R0
b20gbGluZSBoZXJlIGlzIHRoYXQsIHdoaWxlIHNjaGVkdWxpbmcgb2Ygc3RyZWFtcyB3aXRoIHN0
YXRpYw0KPiBwcm9wZXJ0aWVzIG1heSBiZSBjb25zaWRlcmVkIHNpbXBsZSwgcmVhbCB2aWRlbyBt
YXkgYmUgYSB0YWxsZXIgb3JkZXIuDQo+ID4NCj4gPiAvSW5nZW1hcg0KPiA+DQo+ID4NCj4gPg0K
PiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IE1pY2hhZWwg
V2VsemwgW21haWx0bzptaWNoYXdlQGlmaS51aW8ubm9dDQo+ID4+IFNlbnQ6IGRlbiAyMCBqdWxp
IDIwMTUgMTA6MDMNCj4gPj4gVG86IEthcmVuIEUuIEUuIE5pZWxzZW4NCj4gPj4gQ2M6IFphaGVk
dXp6YW1hbiBTYXJrZXI7IEluZ2VtYXIgSm9oYW5zc29uIFM7IHJtY2F0QGlldGYub3JnOyBNaXJq
YQ0KPiA+PiBLw7xobGV3aW5kDQo+ID4+IFN1YmplY3Q6IFJlOiBbcm1jYXRdIFJldmlldyBvZiBk
cmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMQ0KPiA+Pg0KPiA+Pg0KPiA+Pj4+IE9uIDIwLiBq
dWwuIDIwMTUsIGF0IDA3LjMyLCBLYXJlbiBFbGlzYWJldGggRWdlZGUgTmllbHNlbg0KPiA+Pj4g
PGthcmVuLm5pZWxzZW5AdGlldG8uY29tPiB3cm90ZToNCj4gPj4+DQo+ID4+PiBISSwNCj4gPj4+
DQo+ID4+PiBZZXMgLSB0aGVyZSBpcyB0aGUgcG9zc2liaWxpdHkgdG8gaW1wbGVtZW50IGNvdXBs
ZWQgY29uZ2VzdGlvbg0KPiA+Pj4gY29udHJvbCB3aXRoIHNjaGVkdWxpbmcgcHJpb3JpdGllcywg
VGhlcmUgaXMgbm8gZG91YnQgYWJvdXQgdGhhdA0KPiA+Pj4gOi0pLCBJbmRlZWQgU0NUUCBkb2Vz
IGl0IGFuZCBzY3JlYW0gZG9lcyBpdC4NCj4gPj4+IEJ1dCBpdCBpcyBub3Qgc28gd2VsbC1kZXNj
cmliZWQgaW4gdGhlIHNjcmVhbSBkcmFmdCBob3cgZXhhY3RseSB0aGUNCj4gPj4+IHByaW9yaXRp
emF0aW9uIHdvcmtzIGFuZCB3aGljaCBtZWFucyBhbiBhcHBsaWNhdGlvbiBoYXMgdG8gZGVmaW5l
DQo+ID4+PiBkaWZmZXJlbnQgcHJpb3JpdGllcy4NCj4gPj4+IChGb3IgaW5mb3JtYXRpb24gdGhl
biBmb3IgU0NUUCBhIG51bWJlciBvZiBkaWZmZXJlbnQgc2NoZWR1bGluZw0KPiA+Pj4gcG9zc2li
aWxpdGllcyBpcyBkZXNjcmliZWQgaW4NCj4gPj4+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLy4pDQo+ID4+Pg0KPiA+Pj4gVGhlbiBm
b3IgUk1DQVQgY291cGxlZCBjb25nZXN0aW9uIGNvbnRyb2wgIHdlIGhhdmUgdGhlIFdlemx6LA0K
PiA+Pj4gU2FmaXF1bCBwcm9wb3NhbCB3aGVyZSB0aGUgY291cGxlZCBpcyBkb25lIGluLWJldHdl
ZW4gcGVyIGZsb3ctQ0MNCj4gPj4+IGNvbnRleHRzIGJ5IHByaW9yaXRpemF0aW9uIG9uIG1hbmlw
dWxhdGlvbiBvZiB0aGUgY3duZC4NCj4gPj4+IEFuZCB0aGUgd2UgYWxzbyBoYXZlLCBhIG5vdCBz
byBkZXRhaWxlZCBwcm9wb3NhbC9kZXNjcmlwdGlvbiwgb24gaG93DQo+ID4+PiB0aGUgc2FtZSBj
YW4gYmUgYWNoaWV2ZWQgdmlhIHNjaGVkdWxpbmcgKHNjcmVhbSkuDQo+ID4+PiBJdCBzaG91bGQg
YmUgb2sgdG8gYWxsb3cgZm9yIGRpZmZlcmVudCB3YXlzIHRvIGltcGxlbWVudCBjb3VwbGluZywN
Cj4gPj4+IGJ1dCB3ZSBzaG91bGQgdGhlbiBldmVudHVhbGx5IGhhdmUgb25lIGRvY3VtZW50IHRo
YXQgZGVzY3JpYmVzIGJvdGgNCj4gPj4+IHNvbHV0aW9ucy4gU2hvdWxkbid0IHdlID8NCj4gPj4N
Cj4gPj4gSSB0aGluayBzby4gVGhlcmUgaXMgYWxyZWFkeSAoc2hvcnQsIGJlY2F1c2UgaXQncyBz
byBzaW1wbGUpIHRleHQNCj4gPj4gYWJvdXQgc2NoZWR1bGluZyBpbiBjb3VwbGVkLWNjIGFuZCB3
ZSBjYW4gZXh0ZW5kIHRoYXQgYW5kIG1ha2UgaXQNCj4gPj4gc3RhbmQgb3V0IG1vcmUgY2xlYXJs
eSAobm93IGl0J3MgaW4gdGhlIGludHJvIEkgdGhpbmspLg0KPiA+Pg0KPiA+PiBDaGVlcnMsDQo+
ID4+IE1pY2hhZWwNCj4gPg0K


From nobody Fri Jul 24 01:57:29 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77F731A1BCC for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 01:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 cNeCWi_SXcUe for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 01:57:24 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F5ED1A21B2 for <rmcat@ietf.org>; Fri, 24 Jul 2015 01:57:24 -0700 (PDT)
Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZIYnB-0007Km-Jx; Fri, 24 Jul 2015 10:57:21 +0200
Received: from dhcp-9931.meeting.ietf.org ([31.133.153.49]) by mail-mx3.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1ZIYnA-0007bS-J5; Fri, 24 Jul 2015 10:57:21 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se>
Date: Fri, 24 Jul 2015 10:57:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.2070.6)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 6 msgs/h 2 sum rcpts/h 6 sum msgs/h 2 total rcpts 31476 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: DE4AC3A0DCDE35024FC4F6279703CDCA8264375E
X-UiO-SPAM-Test: remote_host: 31.133.153.49 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 3 max/h 2 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/B2FwX7r7k-DJumVbjCkUk0vIdM0>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Jul 2015 08:57:27 -0000

No.

Our algo lets you assign priorities, and they are valid at the time you =
set them, they just give you a portion of the overall rate and it =
applies as soon as you set it.
If  you want to adjust priorities based on the coder output rate =
variation, you can implement this using our algo or with a scheduler. A =
scheduler operates per packet, we operate per time, so =
implementation-wise it's a bit different.

My point is only: whether you do it with our algorithm or without a =
scheduler, I think this should not be in our draft  (and I'm neutral =
about: should it be in the SCReAM draft or separate from it).

Cheers,
Michael

=20
> On 24. jul. 2015, at 10.42, Ingemar Johansson S =
<ingemar.s.johansson@ericsson.com> wrote:
>=20
> Hi
>=20
> Not sure I get it.=20
> Do you mean that coupling algo is immune to video coder output rate =
variation ?
>=20
> /Ingemar
>=20
>> -----Original Message-----
>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>> Sent: den 22 juli 2015 11:16
>> To: Ingemar Johansson S
>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>> K=C3=BChlewind
>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>=20
>> understood; i think these details are beyond the scope of our =
coupling draft
>> which focuses on a different method.
>>=20
>> cheers
>> michael
>>=20
>> Sent from my iPhone
>>=20
>>> On 22. juli 2015, at 11:06, Ingemar Johansson S
>> <ingemar.s.johansson@ericsson.com> wrote:
>>>=20
>>> Hi
>>>=20
>>> Still waiting for the summer to show up so I'll try to chime in =
while this
>> subject is at least luke-warm. I may be slow with follow up on this, =
sorry for
>> that in advance.
>>>=20
>>> Stream prio in SCReAM is outlined in section A.2 in the draft
>> (https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28 ). =
In its
>> function it resembles fq-codel quite a lot in the sense that streams =
that do
>> not get scheduled at a given scheduling instant gets a credit that is =
used to
>> increase the chance of being scheduled at the next scheduling =
instant. A
>> configurable scheduling priority determines how much credit  that is =
given.
>> Looking in the =
https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf
>> draft I would say that this resembles the "Weighted Fair Queueing
>> Scheduler"  the most. Some additional means are needed to make this =
work
>> well in reality though (see below).
>>>=20
>>> The benefit with doing scheduling priority and a common congestion
>> control is an increased probability that the path capacity is fully =
utilized, if a
>> stream becomes idle (for instance no or little activity in one video =
source) ,
>> more resources are allocated to the other sources. And this is =
achieved with
>> no or very little additional delay buildup on the sender side.
>>> Another benefit with stream prioritization is that it is easier to =
make one
>> congestion control behave well (low delay /packet loss) esp. on a =
wireless
>> link. We have simulation results that supports this statement albeit =
in the
>> different context (QUIC congestion control evolution).
>>> The stream prioritization and one congestion control of course =
require
>>> that all the streams share the same bottleneck characteristics
>>>=20
>>> With that said, the biggest challenge I have seen this far is the =
large
>> variability of esp. video sources. Sit still in front of the camera =
and the output
>> rate becomes very low regardless the target rate, move yourself =
closer to
>> the camera and bang!!.. you get 2Mbps video rate all of a sudden. =
This
>> variability causes issues with stream prioritization in the sense =
that less
>> variable streams may be pushed back. Additional code is therefore =
added in
>> SCReAM to correct this anomaly and ensure a (weighted) fair =
distribution
>> over a longer time scale. Still as mentioned in the SCReAM draft, =
this needs
>> to be tried out some more. I have sofar only simulated video sources =
with
>> variability to see that the current implementation is reasonably =
robust.
>>> The bottom line here is that, while scheduling of streams with =
static
>> properties may be considered simple, real video may be a taller =
order.
>>>=20
>>> /Ingemar
>>>=20
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>> Sent: den 20 juli 2015 10:03
>>>> To: Karen E. E. Nielsen
>>>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org; Mirja
>>>> K=C3=BChlewind
>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>=20
>>>>=20
>>>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
>>>>> <karen.nielsen@tieto.com> wrote:
>>>>>=20
>>>>> HI,
>>>>>=20
>>>>> Yes - there is the possibility to implement coupled congestion
>>>>> control with scheduling priorities, There is no doubt about that
>>>>> :-), Indeed SCTP does it and scream does it.
>>>>> But it is not so well-described in the scream draft how exactly =
the
>>>>> prioritization works and which means an application has to define
>>>>> different priorities.
>>>>> (For information then for SCTP a number of different scheduling
>>>>> possibilities is described in
>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>>>>>=20
>>>>> Then for RMCAT coupled congestion control  we have the Wezlz,
>>>>> Safiqul proposal where the coupled is done in-between per flow-CC
>>>>> contexts by prioritization on manipulation of the cwnd.
>>>>> And the we also have, a not so detailed proposal/description, on =
how
>>>>> the same can be achieved via scheduling (scream).
>>>>> It should be ok to allow for different ways to implement coupling,
>>>>> but we should then eventually have one document that describes =
both
>>>>> solutions. Shouldn't we ?
>>>>=20
>>>> I think so. There is already (short, because it's so simple) text
>>>> about scheduling in coupled-cc and we can extend that and make it
>>>> stand out more clearly (now it's in the intro I think).
>>>>=20
>>>> Cheers,
>>>> Michael
>>>=20


From nobody Fri Jul 24 02:14:49 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FB81A87EC for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 02:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 1N_tBBBck3BB for <rmcat@ietfa.amsl.com>; Fri, 24 Jul 2015 02:14:34 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F22BD1A8854 for <rmcat@ietf.org>; Fri, 24 Jul 2015 02:14:33 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-05-55b201f7b2d2
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 06.9D.29223.7F102B55; Fri, 24 Jul 2015 11:14:32 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0210.002; Fri, 24 Jul 2015 11:14:31 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiD//+NBAAAEo4fA
Date: Fri, 24 Jul 2015 09:14:31 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no>
In-Reply-To: <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGfG3RvcH46ZQg52b2SwOtc5ksfhxdier xYbVU1gsVt/8wObA4rFkyU8mj9WrHzJ7HHoe5HHsw1e2AJYoLpuU1JzMstQifbsErozWSZtY CjZ5VTQvu8PSwLjHo4uRg0NCwERi9yaJLkZOIFNM4sK99WxdjFwcQgJHGSUu7zoB5SxmlHj5 cjE7SBWbgI3EykPfGUFsEQE1iRPLV4MVMQtMYZI4f+ocWEIYqKj9TT8rRJGtxMk/y5lAikQE mhglLt6cyAaSYBFQlTjd+Z4JxOYV8JVYNeEOI8S6G6wSmyZcYAFJcArYSczY+hZsNaOArMT9 7/fA4swC4hK3nsxngjhcQGLJnvPMELaoxMvH/1ghbCWJtYe3s4D8ySygKbF+lz5Eq6LElO6H 7BB7BSVOznzCMoFRbBaSqbMQOmYh6ZiFpGMBI8sqRtHi1OKk3HQjI73Uoszk4uL8PL281JJN jMA4O7jlt8EOxpfPHQ8xCnAwKvHwKszZGCrEmlhWXJl7iFGag0VJnHfG5rxQIYH0xJLU7NTU gtSi+KLSnNTiQ4xMHJxSDYxq3NO8uRQmy22eN+Wi4tbjdy811YYJvO9mv8r8fCv/1sbvf+L8 /39UKVfdsbvQeE1S3WmrudIy9Qrd51YuUnTW3jab8VVhuv6imIjkTTHW7158eOi+/8e+lvtm s3N7gie8iF52c6/JeVfrtz+F+Z8vq1gXb5z/2mTO9jWxV42vO2hsUFNhCX6qxFKckWioxVxU nAgA5LsvZpQCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/RctqdP-V4g6mWsr82AXDN6WRkUI>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Jul 2015 09:14:37 -0000

T0ssIHVuZGVyc3RhbmQuIA0KDQpObyBoYXJkIGZlZWxpbmdzIGZyb20gbXkgc2lkZSBpZiB0aGUg
c2NoZWR1bGluZyBkZXRhaWxzIGFyZSByZW1vdmVkIGZyb20gdGhlIFNDUmVBTSBkcmFmdCAoYW5k
IHBvc3NpYmx5IHB1dCBlbHNld2hlcmUpLCBpdCBpcyBjdXJyZW50bHkgb25seSBhbiBhcHBlbmRp
eCBzZWN0aW9uIGFueXdheS4gDQoNCkkgdGhpbmsgaG93ZXZlciB0aGUgc2NoZWR1bGluZyBpdCB3
aWxsIHJlbWFpbiBpbiB0aGUgcnVubmluZyBjb2RlIChDKysgY29kZSBhbmQgT1dSKSBhdCBsZWFz
dCB1bnRpbCBhIGdvb2QgYWx0ZXJuYXRpdmUgaXMgYXZhaWxhYmxlLg0KDQovSW5nZW1hcg0KDQoN
Cj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogTWljaGFlbCBXZWx6bCBbbWFp
bHRvOm1pY2hhd2VAaWZpLnVpby5ub10NCj4gU2VudDogZGVuIDI0IGp1bGkgMjAxNSAxMDo1Nw0K
PiBUbzogSW5nZW1hciBKb2hhbnNzb24gUw0KPiBDYzogS2FyZW4gRS4gRS4gTmllbHNlbjsgWmFo
ZWR1enphbWFuIFNhcmtlcjsgcm1jYXRAaWV0Zi5vcmc7IE1pcmphDQo+IEvDvGhsZXdpbmQNCj4g
U3ViamVjdDogUmU6IFtybWNhdF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtcm1jYXQtc2NyZWFtLWNj
LTAxDQo+IA0KPiBOby4NCj4gDQo+IE91ciBhbGdvIGxldHMgeW91IGFzc2lnbiBwcmlvcml0aWVz
LCBhbmQgdGhleSBhcmUgdmFsaWQgYXQgdGhlIHRpbWUgeW91IHNldA0KPiB0aGVtLCB0aGV5IGp1
c3QgZ2l2ZSB5b3UgYSBwb3J0aW9uIG9mIHRoZSBvdmVyYWxsIHJhdGUgYW5kIGl0IGFwcGxpZXMg
YXMgc29vbiBhcw0KPiB5b3Ugc2V0IGl0Lg0KPiBJZiAgeW91IHdhbnQgdG8gYWRqdXN0IHByaW9y
aXRpZXMgYmFzZWQgb24gdGhlIGNvZGVyIG91dHB1dCByYXRlIHZhcmlhdGlvbiwgeW91DQo+IGNh
biBpbXBsZW1lbnQgdGhpcyB1c2luZyBvdXIgYWxnbyBvciB3aXRoIGEgc2NoZWR1bGVyLiBBIHNj
aGVkdWxlciBvcGVyYXRlcw0KPiBwZXIgcGFja2V0LCB3ZSBvcGVyYXRlIHBlciB0aW1lLCBzbyBp
bXBsZW1lbnRhdGlvbi13aXNlIGl0J3MgYSBiaXQgZGlmZmVyZW50Lg0KPiANCj4gTXkgcG9pbnQg
aXMgb25seTogd2hldGhlciB5b3UgZG8gaXQgd2l0aCBvdXIgYWxnb3JpdGhtIG9yIHdpdGhvdXQg
YQ0KPiBzY2hlZHVsZXIsIEkgdGhpbmsgdGhpcyBzaG91bGQgbm90IGJlIGluIG91ciBkcmFmdCAg
KGFuZCBJJ20gbmV1dHJhbCBhYm91dDoNCj4gc2hvdWxkIGl0IGJlIGluIHRoZSBTQ1JlQU0gZHJh
ZnQgb3Igc2VwYXJhdGUgZnJvbSBpdCkuDQo+IA0KPiBDaGVlcnMsDQo+IE1pY2hhZWwNCj4gDQo+
IA0KPiA+IE9uIDI0LiBqdWwuIDIwMTUsIGF0IDEwLjQyLCBJbmdlbWFyIEpvaGFuc3NvbiBTDQo+
IDxpbmdlbWFyLnMuam9oYW5zc29uQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+ID4NCj4gPiBIaQ0K
PiA+DQo+ID4gTm90IHN1cmUgSSBnZXQgaXQuDQo+ID4gRG8geW91IG1lYW4gdGhhdCBjb3VwbGlu
ZyBhbGdvIGlzIGltbXVuZSB0byB2aWRlbyBjb2RlciBvdXRwdXQgcmF0ZQ0KPiB2YXJpYXRpb24g
Pw0KPiA+DQo+ID4gL0luZ2VtYXINCj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPiA+PiBGcm9tOiBNaWNoYWVsIFdlbHpsIFttYWlsdG86bWljaGF3ZUBpZmkudWlvLm5vXQ0K
PiA+PiBTZW50OiBkZW4gMjIganVsaSAyMDE1IDExOjE2DQo+ID4+IFRvOiBJbmdlbWFyIEpvaGFu
c3NvbiBTDQo+ID4+IENjOiBLYXJlbiBFLiBFLiBOaWVsc2VuOyBaYWhlZHV6emFtYW4gU2Fya2Vy
OyBybWNhdEBpZXRmLm9yZzsgTWlyamENCj4gPj4gS8O8aGxld2luZA0KPiA+PiBTdWJqZWN0OiBS
ZTogW3JtY2F0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gPj4N
Cj4gPj4gdW5kZXJzdG9vZDsgaSB0aGluayB0aGVzZSBkZXRhaWxzIGFyZSBiZXlvbmQgdGhlIHNj
b3BlIG9mIG91cg0KPiA+PiBjb3VwbGluZyBkcmFmdCB3aGljaCBmb2N1c2VzIG9uIGEgZGlmZmVy
ZW50IG1ldGhvZC4NCj4gPj4NCj4gPj4gY2hlZXJzDQo+ID4+IG1pY2hhZWwNCj4gPj4NCj4gPj4g
U2VudCBmcm9tIG15IGlQaG9uZQ0KPiA+Pg0KPiA+Pj4gT24gMjIuIGp1bGkgMjAxNSwgYXQgMTE6
MDYsIEluZ2VtYXIgSm9oYW5zc29uIFMNCj4gPj4gPGluZ2VtYXIucy5qb2hhbnNzb25AZXJpY3Nz
b24uY29tPiB3cm90ZToNCj4gPj4+DQo+ID4+PiBIaQ0KPiA+Pj4NCj4gPj4+IFN0aWxsIHdhaXRp
bmcgZm9yIHRoZSBzdW1tZXIgdG8gc2hvdyB1cCBzbyBJJ2xsIHRyeSB0byBjaGltZSBpbg0KPiA+
Pj4gd2hpbGUgdGhpcw0KPiA+PiBzdWJqZWN0IGlzIGF0IGxlYXN0IGx1a2Utd2FybS4gSSBtYXkg
YmUgc2xvdyB3aXRoIGZvbGxvdyB1cCBvbiB0aGlzLA0KPiA+PiBzb3JyeSBmb3IgdGhhdCBpbiBh
ZHZhbmNlLg0KPiA+Pj4NCj4gPj4+IFN0cmVhbSBwcmlvIGluIFNDUmVBTSBpcyBvdXRsaW5lZCBp
biBzZWN0aW9uIEEuMiBpbiB0aGUgZHJhZnQNCj4gPj4gKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMSNwYWdlLTI4ICkuDQo+ID4+IEluIGl0
cyBmdW5jdGlvbiBpdCByZXNlbWJsZXMgZnEtY29kZWwgcXVpdGUgYSBsb3QgaW4gdGhlIHNlbnNl
IHRoYXQNCj4gPj4gc3RyZWFtcyB0aGF0IGRvIG5vdCBnZXQgc2NoZWR1bGVkIGF0IGEgZ2l2ZW4g
c2NoZWR1bGluZyBpbnN0YW50IGdldHMNCj4gPj4gYSBjcmVkaXQgdGhhdCBpcyB1c2VkIHRvIGlu
Y3JlYXNlIHRoZSBjaGFuY2Ugb2YgYmVpbmcgc2NoZWR1bGVkIGF0DQo+ID4+IHRoZSBuZXh0IHNj
aGVkdWxpbmcgaW5zdGFudC4gQSBjb25maWd1cmFibGUgc2NoZWR1bGluZyBwcmlvcml0eSBkZXRl
cm1pbmVzDQo+IGhvdyBtdWNoIGNyZWRpdCAgdGhhdCBpcyBnaXZlbi4NCj4gPj4gTG9va2luZyBp
biB0aGUNCj4gPj4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9wZGYvZHJhZnQtaWV0Zi10c3Z3Zy1z
Y3RwLW5kYXRhLTA0LnBkZg0KPiA+PiBkcmFmdCBJIHdvdWxkIHNheSB0aGF0IHRoaXMgcmVzZW1i
bGVzIHRoZSAiV2VpZ2h0ZWQgRmFpciBRdWV1ZWluZw0KPiA+PiBTY2hlZHVsZXIiICB0aGUgbW9z
dC4gU29tZSBhZGRpdGlvbmFsIG1lYW5zIGFyZSBuZWVkZWQgdG8gbWFrZSB0aGlzDQo+ID4+IHdv
cmsgd2VsbCBpbiByZWFsaXR5IHRob3VnaCAoc2VlIGJlbG93KS4NCj4gPj4+DQo+ID4+PiBUaGUg
YmVuZWZpdCB3aXRoIGRvaW5nIHNjaGVkdWxpbmcgcHJpb3JpdHkgYW5kIGEgY29tbW9uIGNvbmdl
c3Rpb24NCj4gPj4gY29udHJvbCBpcyBhbiBpbmNyZWFzZWQgcHJvYmFiaWxpdHkgdGhhdCB0aGUg
cGF0aCBjYXBhY2l0eSBpcyBmdWxseQ0KPiA+PiB1dGlsaXplZCwgaWYgYSBzdHJlYW0gYmVjb21l
cyBpZGxlIChmb3IgaW5zdGFuY2Ugbm8gb3IgbGl0dGxlDQo+ID4+IGFjdGl2aXR5IGluIG9uZSB2
aWRlbyBzb3VyY2UpICwgbW9yZSByZXNvdXJjZXMgYXJlIGFsbG9jYXRlZCB0byB0aGUNCj4gPj4g
b3RoZXIgc291cmNlcy4gQW5kIHRoaXMgaXMgYWNoaWV2ZWQgd2l0aCBubyBvciB2ZXJ5IGxpdHRs
ZSBhZGRpdGlvbmFsIGRlbGF5DQo+IGJ1aWxkdXAgb24gdGhlIHNlbmRlciBzaWRlLg0KPiA+Pj4g
QW5vdGhlciBiZW5lZml0IHdpdGggc3RyZWFtIHByaW9yaXRpemF0aW9uIGlzIHRoYXQgaXQgaXMg
ZWFzaWVyIHRvDQo+ID4+PiBtYWtlIG9uZQ0KPiA+PiBjb25nZXN0aW9uIGNvbnRyb2wgYmVoYXZl
IHdlbGwgKGxvdyBkZWxheSAvcGFja2V0IGxvc3MpIGVzcC4gb24gYQ0KPiA+PiB3aXJlbGVzcyBs
aW5rLiBXZSBoYXZlIHNpbXVsYXRpb24gcmVzdWx0cyB0aGF0IHN1cHBvcnRzIHRoaXMNCj4gPj4g
c3RhdGVtZW50IGFsYmVpdCBpbiB0aGUgZGlmZmVyZW50IGNvbnRleHQgKFFVSUMgY29uZ2VzdGlv
biBjb250cm9sDQo+IGV2b2x1dGlvbikuDQo+ID4+PiBUaGUgc3RyZWFtIHByaW9yaXRpemF0aW9u
IGFuZCBvbmUgY29uZ2VzdGlvbiBjb250cm9sIG9mIGNvdXJzZQ0KPiA+Pj4gcmVxdWlyZSB0aGF0
IGFsbCB0aGUgc3RyZWFtcyBzaGFyZSB0aGUgc2FtZSBib3R0bGVuZWNrDQo+ID4+PiBjaGFyYWN0
ZXJpc3RpY3MNCj4gPj4+DQo+ID4+PiBXaXRoIHRoYXQgc2FpZCwgdGhlIGJpZ2dlc3QgY2hhbGxl
bmdlIEkgaGF2ZSBzZWVuIHRoaXMgZmFyIGlzIHRoZQ0KPiA+Pj4gbGFyZ2UNCj4gPj4gdmFyaWFi
aWxpdHkgb2YgZXNwLiB2aWRlbyBzb3VyY2VzLiBTaXQgc3RpbGwgaW4gZnJvbnQgb2YgdGhlIGNh
bWVyYQ0KPiA+PiBhbmQgdGhlIG91dHB1dCByYXRlIGJlY29tZXMgdmVyeSBsb3cgcmVnYXJkbGVz
cyB0aGUgdGFyZ2V0IHJhdGUsIG1vdmUNCj4gPj4geW91cnNlbGYgY2xvc2VyIHRvIHRoZSBjYW1l
cmEgYW5kIGJhbmchIS4uIHlvdSBnZXQgMk1icHMgdmlkZW8gcmF0ZQ0KPiA+PiBhbGwgb2YgYSBz
dWRkZW4uIFRoaXMgdmFyaWFiaWxpdHkgY2F1c2VzIGlzc3VlcyB3aXRoIHN0cmVhbQ0KPiA+PiBw
cmlvcml0aXphdGlvbiBpbiB0aGUgc2Vuc2UgdGhhdCBsZXNzIHZhcmlhYmxlIHN0cmVhbXMgbWF5
IGJlIHB1c2hlZA0KPiA+PiBiYWNrLiBBZGRpdGlvbmFsIGNvZGUgaXMgdGhlcmVmb3JlIGFkZGVk
IGluIFNDUmVBTSB0byBjb3JyZWN0IHRoaXMNCj4gPj4gYW5vbWFseSBhbmQgZW5zdXJlIGEgKHdl
aWdodGVkKSBmYWlyIGRpc3RyaWJ1dGlvbiBvdmVyIGEgbG9uZ2VyIHRpbWUNCj4gPj4gc2NhbGUu
IFN0aWxsIGFzIG1lbnRpb25lZCBpbiB0aGUgU0NSZUFNIGRyYWZ0LCB0aGlzIG5lZWRzIHRvIGJl
IHRyaWVkDQo+ID4+IG91dCBzb21lIG1vcmUuIEkgaGF2ZSBzb2ZhciBvbmx5IHNpbXVsYXRlZCB2
aWRlbyBzb3VyY2VzIHdpdGggdmFyaWFiaWxpdHkNCj4gdG8gc2VlIHRoYXQgdGhlIGN1cnJlbnQg
aW1wbGVtZW50YXRpb24gaXMgcmVhc29uYWJseSByb2J1c3QuDQo+ID4+PiBUaGUgYm90dG9tIGxp
bmUgaGVyZSBpcyB0aGF0LCB3aGlsZSBzY2hlZHVsaW5nIG9mIHN0cmVhbXMgd2l0aA0KPiA+Pj4g
c3RhdGljDQo+ID4+IHByb3BlcnRpZXMgbWF5IGJlIGNvbnNpZGVyZWQgc2ltcGxlLCByZWFsIHZp
ZGVvIG1heSBiZSBhIHRhbGxlciBvcmRlci4NCj4gPj4+DQo+ID4+PiAvSW5nZW1hcg0KPiA+Pj4N
Cj4gPj4+DQo+ID4+Pg0KPiA+Pj4NCj4gPj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
PiA+Pj4+IEZyb206IE1pY2hhZWwgV2VsemwgW21haWx0bzptaWNoYXdlQGlmaS51aW8ubm9dDQo+
ID4+Pj4gU2VudDogZGVuIDIwIGp1bGkgMjAxNSAxMDowMw0KPiA+Pj4+IFRvOiBLYXJlbiBFLiBF
LiBOaWVsc2VuDQo+ID4+Pj4gQ2M6IFphaGVkdXp6YW1hbiBTYXJrZXI7IEluZ2VtYXIgSm9oYW5z
c29uIFM7IHJtY2F0QGlldGYub3JnOyBNaXJqYQ0KPiA+Pj4+IEvDvGhsZXdpbmQNCj4gPj4+PiBT
dWJqZWN0OiBSZTogW3JtY2F0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ybWNhdC1zY3JlYW0tY2Mt
MDENCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4+PiBPbiAyMC4ganVsLiAyMDE1LCBhdCAwNy4zMiwg
S2FyZW4gRWxpc2FiZXRoIEVnZWRlIE5pZWxzZW4NCj4gPj4+Pj4gPGthcmVuLm5pZWxzZW5AdGll
dG8uY29tPiB3cm90ZToNCj4gPj4+Pj4NCj4gPj4+Pj4gSEksDQo+ID4+Pj4+DQo+ID4+Pj4+IFll
cyAtIHRoZXJlIGlzIHRoZSBwb3NzaWJpbGl0eSB0byBpbXBsZW1lbnQgY291cGxlZCBjb25nZXN0
aW9uDQo+ID4+Pj4+IGNvbnRyb2wgd2l0aCBzY2hlZHVsaW5nIHByaW9yaXRpZXMsIFRoZXJlIGlz
IG5vIGRvdWJ0IGFib3V0IHRoYXQNCj4gPj4+Pj4gOi0pLCBJbmRlZWQgU0NUUCBkb2VzIGl0IGFu
ZCBzY3JlYW0gZG9lcyBpdC4NCj4gPj4+Pj4gQnV0IGl0IGlzIG5vdCBzbyB3ZWxsLWRlc2NyaWJl
ZCBpbiB0aGUgc2NyZWFtIGRyYWZ0IGhvdyBleGFjdGx5DQo+ID4+Pj4+IHRoZSBwcmlvcml0aXph
dGlvbiB3b3JrcyBhbmQgd2hpY2ggbWVhbnMgYW4gYXBwbGljYXRpb24gaGFzIHRvDQo+ID4+Pj4+
IGRlZmluZSBkaWZmZXJlbnQgcHJpb3JpdGllcy4NCj4gPj4+Pj4gKEZvciBpbmZvcm1hdGlvbiB0
aGVuIGZvciBTQ1RQIGEgbnVtYmVyIG9mIGRpZmZlcmVudCBzY2hlZHVsaW5nDQo+ID4+Pj4+IHBv
c3NpYmlsaXRpZXMgaXMgZGVzY3JpYmVkIGluDQo+ID4+Pj4+IGh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLy4pDQo+ID4+Pj4+DQo+ID4+
Pj4+IFRoZW4gZm9yIFJNQ0FUIGNvdXBsZWQgY29uZ2VzdGlvbiBjb250cm9sICB3ZSBoYXZlIHRo
ZSBXZXpseiwNCj4gPj4+Pj4gU2FmaXF1bCBwcm9wb3NhbCB3aGVyZSB0aGUgY291cGxlZCBpcyBk
b25lIGluLWJldHdlZW4gcGVyIGZsb3ctQ0MNCj4gPj4+Pj4gY29udGV4dHMgYnkgcHJpb3JpdGl6
YXRpb24gb24gbWFuaXB1bGF0aW9uIG9mIHRoZSBjd25kLg0KPiA+Pj4+PiBBbmQgdGhlIHdlIGFs
c28gaGF2ZSwgYSBub3Qgc28gZGV0YWlsZWQgcHJvcG9zYWwvZGVzY3JpcHRpb24sIG9uDQo+ID4+
Pj4+IGhvdyB0aGUgc2FtZSBjYW4gYmUgYWNoaWV2ZWQgdmlhIHNjaGVkdWxpbmcgKHNjcmVhbSku
DQo+ID4+Pj4+IEl0IHNob3VsZCBiZSBvayB0byBhbGxvdyBmb3IgZGlmZmVyZW50IHdheXMgdG8g
aW1wbGVtZW50IGNvdXBsaW5nLA0KPiA+Pj4+PiBidXQgd2Ugc2hvdWxkIHRoZW4gZXZlbnR1YWxs
eSBoYXZlIG9uZSBkb2N1bWVudCB0aGF0IGRlc2NyaWJlcw0KPiA+Pj4+PiBib3RoIHNvbHV0aW9u
cy4gU2hvdWxkbid0IHdlID8NCj4gPj4+Pg0KPiA+Pj4+IEkgdGhpbmsgc28uIFRoZXJlIGlzIGFs
cmVhZHkgKHNob3J0LCBiZWNhdXNlIGl0J3Mgc28gc2ltcGxlKSB0ZXh0DQo+ID4+Pj4gYWJvdXQg
c2NoZWR1bGluZyBpbiBjb3VwbGVkLWNjIGFuZCB3ZSBjYW4gZXh0ZW5kIHRoYXQgYW5kIG1ha2Ug
aXQNCj4gPj4+PiBzdGFuZCBvdXQgbW9yZSBjbGVhcmx5IChub3cgaXQncyBpbiB0aGUgaW50cm8g
SSB0aGluaykuDQo+ID4+Pj4NCj4gPj4+PiBDaGVlcnMsDQo+ID4+Pj4gTWljaGFlbA0KPiA+Pj4N
Cg0K


From nobody Mon Jul 27 06:58:30 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 424461B2DE2 for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 06:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Vp8I3_2qYb1r for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 06:58:16 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260D21B2D8B for <rmcat@ietf.org>; Mon, 27 Jul 2015 06:58:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id BD323D9307; Mon, 27 Jul 2015 15:58:14 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yEZRxPfaHfYo; Mon, 27 Jul 2015 15:58:14 +0200 (MEST)
Received: from [192.168.178.33] (x5f71a186.dyn.telefonica.de [95.113.161.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 58CDED9305; Mon, 27 Jul 2015 15:58:14 +0200 (MEST)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jul 2015 15:58:13 +0200
Message-Id: <C355D8F8-8A76-43BD-9F51-4DA87F8BBD00@tik.ee.ethz.ch>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/t0Rj1SxVC2l9tN9r8l_dJDLAPxM>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] Call for adoption of draft-alvestrand-rmcat-congestion-03
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jul 2015 13:58:21 -0000

Hi all,

the RMCAT wg is considering adoption of =
draft-alvestrand-rmcat-congestion-03 as a third candidate to address our =
milestone on cc-candidates. This draft has been discussed on the list =
and additional preliminary evaluation results have been presented at the =
last interim.
=20
At the call for adoption at the Prague IETF meeting the document =
received support from the
people present in the meeting room and no comments against adopting this =
draft as an RMCAT wg item were given.
=20
The WG chairs now invite any further comments on this adoption. If there =
are concerns or comments about adoption please send comments to the list =
or to the chairs.=20
=20
The adoption call ends August 10, 2015.=20
=20
Karen and Mirja,
RMCAT Co-Chairs=


From nobody Mon Jul 27 07:03:06 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204301B2DEA for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ocZ3vS2K1s1c for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:02:58 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E1761B2DE2 for <rmcat@ietf.org>; Mon, 27 Jul 2015 07:02:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id ED7CAD930A; Mon, 27 Jul 2015 16:02:53 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jzlpV130-lKn; Mon, 27 Jul 2015 16:02:53 +0200 (MEST)
Received: from [192.168.178.33] (x5f71a186.dyn.telefonica.de [95.113.161.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 96A67D9305; Mon, 27 Jul 2015 16:02:53 +0200 (MEST)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jul 2015 16:02:52 +0200
Message-Id: <B1E1AE4C-2B75-4C23-B0A3-71ED67C053A9@tik.ee.ethz.ch>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/l3zBNawr_HeVVsEjLIPkq04NdWw>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] Call for adoption of draft-zanaty-rmcat-cc-codec-interactions
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jul 2015 14:03:04 -0000

Hi all,

the RMCAT wg is considering adoption of =
draft-zanaty-rmcat-cc-codec-interactions to address our milestone on =
app-iterations. This draft is based on =
draft-ietf-rmcat-app-interaction-01 but only describes the interactions =
between the codec and rmcat congestion control as requested at the last =
meeting in Dallas.
=20
At the call for adoption at the Prague IETF meeting the document =
received support from the
people present in the meeting room and no comments against adopting this =
draft as an RMCAT wg item were given.
=20
The WG chairs now invite any further comments on this adoption. If there =
are concerns or comments about adoption please send comments to the list =
or to the chairs.=20
=20
The adoption call ends August 10, 2015.=20
=20
Karen and Mirja,
RMCAT Co-Chairs=


From nobody Mon Jul 27 07:14:01 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44F3A1B2E26 for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Ncu0BrvX0z6z for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:13:53 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CE1B1B2E2E for <rmcat@ietf.org>; Mon, 27 Jul 2015 07:13:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 29E42D9307; Mon, 27 Jul 2015 16:13:52 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00L4ruMSuuoM; Mon, 27 Jul 2015 16:13:52 +0200 (MEST)
Received: from [192.168.178.33] (x5f71a186.dyn.telefonica.de [95.113.161.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id BF9E6D9305; Mon, 27 Jul 2015 16:13:51 +0200 (MEST)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jul 2015 16:13:50 +0200
Message-Id: <B81DD400-8F60-4EA4-BACE-5CE91FE372B4@tik.ee.ethz.ch>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/j3UssWiwOhauYq-naJygCXpvsmo>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] Call for adoption of draft-welzl-rmcat-coupled-cc-05
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jul 2015 14:14:00 -0000

Hi all,

the RMCAT wg is considering adoption of draft-welzl-rmcat-coupled-cc-05 =
to address our milestone on coupled-cc. This adoption call is on the =
current document (describing coupled congestion control and its =
applicability to NADA) with one change request: any text describing an =
alternative solution to coupled congestion control based on scheduling =
will be moved to the appendix.

With the adoption of the document (similar as for all documents) the =
change control goes over to the working group. Therefore the working may =
consider to extend this document to also describe coupled congestion =
control for other candidates or even alternative approaches. =
Alternatively, the wg might also consider to adopt additional documents =
to address our milestone on coupled-cc. However, such a decision can =
only be made at the time when the respective input is provided to the =
working group. Therefore this discussion is postponed to future =
meetings.
=20
At the call for adoption at the Prague IETF meeting the document =
received support from the
people present in the meeting room.
=20
The WG chairs now invite any further comments on this adoption. If there =
are concerns or comments about adoption please send comments to the list =
or to the chairs.=20
=20
The adoption call ends August 10, 2015.=20
=20
Karen and Mirja,
RMCAT Co-Chairs=


From nobody Mon Jul 27 07:59:18 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA9A1B2E6A for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 F8RpqsExhMv9 for <rmcat@ietfa.amsl.com>; Mon, 27 Jul 2015 07:59:15 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EECD1B2E62 for <rmcat@ietf.org>; Mon, 27 Jul 2015 07:59:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C13D8D9307; Mon, 27 Jul 2015 16:59:13 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id A0bu6BWn8ZUo; Mon, 27 Jul 2015 16:59:13 +0200 (MEST)
Received: from [192.168.178.33] (x5f71a186.dyn.telefonica.de [95.113.161.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 3BF1BD930C; Mon, 27 Jul 2015 16:59:13 +0200 (MEST)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jul 2015 16:59:12 +0200
Message-Id: <1E825A85-FE15-4931-823C-10384221EDD9@tik.ee.ethz.ch>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/teDw_0u4gzLmQNg7zRJJowFjc_Q>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] minutes interim July 19
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jul 2015 14:59:17 -0000

Hi all,

please find the minutes for the interim here:

=
https://www.ietf.org/proceedings/interim/2015/07/19/rmcat/minutes/minutes-=
interim-2015-rmcat-1

Please let me know if there is anything that is not correctly or =
sufficiently presented and therefore needs to be changed!

@Michael Ramalho: Thanks for your notes as well! The current minutes are =
mainly based on my own notes as I believe our notes are very similar. =
However, let me know if you feel that I missed any points from your =
notes or if specific points should be documented in more detail!

Mirja=


From nobody Thu Jul 30 03:32:02 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A621A8942 for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 03:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.21
X-Spam-Level: 
X-Spam-Status: No, score=-1.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 v9kV5tjA6AyT for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 03:31:58 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 576F11A0211 for <rmcat@ietf.org>; Thu, 30 Jul 2015 03:31:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id E1011D9303; Thu, 30 Jul 2015 12:31:34 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rsHiQql3bVE1; Thu, 30 Jul 2015 12:31:34 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id A2C3CD930D; Thu, 30 Jul 2015 12:31:34 +0200 (MEST)
Message-ID: <55B9FD05.1050807@tik.ee.ethz.ch>
Date: Thu, 30 Jul 2015 12:31:33 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,  Michael Welzl <michawe@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/XAIBvW9wiPUzVHjowD-2MeqMc18>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Jul 2015 10:32:01 -0000

Hi Ingemar,

A quick comment here:

> I think however the scheduling it will remain in the running code (C++ code and OWR) at least until a good alternative is available.

If the scheduling stays in the appendix, we definitely need to see evaluation 
results for Scream without scheduling. If scheduling is an essential part of 
Scream, you also need a shared bottleneck detection! Actually I guess we need to 
see evaluation results for Scream without scheduling in any case, because there 
might always be the case where the sbd does not detect a shared bottleneck 
correctly.

Mirja



>
> /Ingemar
>
>
>> -----Original Message-----
>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>> Sent: den 24 juli 2015 10:57
>> To: Ingemar Johansson S
>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>> KÃ¼hlewind
>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>
>> No.
>>
>> Our algo lets you assign priorities, and they are valid at the time you set
>> them, they just give you a portion of the overall rate and it applies as soon as
>> you set it.
>> If  you want to adjust priorities based on the coder output rate variation, you
>> can implement this using our algo or with a scheduler. A scheduler operates
>> per packet, we operate per time, so implementation-wise it's a bit different.
>>
>> My point is only: whether you do it with our algorithm or without a
>> scheduler, I think this should not be in our draft  (and I'm neutral about:
>> should it be in the SCReAM draft or separate from it).
>>
>> Cheers,
>> Michael
>>
>>
>>> On 24. jul. 2015, at 10.42, Ingemar Johansson S
>> <ingemar.s.johansson@ericsson.com> wrote:
>>>
>>> Hi
>>>
>>> Not sure I get it.
>>> Do you mean that coupling algo is immune to video coder output rate
>> variation ?
>>>
>>> /Ingemar
>>>
>>>> -----Original Message-----
>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>> Sent: den 22 juli 2015 11:16
>>>> To: Ingemar Johansson S
>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>>>> KÃ¼hlewind
>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>
>>>> understood; i think these details are beyond the scope of our
>>>> coupling draft which focuses on a different method.
>>>>
>>>> cheers
>>>> michael
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On 22. juli 2015, at 11:06, Ingemar Johansson S
>>>> <ingemar.s.johansson@ericsson.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Still waiting for the summer to show up so I'll try to chime in
>>>>> while this
>>>> subject is at least luke-warm. I may be slow with follow up on this,
>>>> sorry for that in advance.
>>>>>
>>>>> Stream prio in SCReAM is outlined in section A.2 in the draft
>>>> (https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28 ).
>>>> In its function it resembles fq-codel quite a lot in the sense that
>>>> streams that do not get scheduled at a given scheduling instant gets
>>>> a credit that is used to increase the chance of being scheduled at
>>>> the next scheduling instant. A configurable scheduling priority determines
>> how much credit  that is given.
>>>> Looking in the
>>>> https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf
>>>> draft I would say that this resembles the "Weighted Fair Queueing
>>>> Scheduler"  the most. Some additional means are needed to make this
>>>> work well in reality though (see below).
>>>>>
>>>>> The benefit with doing scheduling priority and a common congestion
>>>> control is an increased probability that the path capacity is fully
>>>> utilized, if a stream becomes idle (for instance no or little
>>>> activity in one video source) , more resources are allocated to the
>>>> other sources. And this is achieved with no or very little additional delay
>> buildup on the sender side.
>>>>> Another benefit with stream prioritization is that it is easier to
>>>>> make one
>>>> congestion control behave well (low delay /packet loss) esp. on a
>>>> wireless link. We have simulation results that supports this
>>>> statement albeit in the different context (QUIC congestion control
>> evolution).
>>>>> The stream prioritization and one congestion control of course
>>>>> require that all the streams share the same bottleneck
>>>>> characteristics
>>>>>
>>>>> With that said, the biggest challenge I have seen this far is the
>>>>> large
>>>> variability of esp. video sources. Sit still in front of the camera
>>>> and the output rate becomes very low regardless the target rate, move
>>>> yourself closer to the camera and bang!!.. you get 2Mbps video rate
>>>> all of a sudden. This variability causes issues with stream
>>>> prioritization in the sense that less variable streams may be pushed
>>>> back. Additional code is therefore added in SCReAM to correct this
>>>> anomaly and ensure a (weighted) fair distribution over a longer time
>>>> scale. Still as mentioned in the SCReAM draft, this needs to be tried
>>>> out some more. I have sofar only simulated video sources with variability
>> to see that the current implementation is reasonably robust.
>>>>> The bottom line here is that, while scheduling of streams with
>>>>> static
>>>> properties may be considered simple, real video may be a taller order.
>>>>>
>>>>> /Ingemar
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>> Sent: den 20 juli 2015 10:03
>>>>>> To: Karen E. E. Nielsen
>>>>>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org; Mirja
>>>>>> KÃ¼hlewind
>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>
>>>>>>
>>>>>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
>>>>>>> <karen.nielsen@tieto.com> wrote:
>>>>>>>
>>>>>>> HI,
>>>>>>>
>>>>>>> Yes - there is the possibility to implement coupled congestion
>>>>>>> control with scheduling priorities, There is no doubt about that
>>>>>>> :-), Indeed SCTP does it and scream does it.
>>>>>>> But it is not so well-described in the scream draft how exactly
>>>>>>> the prioritization works and which means an application has to
>>>>>>> define different priorities.
>>>>>>> (For information then for SCTP a number of different scheduling
>>>>>>> possibilities is described in
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>>>>>>>
>>>>>>> Then for RMCAT coupled congestion control  we have the Wezlz,
>>>>>>> Safiqul proposal where the coupled is done in-between per flow-CC
>>>>>>> contexts by prioritization on manipulation of the cwnd.
>>>>>>> And the we also have, a not so detailed proposal/description, on
>>>>>>> how the same can be achieved via scheduling (scream).
>>>>>>> It should be ok to allow for different ways to implement coupling,
>>>>>>> but we should then eventually have one document that describes
>>>>>>> both solutions. Shouldn't we ?
>>>>>>
>>>>>> I think so. There is already (short, because it's so simple) text
>>>>>> about scheduling in coupled-cc and we can extend that and make it
>>>>>> stand out more clearly (now it's in the intro I think).
>>>>>>
>>>>>> Cheers,
>>>>>> Michael
>>>>>
>

-- 
------------------------------------------
Dipl.-Ing. Mirja KÃ¼hlewind
Communication Systems Group
Institute TIK, ETH ZÃ¼rich
Gloriastrasse 35, 8092 ZÃ¼rich, Switzerland

Room ETZ G93
phone: +41 44 63 26932
email: mirja.kuehlewind@tik.ee.ethz.ch
------------------------------------------


From nobody Thu Jul 30 04:22:47 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0ED1A1B24 for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 04:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 fTRcYCdfPJuJ for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 04:22:43 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02CC71A1B1C for <rmcat@ietf.org>; Thu, 30 Jul 2015 04:22:42 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-0c-55ba0900c77d
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 3C.82.29223.0090AB55; Thu, 30 Jul 2015 13:22:41 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0210.002; Thu, 30 Jul 2015 13:22:40 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiD//+NBAAAEo4fAASxm34AABZKoIA==
Date: Thu, 30 Jul 2015 11:22:40 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se> <55B9FD05.1050807@tik.ee.ethz.ch>
In-Reply-To: <55B9FD05.1050807@tik.ee.ethz.ch>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGfG3RpeRc1eowYR7fBaHWmeyWPw4u5PV YsPqKSwWq29+YHNg8Viy5CeTx+rVD5k9Dj0P8jj24StbAEsUl01Kak5mWWqRvl0CV8aHpk2M BTMSKqZPn87ewHgntouRk0NCwESi49x8ZghbTOLCvfVsXYxcHEICRxklGs9dYoZwFjNKHD28 ngWkik3ARmLloe+MILaIQIHEjp2zwYqYBSYwSlx//wFslDBQUfubflaIIluJk3+WM4EUiQhM YpT4+XgqE0iCRUBV4sXhR2ANvAK+Evs63kGtO8AmsXXWXfYuRg4OTgE9iUWbZEFqGAVkJe5/ vwd2BbOAuMStJ/OZIO4WkFiy5zzUD6ISLx//Y4WwlSTWHt7OAjKGWUBTYv0ufYhWRYkp3Q/Z IdYKSpyc+YRlAqPYLCRTZyF0zELSMQtJxwJGllWMosWpxUm56UZGeqlFmcnFxfl5enmpJZsY gXF2cMtvgx2ML587HmIU4GBU4uFN2LszVIg1say4MvcQozQHi5I474zNeaFCAumJJanZqakF qUXxRaU5qcWHGJk4OKUaGNmL6xWiz66R2P7ufYen2t2vDTfU2V7/e7dQ943BrO2Hlp98dz5k 1bkgC9UPmbMXOCuu6UnjuNlUlmyUU8zkHfn2DDuXnZzpLgXbVx9Wd51hbT8ZsKvP/dYmjbJO viC/5eXLX2x7q6hxt6QgW/AoY4xSQej+2JSrj3zWXpy9k4NjztqXzmGb/yqxFGckGmoxFxUn AgCWvFn1lAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/fONrPEWQ2dB1QIWIe4AmQBnDmz0>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Jul 2015 11:22:46 -0000

SGkNCg0KUHJvYmFibHkgbmVlZHMgc29tZSBjbGFyaWZpY2F0aW9uLiBUaGUgdHJhbnNtaXNzaW9u
IHNjaGVkdWxlciB0aGF0IGRlY2lkZXMgd2hlbiB0byB0cmFuc21pdCBSVFAgcGFja2V0cyBpcyBh
biBpbnRlZ3JhbCBwYXJ0IG9mIFNDUmVBTSBhbmQgZGVzY3JpYmVkIGluIHNlY3Rpb24gNC4xLjIu
MiBpbiB0aGUgZHJhZnQuIA0KU3RyZWFtIHByaW9yaXRpemF0aW9uIGlzIGFwcGxpZWQgd2hlbiB0
d28gb3IgbW9yZSBzdHJlYW1zIHNoYXJlIGEgY29uZ2VzdGlvbiBjb250cm9sIGFuZCBpcyBkZXNj
cmliZWQgaW4gc2VjdGlvbiBBLjIuDQoNClRoZSBmb3JtZXIgaGFzIGJlZW4gZXZhbHVhdGVkIGVh
cmxpZXIgLCB0aGUgbGF0dGVyIGlzIG9ubHkgZXhlbXBsaWZpZWQgaW4gDQpodHRwczovL2dpdGh1
Yi5jb20vRXJpY3Nzb25SZXNlYXJjaC9zY3JlYW0vYmxvYi9tYXN0ZXIvU0NSZUFNLWRlc2NyaXB0
aW9uLnBkZiANCg0KVGhlIGV2YWx1YXRpb24gb2Ygc3RyZWFtIHByaW9yaXRpemF0aW9uIGxlYWRz
IHRvIGEgc2V0IG9mIGZvbGxvdy11cCBxdWVzdGlvbnMuIFdoYXQga2luZCBvZiBzb3VyY2UgYmVo
YXZpb3IgZG8gYmUgYXNzdW1lLCBpcyBpdCBDQlIgIG9yIFZCUi4gU3RyZWFtIHByaW9yaXRpemF0
aW9uIG9mIENCUiBzb3VyY2VzIGlzIHF1aXRlIHRyaXZpYWwgdG8gc29sdmUgSU1PLCBWQlIgaXMg
bW9yZSBjb21wbGljYXRlZC4NCg0KL0luZ2VtYXINCg0KDQogDQoNCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogTWlyamEgS8O8aGxld2luZCBbbWFpbHRvOm1pcmphLmt1ZWhs
ZXdpbmRAdGlrLmVlLmV0aHouY2hdDQo+IFNlbnQ6IGRlbiAzMCBqdWxpIDIwMTUgMTI6MzINCj4g
VG86IEluZ2VtYXIgSm9oYW5zc29uIFM7IE1pY2hhZWwgV2VsemwNCj4gQ2M6IEthcmVuIEUuIEUu
IE5pZWxzZW47IFphaGVkdXp6YW1hbiBTYXJrZXI7IHJtY2F0QGlldGYub3JnDQo+IFN1YmplY3Q6
IFJlOiBbcm1jYXRdIFJldmlldyBvZiBkcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMQ0KPiAN
Cj4gSGkgSW5nZW1hciwNCj4gDQo+IEEgcXVpY2sgY29tbWVudCBoZXJlOg0KPiANCj4gPiBJIHRo
aW5rIGhvd2V2ZXIgdGhlIHNjaGVkdWxpbmcgaXQgd2lsbCByZW1haW4gaW4gdGhlIHJ1bm5pbmcg
Y29kZSAoQysrIGNvZGUNCj4gYW5kIE9XUikgYXQgbGVhc3QgdW50aWwgYSBnb29kIGFsdGVybmF0
aXZlIGlzIGF2YWlsYWJsZS4NCj4gDQo+IElmIHRoZSBzY2hlZHVsaW5nIHN0YXlzIGluIHRoZSBh
cHBlbmRpeCwgd2UgZGVmaW5pdGVseSBuZWVkIHRvIHNlZSBldmFsdWF0aW9uDQo+IHJlc3VsdHMg
Zm9yIFNjcmVhbSB3aXRob3V0IHNjaGVkdWxpbmcuIElmIHNjaGVkdWxpbmcgaXMgYW4gZXNzZW50
aWFsIHBhcnQgb2YNCj4gU2NyZWFtLCB5b3UgYWxzbyBuZWVkIGEgc2hhcmVkIGJvdHRsZW5lY2sg
ZGV0ZWN0aW9uISBBY3R1YWxseSBJIGd1ZXNzIHdlDQo+IG5lZWQgdG8gc2VlIGV2YWx1YXRpb24g
cmVzdWx0cyBmb3IgU2NyZWFtIHdpdGhvdXQgc2NoZWR1bGluZyBpbiBhbnkgY2FzZSwNCj4gYmVj
YXVzZSB0aGVyZSBtaWdodCBhbHdheXMgYmUgdGhlIGNhc2Ugd2hlcmUgdGhlIHNiZCBkb2VzIG5v
dCBkZXRlY3QgYQ0KPiBzaGFyZWQgYm90dGxlbmVjayBjb3JyZWN0bHkuDQo+IA0KPiBNaXJqYQ0K
PiANCj4gDQo+IA0KPiA+DQo+ID4gL0luZ2VtYXINCj4gPg0KPiA+DQo+ID4+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IE1pY2hhZWwgV2VsemwgW21haWx0bzptaWNoYXdl
QGlmaS51aW8ubm9dDQo+ID4+IFNlbnQ6IGRlbiAyNCBqdWxpIDIwMTUgMTA6NTcNCj4gPj4gVG86
IEluZ2VtYXIgSm9oYW5zc29uIFMNCj4gPj4gQ2M6IEthcmVuIEUuIEUuIE5pZWxzZW47IFphaGVk
dXp6YW1hbiBTYXJrZXI7IHJtY2F0QGlldGYub3JnOyBNaXJqYQ0KPiA+PiBLw7xobGV3aW5kDQo+
ID4+IFN1YmplY3Q6IFJlOiBbcm1jYXRdIFJldmlldyBvZiBkcmFmdC1pZXRmLXJtY2F0LXNjcmVh
bS1jYy0wMQ0KPiA+Pg0KPiA+PiBOby4NCj4gPj4NCj4gPj4gT3VyIGFsZ28gbGV0cyB5b3UgYXNz
aWduIHByaW9yaXRpZXMsIGFuZCB0aGV5IGFyZSB2YWxpZCBhdCB0aGUgdGltZQ0KPiA+PiB5b3Ug
c2V0IHRoZW0sIHRoZXkganVzdCBnaXZlIHlvdSBhIHBvcnRpb24gb2YgdGhlIG92ZXJhbGwgcmF0
ZSBhbmQgaXQNCj4gPj4gYXBwbGllcyBhcyBzb29uIGFzIHlvdSBzZXQgaXQuDQo+ID4+IElmICB5
b3Ugd2FudCB0byBhZGp1c3QgcHJpb3JpdGllcyBiYXNlZCBvbiB0aGUgY29kZXIgb3V0cHV0IHJh
dGUNCj4gPj4gdmFyaWF0aW9uLCB5b3UgY2FuIGltcGxlbWVudCB0aGlzIHVzaW5nIG91ciBhbGdv
IG9yIHdpdGggYSBzY2hlZHVsZXIuDQo+ID4+IEEgc2NoZWR1bGVyIG9wZXJhdGVzIHBlciBwYWNr
ZXQsIHdlIG9wZXJhdGUgcGVyIHRpbWUsIHNvDQo+IGltcGxlbWVudGF0aW9uLXdpc2UgaXQncyBh
IGJpdCBkaWZmZXJlbnQuDQo+ID4+DQo+ID4+IE15IHBvaW50IGlzIG9ubHk6IHdoZXRoZXIgeW91
IGRvIGl0IHdpdGggb3VyIGFsZ29yaXRobSBvciB3aXRob3V0IGENCj4gPj4gc2NoZWR1bGVyLCBJ
IHRoaW5rIHRoaXMgc2hvdWxkIG5vdCBiZSBpbiBvdXIgZHJhZnQgIChhbmQgSSdtIG5ldXRyYWwg
YWJvdXQ6DQo+ID4+IHNob3VsZCBpdCBiZSBpbiB0aGUgU0NSZUFNIGRyYWZ0IG9yIHNlcGFyYXRl
IGZyb20gaXQpLg0KPiA+Pg0KPiA+PiBDaGVlcnMsDQo+ID4+IE1pY2hhZWwNCj4gPj4NCj4gPj4N
Cj4gPj4+IE9uIDI0LiBqdWwuIDIwMTUsIGF0IDEwLjQyLCBJbmdlbWFyIEpvaGFuc3NvbiBTDQo+
ID4+IDxpbmdlbWFyLnMuam9oYW5zc29uQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+ID4+Pg0KPiA+
Pj4gSGkNCj4gPj4+DQo+ID4+PiBOb3Qgc3VyZSBJIGdldCBpdC4NCj4gPj4+IERvIHlvdSBtZWFu
IHRoYXQgY291cGxpbmcgYWxnbyBpcyBpbW11bmUgdG8gdmlkZW8gY29kZXIgb3V0cHV0IHJhdGUN
Cj4gPj4gdmFyaWF0aW9uID8NCj4gPj4+DQo+ID4+PiAvSW5nZW1hcg0KPiA+Pj4NCj4gPj4+PiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+IEZyb206IE1pY2hhZWwgV2VsemwgW21h
aWx0bzptaWNoYXdlQGlmaS51aW8ubm9dDQo+ID4+Pj4gU2VudDogZGVuIDIyIGp1bGkgMjAxNSAx
MToxNg0KPiA+Pj4+IFRvOiBJbmdlbWFyIEpvaGFuc3NvbiBTDQo+ID4+Pj4gQ2M6IEthcmVuIEUu
IEUuIE5pZWxzZW47IFphaGVkdXp6YW1hbiBTYXJrZXI7IHJtY2F0QGlldGYub3JnOyBNaXJqYQ0K
PiA+Pj4+IEvDvGhsZXdpbmQNCj4gPj4+PiBTdWJqZWN0OiBSZTogW3JtY2F0XSBSZXZpZXcgb2Yg
ZHJhZnQtaWV0Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gPj4+Pg0KPiA+Pj4+IHVuZGVyc3Rvb2Q7
IGkgdGhpbmsgdGhlc2UgZGV0YWlscyBhcmUgYmV5b25kIHRoZSBzY29wZSBvZiBvdXINCj4gPj4+
PiBjb3VwbGluZyBkcmFmdCB3aGljaCBmb2N1c2VzIG9uIGEgZGlmZmVyZW50IG1ldGhvZC4NCj4g
Pj4+Pg0KPiA+Pj4+IGNoZWVycw0KPiA+Pj4+IG1pY2hhZWwNCj4gPj4+Pg0KPiA+Pj4+IFNlbnQg
ZnJvbSBteSBpUGhvbmUNCj4gPj4+Pg0KPiA+Pj4+PiBPbiAyMi4ganVsaSAyMDE1LCBhdCAxMTow
NiwgSW5nZW1hciBKb2hhbnNzb24gUw0KPiA+Pj4+IDxpbmdlbWFyLnMuam9oYW5zc29uQGVyaWNz
c29uLmNvbT4gd3JvdGU6DQo+ID4+Pj4+DQo+ID4+Pj4+IEhpDQo+ID4+Pj4+DQo+ID4+Pj4+IFN0
aWxsIHdhaXRpbmcgZm9yIHRoZSBzdW1tZXIgdG8gc2hvdyB1cCBzbyBJJ2xsIHRyeSB0byBjaGlt
ZSBpbg0KPiA+Pj4+PiB3aGlsZSB0aGlzDQo+ID4+Pj4gc3ViamVjdCBpcyBhdCBsZWFzdCBsdWtl
LXdhcm0uIEkgbWF5IGJlIHNsb3cgd2l0aCBmb2xsb3cgdXAgb24NCj4gPj4+PiB0aGlzLCBzb3Jy
eSBmb3IgdGhhdCBpbiBhZHZhbmNlLg0KPiA+Pj4+Pg0KPiA+Pj4+PiBTdHJlYW0gcHJpbyBpbiBT
Q1JlQU0gaXMgb3V0bGluZWQgaW4gc2VjdGlvbiBBLjIgaW4gdGhlIGRyYWZ0DQo+ID4+Pj4gKGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMSNw
YWdlLTI4ICkuDQo+ID4+Pj4gSW4gaXRzIGZ1bmN0aW9uIGl0IHJlc2VtYmxlcyBmcS1jb2RlbCBx
dWl0ZSBhIGxvdCBpbiB0aGUgc2Vuc2UgdGhhdA0KPiA+Pj4+IHN0cmVhbXMgdGhhdCBkbyBub3Qg
Z2V0IHNjaGVkdWxlZCBhdCBhIGdpdmVuIHNjaGVkdWxpbmcgaW5zdGFudA0KPiA+Pj4+IGdldHMg
YSBjcmVkaXQgdGhhdCBpcyB1c2VkIHRvIGluY3JlYXNlIHRoZSBjaGFuY2Ugb2YgYmVpbmcNCj4g
Pj4+PiBzY2hlZHVsZWQgYXQgdGhlIG5leHQgc2NoZWR1bGluZyBpbnN0YW50LiBBIGNvbmZpZ3Vy
YWJsZSBzY2hlZHVsaW5nDQo+ID4+Pj4gcHJpb3JpdHkgZGV0ZXJtaW5lcw0KPiA+PiBob3cgbXVj
aCBjcmVkaXQgIHRoYXQgaXMgZ2l2ZW4uDQo+ID4+Pj4gTG9va2luZyBpbiB0aGUNCj4gPj4+PiBo
dHRwczovL3Rvb2xzLmlldGYub3JnL3BkZi9kcmFmdC1pZXRmLXRzdndnLXNjdHAtbmRhdGEtMDQu
cGRmDQo+ID4+Pj4gZHJhZnQgSSB3b3VsZCBzYXkgdGhhdCB0aGlzIHJlc2VtYmxlcyB0aGUgIldl
aWdodGVkIEZhaXIgUXVldWVpbmcNCj4gPj4+PiBTY2hlZHVsZXIiICB0aGUgbW9zdC4gU29tZSBh
ZGRpdGlvbmFsIG1lYW5zIGFyZSBuZWVkZWQgdG8gbWFrZSB0aGlzDQo+ID4+Pj4gd29yayB3ZWxs
IGluIHJlYWxpdHkgdGhvdWdoIChzZWUgYmVsb3cpLg0KPiA+Pj4+Pg0KPiA+Pj4+PiBUaGUgYmVu
ZWZpdCB3aXRoIGRvaW5nIHNjaGVkdWxpbmcgcHJpb3JpdHkgYW5kIGEgY29tbW9uIGNvbmdlc3Rp
b24NCj4gPj4+PiBjb250cm9sIGlzIGFuIGluY3JlYXNlZCBwcm9iYWJpbGl0eSB0aGF0IHRoZSBw
YXRoIGNhcGFjaXR5IGlzIGZ1bGx5DQo+ID4+Pj4gdXRpbGl6ZWQsIGlmIGEgc3RyZWFtIGJlY29t
ZXMgaWRsZSAoZm9yIGluc3RhbmNlIG5vIG9yIGxpdHRsZQ0KPiA+Pj4+IGFjdGl2aXR5IGluIG9u
ZSB2aWRlbyBzb3VyY2UpICwgbW9yZSByZXNvdXJjZXMgYXJlIGFsbG9jYXRlZCB0byB0aGUNCj4g
Pj4+PiBvdGhlciBzb3VyY2VzLiBBbmQgdGhpcyBpcyBhY2hpZXZlZCB3aXRoIG5vIG9yIHZlcnkg
bGl0dGxlDQo+ID4+Pj4gYWRkaXRpb25hbCBkZWxheQ0KPiA+PiBidWlsZHVwIG9uIHRoZSBzZW5k
ZXIgc2lkZS4NCj4gPj4+Pj4gQW5vdGhlciBiZW5lZml0IHdpdGggc3RyZWFtIHByaW9yaXRpemF0
aW9uIGlzIHRoYXQgaXQgaXMgZWFzaWVyIHRvDQo+ID4+Pj4+IG1ha2Ugb25lDQo+ID4+Pj4gY29u
Z2VzdGlvbiBjb250cm9sIGJlaGF2ZSB3ZWxsIChsb3cgZGVsYXkgL3BhY2tldCBsb3NzKSBlc3Au
IG9uIGENCj4gPj4+PiB3aXJlbGVzcyBsaW5rLiBXZSBoYXZlIHNpbXVsYXRpb24gcmVzdWx0cyB0
aGF0IHN1cHBvcnRzIHRoaXMNCj4gPj4+PiBzdGF0ZW1lbnQgYWxiZWl0IGluIHRoZSBkaWZmZXJl
bnQgY29udGV4dCAoUVVJQyBjb25nZXN0aW9uIGNvbnRyb2wNCj4gPj4gZXZvbHV0aW9uKS4NCj4g
Pj4+Pj4gVGhlIHN0cmVhbSBwcmlvcml0aXphdGlvbiBhbmQgb25lIGNvbmdlc3Rpb24gY29udHJv
bCBvZiBjb3Vyc2UNCj4gPj4+Pj4gcmVxdWlyZSB0aGF0IGFsbCB0aGUgc3RyZWFtcyBzaGFyZSB0
aGUgc2FtZSBib3R0bGVuZWNrDQo+ID4+Pj4+IGNoYXJhY3RlcmlzdGljcw0KPiA+Pj4+Pg0KPiA+
Pj4+PiBXaXRoIHRoYXQgc2FpZCwgdGhlIGJpZ2dlc3QgY2hhbGxlbmdlIEkgaGF2ZSBzZWVuIHRo
aXMgZmFyIGlzIHRoZQ0KPiA+Pj4+PiBsYXJnZQ0KPiA+Pj4+IHZhcmlhYmlsaXR5IG9mIGVzcC4g
dmlkZW8gc291cmNlcy4gU2l0IHN0aWxsIGluIGZyb250IG9mIHRoZSBjYW1lcmENCj4gPj4+PiBh
bmQgdGhlIG91dHB1dCByYXRlIGJlY29tZXMgdmVyeSBsb3cgcmVnYXJkbGVzcyB0aGUgdGFyZ2V0
IHJhdGUsDQo+ID4+Pj4gbW92ZSB5b3Vyc2VsZiBjbG9zZXIgdG8gdGhlIGNhbWVyYSBhbmQgYmFu
ZyEhLi4geW91IGdldCAyTWJwcyB2aWRlbw0KPiA+Pj4+IHJhdGUgYWxsIG9mIGEgc3VkZGVuLiBU
aGlzIHZhcmlhYmlsaXR5IGNhdXNlcyBpc3N1ZXMgd2l0aCBzdHJlYW0NCj4gPj4+PiBwcmlvcml0
aXphdGlvbiBpbiB0aGUgc2Vuc2UgdGhhdCBsZXNzIHZhcmlhYmxlIHN0cmVhbXMgbWF5IGJlDQo+
ID4+Pj4gcHVzaGVkIGJhY2suIEFkZGl0aW9uYWwgY29kZSBpcyB0aGVyZWZvcmUgYWRkZWQgaW4g
U0NSZUFNIHRvDQo+ID4+Pj4gY29ycmVjdCB0aGlzIGFub21hbHkgYW5kIGVuc3VyZSBhICh3ZWln
aHRlZCkgZmFpciBkaXN0cmlidXRpb24gb3Zlcg0KPiA+Pj4+IGEgbG9uZ2VyIHRpbWUgc2NhbGUu
IFN0aWxsIGFzIG1lbnRpb25lZCBpbiB0aGUgU0NSZUFNIGRyYWZ0LCB0aGlzDQo+ID4+Pj4gbmVl
ZHMgdG8gYmUgdHJpZWQgb3V0IHNvbWUgbW9yZS4gSSBoYXZlIHNvZmFyIG9ubHkgc2ltdWxhdGVk
IHZpZGVvDQo+ID4+Pj4gc291cmNlcyB3aXRoIHZhcmlhYmlsaXR5DQo+ID4+IHRvIHNlZSB0aGF0
IHRoZSBjdXJyZW50IGltcGxlbWVudGF0aW9uIGlzIHJlYXNvbmFibHkgcm9idXN0Lg0KPiA+Pj4+
PiBUaGUgYm90dG9tIGxpbmUgaGVyZSBpcyB0aGF0LCB3aGlsZSBzY2hlZHVsaW5nIG9mIHN0cmVh
bXMgd2l0aA0KPiA+Pj4+PiBzdGF0aWMNCj4gPj4+PiBwcm9wZXJ0aWVzIG1heSBiZSBjb25zaWRl
cmVkIHNpbXBsZSwgcmVhbCB2aWRlbyBtYXkgYmUgYSB0YWxsZXIgb3JkZXIuDQo+ID4+Pj4+DQo+
ID4+Pj4+IC9JbmdlbWFyDQo+ID4+Pj4+DQo+ID4+Pj4+DQo+ID4+Pj4+DQo+ID4+Pj4+DQo+ID4+
Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+Pj4gRnJvbTogTWljaGFlbCBX
ZWx6bCBbbWFpbHRvOm1pY2hhd2VAaWZpLnVpby5ub10NCj4gPj4+Pj4+IFNlbnQ6IGRlbiAyMCBq
dWxpIDIwMTUgMTA6MDMNCj4gPj4+Pj4+IFRvOiBLYXJlbiBFLiBFLiBOaWVsc2VuDQo+ID4+Pj4+
PiBDYzogWmFoZWR1enphbWFuIFNhcmtlcjsgSW5nZW1hciBKb2hhbnNzb24gUzsgcm1jYXRAaWV0
Zi5vcmc7DQo+ID4+Pj4+PiBNaXJqYSBLw7xobGV3aW5kDQo+ID4+Pj4+PiBTdWJqZWN0OiBSZTog
W3JtY2F0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gPj4+Pj4+
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4+PiBPbiAyMC4ganVsLiAyMDE1LCBhdCAwNy4zMiwgS2FyZW4g
RWxpc2FiZXRoIEVnZWRlIE5pZWxzZW4NCj4gPj4+Pj4+PiA8a2FyZW4ubmllbHNlbkB0aWV0by5j
b20+IHdyb3RlOg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gSEksDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+
PiBZZXMgLSB0aGVyZSBpcyB0aGUgcG9zc2liaWxpdHkgdG8gaW1wbGVtZW50IGNvdXBsZWQgY29u
Z2VzdGlvbg0KPiA+Pj4+Pj4+IGNvbnRyb2wgd2l0aCBzY2hlZHVsaW5nIHByaW9yaXRpZXMsIFRo
ZXJlIGlzIG5vIGRvdWJ0IGFib3V0IHRoYXQNCj4gPj4+Pj4+PiA6LSksIEluZGVlZCBTQ1RQIGRv
ZXMgaXQgYW5kIHNjcmVhbSBkb2VzIGl0Lg0KPiA+Pj4+Pj4+IEJ1dCBpdCBpcyBub3Qgc28gd2Vs
bC1kZXNjcmliZWQgaW4gdGhlIHNjcmVhbSBkcmFmdCBob3cgZXhhY3RseQ0KPiA+Pj4+Pj4+IHRo
ZSBwcmlvcml0aXphdGlvbiB3b3JrcyBhbmQgd2hpY2ggbWVhbnMgYW4gYXBwbGljYXRpb24gaGFz
IHRvDQo+ID4+Pj4+Pj4gZGVmaW5lIGRpZmZlcmVudCBwcmlvcml0aWVzLg0KPiA+Pj4+Pj4+IChG
b3IgaW5mb3JtYXRpb24gdGhlbiBmb3IgU0NUUCBhIG51bWJlciBvZiBkaWZmZXJlbnQgc2NoZWR1
bGluZw0KPiA+Pj4+Pj4+IHBvc3NpYmlsaXRpZXMgaXMgZGVzY3JpYmVkIGluDQo+ID4+Pj4+Pj4g
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXRzdndnLXNjdHAtbmRh
dGEvLikNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IFRoZW4gZm9yIFJNQ0FUIGNvdXBsZWQgY29uZ2Vz
dGlvbiBjb250cm9sICB3ZSBoYXZlIHRoZSBXZXpseiwNCj4gPj4+Pj4+PiBTYWZpcXVsIHByb3Bv
c2FsIHdoZXJlIHRoZSBjb3VwbGVkIGlzIGRvbmUgaW4tYmV0d2VlbiBwZXINCj4gPj4+Pj4+PiBm
bG93LUNDIGNvbnRleHRzIGJ5IHByaW9yaXRpemF0aW9uIG9uIG1hbmlwdWxhdGlvbiBvZiB0aGUg
Y3duZC4NCj4gPj4+Pj4+PiBBbmQgdGhlIHdlIGFsc28gaGF2ZSwgYSBub3Qgc28gZGV0YWlsZWQg
cHJvcG9zYWwvZGVzY3JpcHRpb24sIG9uDQo+ID4+Pj4+Pj4gaG93IHRoZSBzYW1lIGNhbiBiZSBh
Y2hpZXZlZCB2aWEgc2NoZWR1bGluZyAoc2NyZWFtKS4NCj4gPj4+Pj4+PiBJdCBzaG91bGQgYmUg
b2sgdG8gYWxsb3cgZm9yIGRpZmZlcmVudCB3YXlzIHRvIGltcGxlbWVudA0KPiA+Pj4+Pj4+IGNv
dXBsaW5nLCBidXQgd2Ugc2hvdWxkIHRoZW4gZXZlbnR1YWxseSBoYXZlIG9uZSBkb2N1bWVudCB0
aGF0DQo+ID4+Pj4+Pj4gZGVzY3JpYmVzIGJvdGggc29sdXRpb25zLiBTaG91bGRuJ3Qgd2UgPw0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IEkgdGhpbmsgc28uIFRoZXJlIGlzIGFscmVhZHkgKHNob3J0LCBi
ZWNhdXNlIGl0J3Mgc28gc2ltcGxlKSB0ZXh0DQo+ID4+Pj4+PiBhYm91dCBzY2hlZHVsaW5nIGlu
IGNvdXBsZWQtY2MgYW5kIHdlIGNhbiBleHRlbmQgdGhhdCBhbmQgbWFrZSBpdA0KPiA+Pj4+Pj4g
c3RhbmQgb3V0IG1vcmUgY2xlYXJseSAobm93IGl0J3MgaW4gdGhlIGludHJvIEkgdGhpbmspLg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IENoZWVycywNCj4gPj4+Pj4+IE1pY2hhZWwNCj4gPj4+Pj4NCj4g
Pg0KPiANCj4gLS0NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQo+IERpcGwuLUluZy4gTWlyamEgS8O8aGxld2luZA0KPiBDb21tdW5pY2F0aW9uIFN5c3RlbXMg
R3JvdXANCj4gSW5zdGl0dXRlIFRJSywgRVRIIFrDvHJpY2gNCj4gR2xvcmlhc3RyYXNzZSAzNSwg
ODA5MiBaw7xyaWNoLCBTd2l0emVybGFuZA0KPiANCj4gUm9vbSBFVFogRzkzDQo+IHBob25lOiAr
NDEgNDQgNjMgMjY5MzINCj4gZW1haWw6IG1pcmphLmt1ZWhsZXdpbmRAdGlrLmVlLmV0aHouY2gN
Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo=


From nobody Thu Jul 30 05:21:26 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C789D1A8769 for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 05:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 yeFS0tluJMMU for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 05:21:22 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519451A8750 for <rmcat@ietf.org>; Thu, 30 Jul 2015 05:21:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id E4A16D930A; Thu, 30 Jul 2015 14:21:20 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wbeoWrmw7sKZ; Thu, 30 Jul 2015 14:21:20 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id A75D8D9303; Thu, 30 Jul 2015 14:21:20 +0200 (MEST)
Message-ID: <55BA16BF.6030101@tik.ee.ethz.ch>
Date: Thu, 30 Jul 2015 14:21:19 +0200
From: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,  Michael Welzl <michawe@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se> <55B9FD05.1050807@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/FfexBhwjQGRKlByoFSQJf_H_jKk>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Jul 2015 12:21:26 -0000

Hi Ingemar,

okay thanks for the clarification. I discussed this with Zahed and the scheduler 
as described in section 4.1.2.2. should probably be renamed to something like 
sending rate controller because without the prioritization it's only handling 
one flow at a time, right?

Mirja


On 30.07.2015 13:22, Ingemar Johansson S wrote:
> Hi
>
> Probably needs some clarification. The transmission scheduler that decides when to transmit RTP packets is an integral part of SCReAM and described in section 4.1.2.2 in the draft.
> Stream prioritization is applied when two or more streams share a congestion control and is described in section A.2.
>
> The former has been evaluated earlier , the latter is only exemplified in
> https://github.com/EricssonResearch/scream/blob/master/SCReAM-description.pdf
>
> The evaluation of stream prioritization leads to a set of follow-up questions. What kind of source behavior do be assume, is it CBR  or VBR. Stream prioritization of CBR sources is quite trivial to solve IMO, VBR is more complicated.
>
> /Ingemar
>
>
>
>
>> -----Original Message-----
>> From: Mirja KÃ¼hlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
>> Sent: den 30 juli 2015 12:32
>> To: Ingemar Johansson S; Michael Welzl
>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org
>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>
>> Hi Ingemar,
>>
>> A quick comment here:
>>
>>> I think however the scheduling it will remain in the running code (C++ code
>> and OWR) at least until a good alternative is available.
>>
>> If the scheduling stays in the appendix, we definitely need to see evaluation
>> results for Scream without scheduling. If scheduling is an essential part of
>> Scream, you also need a shared bottleneck detection! Actually I guess we
>> need to see evaluation results for Scream without scheduling in any case,
>> because there might always be the case where the sbd does not detect a
>> shared bottleneck correctly.
>>
>> Mirja
>>
>>
>>
>>>
>>> /Ingemar
>>>
>>>
>>>> -----Original Message-----
>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>> Sent: den 24 juli 2015 10:57
>>>> To: Ingemar Johansson S
>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>>>> KÃ¼hlewind
>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>
>>>> No.
>>>>
>>>> Our algo lets you assign priorities, and they are valid at the time
>>>> you set them, they just give you a portion of the overall rate and it
>>>> applies as soon as you set it.
>>>> If  you want to adjust priorities based on the coder output rate
>>>> variation, you can implement this using our algo or with a scheduler.
>>>> A scheduler operates per packet, we operate per time, so
>> implementation-wise it's a bit different.
>>>>
>>>> My point is only: whether you do it with our algorithm or without a
>>>> scheduler, I think this should not be in our draft  (and I'm neutral about:
>>>> should it be in the SCReAM draft or separate from it).
>>>>
>>>> Cheers,
>>>> Michael
>>>>
>>>>
>>>>> On 24. jul. 2015, at 10.42, Ingemar Johansson S
>>>> <ingemar.s.johansson@ericsson.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Not sure I get it.
>>>>> Do you mean that coupling algo is immune to video coder output rate
>>>> variation ?
>>>>>
>>>>> /Ingemar
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>> Sent: den 22 juli 2015 11:16
>>>>>> To: Ingemar Johansson S
>>>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>>>>>> KÃ¼hlewind
>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>
>>>>>> understood; i think these details are beyond the scope of our
>>>>>> coupling draft which focuses on a different method.
>>>>>>
>>>>>> cheers
>>>>>> michael
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On 22. juli 2015, at 11:06, Ingemar Johansson S
>>>>>> <ingemar.s.johansson@ericsson.com> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Still waiting for the summer to show up so I'll try to chime in
>>>>>>> while this
>>>>>> subject is at least luke-warm. I may be slow with follow up on
>>>>>> this, sorry for that in advance.
>>>>>>>
>>>>>>> Stream prio in SCReAM is outlined in section A.2 in the draft
>>>>>> (https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28 ).
>>>>>> In its function it resembles fq-codel quite a lot in the sense that
>>>>>> streams that do not get scheduled at a given scheduling instant
>>>>>> gets a credit that is used to increase the chance of being
>>>>>> scheduled at the next scheduling instant. A configurable scheduling
>>>>>> priority determines
>>>> how much credit  that is given.
>>>>>> Looking in the
>>>>>> https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf
>>>>>> draft I would say that this resembles the "Weighted Fair Queueing
>>>>>> Scheduler"  the most. Some additional means are needed to make this
>>>>>> work well in reality though (see below).
>>>>>>>
>>>>>>> The benefit with doing scheduling priority and a common congestion
>>>>>> control is an increased probability that the path capacity is fully
>>>>>> utilized, if a stream becomes idle (for instance no or little
>>>>>> activity in one video source) , more resources are allocated to the
>>>>>> other sources. And this is achieved with no or very little
>>>>>> additional delay
>>>> buildup on the sender side.
>>>>>>> Another benefit with stream prioritization is that it is easier to
>>>>>>> make one
>>>>>> congestion control behave well (low delay /packet loss) esp. on a
>>>>>> wireless link. We have simulation results that supports this
>>>>>> statement albeit in the different context (QUIC congestion control
>>>> evolution).
>>>>>>> The stream prioritization and one congestion control of course
>>>>>>> require that all the streams share the same bottleneck
>>>>>>> characteristics
>>>>>>>
>>>>>>> With that said, the biggest challenge I have seen this far is the
>>>>>>> large
>>>>>> variability of esp. video sources. Sit still in front of the camera
>>>>>> and the output rate becomes very low regardless the target rate,
>>>>>> move yourself closer to the camera and bang!!.. you get 2Mbps video
>>>>>> rate all of a sudden. This variability causes issues with stream
>>>>>> prioritization in the sense that less variable streams may be
>>>>>> pushed back. Additional code is therefore added in SCReAM to
>>>>>> correct this anomaly and ensure a (weighted) fair distribution over
>>>>>> a longer time scale. Still as mentioned in the SCReAM draft, this
>>>>>> needs to be tried out some more. I have sofar only simulated video
>>>>>> sources with variability
>>>> to see that the current implementation is reasonably robust.
>>>>>>> The bottom line here is that, while scheduling of streams with
>>>>>>> static
>>>>>> properties may be considered simple, real video may be a taller order.
>>>>>>>
>>>>>>> /Ingemar
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>>>> Sent: den 20 juli 2015 10:03
>>>>>>>> To: Karen E. E. Nielsen
>>>>>>>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org;
>>>>>>>> Mirja KÃ¼hlewind
>>>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>>>
>>>>>>>>
>>>>>>>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
>>>>>>>>> <karen.nielsen@tieto.com> wrote:
>>>>>>>>>
>>>>>>>>> HI,
>>>>>>>>>
>>>>>>>>> Yes - there is the possibility to implement coupled congestion
>>>>>>>>> control with scheduling priorities, There is no doubt about that
>>>>>>>>> :-), Indeed SCTP does it and scream does it.
>>>>>>>>> But it is not so well-described in the scream draft how exactly
>>>>>>>>> the prioritization works and which means an application has to
>>>>>>>>> define different priorities.
>>>>>>>>> (For information then for SCTP a number of different scheduling
>>>>>>>>> possibilities is described in
>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>>>>>>>>>
>>>>>>>>> Then for RMCAT coupled congestion control  we have the Wezlz,
>>>>>>>>> Safiqul proposal where the coupled is done in-between per
>>>>>>>>> flow-CC contexts by prioritization on manipulation of the cwnd.
>>>>>>>>> And the we also have, a not so detailed proposal/description, on
>>>>>>>>> how the same can be achieved via scheduling (scream).
>>>>>>>>> It should be ok to allow for different ways to implement
>>>>>>>>> coupling, but we should then eventually have one document that
>>>>>>>>> describes both solutions. Shouldn't we ?
>>>>>>>>
>>>>>>>> I think so. There is already (short, because it's so simple) text
>>>>>>>> about scheduling in coupled-cc and we can extend that and make it
>>>>>>>> stand out more clearly (now it's in the intro I think).
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Michael
>>>>>>>
>>>
>>
>> --
>> ------------------------------------------
>> Dipl.-Ing. Mirja KÃ¼hlewind
>> Communication Systems Group
>> Institute TIK, ETH ZÃ¼rich
>> Gloriastrasse 35, 8092 ZÃ¼rich, Switzerland
>>
>> Room ETZ G93
>> phone: +41 44 63 26932
>> email: mirja.kuehlewind@tik.ee.ethz.ch
>> ------------------------------------------

-- 
------------------------------------------
Dipl.-Ing. Mirja KÃ¼hlewind
Communication Systems Group
Institute TIK, ETH ZÃ¼rich
Gloriastrasse 35, 8092 ZÃ¼rich, Switzerland

Room ETZ G93
phone: +41 44 63 26932
email: mirja.kuehlewind@tik.ee.ethz.ch
------------------------------------------


From nobody Thu Jul 30 15:30:34 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34141ACF1D for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 15:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 YyH0fXfyL4hD for <rmcat@ietfa.amsl.com>; Thu, 30 Jul 2015 15:30:30 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02F3E1ACEF7 for <rmcat@ietf.org>; Thu, 30 Jul 2015 15:30:29 -0700 (PDT)
X-AuditID: c1b4fb3a-f79356d000006281-60-55baa58484f5
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id B2.84.25217.485AAB55; Fri, 31 Jul 2015 00:30:28 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0210.002; Fri, 31 Jul 2015 00:30:27 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiD//+NBAAAEo4fAASxm34AABZKoIP//8hWA//8+0tA=
Date: Thu, 30 Jul 2015 22:30:27 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4FCF5@ESESSMB205.ericsson.se>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se> <55B9FD05.1050807@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se> <55BA16BF.6030101@tik.ee.ethz.ch>
In-Reply-To: <55BA16BF.6030101@tik.ee.ethz.ch>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3Rrdl6a5Qg8ULBC0Otc5ksfhxdier xYbVU1gsVt/8wObA4rFkyU8mj9WrHzJ7HHoe5HHsw1e2AJYoLpuU1JzMstQifbsEroxnmzex FpxpZqy4NvsoYwPjnAbGLkZODgkBE4kl9+ayQ9hiEhfurWfrYuTiEBI4yiix8+5iZpCEkMBi RomDF6NBbDYBG4mVh76DNYsIFEjs2DmbGaSBWeAUo8TEZXOYQBLCQEXtb/pZIYpsJU7+Wc4E UiQiMI9RYuXSs2wgCRYBVYmZp7eBreYV8JX4cPktM8TqFewSN66dBevmFNCT+DrrJthURgFZ ifvf77GA2MwC4hK3nsxngrhbQGLJnvPMELaoxMvH/1ghbCWJtYe3A9VzANVrSqzfpQ/Rqigx pfsh1F5BiZMzn7BMYBSbhWTqLISOWUg6ZiHpWMDIsopRtDi1uDg33chIL7UoM7m4OD9PLy+1 ZBMjMNYObvlttYPx4HPHQ4wCHIxKPLwJe3eGCrEmlhVX5h5ilOZgURLnnbE5L1RIID2xJDU7 NbUgtSi+qDQntfgQIxMHp1QD4/SYTqmELMGIi88nrND1kOZmvmrpGMRt9yXgV0/jsfOGNgd3 Fsx2vPexzfilT9Q+2ayEs9GfvIKPvbq0pMwp5c+Swy9eiH0y37w0wWPvMtXIOLarkx2jfDT5 Nyz4JdQaITs5/5S11PXDz5Q2Tpzhtpy109nsmfZkg8WC2+uf1p+4YS3qYJOposRSnJFoqMVc VJwIALOgrHuWAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/TC-r9MoihCVLfivlLk1wfCz6cV0>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Jul 2015 22:30:34 -0000

SGkNCg0KVGhlIHRlcm0gdHJhbnNtaXNzaW9uIHNjaGVkdWxlciB3YXMgdGFrZW4gZnJvbSBhIGRp
c2N1c3Npb24gb24gdGhlIFRDUE0gV0cgKHRocmVhZCBzdGFydHMgYXQgaHR0cDovL3d3dy5pZXRm
Lm9yZy9tYWlsLWFyY2hpdmUvd2ViL3RjcG0vY3VycmVudC9tc2cwODc2OC5odG1sICksIHRoZSBk
ZWZpbml0aW9uIHdhcyBib3Jyb3dlZCBmcm9tIFRDUCBsYW1pbmFyLiBUaGlzIG1lYW5zIHRoYXQg
SSBhbSBjdXJyZW50bHkgY29udmluY2VkIGFib3V0IHRoZSBuYW1lIGNoYW5nZS4gDQpUaGUgUlRQ
IHBhY2tldHMgZnJvbSB0d28gb3IgbW9yZSBzdHJlYW1zIChSVFAgcXVldWVzKSBhcmUgaW4gaXRz
IHNpbXBsZXN0IGZvcm0gcGlja2VkIGluIGEgcm91bmQtcm9iaW4gZmFzaGlvbi4gVGhpcyBpcyBk
ZXNjcmliZWQgaW4gc2VjdGlvbiA0LjEuIElmIHByaW9yaXRpemF0aW9uIGlzIGRlc2lyZWQgdGhl
biBhIGNyZWRpdCBiYXNlZCBzeXN0ZW0gaXMgdXNlZCwgZGVzY3JpYmVkIGluIGFwcGVuZGl4IEEu
Mi4gSW4gcmVhbGl0eSB0aGUgY3JlZGl0IGJhc2VkIGFwcHJvYWNoIGlzIGFsd2F5cyBlbmFibGVk
IGV2ZW4gdGhvdWdoIG5vIHByaW9yaXRpemF0aW9uIGJldHdlZW4gc3RyZWFtcyBpcyBhcHBsaWVk
LCBpbiB0aGlzIGNhc2UgYWxsIHN0cmVhbXMgZ2V0IHRoZSBzYW1lIHByaW9yaXR5Lg0KSXQgaXMg
aW1wZXJhdGl2ZSBob3dldmVyIHRoYXQgYWxsIHN0cmVhbXMgYXJlIGFibGUgdG8gdHJhbnNtaXQg
UlRQIHBhY2tldHMgZnJlcXVlbnRseS4gVGhpcyB0byBhdm9pZCBleHRyYSBxdWV1ZWluZyBkZWxh
eSBvbiB0aGUgc2VuZGVyIHNpZGUuIFdpdGggYSAyOjEgcHJpb3JpdGl6YXRpb24gYWxsb2NhdGlv
biwgb25lIHN0cmVhbSBnZXRzIHRvIHNlbmQgMiBSVFAgcGFja2V0cywgdGhlbiB0aGUgb3RoZXIg
c3RyZWFtIGdldHMgdG8gc2VuZCAxIFJUUCBwYWNrZXQuDQpJdCBpcyBmb3IgaW5zdGFuY2Ugbm90
IHRvbyBwcmFjdGljYWwgdG8gYWxsb3cgb25lIHN0cmVhbSB0byBzZW5kIGZvciAxMDBtcyBhbmQg
dGhlbiBsZXQgdGhlIG90aGVyIHN0cmVhbSB0cmFuc21pdCBmb3IgNTBtcywgdGhpcyB3aWxsIG9u
bHkgaW5jcmVhc2UgbGF0ZW5jeSBhbmQgcmlzayBtYWtpbmcgdGhlIHZpZGVvIGNob3BweS4gVGhp
cyBpcyB0aGUgbWFpbiByZWFzb24gd2h5IFNDUmVBTXMgdHJhbnNtaXQgc2NoZWR1bGluZyBhbmQg
cHJpb3JpdGl6YXRpb24gb3BlcmF0ZXMgaXMgUlRQIHBhY2tldCB0cmFuc21pc3Npb24gY2xvY2tl
ZCBpbnN0ZWFkIG9mIHRpbWVyIGJhc2VkLiANCkJ1dC4uLm9mIGNvdXJzZSBvbmUgY2FuIGltcGxl
bWVudCB0aW1lciBiYXNlZCBwcmlvcml0aXphdGlvbiB3aXRoIHNob3J0ZXIgaW50ZXJ2YWxzLCBp
biB3aGljaCBjYXNlIHRoZSBkaWZmZXJlbmNlcyB3b3VsZCBiZSBzbWFsbGVyLCBidXQgZm9yIFND
UmVBTSBpdCBpcyBtb3JlIHByYWN0aWNhbCB0byBiZSBSVFAgcGFja2V0IHRyYW5zbWlzc2lvbiBi
YXNlZC4NCg0KUFMsIGRlbGliZXJhdGVseSBvbWl0dGVkIHRoZSBmYWN0IHRoYW4gb25lIChvciBl
dmVuIGFsbCBzdHJlYW1zKSBtYXkgaGF2ZSBub3RoaW5nIHRvIHRyYW5zbWl0LCB0aGlzIGlzIGhh
bmRsZWQgaW4gdGhlIGNvZGUgaG93ZXZlci4gIEZvciB0aG9zZSBpbnRlcmVzdGVkLCBpdCBpcyBw
b3NzaWJsZSB0byBleHBlcmltZW50IHdpdGggdGhlIEMrKyBjb2RlIHRvIHNlZSBob3cgdGhlIHN0
cmVhbSBwcmlvcml0aXphdGlvbiBwZXJmb3Jtcy4NCg0KDQovSW5nZW1hciAgDQogDQoNCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNaXJqYSBLw7xobGV3aW5kIFttYWls
dG86bWlyamEua3VlaGxld2luZEB0aWsuZWUuZXRoei5jaF0NCj4gU2VudDogZGVuIDMwIGp1bGkg
MjAxNSAxNDoyMQ0KPiBUbzogSW5nZW1hciBKb2hhbnNzb24gUzsgTWljaGFlbCBXZWx6bA0KPiBD
YzogS2FyZW4gRS4gRS4gTmllbHNlbjsgWmFoZWR1enphbWFuIFNhcmtlcjsgcm1jYXRAaWV0Zi5v
cmcNCj4gU3ViamVjdDogUmU6IFtybWNhdF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtcm1jYXQtc2Ny
ZWFtLWNjLTAxDQo+IA0KPiBIaSBJbmdlbWFyLA0KPiANCj4gb2theSB0aGFua3MgZm9yIHRoZSBj
bGFyaWZpY2F0aW9uLiBJIGRpc2N1c3NlZCB0aGlzIHdpdGggWmFoZWQgYW5kIHRoZQ0KPiBzY2hl
ZHVsZXIgYXMgZGVzY3JpYmVkIGluIHNlY3Rpb24gNC4xLjIuMi4gc2hvdWxkIHByb2JhYmx5IGJl
IHJlbmFtZWQgdG8NCj4gc29tZXRoaW5nIGxpa2Ugc2VuZGluZyByYXRlIGNvbnRyb2xsZXIgYmVj
YXVzZSB3aXRob3V0IHRoZSBwcmlvcml0aXphdGlvbiBpdCdzDQo+IG9ubHkgaGFuZGxpbmcgb25l
IGZsb3cgYXQgYSB0aW1lLCByaWdodD8NCj4gDQo+IE1pcmphDQo+IA0KPiANCj4gT24gMzAuMDcu
MjAxNSAxMzoyMiwgSW5nZW1hciBKb2hhbnNzb24gUyB3cm90ZToNCj4gPiBIaQ0KPiA+DQo+ID4g
UHJvYmFibHkgbmVlZHMgc29tZSBjbGFyaWZpY2F0aW9uLiBUaGUgdHJhbnNtaXNzaW9uIHNjaGVk
dWxlciB0aGF0IGRlY2lkZXMNCj4gd2hlbiB0byB0cmFuc21pdCBSVFAgcGFja2V0cyBpcyBhbiBp
bnRlZ3JhbCBwYXJ0IG9mIFNDUmVBTSBhbmQgZGVzY3JpYmVkIGluDQo+IHNlY3Rpb24gNC4xLjIu
MiBpbiB0aGUgZHJhZnQuDQo+ID4gU3RyZWFtIHByaW9yaXRpemF0aW9uIGlzIGFwcGxpZWQgd2hl
biB0d28gb3IgbW9yZSBzdHJlYW1zIHNoYXJlIGENCj4gY29uZ2VzdGlvbiBjb250cm9sIGFuZCBp
cyBkZXNjcmliZWQgaW4gc2VjdGlvbiBBLjIuDQo+ID4NCj4gPiBUaGUgZm9ybWVyIGhhcyBiZWVu
IGV2YWx1YXRlZCBlYXJsaWVyICwgdGhlIGxhdHRlciBpcyBvbmx5IGV4ZW1wbGlmaWVkDQo+ID4g
aW4NCj4gPiBodHRwczovL2dpdGh1Yi5jb20vRXJpY3Nzb25SZXNlYXJjaC9zY3JlYW0vYmxvYi9t
YXN0ZXIvU0NSZUFNLQ0KPiBkZXNjcmlwdA0KPiA+IGlvbi5wZGYNCj4gPg0KPiA+IFRoZSBldmFs
dWF0aW9uIG9mIHN0cmVhbSBwcmlvcml0aXphdGlvbiBsZWFkcyB0byBhIHNldCBvZiBmb2xsb3ct
dXANCj4gcXVlc3Rpb25zLiBXaGF0IGtpbmQgb2Ygc291cmNlIGJlaGF2aW9yIGRvIGJlIGFzc3Vt
ZSwgaXMgaXQgQ0JSICBvciBWQlIuDQo+IFN0cmVhbSBwcmlvcml0aXphdGlvbiBvZiBDQlIgc291
cmNlcyBpcyBxdWl0ZSB0cml2aWFsIHRvIHNvbHZlIElNTywgVkJSIGlzIG1vcmUNCj4gY29tcGxp
Y2F0ZWQuDQo+ID4NCj4gPiAvSW5nZW1hcg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4+IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IE1pcmphIEvDvGhsZXdpbmQgW21haWx0
bzptaXJqYS5rdWVobGV3aW5kQHRpay5lZS5ldGh6LmNoXQ0KPiA+PiBTZW50OiBkZW4gMzAganVs
aSAyMDE1IDEyOjMyDQo+ID4+IFRvOiBJbmdlbWFyIEpvaGFuc3NvbiBTOyBNaWNoYWVsIFdlbHps
DQo+ID4+IENjOiBLYXJlbiBFLiBFLiBOaWVsc2VuOyBaYWhlZHV6emFtYW4gU2Fya2VyOyBybWNh
dEBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBSZTogW3JtY2F0XSBSZXZpZXcgb2YgZHJhZnQtaWV0
Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gPj4NCj4gPj4gSGkgSW5nZW1hciwNCj4gPj4NCj4gPj4g
QSBxdWljayBjb21tZW50IGhlcmU6DQo+ID4+DQo+ID4+PiBJIHRoaW5rIGhvd2V2ZXIgdGhlIHNj
aGVkdWxpbmcgaXQgd2lsbCByZW1haW4gaW4gdGhlIHJ1bm5pbmcgY29kZQ0KPiA+Pj4gKEMrKyBj
b2RlDQo+ID4+IGFuZCBPV1IpIGF0IGxlYXN0IHVudGlsIGEgZ29vZCBhbHRlcm5hdGl2ZSBpcyBh
dmFpbGFibGUuDQo+ID4+DQo+ID4+IElmIHRoZSBzY2hlZHVsaW5nIHN0YXlzIGluIHRoZSBhcHBl
bmRpeCwgd2UgZGVmaW5pdGVseSBuZWVkIHRvIHNlZQ0KPiA+PiBldmFsdWF0aW9uIHJlc3VsdHMg
Zm9yIFNjcmVhbSB3aXRob3V0IHNjaGVkdWxpbmcuIElmIHNjaGVkdWxpbmcgaXMgYW4NCj4gPj4g
ZXNzZW50aWFsIHBhcnQgb2YgU2NyZWFtLCB5b3UgYWxzbyBuZWVkIGEgc2hhcmVkIGJvdHRsZW5l
Y2sNCj4gPj4gZGV0ZWN0aW9uISBBY3R1YWxseSBJIGd1ZXNzIHdlIG5lZWQgdG8gc2VlIGV2YWx1
YXRpb24gcmVzdWx0cyBmb3INCj4gPj4gU2NyZWFtIHdpdGhvdXQgc2NoZWR1bGluZyBpbiBhbnkg
Y2FzZSwgYmVjYXVzZSB0aGVyZSBtaWdodCBhbHdheXMgYmUNCj4gPj4gdGhlIGNhc2Ugd2hlcmUg
dGhlIHNiZCBkb2VzIG5vdCBkZXRlY3QgYSBzaGFyZWQgYm90dGxlbmVjayBjb3JyZWN0bHkuDQo+
ID4+DQo+ID4+IE1pcmphDQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+Pg0KPiA+Pj4gL0luZ2VtYXIN
Cj4gPj4+DQo+ID4+Pg0KPiA+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+Pj4g
RnJvbTogTWljaGFlbCBXZWx6bCBbbWFpbHRvOm1pY2hhd2VAaWZpLnVpby5ub10NCj4gPj4+PiBT
ZW50OiBkZW4gMjQganVsaSAyMDE1IDEwOjU3DQo+ID4+Pj4gVG86IEluZ2VtYXIgSm9oYW5zc29u
IFMNCj4gPj4+PiBDYzogS2FyZW4gRS4gRS4gTmllbHNlbjsgWmFoZWR1enphbWFuIFNhcmtlcjsg
cm1jYXRAaWV0Zi5vcmc7IE1pcmphDQo+ID4+Pj4gS8O8aGxld2luZA0KPiA+Pj4+IFN1YmplY3Q6
IFJlOiBbcm1jYXRdIFJldmlldyBvZiBkcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMQ0KPiA+
Pj4+DQo+ID4+Pj4gTm8uDQo+ID4+Pj4NCj4gPj4+PiBPdXIgYWxnbyBsZXRzIHlvdSBhc3NpZ24g
cHJpb3JpdGllcywgYW5kIHRoZXkgYXJlIHZhbGlkIGF0IHRoZSB0aW1lDQo+ID4+Pj4geW91IHNl
dCB0aGVtLCB0aGV5IGp1c3QgZ2l2ZSB5b3UgYSBwb3J0aW9uIG9mIHRoZSBvdmVyYWxsIHJhdGUg
YW5kDQo+ID4+Pj4gaXQgYXBwbGllcyBhcyBzb29uIGFzIHlvdSBzZXQgaXQuDQo+ID4+Pj4gSWYg
IHlvdSB3YW50IHRvIGFkanVzdCBwcmlvcml0aWVzIGJhc2VkIG9uIHRoZSBjb2RlciBvdXRwdXQg
cmF0ZQ0KPiA+Pj4+IHZhcmlhdGlvbiwgeW91IGNhbiBpbXBsZW1lbnQgdGhpcyB1c2luZyBvdXIg
YWxnbyBvciB3aXRoIGEgc2NoZWR1bGVyLg0KPiA+Pj4+IEEgc2NoZWR1bGVyIG9wZXJhdGVzIHBl
ciBwYWNrZXQsIHdlIG9wZXJhdGUgcGVyIHRpbWUsIHNvDQo+ID4+IGltcGxlbWVudGF0aW9uLXdp
c2UgaXQncyBhIGJpdCBkaWZmZXJlbnQuDQo+ID4+Pj4NCj4gPj4+PiBNeSBwb2ludCBpcyBvbmx5
OiB3aGV0aGVyIHlvdSBkbyBpdCB3aXRoIG91ciBhbGdvcml0aG0gb3Igd2l0aG91dCBhDQo+ID4+
Pj4gc2NoZWR1bGVyLCBJIHRoaW5rIHRoaXMgc2hvdWxkIG5vdCBiZSBpbiBvdXIgZHJhZnQgIChh
bmQgSSdtIG5ldXRyYWwgYWJvdXQ6DQo+ID4+Pj4gc2hvdWxkIGl0IGJlIGluIHRoZSBTQ1JlQU0g
ZHJhZnQgb3Igc2VwYXJhdGUgZnJvbSBpdCkuDQo+ID4+Pj4NCj4gPj4+PiBDaGVlcnMsDQo+ID4+
Pj4gTWljaGFlbA0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+Pj4gT24gMjQuIGp1bC4gMjAxNSwgYXQg
MTAuNDIsIEluZ2VtYXIgSm9oYW5zc29uIFMNCj4gPj4+PiA8aW5nZW1hci5zLmpvaGFuc3NvbkBl
cmljc3Nvbi5jb20+IHdyb3RlOg0KPiA+Pj4+Pg0KPiA+Pj4+PiBIaQ0KPiA+Pj4+Pg0KPiA+Pj4+
PiBOb3Qgc3VyZSBJIGdldCBpdC4NCj4gPj4+Pj4gRG8geW91IG1lYW4gdGhhdCBjb3VwbGluZyBh
bGdvIGlzIGltbXVuZSB0byB2aWRlbyBjb2RlciBvdXRwdXQNCj4gPj4+Pj4gcmF0ZQ0KPiA+Pj4+
IHZhcmlhdGlvbiA/DQo+ID4+Pj4+DQo+ID4+Pj4+IC9JbmdlbWFyDQo+ID4+Pj4+DQo+ID4+Pj4+
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+Pj4gRnJvbTogTWljaGFlbCBXZWx6
bCBbbWFpbHRvOm1pY2hhd2VAaWZpLnVpby5ub10NCj4gPj4+Pj4+IFNlbnQ6IGRlbiAyMiBqdWxp
IDIwMTUgMTE6MTYNCj4gPj4+Pj4+IFRvOiBJbmdlbWFyIEpvaGFuc3NvbiBTDQo+ID4+Pj4+PiBD
YzogS2FyZW4gRS4gRS4gTmllbHNlbjsgWmFoZWR1enphbWFuIFNhcmtlcjsgcm1jYXRAaWV0Zi5v
cmc7DQo+ID4+Pj4+PiBNaXJqYSBLw7xobGV3aW5kDQo+ID4+Pj4+PiBTdWJqZWN0OiBSZTogW3Jt
Y2F0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ybWNhdC1zY3JlYW0tY2MtMDENCj4gPj4+Pj4+DQo+
ID4+Pj4+PiB1bmRlcnN0b29kOyBpIHRoaW5rIHRoZXNlIGRldGFpbHMgYXJlIGJleW9uZCB0aGUg
c2NvcGUgb2Ygb3VyDQo+ID4+Pj4+PiBjb3VwbGluZyBkcmFmdCB3aGljaCBmb2N1c2VzIG9uIGEg
ZGlmZmVyZW50IG1ldGhvZC4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBjaGVlcnMNCj4gPj4+Pj4+IG1p
Y2hhZWwNCj4gPj4+Pj4+DQo+ID4+Pj4+PiBTZW50IGZyb20gbXkgaVBob25lDQo+ID4+Pj4+Pg0K
PiA+Pj4+Pj4+IE9uIDIyLiBqdWxpIDIwMTUsIGF0IDExOjA2LCBJbmdlbWFyIEpvaGFuc3NvbiBT
DQo+ID4+Pj4+PiA8aW5nZW1hci5zLmpvaGFuc3NvbkBlcmljc3Nvbi5jb20+IHdyb3RlOg0KPiA+
Pj4+Pj4+DQo+ID4+Pj4+Pj4gSGkNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IFN0aWxsIHdhaXRpbmcg
Zm9yIHRoZSBzdW1tZXIgdG8gc2hvdyB1cCBzbyBJJ2xsIHRyeSB0byBjaGltZSBpbg0KPiA+Pj4+
Pj4+IHdoaWxlIHRoaXMNCj4gPj4+Pj4+IHN1YmplY3QgaXMgYXQgbGVhc3QgbHVrZS13YXJtLiBJ
IG1heSBiZSBzbG93IHdpdGggZm9sbG93IHVwIG9uDQo+ID4+Pj4+PiB0aGlzLCBzb3JyeSBmb3Ig
dGhhdCBpbiBhZHZhbmNlLg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gU3RyZWFtIHByaW8gaW4gU0NS
ZUFNIGlzIG91dGxpbmVkIGluIHNlY3Rpb24gQS4yIGluIHRoZSBkcmFmdA0KPiA+Pj4+Pj4gKGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJtY2F0LXNjcmVhbS1jYy0wMSNw
YWdlLTI4DQo+ICkuDQo+ID4+Pj4+PiBJbiBpdHMgZnVuY3Rpb24gaXQgcmVzZW1ibGVzIGZxLWNv
ZGVsIHF1aXRlIGEgbG90IGluIHRoZSBzZW5zZQ0KPiA+Pj4+Pj4gdGhhdCBzdHJlYW1zIHRoYXQg
ZG8gbm90IGdldCBzY2hlZHVsZWQgYXQgYSBnaXZlbiBzY2hlZHVsaW5nDQo+ID4+Pj4+PiBpbnN0
YW50IGdldHMgYSBjcmVkaXQgdGhhdCBpcyB1c2VkIHRvIGluY3JlYXNlIHRoZSBjaGFuY2Ugb2YN
Cj4gPj4+Pj4+IGJlaW5nIHNjaGVkdWxlZCBhdCB0aGUgbmV4dCBzY2hlZHVsaW5nIGluc3RhbnQu
IEEgY29uZmlndXJhYmxlDQo+ID4+Pj4+PiBzY2hlZHVsaW5nIHByaW9yaXR5IGRldGVybWluZXMN
Cj4gPj4+PiBob3cgbXVjaCBjcmVkaXQgIHRoYXQgaXMgZ2l2ZW4uDQo+ID4+Pj4+PiBMb29raW5n
IGluIHRoZQ0KPiA+Pj4+Pj4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9wZGYvZHJhZnQtaWV0Zi10
c3Z3Zy1zY3RwLW5kYXRhLTA0LnBkZg0KPiA+Pj4+Pj4gZHJhZnQgSSB3b3VsZCBzYXkgdGhhdCB0
aGlzIHJlc2VtYmxlcyB0aGUgIldlaWdodGVkIEZhaXIgUXVldWVpbmcNCj4gPj4+Pj4+IFNjaGVk
dWxlciIgIHRoZSBtb3N0LiBTb21lIGFkZGl0aW9uYWwgbWVhbnMgYXJlIG5lZWRlZCB0byBtYWtl
DQo+ID4+Pj4+PiB0aGlzIHdvcmsgd2VsbCBpbiByZWFsaXR5IHRob3VnaCAoc2VlIGJlbG93KS4N
Cj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IFRoZSBiZW5lZml0IHdpdGggZG9pbmcgc2NoZWR1bGluZyBw
cmlvcml0eSBhbmQgYSBjb21tb24NCj4gPj4+Pj4+PiBjb25nZXN0aW9uDQo+ID4+Pj4+PiBjb250
cm9sIGlzIGFuIGluY3JlYXNlZCBwcm9iYWJpbGl0eSB0aGF0IHRoZSBwYXRoIGNhcGFjaXR5IGlz
DQo+ID4+Pj4+PiBmdWxseSB1dGlsaXplZCwgaWYgYSBzdHJlYW0gYmVjb21lcyBpZGxlIChmb3Ig
aW5zdGFuY2Ugbm8gb3INCj4gPj4+Pj4+IGxpdHRsZSBhY3Rpdml0eSBpbiBvbmUgdmlkZW8gc291
cmNlKSAsIG1vcmUgcmVzb3VyY2VzIGFyZQ0KPiA+Pj4+Pj4gYWxsb2NhdGVkIHRvIHRoZSBvdGhl
ciBzb3VyY2VzLiBBbmQgdGhpcyBpcyBhY2hpZXZlZCB3aXRoIG5vIG9yDQo+ID4+Pj4+PiB2ZXJ5
IGxpdHRsZSBhZGRpdGlvbmFsIGRlbGF5DQo+ID4+Pj4gYnVpbGR1cCBvbiB0aGUgc2VuZGVyIHNp
ZGUuDQo+ID4+Pj4+Pj4gQW5vdGhlciBiZW5lZml0IHdpdGggc3RyZWFtIHByaW9yaXRpemF0aW9u
IGlzIHRoYXQgaXQgaXMgZWFzaWVyDQo+ID4+Pj4+Pj4gdG8gbWFrZSBvbmUNCj4gPj4+Pj4+IGNv
bmdlc3Rpb24gY29udHJvbCBiZWhhdmUgd2VsbCAobG93IGRlbGF5IC9wYWNrZXQgbG9zcykgZXNw
LiBvbiBhDQo+ID4+Pj4+PiB3aXJlbGVzcyBsaW5rLiBXZSBoYXZlIHNpbXVsYXRpb24gcmVzdWx0
cyB0aGF0IHN1cHBvcnRzIHRoaXMNCj4gPj4+Pj4+IHN0YXRlbWVudCBhbGJlaXQgaW4gdGhlIGRp
ZmZlcmVudCBjb250ZXh0IChRVUlDIGNvbmdlc3Rpb24NCj4gPj4+Pj4+IGNvbnRyb2wNCj4gPj4+
PiBldm9sdXRpb24pLg0KPiA+Pj4+Pj4+IFRoZSBzdHJlYW0gcHJpb3JpdGl6YXRpb24gYW5kIG9u
ZSBjb25nZXN0aW9uIGNvbnRyb2wgb2YgY291cnNlDQo+ID4+Pj4+Pj4gcmVxdWlyZSB0aGF0IGFs
bCB0aGUgc3RyZWFtcyBzaGFyZSB0aGUgc2FtZSBib3R0bGVuZWNrDQo+ID4+Pj4+Pj4gY2hhcmFj
dGVyaXN0aWNzDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+PiBXaXRoIHRoYXQgc2FpZCwgdGhlIGJpZ2dl
c3QgY2hhbGxlbmdlIEkgaGF2ZSBzZWVuIHRoaXMgZmFyIGlzDQo+ID4+Pj4+Pj4gdGhlIGxhcmdl
DQo+ID4+Pj4+PiB2YXJpYWJpbGl0eSBvZiBlc3AuIHZpZGVvIHNvdXJjZXMuIFNpdCBzdGlsbCBp
biBmcm9udCBvZiB0aGUNCj4gPj4+Pj4+IGNhbWVyYSBhbmQgdGhlIG91dHB1dCByYXRlIGJlY29t
ZXMgdmVyeSBsb3cgcmVnYXJkbGVzcyB0aGUgdGFyZ2V0DQo+ID4+Pj4+PiByYXRlLCBtb3ZlIHlv
dXJzZWxmIGNsb3NlciB0byB0aGUgY2FtZXJhIGFuZCBiYW5nISEuLiB5b3UgZ2V0DQo+ID4+Pj4+
PiAyTWJwcyB2aWRlbyByYXRlIGFsbCBvZiBhIHN1ZGRlbi4gVGhpcyB2YXJpYWJpbGl0eSBjYXVz
ZXMgaXNzdWVzDQo+ID4+Pj4+PiB3aXRoIHN0cmVhbSBwcmlvcml0aXphdGlvbiBpbiB0aGUgc2Vu
c2UgdGhhdCBsZXNzIHZhcmlhYmxlDQo+ID4+Pj4+PiBzdHJlYW1zIG1heSBiZSBwdXNoZWQgYmFj
ay4gQWRkaXRpb25hbCBjb2RlIGlzIHRoZXJlZm9yZSBhZGRlZCBpbg0KPiA+Pj4+Pj4gU0NSZUFN
IHRvIGNvcnJlY3QgdGhpcyBhbm9tYWx5IGFuZCBlbnN1cmUgYSAod2VpZ2h0ZWQpIGZhaXINCj4g
Pj4+Pj4+IGRpc3RyaWJ1dGlvbiBvdmVyIGEgbG9uZ2VyIHRpbWUgc2NhbGUuIFN0aWxsIGFzIG1l
bnRpb25lZCBpbiB0aGUNCj4gPj4+Pj4+IFNDUmVBTSBkcmFmdCwgdGhpcyBuZWVkcyB0byBiZSB0
cmllZCBvdXQgc29tZSBtb3JlLiBJIGhhdmUgc29mYXINCj4gPj4+Pj4+IG9ubHkgc2ltdWxhdGVk
IHZpZGVvIHNvdXJjZXMgd2l0aCB2YXJpYWJpbGl0eQ0KPiA+Pj4+IHRvIHNlZSB0aGF0IHRoZSBj
dXJyZW50IGltcGxlbWVudGF0aW9uIGlzIHJlYXNvbmFibHkgcm9idXN0Lg0KPiA+Pj4+Pj4+IFRo
ZSBib3R0b20gbGluZSBoZXJlIGlzIHRoYXQsIHdoaWxlIHNjaGVkdWxpbmcgb2Ygc3RyZWFtcyB3
aXRoDQo+ID4+Pj4+Pj4gc3RhdGljDQo+ID4+Pj4+PiBwcm9wZXJ0aWVzIG1heSBiZSBjb25zaWRl
cmVkIHNpbXBsZSwgcmVhbCB2aWRlbyBtYXkgYmUgYSB0YWxsZXINCj4gb3JkZXIuDQo+ID4+Pj4+
Pj4NCj4gPj4+Pj4+PiAvSW5nZW1hcg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0K
PiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+Pj4+
Pj4+IEZyb206IE1pY2hhZWwgV2VsemwgW21haWx0bzptaWNoYXdlQGlmaS51aW8ubm9dDQo+ID4+
Pj4+Pj4+IFNlbnQ6IGRlbiAyMCBqdWxpIDIwMTUgMTA6MDMNCj4gPj4+Pj4+Pj4gVG86IEthcmVu
IEUuIEUuIE5pZWxzZW4NCj4gPj4+Pj4+Pj4gQ2M6IFphaGVkdXp6YW1hbiBTYXJrZXI7IEluZ2Vt
YXIgSm9oYW5zc29uIFM7IHJtY2F0QGlldGYub3JnOw0KPiA+Pj4+Pj4+PiBNaXJqYSBLw7xobGV3
aW5kDQo+ID4+Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbcm1jYXRdIFJldmlldyBvZiBkcmFmdC1pZXRm
LXJtY2F0LXNjcmVhbS1jYy0wMQ0KPiA+Pj4+Pj4+Pg0KPiA+Pj4+Pj4+Pg0KPiA+Pj4+Pj4+Pj4+
IE9uIDIwLiBqdWwuIDIwMTUsIGF0IDA3LjMyLCBLYXJlbiBFbGlzYWJldGggRWdlZGUgTmllbHNl
bg0KPiA+Pj4+Pj4+Pj4gPGthcmVuLm5pZWxzZW5AdGlldG8uY29tPiB3cm90ZToNCj4gPj4+Pj4+
Pj4+DQo+ID4+Pj4+Pj4+PiBISSwNCj4gPj4+Pj4+Pj4+DQo+ID4+Pj4+Pj4+PiBZZXMgLSB0aGVy
ZSBpcyB0aGUgcG9zc2liaWxpdHkgdG8gaW1wbGVtZW50IGNvdXBsZWQgY29uZ2VzdGlvbg0KPiA+
Pj4+Pj4+Pj4gY29udHJvbCB3aXRoIHNjaGVkdWxpbmcgcHJpb3JpdGllcywgVGhlcmUgaXMgbm8g
ZG91YnQgYWJvdXQNCj4gPj4+Pj4+Pj4+IHRoYXQgOi0pLCBJbmRlZWQgU0NUUCBkb2VzIGl0IGFu
ZCBzY3JlYW0gZG9lcyBpdC4NCj4gPj4+Pj4+Pj4+IEJ1dCBpdCBpcyBub3Qgc28gd2VsbC1kZXNj
cmliZWQgaW4gdGhlIHNjcmVhbSBkcmFmdCBob3cNCj4gPj4+Pj4+Pj4+IGV4YWN0bHkgdGhlIHBy
aW9yaXRpemF0aW9uIHdvcmtzIGFuZCB3aGljaCBtZWFucyBhbg0KPiA+Pj4+Pj4+Pj4gYXBwbGlj
YXRpb24gaGFzIHRvIGRlZmluZSBkaWZmZXJlbnQgcHJpb3JpdGllcy4NCj4gPj4+Pj4+Pj4+IChG
b3IgaW5mb3JtYXRpb24gdGhlbiBmb3IgU0NUUCBhIG51bWJlciBvZiBkaWZmZXJlbnQNCj4gPj4+
Pj4+Pj4+IHNjaGVkdWxpbmcgcG9zc2liaWxpdGllcyBpcyBkZXNjcmliZWQgaW4NCj4gPj4+Pj4+
Pj4+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1zY3Rw
LW5kYXRhLy4pDQo+ID4+Pj4+Pj4+Pg0KPiA+Pj4+Pj4+Pj4gVGhlbiBmb3IgUk1DQVQgY291cGxl
ZCBjb25nZXN0aW9uIGNvbnRyb2wgIHdlIGhhdmUgdGhlIFdlemx6LA0KPiA+Pj4+Pj4+Pj4gU2Fm
aXF1bCBwcm9wb3NhbCB3aGVyZSB0aGUgY291cGxlZCBpcyBkb25lIGluLWJldHdlZW4gcGVyDQo+
ID4+Pj4+Pj4+PiBmbG93LUNDIGNvbnRleHRzIGJ5IHByaW9yaXRpemF0aW9uIG9uIG1hbmlwdWxh
dGlvbiBvZiB0aGUgY3duZC4NCj4gPj4+Pj4+Pj4+IEFuZCB0aGUgd2UgYWxzbyBoYXZlLCBhIG5v
dCBzbyBkZXRhaWxlZCBwcm9wb3NhbC9kZXNjcmlwdGlvbiwNCj4gPj4+Pj4+Pj4+IG9uIGhvdyB0
aGUgc2FtZSBjYW4gYmUgYWNoaWV2ZWQgdmlhIHNjaGVkdWxpbmcgKHNjcmVhbSkuDQo+ID4+Pj4+
Pj4+PiBJdCBzaG91bGQgYmUgb2sgdG8gYWxsb3cgZm9yIGRpZmZlcmVudCB3YXlzIHRvIGltcGxl
bWVudA0KPiA+Pj4+Pj4+Pj4gY291cGxpbmcsIGJ1dCB3ZSBzaG91bGQgdGhlbiBldmVudHVhbGx5
IGhhdmUgb25lIGRvY3VtZW50DQo+IHRoYXQNCj4gPj4+Pj4+Pj4+IGRlc2NyaWJlcyBib3RoIHNv
bHV0aW9ucy4gU2hvdWxkbid0IHdlID8NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4gSSB0aGluayBz
by4gVGhlcmUgaXMgYWxyZWFkeSAoc2hvcnQsIGJlY2F1c2UgaXQncyBzbyBzaW1wbGUpDQo+ID4+
Pj4+Pj4+IHRleHQgYWJvdXQgc2NoZWR1bGluZyBpbiBjb3VwbGVkLWNjIGFuZCB3ZSBjYW4gZXh0
ZW5kIHRoYXQgYW5kDQo+ID4+Pj4+Pj4+IG1ha2UgaXQgc3RhbmQgb3V0IG1vcmUgY2xlYXJseSAo
bm93IGl0J3MgaW4gdGhlIGludHJvIEkgdGhpbmspLg0KPiA+Pj4+Pj4+Pg0KPiA+Pj4+Pj4+PiBD
aGVlcnMsDQo+ID4+Pj4+Pj4+IE1pY2hhZWwNCj4gPj4+Pj4+Pg0KPiA+Pj4NCj4gPj4NCj4gPj4g
LS0NCj4gPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4+
IERpcGwuLUluZy4gTWlyamEgS8O8aGxld2luZA0KPiA+PiBDb21tdW5pY2F0aW9uIFN5c3RlbXMg
R3JvdXANCj4gPj4gSW5zdGl0dXRlIFRJSywgRVRIIFrDvHJpY2gNCj4gPj4gR2xvcmlhc3RyYXNz
ZSAzNSwgODA5MiBaw7xyaWNoLCBTd2l0emVybGFuZA0KPiA+Pg0KPiA+PiBSb29tIEVUWiBHOTMN
Cj4gPj4gcGhvbmU6ICs0MSA0NCA2MyAyNjkzMg0KPiA+PiBlbWFpbDogbWlyamEua3VlaGxld2lu
ZEB0aWsuZWUuZXRoei5jaA0KPiA+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gDQo+IC0tDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KPiBEaXBsLi1JbmcuIE1pcmphIEvDvGhsZXdpbmQNCj4gQ29tbXVuaWNhdGlvbiBT
eXN0ZW1zIEdyb3VwDQo+IEluc3RpdHV0ZSBUSUssIEVUSCBaw7xyaWNoDQo+IEdsb3JpYXN0cmFz
c2UgMzUsIDgwOTIgWsO8cmljaCwgU3dpdHplcmxhbmQNCj4gDQo+IFJvb20gRVRaIEc5Mw0KPiBw
aG9uZTogKzQxIDQ0IDYzIDI2OTMyDQo+IGVtYWlsOiBtaXJqYS5rdWVobGV3aW5kQHRpay5lZS5l
dGh6LmNoDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K


From nobody Fri Jul 31 00:31:36 2015
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F67F1B32D4 for <rmcat@ietfa.amsl.com>; Fri, 31 Jul 2015 00:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 cym5YXXqxdyH for <rmcat@ietfa.amsl.com>; Fri, 31 Jul 2015 00:31:32 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ED971B32D3 for <rmcat@ietf.org>; Fri, 31 Jul 2015 00:31:31 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-42-55bb2451da5e
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id FF.E3.29223.1542BB55; Fri, 31 Jul 2015 09:31:29 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0210.002; Fri, 31 Jul 2015 09:31:26 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: =?iso-8859-1?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiD//+NBAAAEo4fAASxm34AABZKoIP//8hWA//8+0tCAAiQLFQ==
Date: Fri, 31 Jul 2015 07:31:25 +0000
Message-ID: <8yysa9u4qxydnc7snuuon5ay.1438327885021@email.android.com>
References: <559FB533.5090105@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B3AE0B@ESESSMB205.ericsson.se> <55A4CD90.4020905@ericsson.com> <,> <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se> <55B9FD05.1050807@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se> <55BA16BF.6030101@tik.ee.ethz.ch>, <81564C0D7D4D2A4B9A86C8C7404A13DA34B4FCF5@ESESSMB205.ericsson.se>
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34B4FCF5@ESESSMB205.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+JvjW6gyu5Qgz3b5SwOtc5ksfhxdier xYbVU1gsVt/8wObA4rFkyU8mj9WrHzJ7HHoe5HHsw1e2AJYoLpuU1JzMstQifbsErozW7vVs BevSKn5vn8zSwNgV3MXIySEhYCLxp3kuG4QtJnHh3nogm4tDSOAoo8T2VbdZIZzFjBLrjp5n AaliE7CRWHnoOyOILSKQJ9E5ZwoLSBGzwClGiYnL5jCBJISBilZ9ugtVZCtx8s9yJpAiEYFl jBI3f05lBkmwCKhK/LnSBlTEwcEr4CZx4Uw1xLZX7BJX/v4D28Yp4CexsnM12FBGAVmJ+9/v gcWZBcQlPs99wARxt4DEkj3nmSFsUYmXj/+xQtToSdyYOoUNwtaWWLbwNVgNr4CgxMmZT1gm MIrOQjJqFpKWWUhaZiFpWcDIsopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMKYObvltsIPx 5XPHQ4wCHIxKPLwLru0KFWJNLCuuzD3EKM3BoiTOO2NzXqiQQHpiSWp2ampBalF8UWlOavEh RiYOTqkGRjMu75Vy04prVPYxpu7Yq/qOJehSyKXnKh36Ghn/dqY8SbwW/JjnnPXs7nDFY2wW vJ2PHN7zlcY5xH7xX7C9O+H0/pm/fKo5s8TaFjNIXT0cozNRS+q+jOgC6xSBENGO+5PXJbzR nz/txOzFf4ovGlytS/pydHtqzorP9wKapF7wTXp3zSt+hRJLcUaioRZzUXEiALrtruSKAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/iMEr7iKgPhkMy03KmneDvxLseLM>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 31 Jul 2015 07:31:35 -0000

Errata... Should be "not convinced about the name change", thanks for the h=
eads up Zahed :-)

...But if it is needed in order to get a common set of terms

Sent from Moxier Mail
(http://www.moxier.com)


----- Ursprungligt meddelande -----
Fr=E5n: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Till: Mirja K=FChlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <m=
ichawe@ifi.uio.no>
Kopia: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Zaheduzzaman Sarker=
 <zaheduzzaman.sarker@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Ing=
emar Johansson S <ingemar.s.johansson@ericsson.com>
Skickat: 2015-07-31 0:30
=C4mne: RE: [rmcat] Review of draft-ietf-rmcat-scream-cc-01



Hi

The term transmission scheduler was taken from a discussion on the TCPM WG =
(thread starts at http://www.ietf.org/mail-archive/web/tcpm/current/msg0876=
8.html ), the definition was borrowed from TCP laminar. This means that I a=
m currently convinced about the name change.
The RTP packets from two or more streams (RTP queues) are in its simplest f=
orm picked in a round-robin fashion. This is described in section 4.1. If p=
rioritization is desired then a credit based system is used, described in a=
ppendix A.2. In reality the credit based approach is always enabled even th=
ough no prioritization between streams is applied, in this case all streams=
 get the same priority.
It is imperative however that all streams are able to transmit RTP packets =
frequently. This to avoid extra queueing delay on the sender side. With a 2=
:1 prioritization allocation, one stream gets to send 2 RTP packets, then t=
he other stream gets to send 1 RTP packet.
It is for instance not too practical to allow one stream to send for 100ms =
and then let the other stream transmit for 50ms, this will only increase la=
tency and risk making the video choppy. This is the main reason why SCReAMs=
 transmit scheduling and prioritization operates is RTP packet transmission=
 clocked instead of timer based.
But...of course one can implement timer based prioritization with shorter i=
ntervals, in which case the differences would be smaller, but for SCReAM it=
 is more practical to be RTP packet transmission based.

PS, deliberately omitted the fact than one (or even all streams) may have n=
othing to transmit, this is handled in the code however.  For those interes=
ted, it is possible to experiment with the C++ code to see how the stream p=
rioritization performs.


/Ingemar



> -----Original Message-----
> From: Mirja K=FChlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
> Sent: den 30 juli 2015 14:21
> To: Ingemar Johansson S; Michael Welzl
> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org
> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>
> Hi Ingemar,
>
> okay thanks for the clarification. I discussed this with Zahed and the
> scheduler as described in section 4.1.2.2. should probably be renamed to
> something like sending rate controller because without the prioritization=
 it's
> only handling one flow at a time, right?
>
> Mirja
>
>
> On 30.07.2015 13:22, Ingemar Johansson S wrote:
> > Hi
> >
> > Probably needs some clarification. The transmission scheduler that deci=
des
> when to transmit RTP packets is an integral part of SCReAM and described =
in
> section 4.1.2.2 in the draft.
> > Stream prioritization is applied when two or more streams share a
> congestion control and is described in section A.2.
> >
> > The former has been evaluated earlier , the latter is only exemplified
> > in
> > https://github.com/EricssonResearch/scream/blob/master/SCReAM-
> descript
> > ion.pdf
> >
> > The evaluation of stream prioritization leads to a set of follow-up
> questions. What kind of source behavior do be assume, is it CBR  or VBR.
> Stream prioritization of CBR sources is quite trivial to solve IMO, VBR i=
s more
> complicated.
> >
> > /Ingemar
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Mirja K=FChlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
> >> Sent: den 30 juli 2015 12:32
> >> To: Ingemar Johansson S; Michael Welzl
> >> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org
> >> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
> >>
> >> Hi Ingemar,
> >>
> >> A quick comment here:
> >>
> >>> I think however the scheduling it will remain in the running code
> >>> (C++ code
> >> and OWR) at least until a good alternative is available.
> >>
> >> If the scheduling stays in the appendix, we definitely need to see
> >> evaluation results for Scream without scheduling. If scheduling is an
> >> essential part of Scream, you also need a shared bottleneck
> >> detection! Actually I guess we need to see evaluation results for
> >> Scream without scheduling in any case, because there might always be
> >> the case where the sbd does not detect a shared bottleneck correctly.
> >>
> >> Mirja
> >>
> >>
> >>
> >>>
> >>> /Ingemar
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
> >>>> Sent: den 24 juli 2015 10:57
> >>>> To: Ingemar Johansson S
> >>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
> >>>> K=FChlewind
> >>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
> >>>>
> >>>> No.
> >>>>
> >>>> Our algo lets you assign priorities, and they are valid at the time
> >>>> you set them, they just give you a portion of the overall rate and
> >>>> it applies as soon as you set it.
> >>>> If  you want to adjust priorities based on the coder output rate
> >>>> variation, you can implement this using our algo or with a scheduler=
.
> >>>> A scheduler operates per packet, we operate per time, so
> >> implementation-wise it's a bit different.
> >>>>
> >>>> My point is only: whether you do it with our algorithm or without a
> >>>> scheduler, I think this should not be in our draft  (and I'm neutral=
 about:
> >>>> should it be in the SCReAM draft or separate from it).
> >>>>
> >>>> Cheers,
> >>>> Michael
> >>>>
> >>>>
> >>>>> On 24. jul. 2015, at 10.42, Ingemar Johansson S
> >>>> <ingemar.s.johansson@ericsson.com> wrote:
> >>>>>
> >>>>> Hi
> >>>>>
> >>>>> Not sure I get it.
> >>>>> Do you mean that coupling algo is immune to video coder output
> >>>>> rate
> >>>> variation ?
> >>>>>
> >>>>> /Ingemar
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
> >>>>>> Sent: den 22 juli 2015 11:16
> >>>>>> To: Ingemar Johansson S
> >>>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org;
> >>>>>> Mirja K=FChlewind
> >>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
> >>>>>>
> >>>>>> understood; i think these details are beyond the scope of our
> >>>>>> coupling draft which focuses on a different method.
> >>>>>>
> >>>>>> cheers
> >>>>>> michael
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>>> On 22. juli 2015, at 11:06, Ingemar Johansson S
> >>>>>> <ingemar.s.johansson@ericsson.com> wrote:
> >>>>>>>
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> Still waiting for the summer to show up so I'll try to chime in
> >>>>>>> while this
> >>>>>> subject is at least luke-warm. I may be slow with follow up on
> >>>>>> this, sorry for that in advance.
> >>>>>>>
> >>>>>>> Stream prio in SCReAM is outlined in section A.2 in the draft
> >>>>>> (https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28
> ).
> >>>>>> In its function it resembles fq-codel quite a lot in the sense
> >>>>>> that streams that do not get scheduled at a given scheduling
> >>>>>> instant gets a credit that is used to increase the chance of
> >>>>>> being scheduled at the next scheduling instant. A configurable
> >>>>>> scheduling priority determines
> >>>> how much credit  that is given.
> >>>>>> Looking in the
> >>>>>> https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf
> >>>>>> draft I would say that this resembles the "Weighted Fair Queueing
> >>>>>> Scheduler"  the most. Some additional means are needed to make
> >>>>>> this work well in reality though (see below).
> >>>>>>>
> >>>>>>> The benefit with doing scheduling priority and a common
> >>>>>>> congestion
> >>>>>> control is an increased probability that the path capacity is
> >>>>>> fully utilized, if a stream becomes idle (for instance no or
> >>>>>> little activity in one video source) , more resources are
> >>>>>> allocated to the other sources. And this is achieved with no or
> >>>>>> very little additional delay
> >>>> buildup on the sender side.
> >>>>>>> Another benefit with stream prioritization is that it is easier
> >>>>>>> to make one
> >>>>>> congestion control behave well (low delay /packet loss) esp. on a
> >>>>>> wireless link. We have simulation results that supports this
> >>>>>> statement albeit in the different context (QUIC congestion
> >>>>>> control
> >>>> evolution).
> >>>>>>> The stream prioritization and one congestion control of course
> >>>>>>> require that all the streams share the same bottleneck
> >>>>>>> characteristics
> >>>>>>>
> >>>>>>> With that said, the biggest challenge I have seen this far is
> >>>>>>> the large
> >>>>>> variability of esp. video sources. Sit still in front of the
> >>>>>> camera and the output rate becomes very low regardless the target
> >>>>>> rate, move yourself closer to the camera and bang!!.. you get
> >>>>>> 2Mbps video rate all of a sudden. This variability causes issues
> >>>>>> with stream prioritization in the sense that less variable
> >>>>>> streams may be pushed back. Additional code is therefore added in
> >>>>>> SCReAM to correct this anomaly and ensure a (weighted) fair
> >>>>>> distribution over a longer time scale. Still as mentioned in the
> >>>>>> SCReAM draft, this needs to be tried out some more. I have sofar
> >>>>>> only simulated video sources with variability
> >>>> to see that the current implementation is reasonably robust.
> >>>>>>> The bottom line here is that, while scheduling of streams with
> >>>>>>> static
> >>>>>> properties may be considered simple, real video may be a taller
> order.
> >>>>>>>
> >>>>>>> /Ingemar
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
> >>>>>>>> Sent: den 20 juli 2015 10:03
> >>>>>>>> To: Karen E. E. Nielsen
> >>>>>>>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org;
> >>>>>>>> Mirja K=FChlewind
> >>>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
> >>>>>>>>> <karen.nielsen@tieto.com> wrote:
> >>>>>>>>>
> >>>>>>>>> HI,
> >>>>>>>>>
> >>>>>>>>> Yes - there is the possibility to implement coupled congestion
> >>>>>>>>> control with scheduling priorities, There is no doubt about
> >>>>>>>>> that :-), Indeed SCTP does it and scream does it.
> >>>>>>>>> But it is not so well-described in the scream draft how
> >>>>>>>>> exactly the prioritization works and which means an
> >>>>>>>>> application has to define different priorities.
> >>>>>>>>> (For information then for SCTP a number of different
> >>>>>>>>> scheduling possibilities is described in
> >>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
> >>>>>>>>>
> >>>>>>>>> Then for RMCAT coupled congestion control  we have the Wezlz,
> >>>>>>>>> Safiqul proposal where the coupled is done in-between per
> >>>>>>>>> flow-CC contexts by prioritization on manipulation of the cwnd.
> >>>>>>>>> And the we also have, a not so detailed proposal/description,
> >>>>>>>>> on how the same can be achieved via scheduling (scream).
> >>>>>>>>> It should be ok to allow for different ways to implement
> >>>>>>>>> coupling, but we should then eventually have one document
> that
> >>>>>>>>> describes both solutions. Shouldn't we ?
> >>>>>>>>
> >>>>>>>> I think so. There is already (short, because it's so simple)
> >>>>>>>> text about scheduling in coupled-cc and we can extend that and
> >>>>>>>> make it stand out more clearly (now it's in the intro I think).
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Michael
> >>>>>>>
> >>>
> >>
> >> --
> >> ------------------------------------------
> >> Dipl.-Ing. Mirja K=FChlewind
> >> Communication Systems Group
> >> Institute TIK, ETH Z=FCrich
> >> Gloriastrasse 35, 8092 Z=FCrich, Switzerland
> >>
> >> Room ETZ G93
> >> phone: +41 44 63 26932
> >> email: mirja.kuehlewind@tik.ee.ethz.ch
> >> ------------------------------------------
>
> --
> ------------------------------------------
> Dipl.-Ing. Mirja K=FChlewind
> Communication Systems Group
> Institute TIK, ETH Z=FCrich
> Gloriastrasse 35, 8092 Z=FCrich, Switzerland
>
> Room ETZ G93
> phone: +41 44 63 26932
> email: mirja.kuehlewind@tik.ee.ethz.ch
> ------------------------------------------


From nobody Fri Jul 31 02:13:17 2015
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69C621A0010 for <rmcat@ietfa.amsl.com>; Fri, 31 Jul 2015 02:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RKqIlTXLwkyH for <rmcat@ietfa.amsl.com>; Fri, 31 Jul 2015 02:13:12 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DAAE1A000B for <rmcat@ietf.org>; Fri, 31 Jul 2015 02:13:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id B62DAD930E; Fri, 31 Jul 2015 11:13:09 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1gq6-hh81Byn; Fri, 31 Jul 2015 11:13:09 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 544A6D930D; Fri, 31 Jul 2015 11:13:09 +0200 (MEST)
Message-ID: <55BB3C23.1030804@tik.ee.ethz.ch>
Date: Fri, 31 Jul 2015 11:13:07 +0200
From: =?windows-1252?Q?Mirja_K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,  Michael Welzl <michawe@ifi.uio.no>
References: <559FB533.5090105@tik.ee.ethz.ch> <55A4CD90.4020905@ericsson.com> <, > <17a463d7eb4dddb627d9d52d0e6ceb2d@mail.gmail.com> <pqd7y09y2g7ct1c7xah2lp1e.1436904929881@email.android.com> <456f0d239cbead1c87a3d639688f7495@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACF5C@ESESSMB307.ericsson.se> <07529396e89526f834a8816d1d2502c7@mail.gmail.com> <35276229-26A3-4E8F-ACFB-253A9B6FF26A@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4AA2F@ESESSMB205.ericsson.se> <248FA5A9-1B0E-4ED1-8D51-CA1487E7ABBF@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C46D@ESESSMB205.ericsson.se> <44A520B8-4DEC-4D9C-97DE-5223DD8A4CB0@ifi.uio.no> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4C4DB@ESESSMB205.ericsson.se> <55B9FD05.1050807@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4EACB@ESESSMB205.ericsson.se> <55BA16BF.6030101@tik.ee.ethz.ch>, <81564C0D7D4D2A4B9A86C8C7404A13DA34B4FCF5@ESESSMB205.ericsson.se> <8yysa9u4qxydnc7snuuon5ay.1438327885021@email.android.com>
In-Reply-To: <8yysa9u4qxydnc7snuuon5ay.1438327885021@email.android.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/kQwozEgk1FT00YSwDIr_j8atugo>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 31 Jul 2015 09:13:16 -0000

Hi Ingemar,

the name scheduler is correct for what you describe below. However in Section 
4.1.2.2 it is only described how to calculate send_wnd. There is one sentence 
saying "Packets are transmitted at a pace given by the send window, computed 
below", however, no details about pacing are given in this section. As this 
section is only about send_wnd calculation, this section should be named e.g. 
'sending rate controller".

Anything that described the scheduling of multiple streams is currently in the 
appendix; also what you describe below is, I believe, not documented at all...? 
Whenever you talk about multiplexing stream, scheduling is the right term, 
however please try to separate send rate calculation and scheduling and keep the 
scheduling part including pacing in the appendix for now (until we got one step 
further with the framework doc)!

Moreover, if there are things in the implementation that are not documented in 
the draft (and influence the performance), please update the draft!

Mirja



On 31.07.2015 09:31, Ingemar Johansson S wrote:
> Errata... Should be "not convinced about the name change", thanks for the heads up Zahed :-)
>
> ...But if it is needed in order to get a common set of terms
>
> Sent from Moxier Mail
> (http://www.moxier.com)
>
>
> ----- Ursprungligt meddelande -----
> Från: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
> Till: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <michawe@ifi.uio.no>
> Kopia: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
> Skickat: 2015-07-31 0:30
> Ämne: RE: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>
>
>
> Hi
>
> The term transmission scheduler was taken from a discussion on the TCPM WG (thread starts at http://www.ietf.org/mail-archive/web/tcpm/current/msg08768.html ), the definition was borrowed from TCP laminar. This means that I am currently convinced about the name change.
> The RTP packets from two or more streams (RTP queues) are in its simplest form picked in a round-robin fashion. This is described in section 4.1. If prioritization is desired then a credit based system is used, described in appendix A.2. In reality the credit based approach is always enabled even though no prioritization between streams is applied, in this case all streams get the same priority.
> It is imperative however that all streams are able to transmit RTP packets frequently. This to avoid extra queueing delay on the sender side. With a 2:1 prioritization allocation, one stream gets to send 2 RTP packets, then the other stream gets to send 1 RTP packet.
> It is for instance not too practical to allow one stream to send for 100ms and then let the other stream transmit for 50ms, this will only increase latency and risk making the video choppy. This is the main reason why SCReAMs transmit scheduling and prioritization operates is RTP packet transmission clocked instead of timer based.
> But...of course one can implement timer based prioritization with shorter intervals, in which case the differences would be smaller, but for SCReAM it is more practical to be RTP packet transmission based.
>
> PS, deliberately omitted the fact than one (or even all streams) may have nothing to transmit, this is handled in the code however.  For those interested, it is possible to experiment with the C++ code to see how the stream prioritization performs.
>
>
> /Ingemar
>
>
>
>> -----Original Message-----
>> From: Mirja Kühlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
>> Sent: den 30 juli 2015 14:21
>> To: Ingemar Johansson S; Michael Welzl
>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org
>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>
>> Hi Ingemar,
>>
>> okay thanks for the clarification. I discussed this with Zahed and the
>> scheduler as described in section 4.1.2.2. should probably be renamed to
>> something like sending rate controller because without the prioritization it's
>> only handling one flow at a time, right?
>>
>> Mirja
>>
>>
>> On 30.07.2015 13:22, Ingemar Johansson S wrote:
>>> Hi
>>>
>>> Probably needs some clarification. The transmission scheduler that decides
>> when to transmit RTP packets is an integral part of SCReAM and described in
>> section 4.1.2.2 in the draft.
>>> Stream prioritization is applied when two or more streams share a
>> congestion control and is described in section A.2.
>>>
>>> The former has been evaluated earlier , the latter is only exemplified
>>> in
>>> https://github.com/EricssonResearch/scream/blob/master/SCReAM-
>> descript
>>> ion.pdf
>>>
>>> The evaluation of stream prioritization leads to a set of follow-up
>> questions. What kind of source behavior do be assume, is it CBR  or VBR.
>> Stream prioritization of CBR sources is quite trivial to solve IMO, VBR is more
>> complicated.
>>>
>>> /Ingemar
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Mirja Kühlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
>>>> Sent: den 30 juli 2015 12:32
>>>> To: Ingemar Johansson S; Michael Welzl
>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org
>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>
>>>> Hi Ingemar,
>>>>
>>>> A quick comment here:
>>>>
>>>>> I think however the scheduling it will remain in the running code
>>>>> (C++ code
>>>> and OWR) at least until a good alternative is available.
>>>>
>>>> If the scheduling stays in the appendix, we definitely need to see
>>>> evaluation results for Scream without scheduling. If scheduling is an
>>>> essential part of Scream, you also need a shared bottleneck
>>>> detection! Actually I guess we need to see evaluation results for
>>>> Scream without scheduling in any case, because there might always be
>>>> the case where the sbd does not detect a shared bottleneck correctly.
>>>>
>>>> Mirja
>>>>
>>>>
>>>>
>>>>>
>>>>> /Ingemar
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>> Sent: den 24 juli 2015 10:57
>>>>>> To: Ingemar Johansson S
>>>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Mirja
>>>>>> Kühlewind
>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>
>>>>>> No.
>>>>>>
>>>>>> Our algo lets you assign priorities, and they are valid at the time
>>>>>> you set them, they just give you a portion of the overall rate and
>>>>>> it applies as soon as you set it.
>>>>>> If  you want to adjust priorities based on the coder output rate
>>>>>> variation, you can implement this using our algo or with a scheduler.
>>>>>> A scheduler operates per packet, we operate per time, so
>>>> implementation-wise it's a bit different.
>>>>>>
>>>>>> My point is only: whether you do it with our algorithm or without a
>>>>>> scheduler, I think this should not be in our draft  (and I'm neutral about:
>>>>>> should it be in the SCReAM draft or separate from it).
>>>>>>
>>>>>> Cheers,
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>>> On 24. jul. 2015, at 10.42, Ingemar Johansson S
>>>>>> <ingemar.s.johansson@ericsson.com> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Not sure I get it.
>>>>>>> Do you mean that coupling algo is immune to video coder output
>>>>>>> rate
>>>>>> variation ?
>>>>>>>
>>>>>>> /Ingemar
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>>>> Sent: den 22 juli 2015 11:16
>>>>>>>> To: Ingemar Johansson S
>>>>>>>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org;
>>>>>>>> Mirja Kühlewind
>>>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>>>
>>>>>>>> understood; i think these details are beyond the scope of our
>>>>>>>> coupling draft which focuses on a different method.
>>>>>>>>
>>>>>>>> cheers
>>>>>>>> michael
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>>> On 22. juli 2015, at 11:06, Ingemar Johansson S
>>>>>>>> <ingemar.s.johansson@ericsson.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> Still waiting for the summer to show up so I'll try to chime in
>>>>>>>>> while this
>>>>>>>> subject is at least luke-warm. I may be slow with follow up on
>>>>>>>> this, sorry for that in advance.
>>>>>>>>>
>>>>>>>>> Stream prio in SCReAM is outlined in section A.2 in the draft
>>>>>>>> (https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-01#page-28
>> ).
>>>>>>>> In its function it resembles fq-codel quite a lot in the sense
>>>>>>>> that streams that do not get scheduled at a given scheduling
>>>>>>>> instant gets a credit that is used to increase the chance of
>>>>>>>> being scheduled at the next scheduling instant. A configurable
>>>>>>>> scheduling priority determines
>>>>>> how much credit  that is given.
>>>>>>>> Looking in the
>>>>>>>> https://tools.ietf.org/pdf/draft-ietf-tsvwg-sctp-ndata-04.pdf
>>>>>>>> draft I would say that this resembles the "Weighted Fair Queueing
>>>>>>>> Scheduler"  the most. Some additional means are needed to make
>>>>>>>> this work well in reality though (see below).
>>>>>>>>>
>>>>>>>>> The benefit with doing scheduling priority and a common
>>>>>>>>> congestion
>>>>>>>> control is an increased probability that the path capacity is
>>>>>>>> fully utilized, if a stream becomes idle (for instance no or
>>>>>>>> little activity in one video source) , more resources are
>>>>>>>> allocated to the other sources. And this is achieved with no or
>>>>>>>> very little additional delay
>>>>>> buildup on the sender side.
>>>>>>>>> Another benefit with stream prioritization is that it is easier
>>>>>>>>> to make one
>>>>>>>> congestion control behave well (low delay /packet loss) esp. on a
>>>>>>>> wireless link. We have simulation results that supports this
>>>>>>>> statement albeit in the different context (QUIC congestion
>>>>>>>> control
>>>>>> evolution).
>>>>>>>>> The stream prioritization and one congestion control of course
>>>>>>>>> require that all the streams share the same bottleneck
>>>>>>>>> characteristics
>>>>>>>>>
>>>>>>>>> With that said, the biggest challenge I have seen this far is
>>>>>>>>> the large
>>>>>>>> variability of esp. video sources. Sit still in front of the
>>>>>>>> camera and the output rate becomes very low regardless the target
>>>>>>>> rate, move yourself closer to the camera and bang!!.. you get
>>>>>>>> 2Mbps video rate all of a sudden. This variability causes issues
>>>>>>>> with stream prioritization in the sense that less variable
>>>>>>>> streams may be pushed back. Additional code is therefore added in
>>>>>>>> SCReAM to correct this anomaly and ensure a (weighted) fair
>>>>>>>> distribution over a longer time scale. Still as mentioned in the
>>>>>>>> SCReAM draft, this needs to be tried out some more. I have sofar
>>>>>>>> only simulated video sources with variability
>>>>>> to see that the current implementation is reasonably robust.
>>>>>>>>> The bottom line here is that, while scheduling of streams with
>>>>>>>>> static
>>>>>>>> properties may be considered simple, real video may be a taller
>> order.
>>>>>>>>>
>>>>>>>>> /Ingemar
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Michael Welzl [mailto:michawe@ifi.uio.no]
>>>>>>>>>> Sent: den 20 juli 2015 10:03
>>>>>>>>>> To: Karen E. E. Nielsen
>>>>>>>>>> Cc: Zaheduzzaman Sarker; Ingemar Johansson S; rmcat@ietf.org;
>>>>>>>>>> Mirja Kühlewind
>>>>>>>>>> Subject: Re: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>> On 20. jul. 2015, at 07.32, Karen Elisabeth Egede Nielsen
>>>>>>>>>>> <karen.nielsen@tieto.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> HI,
>>>>>>>>>>>
>>>>>>>>>>> Yes - there is the possibility to implement coupled congestion
>>>>>>>>>>> control with scheduling priorities, There is no doubt about
>>>>>>>>>>> that :-), Indeed SCTP does it and scream does it.
>>>>>>>>>>> But it is not so well-described in the scream draft how
>>>>>>>>>>> exactly the prioritization works and which means an
>>>>>>>>>>> application has to define different priorities.
>>>>>>>>>>> (For information then for SCTP a number of different
>>>>>>>>>>> scheduling possibilities is described in
>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/.)
>>>>>>>>>>>
>>>>>>>>>>> Then for RMCAT coupled congestion control  we have the Wezlz,
>>>>>>>>>>> Safiqul proposal where the coupled is done in-between per
>>>>>>>>>>> flow-CC contexts by prioritization on manipulation of the cwnd.
>>>>>>>>>>> And the we also have, a not so detailed proposal/description,
>>>>>>>>>>> on how the same can be achieved via scheduling (scream).
>>>>>>>>>>> It should be ok to allow for different ways to implement
>>>>>>>>>>> coupling, but we should then eventually have one document
>> that
>>>>>>>>>>> describes both solutions. Shouldn't we ?
>>>>>>>>>>
>>>>>>>>>> I think so. There is already (short, because it's so simple)
>>>>>>>>>> text about scheduling in coupled-cc and we can extend that and
>>>>>>>>>> make it stand out more clearly (now it's in the intro I think).
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Michael
>>>>>>>>>
>>>>>
>>>>
>>>> --
>>>> ------------------------------------------
>>>> Dipl.-Ing. Mirja Kühlewind
>>>> Communication Systems Group
>>>> Institute TIK, ETH Zürich
>>>> Gloriastrasse 35, 8092 Zürich, Switzerland
>>>>
>>>> Room ETZ G93
>>>> phone: +41 44 63 26932
>>>> email: mirja.kuehlewind@tik.ee.ethz.ch
>>>> ------------------------------------------
>>
>> --
>> ------------------------------------------
>> Dipl.-Ing. Mirja Kühlewind
>> Communication Systems Group
>> Institute TIK, ETH Zürich
>> Gloriastrasse 35, 8092 Zürich, Switzerland
>>
>> Room ETZ G93
>> phone: +41 44 63 26932
>> email: mirja.kuehlewind@tik.ee.ethz.ch
>> ------------------------------------------

-- 
------------------------------------------
Dipl.-Ing. Mirja Kühlewind
Communication Systems Group
Institute TIK, ETH Zürich
Gloriastrasse 35, 8092 Zürich, Switzerland

Room ETZ G93
phone: +41 44 63 26932
email: mirja.kuehlewind@tik.ee.ethz.ch
------------------------------------------

