
From nobody Fri Feb  2 08:04:22 2018
Return-Path: <ietf@kuehlewind.net>
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 1814712D961 for <rmcat@ietfa.amsl.com>; Fri,  2 Feb 2018 08:04:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 Ea5ju3ueHnmD for <rmcat@ietfa.amsl.com>; Fri,  2 Feb 2018 08:04:18 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C08D12711B for <rmcat@ietf.org>; Fri,  2 Feb 2018 08:04:17 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=WgvvzzqF15jyU2yPRhB7nw8avKW9pbJqBoCTjAIaMm57ypVm41MFo0EzDsyW3ZfdTq6t59cZz7m95/ESSRG4osdRX8wWq9fKW0PF5DzoPl75yH1+M809LpAH8GRqR/6YJL+7CAeko55okIP7/6axD+rSsmzAT3wcSv48m576kvo=; h=Received:Received:From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:Cc:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 29726 invoked from network); 2 Feb 2018 17:04:15 +0100
Received: from i577bce83.versanet.de (HELO ?192.168.178.33?) (87.123.206.131) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 2 Feb 2018 17:04:15 +0100
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net>
Date: Fri, 2 Feb 2018 17:04:14 +0100
Cc: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
To: draft-ietf-rmcat-sbd.all@ietf.org
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180202160415.29721.31583@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/CRP0VjkRgXQT4OyjGhws9DUWwfw>
Subject: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Feb 2018 16:04:20 -0000

Hi authors, hi chairs,

many thanks for this very well written document as well as a good =
write-up from the shepherd!

Before I start the IETF LC call I have two small questions:

1) Normative references:

I wonder if draft-ietf-rmcat-coupled-cc should be a normative reference, =
especially as it is mentioned in the abstract, but also because it =
probably helps to at least read section 4 (architecture) of =
draft-ietf-rmcat-coupled-cc.

Further this sentence seems to make avtcore-cc-feedback-message should =
also be a normative reference:
"Timing information described by
   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
   sender to calculate relative OWD.=E2=80=9C
I don=E2=80=99t think we want to wait for avtcore-cc-feedback-message =
for publication, therefor I would recommend to say something about the =
resolution used in avtcore-cc-feedback-message, e.g.
=E2=80=9EFrequent timing information in millisecond resolution as =
described by
   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
   sender to calculate relative OWD.=E2=80=9C

2) I can't remember if this was discussed in the group but actually I =
believe it was not: this document could also be an informational =
document, as it is just one example algorithm but there are no =
dependencies on this scheme otherwise. I also don=E2=80=99t think is =
makes too much sense to think about this proposed algorithm as an =
experiment; if you want to change the algorithm or use a different one =
just do it; this is just a documentation of one proposal. I also assume =
that there is actually not much interest in the group to publish an =
updated version of this algorithm as proposed standard, as such why not =
informational from the beginning=E2=80=A6?

If the authors and the group are uncertain about this point, I=E2=80=99m =
okay to start IETF LC as exp and see if we can get further feedback =
there or from the IESG; =E2=80=9Edowngrading=E2=80=9C to information can =
easily be done with any additional actions at any time.

It would be great if you could reply (or update) by early next week as I =
would like to start the IETF LC latest by Wednesday (or I need to move =
the draft to the telechat two weeks later on March 8).

Find further below other comments that came to my mind while reading the =
doc. None of these are critical to proceed the document and may or may =
not be address at any point in the process.

Thanks!
Mirja


=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94
Other review comments:


1) As normative language is very sparsely use in this document and when =
used not really that much necessary, I would recommend to instead not =
used normative language at all, which mean use only lower case words and =
removed the respective preamble text in sec 2.

2) Question on the 2. scenario in section 3 (receiver-side). This says =
that the receiver H3 can calculate stats for SBD for H1 and H2, however =
H1 and H2 cannot implement coupled congestion control, thus congestion =
control would also need to be implemented at the receiver H3, right? =
Maybe worth mentioning...

3) In section 3.2.1, I=E2=80=99d say that the following part could be =
removed as it goes a bit beyond the scope of the document, and also =
seems actually unnecessary to me: if you have a way to request a set of =
metrics and the other end tells you with metrics it can send, you have =
to chose your SBD algorithm based on that information anyway without =
actually being at all restricted to one specific scheme.

"* A protocol identifier (SBD=3D01). This is to future proof the message =
exchange so that potential advances in SBD technology can be easily =
deployed. All following initialization elements relate to the mechanism =
outlined in this document which will have the identifier SBD=3D01.=E2=80=9C=


4) RMCAT is mentioned 3 times on the doc but never really introduced. =
Maybe make the following change:=20
sec 3.1.3: s/SBD in RMCAT/the SBD algorithm described in this document./
sec 3.3.1: s/SBD in the RMCAT context/use of SBD with Coupled congestion =
control for RTP media [draft-ietf-rmcat-coupled-cc]/
sec 6: s/RMCAT congestion control algorithms/RTP Media Congestion =
Avoidance Techniques (RMCAT) algorithms/=20
   or: s/RMCAT congestion control algorithms/congestion control =
algorithm as developed in the RTP Media Congestion Avoidance Techniques =
(RMCAT) working group/

5) Use of the terms one way delay, OWD, or e.g way delay samples (OWD) =
is inconsistent in section 3.2.1 and 3.2.2

6) Just to double-check: sec 3.2.1, 3.2.2, and 3.2.3 use M while 3.2.4 =
and 3.2.5 use N. Is that correct? To be honest I actually still did not =
fully understand yet why and N and M are needed.

7) Sec 5.1:
OLD:
"Timing information described by
   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
   sender to calculate relative OWD."
MAYBE
"Timing information described by
   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
   sender to calculate relative OWD of an Internet path.=E2=80=9C
Or would those information be also sufficient for e.g. a data center =
scenario?

8) Probably the security consideration section should also point to the =
security considerations of draft-ietf-rmcat-coupled-cc.



From nobody Mon Feb  5 17:18:42 2018
Return-Path: <prvs=057550a7a4=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 AFF8912DA27; Mon,  5 Feb 2018 17:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vtpJw2AFR166; Mon,  5 Feb 2018 17:18:38 -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 A584312DA06; Mon,  5 Feb 2018 17:18:38 -0800 (PST)
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, <draft-ietf-rmcat-sbd.all@ietf.org>
CC: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net>
From: Anna Brunstrom <anna.brunstrom@kau.se>
Message-ID: <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se>
Date: Tue, 6 Feb 2018 02:18:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ClientProxiedBy: Exch-A1.personal.kau (130.243.19.82) To Exch-A2.personal.kau (130.243.19.83)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/8v-WmHQTyi2T8DSORGo-nxe8W9E>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 01:18:41 -0000

Hi Mirja, all,

Comments inline.

On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:
> Hi authors, hi chairs,
>
> many thanks for this very well written document as well as a good write-up from the shepherd!
>
> Before I start the IETF LC call I have two small questions:
>
> 1) Normative references:
>
> I wonder if draft-ietf-rmcat-coupled-cc should be a normative reference, especially as it is mentioned in the abstract, but also because it probably helps to at least read section 4 (architecture) of draft-ietf-rmcat-coupled-cc.

My understanding is that only normative statements create normative 
references, so the fact that it is mentioned in the abstract or useful 
to read does not make it normative? As I am not so experienced with the 
process I looked for guidelines on this before reviewing the draft and 
this is at least what draft-peterson-informational-normativity-01 suggests.

> Further this sentence seems to make avtcore-cc-feedback-message should also be a normative reference:
> "Timing information described by
>     [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>     sender to calculate relative OWD.“
> I don’t think we want to wait for avtcore-cc-feedback-message for publication, therefor I would recommend to say something about the resolution used in avtcore-cc-feedback-message, e.g.
> „Frequent timing information in millisecond resolution as described by
>     [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>     sender to calculate relative OWD.“

 From the same reasoning as above, I am not sure that this is a 
normative reference either? But I agree that your proposal to mention 
the resolution is much better! Actually, reading the text now we should 
probably also avoid the lower case should just to not confuse it with 
SHOULD, Perhaps "will be" or "is believed to be" or something similar 
instead of "should be".

> 2) I can't remember if this was discussed in the group but actually I believe it was not: this document could also be an informational document, as it is just one example algorithm but there are no dependencies on this scheme otherwise. I also don’t think is makes too much sense to think about this proposed algorithm as an experiment; if you want to change the algorithm or use a different one just do it; this is just a documentation of one proposal. I also assume that there is actually not much interest in the group to publish an updated version of this algorithm as proposed standard, as such why not informational from the beginning…?
>
> If the authors and the group are uncertain about this point, I’m okay to start IETF LC as exp and see if we can get further feedback there or from the IESG; „downgrading“ to information can easily be done with any additional actions at any time.

This is not something that has been discussed as far as I know, but I am 
not sure what happened in the beginning of the process. Unless the 
authors prefer to have it informational I would not like to change the 
status at this point as this is not something that has been discussed in 
the group. I also do not think it is fully correct to say that SBD does 
not interact with other mechanisms in the network as it can affect 
congestion control and the performance of other flows. So the need to 
verify a sane and useful behavior still seems to be applicable here.

> It would be great if you could reply (or update) by early next week as I would like to start the IETF LC latest by Wednesday (or I need to move the draft to the telechat two weeks later on March 8).
>
> Find further below other comments that came to my mind while reading the doc. None of these are critical to proceed the document and may or may not be address at any point in the process.

Great, thanks! Authors please take them into account in you next update.

Best Regards,
Anna

>
> Thanks!
> Mirja
>
>
> ————————
> Other review comments:
>
>
> 1) As normative language is very sparsely use in this document and when used not really that much necessary, I would recommend to instead not used normative language at all, which mean use only lower case words and removed the respective preamble text in sec 2.
>
> 2) Question on the 2. scenario in section 3 (receiver-side). This says that the receiver H3 can calculate stats for SBD for H1 and H2, however H1 and H2 cannot implement coupled congestion control, thus congestion control would also need to be implemented at the receiver H3, right? Maybe worth mentioning...
>
> 3) In section 3.2.1, I’d say that the following part could be removed as it goes a bit beyond the scope of the document, and also seems actually unnecessary to me: if you have a way to request a set of metrics and the other end tells you with metrics it can send, you have to chose your SBD algorithm based on that information anyway without actually being at all restricted to one specific scheme.
>
> "* A protocol identifier (SBD=01). This is to future proof the message exchange so that potential advances in SBD technology can be easily deployed. All following initialization elements relate to the mechanism outlined in this document which will have the identifier SBD=01.“
>
> 4) RMCAT is mentioned 3 times on the doc but never really introduced. Maybe make the following change:
> sec 3.1.3: s/SBD in RMCAT/the SBD algorithm described in this document./
> sec 3.3.1: s/SBD in the RMCAT context/use of SBD with Coupled congestion control for RTP media [draft-ietf-rmcat-coupled-cc]/
> sec 6: s/RMCAT congestion control algorithms/RTP Media Congestion Avoidance Techniques (RMCAT) algorithms/
>     or: s/RMCAT congestion control algorithms/congestion control algorithm as developed in the RTP Media Congestion Avoidance Techniques (RMCAT) working group/
>
> 5) Use of the terms one way delay, OWD, or e.g way delay samples (OWD) is inconsistent in section 3.2.1 and 3.2.2
>
> 6) Just to double-check: sec 3.2.1, 3.2.2, and 3.2.3 use M while 3.2.4 and 3.2.5 use N. Is that correct? To be honest I actually still did not fully understand yet why and N and M are needed.
>
> 7) Sec 5.1:
> OLD:
> "Timing information described by
>     [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>     sender to calculate relative OWD."
> MAYBE
> "Timing information described by
>     [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>     sender to calculate relative OWD of an Internet path.“
> Or would those information be also sufficient for e.g. a data center scenario?
>
> 8) Probably the security consideration section should also point to the security considerations of draft-ietf-rmcat-coupled-cc.
>
>


From nobody Tue Feb  6 00:21:56 2018
Return-Path: <ietf@kuehlewind.net>
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 ACF61126CF9 for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 00:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 Ls_SP7NTeDHR for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 00:21:52 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 026D5120727 for <rmcat@ietf.org>; Tue,  6 Feb 2018 00:21:51 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=kCg6BZ/q0huMPE6ZmXUEySggVFKpc4XktJ7dNuUoN9nJjcoKsCmo5S8CwO08+GeTSuvw7Msi4OLdQR1hApZATdt862ZcgipuE9hL0/VlY2AvKcM554Uf/j06fYLs73mZVDbwPRIHMt/RbHyV6amGTMyjhXSIjQsyg4b8R5FWNCc=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 18280 invoked from network); 6 Feb 2018 09:21:49 +0100
Received: from mue-88-130-61-180.dsl.tropolys.de (HELO ?192.168.178.33?) (88.130.61.180) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 6 Feb 2018 09:21:49 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se>
Date: Tue, 6 Feb 2018 09:21:48 +0100
Cc: draft-ietf-rmcat-sbd.all@ietf.org, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se>
To: Anna Brunstrom <anna.brunstrom@kau.se>
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180206082149.18274.34592@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/K4mgeI1Ch_VzpHuuiJnhSULS31M>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 08:21:55 -0000

