Re: [rmcat] Benjamin Kaduk's No Objection on draft-ietf-rmcat-eval-test-09: (with COMMENT)

Colin Perkins <csp@csperkins.org> Sun, 12 May 2019 21:15 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1220120130; Sun, 12 May 2019 14:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 KbEEtlcmu_RP; Sun, 12 May 2019 14:15:09 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 D0BEF120006; Sun, 12 May 2019 14:15:08 -0700 (PDT)
Received: from [81.187.2.149] (port=38580 helo=[192.168.0.81]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1hPvoD-00035l-TG; Sun, 12 May 2019 22:15:06 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <FDC681F4-5EDC-466E-9A73-77B00F76FBEB@kuehlewind.net>
Date: Sun, 12 May 2019 22:14:52 +0100
Cc: Benjamin Kaduk <kaduk@mit.edu>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "rmcat-chairs@ietf.org" <rmcat-chairs@ietf.org>, Benjamin Kaduk via Datatracker <noreply@ietf.org>, "draft-ietf-rmcat-eval-test@ietf.org" <draft-ietf-rmcat-eval-test@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <90551451-DAB9-4444-ABBB-3331A3FF4A2A@csperkins.org>
References: <155197033601.24667.6429871717336324511.idtracker@ietfa.amsl.com> <3C53B15F-9C66-4C64-8C15-A643EADE6B54@ericsson.com> <20190323134227.GZ88959@kduck.mit.edu> <0E1DBC98-6486-483C-8CEA-893BAC4F930E@ericsson.com> <20190324135134.GM77890@kduck.mit.edu> <FDC681F4-5EDC-466E-9A73-77B00F76FBEB@kuehlewind.net>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3445.104.8)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/S2tN_K6p91EL9vWlcxkp1TMrmxY>
Subject: Re: [rmcat] Benjamin Kaduk's No Objection on draft-ietf-rmcat-eval-test-09: (with COMMENT)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 May 2019 21:15:11 -0000

Hi,

Just to follow-up: are there still updates required from the authors of this doc, or is it ready to progress?

Colin



> On 2 Apr 2019, at 10:02, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
> 
> Hi Zahed, hi Ben,
> 
> Just a quick note below.
> 
>> On 24. Mar 2019, at 14:51, Benjamin Kaduk <kaduk@mit.edu> wrote:
>> 
>>>>   Section 3
>>>> 
>>>>            +  Bottleneck-link capacity: defines minimum capacity of the
>>>>               end-to-end path
>>>> 
>>>>   I'm not sure I'd describe this as the "minimum capacity of the
>>>>   end-to-end path", since attempts to use anything larger than this value
>>>>   will pile up at the bottleneck.
>>>> 
>>>> [ZS] hmm, I guess that is why that link will act as bottleneck link for a respective testcase. If the flows remain below that capacity it should not experience queuing and as you said anything above that capacity will observe queuing. The job of the congestion control algorithm will be to avoid queuing.
>>> 
>>>   I think I was expecting "maximum capacity" to be more appropriate than
>>>   "minimum capacity".  Perhaps I'm confused about what is intended here.
>>> 
>>> (disclaimer. this has been done in the long past and I hope my memory is supporting me on explaining it ☺)
>>> 
>>> The thinking was that the bottleneck-link capacity was not equals to the maximum link capacity. That means if the maximum link capacity is X then the bottleneck-link capacity is Y , where Y<X and (X-Y) capacity is used by other traffic traversing that link. Hence, in the test if a link is assumed to be bottleneck then the "the bottleneck-link capacity" is the minimum capacity available to the media flow traversing that path. 
>> 
>> Ah, that makes sense.  Maybe "minimum guaranteed capacity" or similar would
>> convey the intent better.
> 
> The word “guaranteed” would be confusing here as people would associate this with some kind of resource reservation. Maybe "minimum link capacity of the end-to-end path”.
> 
> Mirja
> 
> 
> 



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