1 / 6

RMCAT Application Interaction

Discusses conceptual decomposition of RMCAT applications, normative vs. informative language, critical interfaces, and top 5 interactions. Are we guiding congestion control designers effectively?

kdemetrius
Download Presentation

RMCAT Application Interaction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RMCATApplication Interaction draft-ietf-rmcat-app-interaction-01 Mo Zanaty, Varun Singh, SuhasNandakumar, ZahedSarker IETF 91

  2. Goals • Agree on the conceptual decomposition of RMCAT applications to describe interfaces and interactions between congestion control and other functions • Agree on the critical interfaces and interactions • Decide if only informative for normalizing evaluations of solution candidates, or should contain normative language for the scope and interfaces of congestion controllers

  3. Changes since -00 • Focus on top 5 interfaces and interactions • Section 5 now has an overview of the top 5 interactions • Allowed Rate (CC-Codec) • Startup Ramp (CC-Codec) • Delay Tolerance (CC-Codec) • Loss Tolerance (CC-Codec) • Priority / Weight (Config-CC-UDP) • Solution candidates: Please review and provide feedback if these are the top interactions for your algorithm! • Sections 5.x provide further details and more interactions • Replace OS with Network Stack • Acknowledge that user-space stacks are also possible

  4. Conceptual Model Application media and transport configuration, e.g. SDP, WebRTC API constraints, RTP/RTCP, CC Config Codec RTP RTCP Congestion Control Shared State Shared State Network Stack socket interface and other network functions, e.g. ECN, DSCP, PHY events, shaping UDP

  5. Conceptual Model - Top 5 Interactions Application Config Allowed Rate Startup Ramp Delay Tolerance Loss Tolerance Priority Codec RTP RTCP Congestion Control Shared State Shared State Network Stack socket interface and other network functions, e.g. ECN, DSCP, PHY events, shaping UDP

  6. Open Questions • Should the top interactions include Media Elasticity? (range, granularity and convergence time of rate changes) • Informative-only or normative language for the scope and interfaces/interactions of congestion controllers? • Are we providing the right guidance to congestion control designers and application developers? • Are we facilitating evaluation and comparison of solution candidates by normalizing the interfaces and interactions? • Should we move RTP Circuit Breakers (non-) interaction to requirements?

More Related