> Am 06.02.2018 um 02:18 schrieb Anna Brunstrom <anna.brunstrom@kau.se>:
>=20
> Hi Mirja, all,
>=20
> Comments inline.
>=20
> On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:
>> Hi authors, hi chairs,
>>=20
>> many thanks for this very well written document as well as a good =
write-up from the shepherd!
>>=20
>> Before I start the IETF LC call I have two small questions:
>>=20
>> 1) Normative references:
>>=20
>> I wonder if draft-ietf-rmcat-coupled-cc should be a normative =
reference, especially as it is mentioned in the abstract, but also =
because it probably helps to at least read section 4 (architecture) of =
draft-ietf-rmcat-coupled-cc.
>=20
> My understanding is that only normative statements create normative =
references, so the fact that it is mentioned in the abstract or useful =
to read does not make it normative? As I am not so experienced with the =
process I looked for guidelines on this before reviewing the draft and =
this is at least what draft-peterson-informational-normativity-01 =
suggests.

Normative references and normative language are two different things. A =
reference should be normative if it is (or part of it) a required read =
to understand the content of the document. E.g. if you write an TCP =
extension the RFC defining the TCP base protocol must be a normative =
reference. So my question is here, do you think that couple congestion =
is a required read to understand this document (I=E2=80=99m asking this =
because there is this architecture section in =
draft-ietf-rmcat-coupled-cc).

>=20
>> Further this sentence seems to make avtcore-cc-feedback-message =
should also be a normative reference:
>> "Timing information described by
>>    [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>    sender to calculate relative OWD.=E2=80=9C
>> I don=E2=80=99t think we want to wait for avtcore-cc-feedback-message =
for publication, therefor I would recommend to say something about the =
resolution used in avtcore-cc-feedback-message, e.g.
>> =E2=80=9EFrequent timing information in millisecond resolution as =
described by
>>    [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>    sender to calculate relative OWD.=E2=80=9C
>=20
> =46rom the same reasoning as above, I am not sure that this is a =
normative reference either? But I agree that your proposal to mention =
the resolution is much better! Actually, reading the text now we should =
probably also avoid the lower case should just to not confuse it with =
SHOULD, Perhaps "will be" or "is believed to be" or something similar =
instead of "should be=E2=80=9C.

There is no need to avoid lower case should. Actually there is the =
update of RFC2119 which clarifies this. You should probably also use the =
new boilerplate of RFC8174. Forgot to mention that!

>=20
>> 2) I can't remember if this was discussed in the group but actually I =
believe it was not: this document could also be an informational =
document, as it is just one example algorithm but there are no =
dependencies on this scheme otherwise. I also don=E2=80=99t think is =
makes too much sense to think about this proposed algorithm as an =
experiment; if you want to change the algorithm or use a different one =
just do it; this is just a documentation of one proposal. I also assume =
that there is actually not much interest in the group to publish an =
updated version of this algorithm as proposed standard, as such why not =
informational from the beginning=E2=80=A6?
>>=20
>> If the authors and the group are uncertain about this point, I=E2=80=99=
m okay to start IETF LC as exp and see if we can get further feedback =
there or from the IESG; =E2=80=9Edowngrading=E2=80=9C to information can =
easily be done with any additional actions at any time.
>=20
> This is not something that has been discussed as far as I know, but I =
am not sure what happened in the beginning of the process. Unless the =
authors prefer to have it informational I would not like to change the =
status at this point as this is not something that has been discussed in =
the group. I also do not think it is fully correct to say that SBD does =
not interact with other mechanisms in the network as it can affect =
congestion control and the performance of other flows. So the need to =
verify a sane and useful behavior still seems to be applicable here.

I didn=E2=80=99t say it didn=E2=80=99t interact but it does not need to =
be standardized for interoperability.

If we would decide to change the status, in agreement with the authors =
of course, I think it would be okay to simply announce it on the mailing =
list. I would not expect to see a lot of discuss there. I will wait for =
feedback from the authors. However, I don=E2=80=99t have a strong =
opinion here.

Mirja


>=20
>> It would be great if you could reply (or update) by early next week =
as I would like to start the IETF LC latest by Wednesday (or I need to =
move the draft to the telechat two weeks later on March 8).
>>=20
>> Find further below other comments that came to my mind while reading =
the doc. None of these are critical to proceed the document and may or =
may not be address at any point in the process.
>=20
> Great, thanks! Authors please take them into account in you next =
update.
>=20
> Best Regards,
> Anna
>=20
>>=20
>> Thanks!
>> Mirja
>>=20
>>=20
>> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=

>> Other review comments:
>>=20
>>=20
>> 1) As normative language is very sparsely use in this document and =
when used not really that much necessary, I would recommend to instead =
not used normative language at all, which mean use only lower case words =
and removed the respective preamble text in sec 2.
>>=20
>> 2) Question on the 2. scenario in section 3 (receiver-side). This =
says that the receiver H3 can calculate stats for SBD for H1 and H2, =
however H1 and H2 cannot implement coupled congestion control, thus =
congestion control would also need to be implemented at the receiver H3, =
right? Maybe worth mentioning...
>>=20
>> 3) In section 3.2.1, I=E2=80=99d say that the following part could be =
removed as it goes a bit beyond the scope of the document, and also =
seems actually unnecessary to me: if you have a way to request a set of =
metrics and the other end tells you with metrics it can send, you have =
to chose your SBD algorithm based on that information anyway without =
actually being at all restricted to one specific scheme.
>>=20
>> "* A protocol identifier (SBD=3D01). This is to future proof the =
message exchange so that potential advances in SBD technology can be =
easily deployed. All following initialization elements relate to the =
mechanism outlined in this document which will have the identifier =
SBD=3D01.=E2=80=9C
>>=20
>> 4) RMCAT is mentioned 3 times on the doc but never really introduced. =
Maybe make the following change:
>> sec 3.1.3: s/SBD in RMCAT/the SBD algorithm described in this =
document./
>> sec 3.3.1: s/SBD in the RMCAT context/use of SBD with Coupled =
congestion control for RTP media [draft-ietf-rmcat-coupled-cc]/
>> sec 6: s/RMCAT congestion control algorithms/RTP Media Congestion =
Avoidance Techniques (RMCAT) algorithms/
>>    or: s/RMCAT congestion control algorithms/congestion control =
algorithm as developed in the RTP Media Congestion Avoidance Techniques =
(RMCAT) working group/
>>=20
>> 5) Use of the terms one way delay, OWD, or e.g way delay samples =
(OWD) is inconsistent in section 3.2.1 and 3.2.2
>>=20
>> 6) Just to double-check: sec 3.2.1, 3.2.2, and 3.2.3 use M while =
3.2.4 and 3.2.5 use N. Is that correct? To be honest I actually still =
did not fully understand yet why and N and M are needed.
>>=20
>> 7) Sec 5.1:
>> OLD:
>> "Timing information described by
>>    [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>    sender to calculate relative OWD."
>> MAYBE
>> "Timing information described by
>>    [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>    sender to calculate relative OWD of an Internet path.=E2=80=9C
>> Or would those information be also sufficient for e.g. a data center =
scenario?
>>=20
>> 8) Probably the security consideration section should also point to =
the security considerations of draft-ietf-rmcat-coupled-cc.
>>=20
>>=20
>=20


From nobody Tue Feb  6 04:35:10 2018
Return-Path: <michawe@ifi.uio.no>
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 8CF9112E039; Tue,  6 Feb 2018 04:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 1gUTOWpJvaYQ; Tue,  6 Feb 2018 04:35:04 -0800 (PST)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 BFED312DB6E; Tue,  6 Feb 2018 04:35:03 -0800 (PST)
Received: from mail-mx03.uio.no ([129.240.10.15]) by mail-out01.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej2Sj-000745-3H; Tue, 06 Feb 2018 13:35:01 +0100
Received: from 93-58-133-64.ip158.fastwebnet.it ([93.58.133.64] helo=[10.0.0.4]) by mail-mx03.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej2Sh-00005f-3t; Tue, 06 Feb 2018 13:35:01 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_76AD1241-28D9-4D6F-ADF5-060F8FD3F310"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 6 Feb 2018 13:34:57 +0100
In-Reply-To: <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net>
Cc: Anna Brunstrom <anna.brunstrom@kau.se>, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net>
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx03.uio.no: 93.58.133.64 is neither permitted nor denied by domain of ifi.uio.no) client-ip=93.58.133.64;  envelope-from=michawe@ifi.uio.no; helo=[10.0.0.4]; 
X-UiO-Spam-info: not spam, SpamAssassin (score=-4.9, required=5.0, autolearn=disabled, AWL=0.088, HTML_MESSAGE=0.001, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: B82C32CC47104756B05AB5E998A3A8168D777541
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/1XT2Crf2tL0H5dXrwX9W2apDjYU>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 12:35:08 -0000

--Apple-Mail=_76AD1241-28D9-4D6F-ADF5-060F8FD3F310
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

As an author, first of all, thanks for your feedback!

I=E2=80=99m answering a point below:


> On Feb 6, 2018, at 9:21 AM, Mirja Kuehlewind (IETF) =
<ietf@kuehlewind.net> wrote:
>=20
>=20
>=20
>> Am 06.02.2018 um 02:18 schrieb Anna Brunstrom =
<anna.brunstrom@kau.se>:
>>=20
>> Hi Mirja, all,
>>=20
>> Comments inline.
>>=20
>> On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:
>>> Hi authors, hi chairs,
>>>=20
>>> many thanks for this very well written document as well as a good =
write-up from the shepherd!
>>>=20
>>> Before I start the IETF LC call I have two small questions:
>>>=20
>>> 1) Normative references:
>>>=20
>>> I wonder if draft-ietf-rmcat-coupled-cc should be a normative =
reference, especially as it is mentioned in the abstract, but also =
because it probably helps to at least read section 4 (architecture) of =
draft-ietf-rmcat-coupled-cc.
>>=20
>> My understanding is that only normative statements create normative =
references, so the fact that it is mentioned in the abstract or useful =
to read does not make it normative? As I am not so experienced with the =
process I looked for guidelines on this before reviewing the draft and =
this is at least what draft-peterson-informational-normativity-01 =
suggests.
>=20
> Normative references and normative language are two different things. =
A reference should be normative if it is (or part of it) a required read =
to understand the content of the document. E.g. if you write an TCP =
extension the RFC defining the TCP base protocol must be a normative =
reference. So my question is here, do you think that couple congestion =
is a required read to understand this document (I=E2=80=99m asking this =
because there is this architecture section in =
draft-ietf-rmcat-coupled-cc).

I=E2=80=99m not Anna, but at least I think that, despite there being an =
architecture section in draft-ietf-rmcat-coupled-cc, it is not a =
required read to understand draft-ietf-rmcat-sbd-09. It really =
shouldn=E2=80=99t be: SBD is just a mechanism that provides information =
about flows traversing common bottlenecks. Coupled-cc is a mechanism =
that can use it (it doesn=E2=80=99t have to, but if you combine them, =
you can, e.g., couple flows from one sender towards multiple receivers).

Here is an example of how the SBD algorithm can be used independent of =
draft-ietf-rmcat-coupled-cc:

Simone Ferlin, Ozgu Alay, David Hayes, Thomas Dreibholz, Michael Welzl: =
"Revisiting Congestion Control for Multipath TCP with Shared Bottleneck =
Detection", IEEE Infocom 2016, San Francisco, USA, 10-15 April 2016.
http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf =
<http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf>


