From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 ADB2C3CB35; Wed, 22 May 2019 05:53:20 -0400 (EDT) Received: by mail-io1-xd2b.google.com with SMTP id v7so1314627iob.10; Wed, 22 May 2019 02:53:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=7nmVxNIVG0GxvCZSBR3BfhHyeSuWKyAme5M8/K6aZOU=; b=AGC6EfxgHDNmUT1/iCcaCUR8Mn/jS474ZohgPAgal10XGC2EWdCx9zxpAUcfyOji76 1Q5p0csrJCiqpWVbwz8liAOA3N8GIyqgd6lns/vlx8ph5KeAdYGW/eq8wxONnud7VHdo 4btDaviwpTwHxD3UycR7Q0JxHuYty+8SEb62W2gFyvHjYi/bd/dxCA3ujy8gWY7iatLa CfGRr1M+Wymz0J253rBzULHeN7eGtnFRjwpeM6xdJ/3iO0GCL4YKpY5V5INMlAAiY2zX rbN2bcIOsseEbdE/9y0qDMf1E6Z/dStsjLlPoeukANdJrb7qAob5d26jOdXKc8lVNDr0 nW2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=7nmVxNIVG0GxvCZSBR3BfhHyeSuWKyAme5M8/K6aZOU=; b=gpJeMrLc50OAfZuHynSGlEW21Qd4x0v1Urf6HGuU2qsCpP3wp1U4UVktLAvXgsv4JS B0a+1FLaNzWSbUKl/405aVN8NICzjopUp2ajobgHWdMlZhfF8qncVwpRWNdflXEIwYTg 8UAQrvG0mdcaS9Q/2vUxBGb+zhvUZbYAmjrl9SQk6ge3KmwtpAio/6iYgnIKl65meve7 7jn05QXbHocaVG1XEi7A67y77dlclfOXRi+yAmxgP9okC0SFowcJn2GgywN9RIRQdEXA S7GjMPzo4hEujJCT18hSQ/wTn7YJMd1VTz4Z0msn+NuHbR4Q4u3WcmPttF7vcaTMi5t6 2sOQ== X-Gm-Message-State: APjAAAWP9h1bSHq47xtitn4Z53kOfl+TyYWXo/bQf11M7YboMlDboNZY j3IwdEv+VZOuT947xNuK4YtQjROBXF0nzW7S2uZfn/NN0907WQ== X-Google-Smtp-Source: APXvYqwTJIe57Kt2Zjissh6AIYhidTht2GMv+5FK+QaJA8g+2p8QXH0HxLR5xD3ZhrLEeZgsQDDu/tfN/fJVx3ttCZs= X-Received: by 2002:a5d:851a:: with SMTP id q26mr3334500ion.246.1558518799815; Wed, 22 May 2019 02:53:19 -0700 (PDT) MIME-Version: 1.0 From: Dave Taht Date: Wed, 22 May 2019 11:53:07 +0200 Message-ID: To: bloat , Make-Wifi-fast , cerowrt-devel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] will starlink have bufferbloat? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2019 09:53:20 -0000 With the first major starlink launch stuck on the pad, and having never got a straight answer about how starlink was going to manage satellite handovers and admission control, I came up with an "annoyer-in-chief" idea to see if we could find out what the plan was. If everybody here (500+ members of these mailing lists!) could take 2 minutes to compose an interesting tweet or reply to elon musk on the subject, maybe we'd get somewhere. I just did one ( https://twitter.com/mtaht/status/1131131277413822464 ) but a huge variety of posts on the theme are possible, other thoughts were things like: @elonmusk There seems to be no intelligent life among ISPs down here. Has #starlink handled the #bufferbloat problem? ( https://blog.tohojo.dk/media/bufferbloat-and-beyond.pdf ) @elonmusk Keep hoping #bufferbloat will be solved by #starlink - got a plan? ( https://blog.tohojo.dk/media/bufferbloat-and-beyond.pdf ) do it on replies to anything he says about starlink, keep doin it, and perhaps, an answer will appear. Sometimes ya gotta be loud. --=20 Dave T=C3=A4ht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740