From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bobcat.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 02B9E3B2A4; Mon, 26 Feb 2024 15:02:21 -0500 (EST) Received: from mail.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) by bobcat.rjmcmahon.com (Postfix) with ESMTPA id 328CB1B25E; Mon, 26 Feb 2024 12:02:21 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 bobcat.rjmcmahon.com 328CB1B25E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjmcmahon.com; s=bobcat; t=1708977741; bh=8z2HYPdjjHrM0gMaU7vqtJzkjU6CSUAsXEG9I85DDAM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ct88Wn3xkOE8AwqDhOl8VFtpdlcB4/9dK41T8Eg1rceDFr848kObdJI/a8aAoJg3n w/QvnCT1bw0WY8F87dBjS8PSRC2ngvbOwOopDs5yZa1wy33G+wIQIoXewhwhChz+Y+ 6HTew+hQD/Qj34fOk5kpbYy1O9UEzvckg4+pKNXw= MIME-Version: 1.0 Date: Mon, 26 Feb 2024 12:02:21 -0800 From: rjmcmahon To: Dave Taht Cc: =?UTF-8?Q?Network_Neutrality_is_back!_Let=C2=B4s_make_the_technical_a?= =?UTF-8?Q?spects_heard_this_time!?= , Dave Taht via Starlink , Rpm , discuss , National Broadband Mapping Coalition In-Reply-To: References: Message-ID: <3d808d9df1a6929ecfba495e75b4fc1b@rjmcmahon.com> X-Sender: rjmcmahon@rjmcmahon.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Rpm] [M-Lab-Discuss] The FCC 2024 Section 706 Report, GN Docket No. 22-270 is out! 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: Mon, 26 Feb 2024 20:02:22 -0000 Thanks for sharing this. I'm trying to find out what are the key metrics that will be used for this monitoring. I want to make sure iperf 2 can cover the technical, traffic related ones that make sense to a skilled network operator, including a WiFi BSS manager. I didn't read all 327 pages though, from what I did read, I didn't see anything obvious. I assume these types of KPIs may be in reference docs or something. Thanks in advance for any help on this. Bob > And... > > Our bufferbloat.net submittal was cited multiple times! Thank you all > for participating in that process! > > https://docs.fcc.gov/public/attachments/DOC-400675A1.pdf > > It is a long read, and does still start off on the wrong feet (IMHO), > in particular not understanding the difference between idle and > working latency. > > It is my hope that by widening awareness of more of the real problems > with latency under load to policymakers and other submitters > downstream from this new FCC document, and more reading what we had to > say, that we will begin to make serious progress towards finally > fixing bufferbloat in the USA. > > I do keep hoping that somewhere along the way in the future, the costs > of IPv4 address exhaustion and the IPv6 transition, will also get > raised to the national level. [1] > > We are still collecting signatures for what the bufferbloat project > members wrote, and have 1200 bucks in the kitty for further articles > and/or publicity. Thoughts appreciated as to where we can go next with > shifting the national debate about bandwidth in a better direction! > Next up would be trying to get a meeting, and to do an ex-parte > filing, I think, and I wish we could do a live demonstration on > television about it as good as feynman did here: > > https://www.youtube.com/watch?v=raMmRKGkGD4 > > Our original posting is here: > https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY4vH4/edit > > Larry's wonderful post is here: > https://circleid.com/posts/20231211-its-the-latency-fcc > > [1] How can we get more talking about IPv4 and IPv6, too? Will we have > to wait another year? > > https://hackaday.com/2024/02/14/floss-weekly-episode-769-10-more-internet/ > > -- > https://blog.cerowrt.org/post/2024_predictions/ > Dave Täht CSO, LibreQos