>>> Further this sentence seems to make avtcore-cc-feedback-message =
should also be a normative reference:
>>> "Timing information described by
>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>>   sender to calculate relative OWD.=E2=80=9C
>>> I don=E2=80=99t think we want to wait for =
avtcore-cc-feedback-message for publication, therefor I would recommend =
to say something about the resolution used in =
avtcore-cc-feedback-message, e.g.
>>> =E2=80=9EFrequent timing information in millisecond resolution as =
described by
>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for =
the
>>>   sender to calculate relative OWD.=E2=80=9C
>>=20
>> =46rom the same reasoning as above, I am not sure that this is a =
normative reference either? But I agree that your proposal to mention =
the resolution is much better! Actually, reading the text now we should =
probably also avoid the lower case should just to not confuse it with =
SHOULD, Perhaps "will be" or "is believed to be" or something similar =
instead of "should be=E2=80=9C.
>=20
> There is no need to avoid lower case should. Actually there is the =
update of RFC2119 which clarifies this. You should probably also use the =
new boilerplate of RFC8174. Forgot to mention that!
>=20
>>=20
>>> 2) I can't remember if this was discussed in the group but actually =
I believe it was not: this document could also be an informational =
document, as it is just one example algorithm but there are no =
dependencies on this scheme otherwise. I also don=E2=80=99t think is =
makes too much sense to think about this proposed algorithm as an =
experiment; if you want to change the algorithm or use a different one =
just do it; this is just a documentation of one proposal. I also assume =
that there is actually not much interest in the group to publish an =
updated version of this algorithm as proposed standard, as such why not =
informational from the beginning=E2=80=A6?
>>>=20
>>> If the authors and the group are uncertain about this point, I=E2=80=99=
m okay to start IETF LC as exp and see if we can get further feedback =
there or from the IESG; =E2=80=9Edowngrading=E2=80=9C to information can =
easily be done with any additional actions at any time.
>>=20
>> This is not something that has been discussed as far as I know, but I =
am not sure what happened in the beginning of the process. Unless the =
authors prefer to have it informational I would not like to change the =
status at this point as this is not something that has been discussed in =
the group. I also do not think it is fully correct to say that SBD does =
not interact with other mechanisms in the network as it can affect =
congestion control and the performance of other flows. So the need to =
verify a sane and useful behavior still seems to be applicable here.
>=20
> I didn=E2=80=99t say it didn=E2=80=99t interact but it does not need =
to be standardized for interoperability.
>=20
> If we would decide to change the status, in agreement with the authors =
of course, I think it would be okay to simply announce it on the mailing =
list. I would not expect to see a lot of discuss there. I will wait for =
feedback from the authors. However, I don=E2=80=99t have a strong =
opinion here.

We believe that Experimental status is more fitting; we looked at the =
checklist here, from which this seems a pretty clear decision to us:
https://www.ietf.org/standards/process/informational-vs-experimental =
<https://www.ietf.org/standards/process/informational-vs-experimental>

Cheers,
Michael


--Apple-Mail=_76AD1241-28D9-4D6F-ADF5-060F8FD3F310
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"">Hi,<div class=3D""><br class=3D""></div><div class=3D"">As an =
author, first of all, thanks for your feedback!</div><div class=3D""><br =
class=3D""></div><div class=3D"">I=E2=80=99m answering a point =
below:</div><div class=3D""><br class=3D""></div><div class=3D""><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Feb 6, 2018, at 9:21 AM, Mirja Kuehlewind (IETF) &lt;<a =
href=3D"mailto:ietf@kuehlewind.net" class=3D"">ietf@kuehlewind.net</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Am 06.02.2018 um 02:18 =
schrieb Anna Brunstrom &lt;<a href=3D"mailto:anna.brunstrom@kau.se" =
class=3D"">anna.brunstrom@kau.se</a>&gt;:<br class=3D""><br class=3D"">Hi =
Mirja, all,<br class=3D""><br class=3D"">Comments inline.<br =
class=3D""><br class=3D"">On 2018-02-02 17:04, Mirja Kuehlewind (IETF) =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">Hi authors, hi =
chairs,<br class=3D""><br class=3D"">many thanks for this very well =
written document as well as a good write-up from the shepherd!<br =
class=3D""><br class=3D"">Before I start the IETF LC call I have two =
small questions:<br class=3D""><br class=3D"">1) Normative =
references:<br class=3D""><br class=3D"">I wonder if =
draft-ietf-rmcat-coupled-cc should be a normative reference, especially =
as it is mentioned in the abstract, but also because it probably helps =
to at least read section 4 (architecture) of =
draft-ietf-rmcat-coupled-cc.<br class=3D""></blockquote><br class=3D"">My =
understanding is that only normative statements create normative =
references, so the fact that it is mentioned in the abstract or useful =
to read does not make it normative? As I am not so experienced with the =
process I looked for guidelines on this before reviewing the draft and =
this is at least what draft-peterson-informational-normativity-01 =
suggests.<br class=3D""></blockquote><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">Normative references and =
normative language are two different things. A reference should be =
normative if it is (or part of it) a required read to understand the =
content of the document. E.g. if you write an TCP extension the RFC =
defining the TCP base protocol must be a normative reference. So my =
question is here, do you think that couple congestion is a required read =
to understand this document (I=E2=80=99m asking this because there is =
this architecture section in draft-ietf-rmcat-coupled-cc).</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>I=E2=80=99m =
not Anna, but at least I think that, despite there being an architecture =
section in draft-ietf-rmcat-coupled-cc, it is not a required read to =
understand&nbsp;draft-ietf-rmcat-sbd-09. It really shouldn=E2=80=99t be: =
SBD is just a mechanism that provides information about flows traversing =
common bottlenecks. Coupled-cc is a mechanism that can use it (it =
doesn=E2=80=99t have to, but if you combine them, you can, e.g., couple =
flows from one sender towards multiple receivers).</div><div><br =
class=3D""></div><div>Here is an example of how the SBD algorithm can be =
used independent of&nbsp;draft-ietf-rmcat-coupled-cc:</div><div><br =
class=3D""></div><div>Simone Ferlin, Ozgu Alay, David Hayes, Thomas =
Dreibholz, Michael Welzl: "Revisiting Congestion Control =
for&nbsp;Multipath TCP with Shared Bottleneck Detection", IEEE Infocom =
2016, San Francisco, USA, 10-15 April 2016.</div><a =
href=3D"http://heim.ifi.uio.no/michawe/research/publications/infocom2016.p=
df" =
class=3D"">http://heim.ifi.uio.no/michawe/research/publications/infocom201=
6.pdf</a></div><div><br class=3D""></div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" class=3D"">Further this sentence =
seems to make avtcore-cc-feedback-message should also be a normative =
reference:<br class=3D"">"Timing information described by<br =
class=3D"">&nbsp;&nbsp;[I-D.ietf-avtcore-cc-feedback-message] should be =
sufficient for the<br class=3D"">&nbsp;&nbsp;sender to calculate =
relative OWD.=E2=80=9C<br class=3D"">I don=E2=80=99t think we want to =
wait for avtcore-cc-feedback-message for publication, therefor I would =
recommend to say something about the resolution used in =
avtcore-cc-feedback-message, e.g.<br class=3D"">=E2=80=9EFrequent timing =
information in millisecond resolution as described by<br =
class=3D"">&nbsp;&nbsp;[I-D.ietf-avtcore-cc-feedback-message] should be =
sufficient for the<br class=3D"">&nbsp;&nbsp;sender to calculate =
relative OWD.=E2=80=9C<br class=3D""></blockquote><br class=3D"">=46rom =
the same reasoning as above, I am not sure that this is a normative =
reference either? But I agree that your proposal to mention the =
resolution is much better! Actually, reading the text now we should =
probably also avoid the lower case should just to not confuse it with =
SHOULD, Perhaps "will be" or "is believed to be" or something similar =
instead of "should be=E2=80=9C.<br class=3D""></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">There is no need to avoid lower case should. =
Actually there is the update of RFC2119 which clarifies this. You should =
probably also use the new boilerplate of RFC8174. Forgot to mention =
that!</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">2) I can't remember if this was discussed in =
the group but actually I believe it was not: this document could also be =
an informational document, as it is just one example algorithm but there =
are no dependencies on this scheme otherwise. I also don=E2=80=99t think =
is makes too much sense to think about this proposed algorithm as an =
experiment; if you want to change the algorithm or use a different one =
just do it; this is just a documentation of one proposal. I also assume =
that there is actually not much interest in the group to publish an =
updated version of this algorithm as proposed standard, as such why not =
informational from the beginning=E2=80=A6?<br class=3D""><br class=3D"">If=
 the authors and the group are uncertain about this point, I=E2=80=99m =
okay to start IETF LC as exp and see if we can get further feedback =
there or from the IESG; =E2=80=9Edowngrading=E2=80=9C to information can =
easily be done with any additional actions at any time.<br =
class=3D""></blockquote><br class=3D"">This is not something that has =
been discussed as far as I know, but I am not sure what happened in the =
beginning of the process. Unless the authors prefer to have it =
informational I would not like to change the status at this point as =
this is not something that has been discussed in the group. I also do =
not think it is fully correct to say that SBD does not interact with =
other mechanisms in the network as it can affect congestion control and =
the performance of other flows. So the need to verify a sane and useful =
behavior still seems to be applicable here.<br class=3D""></blockquote><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">I didn=E2=80=99t say it didn=E2=80=99t interact =
but it does not need to be standardized for interoperability.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">If we would decide to change the status, in =
agreement with the authors of course, I think it would be okay to simply =
announce it on the mailing list. I would not expect to see a lot of =
discuss there. I will wait for feedback from the authors. However, I =
don=E2=80=99t have a strong opinion here.</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>We believe =
that Experimental status is more fitting; we looked at the checklist =
here, from which this seems a pretty clear decision to us:</div><div><a =
href=3D"https://www.ietf.org/standards/process/informational-vs-experiment=
al" =
class=3D"">https://www.ietf.org/standards/process/informational-vs-experim=
ental</a></div><div><br =
class=3D""></div>Cheers,</div><div>Michael</div><div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_76AD1241-28D9-4D6F-ADF5-060F8FD3F310--


From nobody Tue Feb  6 07:30:48 2018
Return-Path: <prvs=057550a7a4=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 452A612D830; Tue,  6 Feb 2018 07:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 ut2U0hS04dTH; Tue,  6 Feb 2018 07:30:42 -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 1CFA212706D; Tue,  6 Feb 2018 07:30:42 -0800 (PST)
To: Michael Welzl <michawe@ifi.uio.no>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
CC: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, <draft-ietf-rmcat-sbd.all@ietf.org>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no>
From: Anna Brunstrom <anna.brunstrom@kau.se>
Message-ID: <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se>
Date: Tue, 6 Feb 2018 16:30:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no>
Content-Type: multipart/alternative; boundary="------------F244758E9836F1462305A790"
Content-Language: en-US
X-ClientProxiedBy: Exch-A2.personal.kau (130.243.19.83) To Exch-A2.personal.kau (130.243.19.83)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/_fbv-437ZICV-FdzRCV5Zg6xJl4>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 15:30:47 -0000

--------------F244758E9836F1462305A790
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

On 2018-02-06 13:34, Michael Welzl wrote:
> Hi,
>
> As an author, first of all, thanks for your feedback!
>
> I’m answering a point below:
>
>
>> On Feb 6, 2018, at 9:21 AM, Mirja Kuehlewind (IETF) 
>> <ietf@kuehlewind.net <mailto:ietf@kuehlewind.net>> wrote:
>>
>>
>>
>>> Am 06.02.2018 um 02:18 schrieb Anna Brunstrom <anna.brunstrom@kau.se 
>>> <mailto:anna.brunstrom@kau.se>>:
>>>
>>> Hi Mirja, all,
>>>
>>> Comments inline.
>>>
>>> On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:
>>>> Hi authors, hi chairs,
>>>>
>>>> many thanks for this very well written document as well as a good 
>>>> write-up from the shepherd!
>>>>
>>>> Before I start the IETF LC call I have two small questions:
>>>>
>>>> 1) Normative references:
>>>>
>>>> I wonder if draft-ietf-rmcat-coupled-cc should be a normative 
>>>> reference, especially as it is mentioned in the abstract, but also 
>>>> because it probably helps to at least read section 4 (architecture) 
>>>> of draft-ietf-rmcat-coupled-cc.
>>>
>>> My understanding is that only normative statements create normative 
>>> references, so the fact that it is mentioned in the abstract or 
>>> useful to read does not make it normative? As I am not so 
>>> experienced with the process I looked for guidelines on this before 
>>> reviewing the draft and this is at least what 
>>> draft-peterson-informational-normativity-01 suggests.
>>
>> Normative references and normative language are two different things. 
>> A reference should be normative if it is (or part of it) a required 
>> read to understand the content of the document. E.g. if you write an 
>> TCP extension the RFC defining the TCP base protocol must be a 
>> normative reference. So my question is here, do you think that couple 
>> congestion is a required read to understand this document (I’m asking 
>> this because there is this architecture section in 
>> draft-ietf-rmcat-coupled-cc).

