From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "Dave Täht" <dave@taht.net>, "aqm@ietf.org" <aqm@ietf.org>,
"rmcat@ietf.org" <rmcat@ietf.org>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [rmcat] webrtc vs aqm and/or sfq
Date: Sat, 27 Aug 2016 10:01:16 +0000 [thread overview]
Message-ID: <DB4PR07MB34843FB4CDBD276BBE71921C2EF0@DB4PR07MB348.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <fff498ff-a205-eadb-7c17-3a9420d1b439@taht.net>
Hi
For what it is worth, ECN handling is described for SCReAM since a while back.
It is however not yet implemented in the code at (https://github.com/EricssonResearch/scream ), this is however a quite easy task to do and if the interest in SCReAM picks up then I am happy to spend the 2-3 hours that it takes to add ECN support to the code.
/Ingemar
> -----Original Message-----
> From: Dave Täht [mailto:dave@taht.net]
> Sent: den 26 augusti 2016 08:15
> To: aqm@ietf.org; rmcat@ietf.org; bloat@lists.bufferbloat.net
> Subject: [rmcat] webrtc vs aqm and/or sfq
>
> Pretty good paper at:
>
> http://c3lab.poliba.it/images/0/0e/Gcc_aqm.pdf
>
> I do keep hoping the videoconferencing folk give ecn a shot one day,
> especially for iframes. Has anyone pursued the early line of work for ecn that
> was in nada, or tried to add it to gcc?
>
> Another hope is that we see more videoconferencing analyses on wifi and at
> higher baseline rates than 2mbit.
>
prev parent reply other threads:[~2016-08-27 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 6:14 [Bloat] " Dave Täht
2016-08-27 10:01 ` Ingemar Johansson S [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=DB4PR07MB34843FB4CDBD276BBE71921C2EF0@DB4PR07MB348.eurprd07.prod.outlook.com \
--to=ingemar.s.johansson@ericsson.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=rmcat@ietf.org \
/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