From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 A56703CB35 for ; Sun, 27 Mar 2022 10:26:01 -0400 (EDT) Received: by mail-ej1-x631.google.com with SMTP id pv16so23862827ejb.0 for ; Sun, 27 Mar 2022 07:26:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=tVGqha41vQ/ryxTU29GMJmyJwuDmTaVT/0hZnWV7so4=; b=qrz+eJEYszEATyUZT6eu1UU6X1OKtoJ4E4dKKocVo9IB4kxLI4TTRO9ILQGSt5bVkZ AjjNIv2B/buq10GMuPZYHX6OGKBkN/2SEf0Ar27uNr7Ms5bYLjXPmwBqRBEUhA542CoB 76X1CF249SHh/tIyt33OZRXCAyLIgLljv5SS6pzYa/0EwYOSyv11fIsZss5aAzmMjAAP F/MNRoyj4BCDIH8aB0/eDbLSQ+KqaDG7bAgf14IILInBOzwA1z1t0WqZrMCbky+uZzof OLYg7duzXQfOjYW+xNPLIRfyGY6+mP5gqNKpzu8F2d7q19y9zdDUg7BB6p1/S2JHJZPP NqBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=tVGqha41vQ/ryxTU29GMJmyJwuDmTaVT/0hZnWV7so4=; b=jq0os+vXHN/GTURhGRfR5NdIgUutE4/N9RVN4RFl1Ovr0D0pv8CH9P2o7mmuHXyNHr qF8MtO1C2kvsM1yp+JpOi8O79ld7QZC3gOIlc3RghN/7CY1b2SM6qF3zrKvWcOB5Roze w6iTXkPLkxGImpshbimS6ClWTlg2FC5nkFJpoN3IERFDHcrhFrXRRviS0MQm6msLjrg0 trk/1w6CeujM/kI6cvxnQOiKgRq8NfUfIFAEb+At+qyRfMxlqMSrXmxyXBJK8xpTQTFP ON0LhD4P+R+45EfrtGHNu52F0rI0Q+gW0VfLb/rctX55s/av1MQn+xxuHFgpiihRTWkQ itQA== X-Gm-Message-State: AOAM533zt/sROifg+R/l75h2klpHsKhVW+3hOAEB8vw07u4BM3qmJonF l32EYmyTQQHTuaO+vQkXa5eVU8DwvL8i5XpwYNG4yLRILQg= X-Google-Smtp-Source: ABdhPJybrD85sk+u6tLY8OX3NoTOv+wPebxFnvyPhD1AabH1WWJpuTPbxvSRrJ0a7x3F1XWOVnhmrUu1xckDV5iyd+A= X-Received: by 2002:a17:907:7d91:b0:6d7:a1e:a47a with SMTP id oz17-20020a1709077d9100b006d70a1ea47amr22939539ejc.116.1648391160248; Sun, 27 Mar 2022 07:26:00 -0700 (PDT) MIME-Version: 1.0 From: Dave Taht Date: Sun, 27 Mar 2022 10:25:47 -0400 Message-ID: To: Rpm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Rpm] rpm meeting notes from last week X-BeenThere: rpm@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: revolutions per minute - a new metric for measuring responsiveness List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2022 14:26:01 -0000 Sasha has re-organized the meeting notes we've been taking which will be permanently up here: https://docs.google.com/document/d/19K14vrBLNvX_KOdRMK_s0SCYTnj70IJ-dQubL37= kQgw/edit The public meetings continue at 10AM PDT tuesdays. One thing came up in that meeting that bears further reflection: The structure of the the responsiveness test is e2e, and differentiating between the wifi hop and/or sourcing tests from the router - is hard. In the latter case, we are asking a router not only to saturate its network connection, but to do it using crypto, which is a mighty task to ask of a router that's job is primarily routing (with offloads). A thought might be to attempt p2p tests between say, an ios phone and an osx laptop, which would exercise the router as a wifi router. A docker container for the server would be straightforward. (It's still hard for me to trust containers or vm's to run fast or accurately enough, too). Former case is still e2e but with the icmp unreachable idea I described in = wtbb. --=20 I tried to build a better future, a few times: https://wayforward.archive.org/?site=3Dhttps%3A%2F%2Fwww.icei.org Dave T=C3=A4ht CEO, TekLibre, LLC