I did not mean to suggest that normative references and normative 
language were the same. I was referring to these guidelines from the 
draft mentioned above:

/For the benefit of specification authors, the following is a list of 
conditions in which a reference to a document need not be normative://
//   1.  if the source document is itself Informational (not a 
standards-track document, BCP or an Experimental document).//
//   2.  if the referencing statement is not a normative statement; 
i.e., does not prescribes some degree of normative compliance with the 
target document.//
//   3.  if the target document, and in particular any subset scope 
designated by the referencing statement (a section, or what have you), 
contains no normative statements./

Either way, I do not think that coupled congestion control is a required 
read to understand the SBD document.

For the next update the authors may perhaps still consider removing the 
reference from the abstract, as it may in general look a bit odd.

> I’m not Anna, but at least I think that, despite there being an 
> architecture section in draft-ietf-rmcat-coupled-cc, it is not a 
> required read to understand draft-ietf-rmcat-sbd-09. It really 
> shouldn’t be: SBD is just a mechanism that provides information about 
> flows traversing common bottlenecks. Coupled-cc is a mechanism that 
> can use it (it doesn’t have to, but if you combine them, you can, 
> e.g., couple flows from one sender towards multiple receivers).
>
> Here is an example of how the SBD algorithm can be used independent 
> of draft-ietf-rmcat-coupled-cc:
>
> Simone Ferlin, Ozgu Alay, David Hayes, Thomas Dreibholz, Michael 
> Welzl: "Revisiting Congestion Control for Multipath TCP with Shared 
> Bottleneck Detection", IEEE Infocom 2016, San Francisco, USA, 10-15 
> April 2016.
> http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf
>
>
>>>> Further this sentence seems to make avtcore-cc-feedback-message 
>>>> should also be a normative reference:
>>>> "Timing information described by
>>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>>>>   sender to calculate relative OWD.“
>>>> I don’t think we want to wait for avtcore-cc-feedback-message for 
>>>> publication, therefor I would recommend to say something about the 
>>>> resolution used in avtcore-cc-feedback-message, e.g.
>>>> „Frequent timing information in millisecond resolution as described by
>>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>>>>   sender to calculate relative OWD.“
>>>
>>> From the same reasoning as above, I am not sure that this is a 
>>> normative reference either? But I agree that your proposal to 
>>> mention the resolution is much better! Actually, reading the text 
>>> now we should probably also avoid the lower case should just to not 
>>> confuse it with SHOULD, Perhaps "will be" or "is believed to be" or 
>>> something similar instead of "should be“.
>>
>> There is no need to avoid lower case should. Actually there is the 
>> update of RFC2119 which clarifies this. You should probably also use 
>> the new boilerplate of RFC8174. Forgot to mention that!

Ok, good I had missed this. Authors, please add updating the boilerplate 
to the list for the next draft update.

>>
>>>
>>>> 2) I can't remember if this was discussed in the group but actually 
>>>> I believe it was not: this document could also be an informational 
>>>> document, as it is just one example algorithm but there are no 
>>>> dependencies on this scheme otherwise. I also don’t think is makes 
>>>> too much sense to think about this proposed algorithm as an 
>>>> experiment; if you want to change the algorithm or use a different 
>>>> one just do it; this is just a documentation of one proposal. I 
>>>> also assume that there is actually not much interest in the group 
>>>> to publish an updated version of this algorithm as proposed 
>>>> standard, as such why not informational from the beginning…?
>>>>
>>>> If the authors and the group are uncertain about this point, I’m 
>>>> okay to start IETF LC as exp and see if we can get further feedback 
>>>> there or from the IESG; „downgrading“ to information can easily be 
>>>> done with any additional actions at any time.
>>>
>>> This is not something that has been discussed as far as I know, but 
>>> I am not sure what happened in the beginning of the process. Unless 
>>> the authors prefer to have it informational I would not like to 
>>> change the status at this point as this is not something that has 
>>> been discussed in the group. I also do not think it is fully correct 
>>> to say that SBD does not interact with other mechanisms in the 
>>> network as it can affect congestion control and the performance of 
>>> other flows. So the need to verify a sane and useful behavior still 
>>> seems to be applicable here.
>>
>> I didn’t say it didn’t interact but it does not need to be 
>> standardized for interoperability.
>>
>> If we would decide to change the status, in agreement with the 
>> authors of course, I think it would be okay to simply announce it on 
>> the mailing list. I would not expect to see a lot of discuss there. I 
>> will wait for feedback from the authors. However, I don’t have a 
>> strong opinion here.
>
> We believe that Experimental status is more fitting; we looked at the 
> checklist here, from which this seems a pretty clear decision to us:
> https://www.ietf.org/standards/process/informational-vs-experimental

Ok, thanks for the feedback Michael. Then we stay with experimental.

Best Regards,
Anna

>
> Cheers,
> Michael
>


--------------F244758E9836F1462305A790
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 text="#000000" bgcolor="#FFFFFF">
    <p>Hi,<br>
    </p>
    <div class="moz-cite-prefix">On 2018-02-06 13:34, Michael Welzl
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Hi,
      <div class=""><br class="">
      </div>
      <div class="">As an author, first of all, thanks for your
        feedback!</div>
      <div class=""><br class="">
      </div>
      <div class="">I’m answering a point below:</div>
      <div class=""><br class="">
      </div>
      <div class="">
        <div><br class="">
        </div>
        <div>
          <blockquote type="cite" class="">
            <div class="">On Feb 6, 2018, at 9:21 AM, Mirja Kuehlewind
              (IETF) &lt;<a href="mailto:ietf@kuehlewind.net" class=""
                moz-do-not-send="true">ietf@kuehlewind.net</a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class=""><br style="font-family: Helvetica; font-size:
                12px; font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <br style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px;" class="">Am 06.02.2018
                um 02:18 schrieb Anna Brunstrom &lt;<a
                  href="mailto:anna.brunstrom@kau.se" class=""
                  moz-do-not-send="true">anna.brunstrom@kau.se</a>&gt;:<br
                  class="">
                <br class="">
                Hi Mirja, all,<br class="">
                <br class="">
                Comments inline.<br class="">
                <br class="">
                On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:<br
                  class="">
                <blockquote type="cite" class="">Hi authors, hi chairs,<br
                    class="">
                  <br class="">
                  many thanks for this very well written document as
                  well as a good write-up from the shepherd!<br class="">
                  <br class="">
                  Before I start the IETF LC call I have two small
                  questions:<br class="">
                  <br class="">
                  1) Normative references:<br class="">
                  <br class="">
                  I wonder if draft-ietf-rmcat-coupled-cc should be a
                  normative reference, especially as it is mentioned in
                  the abstract, but also because it probably helps to at
                  least read section 4 (architecture) of
                  draft-ietf-rmcat-coupled-cc.<br class="">
                </blockquote>
                <br class="">
                My understanding is that only normative statements
                create normative references, so the fact that it is
                mentioned in the abstract or useful to read does not
                make it normative? As I am not so experienced with the
                process I looked for guidelines on this before reviewing
                the draft and this is at least what
                draft-peterson-informational-normativity-01 suggests.<br
                  class="">
              </blockquote>
              <br style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <span style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; float: none; display:
                inline !important;" class="">Normative references and
                normative language are two different things. A reference
                should be normative if it is (or part of it) a required
                read to understand the content of the document. E.g. if
                you write an TCP extension the RFC defining the TCP base
                protocol must be a normative reference. So my question
                is here, do you think that couple congestion is a
                required read to understand this document (I’m asking
                this because there is this architecture section in
                draft-ietf-rmcat-coupled-cc).</span><br
                style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    I did not mean to suggest that normative references and normative
    language were the same. I was referring to these guidelines from the
    draft mentioned above:<br>
    <br>
    <i>For the benefit of specification authors, the following is a list
      of conditions in which a reference to a document need not be
      normative:</i><i><br>
    </i><i>   1.  if the source document is itself Informational (not a
      standards-track document, BCP or an Experimental document).</i><i><br>
    </i><i>   2.  if the referencing statement is not a normative
      statement; i.e., does not prescribes some degree of normative
      compliance with the target document.</i><i><br>
    </i><i>   3.  if the target document, and in particular any subset
      scope designated by the referencing statement (a section, or what
      have you), contains no normative statements.</i><br>
    <br>
    Either way, I do not think that coupled congestion control is a
    required read to understand the SBD document.<br>
    <br>
    For the next update the authors may perhaps still consider removing
    the reference from the abstract, as it may in general look a bit
    odd.<br>
    <br>
    <blockquote type="cite"
      cite="mid:5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no">
      <div class="">
        <div>
          <div>I’m not Anna, but at least I think that, despite there
            being an architecture section in
            draft-ietf-rmcat-coupled-cc, it is not a required read to
            understand draft-ietf-rmcat-sbd-09. It really shouldn’t be:
            SBD is just a mechanism that provides information about
            flows traversing common bottlenecks. Coupled-cc is a
            mechanism that can use it (it doesn’t have to, but if you
            combine them, you can, e.g., couple flows from one sender
            towards multiple receivers).</div>
          <div><br class="">
          </div>
          <div>Here is an example of how the SBD algorithm can be used
            independent of draft-ietf-rmcat-coupled-cc:</div>
          <div><br class="">
          </div>
          <div>Simone Ferlin, Ozgu Alay, David Hayes, Thomas Dreibholz,
            Michael Welzl: "Revisiting Congestion Control for Multipath
            TCP with Shared Bottleneck Detection", IEEE Infocom 2016,
            San Francisco, USA, 10-15 April 2016.</div>
          <a
href="http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf"
            class="" moz-do-not-send="true">http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf</a></div>
        <div><br class="">
        </div>
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px;" class="">
                <blockquote type="cite" class="">Further this sentence
                  seems to make avtcore-cc-feedback-message should also
                  be a normative reference:<br class="">
                  "Timing information described by<br class="">
                    [I-D.ietf-avtcore-cc-feedback-message] should be
                  sufficient for the<br class="">
                    sender to calculate relative OWD.“<br class="">
                  I don’t think we want to wait for
                  avtcore-cc-feedback-message for publication, therefor
                  I would recommend to say something about the
                  resolution used in avtcore-cc-feedback-message, e.g.<br
                    class="">
                  „Frequent timing information in millisecond resolution
                  as described by<br class="">
                    [I-D.ietf-avtcore-cc-feedback-message] should be
                  sufficient for the<br class="">
                    sender to calculate relative OWD.“<br class="">
                </blockquote>
                <br class="">
                From the same reasoning as above, I am not sure that
                this is a normative reference either? But I agree that
                your proposal to mention the resolution is much better!
                Actually, reading the text now we should probably also
                avoid the lower case should just to not confuse it with
                SHOULD, Perhaps "will be" or "is believed to be" or
                something similar instead of "should be“.<br class="">
              </blockquote>
              <br style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <span style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; float: none; display:
                inline !important;" class="">There is no need to avoid
                lower case should. Actually there is the update of
                RFC2119 which clarifies this. You should probably also
                use the new boilerplate of RFC8174. Forgot to mention
                that!</span><br style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                text-align: start; text-indent: 0px; text-transform:
                none; white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    Ok, good I had missed this. Authors, please add updating the
    boilerplate to the list for the next draft update.<br>
    <br>
    <blockquote type="cite"
      cite="mid:5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no">
      <div class="">
        <div>
          <blockquote type="cite" class="">
            <div class=""><br style="font-family: Helvetica; font-size:
                12px; font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <blockquote type="cite" style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                orphans: auto; text-align: start; text-indent: 0px;
                text-transform: none; white-space: normal; widows: auto;
                word-spacing: 0px; -webkit-text-size-adjust: auto;
                -webkit-text-stroke-width: 0px;" class=""><br class="">
                <blockquote type="cite" class="">2) I can't remember if
                  this was discussed in the group but actually I believe
                  it was not: this document could also be an
                  informational document, as it is just one example
                  algorithm but there are no dependencies on this scheme
                  otherwise. I also don’t think is makes too much sense
                  to think about this proposed algorithm as an
                  experiment; if you want to change the algorithm or use
                  a different one just do it; this is just a
                  documentation of one proposal. I also assume that
                  there is actually not much interest in the group to
                  publish an updated version of this algorithm as
                  proposed standard, as such why not informational from
                  the beginning…?<br class="">
                  <br class="">
                  If the authors and the group are uncertain about this
                  point, I’m okay to start IETF LC as exp and see if we
                  can get further feedback there or from the IESG;
                  „downgrading“ to information can easily be done with
                  any additional actions at any time.<br class="">
                </blockquote>
                <br class="">
                This is not something that has been discussed as far as
                I know, but I am not sure what happened in the beginning
                of the process. Unless the authors prefer to have it
                informational I would not like to change the status at
                this point as this is not something that has been
                discussed in the group. I also do not think it is fully
                correct to say that SBD does not interact with other
                mechanisms in the network as it can affect congestion
                control and the performance of other flows. So the need
                to verify a sane and useful behavior still seems to be
                applicable here.<br class="">
              </blockquote>
              <br style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <span style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; float: none; display:
                inline !important;" class="">I didn’t say it didn’t
                interact but it does not need to be standardized for
                interoperability.</span><br style="font-family:
                Helvetica; font-size: 12px; font-style: normal;
                font-variant-caps: normal; font-weight: normal;
                letter-spacing: normal; text-align: start; text-indent:
                0px; text-transform: none; white-space: normal;
                word-spacing: 0px; -webkit-text-stroke-width: 0px;"
                class="">
              <br style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
              <span style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; float: none; display:
                inline !important;" class="">If we would decide to
                change the status, in agreement with the authors of
                course, I think it would be okay to simply announce it
                on the mailing list. I would not expect to see a lot of
                discuss there. I will wait for feedback from the
                authors. However, I don’t have a strong opinion here.</span><br
                style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
            </div>
          </blockquote>
          <div><br class="">
          </div>
          <div>We believe that Experimental status is more fitting; we
            looked at the checklist here, from which this seems a pretty
            clear decision to us:</div>
          <div><a
