From: Kevin Gross <kevin.gross@avanw.com>
To: Forums1000 <forums1000@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The bigger picture: what components are used together to fight bloat
Date: Sat, 4 May 2013 13:24:03 -0600 [thread overview]
Message-ID: <CALw1_Q34Q7dWGntDKPNM=dbPZ0NOWk7vp3_a+GzmSnSoWtDQSA@mail.gmail.com> (raw)
In-Reply-To: <CANfPCkWVpg9d0C=pJ7X5pp9Ohquxfh+WUPBgGVNA6z1nT_PS-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Not quite UDP, but RTP congestion avoidance is being worked on in the IETF.
Please join us - http://datatracker.ietf.org/wg/rmcat/charter/
Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org
On Thu, May 2, 2013 at 5:44 AM, Forums1000 <forums1000@gmail.com> wrote:
> I hope I can get a bit more information on what comprises the total
> solution. But knitting it together proves a bit hard (for me at least).
> Without this, it is hard to follow the discussions on the list. Has anyone
> made a summary of how all of this works together?
>
> So:
>
> 1. In order to move the bottleneck to a device under our administrative
> control, we need to shape traffic (we need to become the bottleneck).
> 2. Next, we have the AQM-algorithms that manage the (or a) queue.
> 3. And then there are still issues with multiple flows and with UDP?
>
> From what I understand, we need to shape traffic, and then drop packets
> taking into account that the most aggressive flow (the flow that
> contributes the most to filling a buffer), is the flow that will get the
> most packets dropped. This to prevent the aggressive flow from impacting
> flows that behave better.
>
> Now for UDP, is the problem here that we cannot identify flows, and hence,
> only have one queue for UDP whereas for TCP we can have multiple?
>
> Any good resources are more than welcome:-)!
>
> Thanks,
> Jeroen
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
[-- Attachment #2: Type: text/html, Size: 2355 bytes --]
next prev parent reply other threads:[~2013-05-04 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 11:44 Forums1000
2013-05-04 19:24 ` Kevin Gross [this message]
2013-05-04 20:56 ` Dave Taht
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='CALw1_Q34Q7dWGntDKPNM=dbPZ0NOWk7vp3_a+GzmSnSoWtDQSA@mail.gmail.com' \
--to=kevin.gross@avanw.com \
--cc=bloat@lists.bufferbloat.net \
--cc=forums1000@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