From: Dave Taht <dave.taht@gmail.com>
To: Nishanth Sastry <n.sastry@surrey.ac.uk>
Cc: Starlink BufferBloat List <starlink@lists.bufferbloat.net>,
Rick Taylor <rick@tropicalstormsoftware.com>,
Kevin Shortt <kevin.shortt@airbus.com>,
"Edward J. Birrane" <Edward.Birrane@jhuapl.edu>,
Erik Kline <ek.ietf@gmail.com>,
"Juan A. Fraire" <juanfraire@gmail.com>,
Joerg Ott <ott@in.tum.de>
Subject: Re: [Starlink] IETF side meeting on satellite and deep space networks (Tue Mar 18)
Date: Wed, 5 Mar 2025 13:22:30 -0600 [thread overview]
Message-ID: <CAA93jw7B_F64eSp=yrRVkes0=o5ZG+WzH-Wu6oCfRP=89rQ+5Q@mail.gmail.com> (raw)
In-Reply-To: <47A7A95F-B3C7-43A7-9A18-10CA8C2DEC2E@surrey.ac.uk>
How will this be different from the tiptop (formerly deepspace) ietf group?
On Wed, Mar 5, 2025 at 10:31 AM Nishanth Sastry via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Hi all,
>
> A few of us (in cc) are planning a side meeting in IETF Bangkok on Tue March 18th, to discuss a potential new IRTF group for Satellite and Space Comms: https://trello.com/c/oqEoQIua Please feel free to join in and shape the group. Both in person and remote attendance welcome. The meeting will take place in Meeting Room 2, from 15:15-16:15 Bangkok local time (If attending remotely via IETF WebEx, you can convert to your local time here).
>
> Best Wishes
> nishanth
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
Dave Täht CSO, LibreQoS
"A perfect storm" - https://www.youtube.com/watch?v=CQX1PmRULU0
next prev parent reply other threads:[~2025-03-05 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 16:31 Nishanth Sastry
2025-03-05 19:22 ` Dave Taht [this message]
2025-03-05 21:25 ` Nishanth Sastry
2025-03-06 18:48 ` Michael Richardson
2025-03-06 22:37 ` Nishanth Sastry
2025-03-06 23:10 ` Dave Taht
2025-03-06 23:45 ` Michael Richardson
2025-03-07 10:28 ` mohan
2025-03-07 15:09 ` Nishanth Sastry
2025-03-11 23:03 ` Sirapop Theeranantachai
2025-03-05 19:37 ` Ulrich Speidel
2025-03-05 20:31 ` J Pan
2025-03-07 0:03 Nitinder Mohan
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='CAA93jw7B_F64eSp=yrRVkes0=o5ZG+WzH-Wu6oCfRP=89rQ+5Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=Edward.Birrane@jhuapl.edu \
--cc=ek.ietf@gmail.com \
--cc=juanfraire@gmail.com \
--cc=kevin.shortt@airbus.com \
--cc=n.sastry@surrey.ac.uk \
--cc=ott@in.tum.de \
--cc=rick@tropicalstormsoftware.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