From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 956AB3CC60 for ; Tue, 7 May 2024 15:15:09 -0400 (EDT) Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-61e0c1ec7e2so862537b3.0 for ; Tue, 07 May 2024 12:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aterlo.com; s=google; t=1715109309; x=1715714109; darn=lists.bufferbloat.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gP8MDgvv0k6UxxFR+G2bEWFniM8lDoCSn8oBVSuFNxI=; b=i4ePlG27bScJmzkoEtyIz0BbCp2+OWj0g71vhXUg5P7OHGBdB24lbadSZKbfL5eIIC iRKr8A9sIP/W66onPluQE/nnDnqwqYUCI663brYpU1rVpKLA2YQDEEqNueMx6Y1uMp1X T0wVWdd2UOlThBLd4/P/qFY1nTGS4yZ3TlXqo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715109309; x=1715714109; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gP8MDgvv0k6UxxFR+G2bEWFniM8lDoCSn8oBVSuFNxI=; b=LWsV8s07lP9CfcT4itD0D78h/AdKtzgaZwl7uLAhVaGJid+ESdTxbatgbkH0J5Qp2A /g3N3hk7a76vatln+IVLwkZREJGoPYRr0kO+222AoAcVjq5tFsaHSguIWpv7nca8DHtM C3rkoFNmNHCL1Pwt9i9OKfF7g3CKOS1SfcjrML2Jm0KYj1ub9s0NBV7oWd6uCrLpBRtd oPipPihPq4IQ14tk6IvxRPfXr9uhjhVS26QaPtL561p52FkQYN5nMXg3F/r5ODkaXh7Z ZhCGljASJgXpEM7jlESVliY+gPaNO6TfAKPFXerJhHuTftU5qYP2Euqk7w/ESXP1vnkN Eshw== X-Forwarded-Encrypted: i=1; AJvYcCWyhj8JQiUhWnakHG1W8eZOryuBgW5TS9yEwwgCk/QsZ3PAEDNTAth0AICm6bWmO5NG1iT4Va4Uk8lPzCnVo164ajGaGhumBAra8EGP3ZU= X-Gm-Message-State: AOJu0Yz8LiUZsDCTS1d1Q9+yebOIYp50v/BhyDwwGtjlaqHagPukIKYL avh1KX20zOwc7maR5jMLkQPiZ8VYXFTZxBVZqeI/W2/ewsg+G0ykg+A8GHATOUl7xFsazOj86iK 7NRFT8g77jQYKT1NnwTyLNeLsvewFwbxdars82Q== X-Google-Smtp-Source: AGHT+IECJdQqCoKpUzEN4/geGvdZUix3oACIwv2043Mstip3cdwmHPVILNFD+gGDX5eeMgXB/eTEqkB3xlDG0Wocuhg= X-Received: by 2002:a0d:cc03:0:b0:61a:fc74:16e2 with SMTP id 00721157ae682-620766309eamr27366057b3.23.1715109308852; Tue, 07 May 2024 12:15:08 -0700 (PDT) MIME-Version: 1.0 References: <3d6bdccf-e3d1-4f62-a029-25bfd1f458f5@indexexchange.com> <1779481A-0817-4F18-A0D7-A7A5AA0AF9D6@ieee.org> In-Reply-To: From: Jeremy Austin Date: Tue, 7 May 2024 11:14:57 -0800 Message-ID: To: Dave Taht Cc: Eugene Y Chang , Dave Taht via Starlink , Dave Collier-Brown Content-Type: multipart/alternative; boundary="0000000000001b020b0617e2013d" Subject: Re: [Starlink] The "reasons" that bufferbloat isn't a problem 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: Tue, 07 May 2024 19:15:09 -0000 --0000000000001b020b0617e2013d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 7, 2024 at 11:11=E2=80=AFAM Dave Taht via Starlink < starlink@lists.bufferbloat.net> wrote: > The RFC is very plausible but the methods break down in multiple ways, > particularly with wifi. > Dave, can you elaborate more on the failures? Are these being researched or addressed in the current trials, in your opinion? Jeremy --0000000000001b020b0617e2013d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, May 7, 2024 at 11:11=E2=80=AF= AM Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
The RFC is very plausible but the method= s break down in multiple ways,
particularly with wifi.

Dave, can you e= laborate more on the failures? Are these being researched or addressed in t= he current trials, in your opinion?=C2=A0

Jeremy
--0000000000001b020b0617e2013d--