From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 158BD3B29D for ; Thu, 30 Apr 2020 13:29:00 -0400 (EDT) Received: by mail-qk1-x72a.google.com with SMTP id m67so6524817qke.12 for ; Thu, 30 Apr 2020 10:29:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=52tNWcpDLDyJLb3mNLvneiSKeu9/Y5zCtdZG/zhkxQA=; b=r+L/7z6tRL/S1jGv0WXdOlVDHKqAZg7i4jLaGfKzeun4IpyiV1srWFc8YA0VAZyRQ7 O8cGq9KT2/P1YhSjmMt5cIrh2vscCd5ukMfXcgY3TrWAcylLNSzlWuZJlbeawH8i2aQe PrmRWK67JYtE60UMuWrXQAwPvRm9/1C2GBCJKMC5mfuYib3DzkilaXiB7UQZtjJs6uVw Ag74gC2tbhjcvSzHYpZrjLNW5U0OGW3aro/IvXWgT4iNzIuBfFKowUTqMQzFuL5TCdF5 tGIqQEO2vY59YfQ1/U2ytrvlbccpc8GN9l2HXFZm2spwnMuB0MXf0ni/JE8r+ZKJozXB gK9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=52tNWcpDLDyJLb3mNLvneiSKeu9/Y5zCtdZG/zhkxQA=; b=lvoz7+jCA3ItBYRzwYaJwKNSeauYi1305R51wNAfmiqKygKvhEsmfxgmYfLjxlgdVY uOgoL8DrB44O66IKEmENhwcORQcF9h/KhtiwcbSwQU4kxuvuZYWm84IaQjM5JnQKTez9 IASu5FRDKq+8wV/E5qSTeauBOdU5SvXlkBrzzRm7Ibvkt0IUg5tzAbB9P6nGTitZvAwY PlBEkotFDggybhNMme14RBqTTXtK3bvrA3/M+gx6zN1drKW2SxyMfh7E0FIpVgS09M/N kM4yXORyxf/DbZ2VWfTk/Md/ysugWIOStYeD3faZW8K17MjXVTEZ20V5KKDB/hMhhAa5 QlXg== X-Gm-Message-State: AGi0PuZ21jH7c8LQrV52b0RxqjX8hTJ3046/M5AO8N8hHRWkMASotgbE +9xSV562jrLmCjW0wbxjVwpiT5j4pj0= X-Google-Smtp-Source: APiQypK8vg2LBDxHJxIG6VfCtz466BlUdLb+obTKzIUyOy7/drzK9IGQOzrK9wJI7V/snRGDKbRDlQ== X-Received: by 2002:a05:620a:1405:: with SMTP id d5mr4873853qkj.329.1588267739323; Thu, 30 Apr 2020 10:28:59 -0700 (PDT) Received: from richs-mbp-10337.lan ([70.16.109.76]) by smtp.gmail.com with ESMTPSA id o43sm231614qtf.46.2020.04.30.10.28.58 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Apr 2020 10:28:58 -0700 (PDT) From: Rich Brown Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Message-Id: <2937CA62-6FCC-4E32-B7F5-11A6A485F1EE@gmail.com> Date: Thu, 30 Apr 2020 13:28:58 -0400 To: ecn-sane@lists.bufferbloat.net X-Mailer: Apple Mail (2.3608.80.23.2.2) Subject: [Ecn-sane] Questions about TSVWG call X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2020 17:29:00 -0000 Folks, I have been a bystander in these discussions, and could only listen in = to part of the TSVWG conference call. But here are a couple questions = that come to mind from what (I think) I heard... 1) Has anyone run RRUL tests on L4S gear? What would be involved setting = up such a test? Why hasn't it already been done? 2) If I understand correctly, the L4S proposal is to use the ECT(1) bit = as an input to the routing algorithm. If it's set, the router can assume = that it's latency-sensitive traffic and use special routing = rules/queues/etc. How does L4S guard against DoS/cheating? Has such a = proposal been implemented and tested? 3) The L4S proposal is designed to decrease latency. Can there be a = successful L4S deployment in the face of the millions of current CPE = that have no notion of latency control? 4) I have a personal bias toward helping people with dreadfully slow ISP = service. (My home can only get 7mbps/768kbps DSL; others in my town only = get 3mbps/500kbps service.) Does L4S help for slow links like these? Forgive me if this is all common knowledge, or if answers have been = summarized elsewhere. (I would love to have a link.) Thanks. Rich=