On Aug 15, 2012, at 2:53 AM, Matt Mathis wrote:
/• Reasonable share of bandwidth when competing with RMCAT traffic, other real-time media protocols, TCP and other congestion control protocols. A 'reasonable share' means that no flow has a significantly negative impact [RFC5033] on other flows and at minimum that no flow starves./
This does not work. The hedging language for TCP in the previous text ("idealy") is required because protecting RMCAT from TCP (and other protocols such as LEDBAT) can't be solved in general within the scope of this WG. We can try, and there are some partial solutions that will help some of the time, but there are no general solutions that really solve this problem.
Adding the definition of reasonable share is fine.
So, the final thing could become:
/• Reasonable share of bandwidth when competing with RMCAT traffic, other real-time media protocols, TCP and other congestion control protocols. A 'reasonable share' means that, ideally, no flow has a significantly negative impact [RFC5033] on other flows and at minimum that no flow starves./
(I just added "ideally" to Bob's text above) ?? Cheers, Michael