This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20820 - congestion control of data and audio/video
Summary: congestion control of data and audio/video
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-29 18:33 UTC by Matthew Kaufman
Modified: 2014-10-28 18:47 UTC (History)
4 users (show)

See Also:

Attachments

Description Matthew Kaufman 2013-01-29 18:33:50 UTC 
There is no specification within this document nor in any of its normative references explaining how one must implement interoperable congestion control, in particular how congestion control must interact between the data channels and the audio and video streams.
Comment 1 Cullen Jennings 2013-06-19 13:05:04 UTC 
I think we need a chain of normative references to the circuit breaker spec.
Comment 2 Harald Alvestrand 2013-06-20 12:51:07 UTC 
The circuit-breaker spec:

draft-ietf-avtcore-rtp-circuit-breakers

Normative reference from:

draft-ietf-rtcweb-rtp-usage

Normative reference from:

draft-ietf-rtcweb-overview

Earlier, we have had qualms with making a normative reference to -overview, because it would pull in a lot of patent policy sensitive requirements (including, possibly, the video codec). An informative reference sounds like a non-controversial addition.
Comment 3 Harald Alvestrand 2014-10-28 18:47:37 UTC 
Closing as "this has to be solved in the IETF".

We do have a normative dependency on rtcweb-transport.