href="https://www.ietf.org/standards/process/informational-vs-experimental"
              class="" moz-do-not-send="true">https://www.ietf.org/standards/process/informational-vs-experimental</a></div>
        </div>
      </div>
    </blockquote>
    <br>
    Ok, thanks for the feedback Michael. Then we stay with experimental.<br>
    <br>
    Best Regards,<br>
    Anna<br>
    <br>
    <blockquote type="cite"
      cite="mid:5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no">
      <div class="">
        <div>
          <div><br class="">
          </div>
          Cheers,</div>
        <div>Michael</div>
        <div><br class="">
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------F244758E9836F1462305A790--


From nobody Tue Feb  6 07:33:33 2018
Return-Path: <michawe@ifi.uio.no>
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 8CA9C12E055; Tue,  6 Feb 2018 07:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CEseziN7do7O; Tue,  6 Feb 2018 07:33:21 -0800 (PST)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 E9F3612E872; Tue,  6 Feb 2018 07:33:20 -0800 (PST)
Received: from mail-mx01.uio.no ([129.240.10.26]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej5FG-000GF3-DA; Tue, 06 Feb 2018 16:33:18 +0100
Received: from 93-58-133-64.ip158.fastwebnet.it ([93.58.133.64] helo=[10.0.0.4]) by mail-mx01.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej5FD-0003Xu-Au; Tue, 06 Feb 2018 16:33:17 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <1E9479C1-6B02-4D46-8B7C-8791BFD7E744@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2869A284-0579-405F-98C7-5F40BC8120E4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 6 Feb 2018 16:33:12 +0100
In-Reply-To: <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se>
Cc: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
To: Anna Brunstrom <anna.brunstrom@kau.se>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no> <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se>
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx01.uio.no: 93.58.133.64 is neither permitted nor denied by domain of ifi.uio.no) client-ip=93.58.133.64;  envelope-from=michawe@ifi.uio.no; helo=[10.0.0.4]; 
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 0C55A1E8D08B6536BF94068D2F4039CF59631672
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/-SHPalXIs58R9cSmO32OT9QQLOg>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 15:33:23 -0000

--Apple-Mail=_2869A284-0579-405F-98C7-5F40BC8120E4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

(..)

> Either way, I do not think that coupled congestion control is a =
required read to understand the SBD document.
>=20
> For the next update the authors may perhaps still consider removing =
the reference from the abstract, as it may in general look a bit odd.

ACK; I agree.


>>> There is no need to avoid lower case should. Actually there is the =
update of RFC2119 which clarifies this. You should probably also use the =
new boilerplate of RFC8174. Forgot to mention that!
>=20
> Ok, good I had missed this. Authors, please add updating the =
boilerplate to the list for the next draft update.

and ACK.

Thanks!

Cheers,
Michael


--Apple-Mail=_2869A284-0579-405F-98C7-5F40BC8120E4
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">(..)</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">
    Either way, I do not think that coupled congestion control is a
    required read to understand the SBD document.<br class="">
    <br class="">
    For the next update the authors may perhaps still consider removing
    the reference from the abstract, as it may in general look a bit
    odd.<br class=""></div></div></blockquote><div><br class=""></div>ACK; I agree.</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><blockquote type="cite" cite="mid:5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">
              <span style="font-family: Helvetica; font-size: 12px;
                font-style: normal; font-variant-caps: normal;
                font-weight: normal; letter-spacing: normal; text-align:
                start; text-indent: 0px; text-transform: none;
                white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px; float: none; display:
                inline !important;" class="">There is no need to avoid
                lower case should. Actually there is the update of
                RFC2119 which clarifies this. You should probably also
                use the new boilerplate of RFC8174. Forgot to mention
                that!</span><br style="font-family: Helvetica;
                font-size: 12px; font-style: normal; font-variant-caps:
                normal; font-weight: normal; letter-spacing: normal;
                text-align: start; text-indent: 0px; text-transform:
                none; white-space: normal; word-spacing: 0px;
                -webkit-text-stroke-width: 0px;" class="">
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br class="">
    Ok, good I had missed this. Authors, please add updating the
    boilerplate to the list for the next draft update.<br class=""></div></div></blockquote><div><br class=""></div>and ACK.</div><div><br class=""></div><div>Thanks!</div><div><br class=""></div><div>Cheers,</div><div>Michael</div></div><div><br class=""></div></body></html>
--Apple-Mail=_2869A284-0579-405F-98C7-5F40BC8120E4--


From nobody Tue Feb  6 07:59:20 2018
Return-Path: <ietf@kuehlewind.net>
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 3578212D853 for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 07:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 PRy6poJRFsOs for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 07:59:15 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74D9512D849 for <rmcat@ietf.org>; Tue,  6 Feb 2018 07:59:14 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=EClwY5Ef00lVdQN+/oaieUxNvDZAdApxCkz6Ex9Vb7oTaLnHynh4nlbC2qgPITGd8XILTy/8QPSzhXhICoZ8cf4ojBRCvbh/M8R7DvflWoraQwXJdCxFocdCicS8EU/rfghbO0gmVKZS5OPAmpdNp+jGSwjeznVXp8kU2fJJDgM=; h=Received:Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:Content-Transfer-Encoding:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 5513 invoked from network); 6 Feb 2018 16:59:12 +0100
Received: from nb-10688.ethz.ch (HELO ?82.130.103.20?) (82.130.103.20) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 6 Feb 2018 16:59:12 +0100
To: Anna Brunstrom <anna.brunstrom@kau.se>, Michael Welzl <michawe@ifi.uio.no>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no> <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <c0b1e043-8a4c-140f-ba39-7abe44539a8d@kuehlewind.net>
Date: Tue, 6 Feb 2018 16:59:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-PPP-Message-ID: <20180206155912.5505.48109@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/J-2rdJmXnurdlOZACTHWPA0ehDY>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 15:59:19 -0000

Hi Anna,

see below.

On 06.02.2018 16:30, Anna Brunstrom wrote:
> Hi,
> 
> On 2018-02-06 13:34, Michael Welzl wrote:
>> Hi,
>>
>> As an author, first of all, thanks for your feedback!
>>
>> I’m answering a point below:
>>
>>
>>> On Feb 6, 2018, at 9:21 AM, Mirja Kuehlewind (IETF) 
>>> <ietf@kuehlewind.net <mailto:ietf@kuehlewind.net>> wrote:
>>>
>>>
>>>
>>>> Am 06.02.2018 um 02:18 schrieb Anna Brunstrom <anna.brunstrom@kau.se 
>>>> <mailto:anna.brunstrom@kau.se>>:
>>>>
>>>> Hi Mirja, all,
>>>>
>>>> Comments inline.
>>>>
>>>> On 2018-02-02 17:04, Mirja Kuehlewind (IETF) wrote:
>>>>> Hi authors, hi chairs,
>>>>>
>>>>> many thanks for this very well written document as well as a good 
>>>>> write-up from the shepherd!
>>>>>
>>>>> Before I start the IETF LC call I have two small questions:
>>>>>
>>>>> 1) Normative references:
>>>>>
>>>>> I wonder if draft-ietf-rmcat-coupled-cc should be a normative 
>>>>> reference, especially as it is mentioned in the abstract, but also 
>>>>> because it probably helps to at least read section 4 (architecture) 
>>>>> of draft-ietf-rmcat-coupled-cc.
>>>>
>>>> My understanding is that only normative statements create normative 
>>>> references, so the fact that it is mentioned in the abstract or 
>>>> useful to read does not make it normative? As I am not so 
>>>> experienced with the process I looked for guidelines on this before 
>>>> reviewing the draft and this is at least what 
>>>> draft-peterson-informational-normativity-01 suggests.
>>>
>>> Normative references and normative language are two different things. 
>>> A reference should be normative if it is (or part of it) a required 
>>> read to understand the content of the document. E.g. if you write an 
>>> TCP extension the RFC defining the TCP base protocol must be a 
>>> normative reference. So my question is here, do you think that couple 
>>> congestion is a required read to understand this document (I’m asking 
>>> this because there is this architecture section in 
>>> draft-ietf-rmcat-coupled-cc).
> 
> I did not mean to suggest that normative references and normative 
> language were the same. I was referring to these guidelines from the 
> draft mentioned above:

So that document is an 10 year old expired draft and not an RFC but let 
me reply to these points below to avoid future confusion:

> 
> /For the benefit of specification authors, the following is a list of 
> conditions in which a reference to a document need not be normative://
> //   1.  if the source document is itself Informational (not a 
> standards-track document, BCP or an Experimental document).//

This is simply not true. If a "high-order" doc references a 
"lower-order" doc normatively, this is called a down ref and needs to be 
call out in the IETF last call to explicitly make people aware of this 
but it can still be done if it is the right thing to do. The problem 
here is that informational as well as experimental documents do not need 
to have IETF consensus, however, we usually run the same process for all 
the docs so effectively they usually also have IETF consensus.

> //   2.  if the referencing statement is not a normative statement; 
> i.e., does not prescribes some degree of normative compliance with the 
> target document.//

I'm actually not sure what this means. However, if a documents repeats a 
normative statement that was made in a different document that does also 
not automatically mean that this doc has to be referenced normatively 
because if the statement on its own is understandable as such without 
reading the other doc that is fine as well. However, usually it is 
better practice to not repeat the statement normatively (because then 
you have to change two independent docs and keep the knowledge that you 
have to do that, if you ever would want to change that statement). So it 
is better explain the statement non-normatively and refer to the 
original doc normatively instead.

> //   3.  if the target document, and in particular any subset scope 
> designated by the referencing statement (a section, or what have you), 
> contains no normative statements./

This is just not true. If you need to read that section to be able to 
understand the (normative) content of the current doc, which mainly 
means you need that information to implement the current spec correctly, 
it must be normative. This is the bit where we often have discussions 
about terminology. If the terminology that you use if defined in a 
different document and it is not possible to understand the spec in this 
doc without knowing the terminology that's a normative reference. If you 
want to avoid that reference for some reason, you have to copy the 
terminology into the current doc.

> 
> Either way, I do not think that coupled congestion control is a required 
> read to understand the SBD document.

Okay. Just wanted to double-check!

> 
> For the next update the authors may perhaps still consider removing the 
> reference from the abstract, as it may in general look a bit odd.

Yes. I agree. They could also try and re-read and try to understand if 
the intro is understandable without knowing the architecture of 
draft-ietf-rmcat-coupled-cc and if not maybe add a bit more explanation. 
I actually also believe that the text as it is might be fine. I just 
wasn't sure, so I thought I might ask and see if you or the authors have 
further opinions.

