Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Eugene Chang <eugene.chang@alum.mit.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: Eugene Chang <eugene.chang@alum.mit.edu>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] IEEE starlink talk UTC-10 today
Date: Wed, 3 May 2023 03:47:06 +0000	[thread overview]
Message-ID: <DDF6E130-D8C5-4F93-8210-5D0F93922D35@alum.mit.edu> (raw)
In-Reply-To: <CAA93jw7MLwXjYGJTPW7cUH-R=dBfLyq=RazqXeHAO0-B9519TA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 649 bytes --]

Please use this new link https://meet.google.com/tcy-thdi-usv

Gene
-----------------------------------
Eugene Chang
eugene.chang@alum.mit.edu
+1-781-799-0233 (in Honolulu)





> On May 2, 2023, at 3:18 PM, Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> Please come and kibitz!
> 
> https://events.vtools.ieee.org/m/354445
> 
> --
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


[-- Attachment #1.2: Type: text/html, Size: 11849 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2023-05-03  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  1:18 Dave Taht
2023-05-03  1:44 ` Dave Taht
2023-05-03  3:47 ` Eugene Chang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DDF6E130-D8C5-4F93-8210-5D0F93922D35@alum.mit.edu \
    --to=eugene.chang@alum.mit.edu \
    --cc=dave.taht@gmail.com \
    --cc=starlink@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox