Re: [ippm] WGLC for draft-ietf-ippm-responsiveness

Will Hawkins <hawkinsw@obs.cr> Wed, 27 December 2023 21:25 UTC

Return-Path: <hawkinsw@obs.cr>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18CADC1524A3 for <ippm@ietfa.amsl.com>; Wed, 27 Dec 2023 13:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=obs-cr.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0c5A2wC20rB for <ippm@ietfa.amsl.com>; Wed, 27 Dec 2023 13:25:27 -0800 (PST)
Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80B9C14CEFC for <ippm@ietf.org>; Wed, 27 Dec 2023 13:25:27 -0800 (PST)
Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-5cece20f006so48116717b3.3 for <ippm@ietf.org>; Wed, 27 Dec 2023 13:25:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=obs-cr.20230601.gappssmtp.com; s=20230601; t=1703712326; x=1704317126; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=3Qv+z1SWlZyLHhxFuaZ+8zvBmyi5ObWCGLtcUoPNXZY=; b=J4x8UGxRLyhwbcSXW6bR4gWig6aw2FoWJgMMZIBhxMWdpId4JsiKM7oXOZXbXJ3axe d87FAAQxM+fCejGrxjOal5Uca+bgdZTN+NE8E+kYaZFsBH8g0DZlEXqqTG3+BH+wikj9 M2MoPVvQvpA1sDkmSdKe4Kty5EYCQWZF5Lsa2iEjn5tUyUkOxSf7L7wsiW63ObFpLImb IT4z1NGdERurrvOJplLhBiH0DmyWvppndvRiVhOdLQmmI4vEjESQT8+sksfPUyV7U15p ZjLgn8e/6SnqRbZn9Drs0/2v3AwbEVF9pz0SKum8hG5UPkIojbOGSkJ9kDOEFZsotRuF 1hdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703712326; x=1704317126; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=3Qv+z1SWlZyLHhxFuaZ+8zvBmyi5ObWCGLtcUoPNXZY=; b=G0JAdtGYphMANI0r4M72aRl35ZhTUXMPAiQTG3jpeV3MpPygOzQYwqNOP+MKYbW5hZ q2YGPfaDNIjch498P4gsN7SNPuzPy8+fbIq1GV49WvoZZtcl0oQIxrjaEbcHPks5k38C uvC+Voxgbg+wVYIlILk2kraDxjDTT2NJcnhwZgyvJNnlU9RUbLhYp/t0cUAWJJ7bz6q4 +IPa/eyH62xpdxqDkiryP4Qk/I2DU5r/GcLC6b6V4aldonhQ+5NRSFPBNJG/CfNOKcPy 665h/X9L9QbGuXXDvygpqtt+9xpcuUI7TjeP5XcQG3dSrFHIHeSk0VtG4USX+dooVrds dEyA==
X-Gm-Message-State: AOJu0Yz93A2Y1og+AVC6TeOM+HZQsmVDq1cVoPZMNsLw6I44KWNK9PFo IgStii449P1IboX6a4RW5zXALqkmw0H6oHBjwGP92XFS/6oCySEtBFvPZ46HE8c=
X-Google-Smtp-Source: AGHT+IEAYx5p68vWuG9k2hksFM/WObMYxizpHB00QTwy9ayDfzYY+G5b945vZIhytAXqNXoUg+kIIcnhUylycD3JRxY=
X-Received: by 2002:a81:8784:0:b0:5d9:50cc:b901 with SMTP id x126-20020a818784000000b005d950ccb901mr6465254ywf.95.1703712326299; Wed, 27 Dec 2023 13:25:26 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR07MB4142AB4694BB044E939DCD7BE285A@VI1PR07MB4142.eurprd07.prod.outlook.com> <CAKf5G6KfNMM6BsZqSccFUNa3038WLWrnytQaULSbV73jbeCKhw@mail.gmail.com>
In-Reply-To: <CAKf5G6KfNMM6BsZqSccFUNa3038WLWrnytQaULSbV73jbeCKhw@mail.gmail.com>
From: Will Hawkins <hawkinsw@obs.cr>
Date: Wed, 27 Dec 2023 16:25:15 -0500
Message-ID: <CADx9qWhVT8nzoxMbfjfjQ+jFU00jvC1LDtuWYzsGReKANnXk7A@mail.gmail.com>
To: Bjørn Ivar Teigen <bjorn@domos.no>
Cc: "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/dcnusEK5_rAql8xUvo9TePdF8bo>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-responsiveness
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2023 21:25:32 -0000

