<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rest of comments look fine, I think....<br>
<br>
On 10/28/2011 06:18 AM, Randell Jesup wrote:
<blockquote cite="mid:4EAAABA0.8050806@jesup.org" type="cite"><br>
<blockquote type="cite" style="color: rgb(0, 0, 0);">
<blockquote type="cite" style="color: rgb(0, 0, 0);">
<blockquote type="cite" style="color: rgb(0, 0, 0);"> 8.
When receiving a [ insert new AVPF message here ], the
<br>
sender shall attempt to comply with the overall
bandwidth
<br>
requirements by adjusting parameters it can control,
such
<br>
as codec bitrates and modes, and how much data is
sent on
<br>
the data channels.
<br>
</blockquote>
<br>
Suggest "shall" -> "may".
<br>
</blockquote>
</blockquote>
<br>
For any CC algorithm to work, it really <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>should<span class="moz-txt-tag">*</span></b>
try. It may not be able to comply, the algorithm may include some
smoothing, and the sender may have additional information, so it's
not MUST, but wouldn't MAY be too weak?
<br>
</blockquote>
I was thinking that in some applications over some codecs, it may
simply drop packets, layers or channels, without adjusting any
parameters. Suggest that we insert ", for instance" in front of "by
adjusting" - so that it becomes "the sender shall attempt to comply
with the overall bandwidth requirements, for instance by adjusting
parameters it can control".<br>
<br>
8. When receiving a [ insert new AVPF message here ], the
<br>
sender shall attempt to comply with the overall bandwidth
<br>
requirements, for instance by adjusting parameters it can
control, such
<br>
as codec bitrates and modes, and how much data is sent on
<br>
the data channels.
<br>
<br>
This should be OK for the first cut - long term, we have to discuss
what "comply" means ... whether a leaky bucket algorithm (which
would permit some over-bandwidth burstiness) is an appropriate
model, and if so, how deep the bucket should be, or whether that's a
tunable parameter that can be freely set by the implementation
within some boundaries, or...... for now, let's get a simple
statement that is understandable to the main list.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>