IETF Logo Mail Archive

Re: [tsvwg] path forward on L4S issue #16

Jonathan Morton <chromatix99@gmail.com> Thu, 18 June 2020 08:07 UTC

Return-Path: <chromatix99@gmail.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 4BA613A0F47 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jun 2020 01:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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, 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 (2048-bit key) header.d=gmail.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 auM3HTlnSfRk for <tsvwg@ietfa.amsl.com>; Thu, 18 Jun 2020 01:07:44 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 049CF3A0F43 for <tsvwg@ietf.org>; Thu, 18 Jun 2020 01:07:43 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id w15so2906079lfe.11 for <tsvwg@ietf.org>; Thu, 18 Jun 2020 01:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=91uThujW0s4wZwgZLDiRce9+lgrjJIQ2vYZlc10+nEE=; b=LRmYMa7bDDXTxgat6SpVPNxbUDQq+qWaoroO061bPuv+HUtC7ASzQvbvmCoWy6of6m TneKlHVN14K75IPfF8k7vi6nJLvBI1rLoXrcMNnCq1RAON03mpyNeYZf+PDBfXrKuy02 AAjwd6/f+hla0DHi4klTci5sgsV2KsPGqgIopvS+BTV0KuXuURmryH+zCXortzbI3hz8 x2KWl+t9KBVA56VYNmGgbUzm3ni8U5ay5KqlfNcdfFtr+q7a+ywwo0sCkMZNiJdhEgiM Z1PiMrnl/QvSsUDrp9rhoGtLpXFLqi9cXvyZZKru3Nlwon3DIWVQpbE46DpOfwzioBIq SsYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=91uThujW0s4wZwgZLDiRce9+lgrjJIQ2vYZlc10+nEE=; b=aMb0HQ/quRD48Rl7tcKKVTk4Uaqbv0QFpIA9eFVlwG3LiVFlOnuxKX78ezowUiJNHh jIKrwOhD1qEFL6q+M3gxOWA0iGWZb61uQlba0UvDw61BxzUc/EYwsLi2T902dTacGpgZ m19dgr5cd9Oq7Pz/UJCjoTp2K9Jx1XZTaCP7hjBfzwxPHTD6cjcVFwMTZB7X1m+C+/Gx TfjqJhn4HrCEuoDADQt21MCiC0hOij+Pcph6289Fs4v7Fr0OwOuA9W+0uksFdwfz7Dfq d8/SutifJhv5oxwmPzi7rUbLlq4INoKYrPjGBrxbzYtQZkSzx9qZK3y4os3zRX4Yh0qB UGoA==
X-Gm-Message-State: AOAM530vwSEb3hr/H0HVgL9PbCVGuiKR7iqEZOaJLMuu4U0YR8l1WcfC emtpxb6tCOLlo9hrzQZ5qQY=
X-Google-Smtp-Source: ABdhPJyFIhAL/bqwESSen984ZRlE6PKijhqToT2uLZRay9bAehbPqGAqM4lIWfPfp8lFyPxAaL+hDg==
X-Received: by 2002:a19:3f89:: with SMTP id m131mr1741238lfa.202.1592467662003; Thu, 18 Jun 2020 01:07:42 -0700 (PDT)
Received: from jonathartonsmbp.lan (83-245-237-14-nat-p.elisa-mobile.fi. [83.245.237.14]) by smtp.gmail.com with ESMTPSA id d22sm568957lfn.84.2020.06.18.01.07.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jun 2020 01:07:41 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <CBCDBB42-81DF-4DD6-ACB6-2BB8F01F3564@gmx.de>
Date: Thu, 18 Jun 2020 11:07:39 +0300
Cc: Paul Vixie <paul@redbarn.org>, TSVWG <tsvwg@ietf.org>, Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <57B28071-01F3-4C93-B309-1546F6E51C00@gmail.com>
References: <2DC5C89B-C979-4354-98D7-BBDBC78A42B1@gmail.com> <MN2PR19MB40450A06A919354C8D4CFC74839A0@MN2PR19MB4045.namprd19.prod.outlook.com> <9E403EBC-79D4-4C6E-B000-E53BE8B29228@gmx.de> <19188328.uKY2rrpm7d@linux-9daj> <CBCDBB42-81DF-4DD6-ACB6-2BB8F01F3564@gmx.de>
To: Sebastian Moeller <moeller0@gmx.de>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/-wRtWqIQrfF-04z28bIJsw91b5A>
Subject: Re: [tsvwg] path forward on L4S issue #16
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: Thu, 18 Jun 2020 08:07:45 -0000

> On 18 Jun, 2020, at 10:38 am, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> …the idea that a single hop is typically responsible for all delay variation seems like too strong a claim to me…

It's quite easy to construct a counterexample, too: any network path including two wifi hops.  Wifi is inherently a significant source of delay variation due to its shared-medium, half-duplex, CSMA/CA with ARQ architecture.  So even if the rest of that network path introduces no delay variation at all, there are still two hops independently introducing delay variations.

 - Jonathan Morton

v2.23.0 | Report a Bug | By Email