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

Bjørn Ivar Teigen <bjorn@domos.no> Thu, 21 December 2023 10:41 UTC

Return-Path: <bjorn@domos.no>
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 812E9C09036B for <ippm@ietfa.amsl.com>; Thu, 21 Dec 2023 02:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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=domos-no.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 dfGYlqhOlhue for <ippm@ietfa.amsl.com>; Thu, 21 Dec 2023 02:41:07 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 016F8C151072 for <ippm@ietf.org>; Thu, 21 Dec 2023 02:40:51 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2cc9b31a27bso6651621fa.3 for <ippm@ietf.org>; Thu, 21 Dec 2023 02:40:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=domos-no.20230601.gappssmtp.com; s=20230601; t=1703155249; x=1703760049; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=H3TxB03An1lpFXLacVyHxBhs7I5HEO0HjBX9RQ6/mpA=; b=zbR5sOUBY5kTvF33nJiGCnbiMKIqHlTim88d1Ohd50c0ipEV9Jb6uyDsuxRqSSNzSF jH15oPkIEq/y6MIAwMFr3EDucTsiGvdMA7reZ8vYGrg4vP7sxwBZ3ekezy0oQupC4HaO qiAecqB0DOEKlIYmj2OLTqkShCZ42neyMTYH1bXIAvyJRQzPibNnPtw1oKx1WifO4qe0 +Ucu5P8lAaCGybr3tWjb6ukRC9a7Z5gXx039yDUoomnQvsBGBTNSRMY309UiGh3mOaB3 R1YnDljomIVJP8qslDZri35ubiFiY2EKfR4CKHvV/3QCVX5YxBMLBp6XVS+OpV1kyEny zq2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703155249; x=1703760049; h=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=H3TxB03An1lpFXLacVyHxBhs7I5HEO0HjBX9RQ6/mpA=; b=of6z4d5dPoHbCAxmALi1P+ipvsCiIRHad+s2zA/J3oYp9TZhqt7HEaxWYYU/ELINU5 HvVOBeMUQpqH7BK3NSGWUX0HZVqbJvp9BVwoU80fV24QfeAvEd1GG+JNkdy/MHerYYV7 5VVrR+XGhLy1MUnvGACE5CJ1EB/oWzfE9AZrAwUQ3wt55rJivY1SJc18CMcmU4izMMjm Kef96ULUYcNkyphsSvnCcw75a2fAWsADDtbUnbmTJ/LCVieFk28uEgDyoZ/4gu+Remm0 azIBTACwU/ymEjZLSoMbxg0LF/45laj/xB2Id+u6KnlivNSM8tKIOPWeGITqj2jz7Ztx v6BA==
X-Gm-Message-State: AOJu0YxXH82dmTAexDrpFLwrfSAfrxhoIl2w9dhODkazUFhsAbiaw82k VmSw4/AMQA6DcOPEt9c9yb+sAN9RbM/LB40FeyI/li5p1kYqFioDm3YjBg==
X-Google-Smtp-Source: AGHT+IG4R9iAPMKYwn0sKgYPxNTgpJBVtxpU7y/6h5nzL0SHW7eGW9pLsvVKCNOYSuMqsIsnowJUZkkFjFc0yG1zX9s=
X-Received: by 2002:ac2:48b1:0:b0:50e:2f96:4ee with SMTP id u17-20020ac248b1000000b0050e2f9604eemr3802612lfg.36.1703155248634; Thu, 21 Dec 2023 02:40:48 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR07MB4142AB4694BB044E939DCD7BE285A@VI1PR07MB4142.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB4142AB4694BB044E939DCD7BE285A@VI1PR07MB4142.eurprd07.prod.outlook.com>
From: Bjørn Ivar Teigen <bjorn@domos.no>
Date: Thu, 21 Dec 2023 11:40:37 +0100
Message-ID: <CAKf5G6KfNMM6BsZqSccFUNa3038WLWrnytQaULSbV73jbeCKhw@mail.gmail.com>
To: "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000097af9a060d02bb43"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/sPWI9voKFKhCcDOjOcV8xkVIQ6M>
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: Thu, 21 Dec 2023 10:41:11 -0000

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?

.....

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?

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
[image: https://www.understandinglatency.com/]
<https://www.understandinglatency.com/>