Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nishanth Sastry <n.sastry@surrey.ac.uk>
To: Dave Taht <dave.taht@gmail.com>
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 21:25:09 +0000	[thread overview]
Message-ID: <200F1E39-0209-4AED-A431-7B2B408FD4BC@surrey.ac.uk> (raw)
In-Reply-To: <CAA93jw7B_F64eSp=yrRVkes0=o5ZG+WzH-Wu6oCfRP=89rQ+5Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3419 bytes --]

Great question. One clear and easy answer is that this is meant to be an IRTF group rather than an IETF group, so with more of a focus on identifying long-term research issues (that are of interest to the IETF community) rather than on forming standards. We think there is a need for an IRTF-lens to draw clear boundaries, identify overlaps, and connect interfaces across architectures (e.g., Bundle Protocol/IP), different variants the space domain (LEO/DeepSpace), phenomena (Delay/Disruptions down to relativistic effects), and entities (IETF, CCSDS, IOAG, but also the private players in the space, like Starlink).

That said, the meeting is really to figure out what the community thinks there is a need for, and indeed, whether there is a need for something like this. Why not come to the meeting (virtually or in person) to provide your views and inputs on things we could/should do? Of course, appreciate that the Bangkok timezone may not work out for some, but if we manage to get this going, we are hoping to have regular activities in other IETF meetings which will be in other time zones.

Best Wishes
nishanth

On 5 Mar 2025, at 19:22, Dave Taht wrote:

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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrello.com%2Fc%2FoqEoQIua&data=05%7C02%7Cn.sastry%40surrey.ac.uk%7Ca2fef03b23f541882ca208dd5c1b1c64%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638767993722911799%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C60000%7C%7C%7C&sdata=x4PTxhRcMcPTFqhWwzm6sg2Lad8nqmo9CUYY31R5Gac%3D&reserved=0<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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fstarlink&data=05%7C02%7Cn.sastry%40surrey.ac.uk%7Ca2fef03b23f541882ca208dd5c1b1c64%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638767993722931918%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C60000%7C%7C%7C&sdata=7bzx4%2FDtH3DTS74ZpWW08f5PGV%2BXUpzY4vWO9mf0M4I%3D&reserved=0<https://lists.bufferbloat.net/listinfo/starlink>

--
Dave Täht CSO, LibreQoS

"A perfect storm" - https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCQX1PmRULU0&data=05%7C02%7Cn.sastry%40surrey.ac.uk%7Ca2fef03b23f541882ca208dd5c1b1c64%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C1%7C638767993722946990%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C60000%7C%7C%7C&sdata=vzmdcSgXsPw54A2gN38K1msKQO1LWneVsSd9RSOoEAM%3D&reserved=0<https://www.youtube.com/watch?v=CQX1PmRULU0>

[-- Attachment #2: Type: text/html, Size: 4598 bytes --]

  reply	other threads:[~2025-03-05 21:25 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 [this message]
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=200F1E39-0209-4AED-A431-7B2B408FD4BC@surrey.ac.uk \
    --to=n.sastry@surrey.ac.uk \
    --cc=Edward.Birrane@jhuapl.edu \
    --cc=dave.taht@gmail.com \
    --cc=ek.ietf@gmail.com \
    --cc=juanfraire@gmail.com \
    --cc=kevin.shortt@airbus.com \
    --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