Return-Path: 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 C0A26120048; Sat, 9 Nov 2019 12:44:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 KD09rwCXnQfi; Sat, 9 Nov 2019 12:44:15 -0800 (PST) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 DAD3412008D; Sat, 9 Nov 2019 12:44:14 -0800 (PST) Received: by mail-lf1-x135.google.com with SMTP id q28so7024976lfa.5; Sat, 09 Nov 2019 12:44:14 -0800 (PST) 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=sh2yQbNzj4HuD8f+eF/rGZTgQrRfp2sFos1Bfv/bf3k=; b=UnwJm5oHA82BbgSH953CbKK82E6ij8iqUkAfkOKAbgCrVsvssbU9gMHXrI6164lEHd P0KsagvV8tY19Ht/nx0hKcL2npwit/8Wf/1uXqj5bedoyjM9tJuT1gRBqr+8qI89O/19 fKzUPo49qk7f3k4Fcg9y7n0eVbcf9McOKStXBzdBhuzFwWgIZIpk/xFoXMrqkdFCb7E0 Gwrdti6Wz/TVXv/jpkNudiZaAhbNCpFdAw9jebZ++h78vLIsY+xKOoEjJ5lP5k17a77Z P6VyHohferYHnbPPoj1Rt9jq3vhrhb1+WShYJJP4ops1JoCd7bWAzyuFWD5t6DFyE7uW Heuw== 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=sh2yQbNzj4HuD8f+eF/rGZTgQrRfp2sFos1Bfv/bf3k=; b=l7sPzqDC5cUuCbifM+yJ/k1DhiItDwp2DL4ETAhJbpC1iGcfnMV/MhDlCayYkgO0/2 xSdiOvMqQelFSLSUxjiTKsfJwtaZiXqTIT8zqe+jLZgvLy/vc+nayTC+VTW0HY3iiJuP lsFeI/xJSWQfJmw2C7DAn3ygW9bOGWb2CH46m3DitFYoT8pSFJmaWVhEr8cogH666EAO 4EGuZHdEbC4pG1HzXIztk+ODSi1bGhf+Nhf9hR7iBuWIHUFUe/vqb6j39jHBIefaIr8z x38JZifldeXCz7GtxawL/SbEBmiIKyNajK+zERgXwPxLNMyb+zATJX+MubRl1lRYP+TV KjLA== X-Gm-Message-State: APjAAAXpatbTHDhQ8UbUPsUoysQwvT24sZEyX8aZwmB9j5TAvJc4CFCo tiIu01PEAb/3lDXjoFMiths= X-Google-Smtp-Source: APXvYqxTNm88RPgJDpvVohlGH+0fgJarePJcYoYH4lV/eUNpfRg0Ms5g5ti/0XscFJ7RRz1t9tqsFA== X-Received: by 2002:ac2:51a3:: with SMTP id f3mr10858326lfk.38.1573332252630; Sat, 09 Nov 2019 12:44:12 -0800 (PST) Received: from jonathartonsmbp.lan (85-76-23-24-nat.elisa-mobile.fi. [85.76.23.24]) by smtp.gmail.com with ESMTPSA id g26sm4405628lfh.1.2019.11.09.12.44.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Nov 2019 12:44:12 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Jonathan Morton In-Reply-To: Date: Sat, 9 Nov 2019 22:44:10 +0200 Cc: Ingemar Johansson S , "tcpm@ietf.org" , Ingemar Johansson S , "iccrg@irtf.org" , "koen.de_schepper@nokia.com" , "tsvwg@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <96C87F7D-F4C5-422E-9836-79817F39C9CF@gmail.com> References: <2083E62F-0E6D-40B1-B726-A198BFA36220@gmx.de> To: Sebastian Moeller X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [tsvwg] [tcpm] L4S related activity in 3GPP X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2019 20:44:17 -0000 > On 9 Nov, 2019, at 10:38 pm, Sebastian Moeller = wrote: >=20 >> There are other promising features with L4S. One being that it can = enable congestion control algorithms to quickly grab free capacity. >=20 > [SM] When you say L4S, do you mean the congestion signaling? = Then https://tools.ietf.org/html/draft-morton-taht-sce-00 should have = you covered, without the nasty side-effects of the current L4S proposal. = Or do you mean the actual congestion controller as implemented in TCP = prague?=20 Nitpick: the correct reference is now = https://tools.ietf.org/html/draft-morton-tsvwg-sce-01 and significantly = updated relative to that old version. - Jonathan Morton