From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 F27D63B29D for ; Wed, 13 Oct 2021 15:18:08 -0400 (EDT) Received: by mail-qk1-x730.google.com with SMTP id bk7so3249368qkb.13 for ; Wed, 13 Oct 2021 12:18:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=6Qb835LIfkkh+haH49mpGHcoIgSdHtkf6VngDHy5G2M=; b=Xqf5BQ/I7DlfV6LnQm3v7LSc598gWqiE20DdpdFQOGd2ijJ0yeLoaZVu7dNX3KqGsu ZvAbwAQZki7um1rZ5IWfc8VF3amZjouVscn9xarVkWagsnvCvrGnFFXopsWdVK/KolG9 NN7SfwlNqalU+mMDPHyds05K2Z2mt+Mv9h3HmphY11lSx905A4QB3AqzamSe2M9dJBX7 25ETji2seoKzKUsMtiMBYKa3hkEBmRJ+VmbiYjZs6We3eAFml7xEQsi6ItO9E6gDiX+u CrfTcihVATJXL3I525a5dHGYnzK8TJNwLGREqDcW8o2mLoSAAdwtk+BNFXIyjQgU0Gyr zJBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=6Qb835LIfkkh+haH49mpGHcoIgSdHtkf6VngDHy5G2M=; b=Ol3DJwr6izS3Ew98fW1sYAQqH+blbP/m9Nwbtn8fXDTT02h64CiDiZF9w41rKz0oRH OWKgb7dIZlBkpfwbSqfgtkf8TwcjXi9+A5DQmA2+MNiC5IjxDbmAHzfc5tnR6U2/qvmm MF9a6yqtPwueo7pDCT3G52zvbFvNbdT294azVhAPTwCLQ2MAFDPNSfW/zH9ZVjjXhzR2 54fCdOGfxqBD7va4QUNDj2M1RlJ/vOzn75mRpxLN4DVAh3pYSGGxR67zqk/HWAt23qsB cqdCdNDDXTaJoWu+prb4yyIPtnsLKoMTrRNNuL6k4uE2oLEpuO8oTRAdhyPL93pyuGNS iteg== X-Gm-Message-State: AOAM532VeTbwbwcIuV+v26vYgpqGF5QqwLTGZWpK+aKH+K3c+XqbSU3m C+rs3795sMFvI+GxARW2kd35Vdxh5OY= X-Google-Smtp-Source: ABdhPJzEispTQ9jUfvpIqWWVcWndA82RxLbWwQzbIqvgWvQC06A9Bu7oPqN8/QQ4QYxP9KqMtH/Y7w== X-Received: by 2002:a05:620a:24cf:: with SMTP id m15mr995269qkn.434.1634152688469; Wed, 13 Oct 2021 12:18:08 -0700 (PDT) Received: from richs-mbp-pro.lan ([198.55.239.186]) by smtp.gmail.com with ESMTPSA id g11sm280975qko.31.2021.10.13.12.18.07 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Oct 2021 12:18:07 -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.120.23.2.7\)) Message-Id: Date: Wed, 13 Oct 2021 15:18:07 -0400 To: rpm@lists.bufferbloat.net X-Mailer: Apple Mail (2.3608.120.23.2.7) Subject: [Rpm] Does RPM measurement *require* a valid SSL certificate 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: Wed, 13 Oct 2021 19:18:09 -0000 I was about to send out the following invitation on the OpenWrt Forum = (forum.openwrt.org) when I saw the following in = https://github.com/network-quality/server > NOTE: The networkQuality CLI tool will only connect to a server = presenting a valid SSL certificiate [sic]. If you are using a custom CA, = ensure the CA is trusted by the system. This constraint dramatically complicates the rollout of networkQuality = servers. In fact, it makes it impractical to run on a home router = without a lot of farbling around with Let's Encrypt, etc. Would the use of a self-signed certificate invalidate the RPM readings? = If not, could this constraint be relaxed? Thanks. Rich =3D=3D=3D=3D=3D=3D=3D Proposed Invitation to OpenWrt developers = =3D=3D=3D=3D=3D=3D=3D=3D=3D Subject: Seeking RPM Server package for OpenWrt Apple has designed an RPM Tool for macOS 12 and iOS 15 that measures the = "responsiveness" of your network connection. (Responsiveness is the = inverse of latency - the lower the latency, the higher the = responsiveness.)=20 The RPM Tool counts the number of round-trips per minute (RPM) while the = line is fully loaded. A higher number (1,800 RPM and above) is excellent = (that's 30 round-trips per second). Below 1,000 RPM is pretty bad. You = can read more about it at: = https://www.bufferbloat.net/projects/bloat/wiki/toward_a_consumer_responsi= veness_metric#a-proposed-metric-rpm=20 Apple has servers that let you test the responsiveness from your device = to their network infrastructure. But the RPM test can work locally, as = well. It's often the case that local conditions, such as = poorly-performing or weak Wi-Fi, dominate the connection. It's important = to know whether it's your Wi-Fi, your router, or your ISP (and their = connection to the rest of the world) that's causing problems. Your mission, should you choose to accept it, is to implement the server = end of the RPM tooling. It would likely be an OpenWrt package, and would = listen to requests from the client on your phone/laptop so that it could = measure responsiveness from the device to the router. There's a full protocol spec in Section 5 of: = https://datatracker.ietf.org/doc/html/draft-cpaasch-ippm-responsiveness-00= #section-5