From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.nextlayer.at (smtp2.nextlayer.at [IPv6:2a01:190:1764:150::37]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C1C7A3B2A4 for ; Fri, 9 Jul 2021 19:07:54 -0400 (EDT) Received: from [192.168.0.49] (d50-117-141-56.yt.northwestel.net [50.117.141.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.nextlayer.at (Postfix) with ESMTPSA id B030A802749 for ; Sat, 10 Jul 2021 01:07:52 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.nextlayer.at B030A802749 To: starlink@lists.bufferbloat.net References: <1625856001.74681750@apps.rackspace.com> From: Daniel AJ Sokolov Message-ID: <4c973572-ab02-2424-c246-6607b8cd6dfe@sokolov.eu.org> Date: Fri, 9 Jul 2021 16:07:50 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.24) Gecko/20100411 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit Subject: Re: [Starlink] Starlink and bufferbloat status? X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2021 23:07:54 -0000 On 2021-07-09 at 3:58 p.m., David Lang wrote: > IIRC, the definition of 'low latency' for the FCC was something like > 100ms, and Musk was predicting <40ms. Indeed, the Rural Digital Opportunity Fund Auction defined "Low Latency" as "<100 ms", and "High Latency" as "≤ 750 ms & MOS of ≥4". MOS is the Mean Opinion Score, which takes latency and jitter into account. For "Low Latency", jitter/MOS was not defined. MOS goes from 1 (Bad) to 5 (Excellent). https://www.fcc.gov/auction/904/factsheet FYI Daniel