
From nobody Tue Dec  6 10:36:24 2016
Return-Path: <csp@csperkins.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98670129566 for <rmcat@ietfa.amsl.com>; Tue,  6 Dec 2016 10:36:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QUw5ko2wDaJ for <rmcat@ietfa.amsl.com>; Tue,  6 Dec 2016 10:36:20 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA616129A64 for <rmcat@ietf.org>; Tue,  6 Dec 2016 10:36:19 -0800 (PST)
Received: from [82.132.220.146] (port=59757 helo=[172.20.10.2]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1cEKbB-0006cb-Cv; Tue, 06 Dec 2016 18:36:18 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_AEDA5F44-D6B2-493B-B357-253667981709"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <01258ecf-6a8a-1e8f-20f9-8d105ccb889e@kau.se>
Date: Tue, 6 Dec 2016 18:35:43 +0000
Message-Id: <3D88BE15-2E05-490A-A5BB-98993D892A52@csperkins.org>
References: <01258ecf-6a8a-1e8f-20f9-8d105ccb889e@kau.se>
To: Anna Brunstrom <anna.brunstrom@kau.se>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/eI2Q1f8NL2SxbJgjFLR4_rEmJ_g>
Cc: "rmcat@ietf.org" <rmcat@ietf.org>
Subject: Re: [rmcat] RMCAT WGLC: draft-ietf-rmcat-sbd-05 - ends Dec 4
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Dec 2016 18:36:22 -0000

--Apple-Mail=_AEDA5F44-D6B2-493B-B357-253667981709
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 13 Nov 2016, at 15:06, Anna Brunstrom <anna.brunstrom@kau.se> =
wrote:
> This email announces a RMCAT Working Group Last Call (WGLC) on:
>=20
> Shared Bottleneck Detection for Coupled Congestion Control for RTP =
Media
> draft-ietf-rmcat-sbd-05 =
<https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/>
> Due to the IETF week, this WGLC will run for 3 weeks, ending at =
midnight US Eastern Time on Sunday, December 4.  Comments should =
preferably be sent to the rmcat@ietf.org <mailto:rmcat@ietf.org> list, =
although purely editorial comments may be sent directly to the authors =
at draft-ietf-rmcat-sbd@ietf.org <mailto:draft-ietf-rmcat-sbd@ietf.org> =
- if doing so, please cc: the WG chairs at rmcat-chairs@tools.ietf.org =
<mailto:rmcat-chairs@tools.ietf.org>.
>=20
> We are looking for at least a couple of reviews during WGLC, so please =
help review the document.=20


(Posting as an individual participant, not as WG co-chair)

I=E2=80=99ve reviewed this draft. In general, I think it=E2=80=99s in =
very good shape, and suitable for publication as an experimental RFC. I =
do, however, have some comments:

- If I understand correctly, the draft replies on feedback sent every T =
seconds, where T=3D350ms by default. Such feedback is, presumably, to be =
sent by RTCP, since that is the standard back-channel for RTP flows. The =
RTCP reporting interval depends on the allocated RTCP bandwidth, the =
number of participants, and the size of the RTCP packets, and can vary =
between tens of milliseconds and tens of seconds. It=E2=80=99s unlikely =
to be exactly 350ms, although values of that order are not unreasonable. =
To what extent does the proposed mechanism depend on the precise timing =
of the feedback, and what are the acceptable upper- and lower-bounds on =
the feedback interval if the mechanism is to work? It would be useful if =
the draft could include some discussion of this, to aid both =
implementors and those looking to design congestion control and feedback =
mechanisms.=20

- Section 3.3.1 has a sequence of steps that start =E2=80=9Cgroup flows =
whose=E2=80=A6=E2=80=9D. I find this a little hard to follow, in =
particular it=E2=80=99s not clear what flows are left ungrouped after =
each stage. Would changing these steps to start =E2=80=9C=46rom the =
remaining set of ungrouped flows, group those flows whose=E2=80=A6=E2=80=9D=
 reflect the intent and be clearer?=20

- Are the mechanisms in sections 3.4 and 3.5 required to be implemented, =
or are the optional? Some normative language might help to make it =
clearer what an implementation should do with these. It=E2=80=99s not =
clear if they=E2=80=99re essential parts of the algorithm, or =
enhancements for some situations.

- In general, for a protocol specification, I think the draft would =
benefit from a more prescriptive (=E2=80=9Cwhen this happens, do =
this=E2=80=9D) style of writing. I don=E2=80=99t think that=E2=80=99s a =
blocker for Experimental, but something to consider if it=E2=80=99s =
later revised for standards track.

- Section 4.1, 2nd paragraph: I assume the suggestion is that each flow =
should use its media clock? Do any issues that arise when trying to =
group flows that use RTP different clock rates (e.g., the case where the =
audio flow has an 8kHz clock and the video flow has a 90kHz clock)?

- The draft says little about how feedback is to be conveyed. Is the =
expectation that the information can be extracted from the standard RTCP =
reception reports, or maybe XR blocks? It would be helpful if the draft =
could either point to existing feedback mechanisms that are suitable, or =
state that RTCP extensions will be needed.=20

Cheers,
Colin




--=20
Colin Perkins
https://csperkins.org/





--Apple-Mail=_AEDA5F44-D6B2-493B-B357-253667981709
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
13 Nov 2016, at 15:06, Anna Brunstrom &lt;<a =
href=3D"mailto:anna.brunstrom@kau.se" =
class=3D"">anna.brunstrom@kau.se</a>&gt; wrote:</div><div class=3D""><div =
bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""><p wrap=3D"" =
class=3D"">This email announces a RMCAT Working Group Last Call
      (WGLC) on:</p>
    <blockquote class=3D""><p wrap=3D"" class=3D"">Shared Bottleneck =
Detection for Coupled Congestion
        Control for RTP Media<br class=3D"">
        <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/"=
 class=3D"">draft-ietf-rmcat-sbd-05</a></p>
    </blockquote><p wrap=3D"" class=3D"">Due to the IETF week, this WGLC =
will run for 3 weeks,
      ending at midnight US Eastern Time on Sunday, December 4.&nbsp;
      Comments should preferably be sent to the <a =
href=3D"mailto:rmcat@ietf.org" =
class=3D"moz-txt-link-abbreviated">rmcat@ietf.org</a>
      list, although purely editorial comments may be sent directly to
      the authors at <a href=3D"mailto:draft-ietf-rmcat-sbd@ietf.org" =
class=3D"moz-txt-link-abbreviated">draft-ietf-rmcat-sbd@ietf.org</a> - =
if doing so, please
      cc: the WG chairs at <a href=3D"mailto:rmcat-chairs@tools.ietf.org" =
class=3D"moz-txt-link-abbreviated">rmcat-chairs@tools.ietf.org</a>.</p><p =
wrap=3D"" class=3D"">We are looking for at least a couple of reviews =
during
      WGLC, so please help review the document. <br class=3D"">
    </p></div></div></blockquote></div><div class=3D""><br =
class=3D"webkit-block-placeholder"></div><div class=3D""><span =
style=3D"border-collapse: separate; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; widows: 2; border-spacing: 0px;" class=3D"Apple-style-span"><div =
class=3D"" style=3D"color: rgb(0, 0, 0); font-family: 'Lucida Sans =
Typewriter'; font-size: 9px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-transform: =
none; white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;">(Posting as an individual participant, not as WG =
co-chair)</div><div class=3D"" style=3D"color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;"><br class=3D""></div><div class=3D"" style=3D"color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;">I=E2=80=99ve reviewed this draft. In general, I think it=E2=80=99s =
in very good shape, and suitable for publication as an experimental RFC. =
I do, however, have some comments:</div><div class=3D"" style=3D"color: =
rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-size: 9px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-decorations-in-effect: none; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><div class=3D"">- =
If I understand correctly, the draft replies on f<span style=3D"color: =
rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-size: 9px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-decorations-in-effect: none; =
-webkit-text-stroke-width: 0px; text-align: -webkit-auto;" =
class=3D"">eedback sent every T seconds, where T=3D350ms by default. =
Such feedback is, presumably, to be sent by RTCP, since that is the =
standard back-channel for RTP flows. The RTCP reporting interval depends =
on the allocated RTCP bandwidth, the number of participants, and the =
size of the RTCP packets, and can vary between tens of milliseconds and =
tens of seconds. It</span>=E2=80=99s unlikely to be exactly 350ms, =
although values of that order are not unreasonable. To what extent does =
the proposed mechanism depend on the precise timing of the feedback, and =
what are the acceptable upper- and lower-bounds on the feedback interval =
if the mechanism is to work? It would be useful if the draft could =
include some discussion of this, to aid both implementors and those =
looking to design congestion control and feedback =
mechanisms.&nbsp;</div><div class=3D""><br class=3D"">- Section 3.3.1 =
has a sequence of steps that start =E2=80=9Cgroup flows whose=E2=80=A6=E2=80=
=9D. I find this a little hard&nbsp;to follow, in particular it=E2=80=99s =
not clear what flows are left ungrouped after each stage. Would changing =
these steps to start =E2=80=9C=46rom the remaining set of ungrouped =
flows, group&nbsp;those flows whose=E2=80=A6=E2=80=9D reflect the intent =
and be clearer?&nbsp;<br class=3D""><br class=3D"">- Are the mechanisms =
in sections 3.4 and 3.5 required to be implemented, or are the optional? =
Some normative language might help to make it clearer&nbsp;what an =
implementation should do with these. It=E2=80=99s not clear if they=E2=80=99=
re essential parts of the&nbsp;algorithm, or enhancements for some =
situations.</div><div class=3D""><br class=3D""></div><div class=3D"">- =
In general, for a protocol specification, I think the draft would =
benefit from a more prescriptive (=E2=80=9Cwhen this happens, do =
this=E2=80=9D) style of writing. I don=E2=80=99t think that=E2=80=99s a =
blocker for Experimental, but something to consider if it=E2=80=99s =
later revised for standards track.<br class=3D""><br class=3D"">- =
Section 4.1, 2nd paragraph: I assume the suggestion is that each flow =
should use its media&nbsp;clock? Do any issues that arise when trying to =
group flows that use RTP different&nbsp;clock rates (e.g., the case =
where the audio flow has an 8kHz clock and the video flow has =
a&nbsp;90kHz clock)?<br class=3D""><br class=3D"">- The draft says =
little about how feedback is to be conveyed. Is the expectation that =
the&nbsp;information can be extracted from the standard RTCP reception =
reports, or maybe XR blocks? It would be helpful if the draft could =
either point to existing feedback mechanisms that are suitable, or state =
that RTCP extensions will be needed.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Cheers,</div><div =
class=3D"">Colin</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><br class=3D""><br =
class=3D"khtml-block-placeholder"></div><div class=3D"" style=3D"color: =
rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-size: 9px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-decorations-in-effect: none; =
-webkit-text-stroke-width: 0px;">--&nbsp;</div><div class=3D"" =
style=3D"color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-transform: none; =
white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;"></div><div class=3D"" style=3D"color: rgb(0, 0, 0); font-family: =
'Lucida Sans Typewriter'; font-size: 9px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;">Colin Perkins</div><div class=3D"" style=3D"color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: =
0px;"><a href=3D"https://csperkins.org/" =
class=3D"">https://csperkins.org/</a></div><div class=3D"" style=3D"color:=
 rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-size: 9px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-decorations-in-effect: none; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div></span><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_AEDA5F44-D6B2-493B-B357-253667981709--