Bjorn,

I am sorry for not responding sooner! See inline.

On Thu, Dec 21, 2023 at 5:41 AM Bjørn Ivar Teigen <bjorn@domos.no> wrote:
>
> Hello IPPM,
>
>
> I've read draft-ietf-ippm-responsiveness-03. The draft is well-written and easy to read in my opinion. I consider the contribution novel and useful.
>
>
> Please find my comments and questions inline below:
>
>
>
> IP Performance Measurement                                     C. Paasch
> Internet-Draft                                                  R. Meyer
> Intended status: Standards Track                             S. Cheshire
> Expires: 22 April 2024                                        Apple Inc.
>                                                               W. Hawkins
>                                                 University of Cincinnati
>                                                          20 October 2023
>
>                 Responsiveness under Working Conditions
>                    draft-ietf-ippm-responsiveness-03
>
> Abstract
>
> .....
>
> 4.1.1.  Single-flow vs multi-flow
>
> .....
>
>    One of the configuration parameters for the test is an upper bound on
>    the number of parallel load-generating connections.  We recommend a
>    default value for this parameter of 16.
>
>
> Question: What is the rationale for choosing 16 as the upper bound?


Thank you for the question! I will defer to Christoph and Stuart for
their answer re: the upper bound. I have heard them explain the
rationale in the past but cannot seem to recall the specifics! I don't
want to say something incorrect.

>
> .....
>
> 7.  Responsiveness Test Server Discovery
>
>    .....
>
>    Consider this example scenario: A user has a cable modem service
>    offering 100 Mb/s download speed, connected via gigabit Ethernet to
>    one or more Wi-Fi access points in their home, which then offer
>    service to Wi-Fi client devices at different rates depending on
>    distance, interference from other traffic, etc.  By having the cable
>    modem itself host a Responsiveness Test Server instance, the user can
>    then run a test between the cable modem and their computer or
>    smartphone, to help isolate whether bufferbloat they are experiencing
>    is occurring in equipment inside the home (like their Wi-Fi access
>    points) or somewhere outside the home.
>
>
> Comment: It might be useful to add some reflections about how measurements to different points can be compared.
>
> For arguments sake, let's say we measure towards two hypothetical servers and get RPM to an ISP-hosted server of 500, and RPM to the cable modem of 3000.
>
> How can those values be compared or otherwise reasoned about?

I agree that this is an excellent point. While not in the spec, one of
the available RPM clients does contain the concept of a "relative RPM"
score. The relative RPM score 1. calculates the RPM on an unloaded
connection, 2. calculates the RPM under working conditions, and then
3. computes the change. That calculation removes the "absolute"ness of
RPM but does seem to address the point that you raise.

Again, however, the relative RPM score is a non-standard feature
present in only one of the clients. We did not discuss adding it to
the spec itself.

As above, I will defer to Stuart and Christoph for additional context.

Thank you for the feedback!
Will


>
>
> Best regards,
>
> Bjørn Ivar Teigen
>
>
> On Tue, 5 Dec 2023 at 19:10, Marcus Ihlar <marcus.ihlar=40ericsson.com@dmarc.ietf.org> wrote:
>>
>>
>>
>> Hello IPPM,
>>
>>
>>
>> This email starts a Working Group Last Call for " Responsiveness under Working Conditions”, draft-ietf-ippm-responsiveness.
>>
>>
>>
>> https://datatracker.ietf.org/doc/draft-ietf-ippm-responsiveness/
>>
>> https://www.ietf.org/archive/id/draft-ietf-ippm-responsiveness-03.html
>>
>>
>>
>> Please review the document and send your comments in response to this email, along with whether you think the document is ready to progress.
>>
>>
>>
>> Please send your reviews and feedback by Friday, December 22.
>>
>>
>>
>> BR,
>>
>> Marcus & Tommy
>>
>>
>>
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ippm
>
>
>
> --
> Bjørn Ivar Teigen, Ph.D.
> Head of Research
> +47 47335952 | bjorn@domos.ai | www.domos.ai
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm