
From nobody Mon Aug  3 06:20:40 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 BA3761A6EF9 for <rmcat@ietfa.amsl.com>; Mon,  3 Aug 2015 06:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 eFmAX1YmT-HO for <rmcat@ietfa.amsl.com>; Mon,  3 Aug 2015 06:20: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 66E5A1A7005 for <rmcat@ietf.org>; Mon,  3 Aug 2015 06:20:23 -0700 (PDT)
X-AuditID: c1b4fb30-f79706d000007227-c1-55bf6a95d2b4
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id AA.7D.29223.59A6FB55; Mon,  3 Aug 2015 15:20:21 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0210.002; Mon, 3 Aug 2015 15:20:21 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Thread-Topic: SCReAM : stream prioritization 
Thread-Index: AdDN7ZoEhbPltGNFQX2/ZykOcQIZ0Q==
Date: Mon, 3 Aug 2015 13:20:20 +0000
Message-ID: <81564C0D7D4D2A4B9A86C8C7404A13DA34B52199@ESESSMB205.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_81564C0D7D4D2A4B9A86C8C7404A13DA34B52199ESESSMB205erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyM+Jvje7UrP2hBm1LpSwOtc5ksfhxdier xYbVU1gsVt/8wObA4rFkyU8mj9WrHzJ7HHoe5HHsw1e2AJYoLpuU1JzMstQifbsEroyd8x4x F9wKrjh4qYmtgfGXdxcjB4eEgInEtd9CXYycQKaYxIV769m6GLk4hASOMko8XXqGBcJZxCjx bWoHM0gVm4CNxMpD3xlBmkUEDCRu9pqC1DALfGSUaPuznQUkLiygIfHveRBIuYiArsTNfd3M ELaexJvuXjYQm0VARWLLpB+MIDavgK/Ew81vweKMArIS97/fYwGxmQXEJW49mc8EcZyAxJI9 55khbFGJl4//sULYihIfX+1jhKjPl1h7cBMLxExBiZMzn7BMYBSehWTULCRls5CUQcT1JG5M ncIGYWtLLFv4mhnC1pWY8e8QC7L4Akb2VYyixanFSbnpRkZ6qUWZycXF+Xl6eaklmxiBMXZw y2+DHYwvnzseYhTgYFTi4VU4vS9UiDWxrLgy9xCjNAeLkjjvjM15oUIC6YklqdmpqQWpRfFF pTmpxYcYmTg4pRoY9Wat1Qi6sPeOjv2FD+6MB1Qe6OWkqBmtu/l6vldV3LwJE9YG7bf4+OrM 6+XHYg8ydM/0jUia+tSph5Gz1/3wZfMLs7W/M55qfTztS88EoxsJndPMcnxNe36t5F7n9dDi lo7D1v07N6bEzPuQuqaV52G7Cq+TtUlck9X8n26Frb+4Pxxq0P/7Q4mlOCPRUIu5qDgRAPc9 KgKSAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/r87bp1WOp-WNxVvKmqcVD6esLHs>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "mirja.kuehlewind@tik.ee.ethz.ch" <mirja.kuehlewind@tik.ee.ethz.ch>, "Michael Welzl \(michawe@ifi.uio.no\)" <michawe@ifi.uio.no>
Subject: [rmcat] SCReAM : stream prioritization
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, 03 Aug 2015 13:20:37 -0000

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

Hi
Did some cleanup and modifications to the SCReAM C++ code, in the process I=
 also generated a few examples that illustrate how the transmission schedul=
ing and stream prioritization  in SCReAM behaves, see pages 15 to 17 in
https://github.com/EricssonResearch/scream/blob/master/SCReAM-description.p=
df

Page 15 shows the case with two video streams. Initially, only one stream i=
s active, at T=3D31s a second stream is added, at T =3D 91s , the additiona=
l stream becomes inactive.
Inactivity of a stream is declared when no RTP packets are detected for sai=
d stream for a duration of 1s or more.

Page 16 is the same example as above with the difference that the added str=
eam as a 2 times higher priority than the already existing stream.

Page 17 shows an example with three streams, just to verify that the mechan=
ism works or N>2. Initially stream 1 and 3 are active with priority 0.5 eac=
h. At T=3D31, stream 2 with priority 1.0 is added (becomes active), stream =
2 becomes active at T=3D91s.

/Ingemar

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
Ingemar Johansson  M.Sc.
Senior Researcher

Ericsson AB
Wireless Access Networks
Labratoriegr=E4nd 11
971 28, Lule=E5, Sweden
Phone +46-1071 43042
SMS/MMS +46-73 078 3289
ingemar.s.johansson@ericsson.com<mailto:ingemar.s.johansson@ericsson.com>
www.ericsson.com

"No man has a good enough memory
  to be a successful liar"
    Abraham Lincoln<http://www.brainyquote.com/quotes/authors/a/abraham_lin=
coln.html>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=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_81564C0D7D4D2A4B9A86C8C7404A13DA34B52199ESESSMB205erics_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered 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";
	mso-fareast-language:EN-US;}
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";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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]-->
</head>
<body lang=3D"SV" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Did some cleanup and modificati=
ons to the SCReAM C&#43;&#43; code, in the process I also generated a few e=
xamples that illustrate how the transmission scheduling and stream prioriti=
zation &nbsp;in SCReAM behaves, see pages 15 to 17
 in <o:p></o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"https://github.com/EricssonResearch/screa=
m/blob/master/SCReAM-description.pdf">https://github.com/EricssonResearch/s=
cream/blob/master/SCReAM-description.pdf</a>
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Page 15 shows the case with two=
 video streams. Initially, only one stream is active, at T=3D31s a second s=
tream is added, at T =3D 91s , the additional stream becomes inactive.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Inactivity of a stream is decla=
red when no RTP packets are detected for said stream for a duration of 1s o=
r more.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Page 16 is the same example as =
above with the difference that the added stream as a 2 times higher priorit=
y than the already existing stream.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Page 17 shows an example with t=
hree streams, just to verify that the mechanism works or N&gt;2. Initially =
stream 1 and 3 are active with priority 0.5 each. At T=3D31, stream 2 with =
priority 1.0 is added (becomes active), stream
 2 becomes active at T=3D91s.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">/Ingemar</span><span lang=3D"EN=
-US" style=3D"font-size:10.0pt"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Ingemar Johansson&nbsp; M.Sc.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Senior Researcher<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Ericsson AB<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Wireless Access Networks<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Labratoriegr=E4nd 11<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">971 28, Lule=E5, Sweden<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">Phone &#43;46-1071 43042<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV">SMS/MMS &#43;46-73 078 3289<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-fareast-=
language:SV"><a href=3D"mailto:ingemar.s.johansson@ericsson.com"><span lang=
=3D"EN-US" style=3D"color:blue">ingemar.s.johansson@ericsson.com</span></a>=
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;mso-fareast-language:SV"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-fareast-=
language:SV"><a href=3D"www.ericsson.com"><span lang=3D"EN-US" style=3D"col=
or:blue">www.ericsson.com</span></a></span><span lang=3D"EN-US" style=3D"fo=
nt-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-far=
east-language:SV"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;mso-fareast-language:SV"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black;mso-fareast-language:SV">&#8220;<span style=3D"background:wh=
ite">No man has a good enough memory
<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black;background:white;mso-fareast-language:SV">&nbsp;&nbsp;to be =
a successful liar</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-fareast-language:SV">&=
#8221;<span style=3D"color:black"><br>
</span>&nbsp;&nbsp;&nbsp; </span><span style=3D"font-size:10.0pt;font-famil=
y:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-fareast-language:SV"><a href=
=3D"http://www.brainyquote.com/quotes/authors/a/abraham_lincoln.html"><span=
 lang=3D"EN-US" style=3D"color:windowtext;background:white;text-decoration:=
none">Abraham
 Lincoln</span></a></span><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;;mso-fareast-language:SV"=
><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_81564C0D7D4D2A4B9A86C8C7404A13DA34B52199ESESSMB205erics_--


