Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] raptor codes
Date: Sun, 12 Dec 2021 16:32:38 -0800	[thread overview]
Message-ID: <CAA93jw642KEqNAOja36KX2o+DYyE978F==rpYD978J954-c=bQ@mail.gmail.com> (raw)

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

"Mike" Luby (formerly of qualcomm, now the CEO of bitripple) and I
exchanged some email today.

He sent me the attached document explaining in detail how they work.
Up until now I knew of these things, and how they were used, but not
much about their foundations.

I'm a simple guy, I just wanted to know if we could incorporate this
stuff in GPL'd software (e.g. the linux kernel), how big the codebase
needs to be, what APIs made the most sense, what the cpu overheads
were, what code was already available, and the memory (more broadly -
capacity) requirement that vint's still working on...

...

"An identical IPR declaration was made by Qualcomm on the earlier
generation of Raptor codes specified in IETF RFC 5053.  One could
argue that one would like to use another variation of the fountain
codes, but honestly this would lead to the opposite of what David is
trying to achieve, which is interoperability — we designed RaptorQ
specified in IETF RFC 6330 very carefully with essentially ideal
properties so that it could be used as the basis for a agreed upon and
widely deployed standard..."

... If there are hundreds of variants of weird fountain codes out
there, how does that help with interoperability? RaptorQ is part of
the NextGen TV standard (ATSC 3.0) as well, and the reason is for
interoperability"

And lastly: " we at BitRIpple don’t own the IPR rights to RaptorQ, but
I know how to interpret the IPR statement and I know we are just fine.
In fact, BitRipple recently collaborated with Qualcomm and Verizon to
provide the data delivery technology to support the following:

Qualcomm CEO Cristiano Amon (in Hawaii) and Verizon CTO Kyle Malady
(in New Jersey) had the first ever 8K HDR live video conferencing call
between smartphones enabled by BitRipple technology, which was the
first demo during Cristiano’s keynote at the Qualcomm Snapdragon
Technical Summit.

See Qualcomm’s post about this on LinkedIn (https://lnkd.in/g5xTaXDm)
and my post about this as well
(https://www.linkedin.com/posts/michaelluby_watch-qualcomm-and-verizon-demo-worlds-first-activity-6871600498093506560-xl6R).
  There is also a Youtube video of the demo
(https://www.youtube.com/watch?v=Au20PiI27Mg)."




-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

[-- Attachment #2: Raptor_Codes_Foundations_and_Trends®_in_Communications_and_Information_Theory.pdf --]
[-- Type: application/pdf, Size: 1952784 bytes --]

             reply	other threads:[~2021-12-13  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  0:32 Dave Taht [this message]
     [not found] <mailman.1187.1639355577.1267.starlink@lists.bufferbloat.net>
2021-12-13 21:18 ` David P. Reed

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='CAA93jw642KEqNAOja36KX2o+DYyE978F==rpYD978J954-c=bQ@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