> 
>> I’m not Anna, but at least I think that, despite there being an 
>> architecture section in draft-ietf-rmcat-coupled-cc, it is not a 
>> required read to understand draft-ietf-rmcat-sbd-09. It really 
>> shouldn’t be: SBD is just a mechanism that provides information about 
>> flows traversing common bottlenecks. Coupled-cc is a mechanism that 
>> can use it (it doesn’t have to, but if you combine them, you can, 
>> e.g., couple flows from one sender towards multiple receivers).
>>
>> Here is an example of how the SBD algorithm can be used independent 
>> of draft-ietf-rmcat-coupled-cc:
>>
>> Simone Ferlin, Ozgu Alay, David Hayes, Thomas Dreibholz, Michael 
>> Welzl: "Revisiting Congestion Control for Multipath TCP with Shared 
>> Bottleneck Detection", IEEE Infocom 2016, San Francisco, USA, 10-15 
>> April 2016.
>> http://heim.ifi.uio.no/michawe/research/publications/infocom2016.pdf
>>
>>
>>>>> Further this sentence seems to make avtcore-cc-feedback-message 
>>>>> should also be a normative reference:
>>>>> "Timing information described by
>>>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>>>>>   sender to calculate relative OWD.“
>>>>> I don’t think we want to wait for avtcore-cc-feedback-message for 
>>>>> publication, therefor I would recommend to say something about the 
>>>>> resolution used in avtcore-cc-feedback-message, e.g.
>>>>> „Frequent timing information in millisecond resolution as described by
>>>>>   [I-D.ietf-avtcore-cc-feedback-message] should be sufficient for the
>>>>>   sender to calculate relative OWD.“
>>>>
>>>> From the same reasoning as above, I am not sure that this is a 
>>>> normative reference either? But I agree that your proposal to 
>>>> mention the resolution is much better! Actually, reading the text 
>>>> now we should probably also avoid the lower case should just to not 
>>>> confuse it with SHOULD, Perhaps "will be" or "is believed to be" or 
>>>> something similar instead of "should be“.
>>>
>>> There is no need to avoid lower case should. Actually there is the 
>>> update of RFC2119 which clarifies this. You should probably also use 
>>> the new boilerplate of RFC8174. Forgot to mention that!
> 
> Ok, good I had missed this. Authors, please add updating the boilerplate 
> to the list for the next draft update.
> 
>>>
>>>>
>>>>> 2) I can't remember if this was discussed in the group but actually 
>>>>> I believe it was not: this document could also be an informational 
>>>>> document, as it is just one example algorithm but there are no 
>>>>> dependencies on this scheme otherwise. I also don’t think is makes 
>>>>> too much sense to think about this proposed algorithm as an 
>>>>> experiment; if you want to change the algorithm or use a different 
>>>>> one just do it; this is just a documentation of one proposal. I 
>>>>> also assume that there is actually not much interest in the group 
>>>>> to publish an updated version of this algorithm as proposed 
>>>>> standard, as such why not informational from the beginning…?
>>>>>
>>>>> If the authors and the group are uncertain about this point, I’m 
>>>>> okay to start IETF LC as exp and see if we can get further feedback 
>>>>> there or from the IESG; „downgrading“ to information can easily be 
>>>>> done with any additional actions at any time.
>>>>
>>>> This is not something that has been discussed as far as I know, but 
>>>> I am not sure what happened in the beginning of the process. Unless 
>>>> the authors prefer to have it informational I would not like to 
>>>> change the status at this point as this is not something that has 
>>>> been discussed in the group. I also do not think it is fully correct 
>>>> to say that SBD does not interact with other mechanisms in the 
>>>> network as it can affect congestion control and the performance of 
>>>> other flows. So the need to verify a sane and useful behavior still 
>>>> seems to be applicable here.
>>>
>>> I didn’t say it didn’t interact but it does not need to be 
>>> standardized for interoperability.
>>>
>>> If we would decide to change the status, in agreement with the 
>>> authors of course, I think it would be okay to simply announce it on 
>>> the mailing list. I would not expect to see a lot of discuss there. I 
>>> will wait for feedback from the authors. However, I don’t have a 
>>> strong opinion here.
>>
>> We believe that Experimental status is more fitting; we looked at the 
>> checklist here, from which this seems a pretty clear decision to us:
>> https://www.ietf.org/standards/process/informational-vs-experimental

So I would like to add something here. I don't know why you think from 
this text that experimental is the better fit, but I think both are 
suitable and therefore I'm also fine to move on with experimental but I 
wanted to make sure that this has been considered. So both informational 
and experimental do not need to have IETF consensus (but as I said they 
usually have); so no difference in this aspect. Experimental docs are 
usually specs that are not ready for proposed standard yet but 
experimentation in the Internet is needed to move forward. However, sbd 
is not really a spec, it's more a documentation of a mechansims. As such 
I think it could also be moved forward as informational. The difference 
for me at this point is, are there any plans to move it forward to 
proposed standard as any point in the future, or do we keep this 
document as a documentation of the proposed mechanism and probably will 
never touch it again?

> 
> Ok, thanks for the feedback Michael. Then we stay with experimental.

Assuming, we have a decision on the indented status (going for exp as 
the current version said). Would you like to submit another update 
before IETF last call, or should I just start the IETF last right away?

Mirja



> 
> Best Regards,
> Anna
> 
>>
>> Cheers,
>> Michael
>>
> 


From nobody Tue Feb  6 09:07:45 2018
Return-Path: <michawe@ifi.uio.no>
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 88F65126CF6 for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 09:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 oYA1vrSCA-5F for <rmcat@ietfa.amsl.com>; Tue,  6 Feb 2018 09:07:42 -0800 (PST)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 6CEFB12D84F for <rmcat@ietf.org>; Tue,  6 Feb 2018 09:07:42 -0800 (PST)
Received: from mail-mx04.uio.no ([129.240.10.25]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej6iZ-00083y-Ac; Tue, 06 Feb 2018 18:07:39 +0100
Received: from 93-58-133-64.ip158.fastwebnet.it ([93.58.133.64] helo=[10.0.0.4]) by mail-mx04.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1ej6iW-000GMC-BC; Tue, 06 Feb 2018 18:07:39 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <859142F1-3EE6-44E2-875F-77D0CC9C982A@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D52F6E35-7A9A-4588-890A-538004A17995"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 6 Feb 2018 18:07:33 +0100
In-Reply-To: <c0b1e043-8a4c-140f-ba39-7abe44539a8d@kuehlewind.net>
Cc: Anna Brunstrom <anna.brunstrom@kau.se>, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
To: =?utf-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no> <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se> <c0b1e043-8a4c-140f-ba39-7abe44539a8d@kuehlewind.net>
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx04.uio.no: 93.58.133.64 is neither permitted nor denied by domain of ifi.uio.no) client-ip=93.58.133.64;  envelope-from=michawe@ifi.uio.no; helo=[10.0.0.4]; 
X-UiO-Spam-info: not spam, SpamAssassin (score=-4.9, required=5.0, autolearn=disabled, AWL=0.083, HTML_MESSAGE=0.001, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 4F7412587CDEA5E524FB46F36C39F762838D03B5
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/YTtCdahre8bDRk957LSxLjjMyYA>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 17:07:44 -0000

--Apple-Mail=_D52F6E35-7A9A-4588-890A-538004A17995
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

I=E2=80=99m cutting away some things and only answering on the part that =
speaks to me as one of the authors:


>>> We believe that Experimental status is more fitting; we looked at =
the checklist here, from which this seems a pretty clear decision to us:
>>> https://www.ietf.org/standards/process/informational-vs-experimental
>=20
> So I would like to add something here. I don't know why you think from =
this text that experimental is the better fit, but I think both are =
suitable and therefore I'm also fine to move on with experimental but I =
wanted to make sure that this has been considered.

1. If it can't be practiced, it's Informational.  =3D> this is an =
algorithm, it can be practiced.
2. If it's not going to be changed no matter what the result is, it's =
Informational  =3D> that=E2=80=99s not the case, see my answer below =
regarding =E2=80=9Cwill never touch it again=E2=80=9D.
3. (..)work that could be practiced, was developed in the IETF, has been =
dropped for some reason, but is being published for the record(..) =
Informational or Historic  =3D> that=E2=80=99s also not the case.
4. If the IETF may publish something based on this on the standards =
track once we know how well this one works, it's Experimental  =3D> =
again the point below, I do think this can go to standards track after =
more experience.
5. If the document contains implicit or explicit success/failure =
criteria, and it's clear that the outcome can be used as the basis for a =
recommendation to the IETF community, it's Experimental  =3D> well =
there=E2=80=99s a section on expected feedback from experiments.


> So both informational and experimental do not need to have IETF =
consensus (but as I said they usually have); so no difference in this =
aspect. Experimental docs are usually specs that are not ready for =
proposed standard yet but experimentation in the Internet is needed to =
move forward. However, sbd is not really a spec, it's more a =
documentation of a mechansims. As such I think it could also be moved =
forward as informational.

I don=E2=80=99t see what makes you say that this isn=E2=80=99t really a =
spec? It should be, it=E2=80=99s meant to be a spec.


> The difference for me at this point is, are there any plans to move it =
forward to proposed standard as any point in the future, or do we keep =
this document as a documentation of the proposed mechanism and probably =
will never touch it again?

Well, it=E2=80=99s certainly my plan as one of the authors to move this =
forward to proposed standard at some point in the future. We=E2=80=99re =
actively working on this.


>> Ok, thanks for the feedback Michael. Then we stay with experimental.
>=20
> Assuming, we have a decision on the indented status (going for exp as =
the current version said). Would you like to submit another update =
before IETF last call, or should I just start the IETF last right away?

We=E2=80=99d like to do another update - there were some recommendations =
here: removing the reference to coupled-cc from the abstract, different =
boilerplate and your editorial comments. This may take a little bit =
(I=E2=80=99m not the only author).

Cheers,
Michael


--Apple-Mail=_D52F6E35-7A9A-4588-890A-538004A17995
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"">Hi,<div class=3D""><br class=3D""></div><div class=3D"">I=E2=80=
=99m cutting away some things and only answering on the part that speaks =
to me as one of the authors:</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote type=3D"cite" =
class=3D"">We believe that Experimental status is more fitting; we =
looked at the checklist here, from which this seems a pretty clear =
decision to us:<br class=3D""><a =
href=3D"https://www.ietf.org/standards/process/informational-vs-experiment=
al" =
class=3D"">https://www.ietf.org/standards/process/informational-vs-experim=
ental</a><br class=3D""></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">So I would like to add something here. I don't =
know why you think from this text that experimental is the better fit, =
but I think both are suitable and therefore I'm also fine to move on =
with experimental but I wanted to make sure that this has been =
considered.</span></div></blockquote><div><br class=3D""></div><div>1. =
If it can't be practiced, it's Informational. &nbsp;=3D&gt; this is an =
algorithm, it can be practiced.</div><div>2.&nbsp;If it's not going to =
be changed no matter what the result is, it's Informational &nbsp;=3D&gt; =
that=E2=80=99s not the case, see my answer below regarding =E2=80=9Cwill =
never touch it again=E2=80=9D.</div><div>3. (..)work that could be =
practiced, was developed in the IETF, has been dropped for some reason, =
but is being&nbsp;published for the record(..) Informational or Historic =
&nbsp;=3D&gt; that=E2=80=99s also not the case.</div><div>4. If the IETF =
may publish something based on this on the standards track once we know =
how well this one works,&nbsp;it's Experimental &nbsp;=3D&gt; again the =
point below, I do think this can go to standards track after more =
experience.</div><div>5. If the document contains implicit or explicit =
success/failure criteria, and it's clear that the outcome can be =
used&nbsp;as the basis for a recommendation to the IETF community, it's =
Experimental &nbsp;=3D&gt; well there=E2=80=99s a section on expected =
feedback from experiments.</div><div><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D""> So both informational and =
experimental do not need to have IETF consensus (but as I said they =
usually have); so no difference in this aspect. Experimental docs are =
usually specs that are not ready for proposed standard yet but =
experimentation in the Internet is needed to move forward. However, sbd =
is not really a spec, it's more a documentation of a mechansims. As such =
I think it could also be moved forward as =
informational.</span></div></blockquote><div><br class=3D""></div><div>I =
don=E2=80=99t see what makes you say that this isn=E2=80=99t really a =
spec? It should be, it=E2=80=99s meant to be a spec.</div><div><br =
class=3D""></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D""> The difference for me at this point is, are =
there any plans to move it forward to proposed standard as any point in =
the future, or do we keep this document as a documentation of the =
proposed mechanism and probably will never touch it again?</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>Well, =
it=E2=80=99s certainly my plan as one of the authors to move this =
forward to proposed standard at some point in the future. We=E2=80=99re =
actively working on this.</div><div><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Ok, thanks for the feedback =
Michael. Then we stay with experimental.<br class=3D""></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Assuming, we have a decision on the indented =
status (going for exp as the current version said). Would you like to =
submit another update before IETF last call, or should I just start the =
IETF last right away?</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div><div>We=E2=80=99d =
like to do another update - there were some recommendations here: =
removing the reference to coupled-cc from the abstract, different =
boilerplate and your editorial comments. This may take a little bit =
(I=E2=80=99m not the only author).</div><div><br =
class=3D""></div><div>Cheers,</div><div>Michael</div><div><br =
class=3D""></div></div></div></body></html>=

--Apple-Mail=_D52F6E35-7A9A-4588-890A-538004A17995--


From nobody Wed Feb  7 01:26:34 2018
Return-Path: <ietf@kuehlewind.net>
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 6D6A5126D74 for <rmcat@ietfa.amsl.com>; Wed,  7 Feb 2018 01:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 FjCYFBjCxAYk for <rmcat@ietfa.amsl.com>; Wed,  7 Feb 2018 01:26:30 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F27BB126CD6 for <rmcat@ietf.org>; Wed,  7 Feb 2018 01:26:29 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=lHk1RDa+/OEsV4rIlgTpUKyrcAZqlNUdSBy+7/D9wC8sCyqiwOi2cK7ceEqCYFjeg0x8KaWo6X0ea3JA40s19jBHfZW27F5rGviWtlh2BAhMPsFxfroXgcxtsLWw/pPlKUUmm09+8LjFtzU3LybEp0TbumTuIHqZ5EH2Wh+HQZA=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 4542 invoked from network); 7 Feb 2018 10:25:27 +0100
Received: from 178-83-155-34.dynamic.hispeed.ch (HELO ?192.168.220.145?) (178.83.155.34) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 7 Feb 2018 10:25:26 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <859142F1-3EE6-44E2-875F-77D0CC9C982A@ifi.uio.no>
Date: Wed, 7 Feb 2018 10:25:25 +0100
Cc: Anna Brunstrom <anna.brunstrom@kau.se>, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <727594E8-0B83-420F-858C-1081F38BE72A@kuehlewind.net>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no> <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se> <c0b1e043-8a4c-140f-ba39-7abe44539a8d@kuehlewind.net> <859142F1-3EE6-44E2-875F-77D0CC9C982A@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180207092526.4535.19268@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/Sf9Bok3s-qffKgnTNZIYucn6gdA>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Feb 2018 09:26:32 -0000