From nobody Tue Aug  4 04:04:39 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 2033A1B37A1 for <rmcat@ietfa.amsl.com>; Tue,  4 Aug 2015 04:04:38 -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 zyfYapUiZUMs for <rmcat@ietfa.amsl.com>; Tue,  4 Aug 2015 04:04:36 -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 CF1041B37A5 for <rmcat@ietf.org>; Tue,  4 Aug 2015 04:04:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 72BCED9319; Tue,  4 Aug 2015 13:04: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 eLlDwMt9sS-v; Tue,  4 Aug 2015 13:04:34 +0200 (MEST)
Received: from [192.168.178.33] (x4d02ee29.dyn.telefonica.de [77.2.238.41]) (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 06156D9303; Tue,  4 Aug 2015 13:04:33 +0200 (MEST)
From: =?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
Date: Tue, 4 Aug 2015 13:04:32 +0200
Message-Id: <7563D95C-8E49-4F4E-AE5C-FB9940513A91@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/FpRYLtTMIxR3M7mt6k1q7hPVpqI>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Subject: [rmcat] Minutes and reminder!
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, 04 Aug 2015 11:04:38 -0000

Hi all,

I=E2=80=99ve uploaded the minutes:

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

Great thanks to Gorry! As we had a quite packed meeting, I guess he was =
pretty busy=E2=80=A6 Thanks!

Sorry that it took me so long, but I went back and double-checked some =
parts in the audio to makes things as clear as possible!

Let me know if there are still any uncertainties or any modification =
needed. Especially if you have said something on the mic, please =
double-check that your point was captured correctly!

Further please remember that we have currently three adoption calls =
running (until next Mon):
https://datatracker.ietf.org/doc/draft-alvestrand-rmcat-congestion/
https://datatracker.ietf.org/doc/draft-welzl-rmcat-coupled-cc/
=
https://datatracker.ietf.org/doc/draft-zanaty-rmcat-cc-codec-interactions/=


I did not receive any feedback so far but I assume that most people were =
at the meeting and already participated in the hums. So that seems fine.

Further please also remember to read and potentially review =
draft-zhu-rmcat-video-traffic-source:
https://datatracker.ietf.org/doc/draft-zhu-rmcat-video-traffic-source/

If you have read the draft, please indicate this on the mailing or even =
send a full review if you have time. If we see enough interest in this =
draft, we would like to run an adoption call between now and the next =
meeting for this draft.

Enjoy the summer!
Mirja



From nobody Thu Aug  6 02:45:29 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 159BF1B2B75 for <rmcat@ietfa.amsl.com>; Thu,  6 Aug 2015 02:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level: 
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 cKS0224YV4F8 for <rmcat@ietfa.amsl.com>; Thu,  6 Aug 2015 02:45:25 -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 D12241B2B84 for <rmcat@ietf.org>; Thu,  6 Aug 2015 02:45:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 98801D930B; Thu,  6 Aug 2015 11:45:23 +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 APPM7P-ZQaUv; Thu,  6 Aug 2015 11:45:23 +0200 (MEST)
Received: from [192.168.178.33] (x5f71b0a0.dyn.telefonica.de [95.113.176.160]) (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 A8E3ED930A; Thu,  6 Aug 2015 11:45:22 +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>
Date: Thu, 6 Aug 2015 11:45:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B16406D-A1B8-4FEA-B9B0-C2B664F015FA@tik.ee.ethz.ch>
References: <A81C28A3-2D71-4A81-9E84-538B34660FCA@jacobs-university.de>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/LHmxOYTX0PQKBIXA3o275mo_WiE>
Cc: v.bajpai@jacobs-university.de
Subject: [rmcat] Fwd: [hops] measurement platforms and their capabilities (previously was HOPS bar bof notes)
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, 06 Aug 2015 09:45:27 -0000

Hi all,

there was a request for an overview/survey paper on measurement =
platforms in the meeting. I just realized that this pointer was already =
posted on the hops list a while ago (see below).

We, as chairs, will start a Wiki (soon) to collect information about =
measurement platforms as well as measurement tools (and take this as a =
starting point).=20

Let us as well as the group know if you have further knowledge about =
this kind of overview papers or similar things by posting a pointer on =
the list!

Mirja


> Anfang der weitergeleiteten Nachricht:
>=20
> Von: "Bajpai, Vaibhav" <v.bajpai@jacobs-university.de>
> Betreff: [hops] measurement platforms and their capabilities =
(previously was HOPS bar bof notes)
> Datum: 7. April 2015 09:30:59 MESZ
> An: "hops@ietf.org" <hops@ietf.org>
> Kopie: "Bajpai, Vaibhav" <v.bajpai@jacobs-university.de>, Aaron Falk =
<aaron.falk@gmail.com>
>=20
> Dear hops,
>=20
>> On 23 Mar 2015, at 18:51, Aaron Falk <aaron.falk@gmail.com> wrote:
>=20
> [...]
>=20
>> Test infrastructure
>> 	=E2=80=A2 AI: group to share on the list what measurement =
(platforms) exists and what capabilities they have
>=20
> Early discussions within LMAP [1] also often lead to folks asking for =
feature
> sets and possibilities of each contemporary performance measurement =
platform.
> So we started digging literature work in this space and found that =
although
> there were surveys on topology-based measurement platforms (such CAIDA =
Ark
> and DIMES); literature work on performance measurement platforms (such =
RIPE
> Atlas, SamKnows and BISmark) was missing.
>=20
> Therefore, we started writing such a survey in 2013 to plug this gap. =
This
> work got published this week. Thought would share this with you.
>=20
> Hope it helps.
>=20
> =
----------------8<-----------------8<-----------------8<-----------------8=
<
> A Survey on Internet Performance Measurement Platforms and Related =
Standardization Efforts
> Vaibhav Bajpai, J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
> IEEE Communications Surveys & Tutorials
> April, 2015
>=20
> A number of Internet measurement platforms have emerged in the last =
few years.
> These platforms have deployed thousands of probes at strategic =
locations
> within access and backbone networks and behind residential gateways. =
In this
> paper we provide a taxonomy of these measurement platforms on the =
basis of
> their deployment use-case. We describe these platforms in detail by =
exploring
> their coverage, scale, lifetime, deployed metrics and measurement =
tools,
> architecture and overall research impact. We conclude the survey by =
describing
> current standardization efforts to make large-scale performance =
measurement
> platforms interoperable.
>=20
> DOI: http://dx.doi.org/10.1109/COMST.2015.2418435
> Author Copy: =
http://vaibhavbajpai.com/documents/papers/proceedings/lsmp-comst-2015.pdf
> =
----------------8<-----------------8<-----------------8<-----------------8=
<
>=20
> Thanks!
>=20
> [1] https://datatracker.ietf.org/wg/lmap
>=20
> Best, Vaibhav
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> Vaibhav Bajpai
>=20
> Research I, Room 91
> Computer Networks and Distributed Systems (CNDS) Lab
> School of Engineering and Sciences
> Jacobs University Bremen, Germany
>=20
> www.vaibhavbajpai.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
> _______________________________________________
> hops mailing list
> hops@ietf.org
> https://www.ietf.org/mailman/listinfo/hops


From nobody Thu Aug  6 02:47:33 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 5E51F1B2B84 for <rmcat@ietfa.amsl.com>; Thu,  6 Aug 2015 02:47:32 -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 6x7AHBGfLwrN for <rmcat@ietfa.amsl.com>; Thu,  6 Aug 2015 02:47:30 -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 68F581B2B77 for <rmcat@ietf.org>; Thu,  6 Aug 2015 02:47:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id B261CD930C; Thu,  6 Aug 2015 11:47:28 +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 afXd1E9+THFI; Thu,  6 Aug 2015 11:47:28 +0200 (MEST)
Received: from [192.168.178.33] (x5f71b0a0.dyn.telefonica.de [95.113.176.160]) (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 13670D930A; Thu,  6 Aug 2015 11:47:28 +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: <3B16406D-A1B8-4FEA-B9B0-C2B664F015FA@tik.ee.ethz.ch>
Date: Thu, 6 Aug 2015 11:47:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <881BF181-C25C-4A25-B04D-FD295EE0ABEA@tik.ee.ethz.ch>
References: <A81C28A3-2D71-4A81-9E84-538B34660FCA@jacobs-university.de> <3B16406D-A1B8-4FEA-B9B0-C2B664F015FA@tik.ee.ethz.ch>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/XsjUvC0Vq64KWtZBkDTWS0wUqGs>
Cc: v.bajpai@jacobs-university.de
Subject: Re: [rmcat] [hops] measurement platforms and their capabilities (previously was HOPS bar bof notes)
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, 06 Aug 2015 09:47:32 -0000

Sorry wrong list=E2=80=A6 please ignore=E2=80=A6 expect you are =
interested in hops=E2=80=A6


> Am 06.08.2015 um 11:45 schrieb Mirja K=C3=BChlewind =
<mirja.kuehlewind@tik.ee.ethz.ch>:
>=20
> Hi all,
>=20
> there was a request for an overview/survey paper on measurement =
platforms in the meeting. I just realized that this pointer was already =
posted on the hops list a while ago (see below).
>=20
> We, as chairs, will start a Wiki (soon) to collect information about =
measurement platforms as well as measurement tools (and take this as a =
starting point).=20
>=20
> Let us as well as the group know if you have further knowledge about =
this kind of overview papers or similar things by posting a pointer on =
the list!
>=20
> Mirja
>=20
>=20
>> Anfang der weitergeleiteten Nachricht:
>>=20
>> Von: "Bajpai, Vaibhav" <v.bajpai@jacobs-university.de>
>> Betreff: [hops] measurement platforms and their capabilities =
(previously was HOPS bar bof notes)
>> Datum: 7. April 2015 09:30:59 MESZ
>> An: "hops@ietf.org" <hops@ietf.org>
>> Kopie: "Bajpai, Vaibhav" <v.bajpai@jacobs-university.de>, Aaron Falk =
<aaron.falk@gmail.com>
>>=20
>> Dear hops,
>>=20
>>> On 23 Mar 2015, at 18:51, Aaron Falk <aaron.falk@gmail.com> wrote:
>>=20
>> [...]
>>=20
>>> Test infrastructure
>>> 	=E2=80=A2 AI: group to share on the list what measurement =
(platforms) exists and what capabilities they have
>>=20
>> Early discussions within LMAP [1] also often lead to folks asking for =
feature
>> sets and possibilities of each contemporary performance measurement =
platform.
>> So we started digging literature work in this space and found that =
although
>> there were surveys on topology-based measurement platforms (such =
CAIDA Ark
>> and DIMES); literature work on performance measurement platforms =
(such RIPE
>> Atlas, SamKnows and BISmark) was missing.
>>=20
>> Therefore, we started writing such a survey in 2013 to plug this gap. =
This
>> work got published this week. Thought would share this with you.
>>=20
>> Hope it helps.
>>=20
>> =
----------------8<-----------------8<-----------------8<-----------------8=
<
>> A Survey on Internet Performance Measurement Platforms and Related =
Standardization Efforts
>> Vaibhav Bajpai, J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
>> IEEE Communications Surveys & Tutorials
>> April, 2015
>>=20
>> A number of Internet measurement platforms have emerged in the last =
few years.
>> These platforms have deployed thousands of probes at strategic =
locations
>> within access and backbone networks and behind residential gateways. =
In this
>> paper we provide a taxonomy of these measurement platforms on the =
basis of
>> their deployment use-case. We describe these platforms in detail by =
exploring
>> their coverage, scale, lifetime, deployed metrics and measurement =
tools,
>> architecture and overall research impact. We conclude the survey by =
describing
>> current standardization efforts to make large-scale performance =
measurement
>> platforms interoperable.
>>=20
>> DOI: http://dx.doi.org/10.1109/COMST.2015.2418435
>> Author Copy: =
http://vaibhavbajpai.com/documents/papers/proceedings/lsmp-comst-2015.pdf
>> =
----------------8<-----------------8<-----------------8<-----------------8=
<
>>=20
>> Thanks!
>>=20
>> [1] https://datatracker.ietf.org/wg/lmap
>>=20
>> Best, Vaibhav
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>> Vaibhav Bajpai
>>=20
>> Research I, Room 91
>> Computer Networks and Distributed Systems (CNDS) Lab
>> School of Engineering and Sciences
>> Jacobs University Bremen, Germany
>>=20
>> www.vaibhavbajpai.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
>> _______________________________________________
>> hops mailing list
>> hops@ietf.org
>> https://www.ietf.org/mailman/listinfo/hops


From nobody Sun Aug  9 15:02:47 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 CB79E1A6FEF for <rmcat@ietfa.amsl.com>; Sun,  9 Aug 2015 15:02:45 -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 j7Q5ggnm9FCs for <rmcat@ietfa.amsl.com>; Sun,  9 Aug 2015 15:02:43 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id A51E61A001C for <rmcat@ietf.org>; Sun,  9 Aug 2015 15:02:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id F10337C53DE for <rmcat@ietf.org>; Mon, 10 Aug 2015 00:02:41 +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 7XWmddM2kTnE for <rmcat@ietf.org>; Mon, 10 Aug 2015 00:02:40 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:b1be:b4a3:ec58:4864] (unknown [IPv6:2001:470:de0a:27:b1be:b4a3:ec58:4864]) by mork.alvestrand.no (Postfix) with ESMTPSA id 534CB7C53DD for <rmcat@ietf.org>; Mon, 10 Aug 2015 00:02:40 +0200 (CEST)
Message-ID: <55C7CDFF.5000408@alvestrand.no>
Date: Mon, 10 Aug 2015 00:02:39 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: rmcat@ietf.org
References: <E0F7A68B07B53F4FBD12DABD61CBA90E129ABEC5@ESESSMB307.ericsson.se> <CAEbPqrz7xoAnFqRacD2F+Fiwq9=O6jFt-2ktLdyrdng2Hq4c5Q@mail.gmail.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129ACFEF@ESESSMB307.ericsson.se> <D1D1F2FE.2405F%xiaoqzhu@cisco.com>
In-Reply-To: <D1D1F2FE.2405F%xiaoqzhu@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/8bjkcAuCT06qc8bUBPgN1lM9YqU>
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, 09 Aug 2015 22:02:46 -0000

Reminder:

Google has previously released some videos with conference-style material.
A script to fetch them is here:

https://github.com/google/compare-codecs/blob/master/video/fetch_webm_videos.sh

Harald




From nobody Tue Aug 11 06:20:54 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 2D6651A8A4F for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:20:53 -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 ENePJGLSYRzt for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:20:49 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 767DF1A8A59 for <rmcat@ietf.org>; Tue, 11 Aug 2015 06:20:44 -0700 (PDT)
Received: by igui7 with SMTP id i7so39819231igu.1 for <rmcat@ietf.org>; Tue, 11 Aug 2015 06:20:44 -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=b8Kng6QE5PE5saMmDcX8jZxpXsH/DmN2xIvlExpVJn8=; b=rnlrh4C62qAkf1S1Pguus1i2Mk3PPRRqR7uC5N8hruCjJBa9GqfqNWDIb53Y+lVqAn c5kJb6+W/ltX3xeMjByZnlUHg26bUz/I6+1CuNn0fknsjvIkEG7C376RB3QYJvRqauJc hK9pwZb1nPmgO/Sr4D44tIBTkR3mxkJiPpnfM=
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=b8Kng6QE5PE5saMmDcX8jZxpXsH/DmN2xIvlExpVJn8=; b=IbCSlNhX/FsaRjV6LvGFRetFiTQTMef4GGazq9WZnaHlO6te2mk6mpSITB60b1TnOd Whh0XBE4L0gWsjdaH5ODqS8QxhP+NlLH6jRZXnIrVh8bzEICLJf+fBSKbDztzBsywv4E zIOfTPsq1QAPwVAndGeSCtTEjB5xVHD4iGf0S6g3UFQ4LRPTlmBuZCVyifbVcn81/q4K qhNrSKLlWZTGWQfws1m8NnXYeey0hjIQKxIEHFMvKzjyEEQAyYmt63HZoTHT6VjywbMs iZqiyVkVOzx4bRUrjoTDmVi4rCxgau8LEiAJEwBSrbKCldJQrSh9p+/AGZpbi5YCCMS0 3A1g==
X-Gm-Message-State: ALoCoQmBClWgPEG6og6n4a4Zmno4SbEwBSNdJl/LWxrLJj4smIqz7QavFtb/Zp8vT626jHYgwBXEKbPj8cS2+I1H1xE7Xi0uQ6Ua1IB18rLNXyHCcBjIjbI=
X-Received: by 10.50.109.161 with SMTP id ht1mr16136049igb.97.1439299243848; Tue, 11 Aug 2015 06:20:43 -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> <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@e mail.android.com>
In-Reply-To: <8yysa9u4qxydnc7snuuon5ay.1438327885021@email.android.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGmc/6jnjaBhqE3gdH9BjSKecACAIU9jZWAhk0bc8BylhVUQEevPZoAogr6NcA3OMIZQIPrnL7AiqWYA8CIRa8iQJE5pArAjyZaGwCqMlUiAH/sZzjAlQqLeECAWS/8wE3vtd1AlO0nC8CEV8ylQK9v1KRm+WsAgA=
Date: Tue, 11 Aug 2015 15:20:42 +0200
Message-ID: <7300fc62367c0e30573d34a3bb5aa3d8@mail.gmail.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>,  =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Michael Welzl <michawe@ifi.uio.no>
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/8nfb80aRZm3hcoZZk0Yl5TRLw-s>
Cc: 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: Tue, 11 Aug 2015 13:20:53 -0000

Hi,

In SCTP one uses the term scheduler and scheduling for the entity that
selects chunks from the various streams and
bundle them into packets that consumes the common CWND (and the RWND but
that is a different discussion).

This effectively is a realization of coupled congestion control in-between
the multiple streams of the one and the same SCTP association
even if this is not called coupled congestion control.

The point indeed is that scheduling among multiple streams sharing the
same congestion context/CWND calculation is one way of effectively
realizing coupled congestion control .
Here no shared bottleneck detection is needed as it is there by default -
indeed the streams are using same UDP socket (here I assume same DSCP
markings as well).

When the shared bottleneck is not evident and/or when multiple congestion
contexts are maintained, e.g, one CWND for each stream or one CWND for
each bundle of streams (where
internally coupling within the bundle is achieved via scheduling
principles) then SBD and coupled CC as defined in draft-hayes-rmcat-sbd-02
and draft-welzl-rmcat-coupled-cc-05 is a necessary supplement.

BR, Karen (as an individual).


>-----Original Message-----
>From: Ingemar Johansson S [mailto:ingemar.s.johansson@ericsson.com]
>Sent: Friday, July 31, 2015 9:31 AM
>To: Mirja K=C3=BChlewind; Michael Welzl
>Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Ingemar
>Johansson S
>Subject: SV: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>
>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=C3=A5n: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
>Till: Mirja K=C3=BChlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welz=
l
><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
>=C3=84mne: 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=C3=BChlewind [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=C3=BChlewind [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=C3=BChlewind
>> >>>> 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=C3=BChlewind
>> >>>>>> 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=C3=BChlewind
>> >>>>>>>> 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=C3=BChlewind
>> >> Communication Systems Group
>> >> Institute TIK, ETH Z=C3=BCrich
>> >> Gloriastrasse 35, 8092 Z=C3=BCrich, Switzerland
>> >>
>> >> Room ETZ G93
>> >> phone: +41 44 63 26932
>> >> email: mirja.kuehlewind@tik.ee.ethz.ch
>> >> ------------------------------------------
>>
>> --
>> ------------------------------------------
>> Dipl.-Ing. Mirja K=C3=BChlewind
>> Communication Systems Group
>> Institute TIK, ETH Z=C3=BCrich
>> Gloriastrasse 35, 8092 Z=C3=BCrich, Switzerland
>>
>> Room ETZ G93
>> phone: +41 44 63 26932
>> email: mirja.kuehlewind@tik.ee.ethz.ch
>> ------------------------------------------


From nobody Tue Aug 11 06:43: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 24C3C1A6F87 for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:43:53 -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 cHm8G4IgsVC0 for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:43:49 -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 AC9911A8A7A for <rmcat@ietf.org>; Tue, 11 Aug 2015 06:43:48 -0700 (PDT)
X-AuditID: c1b4fb25-f79a26d00000149a-a9-55c9fc1251ae
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 1F.C0.05274.21CF9C55; Tue, 11 Aug 2015 15:43:46 +0200 (CEST)
Received: from ESESSMB205.ericsson.se ([169.254.5.70]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0210.002; Tue, 11 Aug 2015 15:43:46 +0200
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>
Thread-Topic: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
Thread-Index: AQHQuwjSUvgGEfog+E+ekiHUB7EKeJ3ajoow///+aACAADbkAIAAqcECgAbNowCAAPk8AIAAjsAAgAAqLYCAA1ciwP//4geAgAM8FiD//+NBAAAEo4fAASxm34AABZKoIP//8hWA//8+0tCAAiQLFYARibUAgAAn+Ek=
Date: Tue, 11 Aug 2015 13:43:45 +0000
Message-ID: <c22e4qcyg8thd3o5s48uc5lo.1439300622606@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> <8yysa9u4qxydnc7snuuon5ay.1438327885021@e mail.android.com>,<7300fc62367c0e30573d34a3bb5aa3d8@mail.gmail.com>
In-Reply-To: <7300fc62367c0e30573d34a3bb5aa3d8@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+NgFvrOLMWRmVeSWpSXmKPExsUyM+Jvja7Qn5OhBhdemFocap3JYvHj7E5W iw2rp7BYrL75gc2BxWPJkp9MHqtXP2T2OPQ8yOPYh69sASxRXDYpqTmZZalF+nYJXBkrDy1g L3hdUTHj7E/mBsY/SV2MnBwSAiYSMy/1skLYYhIX7q1nA7GFBI4ySrSftuti5AKyFzNKzLt5 hBkkwSZgI7Hy0HdGEFtEwFhiXcNnVpAiZoHTjBLXX91nB0kIAxWt+nQXqshW4uSf5UwgRSIC mxglOtuvgiVYBFQltt1+ADaVV8BNYuKJTlaIdXc4JJa9vw5WxClgJzFr8zQmEJtRQFbi/vd7 LCA2s4C4xOe5D5gg7haQWLLnPDOELSrx8vE/VogaPYkbU6ewQdjaEssWvoZaJihxcuYTlgmM orOQjJqFpGUWkpZZSFoWMLKsYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAiMqYNbfqvuYLz8 xvEQowAHoxIPr0L4yVAh1sSy4srcQ4zSHCxK4rwzNueFCgmkJ5akZqemFqQWxReV5qQWH2Jk 4uCUamAUu1KyUFWz5GvE4oVcnz/PDJKoVHVI0H+akGBTxOnjUN1gvznjwZnt8udyVjye88Vc z0mL73HMwRqToi4G40PpGWsDWTrOnkqbYVyqd/RHRfbplrLqd3rLy7YtWBX6celW/aNMGdO4 b2maPEr7urzKaelxli59/R/cq1frKmVtlogN2Oe6VlWJpTgj0VCLuag4EQAN5r22igIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/bOt9Bv5fDz5eVWcSmsNhAgmZeQg>
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>, Michael Welzl <michawe@ifi.uio.no>
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, 11 Aug 2015 13:43:53 -0000

+1
Ingemar

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


----- Ursprungligt meddelande -----
Fr=E5n: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Till: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, Mirja K=FChle=
wind <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl <michawe@ifi.uio.no>
Kopia: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "rmcat@ietf.=
org" <rmcat@ietf.org>
Skickat: 2015-08-11 15:20
=C4mne: RE: [rmcat] Review of draft-ietf-rmcat-scream-cc-01



Hi,

In SCTP one uses the term scheduler and scheduling for the entity that
selects chunks from the various streams and
bundle them into packets that consumes the common CWND (and the RWND but
that is a different discussion).

This effectively is a realization of coupled congestion control in-between
the multiple streams of the one and the same SCTP association
even if this is not called coupled congestion control.

The point indeed is that scheduling among multiple streams sharing the
same congestion context/CWND calculation is one way of effectively
realizing coupled congestion control .
Here no shared bottleneck detection is needed as it is there by default -
indeed the streams are using same UDP socket (here I assume same DSCP
markings as well).

When the shared bottleneck is not evident and/or when multiple congestion
contexts are maintained, e.g, one CWND for each stream or one CWND for
each bundle of streams (where
internally coupling within the bundle is achieved via scheduling
principles) then SBD and coupled CC as defined in draft-hayes-rmcat-sbd-02
and draft-welzl-rmcat-coupled-cc-05 is a necessary supplement.

BR, Karen (as an individual).


>-----Original Message-----
>From: Ingemar Johansson S [mailto:ingemar.s.johansson@ericsson.com]
>Sent: Friday, July 31, 2015 9:31 AM
>To: Mirja K=FChlewind; Michael Welzl
>Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Ingemar
>Johansson S
>Subject: SV: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>
>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=E5n: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
>Till: Mirja K=FChlewind <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
>=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/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=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
>> > 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=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 Tue Aug 11 06:50:18 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 6D0761A8ABB for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:50:17 -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 g64ziLIQyYBC for <rmcat@ietfa.amsl.com>; Tue, 11 Aug 2015 06:50:13 -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 B8E001A8A9D for <rmcat@ietf.org>; Tue, 11 Aug 2015 06:50:12 -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 1ZP9wO-00089v-Oj; Tue, 11 Aug 2015 15:50:08 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) 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 1ZP9wN-0000Y4-Aj; Tue, 11 Aug 2015 15:50:08 +0200
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <c22e4qcyg8thd3o5s48uc5lo.1439300622606@email.android.com>
Date: Tue, 11 Aug 2015 15:50:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <27D1A679-AD2A-4A5C-930C-8197F0F1A952@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> <55BA16BF.6030101@tik.ee.ethz.ch> <81564C0D7D4D2A4B9A86C8C7404A13DA34B4FCF5@ESESSMB205.ericsson.se> <8yysa9u4qxydnc7snuuon5ay.1 438327885021@e mail.android.com> <7300fc62367c0e30573d34a3bb5aa3d8@mail.gmail.com> <c22e4qcyg8thd3o5s48uc5lo.1439300622606@email.android.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.2102)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 16 msgs/h 7 sum rcpts/h 24 sum msgs/h 10 total rcpts 31991 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.05, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO,  uiouri=NO)
X-UiO-Scanned: 12EC313BF1305AB2DD1A29F9C9DAA217D63B79BE
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -59 maxlevel 80 minaction 2 bait 0 mail/h: 7 total 7573 max/h 17 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/On8pcwO_DJSk2QSRw8OAQLeWyBg>
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.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: Tue, 11 Aug 2015 13:50:17 -0000

+1

Michael


> On 11 Aug 2015, at 15:43, Ingemar Johansson S =
<ingemar.s.johansson@ericsson.com> wrote:
>=20
> +1
> Ingemar
>=20
> Sent from Moxier Mail
> (http://www.moxier.com)
>=20
>=20
> ----- Ursprungligt meddelande -----
> Fr=E5n: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
> Till: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, Mirja =
K=FChlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Michael Welzl =
<michawe@ifi.uio.no>
> Kopia: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, =
"rmcat@ietf.org" <rmcat@ietf.org>
> Skickat: 2015-08-11 15:20
> =C4mne: RE: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>=20
>=20
>=20
> Hi,
>=20
> In SCTP one uses the term scheduler and scheduling for the entity that
> selects chunks from the various streams and
> bundle them into packets that consumes the common CWND (and the RWND =
but
> that is a different discussion).
>=20
> This effectively is a realization of coupled congestion control =
in-between
> the multiple streams of the one and the same SCTP association
> even if this is not called coupled congestion control.
>=20
> The point indeed is that scheduling among multiple streams sharing the
> same congestion context/CWND calculation is one way of effectively
> realizing coupled congestion control .
> Here no shared bottleneck detection is needed as it is there by =
default -
> indeed the streams are using same UDP socket (here I assume same DSCP
> markings as well).
>=20
> When the shared bottleneck is not evident and/or when multiple =
congestion
> contexts are maintained, e.g, one CWND for each stream or one CWND for
> each bundle of streams (where
> internally coupling within the bundle is achieved via scheduling
> principles) then SBD and coupled CC as defined in =
draft-hayes-rmcat-sbd-02
> and draft-welzl-rmcat-coupled-cc-05 is a necessary supplement.
>=20
> BR, Karen (as an individual).
>=20
>=20
>> -----Original Message-----
>> From: Ingemar Johansson S [mailto:ingemar.s.johansson@ericsson.com]
>> Sent: Friday, July 31, 2015 9:31 AM
>> To: Mirja K=FChlewind; Michael Welzl
>> Cc: Karen E. E. Nielsen; Zaheduzzaman Sarker; rmcat@ietf.org; Ingemar
>> Johansson S
>> Subject: SV: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>=20
>> Errata... Should be "not convinced about the name change", thanks for =
the
>> heads up Zahed :-)
>>=20
>> ...But if it is needed in order to get a common set of terms
>>=20
>> Sent from Moxier Mail
>> (http://www.moxier.com)
>>=20
>>=20
>> ----- Ursprungligt meddelande -----
>> Fr=E5n: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
>> Till: Mirja K=FChlewind <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
>> =C4mne: RE: [rmcat] Review of draft-ietf-rmcat-scream-cc-01
>>=20
>>=20
>>=20
>> Hi
>>=20
>> 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.
>>=20
>> 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.
>>=20
>>=20
>> /Ingemar
>>=20
>>=20
>>=20
>>> -----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
>>>=20
>>> Hi Ingemar,
>>>=20
>>> 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?
>>>=20
>>> Mirja
>>>=20
>>>=20
>>> On 30.07.2015 13:22, Ingemar Johansson S wrote:
>>>> Hi
>>>>=20
>>>> 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.
>>>>=20
>>>> The former has been evaluated earlier , the latter is only
>>>> exemplified in
>>>> https://github.com/EricssonResearch/scream/blob/master/SCReAM-
>>> descript
>>>> ion.pdf
>>>>=20
>>>> 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.
>>>>=20
>>>> /Ingemar
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>> -----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
>>>>>=20
>>>>> Hi Ingemar,
>>>>>=20
>>>>> A quick comment here:
>>>>>=20
>>>>>> I think however the scheduling it will remain in the running code
>>>>>> (C++ code
>>>>> and OWR) at least until a good alternative is available.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> Mirja
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> /Ingemar
>>>>>>=20
>>>>>>=20
>>>>>>> -----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
>>>>>>>=20
>>>>>>> No.
>>>>>>>=20
>>>>>>> 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.
>>>>>>>=20
>>>>>>> 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).
>>>>>>>=20
>>>>>>> Cheers,
>>>>>>> Michael
>>>>>>>=20
>>>>>>>=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.
>>>>>>>> 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=FChlewind
>>>>>>>>> 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=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:
>>>>>>>>>>>>=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
>>>>>>=20
>>>>>=20
>>>>> --
>>>>> ------------------------------------------
>>>>> Dipl.-Ing. Mirja K=FChlewind
>>>>> Communication Systems Group
>>>>> Institute TIK, ETH Z=FCrich
>>>>> Gloriastrasse 35, 8092 Z=FCrich, Switzerland
>>>>>=20
>>>>> Room ETZ G93
>>>>> phone: +41 44 63 26932
>>>>> email: mirja.kuehlewind@tik.ee.ethz.ch
>>>>> ------------------------------------------
>>>=20
>>> --
>>> ------------------------------------------
>>> Dipl.-Ing. Mirja K=FChlewind
>>> Communication Systems Group
>>> Institute TIK, ETH Z=FCrich
>>> Gloriastrasse 35, 8092 Z=FCrich, Switzerland
>>>=20
>>> Room ETZ G93
>>> phone: +41 44 63 26932
>>> email: mirja.kuehlewind@tik.ee.ethz.ch
>>> ------------------------------------------


From nobody Thu Aug 13 00:42:01 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 1521D1B2B8F for <rmcat@ietfa.amsl.com>; Thu, 13 Aug 2015 00:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.321
X-Spam-Level: 
X-Spam-Status: No, score=0.321 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, 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 HN-9p159SUw3 for <rmcat@ietfa.amsl.com>; Thu, 13 Aug 2015 00:41:58 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C1741B2B8D for <rmcat@ietf.org>; Thu, 13 Aug 2015 00:41:57 -0700 (PDT)
Received: by igbjg10 with SMTP id jg10so58395581igb.0 for <rmcat@ietf.org>; Thu, 13 Aug 2015 00:41:56 -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:content-type:content-transfer-encoding; bh=NqmYLeDUJ1+pnLzY/ZVCMEv6JAi3mI2swfd4fJitxUc=; b=UUqUk25YTOLfmGTEQ1xqEDLjG62G3jkXtQMXs9WqPYHMTImXkKSMZmiUvS+qmYDOcB TuNmy8jw9IClZKBtxYcRz2/sB3qdCFkS1AQBRUgEavVUNGZMV0lIRvKyqEfy1Eo1ivq/ +yTWjAHgo0s2moYrbVpAc++SgnjjLIGtDmskQ=
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:content-type :content-transfer-encoding; bh=NqmYLeDUJ1+pnLzY/ZVCMEv6JAi3mI2swfd4fJitxUc=; b=RFeHXyiBcfc9MY9x1Fp8QylXofjbihHzVyC58p+azN+QaBnp+NQh4ndYuv1woCiKEP kDknUMbq5Xi5IyJnuSgw5Fnxzkww+IQWS+asjvPsk0Q50Pxf4DXNhKBKyeX2owyjU30j MXZz4XKKM6Ks8JZF8Dw0u2/caaas+S5VFnfgeB4rEfaOaI0He8O2/1wNvrfPuXzQRf0t qiVasIQ+bOnlek8qDNjvuYbIc1jmqStM+ujJA8Shx6vO//+reOqnzenqHUmORa7CpOVA gF1X6J7qNeL22HPAlMcvFAk8SfMjZQQp/c0S/VwEB+kJDx2J/P/TNe3VbrRBYBxb0Z1c 2tHw==
X-Gm-Message-State: ALoCoQm1uLGhcrraUbLPTMqVOJYHwqt3ABWLt/6ODhCzPx/KiaTvSo2Z07dVlKEPJj/V1MB6z5i4ttXyCLupHz2fZAUoFXYbkqf1D6pew1AWxniLfBOurbg=
X-Received: by 10.50.36.1 with SMTP id m1mr1754842igj.4.1439451716700; Thu, 13 Aug 2015 00:41:56 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <7563D95C-8E49-4F4E-AE5C-FB9940513A91@tik.ee.ethz.ch>
In-Reply-To: <7563D95C-8E49-4F4E-AE5C-FB9940513A91@tik.ee.ethz.ch>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHj+AVETPIq8YoeeiwoWsjhDfYQO53jRu4Q
Date: Thu, 13 Aug 2015 09:41:55 +0200
Message-ID: <78af1c493c70c7b051a2a052136c8cd5@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  rmcat WG <rmcat@ietf.org>
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/3RMrY7NVPtc0e_2VlwHxCxRt868>
Subject: Re: [rmcat] Minutes and reminder!
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, 13 Aug 2015 07:42:00 -0000

HI Mirja,

Thanks a lot for all the great work.

BR, Karen

>-----Original Message-----
>From: Mirja K=C3=BChlewind [mailto:mirja.kuehlewind@tik.ee.ethz.ch]
>Sent: Tuesday, August 04, 2015 1:05 PM
>To: rmcat WG (rmcat@ietf.org)
>Cc: Karen Elisabeth Egede Nielsen
>Subject: Minutes and reminder!
>
>Hi all,
>
>I=E2=80=99ve uploaded the minutes:
>
>https://www.ietf.org/proceedings/93/minutes/minutes-93-rmcat
>
>Great thanks to Gorry! As we had a quite packed meeting, I guess he was
>pretty busy=E2=80=A6 Thanks!
>
>Sorry that it took me so long, but I went back and double-checked some
>parts
>in the audio to makes things as clear as possible!
>
>Let me know if there are still any uncertainties or any modification
>needed.
>Especially if you have said something on the mic, please double-check that
>your point was captured correctly!
>
>Further please remember that we have currently three adoption calls runnin=
g
>(until next Mon):
>https://datatracker.ietf.org/doc/draft-alvestrand-rmcat-congestion/
>https://datatracker.ietf.org/doc/draft-welzl-rmcat-coupled-cc/
>https://datatracker.ietf.org/doc/draft-zanaty-rmcat-cc-codec-interactions/
>
>I did not receive any feedback so far but I assume that most people were a=
t
>the meeting and already participated in the hums. So that seems fine.
>
>Further please also remember to read and potentially review
>draft-zhu-rmcat-
>video-traffic-source:
>https://datatracker.ietf.org/doc/draft-zhu-rmcat-video-traffic-source/
>
>If you have read the draft, please indicate this on the mailing or even
>send a
>full review if you have time. If we see enough interest in this draft, we
>would
>like to run an adoption call between now and the next meeting for this
>draft.
>
>Enjoy the summer!
>Mirja
>


From nobody Thu Aug 13 05:30:05 2015
Return-Path: <semena@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 47BE91A1B00; Thu, 13 Aug 2015 05:30:05 -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 vBBkq2QtvN5p; Thu, 13 Aug 2015 05:30:02 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 243051A1A99; Thu, 13 Aug 2015 05:30:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12203; q=dns/txt; s=iport; t=1439469002; x=1440678602; h=message-id:date:from:mime-version:to:cc:subject; bh=lEYMueYsoewtXo8fDvcBfkrLpCn6SwjDSPongpCbDnY=; b=hRWX52BNmtShrjAOs5ULj6sDVQxSnpN9CwU7AWYTZLfPQ3f4vcBnmnYK 4zVOs6Kt2NMOCAVJ7XDcZUoJtoGegnvf5NIwNqYauR7lfpgcoQxgq4l1u LuIlrI5vx4Gff5zUAjb+uPD1iCYruy99bHieoWxJ1dC7wIB53232R+hSF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CPBQDtjMxV/xbLJq1dh3zBQ4EQggoBAQEBAQGBC4QmJ0sLGSMhAhECTA0BBwEBiCqdDJ0dlkEBAQEBAQUBAQEBAQEBARqQXIJwgUMBBJUajGyBSoQrgneRNiaDfzyCfwEBAQ
X-IronPort-AV: E=Sophos;i="5.15,670,1432598400";  d="scan'208,217";a="604906670"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 13 Aug 2015 12:30:00 +0000
Received: from [10.148.51.59] ([10.148.51.59]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t7DCTxgI022314; Thu, 13 Aug 2015 12:29:59 GMT
Message-ID: <55CC8DC7.40903@cisco.com>
Date: Thu, 13 Aug 2015 14:29:59 +0200
From: Sergio Mena <semena@cisco.com>
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>
Content-Type: multipart/alternative; boundary="------------070507070502050805040603"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/F90QKWq5eFWTk3zVZmGeK2W8moc>
Cc: rmcat@ietf.org, draft-ietf-rmcat-eval-test@ietf.org
Subject: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 13 Aug 2015 12:30:05 -0000

This is a multi-part message in MIME format.
--------------070507070502050805040603
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Zahed,

/[CCed the author list of the rmcat test cases draft, as well as the 
rmcat mailing list]/

There was a discussion triggered at rmcat main session in Prague on how 
to simulate bottleneck-link bandwidth changes. Two options were 
discussed (1) changing the physical link throughput (currently specified 
in the draft), and (2) using an insensitive CBR UDP flow as background 
traffic.

My understanding from the discussion during the session was that none of 
these two options can simulate the other and, therefore, we somehow need 
to test how candidate algorithms adapt in both cases.

You and I then had an offline discussion on the subject in which you 
suggested me to review sections 5.1 and 5.2 of the test cases draft, and 
propose an alternate text to extend these two test cases to the 
background traffic option.

I have reviewed sections 5.1 and 5.2 and come up with a proposal for 
extending them to using insensitive background traffic, in addition to 
the current option in the text (physical link throughput change).

Please find below what I would like to propose as updated text for 5.1 
and 5.2. [Text in square brackets are instructions to locate and replace 
the original text].

Thanks,

Sergio Mena


PS Proposed changes:

===========
Section 5.1
===========

[In the three-bullet list after the first paragraph, change the text in 
the second bullet from:]

     o change in available capacity (e.g., due to interface change,
       routing change).

[to]

     o change in available capacity (e.g., due to interface change,
       routing change, sharp change in background traffic).

---

[Replace the paragraph immediately after the three-bullet list mentioned 
above, the one that starts with]

It should be noted that the exact variation...

[with the following]

The test case defined in this section (5.1) is divided into two subcases 
5.1a and 5.1b. The main
difference is how the bottleneck-link capacity is changed in the 
testbed. In 5.1a, the goal is to
simulate a modification in the underlying physical properties, such as 
routing change or interface
change. In 5.1b, the goal is to simulate a sharp change in background 
traffic to which the candidate
algorithm is to adapt.

---

[Change the last item of testbed attributes from]

       *  Competing traffic:

          +  Number of sources : Zero (0)

[to]

       *  Competing traffic:

          +  In 5.1a

             - Number of sources : Zero (0)

          +  In 5.1b

             - Number of sources : One (1)

             - Type of sources : CBR traffic

             - Sending bitrate : See test specific information below.

             - Traffic direction : Forward

             - Congestion control : None (insensitive traffic)

             - Traffic timeline:

               - Start time : 0s

               - End time : 100s

---

[Change 2nd bullet of test-specific information from]

       *  This test uses bottleneck path capacity variation as listed in
          Table 1

[to]

       *  This test uses bottleneck path capacity variation as listed in
          Table 1.

          - In 5.1a, the path capacity transitions are achieved by 
instantly changing the
            physical throughput of the bottleneck link. For simplicity, 
when changing
            the bottleneck link throughput, other parameters such as 
queue length in
            packets will be left unchanged, even if it implies that the 
new queue has a
            different length in milliseconds.

          - In 5.1b, the path capacity transitions are achieved by 
instantly changing the
            sending bitrate of the competing CBR flow. The new sending 
bitrate must be
            the difference between the bottleneck link-capacity (4 Mbps, 
as specified in
            4.2) and the capacity specified in Table 1.

            The sharp bitrate change in the CBR flow might imply the 
losses on both the
            application-related traffic and the CBR flow. As a result, 
the reaction of
            the candidate algorithm might be different in 5.1a and in 
5.1b, hence the
            distinction between the two sub-cases.


===========
Section 5.2
===========

[Insert this after the first paragraph of the section]

Analogously to Section 5.1, the present test case (5.2) is divided into 
two subcases 5.2a and 5.2b.
The main difference is the same: 5.2a simulates a change in the 
underlying physical network properties,
such as routing change or interface change; whereas 5.2b simulates a 
sharp change in background
competing traffic.

---

[Change last paragraph from]

    Test Specific Information: This test uses path capacity variation as
    listed in Table 2 with a corresponding end time of 125 seconds.

[to]

    Test Specific Information: This test uses path capacity variation as
    listed in Table 2 with a corresponding end time of 125 seconds. The
    two media flows stop at time 124.


--------------070507070502050805040603
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Zahed,<br>
    <br>
    <i>[CCed the author list of the rmcat test cases draft, as well as
      the rmcat mailing list]</i><br>
    <br>
    There was a discussion triggered at rmcat main session in Prague on
    how to simulate bottleneck-link bandwidth changes. Two options were
    discussed (1) changing the physical link throughput (currently
    specified in the draft), and (2) using an insensitive CBR UDP flow
    as background traffic.<br>
    <br>
    My understanding from the discussion during the session was that
    none of these two options can simulate the other and, therefore, we
    somehow need to test how candidate algorithms adapt in both cases.<br>
    <br>
    You and I then had an offline discussion on the subject in which you
    suggested me to review sections 5.1 and 5.2 of the test cases draft,
    and propose an alternate text to extend these two test cases to the
    background traffic option.<br>
    <br>
    I have reviewed sections 5.1 and 5.2 and come up with a proposal for
    extending them to using insensitive background traffic, in addition
    to the current option in the text (physical link throughput change).<br>
    <br>
    Please find below what I would like to propose as updated text for
    5.1 and 5.2. [Text in square brackets are instructions to locate and
    replace the original text].<br>
    <br>
    Thanks,<br>
    <br>
    Sergio Mena<br>
    <br>
    <br>
    PS Proposed changes:<br>
    <br>
    ===========<br>
    Section 5.1<br>
    ===========<br>
    <br>
    [In the three-bullet list after the first paragraph, change the text
    in the second bullet from:]<br>
    <br>
        o change in available capacity (e.g., due to interface change,<br>
          routing change).<br>
    <br>
    [to]<br>
    <br>
        o change in available capacity (e.g., due to interface change,<br>
          routing change, sharp change in background traffic).<br>
    <br>
    ---<br>
    <br>
    [Replace the paragraph immediately after the three-bullet list
    mentioned above, the one that starts with]<br>
    <br>
    It should be noted that the exact variation...<br>
    <br>
    [with the following]<br>
    <br>
    The test case defined in this section (5.1) is divided into two
    subcases 5.1a and 5.1b. The main<br>
    difference is how the bottleneck-link capacity is changed in the
    testbed. In 5.1a, the goal is to<br>
    simulate a modification in the underlying physical properties, such
    as routing change or interface<br>
    change. In 5.1b, the goal is to simulate a sharp change in
    background traffic to which the candidate<br>
    algorithm is to adapt.<br>
    <br>
    ---<br>
    <br>
    [Change the last item of testbed attributes from]<br>
    <br>
          *  Competing traffic:<br>
    <br>
             +  Number of sources : Zero (0)<br>
    <br>
    [to]<br>
    <br>
          *  Competing traffic:<br>
    <br>
             +  In 5.1a<br>
    <br>
                - Number of sources : Zero (0)<br>
    <br>
             +  In 5.1b<br>
    <br>
                - Number of sources : One (1)<br>
    <br>
                - Type of sources : CBR traffic <br>
    <br>
                - Sending bitrate : See test specific information below.<br>
    <br>
                - Traffic direction : Forward<br>
    <br>
                - Congestion control : None (insensitive traffic)<br>
    <br>
                - Traffic timeline:<br>
    <br>
                  - Start time : 0s<br>
    <br>
                  - End time : 100s<br>
    <br>
    ---<br>
    <br>
    [Change 2nd bullet of test-specific information from]<br>
    <br>
          *  This test uses bottleneck path capacity variation as listed
    in<br>
             Table 1<br>
    <br>
    [to]<br>
    <br>
          *  This test uses bottleneck path capacity variation as listed
    in<br>
             Table 1.<br>
    <br>
             - In 5.1a, the path capacity transitions are achieved by
    instantly changing the <br>
               physical throughput of the bottleneck link. For
    simplicity, when changing<br>
               the bottleneck link throughput, other parameters such as
    queue length in <br>
               packets will be left unchanged, even if it implies that
    the new queue has a <br>
               different length in milliseconds.<br>
    <br>
             - In 5.1b, the path capacity transitions are achieved by
    instantly changing the<br>
               sending bitrate of the competing CBR flow. The new
    sending bitrate must be<br>
               the difference between the bottleneck link-capacity (4
    Mbps, as specified in <br>
               4.2) and the capacity specified in Table 1.<br>
    <br>
               The sharp bitrate change in the CBR flow might imply the
    losses on both the<br>
               application-related traffic and the CBR flow. As a
    result, the reaction of<br>
               the candidate algorithm might be different in 5.1a and in
    5.1b, hence the<br>
               distinction between the two sub-cases.<br>
    <br>
    <br>
    ===========<br>
    Section 5.2<br>
    ===========<br>
    <br>
    [Insert this after the first paragraph of the section]<br>
    <br>
    Analogously to Section 5.1, the present test case (5.2) is divided
    into two subcases 5.2a and 5.2b.<br>
    The main difference is the same: 5.2a simulates a change in the
    underlying physical network properties,<br>
    such as routing change or interface change; whereas 5.2b simulates a
    sharp change in background<br>
    competing traffic.<br>
    <br>
    ---<br>
    <br>
    [Change last paragraph from]<br>
    <br>
       Test Specific Information: This test uses path capacity variation
    as<br>
       listed in Table 2 with a corresponding end time of 125 seconds.<br>
    <br>
    [to]<br>
    <br>
       Test Specific Information: This test uses path capacity variation
    as<br>
       listed in Table 2 with a corresponding end time of 125 seconds.
    The<br>
       two media flows stop at time 124.<br>
    <br>
  </body>
</html>

--------------070507070502050805040603--


From nobody Mon Aug 24 04:46:01 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 E0C2A1B33C6; Mon, 24 Aug 2015 04:45:58 -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 1jVIv8HTvIGS; Mon, 24 Aug 2015 04:45:56 -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 D05661B3389; Mon, 24 Aug 2015 04:45:51 -0700 (PDT)
X-AuditID: c1b4fb2d-f79626d000004282-28-55db03edfdad
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id AE.0C.17026.DE30BD55; Mon, 24 Aug 2015 13:45:50 +0200 (CEST)
Received: from ESESSMB307.ericsson.se ([169.254.7.210]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0210.002; Mon, 24 Aug 2015 13:45:49 +0200
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Sergio Mena <semena@cisco.com>
Thread-Topic: Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01
Thread-Index: AQHQ1cPHsIfC0lOLU0OunCcg1b+IdZ4bFn7A
Date: Mon, 24 Aug 2015 11:45:49 +0000
Message-ID: <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se>
References: <55CC8DC7.40903@cisco.com>
In-Reply-To: <55CC8DC7.40903@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2ESESSMB307erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGfG3Rvcd8+1Qg5sbGC0m3j/LbrH65gc2 izXTv7E7MHtM+b2R1WPJkp9MAUxRXDYpqTmZZalF+nYJXBn7rr1lKbhxkLFiz82lTA2MJ/Yw djFycEgImEhMnRfQxcgJZIpJXLi3nq2LkYtDSOAoo8T07rksEM4SRokFx78wgTSwCdhIPF7s B9IgIqAk0Xz5EdgcZoESiTsns0DCwgJOEtPvnWWCKHGWWPbrNAtIiYiAkcSRQwkgJouAqsTk T2UgFbwCvhI7myYwg9hCAmoS0/b8YAMp4RRQl5gz1wQkzAh02PdTa8AGMguIS9x6Mp8J4mAB iSV7zjND2KISLx//Y4WwFSV2nm1nhqjPl3i4aw0bxCpBiZMzn7BMYBSdhWTULCRls5CUzQJ7 S1Ni/S59iBJFiSndD9khbA2J1jlz2ZHFFzCyr2IULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQI jLiDW37r7mBc/drxEKMAB6MSD2+C061QIdbEsuLK3EOM0hwsSuK8MzbnhQoJpCeWpGanphak FsUXleakFh9iZOLglGpgnGnOfjCt+IUkcxdT6swn6ycb/eq8+mfZ/StLvNNt9ood+Bm14uyk d6qrv23ikD11cMJLZYGVmRo19z64ORZFcVfkqpRfDjh3Q/aUxnomrx2XfQzZf7z2z3UU2/tt vpcvY+++7V+Uri+5tWjO0s+7Dhd8Wfxc2PAdz7bUaU6Lt99YYRG88XlnkLsSS3FGoqEWc1Fx IgCALIiMmQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/dFep7ol4aP7Bghh2Mc_gXOh0yTw>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 24 Aug 2015 11:45:59 -0000

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

SGkgU2VyZ2lvLA0KDQpUaGFua3MgZm9yIHlvdXIgZWZmb3J0Lg0KDQpJIHRoaW5rIHRoZSBwcm9w
b3NlZCBjaGFuZ2VzIGxvb2tzIGdvb2QuDQoNCkFzIHdlIGhhdmUgcGxhbiB0byB1cGRhdGUgdGhl
IHZhcmlhdGlvbiBvZiBwYXRoIGNhcGFjaXR5IHJlbGF0aXZlIHRvIGluaXRpYWwgcGF0aCBjYXBh
Y2l0eSBmb3IgdGVzdCBjYXNlIDUuMSBhbmQgdGVzdCBjYXNlIDUuMiwgd2UgbmVlZCB0byBjaGFu
Z2UgdGhlIHJlc3BlY3RpdmUgdGV4dCBpbiB0aGUgNS4xYiBhbmQgNS4yYiB0byBiZSBhbGlnbmVk
IHdpdGggdGhhdC4NCg0KT25lIGNsYXJpZmljYXRpb24gcXVlc3Rpb24gOiBpbiA1LjFiIHdoYXQg
ZG9lcyB0aGUg4oCcaW5zZW5zaXRpdmUgdHJhZmZpY+KAnSBtZWFucyBpbiB0aGUgbmV3IHRleHQ/
DQoNCkJSDQoNClphaGVkDQoNCkZyb206IFNlcmdpbyBNZW5hIFttYWlsdG86c2VtZW5hQGNpc2Nv
LmNvbV0NClNlbnQ6IGRlbiAxMyBhdWd1c3RpIDIwMTUgMTQ6MzANClRvOiBaYWhlZHV6emFtYW4g
U2Fya2VyDQpDYzogZHJhZnQtaWV0Zi1ybWNhdC1ldmFsLXRlc3RAaWV0Zi5vcmc7IHJtY2F0QGll
dGYub3JnDQpTdWJqZWN0OiBTZWN0aW9ucyA1LjEgYW5kIDUuMiBvZiBkcmFmdC1pZXRmLXJtY2F0
LWV2YWwtdGVzdC0wMQ0KDQpaYWhlZCwNCg0KW0NDZWQgdGhlIGF1dGhvciBsaXN0IG9mIHRoZSBy
bWNhdCB0ZXN0IGNhc2VzIGRyYWZ0LCBhcyB3ZWxsIGFzIHRoZSBybWNhdCBtYWlsaW5nIGxpc3Rd
DQoNClRoZXJlIHdhcyBhIGRpc2N1c3Npb24gdHJpZ2dlcmVkIGF0IHJtY2F0IG1haW4gc2Vzc2lv
biBpbiBQcmFndWUgb24gaG93IHRvIHNpbXVsYXRlIGJvdHRsZW5lY2stbGluayBiYW5kd2lkdGgg
Y2hhbmdlcy4gVHdvIG9wdGlvbnMgd2VyZSBkaXNjdXNzZWQgKDEpIGNoYW5naW5nIHRoZSBwaHlz
aWNhbCBsaW5rIHRocm91Z2hwdXQgKGN1cnJlbnRseSBzcGVjaWZpZWQgaW4gdGhlIGRyYWZ0KSwg
YW5kICgyKSB1c2luZyBhbiBpbnNlbnNpdGl2ZSBDQlIgVURQIGZsb3cgYXMgYmFja2dyb3VuZCB0
cmFmZmljLg0KDQpNeSB1bmRlcnN0YW5kaW5nIGZyb20gdGhlIGRpc2N1c3Npb24gZHVyaW5nIHRo
ZSBzZXNzaW9uIHdhcyB0aGF0IG5vbmUgb2YgdGhlc2UgdHdvIG9wdGlvbnMgY2FuIHNpbXVsYXRl
IHRoZSBvdGhlciBhbmQsIHRoZXJlZm9yZSwgd2Ugc29tZWhvdyBuZWVkIHRvIHRlc3QgaG93IGNh
bmRpZGF0ZSBhbGdvcml0aG1zIGFkYXB0IGluIGJvdGggY2FzZXMuDQoNCllvdSBhbmQgSSB0aGVu
IGhhZCBhbiBvZmZsaW5lIGRpc2N1c3Npb24gb24gdGhlIHN1YmplY3QgaW4gd2hpY2ggeW91IHN1
Z2dlc3RlZCBtZSB0byByZXZpZXcgc2VjdGlvbnMgNS4xIGFuZCA1LjIgb2YgdGhlIHRlc3QgY2Fz
ZXMgZHJhZnQsIGFuZCBwcm9wb3NlIGFuIGFsdGVybmF0ZSB0ZXh0IHRvIGV4dGVuZCB0aGVzZSB0
d28gdGVzdCBjYXNlcyB0byB0aGUgYmFja2dyb3VuZCB0cmFmZmljIG9wdGlvbi4NCg0KSSBoYXZl
IHJldmlld2VkIHNlY3Rpb25zIDUuMSBhbmQgNS4yIGFuZCBjb21lIHVwIHdpdGggYSBwcm9wb3Nh
bCBmb3IgZXh0ZW5kaW5nIHRoZW0gdG8gdXNpbmcgaW5zZW5zaXRpdmUgYmFja2dyb3VuZCB0cmFm
ZmljLCBpbiBhZGRpdGlvbiB0byB0aGUgY3VycmVudCBvcHRpb24gaW4gdGhlIHRleHQgKHBoeXNp
Y2FsIGxpbmsgdGhyb3VnaHB1dCBjaGFuZ2UpLg0KDQpQbGVhc2UgZmluZCBiZWxvdyB3aGF0IEkg
d291bGQgbGlrZSB0byBwcm9wb3NlIGFzIHVwZGF0ZWQgdGV4dCBmb3IgNS4xIGFuZCA1LjIuIFtU
ZXh0IGluIHNxdWFyZSBicmFja2V0cyBhcmUgaW5zdHJ1Y3Rpb25zIHRvIGxvY2F0ZSBhbmQgcmVw
bGFjZSB0aGUgb3JpZ2luYWwgdGV4dF0uDQoNClRoYW5rcywNCg0KU2VyZ2lvIE1lbmENCg0KDQpQ
UyBQcm9wb3NlZCBjaGFuZ2VzOg0KDQo9PT09PT09PT09PQ0KU2VjdGlvbiA1LjENCj09PT09PT09
PT09DQoNCltJbiB0aGUgdGhyZWUtYnVsbGV0IGxpc3QgYWZ0ZXIgdGhlIGZpcnN0IHBhcmFncmFw
aCwgY2hhbmdlIHRoZSB0ZXh0IGluIHRoZSBzZWNvbmQgYnVsbGV0IGZyb206XQ0KDQogICAgbyBj
aGFuZ2UgaW4gYXZhaWxhYmxlIGNhcGFjaXR5IChlLmcuLCBkdWUgdG8gaW50ZXJmYWNlIGNoYW5n
ZSwNCiAgICAgIHJvdXRpbmcgY2hhbmdlKS4NCg0KW3RvXQ0KDQogICAgbyBjaGFuZ2UgaW4gYXZh
aWxhYmxlIGNhcGFjaXR5IChlLmcuLCBkdWUgdG8gaW50ZXJmYWNlIGNoYW5nZSwNCiAgICAgIHJv
dXRpbmcgY2hhbmdlLCBzaGFycCBjaGFuZ2UgaW4gYmFja2dyb3VuZCB0cmFmZmljKS4NCg0KLS0t
DQoNCltSZXBsYWNlIHRoZSBwYXJhZ3JhcGggaW1tZWRpYXRlbHkgYWZ0ZXIgdGhlIHRocmVlLWJ1
bGxldCBsaXN0IG1lbnRpb25lZCBhYm92ZSwgdGhlIG9uZSB0aGF0IHN0YXJ0cyB3aXRoXQ0KDQpJ
dCBzaG91bGQgYmUgbm90ZWQgdGhhdCB0aGUgZXhhY3QgdmFyaWF0aW9uLi4uDQoNClt3aXRoIHRo
ZSBmb2xsb3dpbmddDQoNClRoZSB0ZXN0IGNhc2UgZGVmaW5lZCBpbiB0aGlzIHNlY3Rpb24gKDUu
MSkgaXMgZGl2aWRlZCBpbnRvIHR3byBzdWJjYXNlcyA1LjFhIGFuZCA1LjFiLiBUaGUgbWFpbg0K
ZGlmZmVyZW5jZSBpcyBob3cgdGhlIGJvdHRsZW5lY2stbGluayBjYXBhY2l0eSBpcyBjaGFuZ2Vk
IGluIHRoZSB0ZXN0YmVkLiBJbiA1LjFhLCB0aGUgZ29hbCBpcyB0bw0Kc2ltdWxhdGUgYSBtb2Rp
ZmljYXRpb24gaW4gdGhlIHVuZGVybHlpbmcgcGh5c2ljYWwgcHJvcGVydGllcywgc3VjaCBhcyBy
b3V0aW5nIGNoYW5nZSBvciBpbnRlcmZhY2UNCmNoYW5nZS4gSW4gNS4xYiwgdGhlIGdvYWwgaXMg
dG8gc2ltdWxhdGUgYSBzaGFycCBjaGFuZ2UgaW4gYmFja2dyb3VuZCB0cmFmZmljIHRvIHdoaWNo
IHRoZSBjYW5kaWRhdGUNCmFsZ29yaXRobSBpcyB0byBhZGFwdC4NCg0KLS0tDQoNCltDaGFuZ2Ug
dGhlIGxhc3QgaXRlbSBvZiB0ZXN0YmVkIGF0dHJpYnV0ZXMgZnJvbV0NCg0KICAgICAgKiAgQ29t
cGV0aW5nIHRyYWZmaWM6DQoNCiAgICAgICAgICsgIE51bWJlciBvZiBzb3VyY2VzIDogWmVybyAo
MCkNCg0KW3RvXQ0KDQogICAgICAqICBDb21wZXRpbmcgdHJhZmZpYzoNCg0KICAgICAgICAgKyAg
SW4gNS4xYQ0KDQogICAgICAgICAgICAtIE51bWJlciBvZiBzb3VyY2VzIDogWmVybyAoMCkNCg0K
ICAgICAgICAgKyAgSW4gNS4xYg0KDQogICAgICAgICAgICAtIE51bWJlciBvZiBzb3VyY2VzIDog
T25lICgxKQ0KDQogICAgICAgICAgICAtIFR5cGUgb2Ygc291cmNlcyA6IENCUiB0cmFmZmljDQoN
CiAgICAgICAgICAgIC0gU2VuZGluZyBiaXRyYXRlIDogU2VlIHRlc3Qgc3BlY2lmaWMgaW5mb3Jt
YXRpb24gYmVsb3cuDQoNCiAgICAgICAgICAgIC0gVHJhZmZpYyBkaXJlY3Rpb24gOiBGb3J3YXJk
DQoNCiAgICAgICAgICAgIC0gQ29uZ2VzdGlvbiBjb250cm9sIDogTm9uZSAoaW5zZW5zaXRpdmUg
dHJhZmZpYykNCg0KICAgICAgICAgICAgLSBUcmFmZmljIHRpbWVsaW5lOg0KDQogICAgICAgICAg
ICAgIC0gU3RhcnQgdGltZSA6IDBzDQoNCiAgICAgICAgICAgICAgLSBFbmQgdGltZSA6IDEwMHMN
Cg0KLS0tDQoNCltDaGFuZ2UgMm5kIGJ1bGxldCBvZiB0ZXN0LXNwZWNpZmljIGluZm9ybWF0aW9u
IGZyb21dDQoNCiAgICAgICogIFRoaXMgdGVzdCB1c2VzIGJvdHRsZW5lY2sgcGF0aCBjYXBhY2l0
eSB2YXJpYXRpb24gYXMgbGlzdGVkIGluDQogICAgICAgICBUYWJsZSAxDQoNClt0b10NCg0KICAg
ICAgKiAgVGhpcyB0ZXN0IHVzZXMgYm90dGxlbmVjayBwYXRoIGNhcGFjaXR5IHZhcmlhdGlvbiBh
cyBsaXN0ZWQgaW4NCiAgICAgICAgIFRhYmxlIDEuDQoNCiAgICAgICAgIC0gSW4gNS4xYSwgdGhl
IHBhdGggY2FwYWNpdHkgdHJhbnNpdGlvbnMgYXJlIGFjaGlldmVkIGJ5IGluc3RhbnRseSBjaGFu
Z2luZyB0aGUNCiAgICAgICAgICAgcGh5c2ljYWwgdGhyb3VnaHB1dCBvZiB0aGUgYm90dGxlbmVj
ayBsaW5rLiBGb3Igc2ltcGxpY2l0eSwgd2hlbiBjaGFuZ2luZw0KICAgICAgICAgICB0aGUgYm90
dGxlbmVjayBsaW5rIHRocm91Z2hwdXQsIG90aGVyIHBhcmFtZXRlcnMgc3VjaCBhcyBxdWV1ZSBs
ZW5ndGggaW4NCiAgICAgICAgICAgcGFja2V0cyB3aWxsIGJlIGxlZnQgdW5jaGFuZ2VkLCBldmVu
IGlmIGl0IGltcGxpZXMgdGhhdCB0aGUgbmV3IHF1ZXVlIGhhcyBhDQogICAgICAgICAgIGRpZmZl
cmVudCBsZW5ndGggaW4gbWlsbGlzZWNvbmRzLg0KDQogICAgICAgICAtIEluIDUuMWIsIHRoZSBw
YXRoIGNhcGFjaXR5IHRyYW5zaXRpb25zIGFyZSBhY2hpZXZlZCBieSBpbnN0YW50bHkgY2hhbmdp
bmcgdGhlDQogICAgICAgICAgIHNlbmRpbmcgYml0cmF0ZSBvZiB0aGUgY29tcGV0aW5nIENCUiBm
bG93LiBUaGUgbmV3IHNlbmRpbmcgYml0cmF0ZSBtdXN0IGJlDQogICAgICAgICAgIHRoZSBkaWZm
ZXJlbmNlIGJldHdlZW4gdGhlIGJvdHRsZW5lY2sgbGluay1jYXBhY2l0eSAoNCBNYnBzLCBhcyBz
cGVjaWZpZWQgaW4NCiAgICAgICAgICAgNC4yKSBhbmQgdGhlIGNhcGFjaXR5IHNwZWNpZmllZCBp
biBUYWJsZSAxLg0KDQogICAgICAgICAgIFRoZSBzaGFycCBiaXRyYXRlIGNoYW5nZSBpbiB0aGUg
Q0JSIGZsb3cgbWlnaHQgaW1wbHkgdGhlIGxvc3NlcyBvbiBib3RoIHRoZQ0KICAgICAgICAgICBh
cHBsaWNhdGlvbi1yZWxhdGVkIHRyYWZmaWMgYW5kIHRoZSBDQlIgZmxvdy4gQXMgYSByZXN1bHQs
IHRoZSByZWFjdGlvbiBvZg0KICAgICAgICAgICB0aGUgY2FuZGlkYXRlIGFsZ29yaXRobSBtaWdo
dCBiZSBkaWZmZXJlbnQgaW4gNS4xYSBhbmQgaW4gNS4xYiwgaGVuY2UgdGhlDQogICAgICAgICAg
IGRpc3RpbmN0aW9uIGJldHdlZW4gdGhlIHR3byBzdWItY2FzZXMuDQoNCg0KPT09PT09PT09PT0N
ClNlY3Rpb24gNS4yDQo9PT09PT09PT09PQ0KDQpbSW5zZXJ0IHRoaXMgYWZ0ZXIgdGhlIGZpcnN0
IHBhcmFncmFwaCBvZiB0aGUgc2VjdGlvbl0NCg0KQW5hbG9nb3VzbHkgdG8gU2VjdGlvbiA1LjEs
IHRoZSBwcmVzZW50IHRlc3QgY2FzZSAoNS4yKSBpcyBkaXZpZGVkIGludG8gdHdvIHN1YmNhc2Vz
IDUuMmEgYW5kIDUuMmIuDQpUaGUgbWFpbiBkaWZmZXJlbmNlIGlzIHRoZSBzYW1lOiA1LjJhIHNp
bXVsYXRlcyBhIGNoYW5nZSBpbiB0aGUgdW5kZXJseWluZyBwaHlzaWNhbCBuZXR3b3JrIHByb3Bl
cnRpZXMsDQpzdWNoIGFzIHJvdXRpbmcgY2hhbmdlIG9yIGludGVyZmFjZSBjaGFuZ2U7IHdoZXJl
YXMgNS4yYiBzaW11bGF0ZXMgYSBzaGFycCBjaGFuZ2UgaW4gYmFja2dyb3VuZA0KY29tcGV0aW5n
IHRyYWZmaWMuDQoNCi0tLQ0KDQpbQ2hhbmdlIGxhc3QgcGFyYWdyYXBoIGZyb21dDQoNCiAgIFRl
c3QgU3BlY2lmaWMgSW5mb3JtYXRpb246IFRoaXMgdGVzdCB1c2VzIHBhdGggY2FwYWNpdHkgdmFy
aWF0aW9uIGFzDQogICBsaXN0ZWQgaW4gVGFibGUgMiB3aXRoIGEgY29ycmVzcG9uZGluZyBlbmQg
dGltZSBvZiAxMjUgc2Vjb25kcy4NCg0KW3RvXQ0KDQogICBUZXN0IFNwZWNpZmljIEluZm9ybWF0
aW9uOiBUaGlzIHRlc3QgdXNlcyBwYXRoIGNhcGFjaXR5IHZhcmlhdGlvbiBhcw0KICAgbGlzdGVk
IGluIFRhYmxlIDIgd2l0aCBhIGNvcnJlc3BvbmRpbmcgZW5kIHRpbWUgb2YgMTI1IHNlY29uZHMu
IFRoZQ0KICAgdHdvIG1lZGlhIGZsb3dzIHN0b3AgYXQgdGltZSAxMjQuDQo=

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2ESESSMB307erics_
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
ZXcgUm9tYW4iLCJzZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVy
bGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjoj
MUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9y
PSJ3aGl0ZSIgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBj
bGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBTZXJnaW8sPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGFua3Mg
Zm9yIHlvdXIgZWZmb3J0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SSB0aGluayB0aGUgcHJvcG9zZWQgY2hhbmdlcyBs
b29rcyBnb29kLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+QXMgd2UgaGF2ZSBwbGFuIHRvIHVwZGF0ZSB0aGUgdmFyaWF0
aW9uIG9mIHBhdGggY2FwYWNpdHkgcmVsYXRpdmUgdG8gaW5pdGlhbCBwYXRoIGNhcGFjaXR5IGZv
ciB0ZXN0IGNhc2UgNS4xIGFuZCB0ZXN0IGNhc2UgNS4yLCB3ZSBuZWVkIHRvIGNoYW5nZSB0aGUg
cmVzcGVjdGl2ZQ0KIHRleHQgaW4gdGhlIDUuMWIgYW5kIDUuMmIgdG8gYmUgYWxpZ25lZCB3aXRo
IHRoYXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5PbmUgY2xhcmlmaWNhdGlvbiBxdWVzdGlvbiA6IGluIDUuMWIgd2hh
dCBkb2VzIHRoZSDigJxpbnNlbnNpdGl2ZSB0cmFmZmlj4oCdIG1lYW5zIGluIHRoZSBuZXcgdGV4
dD88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkJSPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5aYWhlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQi
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOndpbmRvd3RleHQiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjp3aW5kb3d0ZXh0Ij4gU2Vy
Z2lvIE1lbmEgW21haWx0bzpzZW1lbmFAY2lzY28uY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IGRl
biAxMyBhdWd1c3RpIDIwMTUgMTQ6MzA8YnI+DQo8Yj5Ubzo8L2I+IFphaGVkdXp6YW1hbiBTYXJr
ZXI8YnI+DQo8Yj5DYzo8L2I+IGRyYWZ0LWlldGYtcm1jYXQtZXZhbC10ZXN0QGlldGYub3JnOyBy
bWNhdEBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBTZWN0aW9ucyA1LjEgYW5kIDUuMiBv
ZiBkcmFmdC1pZXRmLXJtY2F0LWV2YWwtdGVzdC0wMTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+WmFoZWQs
PGJyPg0KPGJyPg0KPGk+W0NDZWQgdGhlIGF1dGhvciBsaXN0IG9mIHRoZSBybWNhdCB0ZXN0IGNh
c2VzIGRyYWZ0LCBhcyB3ZWxsIGFzIHRoZSBybWNhdCBtYWlsaW5nIGxpc3RdPC9pPjxicj4NCjxi
cj4NClRoZXJlIHdhcyBhIGRpc2N1c3Npb24gdHJpZ2dlcmVkIGF0IHJtY2F0IG1haW4gc2Vzc2lv
biBpbiBQcmFndWUgb24gaG93IHRvIHNpbXVsYXRlIGJvdHRsZW5lY2stbGluayBiYW5kd2lkdGgg
Y2hhbmdlcy4gVHdvIG9wdGlvbnMgd2VyZSBkaXNjdXNzZWQgKDEpIGNoYW5naW5nIHRoZSBwaHlz
aWNhbCBsaW5rIHRocm91Z2hwdXQgKGN1cnJlbnRseSBzcGVjaWZpZWQgaW4gdGhlIGRyYWZ0KSwg
YW5kICgyKSB1c2luZyBhbiBpbnNlbnNpdGl2ZSBDQlINCiBVRFAgZmxvdyBhcyBiYWNrZ3JvdW5k
IHRyYWZmaWMuPGJyPg0KPGJyPg0KTXkgdW5kZXJzdGFuZGluZyBmcm9tIHRoZSBkaXNjdXNzaW9u
IGR1cmluZyB0aGUgc2Vzc2lvbiB3YXMgdGhhdCBub25lIG9mIHRoZXNlIHR3byBvcHRpb25zIGNh
biBzaW11bGF0ZSB0aGUgb3RoZXIgYW5kLCB0aGVyZWZvcmUsIHdlIHNvbWVob3cgbmVlZCB0byB0
ZXN0IGhvdyBjYW5kaWRhdGUgYWxnb3JpdGhtcyBhZGFwdCBpbiBib3RoIGNhc2VzLjxicj4NCjxi
cj4NCllvdSBhbmQgSSB0aGVuIGhhZCBhbiBvZmZsaW5lIGRpc2N1c3Npb24gb24gdGhlIHN1Ympl
Y3QgaW4gd2hpY2ggeW91IHN1Z2dlc3RlZCBtZSB0byByZXZpZXcgc2VjdGlvbnMgNS4xIGFuZCA1
LjIgb2YgdGhlIHRlc3QgY2FzZXMgZHJhZnQsIGFuZCBwcm9wb3NlIGFuIGFsdGVybmF0ZSB0ZXh0
IHRvIGV4dGVuZCB0aGVzZSB0d28gdGVzdCBjYXNlcyB0byB0aGUgYmFja2dyb3VuZCB0cmFmZmlj
IG9wdGlvbi48YnI+DQo8YnI+DQpJIGhhdmUgcmV2aWV3ZWQgc2VjdGlvbnMgNS4xIGFuZCA1LjIg
YW5kIGNvbWUgdXAgd2l0aCBhIHByb3Bvc2FsIGZvciBleHRlbmRpbmcgdGhlbSB0byB1c2luZyBp
bnNlbnNpdGl2ZSBiYWNrZ3JvdW5kIHRyYWZmaWMsIGluIGFkZGl0aW9uIHRvIHRoZSBjdXJyZW50
IG9wdGlvbiBpbiB0aGUgdGV4dCAocGh5c2ljYWwgbGluayB0aHJvdWdocHV0IGNoYW5nZSkuPGJy
Pg0KPGJyPg0KUGxlYXNlIGZpbmQgYmVsb3cgd2hhdCBJIHdvdWxkIGxpa2UgdG8gcHJvcG9zZSBh
cyB1cGRhdGVkIHRleHQgZm9yIDUuMSBhbmQgNS4yLiBbVGV4dCBpbiBzcXVhcmUgYnJhY2tldHMg
YXJlIGluc3RydWN0aW9ucyB0byBsb2NhdGUgYW5kIHJlcGxhY2UgdGhlIG9yaWdpbmFsIHRleHRd
Ljxicj4NCjxicj4NClRoYW5rcyw8YnI+DQo8YnI+DQpTZXJnaW8gTWVuYTxicj4NCjxicj4NCjxi
cj4NClBTIFByb3Bvc2VkIGNoYW5nZXM6PGJyPg0KPGJyPg0KPT09PT09PT09PT08YnI+DQpTZWN0
aW9uIDUuMTxicj4NCj09PT09PT09PT09PGJyPg0KPGJyPg0KW0luIHRoZSB0aHJlZS1idWxsZXQg
bGlzdCBhZnRlciB0aGUgZmlyc3QgcGFyYWdyYXBoLCBjaGFuZ2UgdGhlIHRleHQgaW4gdGhlIHNl
Y29uZCBidWxsZXQgZnJvbTpdPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7IG8gY2hhbmdl
IGluIGF2YWlsYWJsZSBjYXBhY2l0eSAoZS5nLiwgZHVlIHRvIGludGVyZmFjZSBjaGFuZ2UsPGJy
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJvdXRpbmcgY2hhbmdlKS48YnI+DQo8
YnI+DQpbdG9dPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7IG8gY2hhbmdlIGluIGF2YWls
YWJsZSBjYXBhY2l0eSAoZS5nLiwgZHVlIHRvIGludGVyZmFjZSBjaGFuZ2UsPGJyPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJvdXRpbmcgY2hhbmdlLCBzaGFycCBjaGFuZ2UgaW4g
YmFja2dyb3VuZCB0cmFmZmljKS48YnI+DQo8YnI+DQotLS08YnI+DQo8YnI+DQpbUmVwbGFjZSB0
aGUgcGFyYWdyYXBoIGltbWVkaWF0ZWx5IGFmdGVyIHRoZSB0aHJlZS1idWxsZXQgbGlzdCBtZW50
aW9uZWQgYWJvdmUsIHRoZSBvbmUgdGhhdCBzdGFydHMgd2l0aF08YnI+DQo8YnI+DQpJdCBzaG91
bGQgYmUgbm90ZWQgdGhhdCB0aGUgZXhhY3QgdmFyaWF0aW9uLi4uPGJyPg0KPGJyPg0KW3dpdGgg
dGhlIGZvbGxvd2luZ108YnI+DQo8YnI+DQpUaGUgdGVzdCBjYXNlIGRlZmluZWQgaW4gdGhpcyBz
ZWN0aW9uICg1LjEpIGlzIGRpdmlkZWQgaW50byB0d28gc3ViY2FzZXMgNS4xYSBhbmQgNS4xYi4g
VGhlIG1haW48YnI+DQpkaWZmZXJlbmNlIGlzIGhvdyB0aGUgYm90dGxlbmVjay1saW5rIGNhcGFj
aXR5IGlzIGNoYW5nZWQgaW4gdGhlIHRlc3RiZWQuIEluIDUuMWEsIHRoZSBnb2FsIGlzIHRvPGJy
Pg0Kc2ltdWxhdGUgYSBtb2RpZmljYXRpb24gaW4gdGhlIHVuZGVybHlpbmcgcGh5c2ljYWwgcHJv
cGVydGllcywgc3VjaCBhcyByb3V0aW5nIGNoYW5nZSBvciBpbnRlcmZhY2U8YnI+DQpjaGFuZ2Uu
IEluIDUuMWIsIHRoZSBnb2FsIGlzIHRvIHNpbXVsYXRlIGEgc2hhcnAgY2hhbmdlIGluIGJhY2tn
cm91bmQgdHJhZmZpYyB0byB3aGljaCB0aGUgY2FuZGlkYXRlPGJyPg0KYWxnb3JpdGhtIGlzIHRv
IGFkYXB0Ljxicj4NCjxicj4NCi0tLTxicj4NCjxicj4NCltDaGFuZ2UgdGhlIGxhc3QgaXRlbSBv
ZiB0ZXN0YmVkIGF0dHJpYnV0ZXMgZnJvbV08YnI+DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgKiZuYnNwOyBDb21wZXRpbmcgdHJhZmZpYzo8YnI+DQo8YnI+DQombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJiM0MzsmbmJzcDsgTnVt
YmVyIG9mIHNvdXJjZXMgOiBaZXJvICgwKTxicj4NCjxicj4NClt0b108YnI+DQo8YnI+DQombmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgKiZuYnNwOyBDb21wZXRpbmcgdHJhZmZpYzo8YnI+
DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
JiM0MzsmbmJzcDsgSW4gNS4xYTxicj4NCjxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAtIE51bWJlciBvZiBzb3Vy
Y2VzIDogWmVybyAoMCk8YnI+DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgJiM0MzsmbmJzcDsgSW4gNS4xYjxicj4NCjxicj4NCiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyAtIE51bWJlciBvZiBzb3VyY2VzIDogT25lICgxKTxicj4NCjxicj4NCiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAtIFR5
cGUgb2Ygc291cmNlcyA6IENCUiB0cmFmZmljIDxicj4NCjxicj4NCiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAtIFNlbmRp
bmcgYml0cmF0ZSA6IFNlZSB0ZXN0IHNwZWNpZmljIGluZm9ybWF0aW9uIGJlbG93Ljxicj4NCjxi
cj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyAtIFRyYWZmaWMgZGlyZWN0aW9uIDogRm9yd2FyZDxicj4NCjxicj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyAtIENvbmdlc3Rpb24gY29udHJvbCA6IE5vbmUgKGluc2Vuc2l0aXZlIHRyYWZmaWMp
PGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0gVHJhZmZpYyB0aW1lbGluZTo8YnI+DQo8YnI+DQombmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgLSBTdGFydCB0aW1lIDogMHM8YnI+DQo8YnI+DQombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgLSBFbmQgdGltZSA6IDEwMHM8YnI+DQo8YnI+DQotLS08YnI+DQo8YnI+DQpb
Q2hhbmdlIDJuZCBidWxsZXQgb2YgdGVzdC1zcGVjaWZpYyBpbmZvcm1hdGlvbiBmcm9tXTxicj4N
Cjxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAqJm5ic3A7IFRoaXMgdGVzdCB1
c2VzIGJvdHRsZW5lY2sgcGF0aCBjYXBhY2l0eSB2YXJpYXRpb24gYXMgbGlzdGVkIGluPGJyPg0K
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRhYmxlIDE8
YnI+DQo8YnI+DQpbdG9dPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
ICombmJzcDsgVGhpcyB0ZXN0IHVzZXMgYm90dGxlbmVjayBwYXRoIGNhcGFjaXR5IHZhcmlhdGlv
biBhcyBsaXN0ZWQgaW48YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgVGFibGUgMS48YnI+DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLSBJbiA1LjFhLCB0aGUgcGF0aCBjYXBhY2l0eSB0cmFu
c2l0aW9ucyBhcmUgYWNoaWV2ZWQgYnkgaW5zdGFudGx5IGNoYW5naW5nIHRoZQ0KPGJyPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IHBoeXNpY2FsIHRocm91Z2hwdXQgb2YgdGhlIGJvdHRsZW5lY2sgbGluay4gRm9yIHNpbXBsaWNp
dHksIHdoZW4gY2hhbmdpbmc8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdGhlIGJvdHRsZW5lY2sgbGluayB0aHJvdWdocHV0
LCBvdGhlciBwYXJhbWV0ZXJzIHN1Y2ggYXMgcXVldWUgbGVuZ3RoIGluDQo8YnI+DQombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgcGFj
a2V0cyB3aWxsIGJlIGxlZnQgdW5jaGFuZ2VkLCBldmVuIGlmIGl0IGltcGxpZXMgdGhhdCB0aGUg
bmV3IHF1ZXVlIGhhcyBhDQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZGlmZmVyZW50IGxlbmd0aCBpbiBtaWxsaXNlY29u
ZHMuPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IC0gSW4gNS4xYiwgdGhlIHBhdGggY2FwYWNpdHkgdHJhbnNpdGlvbnMgYXJlIGFjaGll
dmVkIGJ5IGluc3RhbnRseSBjaGFuZ2luZyB0aGU8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgc2VuZGluZyBiaXRyYXRlIG9m
IHRoZSBjb21wZXRpbmcgQ0JSIGZsb3cuIFRoZSBuZXcgc2VuZGluZyBiaXRyYXRlIG11c3QgYmU8
YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgdGhlIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGUgYm90dGxlbmVjayBsaW5rLWNhcGFj
aXR5ICg0IE1icHMsIGFzIHNwZWNpZmllZCBpbg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDQuMikgYW5kIHRoZSBjYXBh
Y2l0eSBzcGVjaWZpZWQgaW4gVGFibGUgMS48YnI+DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgVGhlIHNoYXJwIGJpdHJh
dGUgY2hhbmdlIGluIHRoZSBDQlIgZmxvdyBtaWdodCBpbXBseSB0aGUgbG9zc2VzIG9uIGJvdGgg
dGhlPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGFwcGxpY2F0aW9uLXJlbGF0ZWQgdHJhZmZpYyBhbmQgdGhlIENCUiBmbG93
LiBBcyBhIHJlc3VsdCwgdGhlIHJlYWN0aW9uIG9mPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRoZSBjYW5kaWRhdGUgYWxn
b3JpdGhtIG1pZ2h0IGJlIGRpZmZlcmVudCBpbiA1LjFhIGFuZCBpbiA1LjFiLCBoZW5jZSB0aGU8
YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgZGlzdGluY3Rpb24gYmV0d2VlbiB0aGUgdHdvIHN1Yi1jYXNlcy48YnI+DQo8YnI+
DQo8YnI+DQo9PT09PT09PT09PTxicj4NClNlY3Rpb24gNS4yPGJyPg0KPT09PT09PT09PT08YnI+
DQo8YnI+DQpbSW5zZXJ0IHRoaXMgYWZ0ZXIgdGhlIGZpcnN0IHBhcmFncmFwaCBvZiB0aGUgc2Vj
dGlvbl08YnI+DQo8YnI+DQpBbmFsb2dvdXNseSB0byBTZWN0aW9uIDUuMSwgdGhlIHByZXNlbnQg
dGVzdCBjYXNlICg1LjIpIGlzIGRpdmlkZWQgaW50byB0d28gc3ViY2FzZXMgNS4yYSBhbmQgNS4y
Yi48YnI+DQpUaGUgbWFpbiBkaWZmZXJlbmNlIGlzIHRoZSBzYW1lOiA1LjJhIHNpbXVsYXRlcyBh
IGNoYW5nZSBpbiB0aGUgdW5kZXJseWluZyBwaHlzaWNhbCBuZXR3b3JrIHByb3BlcnRpZXMsPGJy
Pg0Kc3VjaCBhcyByb3V0aW5nIGNoYW5nZSBvciBpbnRlcmZhY2UgY2hhbmdlOyB3aGVyZWFzIDUu
MmIgc2ltdWxhdGVzIGEgc2hhcnAgY2hhbmdlIGluIGJhY2tncm91bmQ8YnI+DQpjb21wZXRpbmcg
dHJhZmZpYy48YnI+DQo8YnI+DQotLS08YnI+DQo8YnI+DQpbQ2hhbmdlIGxhc3QgcGFyYWdyYXBo
IGZyb21dPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7IFRlc3QgU3BlY2lmaWMgSW5mb3JtYXRpb246
IFRoaXMgdGVzdCB1c2VzIHBhdGggY2FwYWNpdHkgdmFyaWF0aW9uIGFzPGJyPg0KJm5ic3A7Jm5i
c3A7IGxpc3RlZCBpbiBUYWJsZSAyIHdpdGggYSBjb3JyZXNwb25kaW5nIGVuZCB0aW1lIG9mIDEy
NSBzZWNvbmRzLjxicj4NCjxicj4NClt0b108YnI+DQo8YnI+DQombmJzcDsmbmJzcDsgVGVzdCBT
cGVjaWZpYyBJbmZvcm1hdGlvbjogVGhpcyB0ZXN0IHVzZXMgcGF0aCBjYXBhY2l0eSB2YXJpYXRp
b24gYXM8YnI+DQombmJzcDsmbmJzcDsgbGlzdGVkIGluIFRhYmxlIDIgd2l0aCBhIGNvcnJlc3Bv
bmRpbmcgZW5kIHRpbWUgb2YgMTI1IHNlY29uZHMuIFRoZTxicj4NCiZuYnNwOyZuYnNwOyB0d28g
bWVkaWEgZmxvd3Mgc3RvcCBhdCB0aW1lIDEyNC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2ESESSMB307erics_--


From nobody Wed Aug 26 00:35:46 2015
Return-Path: <semena@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 46B511AD35D; Wed, 26 Aug 2015 00:35:45 -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 KQ0Jm4hDe5bn; Wed, 26 Aug 2015 00:35:42 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2DF21AD356; Wed, 26 Aug 2015 00:35:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21768; q=dns/txt; s=iport; t=1440574542; x=1441784142; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=jaNn/dzHT7ggUa2tMN3gl4MYw5DE3T2xg0RRbAQSAXE=; b=Tyvlabi2nXUoLw3T4cfOExD5tuOwPjE6Rq6L4k5Y5DSPL28Ujy5n+WKs +i9QG6Qf8NAZtmVKJyvb1Y0RJB1U2vN3hgwTsmp/xMv/Ajy0az3VOX18y 9UtevxRpYHRcgSEZ320IC2b76R8qO9OWDgdIcmxmu1EeK1qa35bWxaWGT k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJAgAUa91V/xbLJq1dgk6CCoMjunMBCYZjgRACgXEUAQEBAQEBAYEKhCMBAQEEIwpBCgEQCQIRBAEBAQkWCAMCAgkDAgECATQJCAYNBgIBAYgqlX2dHZUAAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4tbhQoGAYJpgUMBBIxrhTaDFoxygUqEMoJ7iTGESYNqJoQAPDOCTAEBAQ
X-IronPort-AV: E=Sophos;i="5.17,414,1437436800";  d="scan'208,217";a="611191374"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 26 Aug 2015 07:35:38 +0000
Received: from [10.0.2.15] ([10.148.51.67]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t7Q7ZbUP016730; Wed, 26 Aug 2015 07:35:38 GMT
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se>
From: Sergio Mena <semena@cisco.com>
Message-ID: <55DD6C49.1050901@cisco.com>
Date: Wed, 26 Aug 2015 09:35:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se>
Content-Type: multipart/alternative; boundary="------------020901000507010808090702"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/NnlC7iUMDUsui5WP_5TjiLtjbeA>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 26 Aug 2015 07:35:45 -0000

This is a multi-part message in MIME format.
--------------020901000507010808090702
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


Hi Zahed,

First of all, your question. By "insensitive traffic" I meant that the 
flow is CBR, so it won't back off whether other traffic is present in 
the bottleneck link or not. Maybe we can find a better name for this...

On the other hand, in the last days, I have been working on an ns3 
implementation of some of the test cases in the draft. I realized that 
it would be coherent (and useful, IMO) for 5.3 to also have a "b" 
version where both forward and backward paths are changed by a CBR, 
similarly to 5.1 and 5.2. Let me know your thoughts on this.

Regards,

Sergio



On 24/08/15 13:45, Zaheduzzaman Sarker wrote:
>
> Hi Sergio,
>
> Thanks for your effort.
>
> I think the proposed changes looks good.
>
> As we have plan to update the variation of path capacity relative to 
> initial path capacity for test case 5.1 and test case 5.2, we need to 
> change the respective text in the 5.1b and 5.2b to be aligned with that.
>
> One clarification question : in 5.1b what does the “insensitive 
> traffic” means in the new text?
>
> BR
>
> Zahed
>
> *From:*Sergio Mena [mailto:semena@cisco.com]
> *Sent:* den 13 augusti 2015 14:30
> *To:* Zaheduzzaman Sarker
> *Cc:* draft-ietf-rmcat-eval-test@ietf.org; rmcat@ietf.org
> *Subject:* Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01
>
> Zahed,
>
> /[CCed the author list of the rmcat test cases draft, as well as the 
> rmcat mailing list]/
>
> There was a discussion triggered at rmcat main session in Prague on 
> how to simulate bottleneck-link bandwidth changes. Two options were 
> discussed (1) changing the physical link throughput (currently 
> specified in the draft), and (2) using an insensitive CBR UDP flow as 
> background traffic.
>
> My understanding from the discussion during the session was that none 
> of these two options can simulate the other and, therefore, we somehow 
> need to test how candidate algorithms adapt in both cases.
>
> You and I then had an offline discussion on the subject in which you 
> suggested me to review sections 5.1 and 5.2 of the test cases draft, 
> and propose an alternate text to extend these two test cases to the 
> background traffic option.
>
> I have reviewed sections 5.1 and 5.2 and come up with a proposal for 
> extending them to using insensitive background traffic, in addition to 
> the current option in the text (physical link throughput change).
>
> Please find below what I would like to propose as updated text for 5.1 
> and 5.2. [Text in square brackets are instructions to locate and 
> replace the original text].
>
> Thanks,
>
> Sergio Mena
>
>
> PS Proposed changes:
>
> ===========
> Section 5.1
> ===========
>
> [In the three-bullet list after the first paragraph, change the text 
> in the second bullet from:]
>
>     o change in available capacity (e.g., due to interface change,
>       routing change).
>
> [to]
>
>     o change in available capacity (e.g., due to interface change,
>       routing change, sharp change in background traffic).
>
> ---
>
> [Replace the paragraph immediately after the three-bullet list 
> mentioned above, the one that starts with]
>
> It should be noted that the exact variation...
>
> [with the following]
>
> The test case defined in this section (5.1) is divided into two 
> subcases 5.1a and 5.1b. The main
> difference is how the bottleneck-link capacity is changed in the 
> testbed. In 5.1a, the goal is to
> simulate a modification in the underlying physical properties, such as 
> routing change or interface
> change. In 5.1b, the goal is to simulate a sharp change in background 
> traffic to which the candidate
> algorithm is to adapt.
>
> ---
>
> [Change the last item of testbed attributes from]
>
>       *  Competing traffic:
>
>          +  Number of sources : Zero (0)
>
> [to]
>
>       *  Competing traffic:
>
>          +  In 5.1a
>
>             - Number of sources : Zero (0)
>
>          +  In 5.1b
>
>             - Number of sources : One (1)
>
>             - Type of sources : CBR traffic
>
>             - Sending bitrate : See test specific information below.
>
>             - Traffic direction : Forward
>
>             - Congestion control : None (insensitive traffic)
>
>             - Traffic timeline:
>
>               - Start time : 0s
>
>               - End time : 100s
>
> ---
>
> [Change 2nd bullet of test-specific information from]
>
>       *  This test uses bottleneck path capacity variation as listed in
>          Table 1
>
> [to]
>
>       *  This test uses bottleneck path capacity variation as listed in
>          Table 1.
>
>          - In 5.1a, the path capacity transitions are achieved by 
> instantly changing the
>            physical throughput of the bottleneck link. For simplicity, 
> when changing
>            the bottleneck link throughput, other parameters such as 
> queue length in
>            packets will be left unchanged, even if it implies that the 
> new queue has a
>            different length in milliseconds.
>
>          - In 5.1b, the path capacity transitions are achieved by 
> instantly changing the
>            sending bitrate of the competing CBR flow. The new sending 
> bitrate must be
>            the difference between the bottleneck link-capacity (4 
> Mbps, as specified in
>            4.2) and the capacity specified in Table 1.
>
>            The sharp bitrate change in the CBR flow might imply the 
> losses on both the
>            application-related traffic and the CBR flow. As a result, 
> the reaction of
>            the candidate algorithm might be different in 5.1a and in 
> 5.1b, hence the
>            distinction between the two sub-cases.
>
>
> ===========
> Section 5.2
> ===========
>
> [Insert this after the first paragraph of the section]
>
> Analogously to Section 5.1, the present test case (5.2) is divided 
> into two subcases 5.2a and 5.2b.
> The main difference is the same: 5.2a simulates a change in the 
> underlying physical network properties,
> such as routing change or interface change; whereas 5.2b simulates a 
> sharp change in background
> competing traffic.
>
> ---
>
> [Change last paragraph from]
>
>    Test Specific Information: This test uses path capacity variation as
>    listed in Table 2 with a corresponding end time of 125 seconds.
>
> [to]
>
>    Test Specific Information: This test uses path capacity variation as
>    listed in Table 2 with a corresponding end time of 125 seconds. The
>    two media flows stop at time 124.
>


--------------020901000507010808090702
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      Hi Zahed,<br>
      <br>
      First of all, your question. By "insensitive traffic" I meant that
      the flow is CBR, so it won't back off whether other traffic is
      present in the bottleneck link or not. Maybe we can find a better
      name for this...<br>
      <br>
      On the other hand, in the last days, I have been working on an ns3
      implementation of some of the test cases in the draft. I realized
      that it would be coherent (and useful, IMO) for 5.3 to also have a
      "b" version where both forward and backward paths are changed by a
      CBR, similarly to 5.1 and 5.2. Let me know your thoughts on this.<br>
      <br>
      Regards,<br>
      <br>
      Sergio<br>
      <br>
      <br>
      <br>
      On 24/08/15 13:45, Zaheduzzaman Sarker wrote:<br>
    </div>
    <blockquote
cite="mid:E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="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";
	color:black;}
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-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi
            Sergio,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks
            for your effort.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
            think the proposed changes looks good.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">As
            we have plan to update the variation of path capacity
            relative to initial path capacity for test case 5.1 and test
            case 5.2, we need to change the respective text in the 5.1b
            and 5.2b to be aligned with that.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">One
            clarification question : in 5.1b what does the “insensitive
            traffic” means in the new text?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">BR<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Zahed<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                  Sergio Mena [<a class="moz-txt-link-freetext" href="mailto:semena@cisco.com">mailto:semena@cisco.com</a>]
                  <br>
                  <b>Sent:</b> den 13 augusti 2015 14:30<br>
                  <b>To:</b> Zaheduzzaman Sarker<br>
                  <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-rmcat-eval-test@ietf.org">draft-ietf-rmcat-eval-test@ietf.org</a>;
                  <a class="moz-txt-link-abbreviated" href="mailto:rmcat@ietf.org">rmcat@ietf.org</a><br>
                  <b>Subject:</b> Sections 5.1 and 5.2 of
                  draft-ietf-rmcat-eval-test-01<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt">Zahed,<br>
            <br>
            <i>[CCed the author list of the rmcat test cases draft, as
              well as the rmcat mailing list]</i><br>
            <br>
            There was a discussion triggered at rmcat main session in
            Prague on how to simulate bottleneck-link bandwidth changes.
            Two options were discussed (1) changing the physical link
            throughput (currently specified in the draft), and (2) using
            an insensitive CBR UDP flow as background traffic.<br>
            <br>
            My understanding from the discussion during the session was
            that none of these two options can simulate the other and,
            therefore, we somehow need to test how candidate algorithms
            adapt in both cases.<br>
            <br>
            You and I then had an offline discussion on the subject in
            which you suggested me to review sections 5.1 and 5.2 of the
            test cases draft, and propose an alternate text to extend
            these two test cases to the background traffic option.<br>
            <br>
            I have reviewed sections 5.1 and 5.2 and come up with a
            proposal for extending them to using insensitive background
            traffic, in addition to the current option in the text
            (physical link throughput change).<br>
            <br>
            Please find below what I would like to propose as updated
            text for 5.1 and 5.2. [Text in square brackets are
            instructions to locate and replace the original text].<br>
            <br>
            Thanks,<br>
            <br>
            Sergio Mena<br>
            <br>
            <br>
            PS Proposed changes:<br>
            <br>
            ===========<br>
            Section 5.1<br>
            ===========<br>
            <br>
            [In the three-bullet list after the first paragraph, change
            the text in the second bullet from:]<br>
            <br>
                o change in available capacity (e.g., due to interface
            change,<br>
                  routing change).<br>
            <br>
            [to]<br>
            <br>
                o change in available capacity (e.g., due to interface
            change,<br>
                  routing change, sharp change in background traffic).<br>
            <br>
            ---<br>
            <br>
            [Replace the paragraph immediately after the three-bullet
            list mentioned above, the one that starts with]<br>
            <br>
            It should be noted that the exact variation...<br>
            <br>
            [with the following]<br>
            <br>
            The test case defined in this section (5.1) is divided into
            two subcases 5.1a and 5.1b. The main<br>
            difference is how the bottleneck-link capacity is changed in
            the testbed. In 5.1a, the goal is to<br>
            simulate a modification in the underlying physical
            properties, such as routing change or interface<br>
            change. In 5.1b, the goal is to simulate a sharp change in
            background traffic to which the candidate<br>
            algorithm is to adapt.<br>
            <br>
            ---<br>
            <br>
            [Change the last item of testbed attributes from]<br>
            <br>
                  *  Competing traffic:<br>
            <br>
                     +  Number of sources : Zero (0)<br>
            <br>
            [to]<br>
            <br>
                  *  Competing traffic:<br>
            <br>
                     +  In 5.1a<br>
            <br>
                        - Number of sources : Zero (0)<br>
            <br>
                     +  In 5.1b<br>
            <br>
                        - Number of sources : One (1)<br>
            <br>
                        - Type of sources : CBR traffic <br>
            <br>
                        - Sending bitrate : See test specific
            information below.<br>
            <br>
                        - Traffic direction : Forward<br>
            <br>
                        - Congestion control : None (insensitive
            traffic)<br>
            <br>
                        - Traffic timeline:<br>
            <br>
                          - Start time : 0s<br>
            <br>
                          - End time : 100s<br>
            <br>
            ---<br>
            <br>
            [Change 2nd bullet of test-specific information from]<br>
            <br>
                  *  This test uses bottleneck path capacity variation
            as listed in<br>
                     Table 1<br>
            <br>
            [to]<br>
            <br>
                  *  This test uses bottleneck path capacity variation
            as listed in<br>
                     Table 1.<br>
            <br>
                     - In 5.1a, the path capacity transitions are
            achieved by instantly changing the
            <br>
                       physical throughput of the bottleneck link. For
            simplicity, when changing<br>
                       the bottleneck link throughput, other parameters
            such as queue length in
            <br>
                       packets will be left unchanged, even if it
            implies that the new queue has a
            <br>
                       different length in milliseconds.<br>
            <br>
                     - In 5.1b, the path capacity transitions are
            achieved by instantly changing the<br>
                       sending bitrate of the competing CBR flow. The
            new sending bitrate must be<br>
                       the difference between the bottleneck
            link-capacity (4 Mbps, as specified in
            <br>
                       4.2) and the capacity specified in Table 1.<br>
            <br>
                       The sharp bitrate change in the CBR flow might
            imply the losses on both the<br>
                       application-related traffic and the CBR flow. As
            a result, the reaction of<br>
                       the candidate algorithm might be different in
            5.1a and in 5.1b, hence the<br>
                       distinction between the two sub-cases.<br>
            <br>
            <br>
            ===========<br>
            Section 5.2<br>
            ===========<br>
            <br>
            [Insert this after the first paragraph of the section]<br>
            <br>
            Analogously to Section 5.1, the present test case (5.2) is
            divided into two subcases 5.2a and 5.2b.<br>
            The main difference is the same: 5.2a simulates a change in
            the underlying physical network properties,<br>
            such as routing change or interface change; whereas 5.2b
            simulates a sharp change in background<br>
            competing traffic.<br>
            <br>
            ---<br>
            <br>
            [Change last paragraph from]<br>
            <br>
               Test Specific Information: This test uses path capacity
            variation as<br>
               listed in Table 2 with a corresponding end time of 125
            seconds.<br>
            <br>
            [to]<br>
            <br>
               Test Specific Information: This test uses path capacity
            variation as<br>
               listed in Table 2 with a corresponding end time of 125
            seconds. The<br>
               two media flows stop at time 124.<o:p></o:p></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------020901000507010808090702--


From nobody Wed Aug 26 08:08:34 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 3ECFF1A8AEE; Wed, 26 Aug 2015 08:08:33 -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 Vpzl7QKmookv; Wed, 26 Aug 2015 08:08:30 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 274871A8AE0; Wed, 26 Aug 2015 08:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23341; q=dns/txt; s=iport; t=1440601710; x=1441811310; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=sXIZgNdrW1GRu2DTYnbftVehB3Vx0ai2fY4q/GNilro=; b=aDR3PIicoLeCyxgF5iaTQtThRPWIYSXKiqIc8rW88oVj7Ss0eV4oZ5vr QGZUktEBAxf8jsPP5Yqe4b40bGeo/7krBrBS9eLhmROm01HmjTz4Fs2/s ozUk+wOLgFiLQr7+z4/aqH0NfshWi/d/wfJmBFwnFmG7IV54TVUU2V3yJ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CIAgB51d1V/4QNJK1dgk5NgT0GvWIBCYZjgRACgTo4FAEBAQEBAQGBCoQjAQEBBC1BCxACAQgRAwEBASgHMhQJCAIEAQ0FiC7IegEBAQEBAQEBAQEBAQEBAQEBAQEBAReKWIEDhHkRBgGELAWMa4U2gxYBjHGBSoQyjCyESYNqJoN+cYFIgQQBAQE
X-IronPort-AV: E=Sophos; i="5.17,416,1437436800"; d="scan'208,217"; a="21786424"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-9.cisco.com with ESMTP; 26 Aug 2015 15:08:29 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t7QF8T5S009633 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 26 Aug 2015 15:08:29 GMT
Received: from xch-rcd-014.cisco.com (173.37.102.24) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 26 Aug 2015 10:08:28 -0500
Received: from xhc-rcd-x05.cisco.com (173.37.183.79) by xch-rcd-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Wed, 26 Aug 2015 10:08:28 -0500
Received: from xmb-rcd-x01.cisco.com ([169.254.1.191]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0248.002; Wed, 26 Aug 2015 10:08:28 -0500
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: "Sergio Mena de la Cruz (semena)" <semena@cisco.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Thread-Topic: Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01
Thread-Index: AQHQ1cPMOMHy7axU30OV0G2Tiz2fRp4bbSGAgALewoCAACqyAA==
Date: Wed, 26 Aug 2015 15:08:27 +0000
Message-ID: <D2032394.25D91%xiaoqzhu@cisco.com>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se> <55DD6C49.1050901@cisco.com>
In-Reply-To: <55DD6C49.1050901@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.4.150722
x-originating-ip: [173.37.102.30]
Content-Type: multipart/alternative; boundary="_000_D203239425D91xiaoqzhuciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/Bf08zNzkutm4ithKU6EMtcR_grs>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 26 Aug 2015 15:08:33 -0000

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

I concur with Sergio=92s suggestions.

One thought: instead of stating variation within each sub-section, we can s=
tate that there exists two options of changing bandwidth in the beginning o=
f Sec 5. This will also be consistent with the option/flexibility we now of=
fer for folks to pick different initial capacities and scale rest of the BW=
 values accordingly.

Best,
Xiaoqing


From: "Sergio Mena de la Cruz (semena)" <semena@cisco.com<mailto:semena@cis=
co.com>>
Date: Wednesday, August 26, 2015 at 12:35 AM
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com<mailto:zaheduzzam=
an.sarker@ericsson.com>>
Cc: "draft-ietf-rmcat-eval-test@ietf.org<mailto:draft-ietf-rmcat-eval-test@=
ietf.org>" <draft-ietf-rmcat-eval-test@ietf.org<mailto:draft-ietf-rmcat-eva=
l-test@ietf.org>>, "rmcat@ietf.org<mailto:rmcat@ietf.org>" <rmcat@ietf.org<=
mailto:rmcat@ietf.org>>
Subject: Re: Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01


Hi Zahed,

First of all, your question. By "insensitive traffic" I meant that the flow=
 is CBR, so it won't back off whether other traffic is present in the bottl=
eneck link or not. Maybe we can find a better name for this...

On the other hand, in the last days, I have been working on an ns3 implemen=
tation of some of the test cases in the draft. I realized that it would be =
coherent (and useful, IMO) for 5.3 to also have a "b" version where both fo=
rward and backward paths are changed by a CBR, similarly to 5.1 and 5.2. Le=
t me know your thoughts on this.

Regards,

Sergio



On 24/08/15 13:45, Zaheduzzaman Sarker wrote:
Hi Sergio,

Thanks for your effort.

I think the proposed changes looks good.

As we have plan to update the variation of path capacity relative to initia=
l path capacity for test case 5.1 and test case 5.2, we need to change the =
respective text in the 5.1b and 5.2b to be aligned with that.

One clarification question : in 5.1b what does the =93insensitive traffic=
=94 means in the new text?

BR

Zahed

From: Sergio Mena [mailto:semena@cisco.com]
Sent: den 13 augusti 2015 14:30
To: Zaheduzzaman Sarker
Cc: draft-ietf-rmcat-eval-test@ietf.org<mailto:draft-ietf-rmcat-eval-test@i=
etf.org>; rmcat@ietf.org<mailto:rmcat@ietf.org>
Subject: Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01

Zahed,

[CCed the author list of the rmcat test cases draft, as well as the rmcat m=
ailing list]

There was a discussion triggered at rmcat main session in Prague on how to =
simulate bottleneck-link bandwidth changes. Two options were discussed (1) =
changing the physical link throughput (currently specified in the draft), a=
nd (2) using an insensitive CBR UDP flow as background traffic.

My understanding from the discussion during the session was that none of th=
ese two options can simulate the other and, therefore, we somehow need to t=
est how candidate algorithms adapt in both cases.

You and I then had an offline discussion on the subject in which you sugges=
ted me to review sections 5.1 and 5.2 of the test cases draft, and propose =
an alternate text to extend these two test cases to the background traffic =
option.

I have reviewed sections 5.1 and 5.2 and come up with a proposal for extend=
ing them to using insensitive background traffic, in addition to the curren=
t option in the text (physical link throughput change).

Please find below what I would like to propose as updated text for 5.1 and =
5.2. [Text in square brackets are instructions to locate and replace the or=
iginal text].

Thanks,

Sergio Mena


PS Proposed changes:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Section 5.1
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[In the three-bullet list after the first paragraph, change the text in the=
 second bullet from:]

    o change in available capacity (e.g., due to interface change,
      routing change).

[to]

    o change in available capacity (e.g., due to interface change,
      routing change, sharp change in background traffic).

---

[Replace the paragraph immediately after the three-bullet list mentioned ab=
ove, the one that starts with]

It should be noted that the exact variation...

[with the following]

The test case defined in this section (5.1) is divided into two subcases 5.=
1a and 5.1b. The main
difference is how the bottleneck-link capacity is changed in the testbed. I=
n 5.1a, the goal is to
simulate a modification in the underlying physical properties, such as rout=
ing change or interface
change. In 5.1b, the goal is to simulate a sharp change in background traff=
ic to which the candidate
algorithm is to adapt.

---

[Change the last item of testbed attributes from]

      *  Competing traffic:

         +  Number of sources : Zero (0)

[to]

      *  Competing traffic:

         +  In 5.1a

            - Number of sources : Zero (0)

         +  In 5.1b

            - Number of sources : One (1)

            - Type of sources : CBR traffic

            - Sending bitrate : See test specific information below.

            - Traffic direction : Forward

            - Congestion control : None (insensitive traffic)

            - Traffic timeline:

              - Start time : 0s

              - End time : 100s

---

[Change 2nd bullet of test-specific information from]

      *  This test uses bottleneck path capacity variation as listed in
         Table 1

[to]

      *  This test uses bottleneck path capacity variation as listed in
         Table 1.

         - In 5.1a, the path capacity transitions are achieved by instantly=
 changing the
           physical throughput of the bottleneck link. For simplicity, when=
 changing
           the bottleneck link throughput, other parameters such as queue l=
ength in
           packets will be left unchanged, even if it implies that the new =
queue has a
           different length in milliseconds.

         - In 5.1b, the path capacity transitions are achieved by instantly=
 changing the
           sending bitrate of the competing CBR flow. The new sending bitra=
te must be
           the difference between the bottleneck link-capacity (4 Mbps, as =
specified in
           4.2) and the capacity specified in Table 1.

           The sharp bitrate change in the CBR flow might imply the losses =
on both the
           application-related traffic and the CBR flow. As a result, the r=
eaction of
           the candidate algorithm might be different in 5.1a and in 5.1b, =
hence the
           distinction between the two sub-cases.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Section 5.2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[Insert this after the first paragraph of the section]

Analogously to Section 5.1, the present test case (5.2) is divided into two=
 subcases 5.2a and 5.2b.
The main difference is the same: 5.2a simulates a change in the underlying =
physical network properties,
such as routing change or interface change; whereas 5.2b simulates a sharp =
change in background
competing traffic.

---

[Change last paragraph from]

   Test Specific Information: This test uses path capacity variation as
   listed in Table 2 with a corresponding end time of 125 seconds.

[to]

   Test Specific Information: This test uses path capacity variation as
   listed in Table 2 with a corresponding end time of 125 seconds. The
   two media flows stop at time 124.


--_000_D203239425D91xiaoqzhuciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A6B9F9ADE8BC7A4B9D55AF0889B7EB3F@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>I concur with Sergio=92s suggestions. &nbsp;&nbsp;</div>
<div><br>
</div>
<div>One thought: instead of stating variation within each sub-section, we =
can state that there exists two options of changing bandwidth in the beginn=
ing of Sec 5. This will also be consistent with the option/flexibility we n=
ow offer for folks to pick different
 initial capacities and scale rest of the BW values accordingly.&nbsp;</div=
>
<div><br>
</div>
<div>Best,</div>
<div>Xiaoqing</div>
<div><br>
</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>&quot;Sergio Mena de la Cruz =
(semena)&quot; &lt;<a href=3D"mailto:semena@cisco.com">semena@cisco.com</a>=
&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, August 26, 2015 at=
 12:35 AM<br>
<span style=3D"font-weight:bold">To: </span>Zaheduzzaman Sarker &lt;<a href=
=3D"mailto:zaheduzzaman.sarker@ericsson.com">zaheduzzaman.sarker@ericsson.c=
om</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:draft-i=
etf-rmcat-eval-test@ietf.org">draft-ietf-rmcat-eval-test@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:draft-ietf-rmcat-eval-test@ietf.org">draft-ietf-rmca=
t-eval-test@ietf.org</a>&gt;, &quot;<a href=3D"mailto:rmcat@ietf.org">rmcat=
@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:rmcat@ietf.org">rmcat@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Sections 5.1 and 5.2 o=
f draft-ietf-rmcat-eval-test-01<br>
</div>
<div><br>
</div>
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<div class=3D"moz-cite-prefix"><br>
Hi Zahed,<br>
<br>
First of all, your question. By &quot;insensitive traffic&quot; I meant tha=
t the flow is CBR, so it won't back off whether other traffic is present in=
 the bottleneck link or not. Maybe we can find a better name for this...<br=
>
<br>
On the other hand, in the last days, I have been working on an ns3 implemen=
tation of some of the test cases in the draft. I realized that it would be =
coherent (and useful, IMO) for 5.3 to also have a &quot;b&quot; version whe=
re both forward and backward paths are changed
 by a CBR, similarly to 5.1 and 5.2. Let me know your thoughts on this.<br>
<br>
Regards,<br>
<br>
Sergio<br>
<br>
<br>
<br>
On 24/08/15 13:45, Zaheduzzaman Sarker wrote:<br>
</div>
<blockquote cite=3D"mid:E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307=
.ericsson.se" type=3D"cite">
<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";
	color:black;}
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-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Hi Sergio,<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);">Thanks for your effort.<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);">I think the proposed changes looks =
good.<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);">As we have plan to update the varia=
tion of path capacity relative to initial path capacity for test case 5.1 a=
nd test case 5.2, we need to change
 the respective text in the 5.1b and 5.2b to be aligned with that.<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);">One clarification question : in 5.1=
b what does the =93insensitive traffic=94 means in the new text?<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; color: windowtext;">From:</span></b><span style=3D"font-siz=
e: 10pt; font-family: Tahoma, sans-serif; color: windowtext;"> Sergio Mena =
[<a class=3D"moz-txt-link-freetext" href=3D"mailto:semena@cisco.com">mailto=
:semena@cisco.com</a>]
<br>
<b>Sent:</b> den 13 augusti 2015 14:30<br>
<b>To:</b> Zaheduzzaman Sarker<br>
<b>Cc:</b> <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:draft-ietf-=
rmcat-eval-test@ietf.org">
draft-ietf-rmcat-eval-test@ietf.org</a>; <a class=3D"moz-txt-link-abbreviat=
ed" href=3D"mailto:rmcat@ietf.org">
rmcat@ietf.org</a><br>
<b>Subject:</b> Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-01<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Zahed,<br>
<br>
<i>[CCed the author list of the rmcat test cases draft, as well as the rmca=
t mailing list]</i><br>
<br>
There was a discussion triggered at rmcat main session in Prague on how to =
simulate bottleneck-link bandwidth changes. Two options were discussed (1) =
changing the physical link throughput (currently specified in the draft), a=
nd (2) using an insensitive CBR
 UDP flow as background traffic.<br>
<br>
My understanding from the discussion during the session was that none of th=
ese two options can simulate the other and, therefore, we somehow need to t=
est how candidate algorithms adapt in both cases.<br>
<br>
You and I then had an offline discussion on the subject in which you sugges=
ted me to review sections 5.1 and 5.2 of the test cases draft, and propose =
an alternate text to extend these two test cases to the background traffic =
option.<br>
<br>
I have reviewed sections 5.1 and 5.2 and come up with a proposal for extend=
ing them to using insensitive background traffic, in addition to the curren=
t option in the text (physical link throughput change).<br>
<br>
Please find below what I would like to propose as updated text for 5.1 and =
5.2. [Text in square brackets are instructions to locate and replace the or=
iginal text].<br>
<br>
Thanks,<br>
<br>
Sergio Mena<br>
<br>
<br>
PS Proposed changes:<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Section 5.1<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
[In the three-bullet list after the first paragraph, change the text in the=
 second bullet from:]<br>
<br>
&nbsp;&nbsp;&nbsp; o change in available capacity (e.g., due to interface c=
hange,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; routing change).<br>
<br>
[to]<br>
<br>
&nbsp;&nbsp;&nbsp; o change in available capacity (e.g., due to interface c=
hange,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; routing change, sharp change in background t=
raffic).<br>
<br>
---<br>
<br>
[Replace the paragraph immediately after the three-bullet list mentioned ab=
ove, the one that starts with]<br>
<br>
It should be noted that the exact variation...<br>
<br>
[with the following]<br>
<br>
The test case defined in this section (5.1) is divided into two subcases 5.=
1a and 5.1b. The main<br>
difference is how the bottleneck-link capacity is changed in the testbed. I=
n 5.1a, the goal is to<br>
simulate a modification in the underlying physical properties, such as rout=
ing change or interface<br>
change. In 5.1b, the goal is to simulate a sharp change in background traff=
ic to which the candidate<br>
algorithm is to adapt.<br>
<br>
---<br>
<br>
[Change the last item of testbed attributes from]<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; Competing traffic:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;&nbsp; Number of sour=
ces : Zero (0)<br>
<br>
[to]<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; Competing traffic:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;&nbsp; In 5.1a<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Number=
 of sources : Zero (0)<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;&nbsp; In 5.1b<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Number=
 of sources : One (1)<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Type o=
f sources : CBR traffic <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Sendin=
g bitrate : See test specific information below.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Traffi=
c direction : Forward<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Conges=
tion control : None (insensitive traffic)<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Traffi=
c timeline:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; - Start time : 0s<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; - End time : 100s<br>
<br>
---<br>
<br>
[Change 2nd bullet of test-specific information from]<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; This test uses bottleneck path capac=
ity variation as listed in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1<br>
<br>
[to]<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; This test uses bottleneck path capac=
ity variation as listed in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 1.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - In 5.1a, the path capaci=
ty transitions are achieved by instantly changing the
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; physical throu=
ghput of the bottleneck link. For simplicity, when changing<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the bottleneck=
 link throughput, other parameters such as queue length in
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; packets will b=
e left unchanged, even if it implies that the new queue has a
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; different leng=
th in milliseconds.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - In 5.1b, the path capaci=
ty transitions are achieved by instantly changing the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sending bitrat=
e of the competing CBR flow. The new sending bitrate must be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the difference=
 between the bottleneck link-capacity (4 Mbps, as specified in
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4.2) and the c=
apacity specified in Table 1.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The sharp bitr=
ate change in the CBR flow might imply the losses on both the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application-re=
lated traffic and the CBR flow. As a result, the reaction of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the candidate =
algorithm might be different in 5.1a and in 5.1b, hence the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; distinction be=
tween the two sub-cases.<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Section 5.2<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
[Insert this after the first paragraph of the section]<br>
<br>
Analogously to Section 5.1, the present test case (5.2) is divided into two=
 subcases 5.2a and 5.2b.<br>
The main difference is the same: 5.2a simulates a change in the underlying =
physical network properties,<br>
such as routing change or interface change; whereas 5.2b simulates a sharp =
change in background<br>
competing traffic.<br>
<br>
---<br>
<br>
[Change last paragraph from]<br>
<br>
&nbsp;&nbsp; Test Specific Information: This test uses path capacity variat=
ion as<br>
&nbsp;&nbsp; listed in Table 2 with a corresponding end time of 125 seconds=
.<br>
<br>
[to]<br>
<br>
&nbsp;&nbsp; Test Specific Information: This test uses path capacity variat=
ion as<br>
&nbsp;&nbsp; listed in Table 2 with a corresponding end time of 125 seconds=
. The<br>
&nbsp;&nbsp; two media flows stop at time 124.<o:p></o:p></p>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</span>
</body>
</html>

--_000_D203239425D91xiaoqzhuciscocom_--


From nobody Thu Aug 27 01:43:01 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 80C0F1B2EE4; Thu, 27 Aug 2015 01:43:00 -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 CHYg3y8cqvhM; Thu, 27 Aug 2015 01:42:59 -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 6365D1B382D; Thu, 27 Aug 2015 01:42:58 -0700 (PDT)
X-AuditID: c1b4fb25-f79a26d00000149a-1f-55decd9037b6
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id D6.69.05274.09DCED55; Thu, 27 Aug 2015 10:42:56 +0200 (CEST)
Received: from [150.132.141.68] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.50) with Microsoft SMTP Server id 14.3.210.2; Thu, 27 Aug 2015 10:42:55 +0200
To: Sergio Mena <semena@cisco.com>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se> <55DD6C49.1050901@cisco.com>
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Organization: Ericsson AB
Message-ID: <55DECD8F.3070500@ericsson.com>
Date: Thu, 27 Aug 2015 10:42:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55DD6C49.1050901@cisco.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvje6Es/dCDX7sk7SYeP8su8Xqmx/Y LNZM/8buwOwx5fdGVo8lS34yBTBFcdmkpOZklqUW6dslcGVM3yJTME+o4sGBduYGxl18XYyc HBICJhIH1m9gh7DFJC7cW8/WxcjFISRwlFFiw7keFghnDaPE5o89YFXCAk4STXMWsoDYIgJK Es2XHzFCFHUySiz5tYu1i5GDg1mgROLOySwQk03ARuLxYj+Qcn4BSYkNDbuZQWxeAW2J7+vX MoLYLAKqEjuubAMbKSoQIzF/xXSoGkGJkzOfgMU5BTQluicvZAOxmQUsJGbOP88IYctLNG+d zQyySkhAV6LrZdwERqFZSLpnIemYhaRjASPzKkbR4tTipNx0I2O91KLM5OLi/Dy9vNSSTYzA YD645bfqDsbLbxwPMQpwMCrx8Crk3wsVYk0sK67MPcQozcGiJM774hRQSCA9sSQ1OzW1ILUo vqg0J7X4ECMTB6dUAyPPr7ZYfyO+nE39/PeE7Hs0nz8/zad35aH/t+WvdF6fKp5Vwql0Xej+ j7qDX+5uvbSMJ7ZJe1vz2S/r3wg1rfhjdL+igeuhx++tDKyzFkSXtZyWjzjqMkNjdXZXr4J8 G4vc8pZJhr+lj175lG48Z3pNP9ef736nHijyz/NgX8Tx4/BZZevioC1KLMUZiYZazEXFiQD/ zfG+RwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/geBXJ3uupMI4xSnUHR7UPmRYfc0>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 27 Aug 2015 08:43:00 -0000

