Opened 8 years ago

Closed 8 years ago

#19 closed defect (fixed)

Section 7.2: Congestion Control Extensions

Reported by: bernard_aboba@… Owned by: draft-ietf-rtcweb-rtp-usage@…
Priority: major Milestone: milestone1
Component: rtp-usage Version: 1.0
Severity: Active WG Document Keywords:
Cc:

Description

7.2. RTCP Extensions for Congestion Control

As described in Section 5.1.6, the Temporary Maximum Media Stream Bit
Rate (TMMBR) request is supported by WebRTC senders. This request
can be used by a media receiver to impose limitations on the media
sender based on the receiver's determined bit-rate limitations, to
provide a limited means of congestion control.

(tbd: What other RTP/RTCP extensions are needed?)

As described in Section 5.1.6, the Temporary Maximum Media Stream Bit
Rate (TMMBR) request is supported by WebRTC senders. This request
can be used by a media receiver to impose limitations on the media
sender based on the receiver's determined bit-rate limitations, to
provide a limited means of congestion control.

(tbd: What other RTP/RTCP extensions are needed?)

With proprietary congestion control algorithms issues can arise when
different algorithms and implementations interact in a communication
session. If the different implementations have made different
choices in regards to the type of adaptation, for example one sender
based, and one receiver based, then one could end up in situation
where one direction is dual controlled, when the other direction is
not controlled.

(tbd: How to ensure that both paths and sender and receiver based
solutions can interact)

[BA] Some nasty unresolved issues here. In particular, I am concerned about potential gaps in worldview between sender-side and receiver-side congestion control implementations. Is our goal here to guarantee that a sender-side implementation can interoperate with a receiver-side implementation? Or that a sender-side implementation has the information it needs?

Change History (1)

comment:1 Changed 8 years ago by bernard_aboba@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.