From: Hesham ElBakoury <helbakoury@gmail.com>
To: Kurtis Heimerl <kheimerl@cs.washington.edu>
Cc: Jim Forster <jim@connectivitycap.com>,
Starlink list <starlink@lists.bufferbloat.net>,
Giovanni Giambene <giovanni.giambene@unisi.it>
Subject: Re: [Starlink] LEO Panel at IETF 120 GAIA in Vancouver
Date: Thu, 28 Mar 2024 12:14:59 -0700 [thread overview]
Message-ID: <CAFvDQ9ohJ-mn0e2WqYukrqCNjhjOiPAMO9r88p5GYVzDVtVphA@mail.gmail.com> (raw)
In-Reply-To: <CAB+4MyQrOC6VYkNFsUZVD12W7AKW0-20xg_kkK3bJZHC8pB9Qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
I would like to invite Professor Giovanni (copied) to participate on the
panel. He is an expert in Satellites technologies. He is leading the
satellites group in IEEE Future network program.
Professor Giovanni can participate remotely.
Thanks
Hesham
On Mon, Mar 25, 2024, 4:57 PM Kurtis Heimerl via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Great suggestions everyone!
>
> If anyone is on the list (looking at Spencer and Dave) and would like to
> volunteer or would like to make introductions to other notable folks, that
> would be helpful too!
>
> On Mon, Mar 25, 2024 at 4:12 PM Jim Forster <jim@connectivitycap.com>
> wrote:
>
>> Mike Puchol, author of Starlink.sx.
>>
>> Jim
>>
>> On Mar 25, 2024, at 2:54 PM, Frantisek Borsik via Starlink <
>> starlink@lists.bufferbloat.net> wrote:
>>
>> I have a few people in mind:
>>
>> Geoff Huston
>> Dave Taht
>> Oleg Kutkov
>> Spencer Sevilla
>> Larry Press
>>
>>
>> All the best,
>>
>> Frank
>> Frantisek (Frank) Borsik
>>
>> https://www.linkedin.com/in/frantisekborsik
>> Signal, Telegram, WhatsApp: +421919416714
>> iMessage, mobile: +420775230885
>> Skype: casioa5302ca
>> frantisek.borsik@gmail.com
>>
>>
>> On Mon, 25 Mar 2024 at 9:19 PM, Kurtis Heimerl via Starlink <
>> starlink@lists.bufferbloat.net> wrote:
>>
>>> Hey Starlink List,
>>>
>>> I'm Kurtis, a prof at UW and co-chair of the GAIA working group at the
>>> IRTF (https://datatracker.ietf.org/group/gaia/about/). I'd like to hold
>>> a panel on LEOs at the upcoming WG meeting.
>>>
>>> Any suggestions/volunteers on people who want to join in on that? We're
>>> hoping for in-person (lots of LEO work here in the PNW) but remote may be
>>> an option as well.
>>>
>>> Thanks!
>>>
>>>
>>> --
>>> Website: https://kurti.sh/
>>> Public Key: https://flowcrypt.com/pub/kheimerl@cs.washington.edu
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>>
>> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 5192 bytes --]
next prev parent reply other threads:[~2024-03-28 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 20:18 Kurtis Heimerl
2024-03-25 21:54 ` Frantisek Borsik
2024-03-25 23:11 ` Jim Forster
2024-03-25 23:56 ` Kurtis Heimerl
2024-03-28 19:14 ` Hesham ElBakoury [this message]
2024-03-25 22:02 ` the keyboard of geoff goodfellow
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=CAFvDQ9ohJ-mn0e2WqYukrqCNjhjOiPAMO9r88p5GYVzDVtVphA@mail.gmail.com \
--to=helbakoury@gmail.com \
--cc=giovanni.giambene@unisi.it \
--cc=jim@connectivitycap.com \
--cc=kheimerl@cs.washington.edu \
--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