On 2015-08-26 09:35, Sergio Mena wrote:
>
> Hi Zahed,
>
> First of all, your question. By "insensitive traffic" I meant that the
> flow is CBR, so it won't back off whether other traffic is present in
> the bottleneck link or not. Maybe we can find a better name for this...
ok, understood. To me "flow is CBR" is good enough.
>
> On the other hand, in the last days, I have been working on an ns3
> implementation of some of the test cases in the draft. I realized that
> it would be coherent (and useful, IMO) for 5.3 to also have a "b"
> version where both forward and backward paths are changed by a CBR,
> similarly to 5.1 and 5.2. Let me know your thoughts on this.
is it possible to share your findings so that we can also have a look at 
the characteristics the new test option (path capacity limitation by 
introducing CBR) is revealing (applicable for 5.1 and 5.2 as well)? I 
think it is better to discuss and learn more about the test case 
characteristics before we add the new option.

For test case 5.3, it is important that the path capacity change in the 
backward path happens at the right time so that we can see the effect of 
lost or delayed feedback in the forward path. have you seen any change 
required at the time one need to start the CBR traffic to introduce the 
capacity change at correct time? How easy will it be to do this in a lab 
network?

For 5.1, 5.2 (and 5.3), how do you introduce the competing CBR traffic? 
if there is a single bottleneck node between A and B then the competing 
CBR traffic can share the same path as the media traffic. However, if 
there are multiple nodes between A and B (can happen in the lab 
network), then sharing the same path can create multiple bottlenecks, 
right? I haven't tried that yet. Even if that is the case then I think 
this can be solved by some additional text in the draft but it will 
require different topology than the current assumptions.

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 Thu Aug 27 01:48:28 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 6054D1B34F3; Thu, 27 Aug 2015 01:48:20 -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 wNZCqJ7POD66; Thu, 27 Aug 2015 01:48:17 -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 7FA5B1B3294; Thu, 27 Aug 2015 01:48:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 1EE95D9316; Thu, 27 Aug 2015 10:48:16 +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 yBcJKiDzfQek; Thu, 27 Aug 2015 10:48:15 +0200 (MEST)
Received: from [192.168.220.145] (178-83-155-34.dynamic.hispeed.ch [178.83.155.34]) (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 B94DFD9310; Thu, 27 Aug 2015 10:48:15 +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: <55DECD8F.3070500@ericsson.com>
Date: Thu, 27 Aug 2015 10:48:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <79DC7E74-132C-4055-BD4D-46EB2ABEB2F5@tik.ee.ethz.ch>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se> <55DD6C49.1050901@cisco.com> <55DECD8F.3070500@ericsson.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/eKRIS77rJ5xN0Je86qiq3z5wIS4>
Cc: Sergio Mena <semena@cisco.com>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 27 Aug 2015 08:48:20 -0000

Hi all,

just a quick thought in addition (as an individual): if you use CBR =
cross traffic, it would potentially also be interesting to add another =
evaluation metric and that=E2=80=99s the loss rate of the CBR traffic =
because this tells you how 'aggressive' your impact on cross traffic is.

Mirja


> Am 27.08.2015 um 10:42 schrieb Zaheduzzaman Sarker =
<zaheduzzaman.sarker@ericsson.com>:
>=20
>=20
>=20
> On 2015-08-26 09:35, Sergio Mena wrote:
>>=20
>> Hi Zahed,
>>=20
>> First of all, your question. By "insensitive traffic" I meant that =
the
>> flow is CBR, so it won't back off whether other traffic is present in
>> the bottleneck link or not. Maybe we can find a better name for =
this...
> ok, understood. To me "flow is CBR" is good enough.
>>=20
>> On the other hand, in the last days, I have been working on an ns3
>> implementation of some of the test cases in the draft. I realized =
that
>> it would be coherent (and useful, IMO) for 5.3 to also have a "b"
>> version where both forward and backward paths are changed by a CBR,
>> similarly to 5.1 and 5.2. Let me know your thoughts on this.
> is it possible to share your findings so that we can also have a look =
at the characteristics the new test option (path capacity limitation by =
introducing CBR) is revealing (applicable for 5.1 and 5.2 as well)? I =
think it is better to discuss and learn more about the test case =
characteristics before we add the new option.
>=20
> For test case 5.3, it is important that the path capacity change in =
the backward path happens at the right time so that we can see the =
effect of lost or delayed feedback in the forward path. have you seen =
any change required at the time one need to start the CBR traffic to =
introduce the capacity change at correct time? How easy will it be to do =
this in a lab network?
>=20
> For 5.1, 5.2 (and 5.3), how do you introduce the competing CBR =
traffic? if there is a single bottleneck node between A and B then the =
competing CBR traffic can share the same path as the media traffic. =
However, if there are multiple nodes between A and B (can happen in the =
lab network), then sharing the same path can create multiple =
bottlenecks, right? I haven't tried that yet. Even if that is the case =
then I think this can be solved by some additional text in the draft but =
it will require different topology than the current assumptions.
>=20
> BR
> --=20
> Zahed
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=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
>=20
>=20
> 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
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=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 Aug 27 03:51:46 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 87FD71B3B93; Thu, 27 Aug 2015 03:51:44 -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 HQrP6RI2E22R; Thu, 27 Aug 2015 03:51:43 -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 77CEC1B3B95; Thu, 27 Aug 2015 03:51:42 -0700 (PDT)
X-AuditID: c1b4fb2d-f79626d000004282-f9-55deebbc02b4
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id E1.3F.17026.CBBEED55; Thu, 27 Aug 2015 12:51:40 +0200 (CEST)
Received: from [150.132.141.68] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.210.2; Thu, 27 Aug 2015 12:51:39 +0200
To: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se> <55DD6C49.1050901@cisco.com> <55DECD8F.3070500@ericsson.com> <79DC7E74-132C-4055-BD4D-46EB2ABEB2F5@tik.ee.ethz.ch>
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Organization: Ericsson AB
Message-ID: <55DEEBBC.5080300@ericsson.com>
Date: Thu, 27 Aug 2015 12:51:40 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <79DC7E74-132C-4055-BD4D-46EB2ABEB2F5@tik.ee.ethz.ch>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvje6e1/dCDTb9M7GYeP8su8WG1VNY LFbf/MBmsWb6N3YHFo8pvzeyeixZ8pPJ49iHr2wBzFFcNimpOZllqUX6dglcGU8mbmIpOM5W MX9OO1sD41LWLkZODgkBE4mD3ddYIGwxiQv31rN1MXJxCAkcZZQ4OWUhO4SzhlHiTdcbsCph AS+Jfd3HmEFsEQE3iXmr1rNCFD1klJh7cyNYO7PAFEaJ/fNPM3UxcnCwCdhIPF7sB9LALyAp saFhN1gzr4C2xNkdF9hBbBYBVYmJBxaDxUUFYiTmr5gOVSMocXLmE7DFnAJOEhsaz4OdzSxg ITFz/nlGCFteonnrbGaQVUICuhJdL+MmMArNQtI9C0nHLCQdCxiZVzGKFqcWF+emGxnrpRZl JhcX5+fp5aWWbGIEhvnBLb91dzCufu14iFGAg1GJh1ch/16oEGtiWXFl7iFGaQ4WJXHeM9eB QgLpiSWp2ampBalF8UWlOanFhxiZODilGhiXRUw5/Kvg+DM7hUtpq5Ve11wo+vmfo69nq/EB Hf0iTt8jgUp/pZb/CmW84n3jiGVNY6Hv2v+xs/PcXeteBF67cJFNqfNrhlQRx6ybBxefDrC5 9Uol9+L/V/l+Up5hW6RmfJpno21XcmjFSYGDsQXLjjze/3Sh8YWtNQk2k8JnTzbf//R4Xrys EktxRqKhFnNRcSIAPePSSFQCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/bnFJsYmx1XIw_Y-2qzflNBMqanQ>
Cc: Sergio Mena <semena@cisco.com>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 27 Aug 2015 10:51:44 -0000

On 2015-08-27 10:48, Mirja Kühlewind wrote:
> Hi all,
>
> just a quick thought in addition (as an individual): if you use CBR
> cross traffic, it would potentially also be interesting to add
> another evaluation metric and that’s the loss rate of the CBR traffic
> because this tells you how 'aggressive' your impact on cross traffic
> is.
I think this is a very good point. Along with loss rate we might want to 
look at the goodput of the CBR traffic.

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 Thu Aug 27 05:05:27 2015
Return-Path: <semena@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 2F2841B2CF0; Thu, 27 Aug 2015 05:05:25 -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 W5LWm2yQXkJI; Thu, 27 Aug 2015 05:05:18 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4B431B2CDB; Thu, 27 Aug 2015 05:05:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10836; q=dns/txt; s=iport; t=1440677119; x=1441886719; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=TPTf35UBGnd/wP+QZwb1GpX4Pi8qr7+I6jHBEH4ryak=; b=jcXHSxXeACATXp+TD6Jm14bJVmnVnJBZyYMxk9MZy6bxDhOwZlPZ//pf NvdDWzxuF9VTeROzT7BpBABdqVHB/SUakb3z9jWGwZxCgdTp0mf047c3R Y6LbM0UjCz0F6N6lTHdgvhOjcXd1oIXNL1k67OJ1U4BmDT2fCN2WWwVW6 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BzAgAD/N5V/xbLJq1dh3u6VAEJhRuBSIEQAoFrFAEBAQEBAQGBCoQjAQEBAwEjSwoBEAsYCRYLAgIJAwIBAgFFBg0IAQEViA0Isx+VDwEBAQEBAQEBAgEBAQEBAQEBARmLYYQzWAeCaYFDAQSMbIhRhy5FhQCBSoQygnuNfoNrJoIMAxyBVjyBOYFHAQEB
X-IronPort-AV: E=Sophos;i="5.17,422,1437436800";  d="scan'208,217";a="629347184"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 27 Aug 2015 12:05:16 +0000
Received: from [10.0.2.15] ([10.148.51.67]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t7RC5Fh7027270; Thu, 27 Aug 2015 12:05:15 GMT
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
References: <55CC8DC7.40903@cisco.com> <E0F7A68B07B53F4FBD12DABD61CBA90E129E89A2@ESESSMB307.ericsson.se> <55DD6C49.1050901@cisco.com> <55DECD8F.3070500@ericsson.com>
From: Sergio Mena <semena@cisco.com>
Message-ID: <55DEFCFB.1070601@cisco.com>
Date: Thu, 27 Aug 2015 14:05:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55DECD8F.3070500@ericsson.com>
Content-Type: multipart/alternative; boundary="------------070902030505030907050905"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/sVz27HmPefxbHAURfzWq2328164>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>
Subject: Re: [rmcat] Sections 5.1 and 5.2 of draft-ietf-rmcat-eval-test-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, 27 Aug 2015 12:05:25 -0000

This is a multi-part message in MIME format.
--------------070902030505030907050905
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


Hi Zahed,

Please see inline [SM]

Regards,

Sergio


On 27/08/15 10:42, Zaheduzzaman Sarker wrote:
>
>
> On 2015-08-26 09:35, Sergio Mena wrote:
>>
>> Hi Zahed,
>>
>> First of all, your question. By "insensitive traffic" I meant that the
>> flow is CBR, so it won't back off whether other traffic is present in
>> the bottleneck link or not. Maybe we can find a better name for this...
> ok, understood. To me "flow is CBR" is good enough.
>>
>> On the other hand, in the last days, I have been working on an ns3
>> implementation of some of the test cases in the draft. I realized that
>> it would be coherent (and useful, IMO) for 5.3 to also have a "b"
>> version where both forward and backward paths are changed by a CBR,
>> similarly to 5.1 and 5.2. Let me know your thoughts on this.
> is it possible to share your findings so that we can also have a look 
> at the characteristics the new test option (path capacity limitation 
> by introducing CBR) is revealing (applicable for 5.1 and 5.2 as well)? 
> I think it is better to discuss and learn more about the test case 
> characteristics before we add the new option.

[SM] The main reasons why I raised the question (during rmcat session in 
Prague, and later on in this mailing list) of using CBR traffic to limit 
the bottleneck capacity are the following.

  * When one changes the nominal (i.e., physical) line rate of a network 
link (the bottleneck link in our case), there are other important 
parameters that are affected. For instance, packet transmission delay 
changes. Also, importantly enough for CC, the queue sizes in ms will 
also change (since queue sizes are usually specified in terms of packets 
or bytes in real networks).

  * Another important reason is that, in the wild, it is likely that a 
CC algorithm needs to react to abrupt changes in background traffic, 
roughly as likely as it needs to react to changes in topology. And, IMO, 
the test cases you guys are proposing should cover most use cases that 
are likely to occur in real life.

>
> For test case 5.3, it is important that the path capacity change in 
> the backward path happens at the right time so that we can see the 
> effect of lost or delayed feedback in the forward path. have you seen 
> any change required at the time one need to start the CBR traffic to 
> introduce the capacity change at correct time? How easy will it be to 
> do this in a lab network?

[SM] So far, I did not need to change the specified times for the 
backward path in 5.3, in order to expose the features of the CC 
algorithm that this test case is supposed to check (mainly congested 
feedback paths). Bear in mind that the CBR does not ramp up: it starts 
right at the CBR rate. So I think the times specified in the draft are 
fine as they are. Of course, my implementation of the tests is work in 
progress, so I'll let you know quickly if I observe anything else.

I think it would be relatively easy to implement CBR in a real testbed 
(it is simply a process that starts at a given time and sends UDP 
packets at the specified rate right from the beginning). So it takes in 
the order of 100s of ms (1/2 the rtt) for the whole path to "feel" it; 
this is not a problem for 5.3 where times are specified in the order of 
10s of seconds.

>
> For 5.1, 5.2 (and 5.3), how do you introduce the competing CBR 
> traffic? if there is a single bottleneck node between A and B then the 
> competing CBR traffic can share the same path as the media traffic. 
> However, if there are multiple nodes between A and B (can happen in 
> the lab network), then sharing the same path can create multiple 
> bottlenecks, right? I haven't tried that yet. Even if that is the case 
> then I think this can be solved by some additional text in the draft 
> but it will require different topology than the current assumptions.

[SM] The way I understand it: if there are other hops in the real 
testbed we use to run the rmcat tests, the non-bottleneck links should 
have a capacity so high that the particular value of the capacity does 
not matter. Otherwise, there may be losses/queuing delay at places other 
than the bottleneck, /even in the absence of CBR traffic/. If that was 
the case, then the full topology should be specified in the draft, so 
that the results are reproducible (but I do not think that 5.1 5.2 5.3 
should have more than one bottleneck link per direction).

>
> BR


--------------070902030505030907050905
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      Hi Zahed,<br>
      <br>
      Please see inline [SM]<br>
      <br>
      Regards,<br>
      <br>
      Sergio<br>
      <br>
      <br>
      On 27/08/15 10:42, Zaheduzzaman Sarker wrote:<br>
    </div>
    <blockquote cite="mid:55DECD8F.3070500@ericsson.com" type="cite">
      <br>
      <br>
      On 2015-08-26 09:35, Sergio Mena wrote:
      <br>
      <blockquote type="cite">
        <br>
        Hi Zahed,
        <br>
        <br>
        First of all, your question. By "insensitive traffic" I meant
        that the
        <br>
        flow is CBR, so it won't back off whether other traffic is
        present in
        <br>
        the bottleneck link or not. Maybe we can find a better name for
        this...
        <br>
      </blockquote>
      ok, understood. To me "flow is CBR" is good enough.
      <br>
      <blockquote type="cite">
        <br>
        On the other hand, in the last days, I have been working on an
        ns3
        <br>
        implementation of some of the test cases in the draft. I
        realized that
        <br>
        it would be coherent (and useful, IMO) for 5.3 to also have a
        "b"
        <br>
        version where both forward and backward paths are changed by a
        CBR,
        <br>
        similarly to 5.1 and 5.2. Let me know your thoughts on this.
        <br>
      </blockquote>
      is it possible to share your findings so that we can also have a
      look at the characteristics the new test option (path capacity
      limitation by introducing CBR) is revealing (applicable for 5.1
      and 5.2 as well)? I think it is better to discuss and learn more
      about the test case characteristics before we add the new option.
      <br>
    </blockquote>
    <br>
    [SM] The main reasons why I raised the question (during rmcat
    session in Prague, and later on in this mailing list) of using CBR
    traffic to limit the bottleneck capacity are the following.<br>
    <br>
     * When one changes the nominal (i.e., physical) line rate of a
    network link (the bottleneck link in our case), there are other
    important parameters that are affected. For instance, packet
    transmission delay changes. Also, importantly enough for CC, the
    queue sizes in ms will also change (since queue sizes are usually
    specified in terms of packets or bytes in real networks).<br>
    <br>
     * Another important reason is that, in the wild, it is likely that
    a CC algorithm needs to react to abrupt changes in background
    traffic, roughly as likely as it needs to react to changes in
    topology. And, IMO, the test cases you guys are proposing should
    cover most use cases that are likely to occur in real life.<br>
    <br>
    <blockquote cite="mid:55DECD8F.3070500@ericsson.com" type="cite">
      <br>
      For test case 5.3, it is important that the path capacity change
      in the backward path happens at the right time so that we can see
      the effect of lost or delayed feedback in the forward path. have
      you seen any change required at the time one need to start the CBR
      traffic to introduce the capacity change at correct time? How easy
      will it be to do this in a lab network?
      <br>
    </blockquote>
    <br>
    [SM] So far, I did not need to change the specified times for the
    backward path in 5.3, in order to expose the features of the CC
    algorithm that this test case is supposed to check (mainly congested
    feedback paths). Bear in mind that the CBR does not ramp up: it
    starts right at the CBR rate. So I think the times specified in the
    draft are fine as they are. Of course, my implementation of the
    tests is work in progress, so I'll let you know quickly if I observe
    anything else.<br>
    <br>
    I think it would be relatively easy to implement CBR in a real
    testbed (it is simply a process that starts at a given time and
    sends UDP packets at the specified rate right from the beginning).
    So it takes in the order of 100s of ms (1/2 the rtt) for the whole
    path to "feel" it; this is not a problem for 5.3 where times are
    specified in the order of 10s of seconds.<br>
    <br>
    <blockquote cite="mid:55DECD8F.3070500@ericsson.com" type="cite">
      <br>
      For 5.1, 5.2 (and 5.3), how do you introduce the competing CBR
      traffic? if there is a single bottleneck node between A and B then
      the competing CBR traffic can share the same path as the media
      traffic. However, if there are multiple nodes between A and B (can
      happen in the lab network), then sharing the same path can create
      multiple bottlenecks, right? I haven't tried that yet. Even if
      that is the case then I think this can be solved by some
      additional text in the draft but it will require different
      topology than the current assumptions.
      <br>
    </blockquote>
    <br>
    [SM] The way I understand it: if there are other hops in the real
    testbed we use to run the rmcat tests, the non-bottleneck links
    should have a capacity so high that the particular value of the
    capacity does not matter. Otherwise, there may be losses/queuing
    delay at places other than the bottleneck, <i>even in the absence
      of CBR traffic</i>. If that was the case, then the full topology
    should be specified in the draft, so that the results are
    reproducible (but I do not think that 5.1 5.2 5.3 should have more
    than one bottleneck link per direction).<br>
    <br>
    <blockquote cite="mid:55DECD8F.3070500@ericsson.com" type="cite">
      <br>
      BR
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------070902030505030907050905--

