From: Nishanth Sastry <n.sastry@surrey.ac.uk>
To: "LEOCONN@JISCMAIL.AC.UK" <LEOCONN@JISCMAIL.AC.UK>,
Starlink BufferBloat List <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: Pre-Proposed SPACE RG side meeting
Date: Mon, 17 Mar 2025 11:52:15 +0000 [thread overview]
Message-ID: <AEB7380C-B0A2-492D-979A-BCA312364426@surrey.ac.uk> (raw)
In-Reply-To: <9dcb4184-b9f4-4e0d-ae9c-50ecb11e378f@in.tum.de>
A gentle reminder of the previously advertised side meeting happening tomorrow (Mar 18, 1515-1615 Bangkok Local Time) about a potential SPACE RG and some updates, including proposed agenda below. Hope to see some of you there.
Best Wishes
nishanth
Forwarded message:
> From: Joerg Ott <ott@in.tum.de>
> To: deepspace@ietf.org
> Cc: Juan A. Fraire <juanfraire@gmail.com>, Nishanth Sastry <n.sastry@surrey.ac.uk>
> Subject: Pre-Proposed SPACE RG side meeting
> Date: Mon, 17 Mar 2025 16:00:18 +0700
>
> Hi,
>
> on 18 March, 15:15-16:15 ICT (8:15-9:15 UTC) at IETF 122 in meeting room 2, we will hold a side of the not yet quite Proposed SPACE RG. For a draft charter see https://github.com/ekline/spacerg/blob/main/charter.md
>
> [We apologize for the conflict with another satellite side meeting but this didn't exist when we asked for it. Probably parallelism struck.]
>
> SPACE RG is not competing with existing WGs or other RGs. It is not intended to do any protocol specifications but rather learn about deployments, measurements, and tools, and share practices and data.
>
> In particular:
>
> SPACE RG is NOT DTN WG (nor a delayed successor of DTNRG) because we will look at quite well-connected megaconstellations such as Starlink and other satellite networks.
>
> SPACE RG is NOT TIPTOP WG either because we don't try to tweak protocols to work better with larger latencies or in specific environments.
>
> We are considering of being an IRTF research group to begin with. We may compile useful insights into networking properties and look at routing protocols, operational experiences, etc. from a research perspective.
>
> Agenda:
>
> 1. Introduction (5min)
> 2. Short talks for background (clarifying questions only, 25min)
> Juan Fraire: Models and Methods for Near-Earth and Deep Space Networking
> Ulrich Speidel: How fast can Starlink really be? A quick summary
> Nishant Sastry: LEOscope: A global measurement testbed for LEO Satellite Networks
> 3. Round table (20min)
> Where shoudl a Proposed RG go and what should it "deliver"?
> 4. Charter discussion and next steps (10min)
>
> Please join us on site or online at:
> IETF Webex: https://ietf.webex.com/meet/ietfsidemeeting2
>
> Looking forward to seeing you around!
>
> Best,
> Juan, Nishant, and Jörg
parent reply other threads:[~2025-03-17 11:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9dcb4184-b9f4-4e0d-ae9c-50ecb11e378f@in.tum.de>]
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=AEB7380C-B0A2-492D-979A-BCA312364426@surrey.ac.uk \
--to=n.sastry@surrey.ac.uk \
--cc=LEOCONN@JISCMAIL.AC.UK \
--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