Concluded WG RTP Media Congestion Avoidance Techniques (rmcat)

Congratulations to RMCAT working group on delivering all it's planned deliverables. This working group have produced congestion control algorithms, their evaluation test cases and audio-video traffic models for real-time communications. This has been significant efforts by the working group members, thanks for the good work. There is no current working group document to process. Based on the mailing thread https://mailarchive.ietf.org/arch/msg/rmcat/Kd6d5unN19_1pC6-2fXemcAg_2g/, this working group is now closed.

The newly formed CCWG working group could be a venue for discussing RMCAT related topics if needed in future.

Best Regards, Zaheduzzaman Sarker (Responsible Area director as the closing of the working group)

Resources changed to tracker https://trac.ietf.org/trac/rmcat/report/1 (Issue tracker), wiki https://wiki.ietf.org/group/rmcat (Wiki), zulip https://zulip.ietf.org/#streams/161/rmcat (Zulip Stream) from tracker https://trac.ietf.org/trac/rmcat/report/1 (Issue tracker), wiki https://trac.ietf.org/trac/rmcat/wiki (Wiki), zulip https://zulip.ietf.org/#streams/161/rmcat (Zulip Stream)

As of IETF 111, all drafts with the exception of draft-ietf-rmcat-rtp-cc-feedback have been published. The draft-ietf-rmcat-rtp-cc-feedback draft needs to be updated to give guidance on the use of the feedback format.

As of IETF 110, all drafts with the exception of draft-ietf-rmcat-rtp-cc-feedback have been published. The draft-ietf-rmcat-rtp-cc-feedback draft has expired, and needs to be resurrected to give guidance on the use of the feedback format.

As of IETF 109, all drafts with the exception of draft-ietf-rmcat-rtp-cc-feedback are with the RFC Editor. The draft-ietf-rmcat-rtp-cc-feedback draft has expired, and needs to be resurrected.

As of IETF 108, all drafts with the exception of draft-ietf-rmcat-rtp-cc-feedback are with the RFC Editor. The draft-ietf-rmcat-rtp-cc-feedback draft has expired, and needs to be resurrected.

As of IETF 107, all drafts with the exception of draft-ietf-rmcat-rtp-cc-feedback are with the RFC Editor. The feedback format is in WG last call in AVTCORE. The group has enter an implementation and evaluation phase, but expect draft-ietf-rmcat-rtp-cc-feedback (which discusses how to configure feedback rates for the feedback format) to receive some mailing list discussion.

As of IETF 106, the majority of the RMCAT group's work is complete. The candidate congestion control algorithms and evaluation criteria are published or with the RFC Editor, and the feedback format is nearing completion in AVTCORE. The group will enter an implementation and evaluation phase.

During IETF 105, RMCAT discussed revisions to the congestion control feedback draft that's been updated based on implementation experience and is nearing WG last call in AVTCORE. The NADA congestion control algorithm was updated to address AD review comments. Coupled congestion control was previously brought back to the working group from the RFC Editor based on feedback; the chairs are working with the authors to resolve the issue. The remaining drafts have been updated to resolve the remaining issues, and should advance shortly.

During IETF 104, RMCAT discussed revisions to the congestion control feedback draft based on implementation experience at the hackathon. Coupled congestion control was brought back to the working group based on feedback received at IETF 103 and the chairs are working with the authors to help address the issue. The NADA congestion control algorithm is complete, and ready to go to the IESG. The remaining drafts are resolving minor issues, and should advance shortly.

As of IETF 103, RMCAT had completed working group last call on the evaluation and video traffic model drafts, noting only minor issues. These drafts will be updated, a brief WG last call done to confirm the changes, then sent to the IESG in the November/December 2018. The NADA draft has two implementations, that perform as expected. There were implementations of the congestion control feedback draft at the hackathon, resulting in suggestions for minor updates.

As of IETF 102, RMCAT has completed its initial deliverables (SBD has been published as RFC8382; coupled congestion control is with the RFC Editor; and NADA has completed WG last call). The evaluation and video traffic model drafts are in WG last call, but blocked due to lack of review. The authors of the Google congestion control draft have stated that they do not intended to progress that draft further at this time. The RTCP feedback format is under development in AVTCORE, and has received good feedback.

