Re: [tsvwg] L4S and the detection of RFC3168 AQMs

"C. M. Heard" <heard@pobox.com> Fri, 11 December 2020 20:09 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12FA03A0EAA for <tsvwg@ietfa.amsl.com>; Fri, 11 Dec 2020 12:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
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 k7ywwHdYTGbd for <tsvwg@ietfa.amsl.com>; Fri, 11 Dec 2020 12:09:34 -0800 (PST)
Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1DB03A0EA6 for <tsvwg@ietf.org>; Fri, 11 Dec 2020 12:09:34 -0800 (PST)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 5BDF491509 for <tsvwg@ietf.org>; Fri, 11 Dec 2020 15:09:33 -0500 (EST) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=84Bs4SW/KYCRRdpY1FC76qaH6bM=; b=uugGrm pqyKgIa9cPN+BxkGvSQrMgC/KwugeisWK5Kn9PAaKT7FsG9UMP64mqoi/BGISIi/ G0LqJSEF4dgXqfPr0C7hIBAtlTZNo+1kTISpQPkGlgbe7LKaydDnX/cacE0DOoeg /csVQAbdRNTVRiIqiSlfl76Nq0aIWDucofo84=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; q=dns; s=sasl; b=rpBOlOvYK9q4R9BhWk3/3CFrhz8TmQDP NTPfWs7s0UxQ3+Helgd8li13iVtwcdREqFvBPMMsR80j5sSB7tVEq9RH7hSWElrj 3QPMqNPG0JJAbPRT3NtXdHxLcDvwADp88AxpxXRHQO+8Vpo+sRJD2PpSxTj3Qu/f +DSSLcRi5Vw=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 51CCB91508 for <tsvwg@ietf.org>; Fri, 11 Dec 2020 15:09:33 -0500 (EST) (envelope-from heard@pobox.com)
Received: from mail-io1-f53.google.com (unknown [209.85.166.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id C857691506 for <tsvwg@ietf.org>; Fri, 11 Dec 2020 15:09:32 -0500 (EST) (envelope-from heard@pobox.com)
Received: by mail-io1-f53.google.com with SMTP id y5so10720410iow.5 for <tsvwg@ietf.org>; Fri, 11 Dec 2020 12:09:32 -0800 (PST)
X-Gm-Message-State: AOAM531MTJHFanPjXJHXwMBicwA+awdSKZ2sAsbcEso4o4Fn/fRyxDYD cijXmKqBIglzaf9uim0NQj/Nyf8cf48XiZAKxkw=
X-Google-Smtp-Source: ABdhPJwCG7IisgyLN+sdhtAUNDmj2eYoZ76CvQiY9p66Wt2uOz2L01BNaQjj3GDXE7kuPjLDWAxfpbhyu9MZ+j4/FB4=
X-Received: by 2002:a05:6602:106:: with SMTP id s6mr17013011iot.17.1607717372216; Fri, 11 Dec 2020 12:09:32 -0800 (PST)
MIME-Version: 1.0
References: <125328289.3455959.1607381048136.ref@mail.yahoo.com> <125328289.3455959.1607381048136@mail.yahoo.com> <3F562A25-F4F2-4335-9ED7-54299500B8F6@cablelabs.com> <a35cf206-2fc7-c60e-c713-c4f916106bde@bobbriscoe.net> <CAM4esxQQe4MJsU3ZvdVWVeSC6z+YWCytDd3i2im27qhnss1_og@mail.gmail.com>
In-Reply-To: <CAM4esxQQe4MJsU3ZvdVWVeSC6z+YWCytDd3i2im27qhnss1_og@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Fri, 11 Dec 2020 12:09:21 -0800
X-Gmail-Original-Message-ID: <CACL_3VE_FD7wdwXGgbYsBnj0+ox-m6s6V=uZVaVZdgK-fLT2KQ@mail.gmail.com>
Message-ID: <CACL_3VE_FD7wdwXGgbYsBnj0+ox-m6s6V=uZVaVZdgK-fLT2KQ@mail.gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
Cc: TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000deca3905b635de41"
X-Pobox-Relay-ID: C893904E-3BEC-11EB-8B9F-D152C8D8090B-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/VEoVb5yqfTVMvI0tc7o_KY2lY-U>
Subject: Re: [tsvwg] L4S and the detection of RFC3168 AQMs
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2020 20:09:36 -0000

On Fri, Dec 11, 2020 at 11:51 AM Martin Duke <martin.h.duke@gmail.com>
wrote:

> This falls under the "much easier to do in other transports" category,
> where I could just send a PING or HEARTBEAT marked ECT(0) to test the queue
> in mid-connection, without affecting the latency of anything that matters.
> But in the TCP case, I'm not sure how to resolve Bob's second objection
> (running ECT(0) for a long time would be unacceptable).
>

Could zero-length TCP segments be used instead of PING or HEARTBEAT?

Mike Heard