IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Thu, 11 May 2023 02:35 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 8C4ABC20A893; Wed, 10 May 2023 19:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.847
X-Spam-Level:
X-Spam-Status: No, score=-6.847 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 BqoYmce8XiF1; Wed, 10 May 2023 19:35:16 -0700 (PDT)
Received: from mail-oa1-x31.google.com (mail-oa1-x31.google.com [IPv6:2001:4860:4864:20::31]) (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 27B16C1DF993; Wed, 10 May 2023 19:35:16 -0700 (PDT)
Received: by mail-oa1-x31.google.com with SMTP id 586e51a60fabf-192c2569c72so3521196fac.2; Wed, 10 May 2023 19:35:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683772515; x=1686364515; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jPj2hpqcIOMerKWFwvF/F1CfnzDjnMaUGKNGOf2PTaM=; b=b90vWGq2tHv/QjR+Z5HuXg1lCnujR75hOxOhQ/aAcjp7Ob9M9neYFDoGy4o6a5Jcov 0nFGbklmT+EmOk8oraeL8FeN0rF6C7nNl9DqUwNQ+s3idbPnG7zTzApaikexDCYzgrv9 wlH2NostVSH1fNaRtIngXCSy+KqBFBpm+ECKP6JnP5KCAs6ZidJdmQVtRos0UIGF3yVV tjhuzdGu0v0xm7jRJFPMYMMOQFNAlBhiAVFQjNgh7lu89EXl+3wvrs4QulKMYIYU/twk ZQOtADe3ezfvC1ek/RJ0dDwjdxa6BzgCs1bHyeRNacZuGEXT+8fbrhbVzUrs2kedEVKV kO2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683772515; x=1686364515; 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=jPj2hpqcIOMerKWFwvF/F1CfnzDjnMaUGKNGOf2PTaM=; b=DJq1CUhgL/dzOZ8Zh5VaTHZJkL39q5fcC/SUiHnjOw904cvtHoxD6bmTC9yWY8zlhZ qn2n0BsRA7+ayyi4TdmI2AKUkzZVF6/kX03OcF2GOuPglm1JG5X+TsMR90wGHr0SPaAU fHlE2oqhjaQXQI0tiAdG3LqCNCqJJ8GpfqkSIJWwvrUaQl9xLxmniOcvUnTAc4Yf8oy+ CINhzjpZ8kM4Q8MZhp6cqEbAXu2oKyCYCSD0Jq2oyZiP4YBDRhDdRewnUJqE3N8pScE6 qOuHufVqPn3lysbaBkA5ts1OuB1dMcXhdc3Dz036VuIiqc8mheEvVlfE+wHXbRR3vURT m7Fw==
X-Gm-Message-State: AC+VfDx4e3guZsxtRf761nlRObhcAdjk7PRuFMwFAkdr70bMJLyjmzXN TasoSl4RFdE5kfBCC4fd2xzQBg5WoMuqCitNhqc=
X-Google-Smtp-Source: ACHHUZ66Iztacd1oVnHewE85GO7rKrbdeSxFpF8nAWocsLyYoFXzCybMG74YClG2KE0b4Rk+1z2ZtFwCwAM/sLdsu1k=
X-Received: by 2002:a05:6870:5243:b0:196:58cd:4174 with SMTP id o3-20020a056870524300b0019658cd4174mr1771561oai.10.1683772515206; Wed, 10 May 2023 19:35:15 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oZxFEXWD5hZZOJB7q+-f766FsjBGBTNjpuc1jyZyucz3Q@mail.gmail.com> <3103CBFB-5112-4FAC-A2F0-5209F52AB288@apple.com>
In-Reply-To: <3103CBFB-5112-4FAC-A2F0-5209F52AB288@apple.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 11 May 2023 03:35:04 +0100
Message-ID: <CALGR9oboNgFo-BA0Sqstog_JFPm+DL545VUSbksgF1chTnZ7VQ@mail.gmail.com>
To: Tommy Pauly <tpauly@apple.com>
Cc: IETF IPPM WG <ippm@ietf.org>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6ca8405fb61d62b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/ZHX3AG2oAD0uY_0vkbLjWZdi7Vs>
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: Thu, 11 May 2023 02:35:18 -0000

Hey Tommy,

On Thu, May 11, 2023 at 3:00 AM Tommy Pauly <tpauly@apple.com> wrote:

> The document is describing how bits *could* be used, not actually
> suggesting reserving specific ones at this point.
>
> This same feedback did come up in IESG review, and I believe that there
> will be an update to remove details that refer to specific bit ranges to
> avoid this danger.
>

> I’ll let the authors chime in more =)
>


To summarize the issue, there's only 7 bits that any QUIC version
compatible with the Invariants can ever use. Unless client, server and
observers all agree what those bits might mean, there's no way to actually
use them assuredly. The draft doesn't pay enough attention to highlighting
this deployment problem, so there's a risk that the work done to define the
bits in the abstract is for nought because the next steps of trying this
out for real are unclear. Relying on some private agreements of what the
bits might mean isn't safe for several reasons.

Cheers
Lucas

v2.23.0 | Report a Bug | By Email