From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-c2p-546593.sys.comcast.net (resqmta-c2p-546593.sys.comcast.net [IPv6:2001:558:fd00:56::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 08AF43B29D for ; Sun, 8 Dec 2024 02:17:30 -0500 (EST) Received: from resomta-c2p-555921.sys.comcast.net ([96.102.18.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c2p-546593.sys.comcast.net with ESMTPS id KBWnt1AZv7lvxKBX9tFxGW; Sun, 08 Dec 2024 07:16:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1733642211; bh=ildjzrdIQgKuIa1ovDVy39JOVXfCbAyx1Rucbco9Nhg=; h=Received:Received:Received:Content-Type:Message-ID:Date: MIME-Version:From:To:Subject:Xfinity-Spam-Result; b=nJlK55wKSBbqlL/DaLzweXc7OP2yCbTA65Qt7Y13dQuYivNxb2jeb0BwN5l7fz+dT YNXgre2ik8LBffoLL6EZRLOEi7C00vuC+vQp3xcEI7PAGdRxhHnwZmKgpJgcRKcn7l gfOt7wxY7bLemwZ0lg59XYGA/gxfDuYlPobufUE4qZ3dpESpSl90PIAUl3g0Ogvrfu Sb03Hqpzj7A+4SNLhsAaJYDZJtvD6sRJxK9oEzfm3SG/r5ZHTdC6gpL4ETXZwkV+7W TnFhbTZBpE2VtTFHVktvvtFEujsc2JHLWM2TiwmAJ0XdnHF04dykFjatdxFnTk2nny 3ba7W5jc1Qe3Q== Received: from home.sewingwitch.com ([IPv6:2600:1700:a64d:600f:2e0:81ff:feb5:9463]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-c2p-555921.sys.comcast.net with ESMTPSA id KBUhto9hQaKMgKBUltZEFU; Sun, 08 Dec 2024 07:14:29 +0000 Received: from [10.96.7.39] ([10.96.7.39]) (authenticated bits=0) by home.sewingwitch.com (8.14.7/8.14.7) with ESMTP id 4B87EEqP027237 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 7 Dec 2024 23:14:15 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 home.sewingwitch.com 4B87EEqP027237 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sewingwitch.com; s=default; t=1733642055; bh=ildjzrdIQgKuIa1ovDVy39JOVXfCbAyx1Rucbco9Nhg=; h=Date:From:To:Subject:From; b=YDElMgSE8X9WU0rvBtXjvcfN+E4U7CHfjEP85s3cilgobhuS04f8xyezENylrh9R1 PUz0DxlXFkkIZHbQPO5ze00BB0BZEtIrd9Y+LMcYttGu5+VKvH76RiN7UcavXQbUvD tiMi3QW3WQNFEk2z7jidYEE+tqv8YV3fdO4k8h98= Content-Type: multipart/alternative; boundary="------------Bmi0sBQ55JDqKRQF4X8uw0kn" Message-ID: <628c4862-d0e1-4423-81b5-b940da350bdd@sewingwitch.com> Date: Sat, 7 Dec 2024 23:14:13 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Kenneth Porter Content-Language: en-US To: Starlink mailing list X-Scanned-By: MIMEDefang 3.4.1 on 10.96.0.132 X-CMAE-Envelope: MS4xfDQJjWzOVawMJozh5r4/EM3UNKhX87uOgr2714XcpnfwVuJAHm87ZbhSzaryJC3GFDyrFmM840yLjxTyfROC9/VyNhgcRf2iPgwmQwioKkknz8IeGT9y XF5B5QKKk3JXiUGJrfwZgUbv2IFDLy7c5wh47Z15L6uuQUilsh2aJFQiI8u3K8yUMZAfj6s/y0OEj5QwgfuUJi9w7VazTEH0j9wDQymei6e3oPHvTMXLkzx6 3T8lT98Pkb5calGGw9jzpSJix5HfpPmatyQdxkHd5YmrTAiBK04FDIQXU+u4Y31d Subject: [Starlink] =?utf-8?q?A_transport_protocol=E2=80=99s_view_of_Starl?= =?utf-8?q?ink_=28APNIC_blog_article_from_May_2024=29?= 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: Sun, 08 Dec 2024 07:17:31 -0000 This is a multi-part message in MIME format. --------------Bmi0sBQ55JDqKRQF4X8uw0kn Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit A transport protocol’s view of Starlink By Geoff Huston on 17 May 2024 https://blog.apnic.net/2024/05/17/a-transport-protocols-view-of-starlink/ > Digital communications systems always represent a collection of design > tradeoffs. Maximizing one characteristic of a system may impair > others, and various communications services may choose to optimize > different performance parameters based on the intersection of these > design decisions with the physical characteristics of the > communications medium. > > In this article, I’ll look at how TCP, the workhorse transport > protocol of the Internet, interacts with the characteristics of the > Starlink service . > Nice analysis of the satellite handoff's effects on Reno, CUBIC, and BBR. Lots of graphs. [Apologies if this was already discussed here. I checked the May archives and didn't see the link or author's name.] --------------Bmi0sBQ55JDqKRQF4X8uw0kn Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

A transport protocol’s view of Starlink

By on 17 May 2024

https://blog.apnic.net/2024/05/17/a-transport-protocols-view-of-starlink/

Digital communications systems always represent a collection of design tradeoffs. Maximizing one characteristic of a system may impair others, and various communications services may choose to optimize different performance parameters based on the intersection of these design decisions with the physical characteristics of the communications medium.

In this article, I’ll look at how TCP, the workhorse transport protocol of the Internet, interacts with the characteristics of the Starlink service.

Nice analysis of the satellite handoff's effects on Reno, CUBIC, and BBR. Lots of graphs.

[Apologies if this was already discussed here. I checked the May archives and didn't see the link or author's name.]


--------------Bmi0sBQ55JDqKRQF4X8uw0kn--