General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: Alan Jenkins <alan.christopher.jenkins@gmail.com>,
	bloat@lists.bufferbloat.net
Subject: Re: [Bloat] review: Deployment of RITE mechanisms, in use-case trial testbeds report part 1
Date: Sun, 28 Feb 2016 22:27:21 +0100	[thread overview]
Message-ID: <8760x85xvq.fsf@toke.dk> (raw)
In-Reply-To: <87oab0d1sm.wl-jch@pps.univ-paris-diderot.fr> (Juliusz Chroboczek's message of "Sun, 28 Feb 2016 21:20:57 +0100")

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> writes:

>>> Oh, and of course HAS is in itself a hack to work around badly managed
>>> queues in the network. In a nicely fairness queued world, we could do
>>> away with HAS entirely and just, y'know, stream things at the desired
>>> rate...
>
> Perhaps I'm missing something -- how do you to pick the right rate for
> a given user?

Congestion control? With something like fairness queueing that keeps
bandwidth very stable at the fair share, you could conceivably get away
with a much shallower playback buffer in the application and stream at
something very close to real time, rather than using the chunk-based
retrieval of HAS.

However, that remark was mostly meant to be tongue-in-cheek... not sure
if there exists any really good congestion control algorithms for
real-time video.

-Toke

  reply	other threads:[~2016-02-28 21:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56BB8F05.2030006@mti-systems.com>
     [not found] ` <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
2016-02-27 19:04   ` Dave Täht
2016-02-28 13:33     ` Alan Jenkins
2016-02-28 13:39       ` Toke Høiland-Jørgensen
2016-02-28 14:26         ` Alan Jenkins
2016-02-28 20:20           ` Juliusz Chroboczek
2016-02-28 21:27             ` Toke Høiland-Jørgensen [this message]
2016-02-28 21:24           ` Toke Høiland-Jørgensen
2016-02-29 17:55       ` Dave Taht
2016-03-02 11:26     ` [Bloat] [aqm] " De Schepper, Koen (Nokia - BE)
2016-03-02 18:09     ` [Bloat] " Fred Baker (fred)
2016-03-02 20:53       ` Alan Jenkins
2016-03-02 21:47         ` Fred Baker (fred)
2016-03-03 12:13       ` [Bloat] [aqm] " Ingemar Johansson S
2016-03-03 12:31         ` Luca De Cicco
2016-03-03 16:09           ` [Bloat] HAS traffic behaviors Dave Täht
2016-03-03 18:49             ` [Bloat] [aqm] " Luca De Cicco

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=8760x85xvq.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jch@pps.univ-paris-diderot.fr \
    /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