General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kristian Kielhofner <kris@kriskinc.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Cake "out of tree" on Debian
Date: Mon, 30 Jan 2017 12:00:42 -0500	[thread overview]
Message-ID: <CAKDfjgcfjrYVftGJsyt6quzFXXRMZx=N27gozL97P84RjrmYhQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6RJ0OOYvCZd3XMnC2is9QV_uGOcGT_3Yejv=-50atmKA@mail.gmail.com>

On Sun, Jan 29, 2017 at 1:06 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>
> Groovy. I thought you were "Mr. VOIP"?
>
> While the default fq scheme works really well in cake, if you test
> marking packets as voip (EF, CS4,CS6,CS7,VA), it will end up in the
> diffserv3 voice queue.
>
> asterisk used to have an encapsulating protocol called iax2, which
> generated a single flow as backhaul - is that still deployed?
>
> We have a tool in flent based on dit-itg to test this. It's a bit
> painful to setup the first time. I've longed to have a full
> asterisk/freeswitch/jitsy test setup to look harder at voip/video
> characteristics.
>
> There are also now several as yet underdocumented options in cake:
>
> "nat" will look at flows before they are natted so as to isolate them better.
> When combined with the dual-dsthost or dual-srchost option (depending
> on traffic direction) that gives you per host fq, along with per-flow
> fq.
>
> (nat triple-isolate should also do this but we're still sorting out a
> bug on that:
> https://github.com/dtaht/sch_cake/issues/46
> )
>
> wash: washes out dscp markings. Helpful when your provider (:cough:
> comcast) remarks nearly all traffic to CS1.
>
> I just found that appear.in is using the new "goog" marker, which
> marks all videoconferencing traffic as AF41, which is more or less
> appropriately handled in the "diffserv4" model.
>
> In general I have always had good results with the simplest
> (besteffort or diffserv3) settings.
>
> There's also new support for a docsis mode using the new "mpu" idea.
>
> https://github.com/dtaht/sch_cake/pull/45
>

Thank you but I'm not sure I was ever "Mr. VOIP"!

Regarding what I would broadly call "QoS" with other priorities and
projects my personal experience looks something like this:

WonderShaper ----------> CoDel/SQM in OpenWRT "just works" ---> "Cake
looks really cool" (rabbit hole...)

Asterisk still has iax2 although I haven't used it in at least 12
years. If I were to guess iax2 probably represents a tiny fraction of
what I'd call "realtime/VoIP traffic" in networks. However, it's
probably overly represented in smaller deployments, hobbyists, and
home users.

In 2017 I'd suggest looking closer at a FreeSWITCH test setup:

- WebRTC (as well as "traditional" SIP/RTP, of course)
- One of the most robust OPUS implementations I'm aware of; with
dynamic and adaptive FEC (forward error correction) and PLC (packet
loss concealment)
- Relatively rich (in the open source ecosystem) video support
(codecs, "MCU functionality", etc):

https://freeswitch.org/confluence/display/FREESWITCH/FreeSWITCH+1.6+Video

-- 
Kristian Kielhofner

      reply	other threads:[~2017-01-30 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29  2:48 Kristian Kielhofner
2017-01-29  4:51 ` Y
2017-01-29  5:00 ` Y
2017-01-29 10:50 ` Jonathan Morton
2017-01-29 17:36   ` Kristian Kielhofner
2017-01-29 17:42     ` Dave Taht
2017-01-29 17:48       ` Kristian Kielhofner
2017-01-29 18:06         ` Dave Taht
2017-01-30 17:00           ` Kristian Kielhofner [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='CAKDfjgcfjrYVftGJsyt6quzFXXRMZx=N27gozL97P84RjrmYhQ@mail.gmail.com' \
    --to=kris@kriskinc.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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