[AVTCORE] Stephen Farrell's No Objection on draft-ietf-avtcore-rtp-circuit-breakers-15: (with COMMENT)

["Stephen Farrell" <[e-mail]>]

Stephen Farrell has entered the following ballot position for
draft-ietf-avtcore-rtp-circuit-breakers-15: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


I just have a nit and a random query...

- nit: The abstract says "It is expected that future
standards-track congestion control algorithms for RTP will
operate within the envelope defined by this memo." That
seems both unwise and unlikely to work to me. Unwise in
that you're trying to control the future which seems like
it'll just generate heat and not light, and unlikely to
work since it's not clear to me that any CC scheme can
take into account circuit breaker constants configured on
a node that may not be known anywhere else. I'd say better
would be to say that we hope that future CC algorithms
will be consistent with this and leave it at that.
However, if that sentence is the product of a bunch of
haggling then it's probably better to leave it as-is and
I'll just hold my nose a bit;-) (Same sentence is in the
intro - same comment.)

- query: Assuming people have implemented some or all of
this, I wondered if it'd be a good idea to document some
of the ways in which those implementations went wrong,
i.e. bugs already fixed, especially if there were any
that'd result in the circuit not being broken when it
ought be. But that's probably too late or better done in
some other document for now, so feel free to ignore me.