From nobody Wed Dec  7 05:49:08 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: rmcat@ietf.org
Delivered-To: rmcat@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA2A129991; Wed,  7 Dec 2016 05:49:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148111854325.13729.9946710085994858033.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2016 05:49:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/Voc8jdk-l8MfvykfmB2q69lQ2Iw>
Cc: rmcat@ietf.org
Subject: [rmcat] I-D Action: draft-ietf-rmcat-coupled-cc-05.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Dec 2016 13:49:03 -0000

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

        Title           : Coupled congestion control for RTP media
        Authors         : Safiqul Islam
                          Michael Welzl
                          Stein Gjessing
	Filename        : draft-ietf-rmcat-coupled-cc-05.txt
	Pages           : 25
	Date            : 2016-12-07

Abstract:
   When multiple congestion controlled RTP sessions traverse the same
   network bottleneck, combining their controls can improve the total
   on-the-wire behavior in terms of delay, loss and fairness.  This
   document describes such a method for flows that have the same sender,
   in a way that is as flexible and simple as possible while minimizing
   the amount of changes needed to existing RTP applications.  It
   specifies how to apply the method for the NADA congestion control
   algorithm, and provides suggestions on how to apply it to other
   congestion control algorithms.


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

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

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


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

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


From nobody Fri Dec  9 03:19:35 2016
Return-Path: <prvs=0151587775=anna.brunstrom@kau.se>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08E9312A3F1 for <rmcat@ietfa.amsl.com>; Fri,  9 Dec 2016 03:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dw4Gk8gWxN28 for <rmcat@ietfa.amsl.com>; Fri,  9 Dec 2016 03:19:31 -0800 (PST)
Received: from nasse.dc.kau.se (smtp.kau.se [193.10.220.39]) (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 217B112A3AB for <rmcat@ietf.org>; Fri,  9 Dec 2016 03:12:56 -0800 (PST)
X-Spam-Processed: mail.kau.se, Fri, 09 Dec 2016 12:12:49 +0100 (not processed: spam filter heuristic analysis disabled)
X-MDRemoteIP: 193.11.155.110
X-MDArrival-Date: Fri, 09 Dec 2016 12:12:49 +0100
X-Authenticated-Sender: anna.brunstrom@kau.se
X-Return-Path: anna.brunstrom@kau.se
X-Envelope-From: anna.brunstrom@kau.se
X-MDaemon-Deliver-To: rmcat@ietf.org
To: "rmcat@ietf.org" <rmcat@ietf.org>
From: Anna Brunstrom <anna.brunstrom@kau.se>
Message-ID: <72385da9-9de5-8168-b58e-9bd760a6eb8b@kau.se>
Date: Fri, 9 Dec 2016 12:12:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/xzX6KvPNok5IRfDhfJKNY3PsfIY>
Subject: [rmcat] Minutes IETF 97
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2016 11:19:34 -0000

Dear all,

The minutes from the rmcat session at IETF 97 are available at 
https://www.ietf.org/proceedings/97/minutes/minutes-97-rmcat-00.txt. 
Please let the chairs know of any corrections or additions.

Thanks to Alan for taking notes!

Cheers,
Anna




From nobody Fri Dec  9 15:26:22 2016
Return-Path: <csp@csperkins.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 802951295D4 for <rmcat@ietfa.amsl.com>; Fri,  9 Dec 2016 15:26:20 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSLLHur5kuvx for <rmcat@ietfa.amsl.com>; Fri,  9 Dec 2016 15:26:18 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B5C21279EB for <rmcat@ietf.org>; Fri,  9 Dec 2016 15:26:18 -0800 (PST)
Received: from [81.187.2.149] (port=40372 helo=[192.168.0.91]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1cFUYS-0000vx-Ff for rmcat@ietf.org; Fri, 09 Dec 2016 23:26:17 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <148111854325.13729.9946710085994858033.idtracker@ietfa.amsl.com>
Date: Fri, 9 Dec 2016 23:26:15 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <66C087EE-823A-43C9-8E8B-A2364FD6511B@csperkins.org>
References: <148111854325.13729.9946710085994858033.idtracker@ietfa.amsl.com>
To: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: State = no_sa; Score = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/Qq2WSsfhdy6IBTc99SYx39JFoJQ>
Subject: Re: [rmcat] I-D Action: draft-ietf-rmcat-coupled-cc-05.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2016 23:26:20 -0000

WG,

The authors recently submitted draft-ietf-rmcat-coupled-cc-05. Following =
the discussion in the working group session at IETF 97 in Seoul, this =
moves the text on how to use coupled congestion control with the Google =
congestion control (GCC) algorithm from the main text to an appendix, =
and makes the reference to GCC informative. The rest of the document is =
updated to use NADA as the example, rather than NADA and GCC. These =
changes are intended to prevent the coupled congestion control draft =
from blocking on a normative reference to GCC, since the GCC draft is =
not yet finished. They are not intended to change the scope of the work.

The authors have also taken the opportunity to add some minor =
clarifications to the general recommendations, adding text on Stateful =
algorithms and Rate Jumps, in what is now Section 6.2 of the draft.

This draft has completed working group last call. However, since there =
was some discussion around these changes in the meeting, the chairs =
would like to re-open the working group last call for an additional week =
to ensure there are no objections. If you object to the changes in this =
version of the draft, please comment to the list by 16 December 2016. If =
there are no objections, the chairs will prepare the write-up to send =
this to the IESG in early 2017.

Colin
(as WG co-chair)





> On 7 Dec 2016, at 13:49, Internet-Drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the RTP Media Congestion Avoidance =
Techniques of the IETF.
>=20
>        Title           : Coupled congestion control for RTP media
>        Authors         : Safiqul Islam
>                          Michael Welzl
>                          Stein Gjessing
> 	Filename        : draft-ietf-rmcat-coupled-cc-05.txt
> 	Pages           : 25
> 	Date            : 2016-12-07
>=20
> Abstract:
>   When multiple congestion controlled RTP sessions traverse the same
>   network bottleneck, combining their controls can improve the total
>   on-the-wire behavior in terms of delay, loss and fairness.  This
>   document describes such a method for flows that have the same =
sender,
>   in a way that is as flexible and simple as possible while minimizing
>   the amount of changes needed to existing RTP applications.  It
>   specifies how to apply the method for the NADA congestion control
>   algorithm, and provides suggestions on how to apply it to other
>   congestion control algorithms.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rmcat-coupled-cc/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-rmcat-coupled-cc-05
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rmcat-coupled-cc-05
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/

--=20
Colin Perkins
https://csperkins.org/