As of IETF 101, RMCAT has is close to completing its initial deliverables (the SCReAM candidate congestion control algorithm has been published; NADA has completed WG last call; shared bottleneck detection is with the IESG; coupled congestion control is with the RFC Editor). Evaluation, wireless tests, and video traffic model drafts are ready for WG last call.

Open issues:
1) Evaluation criteria has been waiting for an update for some time, but there was good discussion at IETF 101, and we hope this will progress soon; and
2) the RTCP feedback format has been passed to AVTCORE for development, the draft on feedback timing is blocked waiting its completion.

SCReAM has been submitted to IETF. The SBD draft will be ready to go to IESG nits are resolved. NADA has been revised to address WG last call comments, and a new WG last call is expected. The GCC draft is awaiting an update from the authors. The feedback design team has come to consensus on a proposal (draft-dt-rmcat-feedback-message-04) that has been adopted by AVTCORE. The various evaluation and test criteria drafts are essentially done, but are awaiting review. The group agreed that there was value in completing the cc-codec-interactions and framework drafts, but has not yet found the cycles to do so. The group has started discussion on the evaluation needed to move the candidate algorithms to Proposed Standard in future.

The coupled-cc draft has been submitted to the IESG for review. The SCReAM and SBD drafts are ready and the chairs are in the process of writing them up for publication. NADA is being revised to address WG last call comments. The GCC draft is awaiting an update from the authors. The feedback design team has come to consensus on a proposal (draft-dt-rmcat-feedback-message-02) that has been passed to AVTCORE for development. The various evaluation and test criteria drafts are essentially done, and are expected to be submitted to the IESG by IETF 100. The group agreed that there was value in completing the cc-codec-interactions and framework drafts, but that the app-interactions draft has been largely superseded by events. The group has begun discussions on what evaluation is needed to move the candidate algorithms to Proposed Standard in future.

Changed milestone "Submit techniques to detect, instrument or diagnose failing to meet RT schedules to IESG as Informational", set due date to July 2018 from June 2016

Changed milestone "Publish first draft of techniques to detect, instrument or diagnose failing to meet RT schedules", set due date to March 2018 from February 2016

Changed milestone "Submit first congestion control candidate to IESG for Experimental publication", set due date to July 2017 from December 2015, added draft-ietf-rmcat-nada, draft-ietf-rmcat-scream-cc to milestone

The scream, coupled-cc and sbd drafts are ready, and the chairs are in the process of writing them up for publication. The NADA draft is believed close to ready, and should go to WG last call shortly. The group is not meeting in Chicago, but is holding a virtual interim in late April to finalise NADA, and make progress on the RTCP feedback extensions. The chairs will propose updated milestones shortly.

Changed milestone "Submit identifying and controlling groups of flows to IESG for Standards Track publication", set description to "Submit identifying and controlling groups of flows to IESG for Experimental publication"

Changed milestone "Submit techniques to detect, instrument or diagnose failing to meet RT schedules to IESG as Informational", set due date to June 2016 from March 2016

Changed milestone "Publish first draft of techniques to detect, instrument or diagnose failing to meet RT schedules", set due date to February 2016 from September 2015

Changed milestone "Adopt first WG draft of RTCP extensions for use with congestion control algorithms and interactions between applications and RTP flows (if needed)", added draft-ietf-rmcat-rtp-cc-feedback to milestone

Changed milestone "Adopt first WG draft of RTCP extensions for use with congestion control algorithms and interactions between applications and RTP flows (if needed)", added draft-zanaty-rmcat-cc-codec-interactions to milestone

Changed milestone "Submit requirements and evaluation criteria to IESG as Informational", set due date to June 2015 from March 2015, added draft-ietf-rmcat-cc-requirements, draft-ietf-rmcat-eval-criteria to milestone

Changed milestone "Publish first draft of techniques to detect, instrument or diagnose failing to meet RT schedules", set due date to September 2015 from September 2014

Changed milestone "Submit techniques to detect, instrument or diagnose failing to meet RT schedules to IESG as Informational", set due date to March 2016 from March 2015

Changed milestone "Adopt first WG draft of RTCP extensions for use with congestion control algorithms and interactions between applications and RTP flows (if needed)", set due date to August 2014 from December 2013, resolved as "Done"