From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: QUIC in space: hackathon at IETF SFO
Date: Mon, 17 Jul 2023 12:48:21 -0600 [thread overview]
Message-ID: <CAA93jw72okAkh-Cw1+2Ghbesyq7kN8Cg1zVyWJmEXGhP1=VeXQ@mail.gmail.com> (raw)
In-Reply-To: <FBA4A0F9-55CF-4E73-91CF-1F8F37C05A8E@viagenie.ca>
[-- Attachment #1.1.1: Type: text/plain, Size: 2461 bytes --]
---------- Forwarded message ---------
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Date: Mon, Jul 17, 2023, 7:57 AM
Subject: QUIC in space: hackathon at IETF SFO
To: <quic@ietf.org>
Hello,
If you are interested, please join the “party”!
Regards, Marc.
IETF 117 Hackathon <https://wiki.ietf.org/en/meeting/117/hackathon>
wiki.ietf.org <https://wiki.ietf.org/en/meeting/117/hackathon>
[image: apple-touch-icon.png]
<https://wiki.ietf.org/en/meeting/117/hackathon>
<https://wiki.ietf.org/en/meeting/117/hackathon>
QUIC in Space
- Champion(s)
- Marc Blanchet (marc.blanchet at viagenie.ca)
- Christian Huitema (huitema at huitema.net)
- Project Info
- (Deep) Space comm has loooong delays (minutes to hours) and
disruptions. Purpose of the project
is to modify open-source QUIC stacks to be usable for this use case.
QUIC stacks typically
have low initial values to prime the initial communications, which
does not fit with long delays
and make various assumptions not optinal for space comm. Goal of this
project is to:
a) externalize these static values so they could be changed at start
or while running,
b) set a testbed to test with long delays and verify use
c) modify stacks to support the space use case (specially for
disruptions), d) if relevant,
write internet-draft for findings and possible
modifications/extensions to QUIC.
An initial POC was done with Christian Huitema (see below) with his
picoquic stack.
We would like to go further with more QUIC stacks such as Mozilla
Neqo (in Rust) or
Google Quiche(in C++) or Cloudflare Quiche (in Rust) or picoquic(in
C) or QUINN (in Rust).
- Additional Info
- POC: https://www.privateoctopus.com/2023/02/07/quic-to-mars.html
- Mozilla Neqo: https://github.com/mozilla/neqo
- Cloudflare Quiche: https://github.com/cloudflare/quiche
- Google Quiche: https://github.com/google/quiche
- Huitema Picoquic: https://github.com/private-octopus/picoquic
- Quinn: https://github.com/quinn-rs/quinn
- Linux Netem (to introduce delay):
https://man7.org/linux/man-pages/man8/tc-netem.8.html
- MacOSX Network Link Conditioner (to introduce delay):
https://medium.com/@itsanurag/simulate-low-network-with-network-link-conditioner-a1a7f14423b6
[-- Attachment #1.1.2: Type: text/html, Size: 9525 bytes --]
[-- Attachment #1.2: apple-touch-icon.png --]
[-- Type: image/png, Size: 7642 bytes --]
[-- Attachment #2: apple-touch-icon.png --]
[-- Type: image/png, Size: 7642 bytes --]
parent reply other threads:[~2023-07-17 18:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <FBA4A0F9-55CF-4E73-91CF-1F8F37C05A8E@viagenie.ca>]
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='CAA93jw72okAkh-Cw1+2Ghbesyq7kN8Cg1zVyWJmEXGhP1=VeXQ@mail.gmail.com' \
--to=dave.taht@gmail.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