Re: [ippm] QUIC concerns relating to draft-ietf-ippm-explicit-flow-measurements

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 12 May 2023 17:25 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
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 08674C151B3D; Fri, 12 May 2023 10:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zDQMH-c1wjPD; Fri, 12 May 2023 10:25:06 -0700 (PDT)
Received: from mail-oa1-x34.google.com (mail-oa1-x34.google.com [IPv6:2001:4860:4864:20::34]) (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 929FEC1522D9; Fri, 12 May 2023 10:25:06 -0700 (PDT)
Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-192adab8f0eso8095154fac.2; Fri, 12 May 2023 10:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683912305; x=1686504305; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lXynTRHDyYQN/XiU4/OLX5Q8IkkFqKKzmhVeWRnJogA=; b=GRIkI0Tmr15dntdWsbVuACLLLmfkJvfIe9p18mAsdopFV73Y+QCw41ta1o2CXInj2M IdSdyBhHC+YDmqA19E6p41IueVUxFEJQmTjh6gzCszauaeyQXMj99fIvODX6eqNGkYBB rZO4O4059sT3YgPZpUGVp5OY1zYKQV4uNgErfF7YF63BkpxtTzmi6zh2IUMPTn9TNmZB pieivZtYvy0CvEvtW+UNBCsMZcv2aqye/m5e0E+gOvBjkq+GROFt+PNDT2h6Lu64y0Aj XRAWUqvOmZVYy48yH0DtUk1Vw5s3/S8o43+Tsu+UeETOSB1t+yP9wqXfbvbK5Ek1N/MI JFcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683912305; x=1686504305; h=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=lXynTRHDyYQN/XiU4/OLX5Q8IkkFqKKzmhVeWRnJogA=; b=JZtSl0ihHE7q1UVIk6pvhHMeMYRunNjeSRrlWjbXH02EUVv4ovYuWhIM6ZFB/asbR5 Zg7dCX2t4RbRXeu91G7930W50qFwJ4qc8go/FEY5uMSIcxPaKYKxSnsKbsDJvNOhYUlK FOFyKCCYdxf04s1NDe1q7SiVvs1L93RFY9f1EqiZwzt78ClipSFJFHQe7u9vxU1b2ys9 dIOtRO4sEvUlmfZ//6QNvpZnIVdVh84eVhKsKhWCjMwIMy2G3hwKw7ZQ5Ei39xR7vgst BvSPYtvEFQ/l4/9xZXAmov3DBo7zHQZamLc0sUKtmjvRySj1J6SfVItklg5zqIYaDi1s opSA==
X-Gm-Message-State: AC+VfDx++JkIYtCEg6AkrpTt4fV1ZVMuEQ3OlEOikOizU3ij8S2i//QN 6c/e/Cx5fi3CyXKPoUAt3FgtbqO5/6CfvTzbqdI=
X-Google-Smtp-Source: ACHHUZ6A6V71dXy/S+AOuBUvHQwmbxTWDjZcD9Bv1jpYTpyFnyeX16SASk58u09NUxkQ5RPqlbzBWWrWt3Nx+m1y9eA=
X-Received: by 2002:a05:6870:c384:b0:195:f311:46ad with SMTP id g4-20020a056870c38400b00195f31146admr14054717oao.15.1683912305063; Fri, 12 May 2023 10:25:05 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oZxFEXWD5hZZOJB7q+-f766FsjBGBTNjpuc1jyZyucz3Q@mail.gmail.com> <3103CBFB-5112-4FAC-A2F0-5209F52AB288@apple.com> <CALGR9oboNgFo-BA0Sqstog_JFPm+DL545VUSbksgF1chTnZ7VQ@mail.gmail.com> <791fd608-8112-bea7-9e22-5d0b8b9e8b1d@huitema.net> <5cf7edfcdf604f13b7fda36d206babfb@huawei.com> <18d470b2-ccfc-41a3-bbef-a572091502bb@betaapp.fastmail.com> <1cb7ab2a31394a19b20418ca7cd8ebb0@akamai.com> <4e85047d-2197-e75a-a665-211075925dad@huitema.net> <f7ee3a0d-c0f5-491f-a0f5-4fb41bb56ea8@betaapp.fastmail.com> <3f0ffd1d-191e-3d7a-cea5-fa9d89d3dd84@huitema.net> <CADgHTrYPSZTeYPaFzRJZPq1ZyMrAEdxb9xx+0Bsttu7gJcDwww@mail.gmail.com> <VI1PR0701MB6800BCAD13C4EC5DBBF760A6E5759@VI1PR0701MB6800.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB6800BCAD13C4EC5DBBF760A6E5759@VI1PR0701MB6800.eurprd07.prod.outlook.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 12 May 2023 18:24:53 +0100
Message-ID: <CALGR9obh5fNR0cFW2U8yUArCrbvDT90Mwb46E6v3RzBvtwDybw@mail.gmail.com>
To: Nilo Massimo <massimo.nilo=40telecomitalia.it@dmarc.ietf.org>
Cc: "quic@ietf.org" <quic@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, "Bulgarella Fabio (Guest)" <fabio.bulgarella@guest.telecomitalia.it>, "Cociglio Mauro (outlook.com)" <mauro.cociglio@outlook.com>, "giuseppe.fioccola@huawei.com" <giuseppe.fioccola@huawei.com>
Content-Type: multipart/alternative; boundary="000000000000c6c76e05fb82621f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/c13rddcU-frc08JYXBzSHgW_bTY>
Subject: Re: [ippm] QUIC concerns relating to draft-ietf-ippm-explicit-flow-measurements
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: Fri, 12 May 2023 17:25:11 -0000

Hi Nilo,

On Fri, May 12, 2023 at 6:11 PM Nilo Massimo <massimo.nilo=
40telecomitalia.it@dmarc.ietf.org> wrote:

> Hi,
>
> first of all thanks for the many comments received.
>
> As jointly agreed at the time with the chairs of the IPPM, QUIC and TSWG
> WGs, this draft is general and its purpose is to describe only the
> measurement methodologies in a protocol independent way. In order to
> describe their application to a certain protocol, it was agreed to present
> a specific draft in the related WG.
>
> So to give an example, with regard to the COAP protocol, this was done by
> submitting a draft in the CORE WG. See
> https://datatracker.ietf.org/doc/draft-ietf-core-coap-pm/
>
> Therefore, with regard to the QUIC protocol, we will prepare a draft to be
> presented in the QUIC WG which will address the issues highlighted in this
> thread and details related to the possible future implementation.
>
>
>
> As for this draft
> https://datatracker.ietf.org/doc/draft-ietf-ippm-explicit-flow-measurements
> , we will write a new version of it where the section 6 will be placed in a
> draft appendix and renamed to Experimental Examples.
>
> In this way (we hope) it will be clear that we are talking about
> experiments made, and that they must not be interpreted as implementation.
>
>
>
> If the other co-authors agree, we can proceed to make a new version of the
> draft.
>

Given that section 6 just seems to be a trivial presentation of how to
assign bits in QUIC's 7 bit space, I don't really see what the value of
talking about any specifics are. What benefit would the authors see in
keeping an appendix?

Cheers
Lucas