Hi Michael,

that=E2=80=99s okay. Please go ahead and make the updates. I moved the =
draft to the later telechat.

Mirja

P.S.: By spec I actually meant protocol spec=E2=80=A6
=20

> Am 06.02.2018 um 18:07 schrieb Michael Welzl <michawe@ifi.uio.no>:
>=20
> Hi,
>=20
> I=E2=80=99m cutting away some things and only answering on the part =
that speaks to me as one of the authors:
>=20
>=20
>>>> We believe that Experimental status is more fitting; we looked at =
the checklist here, from which this seems a pretty clear decision to us:
>>>> =
https://www.ietf.org/standards/process/informational-vs-experimental
>>=20
>> So I would like to add something here. I don't know why you think =
from this text that experimental is the better fit, but I think both are =
suitable and therefore I'm also fine to move on with experimental but I =
wanted to make sure that this has been considered.
>=20
> 1. If it can't be practiced, it's Informational.  =3D> this is an =
algorithm, it can be practiced.
> 2. If it's not going to be changed no matter what the result is, it's =
Informational  =3D> that=E2=80=99s not the case, see my answer below =
regarding =E2=80=9Cwill never touch it again=E2=80=9D.
> 3. (..)work that could be practiced, was developed in the IETF, has =
been dropped for some reason, but is being published for the record(..) =
Informational or Historic  =3D> that=E2=80=99s also not the case.
> 4. If the IETF may publish something based on this on the standards =
track once we know how well this one works, it's Experimental  =3D> =
again the point below, I do think this can go to standards track after =
more experience.
> 5. If the document contains implicit or explicit success/failure =
criteria, and it's clear that the outcome can be used as the basis for a =
recommendation to the IETF community, it's Experimental  =3D> well =
there=E2=80=99s a section on expected feedback from experiments.
>=20
>=20
>> So both informational and experimental do not need to have IETF =
consensus (but as I said they usually have); so no difference in this =
aspect. Experimental docs are usually specs that are not ready for =
proposed standard yet but experimentation in the Internet is needed to =
move forward. However, sbd is not really a spec, it's more a =
documentation of a mechansims. As such I think it could also be moved =
forward as informational.
>=20
> I don=E2=80=99t see what makes you say that this isn=E2=80=99t really =
a spec? It should be, it=E2=80=99s meant to be a spec.
>=20
>=20
>> The difference for me at this point is, are there any plans to move =
it forward to proposed standard as any point in the future, or do we =
keep this document as a documentation of the proposed mechanism and =
probably will never touch it again?
>=20
> Well, it=E2=80=99s certainly my plan as one of the authors to move =
this forward to proposed standard at some point in the future. We=E2=80=99=
re actively working on this.
>=20
>=20
>>> Ok, thanks for the feedback Michael. Then we stay with experimental.
>>=20
>> Assuming, we have a decision on the indented status (going for exp as =
the current version said). Would you like to submit another update =
before IETF last call, or should I just start the IETF last right away?
>=20
> We=E2=80=99d like to do another update - there were some =
recommendations here: removing the reference to coupled-cc from the =
abstract, different boilerplate and your editorial comments. This may =
take a little bit (I=E2=80=99m not the only author).
>=20
> Cheers,
> Michael
>=20


From nobody Mon Feb 12 13:18:01 2018
Return-Path: <ietf@kuehlewind.net>
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 643B012D963 for <rmcat@ietfa.amsl.com>; Mon, 12 Feb 2018 13:17:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 Skdx1EVAjmaf for <rmcat@ietfa.amsl.com>; Mon, 12 Feb 2018 13:17:57 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F4C312704A for <rmcat@ietf.org>; Mon, 12 Feb 2018 13:17:57 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=AP/Ed0tleD0gPb3QXIb48vWdSIaOeJMbxjrvzNqvUXQbqYyyNd3SOz43RJR98ZlIYbxYPcNGXHQOFzqUVA1nDCeoD5YpTDddDXwHZB4Csc8CuxwaJgAbhA0w+yGMPYB0Wyonmqn4SaGc/bPuHvIE3tfLIWa0i7T8L9RIxBYa+Zc=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 19299 invoked from network); 12 Feb 2018 22:11:14 +0100
Received: from mue-88-130-61-078.dsl.tropolys.de (HELO ?192.168.178.33?) (88.130.61.78) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 12 Feb 2018 22:11:14 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <727594E8-0B83-420F-858C-1081F38BE72A@kuehlewind.net>
Date: Mon, 12 Feb 2018 22:11:13 +0100
Cc: Anna Brunstrom <anna.brunstrom@kau.se>, "rmcat WG (rmcat@ietf.org)" <rmcat@ietf.org>, draft-ietf-rmcat-sbd.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B083DFF2-2386-445C-82B9-1455E50EA673@kuehlewind.net>
References: <227D2FC6-A331-4311-A8BF-E783B9F0B8EB@kuehlewind.net> <1b78e928-3fb3-7959-552a-e4c9bbcd7af6@kau.se> <1E245578-0EC9-4496-A683-9FBFBA1FC5C2@kuehlewind.net> <5E43ED74-2BBF-4E1E-8C4B-21D2D718E2F2@ifi.uio.no> <fcdafb8d-d3ff-5bd0-f502-9baea1dac615@kau.se> <c0b1e043-8a4c-140f-ba39-7abe44539a8d@kuehlewind.net> <859142F1-3EE6-44E2-875F-77D0CC9C982A@ifi.uio.no> <727594E8-0B83-420F-858C-1081F38BE72A@kuehlewind.net>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180212211114.19292.19775@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/vbHnHBUezScobYbD-7RIYvMx0S0>
Subject: Re: [rmcat] AD review of draft-ietf-rmcat-sbd-09
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Feb 2018 21:17:59 -0000

Hi,

when will you likely submit an update?

Mirja


> Am 07.02.2018 um 10:25 schrieb Mirja Kuehlewind (IETF) =
<ietf@kuehlewind.net>:
>=20
> Hi Michael,
>=20
> that=E2=80=99s okay. Please go ahead and make the updates. I moved the =
draft to the later telechat.
>=20
> Mirja
>=20
> P.S.: By spec I actually meant protocol spec=E2=80=A6
>=20
>=20
>> Am 06.02.2018 um 18:07 schrieb Michael Welzl <michawe@ifi.uio.no>:
>>=20
>> Hi,
>>=20
>> I=E2=80=99m cutting away some things and only answering on the part =
that speaks to me as one of the authors:
>>=20
>>=20
>>>>> We believe that Experimental status is more fitting; we looked at =
the checklist here, from which this seems a pretty clear decision to us:
>>>>> =
https://www.ietf.org/standards/process/informational-vs-experimental
>>>=20
>>> So I would like to add something here. I don't know why you think =
from this text that experimental is the better fit, but I think both are =
suitable and therefore I'm also fine to move on with experimental but I =
wanted to make sure that this has been considered.
>>=20
>> 1. If it can't be practiced, it's Informational.  =3D> this is an =
algorithm, it can be practiced.
>> 2. If it's not going to be changed no matter what the result is, it's =
Informational  =3D> that=E2=80=99s not the case, see my answer below =
regarding =E2=80=9Cwill never touch it again=E2=80=9D.
>> 3. (..)work that could be practiced, was developed in the IETF, has =
been dropped for some reason, but is being published for the record(..) =
Informational or Historic  =3D> that=E2=80=99s also not the case.
>> 4. If the IETF may publish something based on this on the standards =
track once we know how well this one works, it's Experimental  =3D> =
again the point below, I do think this can go to standards track after =
more experience.
>> 5. If the document contains implicit or explicit success/failure =
criteria, and it's clear that the outcome can be used as the basis for a =
recommendation to the IETF community, it's Experimental  =3D> well =
there=E2=80=99s a section on expected feedback from experiments.
>>=20
>>=20
>>> So both informational and experimental do not need to have IETF =
consensus (but as I said they usually have); so no difference in this =
aspect. Experimental docs are usually specs that are not ready for =
proposed standard yet but experimentation in the Internet is needed to =
move forward. However, sbd is not really a spec, it's more a =
documentation of a mechansims. As such I think it could also be moved =
forward as informational.
>>=20
>> I don=E2=80=99t see what makes you say that this isn=E2=80=99t really =
a spec? It should be, it=E2=80=99s meant to be a spec.
>>=20
>>=20
>>> The difference for me at this point is, are there any plans to move =
it forward to proposed standard as any point in the future, or do we =
keep this document as a documentation of the proposed mechanism and =
probably will never touch it again?
>>=20
>> Well, it=E2=80=99s certainly my plan as one of the authors to move =
this forward to proposed standard at some point in the future. We=E2=80=99=
re actively working on this.
>>=20
>>=20
>>>> Ok, thanks for the feedback Michael. Then we stay with =
experimental.
>>>=20
>>> Assuming, we have a decision on the indented status (going for exp =
as the current version said). Would you like to submit another update =
before IETF last call, or should I just start the IETF last right away?
>>=20
>> We=E2=80=99d like to do another update - there were some =
recommendations here: removing the reference to coupled-cc from the =
abstract, different boilerplate and your editorial comments. This may =
take a little bit (I=E2=80=99m not the only author).
>>=20
>> Cheers,
>> Michael
>>=20
>=20


