I tried for a more concise and "pointy" version of the description of what we need to get done. The text below came out. Is this something we can use as a starting point? What needs to change? This is a charter based on the one suggested in December 2011, but substantially rewritten. It is an input document. Draft is here: https://sites.google.com/a/alvestrand.com/rtp-congestion/bof-planning-page/w... RTP Media Congestion Avoidance Techniques (rmcat) Status: Proposed Working Group Last Updated: 2012-05-08 Chair(s): TBD Transport Area Director(s): Wesley Eddy <wes@mti-systems.com> Transport Area Advisor: Wesley Eddy <wes@mti-systems.com> Mailing Lists: TBD (until establishment, we use rtp-congestion@alvestrand.no) Description of Working Group In today's current internet, part of the traffic is delivery of interactive real time media, often in the form of sets of media flows using RTP over UDP. There is no generally accepted congestion control mechanism for this kind of data flow. With the deployment of applications using the RTCWEB protocol suite, the number of such flows is likely to increase, especially non-fixed-rate flows such as video or adaptive audio. There is therefore some urgency in specifying one or more congestion control mechanisms that can find general acceptance. The set of requirements for such an algorithm includes, but is not limited to: * Low delay for the case where there is no competing traffic using other algorithms * Fair share of bandwidth when there is competing traffic using other algorithms * Effective use of signals like packet loss and ECN markings to adapt to congestion The working group will: * Develop a clear understanding of the congestion control requirements for RTP flows, and document deficiencies of existing mechanisms such as TFRC with regards to these requirements * Determine if there is an appropriate means to define standard RTP/RTCP extensions for carrying congestion control feedback, similar to how DCCP defines CCIDs, and if so, document such extensions as standards-track RFCs. * Define evaluation criteria for proposed mechanisms, and publish these as an Informational RFCs. * Find or develop candidate congestion control algorithms, verify that these can be tested on the Internet without significant risk, and publish one or more of these as Experimental RFCs. * Publish the result of experimentation with these Experimental algorithms on the Internet * Once an algorithm has been found or developed that meets the evaluation criteria, and has a satisfactory amount of documented experience on the Internet, publish this algorithm as a Standards Track RFC. There may be more than one such algorithm. The work will be guided by the advice laid out in RFC 5405 (UDP usage guidelines) and RFC 2914 (congestion control principles). The following topics are out of scope: * Circuit-breaker algorithms for stopping media flows when network conditions render them useless; this work is done in AVTCORE. * Media flows for non-interactive purposes like stored video playback; those are not as delay sensitive as interactive traffic. * Modifications to TCP of any kind. The working group is expected to work closely with the RAI area, including the AVTCORE, AVTEXT and RTCWEB working group. It will also liaise closely with other Transport area groups working on congestion control, and with the Internet Congestion Control Research Group of the IRTF. Deliverables * Evaluation criteria for congestion control algorithms for interactive real time media - Informational RFC * RTCP extensions for use with congestion control algorithms - Standards-track RFC * Candidate congestion control algorithm for interactive real time media - Experimental RFCs (likely more than one) * Experimentation and evaluation results for candidate congestion control algorithms - Informational RFC * A recommended congestion control algorithm for interactive real time media - Standards-track RFC Milestones - still missing