From: Eugene Y Chang <eugene.chang@ieee.org>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Seeking technical speaker on measuring/measured Starlink performance
Date: Sun, 12 Mar 2023 14:29:25 -1000 [thread overview]
Message-ID: <18C15CB6-9CA0-4207-9C8A-D6B4EF48E9E0@ieee.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]
Friends,
I am seeking a technical speaker for the Hawaii IEEE Communications Society chapter.
My wish list (negotiable):
Realtime remote presentation followed by Q&A
Challenges of measuring real Starlink performance
Best practices for measuring Starlink performance
What has been measured…
The good, the bad, and the ugly.
Presentation 45 - 60 mins
17:30 HST (GMT-10)
Typically Tuesdays. Wednesdays could be alternative.
Of course, we have a few Starlink users.
I don’t know of any local users looking closely at their real service levels.
Gene
----------------------------------------------
Eugene Chang
IEEE Senior Life Member
eugene.chang@ieee.org <mailto:eugene.chang@ieee.org>
m 781-799-0233 (in Honolulu)
[-- Attachment #1.2: Type: text/html, Size: 3452 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2023-03-13 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=18C15CB6-9CA0-4207-9C8A-D6B4EF48E9E0@ieee.org \
--to=eugene.chang@ieee.org \
--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