From: Dave Taht <dave.taht@gmail.com>
To: Oleg Kutkov <contact@olegkutkov.me>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] System and method of providing a medium access control scheduler
Date: Thu, 23 Feb 2023 17:17:33 -0800 [thread overview]
Message-ID: <CAA93jw7QV3f6ETwBkuYRdwzFU6Af10rsCsvUXZPsFeDjzqZ9zg@mail.gmail.com> (raw)
In-Reply-To: <5306fbfd-36fc-f9fe-55f8-c0f95b603795@olegkutkov.me>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
I do hope more patents appear. There is apparently no support for retries
at this layer (yay!), no documentation on what error correction is used
besides OFDMA, or how packets are encrypted.
Some of the patents cited are pretty interesting, notably the oldest one.
Good to have some baseline numbers for the intervals!
[-- Attachment #2: Type: text/html, Size: 383 bytes --]
prev parent reply other threads:[~2023-02-24 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:53 Dave Taht
2023-02-23 23:47 ` Oleg Kutkov
2023-02-24 0:08 ` David Lang
2023-02-24 0:18 ` Oleg Kutkov
2023-02-24 0:51 ` Ulrich Speidel
2023-02-24 1:05 ` Oleg Kutkov
2023-02-24 1:17 ` Dave Taht [this message]
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=CAA93jw7QV3f6ETwBkuYRdwzFU6Af10rsCsvUXZPsFeDjzqZ9zg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=contact@olegkutkov.me \
--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