From: J Pan <Pan@uvic.ca>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] IETF side meeting on satellite and deep space networks (Tue Mar 18)
Date: Wed, 5 Mar 2025 12:31:04 -0800 [thread overview]
Message-ID: <CAHn=e4h6LvAYd7FdGVG5AZyye1Jd25xJdtV+AAJkhpUySCxd=g@mail.gmail.com> (raw)
In-Reply-To: <662863e1-518f-48a1-8723-5b05f3409820@auckland.ac.nz>
satellite networks have some funny interactions with content providers
https://www.reddit.com/r/CloudFlare/comments/1iw4dwj/why_1111_keeps_switching_between_jnb_and_nbo_for/
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Wed, Mar 5, 2025 at 11:37 AM Ulrich Speidel via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> I'll see whether I can make it - hopefully so.
>
> Could we add challenges of content delivery to the agenda?
>
> On 6/03/2025 5:31 am, Nishanth Sastry via Starlink 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
>
> --
> ****************************************************************
> Dr. Ulrich Speidel
>
> School of Computer Science
>
> Room 303S.594 (City Campus)
>
> The University of Auckland
> u.speidel@auckland.ac.nz
> http://www.cs.auckland.ac.nz/~ulrich/
> ****************************************************************
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2025-03-05 20:31 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
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 [this message]
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='CAHn=e4h6LvAYd7FdGVG5AZyye1Jd25xJdtV+AAJkhpUySCxd=g@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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