General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] quic's spin bit proposal
Date: Fri, 15 Dec 2017 17:06:34 +0000	[thread overview]
Message-ID: <CAGrdgiVP4cSVoMmpqgh7p=2roaAHonK_SEY1VBzrboZwv2+8hQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7TNaNNs8t9v-hnA59jznKWL0DssS8oYbrm++70yDj+3g@mail.gmail.com>

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

On Tue, Dec 12, 2017 at 9:47 PM Dave Taht <dave.taht@gmail.com> wrote:

>
> In a world where quic is 7% of all traffic presently (wow, I didn't
> know)...
>
>
BitTorrent's MicroTP (uTP) had about 15% at some point as well. This was
especially scary as:

* it used the then not-fully-understood LEDBAT congestion algorithm.
* the de-facto implementation wasn't too well understood and there no
competing implementations in order to understand interoperability.
* there were no formal process when it was created.
* for simplicty it dropped half-open connections. But implemented that in a
slightly faulty way.

I know, because I had an experiment where I did an Erlang-implementation of
the protocol.

At least QUIC seems to be getting some process now, which is good.

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

      reply	other threads:[~2017-12-15 17:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 20:46 Dave Taht
2017-12-15 17:06 ` Jesper Louis Andersen [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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGrdgiVP4cSVoMmpqgh7p=2roaAHonK_SEY1VBzrboZwv2+8hQ@mail.gmail.com' \
    --to=jesper.louis.andersen@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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