From: Sebastian Moeller <moeller0@gmx.de>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] curious.....
Date: Mon, 9 Dec 2013 10:51:25 +0100 [thread overview]
Message-ID: <25FDEED2-23A8-4EF4-8921-ACCF65E0CC62@gmx.de> (raw)
In-Reply-To: <20131208204152.B9918406062@ip-64-139-1-69.sjc.megapath.net>
Hi Hal,
On Dec 8, 2013, at 21:41 , Hal Murray <hmurray@megapathdsl.net> wrote:
>
>> Even at 1000 symmetric I still think it would be a good idea to isolate
>> really latency critical traffic from the rest, even if under normal
>> circumstances there should be no problem, I guess a "better safe than sorry"
>> approach. But, hey I do not do this for a living so I might be on the wrong
>> track here.
>
> The problem is who gets to decide what is latency critical and/or how to do
> it such that the bad-guys can't game the system.
Ah, that is easy, in your home-router that is you :); no one else knows how much you value uninterrupted VoIP sessions. Now as always this is not perfect as you can not fully control the marking on the downlink, but in that case I still think it makes sense to mark on your router and shape the downlink, while not as good as the uplink shaping and marking it still improves things noticeably.
best
Sebastian
>
> Has somebody made a list of various interesting cases, and where they break?
>
>
>
>
> --
> These are my opinions. I hate spam.
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2013-12-09 9:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09 9:51 ` Sebastian Moeller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04 0:25 ` Outback Dingo
2013-12-04 0:38 ` Dave Taht
2013-12-06 17:19 ` Juliusz Chroboczek
2013-12-06 18:15 ` Dave Taht
2013-12-07 11:24 ` Sebastian Moeller
2013-12-10 19:05 ` Dave Taht
2013-12-11 10:44 ` Sebastian Moeller
2013-12-07 12:59 ` Juliusz Chroboczek
2013-12-08 1:27 ` Steinar H. Gunderson
2013-12-08 5:24 ` Mikael Abrahamsson
2013-12-08 11:00 ` Mark Constable
2013-12-08 14:01 ` Outback Dingo
2013-12-08 14:03 ` Outback Dingo
2013-12-08 16:44 ` Mark Constable
2013-12-08 19:00 ` Sebastian Moeller
2013-12-08 13:12 ` Juliusz Chroboczek
2013-12-08 16:46 ` Jonathan Morton
2013-12-08 16:51 ` Dave Taht
2013-12-08 17:56 ` Juliusz Chroboczek
2013-12-08 21:05 ` Jonathan Morton
2013-12-08 14:22 ` Aaron Wood
2013-12-08 14:41 ` Jim Gettys
2013-12-08 10:40 ` Sebastian Moeller
2013-12-08 13:25 ` Juliusz Chroboczek
2013-12-08 16:26 ` Sebastian Moeller
2013-12-08 17:47 ` Juliusz Chroboczek
2013-12-08 19:02 ` Sebastian Moeller
2013-12-22 1:38 ` Dan Siemon
2013-12-22 3:46 ` Stephen Hemminger
2013-12-08 19:01 ` Jonathan Morton
2013-12-08 19:21 ` Sebastian Moeller
2013-12-08 16:01 ` Neil Davies
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=25FDEED2-23A8-4EF4-8921-ACCF65E0CC62@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=hmurray@megapathdsl.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