From nobody Tue Feb 13 09:35:14 2018
Return-Path: <xiaoqzhu@cisco.com>
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 5C98812D86A; Tue, 13 Feb 2018 09:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.529
X-Spam-Level: 
X-Spam-Status: No, score=-14.529 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 6V0oz7BnLgIP; Tue, 13 Feb 2018 09:35:11 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D30C712D878; Tue, 13 Feb 2018 09:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5159; q=dns/txt; s=iport; t=1518543310; x=1519752910; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EezUcA/nTMGcYzYWWlP3wvMRCV8R9iFeqlcliyG0vok=; b=UvtRm/KLw1ftG45Vv+EC9u26zScvwe5f3QBcHtNdO2TmxUpJbz5483Gz VSGDA0Mw3t/YJcC34kPrgJVBjL1twTpsQpRemcoCMwUFrW3X8aNvbe7Qq h0aDULnShQ2sARF5Q36gMpXdzK6KaKzsokRZhB30puY6fAN3SrlTAlInA o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BVBQB2IYNa/5BdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJaAUYxZnAoCoYqh1WOJoICgReDOQECAY0phVsVggMKJYUWAoJ?= =?us-ascii?q?oVBgBAgEBAQEBAQJrKIUjAQEBAgJ5EAIBCAQNBAEBCh4HDyMUCQgCBAENBYlRZ?= =?us-ascii?q?BCyU4N+hH6CEQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhQGCFYFXgWiDLoFJgSF?= =?us-ascii?q?FAQECARiBHgUBEgFVhUYFkAGDGZEUCQKIHo1kgh+GKot7ixSCbolpAhEZAYE7A?= =?us-ascii?q?R85YHBwFT2CRoJhghZ4AYt/gSWBFwEBAQ?=
X-IronPort-AV: E=Sophos; i="5.46,508,1511827200"; d="scan'208,217"; a="69764240"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2018 17:35:10 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w1DHZ9tr020442 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Feb 2018 17:35:09 GMT
Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 13 Feb 2018 11:35:09 -0600
Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1320.000; Tue, 13 Feb 2018 11:35:09 -0600
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Anna Brunstrom <anna.brunstrom@kau.se>, "csp@csperkins.org" <csp@csperkins.org>, "mls.ietf@gmail.com" <mls.ietf@gmail.com>
CC: "rmcat@ietf.org" <rmcat@ietf.org>, "draft-ietf-rmcat-nada.authors@ietf.org" <draft-ietf-rmcat-nada.authors@ietf.org>
Thread-Topic: [rmcat] Second RMCAT WGLC for draft-ietf-rmcat-nada - ends December 21
Thread-Index: AQHTbzgLRq0LZ6G+wkOkFqw5N5N1oqOi/+6I
Date: Tue, 13 Feb 2018 17:35:09 +0000
Message-ID: <1518543311258.67035@cisco.com>
References: <477d9a14-8cb3-9edf-467f-660469615e23@kau.se>
In-Reply-To: <477d9a14-8cb3-9edf-467f-660469615e23@kau.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.152.245.38]
Content-Type: multipart/alternative; boundary="_000_151854331125867035ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/x8urWqDp9oWrZkbRDIXoBLjwrqw>
Subject: Re: [rmcat] Second RMCAT WGLC for draft-ietf-rmcat-nada - ends December 21
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Feb 2018 17:35:13 -0000

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

Dear WG Chairs,


I would like to check the status of the NADA draft. As I understand the sec=
ond WGLC is now over.  Just wondering what are the the next steps we shall =
expect?


Thanks,

Xiaoqing



________________________________
From: rmcat <rmcat-bounces@ietf.org> on behalf of Anna Brunstrom <anna.brun=
strom@kau.se>
Sent: Thursday, December 7, 2017 2:47 AM
To: rmcat@ietf.org
Subject: [rmcat] Second RMCAT WGLC for draft-ietf-rmcat-nada - ends Decembe=
r 21


This email announces a second RMCAT Working Group Last Call (WGLC) on:

NADA: A Unified Congestion Control Scheme for Real-Time Media
https://tools.ietf.org/html/draft-ietf-rmcat-nada-06

The purpose of this second WGLC is to give the WG a chance to review the up=
date to the NADA algorithm that was performed as a result of the comments r=
aise during the first WGLC. This second WGLC will run for 2 weeks, ending a=
t midnight US Eastern Time on Thursday, December 21.  Comments should be se=
nt to the rmcat@ietf.org<mailto:rmcat@ietf.org> list.

As previously announced on the list, the authors have made a complete set o=
f NS3 evaluation results for the revised algorithm available via the follow=
ing Dropbox link: https://www.dropbox.com/s/sgrcilpv0ez2vwf/2017-11-20-ietf=
-rmcat-nada-eval.pdf?dl=3D0. Please note that the 05 version of the draft c=
ontains the algorithm updates. The latest 06 version contains further text =
refinements, but no algorithm changes.

Thanks to all who provided feedback during the first WGLC. Ingemar, Julius,=
 Roland, could you please confirm to the list or to the chairs if the lates=
t version addresses your comments.

Thanks,
Anna
(as WG co-chair)




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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none"><!-- p { margin-top: 0px; m=
argin-bottom: 0px; }--></style>
</head>
<body dir=3D"ltr" style=3D"font-size:12pt;color:#000000;background-color:#F=
FFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Dear WG Chairs,&nbsp;<br>
</p>
<p><span style=3D"font-size: 12pt;"><br>
</span></p>
<p><span style=3D"font-size: 12pt;">I would like to check the status of the=
 NADA draft.&nbsp;As I understand the second WGLC is now over.&nbsp; Just w=
ondering what&nbsp;are the&nbsp;the next steps we shall expect?&nbsp;</span=
><br>
</p>
<p><span style=3D"font-size: 12pt;"><br>
</span></p>
<p>Thanks,<br>
</p>
<p>Xiaoqing</p>
<p><span style=3D"font-size: 12pt;"><br>
</span></p>
<p><span style=3D"font-size: 12pt;"><br>
</span></p>
<div style=3D"color: rgb(33, 33, 33);">
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> rmcat &lt;rmcat-bounc=
es@ietf.org&gt; on behalf of Anna Brunstrom &lt;anna.brunstrom@kau.se&gt;<b=
r>
<b>Sent:</b> Thursday, December 7, 2017 2:47 AM<br>
<b>To:</b> rmcat@ietf.org<br>
<b>Subject:</b> [rmcat] Second RMCAT WGLC for draft-ietf-rmcat-nada - ends =
December 21</font>
<div>&nbsp;</div>
</div>
<div>
<p>This email announces a second RMCAT Working Group Last Call (WGLC) on:</=
p>
<blockquote>
<p>NADA: A Unified Congestion Control Scheme for Real-Time Media <br>
<a class=3D"moz-txt-link-freetext" href=3D"https://tools.ietf.org/html/draf=
t-ietf-rmcat-nada-06">https://tools.ietf.org/html/draft-ietf-rmcat-nada-06<=
/a><br>
</p>
</blockquote>
<p>The purpose of this second WGLC is to give the WG a chance to review the=
 update to the NADA algorithm that was performed as a result of the comment=
s raise during the first WGLC. This second WGLC will run for 2 weeks, endin=
g at midnight US Eastern Time on
 Thursday, December 21.&nbsp; Comments should be sent to the <a class=3D"mo=
z-txt-link-abbreviated" href=3D"mailto:rmcat@ietf.org">
rmcat@ietf.org</a> list. <br>
</p>
<p>As previously announced on the list, the authors have made a complete se=
t of NS3 evaluation results for the revised algorithm available via the fol=
lowing Dropbox link:
<a class=3D"moz-txt-link-freetext" href=3D"https://www.dropbox.com/s/sgrcil=
pv0ez2vwf/2017-11-20-ietf-rmcat-nada-eval.pdf?dl=3D0">
https://www.dropbox.com/s/sgrcilpv0ez2vwf/2017-11-20-ietf-rmcat-nada-eval.p=
df?dl=3D0</a>. Please note that the 05 version of the draft contains the al=
gorithm updates. The latest 06 version contains further text refinements, b=
ut no algorithm changes.</p>
<p>Thanks to all who provided feedback during the first WGLC. Ingemar, Juli=
us, Roland, could you please confirm to the list or to the chairs if the la=
test version addresses your comments.<br>
</p>
Thanks,<br>
Anna<br>
(as WG co-chair)<br>
<br>
<br>
<p><br>
</p>
</div>
</div>
</body>
</html>

--_000_151854331125867035ciscocom_--


From nobody Fri Feb 16 07:41:59 2018
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 BBB26120725; Fri, 16 Feb 2018 07:41:53 -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>
Cc: rmcat@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151879571371.1381.8014838742074782998@ietfa.amsl.com>
Date: Fri, 16 Feb 2018 07:41:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/_CoqfabmP9HlncA83_skPuHX-Lg>
Subject: [rmcat] I-D Action: draft-ietf-rmcat-sbd-10.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Feb 2018 15:41:54 -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 WG of the IETF.

        Title           : Shared Bottleneck Detection for Coupled Congestion Control for RTP Media.
        Authors         : David Hayes
                          Simone Ferlin
                          Michael Welzl
                          Kristian Hiorth
	Filename        : draft-ietf-rmcat-sbd-10.txt
	Pages           : 24
	Date            : 2018-02-16

Abstract:
   This document describes a mechanism to detect whether end-to-end data
   flows share a common bottleneck.  It relies on summary statistics
   that are calculated based on continuous measurements and used as
   input to a grouping algorithm that runs wherever the knowledge is
   needed.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-rmcat-sbd-10
https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-sbd-10

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


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 Feb 16 08:28:01 2018
Return-Path: <iesg-secretary@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 A0F63120454; Fri, 16 Feb 2018 08:27:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
CC: rmcat-chairs@ietf.org, rmcat@ietf.org, draft-ietf-rmcat-sbd@ietf.org, ietf@kuehlewind.net, anna.brunstrom@kau.se, Anna Brunstrom <anna.brunstrom@kau.se>
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151879847961.1393.4939609942365260654.idtracker@ietfa.amsl.com>
Date: Fri, 16 Feb 2018 08:27:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/3FxbcRG-09njZbjvrQxb-EQcCVc>
Subject: [rmcat] Last Call: <draft-ietf-rmcat-sbd-10.txt> (Shared Bottleneck Detection for Coupled Congestion Control for RTP Media.) to Experimental RFC
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Feb 2018 16:28:00 -0000

The IESG has received a request from the RTP Media Congestion Avoidance
Techniques WG (rmcat) to consider the following document: - 'Shared
Bottleneck Detection for Coupled Congestion Control for RTP
   Media.'
  <draft-ietf-rmcat-sbd-10.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-03-02. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document describes a mechanism to detect whether end-to-end data
   flows share a common bottleneck.  It relies on summary statistics
   that are calculated based on continuous measurements and used as
   input to a grouping algorithm that runs wherever the knowledge is
   needed.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Mon Feb 26 06:53:59 2018
Return-Path: <iesg-secretary@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 7692C12D7F9; Mon, 26 Feb 2018 06:53:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.4
Auto-Submitted: auto-generated
Precedence: bulk
CC: rmcat-chairs@ietf.org, rmcat@ietf.org, draft-ietf-rmcat-sbd@ietf.org, ietf@kuehlewind.net, anna.brunstrom@kau.se, Anna Brunstrom <anna.brunstrom@kau.se>
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151965683247.31394.7018055597222708797.idtracker@ietfa.amsl.com>
Date: Mon, 26 Feb 2018 06:53:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/dVKvVSFI8-fhmp53rxvL0jbDGQ8>
Subject: [rmcat] EXTENDED Last Call: <draft-ietf-rmcat-sbd-10.txt> (Shared Bottleneck Detection for Coupled Congestion Control for RTP Media.) to Experimental RFC
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Feb 2018 14:53:53 -0000

The IESG has received a request from the RTP Media Congestion Avoidance
Techniques WG (rmcat) to consider the following document: - 'Shared
Bottleneck Detection for Coupled Congestion Control for RTP
   Media.'
  <draft-ietf-rmcat-sbd-10.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-03-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document describes a mechanism to detect whether end-to-end data
   flows share a common bottleneck.  It relies on summary statistics
   that are calculated based on continuous measurements and used as
   input to a grouping algorithm that runs wherever the knowledge is
   needed.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Tue Feb 27 15:17:53 2018
Return-Path: <agenda@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 E0F9312EA90; Tue, 27 Feb 2018 15:11:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <rmcat-chairs@ietf.org>, <csp@csperkins.org>
Cc: rmcat@ietf.org, ietf@kuehlewind.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151977307891.5200.6411965887349382144.idtracker@ietfa.amsl.com>
Date: Tue, 27 Feb 2018 15:11:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/RXbB-Mv_ufxbhMYSn-PftS7I9pM>
Subject: [rmcat] rmcat - Requested session has been scheduled for IETF 101
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
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, 27 Feb 2018 23:11:21 -0000

Dear Colin Perkins,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

rmcat Session 1 (1:30:00)
    Wednesday, Afternoon Session I 1330-1500
    Room Name: Palace C size: 50
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: RTP Media Congestion Avoidance Techniques
Area Name: Transport Area
Session Requester: Colin Perkins

Number of Sessions: 1
Length of Session(s):  1.5 Hours
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: avtcore irtfopen maprg mmusic rtcweb taps tsvarea tsvwg xrblock tcpm iccrg quic
 Second Priority: artarea dispatch



People who must be present:
  Colin Perkins
  Martin Stiemerling
  Mirja Kuehlewind
  Anna Brunstrom

Resources Requested:

Special Requests:
  
---------------------------------------------------------

